Inside Macintosh/Inside Macintosh CD-ROM_1995 (CD).toast/Books/Interapplication Comm/Interapplication Comm

Text File | 1994-08-11 | 14MB | 40,181 lines

INSIDE MACINTOSHInterapplication CommunicationISBN 0-201-62200-91 2 3 4 5 6 7 8 9-MU-9796959493First Printing, June 1993    Apple Computer, Inc.© 1993, Apple Computer, Inc.All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, mechanical, electronic, photocopying, recording, or otherwise, without prior written permission of Apple Computer, Inc. Printed in the United States of America.No licenses, express or implied, are granted with respect to any of the technology described in this book. Apple retains all intellectual property rights associated with the technology described in this book. This book is intended to assist application developers to develop applications only for Apple Macintosh computers.Apple Computer, Inc.20525 Mariani AvenueCupertino, CA 95014408-996-1010Apple, the Apple logo, APDA, AppleLink, AppleTalk, LaserWriter, Macintosh, MPW, and SANE are trademarks of Apple Computer, Inc., registered in the United States and other countries.AppleScript, Finder, Moof, New York, QuickDraw, QuickTime, and System 7 are trademarks of Apple Computer, Inc.Adobe Illustrator, Adobe Photoshop, and PostScript are trademarks of Adobe Systems Incorporated, which may be registered in certain jurisdictions.America Online is a service mark of Quantum Computer Services, Inc.CompuServe is a registered trademark of CompuServe, Inc.FrameMaker is a registered trademark of Frame Technology Corporation.Helvetica, Palatino, and Times are registered trademarks of Linotype Company.HyperCard and HyperTalk are registered trademarks of Claris Corporation.Internet is a trademark of Digital Equipment Corporation.ITC Zapf Dingbats is a registered trademark of International Typeface Corporation.Optrotech is a trademark of Orbotech Corporation.Simultaneously published in the United States and Canada.LIMITED WARRANTY ON MEDIA AND REPLACEMENTALL IMPLIED WARRANTIES ON THIS MANUAL, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ARE LIMITED IN DURATION TO NINETY (90) DAYS FROM THE DATE OF THE ORIGINAL RETAIL PURCHASE OF THIS PRODUCT.Even though Apple has reviewed this manual, APPLE MAKES NO WARRANTY OR REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS MANUAL, ITS QUALITY, ACCURACY, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. AS A RESULT, THIS MANUAL IS SOLD “AS IS,” AND YOU, THE PURCHASER, ARE ASSUMING THE ENTIRE RISK AS TO ITS QUALITY AND ACCURACY.IN NO EVENT WILL APPLE BE LIABLE FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES RESULTING FROM ANY DEFECT OR INACCURACY IN THIS MANUAL, even if advised of the possibility of such damages.THE WARRANTY AND REMEDIES SET FORTH ABOVE ARE EXCLUSIVE AND IN LIEU OF ALL OTHERS, ORAL OR WRITTEN, EXPRESS OR IMPLIED. No Apple dealer, agent, or employee is authorized to make any modification, extension, or addition to this warranty.Some states do not allow the exclusion or limitation of implied warranties or liability for incidental or consequential damages, so the above limitation or exclusion may not apply to you. This warranty gives you specific legal rights, and you may also have other rights which vary from state to state.ContentsFigures, Tables, and ListingsxvPreface    About This BookxxiiiFormat of a Typical ChapterxxivConventions Used in This BookxxvSpecial FontsxxvTypes of NotesxxvAssembly-Language InformationxxviThe Development EnvironmentxxviChapter 1    Introduction to Interapplication Communication1-1Overview of Interapplication Communication1-3Sharing Data Among Applications1-6Sending and Responding to Apple Events1-9Standard Apple Events1-10Handling Apple Events1-12Supporting AppleScript and Other Scripting Languages1-13Scriptable Applications1-16Recordable Applications1-18Applications That Manipulate and Execute Scripts1-19Exchanging Message Blocks1-22Chapter 2    Edition Manager2-1Introduction to Publishers, Subscribers, and Editions2-4About the Edition Manager2-12Using the Edition Manager2-12Receiving Apple Events From the Edition Manager2-13Creating the Section Record and Alias Record2-15Saving a Document Containing Sections2-19Opening and Closing a Document Containing Sections2-22Reading and Writing a Section2-24Formats in an Edition2-24Opening an Edition2-26Format Marks2-27Reading and Writing Edition Data2-27Closing an Edition2-28Creating a Publisher2-29Creating the Edition Container2-32Opening an Edition Container to Write Data2-35Creating a Subscriber2-37Opening an Edition Container to Read Data2-41Choosing Which Edition Format to Read2-41Using Publisher and Subscriber Options2-43Publishing a New Edition While Saving or Manually2-47Subscribing to an Edition Automatically or Manually2-48Canceling Sections Within Documents2-48Locating a Publisher Through a Subscriber2-49Renaming a Document Containing Sections2-50Displaying Publisher and Subscriber Borders2-50Text Borders2-54Spreadsheet Borders2-55Object-Oriented Graphics Borders2-56Bitmapped Graphics Borders2-57Duplicating Publishers and Subscribers2-58Modifying a Subscriber2-59Relocating an Edition2-60Customizing Dialog Boxes2-60Subscribing to Non-Edition Files2-62Getting the Current Edition Opener2-63Setting an Edition Opener2-63Calling an Edition Opener2-64Opening and Closing Editions2-68Listing Files That Can Be Subscribed To2-68Reading From and Writing to Files2-68Calling a Format I/O Function2-68Edition Manager Reference2-71Data Structures2-71The Edition Container Record2-71The Section Record2-72Edition Manager Routines2-73Initializing the Edition Manager2-74Creating and Registering a Section2-74Creating and Deleting an Edition Container2-79Setting and Getting a Format Mark2-81Reading in Edition Data2-83Writing out Edition Data2-86Closing an Edition After Reading or Writing2-88Displaying Dialog Boxes2-90Locating a Publisher and Edition From a Subscriber2-98Edition Container Formats2-101Reading and Writing Non-Edition Files2-102Application-Defined Routines2-105Summary of the Edition Manager2-106Pascal Summary2-106Constants2-106Data Types2-108Edition Manager Routines2-111Application-Defined Routines2-113C Summary2-114Constants2-114Data Types2-116Edition Manager Routines2-119Application-Defined Routines2-122Result Codes2-122Chapter 3    Introduction to Apple Events3-1About Apple Events3-3Apple Events and Apple Event Objects3-6Apple Event Attributes and Parameters3-7Apple Event Attributes3-8Apple Event Parameters3-9Interpreting Apple Event Attributes and Parameters3-10Data Structures Within Apple Events3-12Descriptor Records3-12Keyword-Specified Descriptor Records3-15Descriptor Lists3-16Responding to Apple Events3-20Accepting and Processing Apple Events3-20About Apple Event Handlers3-23Extracting and Checking Data3-23Interacting With the User3-25Performing the Requested Action and Returning a Result3-25Creating and Sending Apple Events3-28Creating an Apple Event Record3-29Adding Apple Event Attributes and Parameters3-29Sending an Apple Event and Handling the Reply3-30Working With Object Specifier Records3-32Data Structures Within an Object Specifier Record3-34The Classification of Apple Event Objects3-39Object Classes3-39Properties and Elements3-42Finding Apple Event Objects3-46About the Apple Event Manager3-48Supporting Apple Events as a Server Application3-48Supporting Apple Events as a Client Application3-49Supporting Apple Event Objects3-49Supporting Apple Event Recording3-50Chapter 4    Responding to Apple Events4-1Handling Apple Events4-4Accepting an Apple Event4-5Installing Entries in the Apple Event Dispatch Tables4-7Installing Entries for the Required Apple Events4-8Installing Entries for Apple Events Sent by the Edition Manager4-9How Apple Event Dispatching Works4-9Handling the Required Apple Events4-11Required Apple Events4-11Handling the Open Application Event4-14Handling the Open Documents Event4-15Handling the Print Documents Event4-17Handling the Quit Application Event4-19Handling Apple Events Sent by the Edition Manager4-20The Section Read, Section Write, and Section Scroll Events4-21Handling the Create Publisher Event4-22Getting Data Out of an Apple Event4-25Getting Data Out of an Apple Event Parameter4-26Getting Data Out of an Attribute4-28Getting Data Out of a Descriptor List4-31Writing Apple Event Handlers4-33Replying to an Apple Event4-36Disposing of Apple Event Data Structures4-39Writing and Installing Coercion Handlers4-41Interacting With the User4-45Setting the Client Application’s User Interaction Preferences4-46Setting the Server Application’s User Interaction Preferences4-48Requesting User Interaction4-49Reference to Responding to Apple Events4-56Data Structures Used by the Apple Event Manager4-56Descriptor Records and Related Data Structures4-56Apple Event Array Data Types4-60Routines for Responding to Apple Events4-61Creating and Managing the Apple Event Dispatch Tables4-61Dispatching Apple Events4-66Getting Data or Descriptor Records Out of Apple Event Parameters and Attributes4-68Counting the Items in Descriptor Lists4-74Getting Items From Descriptor Lists4-74Getting Data and Keyword-Specified Descriptor Records Out of AE Records4-78Requesting User Interaction4-81Requesting More Time to Respond to Apple Events4-84Suspending and Resuming Apple Event Handling4-85Getting the Sizes and Descriptor Types of Descriptor Records4-89Deleting Descriptor Records4-92Deallocating Memory for Descriptor Records4-93Coercing Descriptor Types4-94Creating and Managing the Coercion Handler Dispatch Tables4-96Creating and Managing the Special Handler Dispatch Tables4-99Getting Information About the Apple Event Manager4-103Application-Defined Routines4-104Summary of Responding to Apple Events4-108Pascal Summary4-108Constants4-108Data Types4-112Routines for Responding to Apple Events4-114Application-Defined Routines4-118C Summary4-118Constants4-118Data Types4-123Routines for Responding to Apple Events4-124Application-Defined Routines4-128Assembly-Language Summary4-128Trap Macros4-128Result Codes4-130Chapter 5    Creating and Sending Apple Events5-1Creating an Apple Event5-3Adding Parameters to an Apple Event5-5Specifying Optional Parameters for an Apple Event5-7Specifying a Target Address5-10Creating an Address Descriptor Record5-11Addressing an Apple Event for Direct Dispatching5-13Sending an Apple Event5-13Dealing With Timeouts5-20Writing an Idle Function5-21Writing a Reply Filter Function5-24Reference to Creating and Sending Apple Events5-24Routines for Creating and Sending Apple Events5-25Creating Apple Events5-25Creating and Duplicating Descriptor Records5-26Creating Descriptor Lists and AE Records5-28Adding Items to Descriptor Lists5-29Adding Data and Descriptor Records to AE Records5-32Adding Parameters and Attributes to Apple Events5-33Sending Apple Events5-37Application-Defined Routines5-41Summary of Creating and Sending Apple Events5-44Pascal Summary5-44Constants5-44Data Types5-48Routines for Creating and Sending Apple Events5-50Application-Defined Routines5-51C Summary5-51Constants5-51Data Types5-56Routines for Creating and Sending Apple Events5-57Application-Defined Routines5-59Assembly-Language Summary5-59Trap Macros5-59Result Codes5-60Chapter 6    Resolving and Creating Object Specifier Records6-1Resolving Object Specifier Records6-4Descriptor Records Used in Object Specifier Records6-8Object Class6-9Container6-9Key Form6-11Key Data6-12Key Data for a Property ID6-13Key Data for an Object’s Name6-14Key Data for a Unique ID6-14Key Data for Absolute Position6-14Key Data for Relative Position6-15Key Data for a Test6-15Key Data for a Range6-20Installing Entries in the Object Accessor Dispatch Tables6-21Installing Object Accessor Functions That Find Apple Event Objects6-23Installing Object Accessor Functions That Find Properties6-27Writing Object Accessor Functions6-28Writing Object Accessor Functions That Find Apple Event Objects6-29Writing Object Accessor Functions That Find Properties6-37Defining Tokens6-39Handling Whose Tests6-41Writing Object Callback Functions6-45Writing an Object-Counting Function6-48Writing an Object-Comparison Function6-50Writing Marking Callback Functions6-53Creating Object Specifier Records6-55Creating a Simple Object Specifier Record6-57Specifying the Container Hierarchy6-61Specifying a Property6-63Specifying a Relative Position6-64Creating a Complex Object Specifier Record6-64Specifying a Test6-64Specifying a Range6-72Reference to Resolving and Creating Object Specifier Records6-75Data Structures Used in Object Specifier Records6-75Routines for Resolving and Creating Object Specifier Records6-77Initializing the Object Support Library6-77Setting Object Accessor Functions and Object Callback Functions6-77Getting, Calling, and Removing Object Accessor Functions6-81Resolving Object Specifier Records6-85Deallocating Memory for Tokens6-87Creating Object Specifier Records6-88Application-Defined Routines6-94Object Accessor Functions6-94Object Callback Functions6-96Summary of Resolving and Creating Object Specifier Records6-104Pascal Summary6-104Constants6-104Data Types6-106Routines for Resolving and Creating Object Specifier Records6-106Application-Defined Routines6-108C Summary6-109Constants6-109Data Types6-111Routines for Resolving and Creating Object Specifier Records6-112Application-Defined Routines6-114Assembly-Language Summary6-115Trap Macros6-115Result Codes6-115Chapter 7    Introduction to Scripting7-1About Scripts and Scripting Components7-4Script Editors and Script Files7-6Scripting Components and Scriptable Applications7-8Scripting Components and Applications That Execute Scripts7-11Making Your Application Scriptable7-14About Apple Event Terminology Resources7-15How AppleScript Uses Terminology Information7-17Dynamic Loading of Terminology Information7-20Making Your Application Recordable7-20Manipulating and Executing Scripts7-22Compiling, Saving, Modifying, and Executing Scripts7-24Using a Script Context to Handle an Apple Event7-25Chapter 8    Apple Event Terminology Resources8-1Defining Terminology for Use by the AppleScript Component8-3Structure of Apple Event Terminology Resources8-8Creating an Apple Event Terminology Extension Resource8-13Supporting Standard Suites Without Extensions8-14Extending the Standard Suites8-16Supporting Subsets of Suites8-23Supporting New Suites8-23Handling the Get AETE Event8-23Reference to Apple Event Terminology Resources8-26Header Data for an Apple Event Terminology Resource8-27Suite Data for an Apple Event Terminology Resource8-27Event Data8-29Object Class Data8-36Comparison Operator Data8-42Enumeration and Enumerator Data8-43The Scripting Size Resource8-45Chapter 9    Recording Apple Events9-1About Recordable Applications9-3Factoring Your Application for Recording9-6Factoring the Quit Command and the New Command9-6Sending Apple Events Without Executing Them9-12What to Record9-14Recording User Actions9-15Recording the Selection of Text Objects9-18Recording Insertion Points9-23Recording Typing9-27Recording the Selection of Nontext Objects9-30Identifying Objects9-32Moving the Selection During Recording9-34Recording Interactions With Dialog Boxes9-35How Apple Event Recording Works9-35Chapter 10    Scripting Components10-1Connecting to a Scripting Component10-3Using Scripting Component Routines10-7Compiling and Executing Source Data10-7Saving Script Data10-12Storage Formats for Script Data10-12Resource and File Types for Script Data10-13Loading and Executing Script Data10-14Modifying and Recompiling a Compiled Script10-17Using a Script Context to Handle an Apple Event10-19Supplying a Resume Dispatch Function10-21Supplying an Alternative Active Function10-23Supplying Alternative Create and Send Functions10-24Alternative Create Functions10-24Alternative Send Functions10-25Recording Scripts10-26Writing a Scripting Component10-27Scripting Components Reference10-28Data Structures10-29Required Scripting Component Routines10-30Saving and Loading Script Data10-30Executing and Disposing of Scripts10-33Setting and Getting Script Information10-41Manipulating the Active Function10-45Optional Scripting Component Routines10-46Compiling Scripts10-47Getting Source Data10-51Coercing Script Values10-52Manipulating the Create and Send Functions10-55Recording Scripts10-59Executing Scripts in One Step10-61Manipulating Dialects10-67Using Script Contexts to Handle Apple Events10-71AppleScript Component Routines10-80Initializing AppleScript10-80Getting and Setting Styles for Source Data10-82Generic Scripting Component Routines10-84Getting and Setting the Default Scripting Component10-86Using Component-Specific Routines10-87Routines Used by Scripting Components10-92Manipulating Trailers for Generic Storage Descriptor Records10-92Application-Defined Routines10-94Summary of Scripting Components10-99Pascal Summary10-99Constants10-99Data Types10-105Required Scripting Component Routines10-106Optional Scripting Component Routines10-107AppleScript Component Routines10-110Generic Scripting Component Routines10-110Routines Used by Scripting Components10-111Application-Defined Routines10-111C Summary10-112Constants10-112Data Types10-118Required Scripting Component Routines10-119Optional Scripting Component Routines10-120AppleScript Component Routines10-123Generic Scripting Component Routines10-123Routines Used by Scripting Components10-124Application-Defined Routines10-124Result Codes10-125Chapter 11    Program-to-Program Communications Toolbox11-1About the PPC Toolbox11-4Ports, Sessions, and Message Blocks11-4Setting Up Authenticated Sessions11-6Using the PPC Toolbox11-10PPC Toolbox Calling Conventions11-14Specifying Port Names and Location Names11-17Opening a Port11-20Browsing for Ports Using the Program Linking Dialog Box11-22Obtaining a List of Available Ports11-27Preparing for a Session11-29Initiating a PPC Session11-29Receiving Session Requests11-35Accepting or Rejecting Session Requests11-37Exchanging Data During a PPC Session11-39Reading Data From an Application11-40Sending Data to an Application11-42Ending a Session and Closing a Port11-43Invalidating Users11-44PPC Toolbox Reference11-46Data Structures11-46The PPC Toolbox Parameter Block11-46The PPC Port Record11-48The Location Name Record11-49The Port Information Record11-50PPC Toolbox Routines11-50Initializing the PPC Toolbox11-51Using the Program Linking Dialog Box11-51Obtaining a List of Ports11-54Opening and Closing a Port11-56Starting and Ending a Session11-59Receiving, Accepting, and Rejecting a Session11-66Reading and Writing Data11-71Locating a Default User and Invalidating a User11-75Application-Defined Routines11-77Completion Routines for PPC Toolbox Routines11-77Port Filter Functions11-78Summary of the PPC Toolbox11-80Pascal Summary11-80Constants11-80Data Types11-81PPC Toolbox Routines11-87Application-Defined Routines11-88C Summary11-89Constants11-89Data Types11-90PPC Toolbox Routines11-95Application-Defined Routines11-96Assembly-Language Summary11-96Trap Macros11-96Result Codes11-97Chapter 12    Data Access Manager12-1About the Data Access Manager12-5The High-Level Interface12-7Sending a Query Through the High-Level Interface12-8Retrieving Data Through the High-Level Interface12-9The Low-Level Interface12-9Sending a Query Through the Low-Level Interface12-10Retrieving Data Through the Low-Level Interface12-11Comparison of the High-Level and Low-Level Interfaces12-11Using the Data Access Manager12-12Executing Routines Asynchronously12-12General Guidelines for the User Interface12-13Keep the User in Control12-13Provide Feedback to the User12-13Using the High-Level Interface12-14Writing a Status Routine for High-Level Functions12-22Using the Low-Level Interface12-28Getting Information About Sessions in Progress12-35Processing Query Results12-36Getting Query Results12-36Converting Query Results to Text12-42Creating a Query Document12-46User Interface Guidelines for Query Documents12-46Contents of a Query Document12-48Query Records and Query Resources12-51Writing a Query Definition Function12-51Data Access Manager Reference12-54Data Structures12-54The Asynchronous Parameter Block12-55The Query Record12-56The Results Record12-58Data Access Manager Routines12-59Initializing the Data Access Manager12-60High-Level Interface: Handling Query Documents12-61High-Level Interface: Handling Query Results12-65Low-Level Interface: Controlling the Session12-68Low-Level Interface: Sending and Executing Queries12-76Low-Level Interface: Retrieving Results12-82Installing and Removing Result Handlers12-86Application-Defined Routines12-89Resources12-90The Query Resource12-90The Query String Resource12-91The Query Definition Function Resource12-92Summary of the Data Access Manager12-93Pascal Summary12-93Constants12-93Data Types12-94Data Access Manager Routines12-96Application-Defined Routines12-98C Summary12-98Constants12-98Data Types12-100Data Access Manager Routines12-101Application-Defined Routines12-103Assembly-Language Summary12-103Trap Macros12-103Result Codes12-104GlossaryGL-1IndexIN-1Figures, Tables, and ListingsPreface    About This BookxxiiiChapter 1    Introduction to Interapplication Communication1-1Figure 1-1    Principal methods of communication between applications1-5Figure 1-2    Sharing data with the aid of the Edition Manager1-7Figure 1-3    A publisher, an edition, and a subscriber1-8Figure 1-4    Sharing dynamic data with other applications1-8Figure 1-5    Sending and responding to Apple events with the aid of the Apple Event Manager1-10Figure 1-6    A Set Data event1-12Figure 1-7    How a scripting component executes a script1-14Figure 1-8    A Set Data event sent during script execution1-17Figure 1-9    Recording user actions in a factored application1-19Figure 1-10    Controlling an application’s own behavior by executing a script1-20Figure 1-11    Posting an invoice and updating a database by executing a script1-21Chapter 2    Edition Manager2-1Figure 2-1    The default edition icon2-4Figure 2-2    A publisher, an edition, and a subscriber2-5Figure 2-3    The publisher dialog box2-5Figure 2-4    The subscriber dialog box2-7Figure 2-5    A document and its corresponding editions2-8Figure 2-6    Publisher and subscriber borders2-9Figure 2-7    Edition Manager commands in the Edit menu2-10Figure 2-8    Edition Manager commands under the Publishing menu command2-11Figure 2-9    A document with a publisher and subscriber and its resource fork2-16Figure 2-10    The new publisher alert box2-19Figure 2-11    A sample publisher dialog box2-29Figure 2-12    A sample subscriber dialog box2-37Figure 2-13    The publisher options dialog box with update mode set to On Save2-43Figure 2-14    The publisher options dialog box with update mode set to Manually2-44Figure 2-15    The subscriber options dialog box with update mode set to Automatically2-44Figure 2-16    The subscriber options dialog box with update mode set to Manually2-45Figure 2-17    Edit menu with Show/Hide Borders menu command2-51Figure 2-18    Publisher borders2-52Figure 2-19    Subscriber borders2-53Figure 2-20    A publisher with contents removed2-54Figure 2-21    A publisher border within a spreadsheet document2-55Figure 2-22    A publisher border with resize handles2-56Figure 2-23    A publisher and subscriber with clipped graphics2-57Figure 2-24    Creating multiple publishers alert box2-58Figure 2-25    Saving multiple publishers alert box2-58Figure 2-26    Subscribing directly to a 'PICT' file2-62Listing 2-1    Accepting Section Read events and verifying if a section is registered2-14Listing 2-2    Saving a document containing sections2-21Listing 2-3    Opening a document containing sections2-23Listing 2-4    Creating a publisher2-33Listing 2-5    Writing data to an edition2-36Listing 2-6    Creating a subscriber2-40Listing 2-7    Reading in edition data2-42Listing 2-8    Responding to action codes2-46Listing 2-9    Using your own edition opener function2-67Chapter 3    Introduction to Apple Events3-1Figure 3-1    An Open Documents event3-4Figure 3-2    A Get Data event3-7Figure 3-3    Major attributes and direct parameter of an Open Documents event3-10Figure 3-4    Major attributes and direct parameter of a Get Data event3-11Figure 3-5    A descriptor record whose data handle refers to an unterminated string3-13Figure 3-6    A descriptor record whose data handle refers to event class data3-14Figure 3-7    A keyword-specified descriptor record for the event class attribute of an Open Documents event3-16Figure 3-8    A descriptor list for a list of aliases3-17Figure 3-9    Data structures within an Open Documents event3-19Figure 3-10    Accepting and processing an Open Documents event3-21Figure 3-11    The Apple Event Manager calling the handler for an Open Documents event3-22Figure 3-12    Responding to an Open Documents event3-27Figure 3-13    Data structures within a simple object specifier record3-37Figure 3-14    An object specifier record in a Get Data event3-38Figure 3-15    Superclasses and subclasses3-40Figure 3-16    The object class inheritance hierarchy for the object class cWindow3-44Figure 3-17    An Apple event object of class cWord contained in an Apple event object of class cParagraph3-46Chapter 4    Responding to Apple Events4-1Figure 4-1    A document with a button that triggers a Get Data event4-51Figure 4-2    A server application displaying a dialog box that requests information from the user4-52Figure 4-3    Handling user interaction4-53Figure 4-4    Handling user interaction with the kAEWaitReply flag set4-54Figure 4-5    Handling user interaction with the kAEQueueReply flag set4-55Table 4-1    Coercion handling provided by the Apple Event Manager4-43Table 4-2    Descriptor types used by the Apple Event Manager (excluding those used with object specifier records)4-57Listing 4-1    A DoEvent procedure4-5Listing 4-2    A DoHighLevelEvent procedure for handling Apple events and other high-level events4-6Listing 4-3    Adding entries for the required Apple events to an application’s Apple event dispatch table4-8Listing 4-4    Adding entries for Apple events sent by the Edition Manager to an application’s Apple event dispatch table4-9Listing 4-5    A handler for the Open Application event4-15Listing 4-6    A handler for the Open Documents event4-15Listing 4-7    A handler for the Print Documents event4-18Listing 4-8    A handler for the Quit Application event4-19Listing 4-9    A handler for the Create Publisher event4-23Listing 4-10    Extracting items from a descriptor list4-33Listing 4-11    A function that checks for a keyMissedKeywordAttr attribute4-35Listing 4-12    Adding the keyErrorString parameter to the reply Apple event4-38Listing 4-13    Adding parameters to the reply Apple event4-39Listing 4-14    Using the AEInteractWithUser function4-50Chapter 5    Creating and Sending Apple Events5-1Listing 5-1    Creating the optional keyword for the Create Publisher event5-9Listing 5-2    Creating a target address5-11Listing 5-3    Specifying a target address in an Apple event by using the PPCBrowser function5-12Listing 5-4    Sending an Apple event5-17Listing 5-5    An idle function5-23Chapter 6    Resolving and Creating Object Specifier Records6-1Figure 6-1    Resolving an object specifier record for a table in a document6-6Figure 6-2    Nested object specifier records that specify a container hierarchy6-10Figure 6-3    The container hierarchy for the first row in a table that meets a test6-18Figure 6-4    A logical descriptor record that specifies a test6-19Figure 6-5    Descriptor record for an application-defined token that identifies a document6-39Figure 6-6    Descriptor record for an application-defined token that identifies the pbounds property of a window6-40Figure 6-7    A container hierarchy created by the Apple Event Manager using a whose descriptor record6-43Table 6-1    Standard descriptor types used with keyAEKeyData6-12Table 6-2    Keyword-specified descriptor records for typeCompDescriptor6-16Table 6-3    Keyword-specified descriptor records for typeLogicalDescriptor6-17Table 6-4    Keyword-specified descriptor records in a descriptor record of type typeRangeDescriptor6-20Table 6-5    Keyword-specified descriptor records for typeWhoseDescriptor6-42Table 6-6    Keyword-specified descriptor records for typeWhoseRange6-44Table 6-7    Nested object specifier records that describe a container hierarchy6-56Table 6-8    Object specifier record for the first row that meets a test in the table named “MyAddresses”6-65Table 6-9    Logical descriptor record that specifies a test6-66Table 6-10    A range descriptor record6-73Table 6-11    Keyword-specified descriptor records for typeObjectSpecifier6-76Listing 6-1    Installing object accessor functions that find elements of different classes for container tokens of the same type6-23Listing 6-2    Installing one object accessor function that finds elements of different classes for container tokens of one type6-25Listing 6-3    Installing object accessor functions that find elements of the same class for container tokens of different types6-25Listing 6-4    Installing object accessor functions that locate elements of different classes in the default container6-26Listing 6-5    An object accessor function that locates Apple event objects of object class cDocument6-30Listing 6-6    An object accessor function that locates Apple event objects of object class cParagraph6-32Listing 6-7    An object accessor function that locates Apple event objects of object class cWord6-34Listing 6-8    An object accessor function that locates Apple event objects of object class cWindow6-35Listing 6-9    An object accessor function that identifies any property of a window6-38Listing 6-10    An object-counting function6-49Listing 6-11    Object-comparison function that compares two Apple event objects6-52Listing 6-12    Creating an object specifier record using CreateObjSpecifier6-58Listing 6-13    Using CreateObjSpecifier in an application-defined function6-59Listing 6-14    Specifying a document container6-61Listing 6-15    Specifying a table container6-62Listing 6-16    Creating an object specifier record with the key form formName6-67Listing 6-17    Creating a comparison descriptor record6-68Listing 6-18    Creating a logical descriptor record6-70Listing 6-19    Creating a complex object specifier record6-70Listing 6-20    Creating a range descriptor record6-74Chapter 7    Introduction to Scripting7-1Figure 7-1    A script window in the Script Editor application7-6Figure 7-2    Script file icons in the Finder and corresponding user actions7-7Figure 7-3    How the AppleScript component executes a script7-9Figure 7-4    How an application uses the AppleScript component to execute a script7-13Figure 7-5    Role of the 'aete' and 'aeut' resources when the AppleScript component compiles and executes a script7-18Figure 7-6    Role of the 'aete' and 'aeut' resources when the AppleScript component records and decompiles a script7-19Figure 7-7    Using a handler in a script context to handle an Apple event7-26Chapter 8    Apple Event Terminology Resources8-1Figure 8-1    Structure of an 'aeut' or 'aete' resource8-26Figure 8-2    Structure of the header data in an 'aeut' or 'aete' resource8-27Figure 8-3    Structure of suite data in an 'aeut' or 'aete' resource8-28Figure 8-4    Structure of event data in an 'aeut' or 'aete' resource8-30Figure 8-5    Structure of additional parameter data in an 'aeut' or 'aete' resource8-34Figure 8-6    Structure of object class data in an 'aeut' or 'aete' resource8-36Figure 8-7    Structure of property data in an 'aeut' or 'aete' resource8-38Figure 8-8    Structure of element class data in an 'aeut' or 'aete' resource8-41Figure 8-9    Structure of comparison operator data in an 'aeut' or 'aete' resource8-42Figure 8-10    Structure of enumeration data in an 'aeut' or 'aete' resource8-43Figure 8-11    Structure of enumerator data in an 'aeut' or 'aete' resource8-44Table 8-1    Syntax for AppleScript arguments that correspond to direct parameters8-5Table 8-2    Syntax for AppleScript arguments that correspond to insertion location descriptor records8-6Table 8-3    Structure of the 'aeut' and 'aete' resources8-8Listing 8-1    Resource type declaration for the 'aeut' resource8-9Listing 8-2    Rez input for an 'aete' resource for an application that supports the Required and Core suites in their entirety8-15Listing 8-3    Rez input for an 'aete' resource that extends the definitions of the Required, Core, and Text suites8-17Listing 8-4    A handler for the Get AETE event8-25Listing 8-5    Resource type declaration for the 'scsz' resource8-45Chapter 9    Recording Apple Events9-1Listing 9-1    A function used by a factored application to send itself a Quit Application event9-7Listing 9-2    A routine used by a factored application to handle a Quit Application event9-8Listing 9-3    A routine used by a factored application to send itself a Create Element event9-10Listing 9-4    The Create Element event handler for a factored application9-11Listing 9-5    A routine used by a factored application to handle window movement9-13Chapter 10    Scripting Components10-1Figure 10-1    A generic storage descriptor record10-12Figure 10-2    A component-specific storage descriptor record10-13Listing 10-1    Locating a scripting component that supports specific optional routines10-6Listing 10-2    A routine that compiles and executes source data10-9Listing 10-3    A procedure that uses OSAScriptError to get information about an execution error10-11Listing 10-4    A routine that loads and executes script data previously saved using a generic storage descriptor record10-16Listing 10-5    A routine that displays a compiled script for editing and recompiles it10-18Listing 10-6    A function that loads and modifies script data, then saves it using a generic storage descriptor record10-19Listing 10-7    A general Apple event handler that uses the OSADoEvent function10-21Chapter 11    Program-to-Program Communications Toolbox11-1Figure 11-1    A PPC Toolbox session between two applications11-5Figure 11-2    The icon for the Sharing Setup control panel11-6Figure 11-3    The Sharing Setup control panel11-6Figure 11-4    The session termination alert box11-7Figure 11-5    The users and groups dialog box11-8Figure 11-6    The user termination alert box11-8Figure 11-7    The guest dialog box11-9Figure 11-8    The PPC Toolbox authentication process11-10Figure 11-9    Database and spreadsheet applications using the PPC Toolbox11-13Figure 11-10    Two Macintosh applications and their corresponding ports11-18Figure 11-11    The PPC Toolbox and a dictionary service application11-20Figure 11-12    The program linking dialog box11-22Figure 11-13    The program linking dialog box without a zone list11-23Figure 11-14    The user identity dialog box11-30Figure 11-15    The incorrect password dialog box11-31Figure 11-16    The invalid user name dialog box11-31Figure 11-17    Transmitting message blocks11-40Figure 11-18    The PPC Toolbox parameter blocks11-47Listing 11-1    Initializing the PPC Toolbox using the PPCInit function11-12Listing 11-2    Opening a PPC port11-21Listing 11-3    Using a port filter function11-24Listing 11-4    Browsing through dictionary service ports11-26Listing 11-5    Using the IPCListPorts function to obtain a list of ports11-28Listing 11-6    Using the StartSecureSession function to establish a session11-32Listing 11-7    Initiating a session using the PPCStart function11-34Listing 11-8    Using the PPCInform function to enable a port to receive sessions11-36Listing 11-9    Completion routine for a PPCInform function11-37Listing 11-10    Accepting a session request using the PPCAccept function11-38Listing 11-11    Completion routine for a PPCAccept function11-38Listing 11-12    Rejecting a session request using the PPCReject function11-39Listing 11-13    Completion routine for a PPCReject function11-39Listing 11-14    Using the PPCRead function to read data during a session11-41Listing 11-15    Polling the ioResult field to determine if a PPCRead function has completed11-41Listing 11-16    Using the PPCWrite function to write data during a session11-42Listing 11-17    Polling the ioResult field to determine if a PPCWrite function has completed11-43Listing 11-18    Ending a PPC session using the PPCEnd function11-43Listing 11-19    Closing a PPC port using the PPCClose function11-44Listing 11-20    Using the DeleteUserIdentity function to invalidate a user identity11-45Chapter 12    Data Access Manager12-1Figure 12-1    A connection with a database12-6Figure 12-2    Using high-level Data Access Manager routines12-8Figure 12-3    Using low-level Data Access Manager routines12-10Figure 12-4    A flowchart of a session using the high-level interface12-15Figure 12-5    A flowchart of a session using the low-level interface12-29Figure 12-6    A query document dialog box12-47Figure 12-7    The relationship between resources in a query document and the query record12-49Figure 12-8    The relationship between a query definition function and queries12-50Figure 12-9    Structure of a compiled query ('qrsc') resource12-90Figure 12-10    Structure of a compiled query string ('wstr') resource12-91Table 12-1    Data types defined by the Data Access Manager12-38Listing 12-1    Using the high-level interface12-18Listing 12-2    Two completion routines12-21Listing 12-3    A sample status routine12-26Listing 12-4    Sending a query fragment12-31Listing 12-5    Using the low-level interface12-33Listing 12-6    A result handler12-45Listing 12-7    A query definition function12-52About This BookThis book, Inside Macintosh: Interapplication Communication, describes the interapplication communication architecture, which provides a standard and extensible mechanism for communication among Macintosh applications. This book also describes the system software routines that you can use to implement various forms of interapplication communication in your application.If you are new to programming on the Macintosh computer, you should read Inside Macintosh: Overview for an introduction to general concepts of Macintosh programming; Inside Macintosh: Macintosh Toolbox Essentials for information on how to use menus, windows, and controls in your application; and Macintosh Human Interface Guidelines for a complete discussion of user interface guidelines and principles that every Macintosh application should follow.This book describes how to implement publish and subscribe features in your application, how to communicate with other applications using Apple events, how to respond to scripts, and how to exchange information with other applications using the PPC Toolbox. It also discusses how your application can use the Data Access Manager to access information from a database application or other data source.For an overview of all the features provided by the interapplication communication architecture, see the chapter “Introduction to Interapplication Communication” in this book.To provide support for publish and subscribe features in your application, see the chapter “Edition Manager” in this book. This chapter describes how your application can allow users to share dynamic data among many documents.To communicate with other applications by using Apple events, first see the chapter “Introduction to Apple Events” for a general introduction to Apple events. For information on how to respond to the required Apple events, see the chapter “Responding to Apple Events.” To create and send Apple events, see the chapter “Creating and Sending Apple Events.”You can choose to write your application so that it can recognize descriptions, in Apple events, of objects in the application such as words, paragraphs, shapes, or documents. To do so, see the chapter “Resolving and Creating Object Specifier Records.”In addition to supporting Apple events, you can make your application scriptable—that is, capable of responding to Apple events sent to it by a scripting component. By executing scripts, users of scriptable applications can automate repetitive tasks or conditional tasks that involve multiple applications. For more general information about scripting, see the chapter “Introduction to Scripting.” See the chapter “Apple Event Terminology Resources” for information on the resources your application needs to provide in order to be scriptable.You can also make your application recordable, that is, capable of recording a user’s actions for later playback. For more information, see the chapter “Recording Apple Events.”For information on how your application can execute a script with the aid of a scripting component, see the chapter “Scripting Components.”Although you’ll usually want to use Apple events to communicate with other applications, if you need low-level control of communication between applications you can use the Program-to-Program Communications (PPC) Toolbox. For more information, see the chapter “Program-to-Program Communications Toolbox.”Applications can use the Data Access Manager to access information from a database application or other data source. For example, a user in San Francisco might use a spreadsheet application to request data from a company database in New York. The spreadsheet application can use the Data Access Manager to request the data from the database. The database application in New York sends back the requested data, and the spreadsheet application can then use this data to generate a graph of the information. For information on sending and retrieving information from a data source, see the chapter “Data Access Manager.”For definitions of specific Apple events and Apple event objects, see the Apple Event Registry: Standard Suites, available from APDA.For information on handling files in your application and a description of aliases and alias records, see Inside Macintosh: Files.For information on processes and process serial numbers, see Inside Macintosh: Processes.Format of a Typical ChapterAlmost all chapters in this book follow a standard structure. For example, the chapter “Creating and Sending Apple Events” contains these sections:n    “Creating an Apple Event” and “Sending an Apple Event.” These sections describe how your application can create and send Apple events. They describe the Apple Event Manager routines that you can use to accomplish these tasks, give related user interface information, and provide code samples and additional information.n    “Reference to Creating and Sending Apple Events.” This section provides a complete reference to the Apple Event Manager routines you can use to create and send Apple events. Each routine description also follows a standard format, which presents the routine declaration followed by a description of every parameter of the routine. Some routine descriptions also give additional descriptive information, such as assembly-language information or result codes.n    “Summary of Creating and Sending Apple Events.” This section provides the Pascal and C interfaces for the constants, data structures, routines, and result codes associated with the Apple Event Manager routines for creating and sending Apple events. It also includes relevant assembly-language interface information.Conventions Used in This BookInside Macintosh uses various conventions to present information. Words that require special treatment appear in specific fonts or font styles. Certain information, such as the contents of registers, use special formats so that you can scan them quickly.Special FontsAll code listings, reserved words, and the names of actual data structures, fields, constants, parameters, and routines are shown in Courier (this is Courier).Words that appear in boldface are key terms or concepts and are defined in the Glossary.Types of NotesThere are several types of notes used in this book.NoteA note like this contains information that is interesting but possibly not essential to an understanding of the main text. (An example appears on page 3-26.)uIMPORTANTA note like this contains information that is essential for an understanding of the main text. (An example appears on page 3-33.)ssWARNINGWarnings like this indicate potential problems that you should be aware of as you design your application. Failure to heed these warnings could result in system crashes or loss of data. (An example appears on page page 4-10.)sAssembly-Language InformationSome chapters provide additional assembly-language information. For example, Inside Macintosh provides information about the registers for specific routines like this:Registers on entry        A0    Contents of register A0 on entry    Registers on exit        D0    Contents of register D0 on exit    In addition, Inside Macintosh provides information about the fields of a parameter block in this format:´    inAndOut    Integer    Input/output parameter.    ¨    output1    Ptr    Output parameter.    Æ    input1    Ptr    Input parameter.    The arrow in the far left column indicates whether the field is an input parameter, output parameter, or both. You must supply values for all input parameters and input/output parameters. The routine returns values in output parameters and input/output parameters.The second column shows the field name as defined in the MPW Pascal interface files; the third column indicates the Pascal data type of that field. The fourth column provides a brief description of the use of the field. For a complete description of each field, see the discussion that follows the parameter block or the description of the parameter block in the reference section of the chapter.The Development EnvironmentThe system software routines described in this book are available using Pascal, C, or assembly-language interfaces. How you access these routines depends on the development environment you are using. When showing system software routines, this book uses the Pascal interface available with the Macintosh Programmer’s Workshop (MPW).All code listings in this book are shown in Pascal (except for listings that describe resources, which are shown in Rez-input format). They show methods of using various routines and illustrate techniques for accomplishing particular tasks. All code listings have been compiled and, in many cases, tested. However, Apple Computer, Inc., does not intend for you to use these code samples in your application. You can find the location of code listings in the list of figures, tables, and listings. If you know the name of a particular routine (such as MyHandleODoc or MyHandleQuit) shown in a code listing, you can find the page on which the routine occurs by looking under the entry “sample routines” in the index of this book.In order to make the code listings in this book more readable, they show only limited error handling. You need to develop your own techniques for handling errors. This book occasionally illustrates concepts by reference to sample applications called SurfWriter, SurfDB, and SurfCharter; these are not actual products of Apple Computer, Inc.APDA is Apple’s worldwide source for over three hundred development tools, technical resources, training products, and information for anyone interested in developing applications on Apple platforms. Customers receive the quarterly APDA Tools Catalog featuring all current versions of Apple development tools and the most popular third-party development tools. Ordering is easy; there are no membership fees, and application forms are not required for most of our products. APDA offers convenient payment and shipping options, including site licensing.To order products or to request a complimentary copy of the APDA Tools Catalog, contactAPDA Apple Computer, Inc. P.O. Box 319Buffalo, NY 14207-0319Telephone    [phone] (United States)800-637-0029 (Canada)716-871-6555 (International)    Fax    [phone]     AppleLink    APDA    America Online    APDA    CompuServe    76666,2405    Internet    [e-mail]            If you provide commercial products and services, call 408-974-4897 for information on the developer support programs available from Apple.For information on registering signatures, file types, and other technical information, contactMacintosh Developer Technical SupportApple Computer, Inc.20525 Mariani Avenue, M/S 75-3TCupertino, CA 95014-6299The Apple Event Registrar maintains the Apple Event Registry: Standard Suites and other information about the ongoing development of Apple event suites. For more information about Apple event suites, including those under development, send electronic mail to the AppleLink address REGISTRY.Listing 1-0Table 1-0Introduction to Interapplication CommunicationContentsOverview of Interapplication Communication1-3Sharing Data Among Applications1-6Sending and Responding to Apple Events1-9Standard Apple Events1-10Handling Apple Events1-12Supporting AppleScript and Other Scripting Languages1-13Scriptable Applications1-16Recordable Applications1-18Applications That Manipulate and Execute Scripts1-19Exchanging Message Blocks1-22Introduction to Interapplication CommunicationThis chapter describes the interapplication communication (IAC) architecture for Macintosh computers, summarizes how your application can take advantage of it, and tells you where in this book to find the information you need to perform specific tasks.The Apple Event Manager, Event Manager, and Program-to-Program Communications (PPC) Toolbox underlie all the IAC tasks your application can perform. This chapter introduces the Apple Event Manager and the Program-to-Program Communications Toolbox. For information about the Event Manager, see Inside Macintosh: Macintosh Toolbox Essentials. For definitions of the standard Apple events available for use by all applications, see the Apple Event Registry: Standard Suites.The IAC architecture includes the Open Scripting Architecture (OSA). The OSA provides a mechanism that allows users to control multiple applications by means of scripts, or sets of instructions, written in a variety of scripting languages. Each scripting language has a corresponding scripting component that is managed by the Component Manager. When a user executes a script, the scripting component sends Apple events to one or more applications to perform the actions the script describes.This chapter introduces the OSA and describes how to make your application scriptable, or capable of responding to Apple events sent to it by a scripting component. For more information about using the Component Manager, see Inside Macintosh: More Macintosh Toolbox.Overview of Interapplication CommunicationThe interapplication communication (IAC) architecture provides a standard and extensible mechanism for communication among Macintosh applications. The IAC architecture makes it possible for your application ton    provide automated copy and paste operations between your application and other applicationsn    be manipulated by means of scriptsn    send and respond to Apple eventsn    send and respond to high-level events other than Apple eventsn    read and write blocks of data between applicationsThe chapter “Event Manager” in Inside Macintosh: Macintosh Toolbox Essentials describes how your application can use Event Manager routines to send and respond to high-level events. High-level events need not adhere to any specific protocol, so their interpretation is defined by each application that sends or receives them.The most important requirement for high-level communication among all applications is a common vocabulary of events. To provide such a standard, Apple Computer, Inc., has defined a protocol called the Apple Event Interprocess Messaging Protocol (AEIMP). High-level events that conform to this protocol are called Apple events. The vocabulary of publicly available Apple events is published in the Apple Event Registry: Standard Suites, which defines the standard Apple events that developers and Apple have worked out for use by all applications. To ensure that your application can communicate at a high level with other applications that support Apple events now and in the future, you should support the standard Apple events that are appropriate for your application. Effective IAC requires close cooperation among applications at several levels. In addition to the format for high-level events and the standard vocabulary of Apple events, Apple has defined several other standards your application can use to communicate with other applications. These include standard methods for dealing with shared dynamic data, scripts, and low-level message blocks. The IAC architecture comprises the following parts: n    The Edition Manager allows applications to automate copy and paste operations between applications, so that data can be shared dynamically.n    The Open Scripting Architecture (OSA) provides a standard mechanism, based on the Apple Event Manager, that allows users to control multiple applications by means of scripts written in a variety of scripting languages.n    The Apple Event Manager allows applications to send and respond to Apple events.n    The Event Manager allows applications to send and respond to high-level events other than Apple events.n    The Program-to-Program Communications (PPC) Toolbox allows applications to exchange blocks of data with each other by reading and writing low-level message blocks. It also provides a standard user interface that allows a user working in one application to select another application with which to exchange data.Figure 1-1 shows the primary relationships among these parts. The managers and components toward the top of the figure rely on the managers beneath them. The Edition Manager uses the services of the Apple Event Manager to support dynamic data sharing. Scripting components manipulate and execute scripts with the aid of the Apple Event Manager. The Apple Event Manager in turn relies on the Event Manager to send Apple events as high-level events, and the Event Manager uses the services of the PPC Toolbox. Figure 1-1 also shows the five principal means of communication provided by the IAC architecture. In addition to using the Edition Manager and scripting components to send Apple events on their behalf, applications can use the Apple Event Manager directly to send Apple events to other applications. All applications can use the Apple Event Manager to respond appropriately to Apple events, whether they are sent by the Edition Manager, a scripting component, or other applications. Applications can also use the Event Manager directly to send or receive high-level events other than Apple events, and the PPC Toolbox directly to send or receive blocks of data.Figure 1-1    Principal methods of communication between applicationsThe five forms of IAC shown in Figure 1-1 can be summarized as follows:n    Sharing dynamic data. The Edition Manager allows users to copy data from one application’s document to another application’s document, updating information automatically when the data in the original document changes. The verbs publish and subscribe describe this form of dynamic data sharing, and the noun edition describes a copy of the data to be shared. Applications that support dynamic data sharing must implement the Create Publisher and Subscribe To menu commands. The Edition Manager provides the interface that allows applications to share editions.You can let users publish and subscribe on a local volume or across a network. In general, users should be able to publish or subscribe to anything that they can copy or paste. “Sharing Data Among Applications,” which begins on page 1-6, describes how you can use the publish and subscribe features in your application.n    Scripting. The OSA includes the Apple Event Manager, the Apple events defined by the Apple Event Registry: Standard Suites, and the routines supported by scripting components, which applications can use via the Component Manager to execute scripts. Script-editing applications such as Script Editor (not shown in Figure 1-1) allow users to manipulate and execute scripts. Each scripting language has a corresponding scripting component that can execute scripts written in that language. Scripting components typically implement a text-based scripting language based on Apple events. For example, the AppleScript component implements AppleScript, the standard user scripting language defined by Apple Computer, Inc. When the AppleScript component executes a script, it performs the actions described in the script, including sending Apple events to applications when necessary. “Supporting AppleScript and Other Scripting Languages,” which begins on page 1-13, describes how the OSA makes it possible for your application to n    provide human-language equivalents to Apple event codes so that scripting components can send your application the appropriate Apple events during script executionn    allow users to record their actions in the form of a scriptn    manipulate and execute scriptsn    Sending and responding to Apple events. Your application can send Apple events directly to other applications to request services or information or to provide information. To support AppleScript and most other scripting languages based on the OSA, your application must be able to respond to Apple events. “Sending and Responding to Apple Events,” which begins on page 1-9, describes how applications can send and respond to Apple events with the aid of the Apple Event Manager.n    Sending and responding to other high-level events. The Event Manager allows applications to support high-level events other than Apple events. See the chapter “Event Manager” in Inside Macintosh: Macintosh Toolbox Essentials for information about high-level events.n    Exchanging message blocks. The PPC Toolbox allows applications to exchange blocks of data with each other by reading and writing low-level message blocks. This method of communication is most useful for applications that are closely integrated, specifically designed to work together, or dependent on each other for information. It can also be used in code that is not event-based. See “Exchanging Message Blocks” on page 1-22 for a summary of the capabilities provided by the PPC Toolbox.All forms of IAC are based on the premise that applications cooperate with each other. Both the application sending a high-level event or low-level message block and the application receiving it must agree on the protocol for communication. You can ensure effective high-level communication between your application and other Macintosh applications by supporting the standard Apple events defined in the Apple Event Registry: Standard Suites. Sharing Data Among ApplicationsAll Macintosh applications can use the Scrap Manager to share static data by allowing the user to copy and paste data between documents. Dynamic data sharing, or automated copy and paste operations between applications, extends this capability to dynamically changing data. The Edition Manager lets applications share dynamic data at the user’s request. You incorporate publish and subscribe capabilities in your application much as you incorporate copy and paste capabilities.A user can publish data by selecting a portion of text, graphics, or other data in a document and choosing Create Publisher from the Edit menu. In response, your application saves the selected information in a separate file. This stored information is referred to as an edition. The user can subscribe to an edition by choosing Subscribe To from the Edit menu; when the user selects a file that contains an edition, your application includes the information from the edition in the current document. The information in an edition can be shared by many documents.Figure 1-2 shows the principal relationships among the Edition Manager, the publishing application, the subscribing application, and the file that contains the edition. In addition to the relationships illustrated in the figure, the Edition Manager uses the Apple Event Manager to communicate with applications that are sharing dynamic data.Figure 1-2    Sharing data with the aid of the Edition ManagerA publisher is a portion of a document that is made available to other documents through an edition. A subscriber is a portion of a document that reads the information from an edition. Figure 1-3 shows a document containing a publisher, a file containing an edition, and a document containing a subscriber. The bottom fish in the Fishes of the World document is a publisher. The information from this publisher is made available to other documents through the Illustration edition. The Aquarium poster document contains a subscriber that gets its information from the Illustration edition. Note that when a user selects a publisher or subscriber within a document, your application should display a border surrounding the publisher or subscriber.In general, when a user modifies the contents of a publisher and saves the document, your application should write the new data to the edition. The Edition Manager then uses the Apple Event Manager to inform all open applications with subscribers to the edition that it has been updated. These applications can then automatically update the subscribers in the documents.Figure 1-3    A publisher, an edition, and a subscriberFor example, suppose the user changes the color of the fish in the Fishes of the World document shown in Figure 1-3, then saves the document. This automatically changes the Illustration edition, and the subscribing application can update the Aquarium poster document if that’s what the user wants to do.Figure 1-4 shows how a user might create a poster from information contained in other documents.Figure 1-4    Sharing dynamic data with other applicationsYour application should save the new information in the edition whenever the user edits the publisher and saves the document that contains the publisher—unless the user has indicated that the information should be saved in the edition on request only. When the user saves new information in an edition, the Edition Manager replaces the previous contents.When an edition is updated, the Edition Manager informs your application. Your application should then update any subscribers (unless the user has indicated that updates should be incorporated on request only).For example, suppose a user opens a word-processing document called My Stocks that accesses information from an edition called Stock Report. The Stock Report edition might be updated twice a day by an online database. As the information in the edition changes, the My Stocks document can receive automatic updates with the latest information.You can implement publish and subscribe capabilities in your application by using the routines provided by the Edition Manager and supporting the related Apple events. The chapter “Edition Manager” in this book provides sample code that shows how to add these features to your application. The chapter “Responding to Apple Events” in this book describes how to support the related Apple events. Sending and Responding to Apple EventsAn Apple event is a high-level event that conforms to the Apple Event Interprocess Messaging Protocol. The Apple Event Manager uses the Event Manager to send Apple events between applications on the same computer or between applications on remote computers.   Applications typically use Apple events to request services and information from other applications or to provide services and information in response to such requests. For example, any application can use the Get Data Apple event to request that your application locate and return a particular set of data, such as a table. If your application supports the Get Data event, it should be able to recognize the event and respond by locating the requested data and returning a copy of the data to the application that requested it.  Communication between two applications that support Apple events is initiated by a client application, which sends an Apple event to request a service or information. For example, a client application might request services such as printing specific files, checking the spelling of a list of words, or performing a numeric calculation; or it might request information, such as one customer’s address or a list of names and addresses of all customers living in Ohio. The application providing the service or the requested information is called a server application. The client and server applications can reside on the same local computer or on remote computers connected to a network. Figure 1-5 shows the relationships among a client application, the Apple Event Manager, and a server application. The client application uses Apple Event Manager routines to create and send the Apple event, and the server application uses Apple Event Manager routines to interpret the Apple event and respond appropriately. If the client application so requests, the server application adds information to a reply Apple event that the Apple Event Manager returns to the client application. Figure 1-5    Sending and responding to Apple events with the aid of the Apple Event ManagerIf an Apple event is one of the standard events defined in the Apple Event Registry: Standard Suites, the client application can construct the event and the server application can interpret it according to the standard definition for that event. To ensure that your application can respond to Apple events sent by other applications, you should support the standard Apple events that are appropriate for your application.Standard Apple EventsThe current edition of Apple Event Registry: Standard Suites defines the standard suites of Apple events, which are groups of related events that are usually implemented together. The Apple Event Registrar maintains the Apple Event Registry: Standard Suites and other information about the ongoing development of Apple event suites. The standard suites include the following:  n    The Required suite consists of the four Apple events that the Finder sends to applications. These events are Open Application, Open Documents, Print Documents, and Quit Application. The Finder uses the required events as part of the mechanisms in System 7 and later versions for launching and terminating applications. To support System 7, your application must support the required Apple events as described in the chapter “Responding to Apple Events” in this book.  n    The Core suite consists of the basic Apple events, including Get Data, Set Data, Move, Delete, and Save, that nearly all applications use to communicate. You should support the Apple events in the Core suite that make sense for your application. n    A functional-area suite consists of a group of Apple events that support a related functional area. Functional-area suites include the Text suite and the Database suite. You can decide which functional-area suites to support according to which features your application provides. For example, most word-processing applications should support the Text suite, and most database applications should support the Database suite.You do not need to implement all Apple events at once. You should begin by supporting the required Apple events, then add support for the events sent by the Edition Manager, the core events, and the functional-area events as appropriate for your application. If necessary, you can extend the definitions of the standard Apple events to suit specific capabilities of your application. You can also define your own custom Apple events. However, only those applications that choose to support your custom Apple events explicitly will be able to make use of them. If all applications communicated solely by means of custom Apple events, every application would have to support all other applications’ custom events. Instead of creating custom Apple events, try to use the standard Apple events and extend their definitions as necessary.Apple events describe actions to be performed by the applications that receive them. In addition to a vocabulary of actions, or “verbs,” effective communication between applications requires a method of referring to windows, data (such as words or graphic elements), files, folders, volumes, zones, and other items on which actions can be performed. The Apple Event Manager provides a method for specifying structured names, or “noun phrases,” that applications can use to describe the objects on which Apple events act. The Apple Event Registry: Standard Suites includes definitions for Apple event object classes, which are simply names for objects that can be acted upon by each kind of Apple event. Applications use these definitions and Apple Event Manager routines to create complex descriptions of almost any discrete item in another application or its documents. For example, an application could use Apple Event Manager routines and standard object class definitions to construct a Get Data event that requests “the most recent invoice to John Chapman in the Invoices database on the Archives server in the Accounting zone” and send the event to the appropriate application across the network.An Apple event object is any item supported by an application, such as a word, paragraph, shape, or document, that can be described in an Apple event. In the example just given, the specified invoice, the Invoices database, the Archives server, and the Accounting zone are nested Apple event objects. Nearly any item that a user can differentiate and manipulate on a Macintosh computer can be described as an Apple event object of a specified object class nested within other Apple event objects. When handling an Apple event that includes such a description, an application must locate the specified Apple event object and perform the requested action on it.  Most of the standard Apple events defined in the Apple Event Registry: Standard Suites require your application to recognize specific Apple event object classes. Support for the standard Apple events, including Apple event object classes, allows your application to respond to requests for services or information from any other application or process. Handling Apple EventsFigure 1-6 shows a common Apple event from the Core suite, the Set Data event. The SurfDB application is the client; it sends a Set Data event to the SurfCharter application. This event requests that SurfCharter use some new sales figures generated by SurfDB to update the data for the chart named “Summary of Sales” in the document named “Sales Chart.” The Apple event contains information that identifies an action—setting data—and a description of the Apple event object on which to perform the action—“the chart named Summary of Sales in the document named Sales Report.” The Apple event also includes the new data for the chart.  Figure 1-6    A Set Data eventTo respond appropriately, the SurfCharter application in Figure 1-6 can use the Apple Event Manager to determine what kind of Apple event has been sent and pass the event to the appropriate Apple event handler. An Apple event handler is an application-defined function that extracts pertinent data from an Apple event, performs the requested action, and returns a result. In this case, the Set Data event handler must locate an Apple event object—that is, the specified chart in the specified document—and change the data displayed in the chart as requested. The Apple Event Manager provides routines that a server application can use in its Apple event handlers to take apart an Apple event and examine its contents. The SurfCharter application in Figure 1-6 can interpret the contents of the Set Data Apple event according to the definition of that event in the Apple Event Registry: Standard Suites. The Set Data event handler uses both Apple Event Manager routines and the SurfCharter application’s own routines to locate the chart and make the requested change.The Apple Event Manager also provides routines that a client application can use to construct and send an Apple event. However, the most important requirement for applications that support IAC is the ability to respond to Apple events, because this ability is essential for an application that users can control through scripts. The next section describes how you can use Apple events to support scripting in your application.The chapter “Introduction to Apple Events” in this book provides an overview of Apple events and describes how you can use the Apple Event Manager to implement Apple events in your application. The chapters “Responding to Apple Events,” “Creating and Sending Apple Events,” “Resolving and Creating Object Specifier Records,” and “Recording Apple Events” provide detailed information about the Apple Event Manager.  Supporting AppleScript and Other Scripting LanguagesA script is any collection of data that, when executed by the appropriate program, causes a corresponding action or series of actions. For example, some database, telecommunications, and page-layout applications allow users to automate repetitive or conditional tasks by means of scripts written in proprietary scripting languages. The HyperTalk® scripting language allows users to control the behavior of HyperCard® stacks. Macro programs can automate tasks at the level of mouse clicks and keystrokes.   The Open Scripting Architecture (OSA) provides a standard mechanism that allows users to control multiple applications with scripts written in a variety of scripting languages. Each scripting language has a corresponding scripting component. When a scripting component executes a script, it performs the actions described in the script, including sending Apple events to applications if necessary. The OSA comprises the following parts:n    The Apple Event Manager allows applications to respond to Apple events sent by scripting components (see the previous section, “Sending and Responding to Apple Events”).n    The Apple Event Registry: Standard Suites defines the standard vocabulary of Apple events.n    The standard scripting component data structures, routines, and resources allow applications to interact with any scripting component. n    The AppleScript component implements the AppleScript scripting language.The AppleScript component, which implements the AppleScript scripting language, is the implementation of the OSA provided by Apple Computer, Inc. Users can view a script written in the AppleScript scripting language in several different dialects, or versions of the AppleScript language that resemble specific human languages or programming languages.Figure 1-7 shows the relationships among some of these parts. The client application in Figure 1-7 is Script Editor, an application provided by Apple Computer, Inc., that allows users to record, edit, and execute scripts. The client application could also be any other application that uses the standard scripting component routines to execute scripts. Script Editor uses the Component Manager to open a connection with the scripting component that created the script to be executed. Figure 1-7    How a scripting component executes a scriptLike sound resources, scripts can be stored in applications and documents as well as in distinct script files that can be manipulated from the Finder. Script Editor allows users to execute scripts stored in script files. Users can also execute special script files called script applications simply by opening them from the Finder. During script execution, scripting components perform actions described in the script, using the Apple Event Manager to send Apple events when necessary. The server applications shown in Figure 1-7 use the Apple Event Manager to examine the contents of the Apple events they receive and to respond appropriately. A server application always responds to the same Apple event in the same way, regardless of whether the event is sent by a scripting component or directly by a client application. You can take advantage of the OSA in three ways:n    You can make your application scriptable, or capable of responding to Apple events sent to it by a scripting component. An application is scriptable if itn    Responds to the appropriate standard Apple events. See the previous section, “Sending and Responding to Apple Events.”n    Provides an Apple event terminology extension ('aete') resource that describes which Apple events your application supports and the corresponding human-language terminology for use in scripts. The 'aete' resource allows scripting components to interpret scripts correctly and send the appropriate Apple events to your application during script execution. By executing scripts, users of scriptable applications can perform almost any task that they would otherwise perform by choosing menu commands, typing, and so on. Users can also execute scripts to perform many tasks that might otherwise be difficult to accomplish, especially repetitive or conditional tasks that involve multiple applications.n    You can make your application recordable—that is, capable of sending Apple events to itself in response to user actions such as choosing a menu command or changing the contents of a document. After a user has turned on recording for a particular scripting component, the scripting component receives copies of all subsequent Apple events and records them in the form of a script. n    You can have your application manipulate and execute scripts with the aid of a scripting component. To do so, your application mustn    use the Component Manager to open a connection with the appropriate componentn    use the standard scripting component routines to record, edit, compile, save, load, or execute scripts when necessaryUsers of applications that execute scripts can modify the applications’ behavior by editing the scripts. For example, a user of an invoice program might be able to write a script that checks and if necessary updates customer information in a separate database application each time the user posts an invoice.The sections that follow describe these three kinds of scripting capabilities in more detail. The chapter “Introduction to Scripting” in this book provides an overview of the way scripting components work and how you can implement support for scripting in your application.Scriptable ApplicationsIf your application can respond to standard Apple events sent by other applications, it can also respond to the same Apple events sent by a scripting component. Before executing a script that controls your application, a scripting component must associate the human-language terms used in the script with specific Apple event codes supported by your application. Scriptable applications provide this information in an Apple event terminology extension ('aete') resource.   Because scripting components can obtain information from 'aete' resources about the nature of different applications’ support for Apple events, a single script can describe complex tasks performed cooperatively by several specialized applications. For example, a user can execute an AppleScript script to locate all records in a database with specific characteristics, update a series of charts based on those records, import the charts into a page-layout document, and send the document to a remote computer on the network via electronic mail. When a user executes such a script, the AppleScript component attempts to perform the actions the script describes, including sending Apple events to various applications when necessary. To map human-language terms used in the script to the corresponding Apple events supported by each application, the AppleScript component looks up the terms in the applications’ 'aete' resources. Each human-language term specified by an application’s 'aete' resource has a corresponding Apple event code. After the AppleScript component has identified the Apple event codes for the terms used in a script, it can create and send the Apple events that perform the actions described in the script.To respond appropriately to the Apple events sent to it by the AppleScript component, the database application in this example must be able to locate records with specific characteristics so that it can identify and return the requested data. The other applications involved must support Apple events that perform the other actions described in the script.One line in such a script might be a statement like this:copy Totals to chart "Summary of Sales" of document "Sales Chart"In this statement, the word Totals is a variable that has been set earlier in the same script to the value of the new data generated by a database application. The statement causes the AppleScript component to send a Set Data event updating the chart named “Summary of Sales.” Figure 1-8 shows how the AppleScript component would execute this statement. (Figure 1-6 on page 1-12 shows a database application that sends a similar Set Data event directly.) To interpret the terms in this script statement correctly, the AppleScript component must be able to look them up in the SurfCharter application’s 'aete' resource, which maps those terms to the corresponding codes for Apple events, object classes, and so on used by the Apple Event Manager. The AppleScript component can then create and send the Set Data event to SurfCharter.When it receives the Set Data event, the SurfCharter application uses the Apple Event Manager to determine what kind of Apple event has been sent and to pass the event to SurfCharter’s handler for that event, which in turn locates the chart and changes its data as requested.The chapter “Introduction to Scripting” in this book describes how the 'aete' resource works. The chapter “Apple Event Terminology Resources” describes how to define terminology for use by the AppleScript component and how to create an 'aete' resource.Figure 1-8    A Set Data event sent during script executionRecordable ApplicationsIf you decide to make your application scriptable, you can also make it recordable, allowing users to record their actions in your application in the form of a script. Even users with little or no knowledge of a particular scripting language can record their actions in recordable applications in the form of a script. More knowledgeable users can record scripts and then edit or combine them as desired.  Applications generally have two parts: the code that implements the application’s user interface and the code that actually performs the work of the application when the user manipulates the interface. To make your application fully recordable, you should separate these two parts of your application, using Apple events to connect user actions with the work your application performs. Any significant user action within a recordable application should generate Apple events that a scripting component can record as statements in a script. For example, when a user chooses New from the File menu, a recordable application sends itself a Create Element event, and the application’s handler for that event creates the new document. Implementing Apple events in this manner is called factoring your application. A factored application acts as both the client and the server application for the Apple events it sends to itself. In general, a recordable application should generate Apple events for any user action that could be reversed by the Undo command. A recordable application can usually handle a greater variety of Apple events than it can record, since it must record the same action the same way every time even though Apple events might be able to trigger that action in several different ways.A recordable event is any Apple event that any recordable application sends to itself while recording is turned on for the local computer (with the exception of events that the application indicates it does not want to be recorded). After a user turns on recording from the Script Editor application, the Apple Event Manager sends copies of all recordable events to Script Editor. A scripting component previously selected by the user handles each copied event for Script Editor by translating the event into the scripting component’s scripting language and recording the translation as part of a Script Editor script. When a scripting component executes a recorded script, it sends the corresponding Apple events to the applications in which they were recorded.Figure 1-9 illustrates how Apple event recording works. The user performs a significant action (such as choosing New from the File menu), and the SurfCharter application sends itself an Apple event to perform the task associated with that action. If recording is turned on, the Apple Event Manager automatically sends a copy of each recordable Apple event to the application (for example, Script Editor) that initiated recording. The scripting component handles the copy of each recordable event by translating it and recording it as part of a script. To translate each Apple event correctly, the scripting component must first check what equivalent human-language terminology the SurfCharter application uses for that Apple event. The scripting component then records the equivalent statement in the script.The chapter “Recording Apple Events” in this book describes the Apple Event Manager’s recording mechanism in more detail and explains how to use Apple events to factor your application.Figure 1-9    Recording user actions in a factored applicationApplications That Manipulate and Execute ScriptsLike sound resources, scripts can be stored either as separate files with their own icons in the Finder or within an application or its documents. Your application can store and execute scripts regardless of whether it is scriptable or recordable. If your application is scriptable, however, it can execute scripts that control its own behavior, thus acting as both the client application and the server application for the corresponding Apple events. Your application can establish a connection with any scripting component that is registered with the Component Manager on the same computer. Each scripting component can manipulate and execute scripts written in the corresponding scripting language (or, as in the case of AppleScript, one of the scripting language’s dialects) when your application calls the standard scripting component routines.You can use the standard scripting component routines to n    get a handle to a script so you can save the script in a preferences file, in the data fork of a document, or as a separate script filen    manipulate scripts associated with any part of your application or its documents, including both Apple event objects and other objects defined by the applicationn    let users record and edit scriptsn    compile and execute scriptsFigure 1-10 shows how an application might execute a script that controls its own behavior. The appropriate user action handler executes the script in response to a user action, which can be almost anything: choosing a menu command, clicking a button, tabbing from one table cell to another, and so on. The script might consist of a single statement that describes some default action, such as saving or printing, or a series of statements that describe a series of tasks, such as setting default preferences or styles. Figure 1-10 shows a script that corresponds to a single Apple event, but the script could just as easily correspond to a whole series of Apple events. If your application allows users to modify such a script, they can modify the behavior of your application to suit their needs.Figure 1-10    Controlling an application’s own behavior by executing a scriptYour application can associate a script with any Apple event object or application-defined object and execute the script when that object is manipulated in some way. The script can describe actions to be taken by your application, as in Figure 1-10, or actions to be taken by several applications. For example, a user of a word-processing application might attach a script to a specific word so that the application executes the script whenever that word is double-clicked. Such a script could trigger Apple events that look up and display related information from a separate document, run a QuickTime movie, perform a calculation, play a voice annotation, and so on.Figure 1-11 shows one way that a script can be used to control two or more applications. When a user chooses the Post Invoice command in the accounting application, the user action handler for that menu command executes a default script for posting an invoice. That script might describe actions such as saving the invoice, updating the sales journal, and so on. The scripting component sends Apple events to the accounting application to perform these actions. Figure 1-11    Posting an invoice and updating a database by executing a scriptThe accounting application also allows users to open the default invoice-posting script in Script Editor and modify it so that additional actions are performed when it is executed. For example, as shown in Figure 1-11, the script could instruct the SurfDB application to update a database of customer information in addition to performing the default posting actions. In this case, the scripting component sends Apple events to both the accounting application and SurfDB to carry out all the actions described by the script.There is no limit to the actions such a script can describe. In addition to sending the Apple events shown in Figure 1-11, the invoice-posting script could be used to trigger Apple events that cause other applications to perform a credit check, send the invoice to the customer by electronic mail, forward inventory information to a remote server on the network, and so on.The chapter “Scripting Components” in this book describes how your application can use the standard scripting component routines to manipulate and execute its own scripts and allow users to modify those scripts.   Exchanging Message BlocksYou should be able to meet most of your application’s IAC needs by using the Apple Event Manager or the Event Manager. However, if you need low-level control or services not provided by the Apple Event Manager or the Event Manager, you can use the PPC Toolbox. The PPC Toolbox lets you send large amounts of data to other applications located on the same computer or across a network. The PPC Toolbox can also be used by pieces of code that are not event-driven. The PPC Toolbox is usually called by the Operating System; device drivers, desk accessories, or other code modules can also use it.You cannot use the PPC Toolbox to send data between applications unless both your application and the application you’re communicating with are open at the same time. To initiate communication, one program opens a port and requests a session with another program. The target application must also open a port and accept the request. Once a session is established, the two programs can read and write low-level message blocks. The PPC Toolbox also provides a standard user interface that allows a user working in one application to select another application with which to exchange data, whether the communication is achieved by means of Apple events, other high-level events, or message blocks.The chapter “Program-to-Program Communications Toolbox” in this book describes how programs can exchange low-level message blocks.    Listing 2-0Table 2-0Edition ManagerContentsIntroduction to Publishers, Subscribers, and Editions2-4About the Edition Manager2-12Using the Edition Manager2-12Receiving Apple Events From the Edition Manager2-13Creating the Section Record and Alias Record2-15Saving a Document Containing Sections2-19Opening and Closing a Document Containing Sections2-22Reading and Writing a Section2-24Formats in an Edition2-24Opening an Edition2-26Format Marks2-27Reading and Writing Edition Data2-27Closing an Edition2-28Creating a Publisher2-29Creating the Edition Container2-32Opening an Edition Container to Write Data2-35Creating a Subscriber2-37Opening an Edition Container to Read Data2-41Choosing Which Edition Format to Read2-41Using Publisher and Subscriber Options2-43Publishing a New Edition While Saving or Manually2-47Subscribing to an Edition Automatically or Manually2-48Canceling Sections Within Documents2-48Locating a Publisher Through a Subscriber2-49Renaming a Document Containing Sections2-50Displaying Publisher and Subscriber Borders2-50Text Borders2-54Spreadsheet Borders2-55Object-Oriented Graphics Borders2-56Bitmapped Graphics Borders2-57Duplicating Publishers and Subscribers2-58Modifying a Subscriber2-59Relocating an Edition2-60Customizing Dialog Boxes2-60Subscribing to Non-Edition Files2-62Getting the Current Edition Opener2-63Setting an Edition Opener2-63Calling an Edition Opener2-64Opening and Closing Editions2-68Listing Files That Can Be Subscribed To2-68Reading From and Writing to Files2-68Calling a Format I/O Function2-68Edition Manager Reference2-71Data Structures2-71The Edition Container Record2-71The Section Record2-72Edition Manager Routines2-73Initializing the Edition Manager2-74Creating and Registering a Section2-74Creating and Deleting an Edition Container2-79Setting and Getting a Format Mark2-81Reading in Edition Data2-83Writing out Edition Data2-86Closing an Edition After Reading or Writing2-88Displaying Dialog Boxes2-90Locating a Publisher and Edition From a Subscriber2-98Edition Container Formats2-101Reading and Writing Non-Edition Files2-102Application-Defined Routines2-105Summary of the Edition Manager2-106Pascal Summary2-106Constants2-106Data Types2-108Edition Manager Routines2-111Application-Defined Routines2-113C Summary2-114Constants2-114Data Types2-116Edition Manager Routines2-119Application-Defined Routines2-122Result Codes2-122Edition ManagerThis chapter describes how you can use the Edition Manager to allow your users to share and automatically update data from numerous documents and applications.The Edition Manager is available only in System 7 or later. It can be used by many different applications located on a single disk or throughout a network of Macintosh computers. To test for the existence of the Edition Manager, use the Gestalt function, described in Inside Macintosh: Operating System Utilities. Read the information in this chapter if you want your application’s documents to share and automatically update data, or if you want to share and automatically update data with documents created by other applications that support the Edition Manager.For example, a user might want to capture sales figures and totals from within a spreadsheet and then include this information in a word-processing document that summarizes sales for a given month. The Edition Manager establishes a connection between these two documents. When a user modifies the spreadsheet, the information in the word-processing document can be automatically updated to contain the latest changes. To accomplish this, both the spreadsheet application and the word-processing application must support the features of the Edition Manager.To use this chapter, you should be familiar with sending and receiving high-level events, described in the chapter “Event Manager” in Inside Macintosh: Macintosh Toolbox Essentials. Your application must also support Apple events to receive Apple events from the Edition Manager. See the following chapters in this book for detailed information on Apple events. The Edition Manager provides you with the ability ton    capture data within a document and integrate it into another documentn    modify information in a document and automatically update any document that shares its datan    share information between applications on the same computer or across a network of Macintosh computersBuilding the capabilities of the Edition Manager into your program is similar to building cut-and-paste features into your program. Text, graphics, spreadsheet cells, database reports—any data that you can select, you can make accessible to other applications that support the Edition Manager. The next section provides an overview of the main elements of the Edition Manager. Following sections discuss how to implement these features in your application.This chapter also describes an advanced feature that allows applications to share data directly from a file.Introduction to Publishers, Subscribers, and EditionsA section is a portion of a document that shares its contents with other documents. The Edition Manager supports two types of sections: publishers and subscribers. A publisher is a section within a document that makes its data available to other documents or applications. A subscriber is a section within a document that obtains its data from other documents or applications.Your application writes a copy of the data in each publisher to a separate file called an edition container. The actual data that is written to the edition container is referred to as the edition. Your application obtains the data for each subscriber by reading data from the edition container. Note that throughout this chapter, the term edition refers to the edition container and the data it contains. You publish data when you want to make it available to other documents and applications. When data is published, it is stored in an edition container. You subscribe to data that a publisher makes available by reading an edition from its container. NoteSection and edition container are programmatic terms. You should not use them in your application or your documentation. Use publishers, subscribers, and editions. You should also refrain from using other terms such as publication or subscription to describe the dynamic sharing of information provided by the Edition Manager. Use the terms publish and subscribe to describe the Edition Manager features.uEach edition has an icon that is visible from the Finder. Figure 2-1 shows the default edition icon.Figure 2-1    The default edition iconThe name that the user specifies for the edition is located next to the edition icon. For information on providing icons for the editions created by your application, see the chapter “Finder Interface” in Inside Macintosh: Macintosh Toolbox Essentials. Figure 2-2 illustrates a document containing a single publisher, its corresponding edition, and a subscriber to the edition in another document.Figure 2-2    A publisher, an edition, and a subscriberNote that the publisher and subscriber borders illustrated in Figure 2-2 may appear slightly different from the borders you see on the screen. Figure 2-6 on page 2-9 shows the publisher and subscriber borders as they appear onscreen.Data always flows in one direction, from publisher to edition to subscriber. Documents that contain publishers and subscribers do not have to be open at the same time to share data. Whenever the user saves a document that contains a publisher, the edition changes to reflect the current data from the publisher. All subscribers update their contents from the edition. Any number of subscribers can subscribe to a single edition.To create a publisher within a document, a user selects an area of the document to share and chooses Create Publisher from the Edit menu (see Figure 2-7 on page 2-10). Figure 2-3 shows the dialog box that your application should display when the user chooses Create Publisher.Figure 2-3    The publisher dialog boxYour application provides a thumbnail sketch of the edition data, which the Edition Manager displays in the preview area of the publisher dialog box. Your preview of the edition in this dialog box should provide a visual cue about the type of information that the user has selected to publish.A preview area also appears in the subscriber dialog box (see Figure 2-4). This preview, too, should provide a visual cue about the type of information the edition contains. For example, it should allow users to distinguish between text information and spreadsheet arrays.The publisher dialog box uses the extended interface of the standard file dialog box that accompanies System 7. The user navigates through the contents of the disk using the mouse or keyboard.A user can modify a publisher within a document just like any other portion of a document. As a default, each time a user saves a document containing a publisher, your application should automatically write the publisher’s data to the edition. You also need to provide the user with the choice of sending new publisher data to an edition manually (that is, only at the user’s specific request). You should provide these options by using the publisher options dialog box described later in “Using Publisher and Subscriber Options” beginning on page 2-43.For example, one user may choose to update an edition automatically each time a document is saved. This update mode is useful for a user who creates a publisher within a spreadsheet application that records stock information. Each time the user updates the stock information and saves the spreadsheet, a new edition automatically becomes available to subscribers.Another user may choose to update an edition only upon request. This update mode might be useful for a user who creates a publisher within a word-processing application for a quarterly sales report. The user incrementally updates the sales report throughout the entire quarter but does not want this information to be available to subscribers until the end of the quarter. Only at the end of each quarter does the user specifically request to update the edition and make it available to any subscribers.To create a subscriber within a document, the user places the insertion point and chooses Subscribe To from the Edit menu. Figure 2-4 shows the dialog box that your application should display when the user chooses Subscribe To. Figure 2-4    The subscriber dialog boxThe subscriber dialog box also uses the extended interface of the standard file dialog box introduced with System 7. Initially, the dialog box should highlight the name of the last edition published or subscribed to. This allows a user to create a publisher and immediately subscribe to its edition.A subscriber receives its data from a single edition. By default, your application should automatically update a document containing a subscriber whenever a new edition is available. You also need to provide the user with the choice of receiving the latest edition manually (that is, only when the user specifically requests it). You can provide these options by using the subscriber options dialog box described later in “Using Publisher and Subscriber Options” beginning on page 2-43.For example, one user may choose to receive new editions automatically as they become available. This update mode is useful for a user who subscribes to information from an edition that consists of daily sales figures. This user automatically acquires each version of the sales information as it becomes available.Another user may choose to receive a new edition only upon request. This update mode is useful for a user who creates a subscriber to an edition that consists of graphics data (such as a company logo). The user may require only periodic versions of the logo and not need frequent updates. In this case, your application should update the subscriber with a new edition only when the user specifically requests it.A user can select, cut, copy, or paste an entire subscriber. Although the contents of the subscriber as a whole can be modified, a user cannot edit portions of a subscriber. For example, a user can underline or italicize the entire subscriber text but cannot delete a sentence or rotate a single graphic object. This restriction protects the user from losing changes to a subscriber when a new edition arrives. Remember that, as a default, new editions should automatically update a subscriber. Any changes that a user made to the subscriber text would have to be reapplied by the user when the new edition arrives. See “Modifying a Subscriber” on page 2-59 for further information.A single document can contain any number or combination of publishers and subscribers. Figure 2-5 shows an example of a document that contains two publishers and one subscriber (and their corresponding editions). Remember that data always flows in one direction, from publisher to edition to subscriber. The “Concert flyer” document contains a publisher that is subscribed to by the “Benefit concert” document. The “Concert flyer” document also subscribes to a portion of the “Pianos & palm trees” document. In addition, the “Concert flyer” document as a whole is subscribed to by the “Sample flyer” document.Figure 2-5    A document and its corresponding editionsYou should distinguish each selected publisher and subscriber within a document with a border. Display a publisher border as three pixels wide with 50 percent gray lines, and display a subscriber border as three pixels wide with 75 percent gray lines. A rectangle of one white pixel should separate the data from the border itself. Borders should be drawn outside the contents of publishers and subscribers so that data is not obscured. See Figure 2-6 for an illustration of the borders as they appear onscreen. See “Displaying Publisher and Subscriber Borders” on page 2-50 for detailed information on how to implement borders for specific applications.Figure 2-6 shows a document containing a publisher and a document containing a subscriber, with borders displayed for each.Borders for publishers and subscribers should behave like the borders of 'PICT' graphics within a word-processing document. Your application should display a border whenever the user clicks within the content area of a publisher or a subscriber. Your application should hide the border whenever the user clicks outside the content area. See “Displaying Publisher and Subscriber Borders” on page 2-50 for detailed information on how to implement borders for specific applications.Figure 2-6    Publisher and subscriber bordersYou also need to support the standard Edition Manager menu commands in the Edit menu. These menu items includen    Create Publisher…n    Subscribe To…n    Publisher/Subscriber Options…n    Show/Hide Borders (optional)n    Stop All Editions (optional)Use a divider to separate the Edition Manager menu commands from the standard Edit menu commands Cut, Copy, and Paste. Figure 2-7 shows the standard Edition Manager menu commands.Figure 2-7    Edition Manager commands in the Edit menuThe Subscriber Options menu command should toggle with the Publisher Options menu command. When a user selects a subscriber and then accesses the menu bar, your application should adjust its menus so that the Subscriber Options menu command appears in the Edit menu. When a user selects a publisher and then accesses the menu bar, your application should adjust its menus so that the Publisher Options menu command appears in the Edit menu. In addition, you may support a Show Borders menu command that toggles with Hide Borders to display or hide all publishers and subscriber borders within documents. You may also support a Stop All Editions menu command to provide a method for temporarily suspending all update activity in a document. When the user chooses this command, you should place a checkmark next to it. You should also stop all publishers from sending data to editions and all subscribers from receiving new editions. When the user chooses this command again, remove the checkmark and update any subscribers that are set up to receive new editions automatically.If you find that you need all of the available space in the Edit menu for your application’s commands, you may create a hierarchical menu for the Edition Manager menu commands. If you choose to implement this structure, you should allow users to access the Edition Manager menu commands through a Publishing menu command in the Edit menu. Because this menu structure is not as accessible to users, you should implement it only if you have no other alternative.Figure 2-8 shows the Edition Manager menu commands in a hierarchical menu structure.Figure 2-8    Edition Manager commands under the Publishing menu commandFor each publisher or subscriber within an open document, you must have a section record and an alias record. The section record contains a time stamp that records the version of the data that resides in the section. The section record also identifies the section as either a publisher or subscriber, and it establishes a unique identity for each publisher or subscriber. The section record does not contain the data within the section. The alias record is a reference to the edition container from the document that contains the corresponding publisher or subscriber section.There are special options associated with publishers and subscribers within documents. Your application can use the publisher and subscriber options dialog boxes provided by the Edition Manager to make these choices available to the user. For example, a user can select Open Publisher within the subscriber options dialog box to access the document containing the publisher. Your application can also allow a user to cancel subscribers or publishers within documents, specify when to update an edition from a publisher, or specify when to update a subscriber with a new edition. These options are described in “Using Publisher and Subscriber Options” beginning on page 2-43.About the Edition ManagerThe next section discusses how to save, open, read, and write a document that shares data. In addition, it describes how ton    make data accessible to other applicationsn    integrate data into numerous documentsn    set update optionsn    implement bordersn    modify shared datan    customize dialog boxesn    subscribe to data in non-edition filesUsing the Edition ManagerThis section describes how your application cann    receive Apple events from the Edition Managern    set up a section record and alias record for open documents containing sectionsn    save a document that contains sectionsn    open a document that contains sectionsn    read and write sectionsn    create a publisher within a document, create its edition container, and write data to itn    create a subscriber within a document and read its data from an editionTo begin, you must determine whether the Edition Manager is available on the system by using the Gestalt function with the gestaltEditionMgrAttr ('edtn') selector. If the response parameter returns 1 in the bit defined by the gestaltEditionMgrPresent constant (bit 0), the Edition Manager is present.If the Edition Manager is present, load it into memory using the InitEditionPack function. This function determines whether the machine has enough space in the system heap for the Edition Manager to operate.err := InitEditionPack;If the InitEditionPack function returns noErr, you have enough space to load the package. If you do not have enough space, the application can either terminate itself or continue with the Edition Manager functionality disabled.Receiving Apple Events From the Edition ManagerApplications that use the Edition Manager must support Apple events. This requires that your application support the required Open Documents event and Apple events sent by the Edition Manager. See the chapter “Introduction to Apple Events” in this book for general information on Apple events.Apple events sent by the Edition Manager arrive as high-level events. The EventRecord data type defines the event record.TYPE EventRecord =    RECORD        what:                Integer;                {kHighLevelEvent}        message:                LongInt;                {'sect'}        when:                LongInt;        where:                Point;                {'read', 'writ', 'cncl', 'scrl'}        modifiers:                Integer;    END;The Edition Manager can send these Apple events with the event class and event ID as shown here:n    Section Read events ('sect' 'read')n    Section Write events ('sect' 'writ')n    Section Cancel events ('sect' 'cncl')n    Section Scroll events ('sect' 'scrl')Each time your application creates a publisher or a subscriber, the Edition Manager registers its section. When an edition is updated, the Edition Manager scans its list to locate registered subscribers. For each registered subscriber that is set up to receive updated editions automatically, your application receives a Section Read event.If the Edition Manager discovers that an edition file is missing while registering a publisher, it creates a new edition file and sends the publisher a Section Write event. When you receive a Section Cancel event, you need to cancel the specified section. Note that the current Edition Manager does not send you Section Cancel events, but you do need to provide a handler for future expansion.If the user selects a subscriber within a document and then selects Open Publisher in the subscriber options dialog box, the publishing application receives the Open Documents event and opens the document containing the publisher. The publishing application also receives a Section Scroll event. Scroll to the location of the publisher, display this section on the user’s screen, and turn on its border.See “Opening and Closing a Document Containing Sections” beginning on page 2-22 for detailed information on registering and unregistering a section and writing data to an edition. See “Using Publisher and Subscriber Options” beginning on page 2-43 for information on publisher and subscriber options.After receiving an Apple event sent by the Edition Manager, use the Apple Event Manager to extract the section handle. In addition, you must also call the IsRegisteredSection function to determine whether the section is registered. It is possible (because of a race condition) to receive an event for a section that you recently disposed of or unregistered. One way to ensure that an event corresponds to a valid section is to call the IsRegisteredSection function after you receive an event.  err := IsRegisteredSection (sectionH);Listing 2-1 illustrates how to use the Apple Event Manager and install an event handler to handle Section Read events. You can write similar code for Section Write events, Section Scroll events, and Section Cancel events.Listing 2-1    Accepting Section Read events and verifying if a section is registered{the following goes in your initialization code}myErr := AEInstallEventHandler(sectionEventMsgClass {'sect'},                                         sectionReadMsgID {'read'},                                         @MyHandleSectionReadEvent, 0,                                         FALSE);{this is the routine the Apple Event Manager calls when a }{ Section Read event arrives}FUNCTION MyHandleSectionReadEvent(theAppleEvent,                                             reply: AppleEvent;                                             refCon: LongInt): OSErr;VAR    myErr:                OSErr;    sectionH:                SectionHandle;BEGIN    {get section handle out of Apple event message buffer}    myErr := MyGetSectionHandleFromEvent(theAppleEvent, sectionH);    IF myErr = noErr THEN    BEGIN        IF IsRegisteredSection(sectionH) = noErr THEN            {if section is registered, read the new data}            MyHandleSectionReadEvent := DoSectionRead(sectionH);    END     ELSE        MyHandleSectionReadEvent := myErr;END; {MyHandleSectionReadEvent}{this routine reads in subscriber data and updates its display}FUNCTION DoSectionRead(subscriber: SectionHandle): OSErr;BEGIN    {your code here}END;        {DoSectionRead}{this is part of your Apple event–handling code}FUNCTION MyGetSectionHandleFromEvent(theAppleEvent: AppleEvent;                                                 VAR sectionH: SectionHandle)                                                 : OSErr;VAR    ignoreType:                    DescType;    ignoreSize:                    Size;BEGIN    {parse section handle out of message buffer}    MyGetSectionHandleFromEvent        := AEGetParamPtr( theAppleEvent,                                                {event to parse}                                keyDirectObject,                        {look for direct }                                                        { object}                                typeSectionH,                         {want a SectionHandle}                                ignoreType,                        {ignore type it could }                                                        { get}                                @sectionH,                         {put SectionHandle }                                                        { here}                                SizeOf(sectionH),                        {size of storage for }                                                        { SectionHandle}                                ignoreSize);                        {ignore storage it }                                                        { used}END; {MyGetSectionHandleFromEvent} In addition to the Section Read, Section Write, Section Cancel, and Section Scroll events, your application can also respond to the Create Publisher event. For more information on this event, as well as additional information on how to handle Apple events, see the chapter “Responding to Apple Events” in this book. Creating the Section Record and Alias RecordYour application is responsible for creating a section record and an alias record for each publisher and subscriber section within an open document.The section record identifies each section as a publisher or subscriber and provides identification for each section. The section record does not contain the data within the section; it describes the attributes of the section. Your application must provide its own method for associating the data within a section with its section record. Your application is also responsible for saving the data in the section.The alias field of the section record contains a handle to its alias record. The alias record is a reference to the edition container from the document that contains the publisher or subscriber section. You should be familiar with the Alias Manager’s conventions for creating alias records and identifying files, folders, and volumes to locate files that have been moved, copied, or restored from backup. For information on the Alias Manager, see Inside Macintosh: Files.When a user saves a document, your application should store all section records and alias records in the document’s resource fork. Corresponding section records and alias records should have the same resource ID.Figure 2-9 shows a document containing a publisher and subscriber, and the corresponding section records and alias records.Figure 2-9    A document with a publisher and subscriber and its resource forkA section record contains information to identify the data contained within a section as a publisher or a subscriber, a time stamp to record the last modification of the section, and unique identification for each section. The SectionRecord data type defines the section record.TYPE SectionRecord =     RECORD        version:                    SignedByte;                    {always 1 in 7.0}        kind:                    SectionType;                    {publisher or subscriber}        mode:                    UpdateMode;                    {automatic or manual}        mdDate:                    TimeStamp;                    {last change in document}        sectionID:                    LongInt;                    {application-specific, }                                                { unique per document}        refCon:                    LongInt;                    {application-specific}        alias:                    AliasHandle;                    {handle to alias record}        {The following fields are private and are set up by the }        { RegisterSection function described later within this }        { chapter. Do not modify the private fields.}        subPart:                    LongInt;                    {private}        nextSection:                    SectionHandle;                    {private, do not use as a }                                                { linked list}        controlBlock:                    Handle;                    {may be used for comparison }                                                { only}        refNum:                    EditionRefNum;                    {private}END;Field descriptionsversion    Indicates the version of the section record, currently $01.kind    Defines the section type as either publisher or subscriber with the stPublisher or stSubscriber constant.mode    Indicates if editions are updated automatically or manually.mdDate    Indicates which version (modification date) of the section’s contents is contained within the publisher or subscriber. The mdDate field is set to 0 when you create a new subscriber section and to the current time when you create a new publisher. Be sure to update this field each time publisher data is modified. The section’s modification date is compared to the edition’s modification date to determine whether the section and the edition contain the same data. The section modification date is displayed in the publisher and subscriber options dialog boxes. See “Closing an Edition” on page 2-28 for detailed information.sectionID    Provides a unique number for each section within a document. A simple way to implement this is to create a counter for each document that is saved to disk with the document. The counter should start at 1. The section ID is currently used as a tie breaker in the GoToPublisherSection function when there are multiple publishers to the same edition in a single document. The section ID should not be 0 or –1. See “Duplicating Publishers and Subscribers” on page 2-58 for information on multiple publishers.refCon    Reference constant available for application-specific use.alias    Contains a handle to the alias record for a particular section within a document.Whenever the user creates a publisher or subscriber, call the NewSection function to create the section record and the alias record.err := NewSection(container, sectionDocument, kind, sectionID,                       initialMode, sectionH);The NewSection function creates a new section record (either publisher or subscriber), indicates whether editions are updated automatically or manually, sets the modification date, and creates an alias record from the document containing the section to the edition container.You can set the sectionDocument parameter to NIL if the current document has never been saved. Use the AssociateSection function to update the alias record of a registered section when the user names or renames a document by choosing Save As from the File menu. If you are creating a subscriber with the initialMode parameter set to receive new editions automatically, your application receives a Section Read event each time a new edition becomes available for this subscriber.If an error is encountered, the NewSection function returns NIL in the sectionH parameter. Otherwise, NewSection returns a handle to the allocated section record in the sectionH parameter.Set the initialMode parameter to the update mode for each subscriber and publisher created. You can specify the update mode using these constants:CONST            sumAutomatic                    = 0;            {subscriber receives new }                                            { editions automatically}            sumManual                    = 1;            {subscriber receives new }                                            { editions manually}            pumOnSave                    = 0;            {publisher sends new }                                            { editions on save}            pumManual                    = 1;            {publisher does not send }                                            { new editions until user }                                             { request}See “Using Publisher and Subscriber Options” beginning on page 2-43 for detailed information on update modes for publishers and subscribers. See Listing 2-4 beginning on page 2-33 for code that uses the NewSection function to create a publisher. See Listing 2-6 on page 2-40 for code that uses NewSection to create a subscriber. Saving a Document Containing SectionsWhen saving a document that contains sections, you should write out each section record as a resource of type 'sect' and write out each alias record as a resource of type 'alis' with the same ID as the section record. See the chapter “Resource Manager” in Inside Macintosh: More Macintosh Toolbox for detailed information on resources. If a user closes a document that contains newly created publishers without attempting to save its contents, you should display an alert box similar to the one shown in Figure 2-10.Figure 2-10    The new publisher alert boxIf you keep the section records and alias records for each publisher and subscriber as resources, you can use the ChangedResource or WriteResource function. If you detach the section records and alias records from each section, you need to clone the handles and use the AddResource function. See the chapter “Resource Manager” in Inside Macintosh: More Macintosh Toolbox for detailed information on the ChangedResource, WriteResource, and AddResource functions.Use the PBExchangeFiles function to ensure that the file ID remains the same each time you save a document that contains sections. Saving a file typically involves creating a new file (with a temporary name), writing data to it, closing it, and then deleting the original file that you are replacing. You rename the temporary file with the original filename, which leads to a new file ID. The PBExchangeFiles function swaps the contents of the two files (even if they are open) by getting both catalog entries and swapping the allocation pointers. If the files are open, the file control block (FCB) is updated so that the reference numbers still access the same contents (under a new name). See Inside Macintosh: Files for detailed information on the PBExchangeFiles function.Listing 2-2 illustrates how to save a file that contains sections. If the contents of a publisher have changed since the last save, the application-defined procedure MySaveDocument writes the publisher’s data to its edition. It then writes out to the saved document the section records and alias records of all publishers and subscribers. MySaveDocument calls another application-defined routine, MyGetSectionAliasPair, to return a handle and resource ID to a section. As described earlier, you should write out the eligible section records and alias records as resources to allow for future compatibility. There are several different techniques for saving or adding resources; this listing illustrates one technique. The section handles are still valid after using the AddResource function because this listing illustrates just saving, not closing, the file.Before you write out sections, you need to see if any publisher sections share the same control block. Publishers that share the same control block share the same edition.If a user creates an identical copy of a file by choosing Save As from the File menu and does not make any changes to this new file, you simply use the AssociateSection function to indicate to the Edition Manager which document a section is located in.Listing 2-2    Saving a document containing sectionsPROCEDURE MySaveDocument(thisDocument: MyDocumentInfoPtr;                                   numberOfSections: Integer);VAR    aSectionH:                        SectionHandle;    copiedSectionH:                        Handle;    copiedAliasH:                        Handle;    resID:                        Integer;    thisone:                        Integer;    myErr:                        OSErr;BEGIN    FOR thisone := 1 TO numberOfSections DO    BEGIN        aSectionH := MyGetSectionAliasPair(thisDocument, thisone,                                                       resID);        IF (aSectionH^^.kind = stPublisher) &            (aSectionH^^.mode = pumOnSave) &            (MyCheckForDataChanged(aSectionH)) THEN            DoWriteEdition(aSectionH);    END; {end of for}    {set the curResFile to the resource fork of thisDocument}    UseResFile(thisDocument^.resForkRefNum);    {write all section and alias records to the document}    FOR thisone := 1 TO numberOfSections DO    BEGIN        {given an index, get the next section handle and resID }        { from your internal list of sections for this file}        aSectionH := MyGetSectionAliasPair(thisDocument, thisone,                                                       resID);        {check for duplication of control block values}        MyCheckForDupes(thisDocument, numberOfSections);        {save section record to disk}        copiedSectionH := Handle(aSectionH);        myErr := HandToHand(copiedSectionH);        AddResource(copiedSectionH, rSectionType, resID, '');        {save alias record to disk}        copiedAliasH := Handle(aSectionH^^.alias);        myErr := HandToHand(copiedAliasH);        AddResource(copiedSectionH, rAliasType, resID, '');    END; {end of for}    {write rest of document to disk}END; Opening and Closing a Document Containing SectionsWhen opening a document that contains sections, your application should use the GetResource function to get the section record and the alias record for each publisher and subscriber. Set the alias field of the section record to be the handle to the alias. See the chapter “Resource Manager” in Inside Macintosh: More Macintosh Toolbox for detailed information on the GetResource function.You also need to register each section using the RegisterSection function. The RegisterSection function informs the Edition Manager that a section exists.err := RegisterSection(sectionDocument, sectionH,                              aliasWasUpdated);The RegisterSection function adds the section record to the Edition Manager’s list of registered sections. This function assumes that the alias field of each section record is a handle to the alias record. The alias record is a reference to the edition container from the section’s document. If the RegisterSection function successfully locates the edition container for a particular section, the section is registered through a shared control block. The control block is a private field in the section record.If the RegisterSection function cannot find the edition container for a particular subscriber, RegisterSection returns the containerNotFoundWrn result code. If the RegisterSection function cannot find the edition container for a particular publisher, RegisterSection creates an empty edition container for the publisher in the last place the edition was located. The Edition Manager sends your application a Section Write event for that section. When a user attempts to open a document that contains multiple publishers to the same edition, you should warn the user by displaying an alert box (see “Duplicating Publishers and Subscribers” on page 2-58).When a user opens a document that contains a subscriber (with an update mode set to automatic), receives a new edition, and then closes the document without making any changes to the file, you should update the document and simply allow the user to close it. You do not need to prompt the user to save changes to the file.When closing a document that contains sections, you must unregister each section (using the UnRegisterSection function) and dispose of each corresponding section record and alias record.err := UnRegisterSection(sectionH);The UnRegisterSection function removes the section record from the list of registered sections and unlinks itself from the shared control block.Listing 2-3 illustrates how to open an existing file that contains sections. As described earlier, you should retrieve the section and alias resources, connect the pair through the alias field of the section record, and register the section with the Edition Manager. There are many different techniques for retrieving resources; this listing shows one technique. If an alias was out of date and was updated by the Alias Manager during the resolve, the Edition Manager sets the aliasWasUpdated parameter of the RegisterSection function to TRUE. This means that you should save the document. Additionally, your application must maintain its own list of registered sections for each open document that contains sections. You use this list to write out new editions for updated publishers within a document.Listing 2-3    Opening a document containing sectionsPROCEDURE MyOpenExistingDocument(thisDocument: MyDocumentInfoPtr);VAR    sectionH:                            SectionHandle;    aliasH:                            AliasHandle;    aliasWasUpdated:                            Boolean;    registerErr:                            OSErr;    resID:                            Integer;    theResType:                            ResType;    thisone:                            Integer;    numberOfSections:                            Integer;    aName:                            Str255;BEGIN    UseResFile(thisDocument^.resForkRefNum);    {find out the number of section resources}    numberOfSections := Count1Resources(rSectionType);    FOR thisone := 1 TO numberOfSections DO    BEGIN        sectionH := SectionHandle(Get1IndResource(rSectionType,                                                                thisone));        IF sectionH = NIL THEN                                {something could be wrong with }            MySectionErr;                            { the file, handle appropriately}         {get resource ID of the section & use same ID for alias}        GetResInfo(Handle(sectionH), resID, theResType, aName);        {detaching is not necessary, but it is convenient}        DetachResource(Handle(sectionH));        {get the alias}        aliasH := AliasHandle(Get1Resource(rAliasType, resID));        IF aliasH = NIL THEN                                {something could be wrong with }            MyAliasErr;                            { the file, handle appropriately}         DetachResource(Handle(aliasH));        {connect section and alias together}        sectionH^^.alias := aliasH;        {register the section}        registerErr := RegisterSection(thisDocument^.fileSpec,                                                       sectionH, aliasWasUpdated);        {The RegisterSection function may return an error if }        { a section is not registered. This is not a fatal error. }        { Continue looping to register remaining sections.}        {add this section/alias pair to your internal bookkeeping}        MyAddSectionAliasPair(thisDocument, sectionH, resID);        IF aliasWasUpdated THEN             {If alias has changed, make a note of this. }            { It's important to know this when you save.}            MyAliasHasChanged(sectionH);    END; {end of FOR}END;  Reading and Writing a SectionYour application writes publisher data to an edition. New publisher data replaces the previous contents of the edition, making the previous edition information irretrievable. Your application reads data from an edition for each subscriber within a document.The following sections describe how ton    use different formats to write to or read from an editionn    open an edition to initiate writing or readingn    set a format markn    write to or read from an editionn    close an edition after successfully writing or reading dataFormats in an EditionYou can write data to an edition in several different formats. These formats are the same as scrap format types. Scrap format types are indicated by a four-character tag.Typically, when a user copies data, you identify the scrap format types and then write the data to the scrap. With the Edition Manager, when a user decides to publish data, you identify the format types and then write the data to an edition. You can write multiple formats of the same data.For an edition, you should write your preferred formats first. In general, to write data to an edition, your application should use either 'TEXT' format or 'PICT' format. This allows your application to share data with most other applications. To subscribe to an edition, your application should be able to read both 'TEXT' and 'PICT' files. In addition, your application can write any other private formats that you want to support.Scrap format types are described in the chapter “Scrap Manager” in Inside Macintosh: More Macintosh Toolbox.A few special formats are defined as constants.CONST        kPublisherDocAliasFormat                                    = 'alis';    {alias record from the }                                                        { edition to publisher}        kPreviewFormat                                    = 'prvw';    {'PICT' thumbnail }                                                        { sketch}        kFormatListFormat                                    = 'fmts';    {lists all available }                                                        { formats}The kPublisherDocAliasFormat ('alis') format is written by the Edition Manager. It is an alias record from the edition to the publisher’s document. Appended to the end of the alias is the section ID of the publisher, which the Edition Manager uses to distinguish between multiple publishers to a single edition. You should discourage users from making multiple copies of the same publisher. See “Duplicating Publishers and Subscribers” on page 2-58 for detailed information.In addition to writing a publisher’s data to an edition in the 'TEXT' format or 'PICT' format, your application can also write data to an edition in the kPreviewFormat ('prvw') format. If you provide a 'prvw' format in an edition, the Edition Manager uses it to display a preview of the edition data in the preview area of the subscriber dialog box. The 'prvw' format has the same format as a 'PICT' file. To draw a preview in the 'prvw' format, the Edition Manager calls DrawPicture with a rectangle of 120 by 120 pixels. (See Inside Macintosh: Imaging for more information about DrawPicture.) Your application should provide data in a 'prvw' format so that the data displays well in a rectangle of this size. Your application can also use this preview to display subscriber data within a document (to save space).If your application does not provide a preview in the 'prvw' format for an edition, the Edition Manager attempts to provide a preview by using the edition’s 'PICT' format. To draw a preview in the 'PICT' format, the Edition Manager examines the picture’s bounding rectangle and calls DrawPicture with a rectangle that scales the picture proportionally and centers it in a 120-by-12-pixel area. The kFormatListFormat ('fmts') format is a virtual format that is read but never written. It is a list of all the formats and their lengths. Applications can use this format in place of the EditionHasFormat function (described in “Choosing Which Edition Format to Read” on page 2-41), which provides a procedural interface to determine which formats are available.If your application can read two or more of the available formats, use 'fmts' to determine the priority of these formats for a particular edition. The order of 'fmts' reflects the order in which the formats were written.The FormatsAvailable data type defines a record for the 'fmts' format.TYPE FormatsAvailable = ARRAY[0..0] OF    RECORD        theType:                FormatType;                    {format type for an edition}        theLength:                LongInt;                    {length of edition format }                                            { type}    END;For example, an edition container may have a format type 'TEXT' of length 100, and a format type 'styl' of length 32. A subscriber to this edition can open it and then read the format type 'fmts' to list all available formats. In this example, it returns 16 bytes: 'TEXT' $00000064 'styl' $00000020.Opening an EditionFor a publisher, use the OpenNewEdition function to initiate the writing of data to an edition. (Note that the edition container must already exist before you initiate writing; see “Creating the Edition Container” beginning on page 2-32.)err := OpenNewEdition(publisherSectionH, fdCreator,                             publisherSectionDocument, refNum);The publisherSectionH parameter is the publisher section that you are writing to the edition. The fdCreator parameter is the Finder creator type of the new edition. (The edition container file already has a creator type; you can specify the same creator type or establish a new creator type for the edition.)The publisherSectionDocument parameter specifies the document that contains the publisher. This parameter is used to create an alias from the edition to the publisher’s document. If you pass NIL for publisherSectionDocument, an alias is not made in the edition file. The refNum parameter returns the reference number for the edition.For a subscriber, use the OpenEdition function to initiate the reading of data from an edition.err := OpenEdition(subscriberSectionH, refNum);The subscriberSectionH parameter is a handle to the section record for a given section. The refNum parameter returns the reference number for the edition.The user may rename or move the edition in the Finder. Before writing to or reading data from an edition, the Edition Manager verifies the name of the edition. This process is referred to as synching or synchronization. Synching ensures that the Edition Manager’s existing edition names correspond to the Finder’s existing edition names by updating the control block.Format MarksEach format has its own mark. The mark indicates the next position of a read or write operation. Initially, a mark automatically defaults to 0. After reading or writing data, the format mark is set past the last position written to or read from. The mark is similar to the File Manager’s current read or write position marker for a data fork. Any time that an edition is open (after calling the OpenEdition or the OpenNewEdition function), any of the marks for each format can be queried or set. To set the current mark for a section format to a new location, use the SetEditionFormatMark function.err := SetEditionFormatMark(whichEdition, whichFormat,                                     setMarkTo);To get the current mark for a format in an edition file, use the GetEditionFormatMark function.err := GetEditionFormatMark(whichEdition, whichFormat,                                     currentMark);Reading and Writing Edition DataThe Edition Manager allows you to read or write data a few bytes at a time (as with a data fork of a Macintosh file) instead of in one block (as with the Scrap Manager). You can read sequentially by setting the mark to 0 and repeatedly calling read, or you can jump to a specific offset by setting the mark there. The Edition Manager also adds the capability to stream multiple formats by keeping a separate mark for each format. This allows you to write a few bytes of one format and then write a few bytes of another format, and so forth.Once you have opened the edition container for a particular publisher, you can begin writing data to the edition. Use the WriteEdition function to write publisher data to an edition.err := WriteEdition(whichEdition, whichFormat, buffPtr, buffLen);The WriteEdition function writes the specified format (beginning at the current mark for that format type) from the buffer pointed to by the buffPtr parameter up to buffLen bytes. After you open the edition container for a subscriber and determine which formats to read, use the ReadEdition function to read edition data.err := ReadEdition(whichEdition, whichFormat, buffPtr, buffLen);The ReadEdition function reads the data with the specified format (whichFormat) from the edition into the buffer. The ReadEdition function begins reading at the current mark for that format and continues to read up to buffLen bytes. The actual number of bytes read is returned in the buffLen parameter. Once the buffLen parameter returns a value smaller than the value you have specified, there is no additional data to read, and the ReadEdition function returns a noErr result code. NoteThe Translation Manager (if it is available) attempts implicit translation under certain circumstances. For instance, it does so when your application attempts to read from an edition a format type that is not in the edition. In this case, the Translation Manager attempts to translate the data into the requested format. For more information, see the chapter “Translation Manager” in Inside Macintosh: More Macintosh Toolbox.uClosing an EditionWhen you are done writing to or reading data from an edition, call the CloseEdition function.err := CloseEdition(whichEdition, successful);Each time a user edits a publisher within a document, you must update the modification date in the section record (even if the data is not yet written). When the update mode is set to Manually, the user can compare the modification dates for a publisher and its edition in the publisher options dialog box. One modification date indicates when the publisher last wrote data to the edition, and the other modification date indicates when the publisher section was last edited.If the successful parameter for a publisher is TRUE, the CloseEdition function makes the newly written data available to subscribers and sets the modification date in the mdDate field of the edition to correspond to the modification date of the publisher’s section record. If the two dates differ, the Edition Manager sends a Section Read event to all current subscribers.If the successful parameter for a subscriber is TRUE, the CloseEdition function sets the modification date of the subscriber’s section record to correspond to the modification date of the edition.If you cannot successfully read from or write data to an edition, set the successful parameter to FALSE. For a publisher, data is not written to the edition, but it should still be saved with the document that contains the section. When the document is next saved, data can then be written to the edition. See “Closing an Edition After Reading or Writing” on page 2-88 for additional information on the CloseEdition function.Creating a PublisherYou need to support a Create Publisher menu command in the Edit menu. When a user selects a portion of a document and chooses Create Publisher from this menu, you should display the publisher dialog box on the user’s screen. The Create Publisher menu command should remain dimmed until the user selects a portion of a document.Use the NewPublisherDialog function to display the publisher dialog box on the user’s screen. This function is similar to the CustomPutFile procedure described in the chapter “Standard File Package” in Inside Macintosh: Files.err := NewPublisherDialog(reply);The dialog box contains space for a preview (a thumbnail sketch) of the edition and a space for the user to type the name of the edition in which to write the publisher data. Figure 2-11 illustrates a sample publisher dialog box.Figure 2-11    A sample publisher dialog boxThe NewPublisherDialog function displays the preview (provided by your application), displays a text box with the default name of the edition (provided by your application), and handles all user input until the user clicks Publish or Cancel.You pass a new publisher reply record as a parameter to the NewPublisherDialog function.TYPE NewPublisherReply =     RECORD        canceled:                Boolean;                        {user clicked Cancel}        replacing:                Boolean;                        {user chose existing }                                                { filename for an edition}        usePart:                Boolean;                        {always FALSE in version 7.0}        preview:                Handle;                        {handle to 'prvw', 'PICT', }                                                { 'TEXT', or 'snd ' data}        previewFormat:                                        {type of preview}                        FormatType;                            container:                EditionContainerSpec;                            {initially, default name }                                                { and location of edition; }                                                { on return, edition name & }                                                { location chosen by the }                                                 { user to publish data to}    END;You fill in the usePart, preview, previewFormat, and container fields of the new publisher reply record.Always set the usePart field to FALSE. The preview field should contain either NIL or the data to display in the preview. The previewFormat field should contain 'PICT', 'TEXT', 'snd ', or 'prvw'.Set the container field to be the default name and folder for the edition. The default name should reflect the data contained in the publisher. For example, if a user publishes a bar chart of sales information entitled “sales data,” then the default name for the edition could also be “sales data.” Otherwise, you should use the document name followed by a hyphen (-) and a number to establish uniqueness. For example, your default name could be “January Totals - 3.”If the document has not been saved, the default name should be “untitled edition <n>” where n is a number to establish uniqueness. The default folder should be the same as the edition for the last publisher created in the same document. If this is the first publisher in the document, the default folder should be the same folder that the document is in.The canceled field of the new publisher reply record indicates whether the user clicked Cancel. The replacing field indicates whether the user chose to replace an existing edition file. If replacing returns FALSE, call the CreateEditionContainerFile function to create an edition file.The container field is of data type EditionContainerSpec.TYPE EditionContainerSpec =     RECORD        theFile:                    FSSpec;                {record that identifies the }                                            { file to contain edition data}        theFileScript:                    ScriptCode;                {script code of filename}        thePart:                    LongInt;                {which part of file, }                                            { always kPartsNotUsed}        thePartName:                    Str31;                {not used in version 7.0}        thePartScript:                    ScriptCode;                {not used in version 7.0}    END;The field theFile is a file system specification record, a data structure of type FSSpec. You identify the edition using a volume reference number, directory ID, and filename. When specifying an edition, follow the standard conventions described in Inside Macintosh: Files.After filling in the fields of the new publisher reply record, pass it as a parameter to the NewPublisherDialog function, which displays the publisher dialog box.err := NewPublisherDialog(reply);After displaying the publisher dialog box, use the CreateEditionContainerFile function to create the edition container, and then use the NewSection function to create the section record and the alias record. See the next section, “Creating the Edition Container,” and “Creating the Section Record and Alias Record” on page 2-15 for detailed information.The following code segment illustrates how your application might respond to the user choosing the Create Publisher menu item. In this case, the code sets up the preview for the edition, sets the default name for the edition container, and calls an application-defined function (DoNewPublisher, shown in Listing 2-4 on page 2-33) to display the publisher dialog box on the user’s screen. An application might call the DoNewPublisher function in response to the user’s choosing Create Publisher from the Edit menu or in response to handling the Create Publisher event. The chapter “Responding to Apple Events” in this book gives an example of a handler for the Create Publisher event.VAR    thisDocument:                             MyDocumentInfoPtr;     promptForDialog:                             Boolean;    preview:                             Handle;     previewFormat:                             FormatType;     defaultLocation:                             EditionContainerSpec;    myErr:                            OSErr;BEGIN    {Get a preview to show the user. The MyGetPreviewForSelection }    { function returns a handle to the preview.}    preview := MyGetPreviewForSelection(thisDocument);    previewFormat := 'TEXT';    defaultLocation := MyGetDefaultEditionSpec(thisDocument);    promptForDialog := TRUE;    myErr := DoNewPublisher(thisDocument, promptForDialog, preview,                                     previewFormat, defaultLocation);END;Creating the Edition ContainerUse the CreateEditionContainerFile function to create an edition container to hold the publisher data.err := CreateEditionContainerFile(editionFile, fdCreator,                                             editionFileNameScript);This function creates an edition container. The edition container is empty (that is, it does not contain any formats) at this time.To associate an icon with the edition container, create the appropriate entries for the icon in your application’s bundle. See the chapter “Finder Interface” in Inside Macintosh: Macintosh Toolbox Essentials for additional information. Depending on the contents of the edition, the file type will be 'edtp' (for graphics), 'edtt' (for text), or 'edts' (for sound).After creating the edition container, use the NewSection function to create the section record and alias record for the section.Listing 2-4 illustrates how to create a publisher. The DoNewPublisher function shown in the listing is a function provided by an application. Note that an application might call the DoNewPublisher function in response to the user’s choosing the Create Publisher command or in response to the Create Publisher event. The chapter “Responding to Apple Events” in this book gives an example of a handler for the Create Publisher event.The parameters to the DoNewPublisher function include a pointer to information about the document, a Boolean value that indicates if the function should display the new publisher dialog box, the preview for the edition, the preview format, and an edition container.The function displays the publisher dialog box if requested, letting the user accept or change the name of the edition and the location where the edition should reside. Use the CreateEditionContainerFile function to create the edition with the given name and location. Use the NewSection function to create a new section for the publisher.After the section is created, you must write out the edition data. Be sure to add the newly created section to your list of sections for this document. There are several different techniques for creating publishers and unique IDs; this listing displays one technique.After creating the edition container and creating a new section record, the DoNewPublisher function calls another application-defined routine, DoWriteEdition, to open the edition and write data to it.Listing 2-4    Creating a publisherFUNCTION DoNewPublisher(thisDocument: MyDocumentInfoPtr;                                promptForDialog: Boolean;                                 preview: Handle;                                previewFormat: FormatType;                                editionSpec: EditionContainerSpec)                                : OSErr;VAR    getLastErr, dialogErr:                                OSErr;    createErr, sectionErr:                                OSErr;    resID:                                Integer;    thisSectionH:                                SectionHandle;    reply:                                NewPublisherReply;BEGIN    {set up info for new publisher reply record}    reply.replacing := FALSE;    reply.usePart := FALSE;    reply.preview := preview;    reply.previewFormat := previewFormat;    reply.container := editionSpec;    IF promptForDialog THEN     BEGIN        {user interaction is allowed}        {display dialog box and let user select}        dialogErr := NewPublisherDialog(reply);        {dispose of preview data handle}        DisposeHandle(reply.preview);        IF dialogErr <> noErr THEN MyErrHandler(dialogErr);        IF reply.canceled THEN        BEGIN            {do nothing if user canceled}            DoNewPublisher := userCanceledErr;            EXIT(DoNewPublisher);        END;    END;        {of promptForDialog}    IF NOT reply.replacing THEN    BEGIN                {if user isn't replacing an existing file, create a new one}        createErr :=             CreateEditionContainerFile(reply.container.theFile,                                              kAppSignature,                                              reply.container.theFileScript);        IF createErr <> noErr THEN        BEGIN            DoNewPublisher := errAEPermissionDenied;            EXIT(DoNewPublisher);        END;    END; {of not replacing}    {Advance counter to make a new unique sectionID for this }    { document. It is not required that you equate section IDs }    { with resources.}    thisDocument^.nextSectionID := thisDocument^.nextSectionID + 1;    {create a publisher section}    sectionErr := NewSection(reply.container,                                     thisDocument^.fileSpecPtr,                                      stPublisher,                                     thisDocument^.nextSectionID,                                      pumOnSave, thisSectionH);    IF (sectionErr <> noErr) & (sectionErr <> multiplePublisherWrn)             & (sectionErr <> notThePublisherWrn) THEN        MyErrHandler(sectionErr);    resID := thisDocument^.nextSectionID;    {add this section/alias pair to app's internal bookkeeping}    MyAddSectionAliasPair(thisDocument, thisSectionH, resID);    {write out first edition}    DoWriteEdition(thisSectionH);    {Remember that the section and alias records need to be }    { saved as resources when the user saves the document.}    {set the function result appropriately}    DoNewPublisher := MyGetLastError;END; Opening an Edition Container to Write DataSeveral routines are required to write (publish) data from a publisher to an edition container. (For information on creating an edition container, see the previous section.) Before writing data to an edition, you must use the OpenNewEdition function. This function should be used only for a publisher within a document. Use this function to initiate the writing of data to an edition.err := OpenNewEdition(publisherSectionH, fdCreator,                             publisherSectionDocument, refNum);A user may try to save a document containing a publisher that is unable to write its data to an edition—because another publisher (that shares the same edition) is writing, another subscriber (that shares the same edition) is reading, or a publisher located on another computer is registered to the section. In such a case, you may decide to refrain from writing to the edition so that the user does not have to wait. You should also refrain from displaying an error to the user. The contents of the publisher are saved to disk with the document. The next time that the user saves the document, you can write the publisher data to the edition. You should display an alert box to discourage users from making multiple copies of the same publisher and pasting them in the same or other documents (see “Duplicating Publishers and Subscribers” on page 2-58).If a user clicks Send Edition Now within the publisher options dialog box (to write publisher data to an edition manually), and the publisher is unable to write its data to its edition (for any of the reasons outlined above), you should display an error message.After you are finished writing data to an edition, use the CloseEdition function to close the edition.Listing 2-5 illustrates how to write data to an edition. For an existing edition container, you must open the edition, write each format using the WriteEdition function, and close the edition using the CloseEdition function. This listing shows how to write text only. If the edition is written successfully, subscribers receive Section Read events.Listing 2-5    Writing data to an editionPROCEDURE DoWriteEdition(thePublisher: SectionHandle);VAR    eRefNum:                    EditionRefNum;    openErr:                    OSErr;    writeErr:                    OSErr;    closeErr:                    OSErr;    thisDocument:                    MyDocumentInfoPtr;    textHandle:                    Handle;BEGIN    {find out which document this section belongs to}    thisDocument := MyFindDocument(thePublisher);    {open edition for writing}    openErr := OpenNewEdition(thePublisher, kAppSignature,                                          thisDocument^.fileSpecPtr, eRefNum);    IF openErr <> noErr THEN        MyErrHandler(openErr);    {handle error and exit}    {get the text data to write}    textHandle := MyGetTextInSection(thePublisher, thisDocument);    {write out text data}    HLock(textHandle);    writeErr := WriteEdition(eRefNum, 'TEXT', textHandle^,                                       GetHandleSize(textHandle));    HUnLock(textHandle);    IF writeErr <> noErr THEN    BEGIN        {There were problems writing; simply close the edition. }        { When successful = FALSE, the edition data <> section }        { data. Note: this isn't fatal or bad; it just means }        { that the data wasn't written and no Section Read events }        { will be generated.}        closeErr := CloseEdition(eRefNum, FALSE);    END     ELSE    BEGIN        {The write was successful; now close the edition. }        { When successful = TRUE, the edition data = section data.}        { This edition is now available to any subscribers. }        { Section Read events will be sent to current subscribers.}        closeErr := CloseEdition(eRefNum, TRUE);    END;END; Creating a SubscriberYou need to create a Subscribe To menu command in the Edit menu. When a user chooses Subscribe To from this menu, your application should display the subscriber dialog box on the user’s screen.Use the NewSubscriberDialog function to display the subscriber dialog box on the user’s screen. This function is similar to the CustomGetFile procedure described in the chapter “Standard File Package” in Inside Macintosh: Files.To create a subscriber, you must get information from the user, such as the name of the edition being subscribed to. The dialog box displays a listing of all available editions and allows the user to see a preview (thumbnail sketch) of the edition selected. Figure 2-12 shows a sample subscriber dialog box.Figure 2-12    A sample subscriber dialog boxThe subscriber dialog box allows the user to choose an edition to subscribe to. The NewSubscriberDialog function handles all user interaction until a user clicks Subscribe or Cancel. When a user selects an edition container, the Edition Manager accesses the preview for the edition container (if it is available) and displays it.You pass a new subscriber reply record as a parameter to the NewSubscriberDialog function.TYPE        NewSubscriberReply =        RECORD            canceled:                Boolean;                {user clicked Cancel}            formatsMask:                SignedByte;                {formats required}            container:                EditionContainerSpec;                        {initially, default }                                            { name & location of edition }                                            { to subscribe to; on return, }                                            { edition name & location }                                            { chosen by the user}        END;The canceled field returns a Boolean value of TRUE if the user clicked Cancel. To indicate which edition format types (text, graphics, or sound) your application can read, you set the formatsMask field to one or more of these constants:CONST        kPICTformatMask                        = 1;                    {can subscribe to 'PICT'}         kTEXTformatMask                        = 2;                    {can subscribe to 'TEXT'}        ksndFormatMask                        = 4;                    {can subscribe to 'snd '}To support a combination of formats, add the constants together. For example, a formatsMask of 3 displays both graphics and text edition format types in the subscriber dialog box.The container field is of data type EditionContainerSpec. You must initialize the container field with the default edition volume reference number, directory ID, filename, and part. To do so, use the GetLastEditionContainerUsed function to obtain the name of the last edition displayed in the dialog box.err := GetLastEditionContainerUsed(container);This function returns the last edition container for which a new section was created using the NewSection function. If there is no last edition, or if the edition was deleted, GetLastEditionContainerUsed still returns the correct volume reference number and directory ID to use, but leaves the filename blank and returns the fnfErr result code.The container field is of data type EditionContainerSpec.TYPE EditionContainerSpec =     RECORD        theFile:                        FSSpec;                    {file containing edition }                                                    { data}        theFileScript:                        ScriptCode;                    {script code of filename}        thePart:                        LongInt;                    {which part of file, }                                                    { always kPartsNotUsed}        thePartName:                        Str31;                    {reserved}        thePartScript:                        ScriptCode;                    {reserved}    END;The field theFile is of type FSSpec. See Inside Macintosh: Files for further information on file system specification records.After filling in the fields of the new subscriber reply record, pass it as a parameter to the NewSubscriberDialog function, which displays the subscriber dialog box.err := NewSubscriberDialog(reply);After displaying the subscriber dialog box, call the NewSection function to create the section record and the alias record. See “Creating the Section Record and Alias Record” beginning on page 2-15 for detailed information.If the subscriber is set up to receive new editions automatically (not manually), the Edition Manager sends your application a Section Read event. Whenever your application receives a Section Read event, it should read the contents of the edition into the subscriber.Listing 2-6 illustrates how to create a subscriber. As described earlier, you must set up and display the subscriber dialog box to allow the user to subscribe to any of the available editions. After your application creates a subscriber, your application receives a Section Read event to read in the data being subscribed to. Be sure to add the newly created section to your list of sections for this file. There are many different techniques for creating subscribers and unique IDs; this listing displays one technique.Listing 2-6    Creating a subscriberPROCEDURE DoNewSubscriber(thisDocument: MyDocumentInfoPtr);VAR    getLastErr:                    OSErr;    dialogErr:                    OSErr;    sectionErr:                    OSErr;    resID:                    Integer;    thisSectionH:                    SectionHandle;    reply:                    NewSubscriberReply;BEGIN    {put default edition name into reply record}    getLastErr := GetLastEditionContainerUsed(reply.container);    {can subscribe to pictures or text}    reply.formatsMask := kPICTformatMask + kTEXTformatMask;    {display dialog box & let user select edition to subscribe to}    dialogErr := NewSubscriberDialog(reply);    IF dialogErr <> noErr THEN         MyErrHandler(dialogErr);                                    {handle error and exit}    IF reply.canceled THEN                                                 EXIT(DoNewSubscriber);                                    {do nothing if user canceled}    {Advance counter to make a new unique sectionID for this }    { document. It is not necessary to equate section IDs with }    { resources.}    thisDocument^.nextSectionID := thisDocument^.nextSectionID + 1;    {create a subscriber section}    sectionErr := NewSection(reply.container,                                      thisDocument^.fileSpecPtr,                                     stSubscriber,                                      thisDocument^.nextSectionID,                                      sumAutomatic, thisSectionH);    IF sectionErr <> noErr THEN        MyErrHandler(sectionErr);    {handle error and exit}    resID := thisDocument^.nextSectionID;    {add this section/alias pair to app's internal bookkeeping}    MyAddSectionAliasPair(thisDocument, thisSectionH, resID);    {Remember that you will receive a Section Read event to read }    { in the edition that you just subscribed to because the }    { initial mode is set to sumAutomatic.}    {Remember that the section and alias records need to be saved }     { as resources when the user saves the document.}END; Opening an Edition Container to Read DataBefore reading data from an edition, you must use the OpenEdition function. Your application should only use this function for a subscriber. Use this function to initiate the reading of data from an edition.err := OpenEdition(subscriberSectionH, refNum);As a precaution, you should retain the old data until the user can no longer undo. This allows you to undo changes if the user requests it.Your application can supply a procedure such as DoReadEdition to read in data from the edition to a subscriber. When your application opens a document containing a subscriber that is set up to receive new editions automatically, the Edition Manager sends you a Section Read event if the edition has been updated. The Section Read event supplies the handle to the section that requires updating. Listing 2-7, shown in the next section, provides an example of reading data from an edition.Choosing Which Edition Format to ReadAfter your application opens the edition container for a subscriber, it can look in the edition for formats that it understands. To accomplish this, use the EditionHasFormat function.err := EditionHasFormat(whichEdition, whichFormat, formatSize);The EditionHasFormat function returns the noTypeErr result code if a requested format is not available. If the requested format is available, this function returns the noErr result code, and the formatSize parameter contains the size of the data in the specified format or kFormatLengthUnknown (–1), which signifies that the size is unknown.NoteThe Translation Manager (if it is available) attempts implicit translation under certain circumstances. For instance, it does so when your application attempts to read from an edition a format type that is not in the edition. In this case, the Translation Manager attempts to translate the data into the requested format. For more information, see the chapter “Translation Manager” in Inside Macintosh: More Macintosh Toolbox.uAfter your application opens the edition container and determines which formats it wants to read, call the ReadEdition function to read in the edition data. See “Reading and Writing Edition Data” on page 2-27 for detailed information.After you have completed writing the edition data into the subscriber section, call the CloseEdition function to close the edition. See “Closing an Edition” on page 2-28 for detailed information.Listing 2-7 illustrates how to read data from an edition. As described earlier, you must open the edition, determine which formats to read, use the ReadEdition function to read in data, and then use the CloseEdition function to close the edition. This listing shows how to read only text.Listing 2-7    Reading in edition dataPROCEDURE DoReadEdition(theSubscriber: SectionHandle);VAR    eRefNum:                        EditionRefNum;    openErr:                        OSErr;    readErr:                        OSErr;    closeErr:                        OSErr;    thisDocument:                        MyDocumentInfoPtr;    textHandle:                        Handle;    formatLen:                        Size;BEGIN    {find out which document this section belongs to}    thisDocument := MyFindDocument(theSubscriber);    {open the edition for reading}    openErr := OpenEdition(theSubscriber, eRefNum);    IF openErr <> noErr THEN        MyErrHandler(openErr);                                {handle error and exit}    {look for 'TEXT' format}    IF EditionHasFormat(eRefNum, 'TEXT', formatLen) = noErr THEN    BEGIN        {get the handle of location to read to}        textHandle := MyGetTextInSection(theSubscriber,                                                   thisDocument);        SetHandleSize(textHandle, formatLen);        HLock(textHandle);        readErr := ReadEdition(eRefNum, 'TEXT', textHandle^,                                       formatLen);        MyUpdateSubscriberText(theSubscriber, textHandle, readErr);        HUnLock(textHandle);        IF readErr = noErr THEN        BEGIN                    {The read was successful; now close the edition. When }            { successful = TRUE, the section data = edition data.}            closeErr := CloseEdition(eRefNum, TRUE);            EXIT(DoReadEdition);        END;                                                    END;        {of EditionHasFormat}    {'TEXT' format wasn't found or read error; just close }    { the edition. FALSE tells the Edition Manager that your }    { application did not get the latest edition.}    closeErr := CloseEdition(eRefNum, FALSE);END; Using Publisher and Subscriber OptionsYou can allow users to set several special options associated with publishers and subscribers. To set these preferences, users change settings in two dialog boxes provided by the Edition Manager: publisher options and subscriber options. To make these dialog boxes available to the user, provide a command in the Edit menu that toggles between Publisher Options (when the user has selected a publisher within a document) and Subscriber Options (when a user has selected a subscriber within a document). When a user chooses one of these menu commands, you need to display the appropriate dialog box. Use the SectionOptionsDialog function to display the publisher options or subscriber options dialog box on the user’s screen.err := SectionOptionsDialog(reply);Each dialog box contains information regarding the section and its edition. Figure 2-13 shows the publisher options dialog box with the update mode set to On Save. Figure 2-13    The publisher options dialog box with update mode set to On SaveFigure 2-14 shows the publisher options dialog box with the update mode set to Manually.Figure 2-14    The publisher options dialog box with update mode set to Manually As a shortcut for the user, you should display the publisher options dialog box when the user double-clicks a publisher section in a document. Figure 2-15 shows the subscriber options dialog box with the update mode set to Automatically. Figure 2-15    The subscriber options dialog box with update mode set to Automatically Figure 2-16 shows the subscriber options dialog box with the update mode set to Manually.Figure 2-16    The subscriber options dialog box with update mode set to ManuallyAs a shortcut for the user, you should display the subscriber options dialog box when the user double-clicks a subscriber section in a document.You pass a section options reply record as a parameter to the SectionOptionsDialog function.TYPE SectionOptionsReply =     RECORD        canceled:                Boolean;                        {user clicked Cancel}        changed:                Boolean;                        {changed section record}        sectionH:                SectionHandle;                         {handle to the specified }                                                { section record}        action:                ResType;                        {action codes}    END;Set the sectionH parameter to the handle to the section record for the section the user selected.Upon return of the SectionOptionsDialog function, the canceled and changed fields are set. If the canceled field is set to TRUE, the user clicked Cancel. Otherwise, this field is set to FALSE. If the changed field is set to TRUE, the section record is changed. For example, the user may have changed the update mode.The SectionOptionsDialog function returns in the action parameter the code for one of five user actions. The function dismisses the publisher and subscriber options dialog boxes after the user clicks a button.n    Action code is 'read' for a click of the Get Edition Now button.n    Action code is 'writ' for a click of the Send Edition Now button.n    Action code is 'goto' for a click of the Open Publisher button.n    Action code is 'cncl' for a click of the Cancel Publisher or Cancel Subscriber button.n    Action code is '    ' ($20202020) for a click of the OK button. Listing 2-8 shows an example of how your application can respond to the action codes received from the section options reply record. You can use several different techniques for this purpose; this listing shows one technique.Listing 2-8    Responding to action codesPROCEDURE DoOptionsDialog(theSection: SectionHandle);VAR    reply:                        SectionOptionsReply;    theEditionInfo:                        EditionInfoRecord;    action:                        ResType;    sodErr, geiErr:                        OSErr;    gpiErr, gpsErr:                        OSErr;BEGIN    reply.sectionH := theSection;    {display options dialog box}    sodErr := SectionOptionsDialog(reply);    {determine what the user did and handle appropriately}    IF reply.canceled THEN                                {user selected the Cancel button}        EXIT(DoOptionsDialog);    IF reply.changed THEN        {the section record has changed; make note of this}        MySectionHasChanged(theSection);        {if you customize, you may want to do some }        { post-processing now}    {get the action code}    action := reply.action;    IF (action = 'read') THEN    BEGIN            {user selected Get Edition Now button}        DoReadEdition(theSection);        EXIT(DoOptionsDialog);    END;    IF (action = 'writ') THEN    BEGIN            {user selected Send Edition Now button}        DoWriteEdition(theSection);        EXIT(DoOptionsDialog);    END;    IF (action = 'goto') THEN    BEGIN            {user selected Open Publisher button}        geiErr := GetEditionInfo(theSection, theEditionInfo);        IF geiErr <> noErr THEN             MyErrHandler(geiErr);    {handle error and exit}        gpsErr := GotoPublisherSection(theEditionInfo.container);        IF gpsErr <> noErr THEN            MyErrHandler(gpsErr);    {handle error and exit}        EXIT(DoOptionsDialog);    END;    IF (action = 'cncl') THEN    BEGIN     {User selected Cancel Publisher or Cancel Subscriber }        { button. Call the UnRegisterSection function and dispose }        { of the section record and alias record.}        EXIT(DoOptionsDialog);    END;END;The following sections describe the features of the publisher and subscriber options dialog boxes.Publishing a New Edition While Saving or ManuallyBy default, your application should write publisher data to an edition each time the user saves the document and the contents of the publisher differ from the latest edition. In the publisher options dialog box, the user can choose to write new data to an edition each time the document is saved (by clicking On Save) or only upon the user’s specific request (by clicking Manually).When the update mode is set to manual, a user must click the Send Edition Now button in the publisher options dialog box to write publisher data to an edition. When a user clicks this button, the section options reply record contains the action code 'writ'. In this case, you should write out the new edition. Writing to an edition manually is useful when a user tends to save a document numerous times while revising it.Each time the user saves the document, check the update mode of the publisher section. If the publisher section sends its data to an edition when the document is saved, check whether the publisher data has changed since it was last written to the edition. If so, write the publisher’s data to the new edition.In addition, you may also support a Stop All Editions menu command to provide a method for temporarily suspending all update activity. See “Introduction to Publishers, Subscribers, and Editions” beginning on page 2-4 for additional information.Subscribing to an Edition Automatically or ManuallyBy default, your application should subscribe to an edition each time new edition data becomes available. In the subscriber options dialog box, the user can choose to read new data from an edition as the data is available (by clicking Automatically) or only upon the user’s specific request (by clicking Manually).When the update mode is set to manual, the user must click the Get Edition Now button in the subscriber options dialog box to receive new editions. When a user clicks this button, the section options reply record contains the action code 'read'. In this case, you should read in the new edition. See “Opening an Edition Container to Read Data” beginning on page 2-41 for detailed information.When the update mode is set to automatic, your application receives a Section Read event each time a new edition becomes available. In response, you should read the new edition data beginning with the OpenEdition function.Your application does not receive Section Read events for subscribers that receive new editions manually.You may also support a Stop All Editions menu command to provide a method for temporarily suspending all update activity. See “Introduction to Publishers, Subscribers, and Editions” beginning on page 2-4 for additional information.Canceling Sections Within DocumentsThe option of canceling publishers and subscribers is available to the user through the Cancel Publisher and Cancel Subscriber buttons in the corresponding options dialog boxes. When the user clicks one of these buttons, the action code of the section options reply record is 'cncl'. See “Relocating an Edition” on page 2-60 for additional information on canceling a section.When a user cancels a section (either a publisher or subscriber) and then saves the document, or when a user closes an untitled document (which contains newly created sections) without saving it, you must unregister each corresponding section record and alias record using the UnRegisterSection function. In addition, you should also delete the section record and alias record using the DisposeHandle procedure. See Inside Macintosh: Memory for additional information on the DisposeHandle procedure.When a user cancels a publisher section and then saves the document, or when a user closes an untitled document (which contains newly created publishers) without saving it, you must also delete any corresponding edition containers (in addition to deleting section records and alias records).Do not delete an edition container file, section record, or alias record until the user saves the document; the user may decide to undo changes before saving the document.To locate the appropriate edition container to be deleted (before you use the UnRegisterSection function), use the GetEditionInfo function.err := GetEditionInfo(sectionH, editionInfo);The editionInfo parameter is a record of data type EditionInfoRecord.TYPE EditionInfoRecord =     RECORD        crDate:                TimeStamp;                            {date edition container }                                                    { was created}        mdDate:                TimeStamp;                            {date of last change}        fdCreator:                OSType;                            {file creator}        fdType:                OSType;                            {file type}        container:                EditionContainerSpec;                            {the edition}    END;The GetEditionInfo function returns the edition container as part of the edition information.The crDate field contains the creation date of the edition. The mdDate field contains the modification date of the edition.The fdType and the fdCreator fields are the type and creator of the edition file. The container field includes a volume reference number, directory ID, filename, script, and part number for the edition.To remove the edition container, use the DeleteEditionContainerFile function.err := DeleteEditionContainerFile(editionFile);Locating a Publisher Through a SubscriberThe user can locate a publisher from a subscriber within a document by clicking the Open Publisher button in the subscriber options dialog box. As a shortcut, Apple suggests that you also allow the user to locate a publisher by selecting a subscriber in a document and pressing Option–double-click.When the action code of the SectionOptionsReply record is 'goto', use the GoToPublisherSection function.err := GoToPublisherSection(container);The GoToPublisherSection function locates the correct document by resolving the alias in the edition, and it launches the document’s application if necessary (the Edition Manager sends an Open Documents event). The Edition Manager then sends the publishing application a Section Scroll event. If the document containing the requested publisher is located on the same computer as its subscriber, the document opens and scrolls to the location of the publisher. If the document containing the requested publisher is located on a shared volume (using file sharing), the document opens and scrolls to the location of the publisher only if the user has privileges to open the document from the Finder.You need to provide the GoToPublisherSection function with the edition container. To accomplish this, use the GetEditionInfo function. See the previous section, “Canceling Sections Within Documents,” for information on the GetEditionInfo function.Renaming a Document Containing SectionsIf a user renames a document that contains sections by choosing Save As from the File menu, or if a user pastes a portion of a document that contains a section into another document, use the AssociateSection function.Use the AssociateSection function to update the alias record of a registered section.err := AssociateSection (sectionH, newSectionDocument);The AssociateSection function internally calls the UpdateAlias function. It is also possible to update the alias record using the Alias Manager (see the chapter “Alias Manager” in Inside Macintosh: Files for additional information).Displaying Publisher and Subscriber BordersEach publisher and subscriber within a document should have a border that appears when a user selects the contents of these sections. You should display a publisher border as three pixels wide with 50 percent gray lines and a subscriber border as three pixels wide with 75 percent gray lines. Separate the contents of the section from the border itself with one pixel of white space. To create your borders, you should use patterns, not colors. Depending on the user’s monitor type, colors may not be distinguishable.In general, borders for publishers and subscribers should behave like the borders of 'PICT' graphics in a word-processing document. A border should appear when the user clicks the content area of a publisher or a subscriber and disappear when the user clicks outside the content area of a section. You can also make all publisher and subscriber borders appear or disappear by implementing an optional Show/Hide Borders menu command. Figure 2-17 displays the Edition Manager Show/Hide Borders menu command in the Edit menu.Figure 2-17    Edit menu with Show/Hide Borders menu commandDepending on your application, you may choose to include resize handles or similar components in your borders. See “Object-Oriented Graphics Borders” on page 2-56 for an example of resize handles.Whenever a user selects a portion of a publisher or sets the insertion point within a publisher, you should display the border as 50 percent gray. A user can copy the contents of a publisher or subscriber without copying the section itself by selecting the data, copying, and then pasting the data in a new location. A user can cut and paste a selection that contains an entire publisher or subscriber, but you should discourage users from making multiple copies of a publisher. See “Duplicating Publishers and Subscribers” on page 2-58 for detailed information.When the user modifies a publisher, your application should grow or shrink its border to accommodate the new dimension of the section.You should display only one publisher border within a document at a time. If a cursor is inserted within a publisher that is contained within a larger publisher, you should display only the smaller, internal publisher border. If it is absolutely necessary to display all section borders within a document at the same time, you can create a Show/Hide Borders menu item. You do not need to provide support for publishers contained within other publishers. If you do not, you should dim the Create Publisher menu command (to indicate that it is not selectable) when a user attempts to create a publisher within an existing publisher.Figure 2-18 shows the recommended border behavior for publishers. The top window shows a publisher with its borders displayed. The middle window shows how the borders look when a user selects some of the contents of a section. The bottom window shows how the borders look when a user selects data within a document that includes a publisher section.Figure 2-18    Publisher bordersFigure 2-19 shows the recommended border behavior for subscribers. The top window shows a subscriber with its borders displayed. The middle window shows how the borders look when a user selects the contents of a section. The bottom window shows how the borders look when a user selects data within a document that includes a subscriber section.Figure 2-19    Subscriber bordersIf a user tries to select only a portion of a subscriber, you should highlight the entire contents of the subscriber. A user cannot edit the data in a subscriber. See “Modifying a Subscriber” on page 2-59 for detailed information.If a user cancels a section using the publisher or subscriber options dialog box, your application should leave the contents of the section within the document, but you should be sure to remove the borders from this data, as it is no longer considered a section.Generally, the appearance and function of publisher and subscriber borders should be the same across different applications. The following sections entitled “Text Borders,” “Spreadsheet Borders,” “Object-Oriented Graphics Borders,” and “Bitmapped Graphics Borders” describe specialized features for publisher and subscriber borders in word-processing, spreadsheet, or graphics applications. Text BordersIn word-processing documents, a publisher may contain other publishers. However, one publisher should not overlap another publisher. You should display only one publisher border at a time. If an insertion point is placed within a publisher that is encompassed by another larger publisher, you should display only the smaller internal publisher border.In exceptional cases, it may be necessary to display more than one publisher or subscriber border at a time. For example, a publisher may consist of a paragraph that includes a marker for a footnote. The data contained within the footnote should also be considered part of the publisher. When a user selects the paragraph, you should simultaneously display a border around the footnote.The border of a publisher that contains text should be located between characters within the text. The insertion point, when placed on such a boundary, should gravitate toward the publisher. That is, a click in front (to the left) of a publisher border should place the cursor inside the publisher, so that subsequent typing goes inside the publisher. Clicking at the end (to the right) of a publisher border should also place the cursor inside the publisher.Whenever two separate borders are adjacent, the boundary click should go in between them. This is also true for a border that is next to other nontextual aspects of a document, such as 'PICT' graphics or page breaks.When a user removes information from a publisher that contains text data, you should resize the border so that it becomes smaller. When a user adds information to the publisher, you should enlarge the border to accommodate the new text. The insertion point should remain within the publisher. If a user highlights the entire contents of a publisher and then chooses Cut from the Edit menu, you should not delete the publisher border within the document. The user may intend to delete the existing publisher data and replace it with new data, or the user may want to move the entire publisher and its data to a new location. Figure 2-20 shows this state.Figure 2-20    A publisher with contents removedYou should leave the cursor inside the small publisher border for further typing. If the user inserts the cursor in a new location (instead of typing data inside the existing border), you need to remove the empty publisher border from the document to allow the user to move the publisher. This effectively deletes the publisher from the document. If the user pastes the publisher that is currently held in the scrap, you should re-create its border. If the user cuts or copies other data from the document before pasting the publisher from the scrap, the publisher should be removed from the scrap.Spreadsheet BordersBorders around spreadsheet data or other data in arrays should look and behave very much like text borders. Figure 2-21 shows a typical border within a spreadsheet document.Figure 2-21    A publisher border within a spreadsheet documentNote that the border goes below the column headers (A, B, C, D) and to the right of the row labels (1, 2, 3, 4)—it should not overlap these cell boundaries. The border at the bottom and the border on the right side can be placed within the adjacent cells (outside of the cells that constitute the publisher).Unlike borders in word-processing applications, borders in spreadsheet documents (or other documents with array data) can overlap. That is, a user can select a row of cells to be a publisher and an overlapping column of those cells to be another publisher. You should never display more than one publisher border at a time. When a user selects a spreadsheet cell that is part of more than one publisher, you should display only the border of the publisher that was last edited. (This can be accomplished by comparing the modification dates of the publishers.)If it is absolutely necessary to display all section borders within a document at the same time, you can create a Show/Hide Borders command in the Edit menu to toggle all borders on and off.When data is added to or deleted from a publisher that consists of a spreadsheet cell or other array, you should resize its border to accommodate the addition or deletion of data. A publisher should behave like a named range in a spreadsheet. For example, if a user cuts a row within a publisher that consists of a named range in a spreadsheet, you should shrink the publisher data and its border correspondingly.When a user cuts a publisher and its entire contents within a spreadsheet document, the entire section should be held in the scrap. Do not leave an empty publisher border in a spreadsheet (as recommended for text borders). If a user attempts to paste a copy of an existing publisher, you should warn the user by displaying an alert box (see “Duplicating Publishers and Subscribers” on page 2-58).Object-Oriented Graphics BordersIn an object-oriented drawing application, the publisher border should fit just around the selected objects.You can provide resize handles that appear with all drawing objects to allow the user to resize the border of a publisher. Figure 2-22 shows a publisher border with resize handles.Figure 2-22    A publisher border with resize handlesAn application can make publisher borders appear to float over the area the user publishes. The border acts like a clipping rectangle—anything within the border becomes the publisher. Figure 2-23 shows a publisher that contains clipped graphics and its subscriber in another application.A user can create publishers and subscribers that overlap each other. Thus, borders may overlap and it may no longer be possible to turn on a particular border when the user clicks within a publisher. Drawing applications should provide a menu command, Show Borders, that toggles to Hide Borders. This command should allow users to turn all publisher and subscriber borders on or off.Figure 2-23    A publisher and subscriber with clipped graphicsBitmapped Graphics BordersCreating a border around bitmapped graphics in applications is similar to doing so in object-oriented drawing applications. The border appears around the selected area. The user can create overlapping publishers and subscribers in bitmapped graphics applications. You need to provide a Show/Hide Borders command to allow users to turn all borders on and off.Duplicating Publishers and SubscribersWhenever a user clicks a publisher or subscriber border, you should change the contents of the section to a selected state. You should discourage users from making multiple copies of a publisher and pasting them in the same or other documents, because the contents of the edition would be difficult or impossible to predict. Multiple copies of the same publisher also contain the same control block value. See “Creating and Registering a Section” on page 2-74 for detailed information on control blocks.When a user attempts to create a copy of a publisher that already exists, you should display an alert box such as the one shown in Figure 2-24.Figure 2-24    Creating multiple publishers alert boxWhen a user attempts to save a document that contains multiple copies of the same publisher, display an alert box such as the one shown in Figure 2-25.Figure 2-25    Saving multiple publishers alert boxIf a user decides to ignore your alert box, your application should still save the document, but you should continue to display this error message every time the user saves this document.A user can modify the contents of any duplicate publisher, but the contents of the edition will be whichever publisher was the last to write.When a user chooses to copy and paste or duplicate a section, use the HandToHand function (described in Inside Macintosh: Memory) to duplicate the section record and alias record. Set the alias field of the cloned section record to the handle of the cloned alias record and generate a unique section identification number for it. In addition, you should also place the section data, section record, and alias record in the scrap.Use the RegisterSection function (described in “Opening and Closing a Document Containing Sections” on page 2-22) to register the cloned section’s section record.A user can select the contents of a publisher without selecting the border and copy just the data to a new location. In this case, the user has simply copied data (and not the publisher). Do not create a border for this data in the new location.Modifying a SubscriberWhen the user selects data or clicks the data area of a subscriber, you should highlight the entire contents of the subscriber using inverse video. Although you shouldn’t allow a user to edit the information in a subscriber, you can allow a user to make global adornments to subscribers. In other words, users can change the font, size, or other characteristics of the entire subscriber. For example, a user might select a subscriber within a document and change all text from plain to bold. However, you should discourage users from modifying the individual elements contained within a subscriber—for example, by editing a sentence or rotating an individual graphic object.Remember that each time a new edition arrives for a subscriber, any modifications that the user has introduced are overwritten. Global changes to a subscriber are much easier for your application to regenerate.NoteAlthough adornments should be global and never partial, you may still need to give users the ability to select portions of a subscriber, for instance, when performing spell checking and search-and-replace operations.uIf you do allow a user to edit a subscriber section, provide an enable/disable editing option within the subscriber options dialog box using the SectionOptionsExpDialog function, described in “Customizing Dialog Boxes” beginning on the next page. When you allow a user to edit a subscriber, you should change the subscriber from a selected state to editable data.Because a user can modify a publisher just like any other portion of a document, its subscriber may change in size as well as content. For example, a user may modify a publisher by adding two additional columns to a spreadsheet.Relocating an EditionIn the Finder, users cannot move an edition across volumes. To relocate an edition, the user must first select its publisher and cancel the section (remember to remove the border). The user needs to republish and then select a new volume location for the edition. As a convenience for the user, you should retain the selection of all the publisher data after the user cancels the section to make it easy to republish the section.Customizing Dialog BoxesThe expandable dialog box functions allow you to add items to the bottom of the dialog boxes, apply alternate mapping of events to item hits, apply alternate meanings to the item hits, and choose the location of the dialog boxes. See the chapter “Dialog Manager” in Inside Macintosh: Macintosh Toolbox Essentials and the chapter “Standard File Package” in Inside Macintosh: Files for additional information.The expandable versions of these dialog boxes require five additional parameters. Use the NewPublisherExpDialog function to expand the publisher dialog box.err := NewPublisherExpDialog (reply, where, expansionDITLresID,                                         dlgHook, filterProc, yourDataPtr);Use the NewSubscriberExpDialog function to expand the subscriber dialog box.err := NewSubscriberExpDialog (reply, where, expansionDITLresID,                                         dlgHook, filterProc, yourDataPtr);Use the SectionOptionsExpDialog function to expand the publisher options and the subscriber options dialog boxes.err := SectionOptionsExpDialog (reply, where, expansionDITLresID,                                          dlgHook, filterProc, yourDataPtr);The reply parameter is a pointer to a NewPublisherReply, NewSubscriberReply, or SectionOptionsReply record, respectively.You can automatically center the dialog box by passing (–1, –1) in the where parameter. The expansionDITLresID parameter should contain 0 or a valid item list ('DITL') resource ID. This integer is the resource ID of an item list whose items are appended to the end of the standard item list. The dialog items keep their relative positions, but they are moved as a group to the bottom of the dialog box. See the chapter “Dialog Manager” in Inside Macintosh: Macintosh Toolbox Essentials for additional information on item lists.The filterProc parameter should be a pointer to an expandable modal-dialog filter function or NIL. An expandable modal-dialog filter function is similar to a modal-dialog filter function or event filter function except that an expandable modal-dialog filter function accepts two extra parameters. The ModalDialog procedure calls the expandable modal-dialog filter function you provide in this parameter. Providing a filter function enables you to map real events (such as a mouse-down event) to an item hit (such as clicking the Cancel button). For instance, you may want to map a keyboard equivalent to an item hit. See the chapter “Dialog Manager” in Inside Macintosh: Macintosh Toolbox Essentials for information on the ModalDialog procedure.The dlgHook parameter should be a pointer to an expandable dialog hook function or NIL. An expandable dialog hook function is similar to a dialog hook function except that an expandable dialog hook function accepts an additional parameter. The NewSubscriberExpDialog, NewPublisherExpDialog, and SectionOptionsExpDialog functions call your expandable dialog hook function after each call to the ModalDialog procedure. The dialog hook function should take the appropriate action, such as filling in a checkbox. The itemOffset parameter to the procedure is the number of items in the item list before the expansion dialog items. You need to subtract the item offset from the item hit to get the relative item number in the expansion dialog item list. The expandable dialog hook function should return as its function result the absolute item number. When the Edition Manager displays subsidiary dialog boxes in front of another dialog box on the user’s screen, your dialog hook and event filter functions should check the refCon field in the WindowRecord data type (from the window field in the DialogRecord) to determine which window is currently in the foreground. The main dialog box for the NewPublisherExpDialog and the NewSubscriberExpDialog functions contains the following constant:CONST            sfMainDialogRefCon                            = 'stdf';                {new publisher and }                                                        { new subscriber}The main dialog box for the SectionOptionsExpDialog function contains the following constant:CONST            emOptionsDialogRefCon                                = 'optn';                {options dialog}See “Summary of the Edition Manager” beginning on page 2-106 for additional constants. The yourDataPtr parameter is reserved for your use. It is passed back to your dialog hook and event filter function. This parameter does not have to be of type Ptr—it can be any 32-bit quantity that you want. In Pascal, you can pass yourDataPtr in register A6 , and declare your dialog hook and modal-dialog filter as local functions without the last parameter. The stack frame is set up properly for these functions to access their parent local variables. See the chapter “Standard File Package” in Inside Macintosh: Files for detailed information.For the NewPublisherExpDialog and NewSubscriberExpDialog functions, all the pseudo-items for the Standard File Package—such as sfHookFirstCall(–1), sfHookNullEvent(100), sfHookRebuildList(101), and sfHookLastCall(–2)—can be used, as well as emHookRedrawPreview(150).For the SectionOptionsExpDialog function, the only valid pseudo-items are sfHookFirstCall(–1), sfHookNullEvent(100), sfHookLastCall(–2), emHookRedrawPreview(150), emHookCancelSection(160), emHookGoToPublisher(161), emHookGetEditionNow(162), emHookSendEditionNow(162), emHookManualUpdateMode(163), and emHookAutoUpdateMode(164). See the chapter “Standard File Package” in Inside Macintosh: Files for information on pseudo-items.Subscribing to Non-Edition FilesUsing the Edition Manager, a subscriber can read data directly from another document, such as an entire 'PICT' file, instead of subscribing to an edition. This feature is for advanced applications that can set up bottleneck procedures for reading. Figure 2-26 shows a document that is subscribing directly to a 'PICT' file. Figure 2-26    Subscribing directly to a 'PICT' fileFor each application, the Edition Manager keeps a pointer to a bottleneck function. The Edition Manager never opens or closes an edition container directly. Instead, the Edition Manager calls the current edition opener. The InitEditionPack function (described on page 2-74) sets up the current system opener function.To override the standard opener function, create an opener function that contains the following parameters:FUNCTION MyOpener (selector: EditionOpenerVerb;                          VAR PB: EditionOpenerParamBlock): OSErr;Your opener needs to know which formats the file contains and how the data is supposed to be read or written. The opener function is passed an edition opener verb in the selector parameter, which identifies the action the opener function should perform. The opener can allocate a handle or pointer to contain information such as file reference numbers. This value is passed to the I/O routines in the ioRefNum field of the edition opener parameter block.The eoOpen and eoOpenNew edition opener verbs (described in “Calling an Edition Opener” on page 2-64) return a pointer to a function to do the actual reading and writing.The following sections describen    how to get the current edition opener n    how to set your own edition opener n    how to call an edition opener n    the edition opener parametersGetting the Current Edition OpenerWhen you want to get the current edition opener, use the GetEditionOpenerProc function.err := GetEditionOpenerProc(opener);The opener parameter returns a pointer to the current edition opener. A different current opener is kept for each application. One application’s opener is never called by another application.Setting an Edition OpenerYou can provide your own edition opener. To do so, use the SetEditionOpenerProc function.err := SetEditionOpenerProc(@MyOpener);The @MyOpener parameter is a pointer to the edition opener function that you are providing. If you set the current opener to be a routine in your own code, be sure to call the GetEditionOpenerProc function first so that you can save the previous opener. If your opener is passed a selector that it does not understand, use the previous opener provided by the Edition Manager to handle it. See the next section for a list of selectors.Calling an Edition OpenerYou use the CallEditionOpenerProc function to call an edition opener. Since the Edition Manager is a package that may move, a real pointer cannot be safely returned for the standard opener and I/O routines. The system opener and the I/O routines are returned as a value that is not a valid address to a procedure. The CallEditionOpenerProc and CallFormatIOProc functions check for these values and call the system openers.You should never assume that a value for a system opener is a fixed constant.err := CallEditionOpenerProc (selector, PB, routine);Set the selector parameter to one of the edition opener verbs. The edition opener verbs includen    eoCanSubscriben    eoOpenn    eoClosen    eoOpenNewn    eoCloseNewThe PB parameter of the CallEditionOpenerProc function is an edition opener parameter block.TYPE EditionOpenerParamBlock =     RECORD        info:                    EditionInfoRecord;                            {edition container to }                                                        { be subscribed to}        sectionH:                    SectionHandle;                            {publisher or }                                                        { subscriber }                                                        { requesting open}        document:                    FSSpecPtr;                            {document passed}        fdCreator:                    OSType;                            {Finder creator type}        ioRefNum:                    LongInt;                            {reference number}        ioProc:                    FormatIOProcPtr;                            {routine to read }                                                        { formats}        success:                    Boolean;                            {reading or writing }                                                        { was successful}        formatsMask:                    SignedByte;                            {formats required to }                                                        { subscribe}    END;The routine parameter of the CallEditionOpenerProc function is a pointer to an edition opener function.The following list shows which fields of the edition opener parameter block are used by the edition opener verbs:Opener verb        Field    Description    Called by (continued)    eoCanSubscribe    Æ    info    Edition container to subscribe to.    NewSubscriberDialogfunction for a subscriber        Æ    formatsMask    Formats required to subscribe.            ¨    Return value    A noErr code indicates that an edition container can be subscribed to. A noTypeErr code indicates that an edition container cannot be subscribed to.        eoOpen    Æ    info    Edition container to open for reading.    OpenEdition and GetStandardFormats functions for a subscriber        Æ    sectionH    Subscriber section requesting open or NIL.                                ¨    ioRefNum    Reference number for use by I/O routine. Not the same as EditionRefNum.                                ¨    ioProc    I/O routine to call to read formats.            ¨    Return value    A noErr code or appropriate error code.        eoClose    Æ    info    Edition container to be closed for reading.    CloseEdition and GetStandardFormats functions for a subscriber                            Æ    sectionH    Subscriber section requesting close or NIL.                                Æ    ioRefNum    Value returned by eoOpen.            Æ    ioProc    Value returned by eoOpen.            Æ    success    Success value passed to the CloseEdition function.                                ¨    Return value    A noErr code or appropriate error code.                        continued    eoOpenNew    Æ    info    Edition container to open for writing.    OpenNewEdition function for a publisher        Æ    sectionH    Publisher section requesting open or NIL.                                Æ    document    Document pointer passed into the OpenNewEdition function.                                Æ    fdCreator    The fdCreator passed into the OpenNewEdition function.                                ¨    ioRefNum    Reference number for use by I/O routine. Not the same as EditionRefNum.                                                    ¨    ioProc    I/O routine to call to write formats.            ¨    Return value    A noErr code or appropriate error code.        eoCloseNew    Æ    info    Edition container to be closed after writing.    CloseEdition function for a publisher                            Æ    sectionH    Publisher section requesting close or NIL.                                Æ    ioRefNum    Value returned by eoOpenNew.            Æ    ioProc    Value returned by eoOpenNew.            Æ    success    Success value passed to the CloseEdition function.                                ¨    Return value    A noErr code or appropriate error code.        As Listing 2-9 demonstrates, you install your own edition opener function by first saving the current opener and then installing your own opener. The listing also shows an edition opener, the MyEditionOpener function. When it receives the eoCanSubscribe opener verb, the MyEditionOpener function calls another application-defined routine, MyCanSubscribe. The Edition Manager sends your edition opener this verb to help it build the list of files displayed by the NewSubscriber function. The MyCanSubscribe function returns noErr if it can subscribe to the file; otherwise, it calls the original edition opener to handle the request.Listing 2-9    Using your own edition opener functionVAR    gOriginalOpener: EditionOpenerProcPtr;    {global variable}PROCEDURE MyInstallMyOpener;BEGIN    FailOSErr(GetEditionOpenerProc(gOriginalOpener));    FailOSErr(SetEditionOpenerProc(@MyEditionOpener));END; {MyInstallMyOpener}FUNCTION MyEditionOpener (selector: EditionOpenerVerb;                                   VAR PB: EditionOpenerParamBlock)                                     : OSErr; BEGIN    WITH PB DO    BEGIN        CASE selector OF            eoCanSubscribe:                MyEditionOpener := MyCanSubscribe(PB);            eoOpen:                MyEditionOpener := MyEditionOpen(PB);            eoClose:                MyEditionOpener := MyEditionClose(PB);            OTHERWISE                {call the original edition opener}                MyEditionOpener                     := CallEditionOpenerProc(selector, PB,                                                    gOriginalOpener);        END; {of CASE}    END; {of WITH}END; {MyEditionOpener}FUNCTION MyCanSubscribe (VAR PB: EditionOpenerParamBlock): OSErr;BEGIN    {check file type to see if it is a file you can emulate as an }    { edition}    IF PB.info.fdType = {for example}'PICT' THEN        MyCanSubscribe := noErr    ELSE {otherwise, let the saved edition opener decide}            MyCanSubscribe := CallEditionOpenerProc(eoCanSubscribe,                                                                PB, gOriginalOpener);END; {MyCanSubscribe}Opening and Closing EditionsEach time the Edition Manager opens or closes an edition container, it calls the current edition opener procedure and passes it an opener verb and a parameter block.Your opener must be careful when closing documents since a document may already have been opened by another application. Be sure to use the Open/Deny modes whenever possible. Do not close a document if it was already open when your application opened it.Listing Files That Can Be Subscribed ToThe NewSubscriberDialog function calls the edition opener function and passes the eoCanSubscribe opener verb in the selector parameter to build the list of files that can be subscribed to. The preview in the subscriber dialog box is generated by calling the GetStandardFormats function (described in “Edition Container Formats” on page 2-101), which calls the format I/O procedure with the verbs eoOpen, ioHasFormat, ioRead, and then eoClose. See “Calling a Format I/O Function” on this page for detailed information on format I/O verbs.Reading From and Writing to FilesThe I/O procedure is a routine that actually reads and writes the data. It too has an interface of a selector and a parameter block.To override the standard reading and writing functions, create an I/O function. Note that you also need to provide your own opener function to call your I/O function. See “Calling an Edition Opener” on page 2-64.FUNCTION MyIO (selector: FormatIOVerb;                     VAR PB: FormatIOParamBlock): OSErr;Calling a Format I/O FunctionTo indicate to the Edition Manager which format I/O function to use, use the CallFormatIOProc function.err := CallFormatIOProc (selector, PB, routine);Set the selector parameter to one of the format I/O verbs. The format I/O verbs include n    ioHasFormatn    ioReadFormatn    ioNewFormatn    ioWriteFormatThe PB parameter of the CallFormatIOProc function contains a format I/O parameter block.TYPE FormatIOParamBlock =     RECORD        ioRefNum:                    LongInt;                    {reference number}        format:                    FormatType;                    {edition format type}        formatIndex    :                LongInt;                    {opener-specific enumeration }                                                { of formats}        offset:                    LongInt;                    {offset into format}        buffPtr:                    Ptr;                    {data starts here}        buffLen:                    LongInt;                    {length of data}    END;The routine parameter of the CallFormatIOProc function is a pointer to a formatI/O function.The following list shows which fields of FormatIOParamBlock are used by the format I/O verbs:Format I/O verb        Parameter    Description    Called by (continued)    ioHasFormat    Æ    ioRefNum    I/O reference number returned by opener.    EditionHasFormat, GetStandardFormats, and ReadEdition functions        Æ    format    Check for this format.            ¨    formatIndex    An optional enumeration of the supplied format.            ¨    buffLen    If found, return the length size or –1 if size is unknown.            ¨    Return value    A noErr or noTypeErr code.                        continued    ioReadFormat    Æ    ioRefNum    I/O reference number returned by opener.    ReadEdition and GetStandardFormats functions        Æ    format    Get this format.            Æ    formatIndex    Value returned by ioHasFormat.            Æ    offset    Read format beginning from this offset.            Æ    buffPtr    Put data beginning here.            ´    buffLen    Specify buffer length to read, and return actual amount received.            ¨    Return value    A noErr code, or appropriate error code.        ioNewFormat    Æ    ioRefNum    I/O reference number returned by opener.    SetEditionFormatMarkand WriteEdition functions        Æ    format    Create this format.            ¨    formatIndex    An optional enumeration of the supplied format.            ¨    Return value    A noErr code, or appropriate error code.        ioWriteFormat    Æ    ioRefNum    I/O reference number returned by opener.    WriteEdition function        Æ    format    Get this format.            Æ    formatIndex    Value returned by ioNewFormat.            Æ    offset    Write format beginning from this offset.            Æ    buffPtr    Get data beginning here.            ´    buffLen    Specify buffer length to write.            ¨    Return value    A noErr code or appropriate error code.        The marks for each format are kept by the Edition Manager. The format I/O function only needs to be able to read or write, beginning at any offset. If you know that your application always reads an entire format sequentially, you can ignore the offset. Edition Manager ReferenceThis section describes the data structures and routines that are specific to the Edition Manager. The “Data Structures” section describes the edition container record and the section record. The “Edition Manager Routines” section describes the routines your application can use to implement publish and subscribe features in your application.Data StructuresThis section describes the edition container record and the section record. See page 2-91 for a description of the new subscriber reply record, page 2-93 for a description of the new publisher reply record, page 2-95 for a description of the section options record, and page 2-99 for a description of the edition info record. For information on the edition opener parameter block and format I/O parameter block, see page 2-103 and page 2-104, respectively.The Edition Container RecordAn edition container record identifies a specific edition file. Many Edition Manager routines require an edition container record as a parameter. The EditionContainerSpec data type defines an edition container record.TYPE EditionContainerSpec =     RECORD        theFile:                        FSSpec;                    {file containing edition }                                                    { data}        theFileScript:                        ScriptCode;                    {script code of filename}        thePart:                        LongInt;                    {which part of file, }                                                    { always kPartsNotUsed}        thePartName:                        Str31;                    {reserved}        thePartScript:                        ScriptCode;                    {reserved}    END;Field descriptionstheFile    A file specificiation record that identifies the name and location of the edition file. Specify the file using the standard conventions for file specification records as described in the chapter “Introduction to File Management” in Inside Macintosh: Files.theFileScript    A script code that identifies the script in which the name of the document is to be displayed in the Finder. A script code of smSystemScript represents the default system script.thePart    A value that must always be set to kPartsNotUsed in System 7.thePartName    Reserved.thePartScript    Reserved.The Section RecordA section record identifies a specific publisher or subscriber section. It contains information to identify the section as a publisher or a subscriber, a time stamp to record the last modification of the section, and unique identification for each section. Many Edition Manager routines require a handle to a section record as a parameter. The SectionRecord data type defines a section record.TYPE SectionRecord =     RECORD        version:                    SignedByte;                    {always 1 in 7.0}        kind:                    SectionType;                    {publisher or subscriber}        mode:                    UpdateMode;                    {automatic or manual}        mdDate:                    TimeStamp;                    {last change in document}        sectionID:                    LongInt;                    {application-specific, }                                                { unique per document}        refCon:                    LongInt;                    {application-specific}        alias:                    AliasHandle;                    {handle to alias record}        {The following fields are private and are set up by the }        { RegisterSection function. Do not modify the private }        { fields.}        subPart:                    LongInt;                    {private}        nextSection:                    SectionHandle;                    {private, do not use as a }                                                { linked list}        controlBlock:                    Handle;                    {may be used for comparison }                                                { only}        refNum:                    EditionRefNum;                    {private}END;Field descriptionsversion    Indicates the version of the section record, currently $01.kind    Defines the section type as either publisher or subscriber with the stPublisher or stSubscriber constant.mode    Indicates if editions are updated automatically or manually.mdDate    Indicates which version (modification date) of the section’s contents is contained within the publisher or subscriber. The mdDate field is set to 0 when you create a new subscriber section and to the current time when you create a new publisher. Be sure to update this field each time publisher data is modified. The section’s modification date is compared to the edition’s modification date to determine whether the section and the edition contain the same data. The section modification date is displayed in the publisher and subscriber options dialog boxes. See “Closing an Edition” on page 2-28 for detailed information.sectionID    Provides a unique number for each section within a document. A simple way to implement this is to create a counter for each document that is saved to disk with the document. The counter should start at 1. The section ID is currently used as a tie breaker in the GoToPublisherSection function when there are multiple publishers to the same edition in a single document. The section ID should not be 0 or –1. See “Duplicating Publishers and Subscribers” on page 2-58 for information on multiple publishers.refCon    Reference constant available for application-specific use.alias    Contains a handle to the alias record for a particular section within a document.Whenever the user creates a publisher or subscriber, call the NewSection function (described on page 2-75) to create a section record and alias record.Edition Manager RoutinesThis section describes the routines you use ton    initialize the Edition Managern    create and register a sectionn    create and delete an edition containern    set and locate a format markn    read in edition datan    write out edition datan    close an edition after reading or writingn    display dialog boxesn    locate a publisher and edition from a subscribern    read and write non-edition filesResult codes appear at the end of each function where applicable. In addition to the specific result codes listed, you may receive errors generated by the Alias Manager, File Manager, and Memory Manager.Initializing the Edition ManagerYou use the InitEditionPack function to initialize the Edition Manager. Note that you should call this function only once.InitEditionPackBefore calling the InitEditionPack function, be sure to determine whether the Edition Manager is available on your system by using the Gestalt function with the gestaltEditionMgrAttr ('edtn') selector.FUNCTION InitEditionPack: OSErr;DESCRIPTIONThe InitEditionPack function returns an error if the package could not be loaded into the system heap and properly initialized. RESULT CODESnoErr    0    No error    memFullErr    –108    Could not load package    Creating and Registering a SectionYou use the NewSection function to create a new section (either publisher or subscriber) and alias record (which is a reference to the edition container from the document containing the publisher or subscriber section).The NewSection function registers a section much as the RegisterSection function informs the Edition Manager about a section (except that the NewSection function does not resolve an alias to find the edition container).When a section needs to be disposed of because the document containing the section is being closed or because the user has canceled the section, you need to call the UnRegisterSection function before disposing of the section.Using the IsRegisteredSection function, your application must verify that each event received is for a registered section. This is necessary because your application may have just called UnRegisterSection while the event was already being held in the event queue.If a user saves a document that contains sections under another name (using Save As) or pastes a portion of a document that contains a section into another document, use the AssociateSection function to update the section’s alias record. NewSectionUse the NewSection function to create a new section record and alias record for a new publisher or subscriber.FUNCTION NewSection (container: EditionContainerSpec;                            sectionDocument: FSSpecPtr;                             kind: SectionType; sectionID: LongInt;                            initialMode: UpdateMode;                             VAR sectionH: SectionHandle): OSErr;container    The edition you want to publish or subscribe to. sectionDocumentThe volume reference number, directory ID, and filename of the document that contains a section. The sectionDocument parameter can be NIL if your current document has never been saved. If so, when the user finally saves the document, remember to call the AssociateSection function for each section to update its alias record.kind    The type of section (publisher or subscriber) being created. sectionID    A unique number for a section within a document. The NewSection function initializes the sectionID field of the new section record with the specified value. Do not use 0 or –1 for an ID number; these numbers are reserved. If your application copies a section, you need to specify a unique number for the copied section. initialModeThe update mode for the section. For publishers this is either the pumOnSave or pumManual constant, and for subscribers it is either sumAutomatic or sumManual. A subscriber created with sumAutomatic mode automatically receives a Section Read event. To prevent this initial Section Read event, you should set the initialMode parameter to sumManual and then, when NewSection returns, set the mode field of the section record to sumAutomatic.sectionH    The NewSection function returns a handle to the allocated section record in this parameter. If an error occurs, NewSection returns NIL in this parameter.DESCRIPTIONThe NewSection function allocates two handles in the current zone: one handle for the section record and another handle for the alias record. Note that you are responsible for unregistering handles created by the Edition Manager.Your application receives the multiplePublisherWrn result code if there is another registered publisher to the same edition. Your application receives the notThePublisherWrn result code if another publisher (to the same edition) was the last section to write to the edition. The multiplePublisherWrn result code takes priority over the notThePublisherWrn result code.RESULT CODESnoErr    0    No error    editionMgrInitErr    –450    Manager not initialized    badSectionErr    –451    Not a valid section type    badSubPartErr    –454    Bad edition container spec    multiplePublisherWrn    –460    Already is a publisher    notThePublisherWrn    –463    Not the publisher    SEE ALSOFor information on the edition container record, see page 2-71. For information on the section record, see “The Section Record” beginning on page 2-72. For information on file specification records, see Inside Macintosh: Files. See Listing 2-4 on page 2-33 for an example that uses NewSection to create a publisher and Listing 2-6 on page 2-40 for an example that creates a subscriber using NewSection.RegisterSectionWhen opening a document that contains sections, register each section using the RegisterSection function. FUNCTION RegisterSection (sectionDocument: FSSpec;                                  sectionH: SectionHandle;                                   VAR aliasWasUpdated: Boolean): OSErr;sectionDocumentThe volume reference number, directory ID, and filename of the document that contains a section. sectionH    A handle to the section record for a given section.aliasWasUpdatedA Boolean value that returns TRUE if the alias for the edition container subscribed to was out of date and was updated. This may occur if the edition file was moved to a new location or was renamed.DESCRIPTIONThe RegisterSection function adds the section record to the Edition Manager’s list of registered sections and tries to allocate a control block. After calling the RegisterSection function, the controlBlock field of the section record contains either NIL or a valid control block.For a subscriber, the controlBlock field contains NIL if the RegisterSection function could not locate the edition container being subscribed to. The RegisterSection function then returns either the containerNotFoundWrn or the userCanceledErr result code. For a publisher, if the RegisterSection function could not locate its corresponding edition container, the Edition Manager creates an edition container in the last place the edition was located and creates a control block for it. If the RegisterSection function could not locate a publisher’s corresponding edition container or its volume, the controlBlock field contains NIL. You should never re-register a section that is already registered.Note that you can compare control blocks for individual sections. If two sections contain the same control block value, these sections publish or subscribe to the same edition (unless the control block is NIL). The Edition Manager keeps track of how many sections are referencing a control block to know when it can be deallocated. The control block maintains a count of how many sections are referencing it. Each time you use the UnRegisterSection function, the control block subtracts 1 from the number of sections. When the number of sections reaches 0, the control block is deallocated.Your application receives the multiplePublisherWrn result code if there is another registered publisher to the same edition. Your application receives the notThePublisherWrn result code if another publisher (to the same edition) was the last section to write to the edition. The multiplePublisherWrn result code takes priority over the notThePublisherWrn result code.RESULT CODESnoErr    0    No error    userCanceledErr    –128    User clicked Cancel in dialog box    editionMgrInitErr    –450    Manager not initialized    badSectionErr    –451    Not valid section type    multiplePublisherWrn    –460    Already is a publisher    containerNotFoundWrn    –461    Alias was not resolved    notThePublisherWrn    –463    Not the publisher    SEE ALSOFor information on the section record, see “The Section Record” beginning on page 2-72. For information on file specification records, see Inside Macintosh: Files. For additional information and an example of the use of RegisterSection, see “Opening and Closing a Document Containing Sections” beginning on page 2-22.UnRegisterSectionWhen a section needs to be disposed of because the document containing the section is being closed or because the user has canceled the section, you need to call the UnRegisterSection function before disposing of the section.FUNCTION UnRegisterSection (sectionH: SectionHandle): OSErr;sectionH    A handle to the section record for a given section.DESCRIPTIONThe UnRegisterSection function removes the section from the Edition Manager’s list of registered sections. You can then dispose of the section record and alias record with standard Memory Manager and Resource Manager calls. Once unregistered, a section does not receive any events and cannot read or write any data. Depending on your Clipboard strategy, you may want to unregister sections that have been cut into the Clipboard.RESULT CODESnoErr    0    No error    fBsyErr    –47    Section doing I/O    editionMgrInitErr    –450    Manager not initialized    notRegisteredSectionErr    –452    Not registered    IsRegisteredSectionUpon receiving a section event, your application must call the IsRegisteredSection function to verify that the event received is for a registered section. You must call IsRegisteredSection before handling a section event because your application may have just called UnRegisterSection while the event was already being held in the event queue.FUNCTION IsRegisteredSection (sectionH: SectionHandle): OSErr;sectionH    A handle to the section record for a given section. DESCRIPTIONThe IsRegisteredSection function returns a result code (not a Boolean value) indicating whether the section is registered. A noErr result code indicates that a section is registered.RESULT CODESnoErr    0    No error    notRegisteredSectionErr    –452    Not registered    SEE ALSOFor an example of the use of IsRegisteredSection, see Listing 2-1 on page 2-14.AssociateSectionIf a user saves a document that contains sections under another name (using Save As) or pastes a portion of a document that contains a section into another document, use the AssociateSection function to update the section’s alias record.FUNCTION AssociateSection (sectionH: SectionHandle;                                    newSectionDocument: FSSpecPtr): OSErr;sectionH    A handle to the section record for a given section. newSectionDocumentThe volume reference number, directory ID, and filename of the new document. DESCRIPTIONThe AssociateSection function calls UpdateAlias on the section’s alias record. RESULT CODESnoErr    0    No error    paramErr    –50    Invalid parameter    SEE ALSOFor information on the UpdateAlias function, see the chapter “Alias Manager” in Inside Macintosh: Files.Creating and Deleting an Edition ContainerEach time a user creates a new publisher section within a document to an edition that does not already exist, you use the CreateEditionContainerFile function to create an empty edition container.To remove the edition container, use the DeleteEditionContainerFile function.CreateEditionContainerFileYou use the CreateEditionContainerFile function to create an empty edition container.FUNCTION CreateEditionContainerFile                             (editionFile: FSSpec; fdCreator: OSType;                              editionFileNameScript: ScriptCode): OSErr;editionFileThe volume reference number, directory ID, and filename for the edition container being created. fdCreator    The creator type for the edition.editionFileNameScriptThe script of the filename. (You can get this value from the theFileScript field of an edition container specification record.)DESCRIPTIONThe CreateEditionContainerFile function creates an empty edition container file (it does not contain any formats). This function sets the file type of the edition to 'edtu'. As soon as you write data to the edition, the Edition Manager updates the type (to 'edtp' for graphics, 'edtt' for text, or 'edts' for sound). If your application writes both 'TEXT' and 'PICT' formats to the edition, the Edition Manager sets the file type to the type that was written first. If your application has a bundle, you should designate an icon for the appropriate edition types that you can write. RESULT CODESnoErr    0    No error    dskFulErr    –34    Disk is full    nsvErr    –35    No such volume    ioErr    –36    I/O error    bdNamErr    –37    Bad filename    fnfErr    –43    File not found    dirNFErr    –120    Directory not found    editionMgrInitErr    –450    Manager not initialized    SEE ALSOFor information on file specification records, see Inside Macintosh: Files. For an example of the use of CreateEditionContainerFile, see Listing 2-4 on page 2-33.DeleteEditionContainerFileIf a user cancels a publisher section within a document or closes a document containing a newly created publisher without saving, you need to remove the edition container. To locate the appropriate edition container to be deleted, use the GetEditionInfo function. You use the UnRegisterSection function (only after using the GetEditionInfo function) to unregister the section record and alias record of the publisher being canceled. To remove the edition container, use the DeleteEditionContainerFile function. FUNCTION DeleteEditionContainerFile (editionFile: FSSpec): OSErr;editionFileThe volume reference number, directory ID, and filename for the edition container being deleted.DESCRIPTIONIf the user cancels a publisher, do not call the DeleteEditionContainerFile function until the user saves the document. This allows the user to undo changes and revert to the last saved version of the document.The DeleteEditionContainerFile function deletes the edition container only if there is no registered publisher. You need to unregister a publisher before you can delete its corresponding edition container.You should use the DeleteEditionContainerFile function even if there are subscribers to the edition. When a subscriber section tries to read in data, it receives an error if the edition container has been deleted. RESULT CODESnoErr    0    No error    nsvErr    –35    No such volume    ioErr    –36    I/O error    bdNamErr    –37    Bad filename    fnfErr    –43        File not found    dirNFErr    –120    Directory not found    editionMgrInitErr    –450    Manager not initialized    SEE ALSOSee page 2-98 for detailed information on the GetEditionInfo function. See page 2-77 for information on the UnRegisterSection function. For information on file specification records, see Inside Macintosh: Files. Setting and Getting a Format MarkUse the SetEditionFormatMark function to set the current mark for a section format and the GetEditionFormatMark function to get the current mark for a particular format. SetEditionFormatMarkA format mark indicates the next position of a read or write operation. Initially, a mark defaults to 0. After reading or writing data, the format mark is set past the last position written to or read from. To set the current mark for a given format, use the SetEditionFormatMark function.FUNCTION SetEditionFormatMark (whichEdition: EditionRefNum;                                         whichFormat: FormatType;                                         setMarkTo: LongInt): OSErr;whichEditionThe reference number for the edition. whichFormatThe format type for the edition.setMarkTo    The offset for the next read or write for this format.DESCRIPTIONThe SetEditionFormatMark function sets the current mark for the specified format type according to the value of the setMarkTo parameter.RESULT CODESnoErr    0    No error    rfNumErr    –51    Bad edition reference number    noTypeErr    –102    Unknown format (subscriber only)    editionMgrInitErr    –450    Manager not initialized    GetEditionFormatMarkUse the GetEditionFormatMark function to get the current mark for a particular format.FUNCTION GetEditionFormatMark (whichEdition: EditionRefNum;                                         whichFormat: FormatType;                                          VAR currentMark: LongInt): OSErr;whichEditionThe reference number for the edition. whichFormatThe format type whose mark you want to get.currentMarkThe GetEditionFormatMark function returns the mark for the specified format in this parameter. DESCRIPTIONIf the edition does not support the format specified in the whichFormat parameter, you receive a noTypeErr result code.RESULT CODESnoErr    0    No error    rfNumErr    –51    Bad edition reference number    noTypeErr    –102    Unknown format    editionMgrInitErr    –450    Manager not initialized    Reading in Edition DataTo initiate the reading of data from an edition (for a subscriber), use the OpenEdition function.Use the EditionHasFormat function to learn in which formats the edition data is available.Use the ReadEdition function to read data from an edition. This function reads from the current mark for the specified format.OpenEditionTo initiate the reading of data from an edition (for a subscriber), use the OpenEdition function.FUNCTION OpenEdition (subscriberSectionH: SectionHandle;                              VAR refNum: EditionRefNum): OSErr;subscriberSectionHA handle to the section record for a given section. refNum    The OpenEdition function returns the reference number for the edition in this parameter.DESCRIPTIONThe OpenEdition function opens an edition for reading and returns a reference number that your application can use to refer to this edition in other Edition Manager routines. Multiple subscribers can each call the OpenEdition function simultaneously (each call returns a different reference number) and read data from a single edition. If a publisher (located on a different machine) is writing to an edition when you use the OpenEdition function, you receive an flLckedErr result code.RESULT CODESnoErr    0    No error    fnfErr    –43    File not found    flLckedErr    –45    Publisher writing to an edition    permErr    –54    Not a subscriber    editionMgrInitErr    –450    Manager not initialized    SEE ALSOFor an example of the use of OpenEdition, see Listing 2-7 on page 2-42.EditionHasFormatUse the EditionHasFormat function to learn in which formats the edition data is available.FUNCTION EditionHasFormat (whichEdition: EditionRefNum;                                    whichFormat: FormatType;                                     VAR formatSize: Size): OSErr;whichEditionThe reference number for the edition. whichFormatThe format type that you are requesting. For the whichFormat parameter, you should decide which formats to read in the same way that you do when reading data from the scrap. You can also get a list of all the available formats and their respective lengths by reading the kFormatListFormat ('fmts') format. formatSizeThe EditionHasFormat function returns the format length in this parameter.DESCRIPTIONIf the requested format is available, the EditionHasFormat function returns noErr, and the formatSize parameter returns the size of the data in the specified format or kFormatLengthUnknown (–1), which signifies that the size is unknown. You should therefore continue to read the format until there is no more data.NoteNoteThe Translation Manager (if it is available) attempts implicit translation under certain circumstances. For instance, it does so when your application attempts to read from an edition a format type that is not in the edition. In this case, the Translation Manager attempts to translate the data into the requested format. For more information, see the chapter “Translation Manager” in Inside Macintosh: More Macintosh Toolbox.uRESULT CODESnoErr    0    No error    rfNumErr    –51    Bad edition reference number    noTypeErr    –102    Format not available    editionMgrInitErr    –450    Manager not initialized    SEE ALSOFor an example of the use of EditionHasFormat, see Listing 2-7 beginning on page 2-42. For information about the Translation Manager and Scrap Manager, see Inside Macintosh: More Macintosh Toolbox.ReadEditionUse the ReadEdition function to read data from an edition. This function reads from the current mark for the specified format.FUNCTION ReadEdition (whichEdition: EditionRefNum;                              whichFormat: FormatType; buffPtr: UNIV Ptr;                             VAR buffLen: Size): OSErr;whichEditionThe reference number for the edition. whichFormatThe format type that you want to read. buffPtr    A pointer to the buffer into which you want to read the data.buffLen    The number of bytes that you want to read into the buffer. The ReadEdition function returns the actual number of bytes read in the buffLen parameter. DESCRIPTIONThe ReadEdition function reads data from the edition into the specified buffer. ReadEdition returns in the buffLen parameter the total number of bytes read into the buffer. If the buffLen parameter returns a value smaller than the value you have specified, there is no additional data to read, and the ReadEdition function returns a noErr result code. If you use the ReadEdition function after all data is read in, the ReadEdition function returns an eofErr result code.You can read data from an edition while a publisher on the same machine is writing data to the same edition. The data that you are reading is the old edition (not the data that the publisher is writing). If the publisher finishes writing data before you are through reading the old edition data, the ReadEdition function returns an abortErr result code. If the ReadEdition function returns an abortErr result code, you should stop trying to read data and use the CloseEdition function with the successful parameter set to FALSE. NoteThe Translation Manager (if it is available) attempts implicit translation under certain circumstances. For instance, it does so when your application attempts to read from an edition a format type that is not in the edition. In this case, the Translation Manager attempts to translate the data into the requested format. For more information, see the chapter “Translation Manager” in Inside Macintosh: More Macintosh Toolbox.u RESULT CODESnoErr    0    No error    abortErr    –27    Publisher has written a new edition    ioErr    –36    I/O error    fnOpnErr    –38    File not open    eofErr    –39    No more data of that format    rfNumErr    –51    Bad edition reference number    noTypeErr    –102    Format not available    editionMgrInitErr    –450    Manager not initialized    SEE ALSOFor an example of the use of ReadEdition, see Listing 2-7 beginning on page 2-42. Writing out Edition DataTo initiate the writing of data from a publisher to its edition container, use the OpenNewEdition function. (To create an edition container, use the CreateEditionContainerFile function, as described on page 2-79.)Use the WriteEdition function to write data to an edition.OpenNewEditionTo initiate the writing of data from a publisher to its edition container, use the OpenNewEdition function.FUNCTION OpenNewEdition (publisherSectionH: SectionHandle;                                 fdCreator: OSType;                                 publisherSectionDocument: FSSpecPtr;                                  VAR refNum: EditionRefNum): OSErr;publisherSectionHThe publisher section that is writing to the edition. fdCreator    The Finder creator type of the new edition icon.publisherSectionDocumentThe document that contains the publisher. This parameter is used to create an alias from the edition to the publisher’s document. If you pass NIL for publisherSectionDocument, an alias is not made in the edition file.refNum    The OpenNewEdition function returns the reference number for the edition in this parameter. You specify this reference number as a parameter for subsequent calls to WriteEdition, SetEditionFormatMark, and CloseEdition to specify which publisher is writing its data to an edition. If the edition cannot be opened for writing because there is another publisher writing to it, or because the file system does not allow writing, an error is returned and OpenNewEdition sets refNum to NIL. DESCRIPTIONThe OpenNewEdition function opens an edition for writing. The function returns an flLckdErr result code if there is a subscriber on another machine reading data from the same edition. The OpenNewEdition function returns a permErr result code if there is a registered publisher to that edition on another machine.The Edition Manager allows two registered publishers that are located on the same machine to write to the same edition. Note that multiple publishers cannot write to the same edition simultaneously—only one publisher can write to an edition at a given time.RESULT CODESnoErr    0    No error    ioErr    –36    I/O error    flLckdErr    –45    Edition in use by another section    permErr    –54    Registered publisher on another machine    wrPermErr    –61    Not a publisher    editionMgrInitErr    –450    Manager not initialized    SEE ALSOFor an example of the use of OpenNewEdition, see Listing 2-5 beginning on page 2-36. WriteEditionUse the WriteEdition function to write data to an edition. This function begins writing at the current mark for the specified format.FUNCTION WriteEdition (whichEdition: EditionRefNum;                               whichFormat: FormatType;                               buffPtr: UNIV Ptr; buffLen: Size): OSErr;whichEditionThe reference number for the edition. whichFormatThe format type that you want to write. buffPtr    A pointer to the buffer containing the data to write to the edition. buffLen    The number of bytes that you want to write to the edition. DESCRIPTIONThe WriteEdition function writes the specified number of bytes to the edition. If the data cannot be entirely written to the edition, the WriteEdition function returns an error.RESULT CODESnoErr    0    No error    dskFulErr    –34    Disk is full    ioErr    –36    I/O error    rfNumErr    –51    Bad edition reference number    editionMgrInitErr    –450    Manager not initialized    SEE ALSOFor an example that writes data to an edition, see Listing 2-5 beginning on page 2-36. Closing an Edition After Reading or WritingAfter finishing reading from or writing to an edition, use the CloseEdition function to close the edition.CloseEditionUse the CloseEdition function to close an edition after you finish reading from or writing to it.FUNCTION CloseEdition (whichEdition: EditionRefNum;                               successful: Boolean): OSErr;whichEditionThe reference number for the edition. successfulA value that indicates whether your application was successful (TRUE) or unsuccessful (FALSE) in reading from or writing data to the edition.DESCRIPTIONWhen a subscriber successfully finishes reading data from the edition, the CloseEdition function takes the modification date of the edition file that you have read and puts it in the mdDate field of the subscriber’s section record. This indicates that the data contained in the edition and the subscriber section within the document are the same.When a subscriber is unsuccessful in reading data from an edition (because there is not enough memory, or you didn’t find a format that you can read), set the successful parameter to FALSE. The CloseEdition function then closes the edition, but does not set the mdDate field. This implies that the subscriber is not updated with the latest edition.When a publisher successfully finishes writing data to an edition, the CloseEdition function makes the data that the publisher has written to the edition available to any subscribers and sets the corresponding edition file’s modification date (ioFlMdDat) to the mdDate field of the publisher’s section record. The Edition Manager then sends a Section Read event to all current subscribers set to automatic update mode. At this point, the file type of the edition file is set based on the first known format that the publisher wrote.When a publisher is unsuccessful in writing data to an edition, the CloseEdition function discards what the publisher has written to the edition. The data contained in the edition prior to writing remains unchanged, and Section Read events are not sent to subscribers. RESULT CODESnoErr    0    No error    ioErr    –36    I/O error    fnOpnErr    –38    File not open    rfNumErr    –51    Bad edition reference number    editionMgrInitErr    –450    Manager not initialized    SEE ALSOFor an example of the use of CloseEdition, see Listing 2-5 beginning on page 2-36. Displaying Dialog BoxesThe Edition Manager supports three dialog boxes: publisher, subscriber, and options dialog boxes. Your application can display simple dialog boxes that appear centered on the user’s screen, or you can customize your dialog boxes.Use the GetLastEditionContainerUsed function to get the default edition to display.Use the NewSubscriberDialog function to display the subscriber dialog box on the user’s screen and use the NewPublisherDialog function to display the publisher dialog box on the user’s screen. Unlike the Standard File Package routines, the NewPublisherDialog and the NewSubscriberDialog functions allow you to specify the initial volume reference number and directory ID so that there can be one default location for editions for all applications.You use the SectionOptionsDialog function to display the publisher options and subscriber options dialog boxes on the user’s screen.The NewSubscriberExpDialog, NewPublisherExpDialog, and SectionOptionsExpDialog functions are the same as the simple dialog functions but have five additional parameters.GetLastEditionContainerUsedUse the GetLastEditionContainerUsed function to get the default edition to display. This function allows a user to easily subscribe to the data recently published. FUNCTION GetLastEditionContainerUsed                         (VAR container: EditionContainerSpec): OSErr;container    If the GetLastEditionContainerUsed function locates the last edition for which a section was created, the container parameter contains its volume reference number, directory ID, filename, and part, and returns a noErr result code. (The last edition created is associated with the last time that your application or another application located on the same machine used the NewSection function.) DESCRIPTIONIf the last edition used is missing, the GetLastEditionContainerUsed function returns an fnfErr result code, but still returns the correct volume reference number and directory ID that you should use for the NewSubscriberDialog function.Pass the information from the GetLastEditionContainerUsed function to the NewSubscriberDialog function.RESULT CODESnoErr    0    No error    fnfErr    –43    Edition container not found    editionMgrInitErr    –450    Manager not initialized    SEE ALSOFor an example of the use of GetLastEditionContainerUsed, see Listing 2-6 beginning on page 2-40. For a description of the edition container record, see page 2-71. The NewSubscriberDialog function is described next.NewSubscriberDialogWhen a user chooses the Subscribe To menu command, your application should call the NewSubscriberDialog function to allow the user to choose an edition to subscribe to. FUNCTION NewSubscriberDialog                             (VAR reply: NewSubscriberReply): OSErr;reply    The new subscriber reply record. You specify a location to use as the default edition container in the container field of this record. You also specify in the formatsMask field which edition format types NewSubscriberDialog should display. The NewSubscriberDialog function returns information concerning the user’s choice in the canceled and container fields of this record.TYPE NewSubscriberReply =     RECORD        canceled:                    Boolean;                            {user canceled }                                                        { dialog box}        formatsMask:                    SignedByte;                            {formats required}        container:                    EditionContainerSpec;                            {edition selected}    END;Field descriptionscanceled    The NewSubscriberDialog function returns in this field a value that indicates whether the user canceled the dialog box. The function returns TRUE in the canceled field if the user canceled the dialog box. Otherwise, the function returns FALSE in this field and returns in the container field the edition container for the new subscriber.formatsMask    The formatsMask field indicates which edition format type (text, graphics, and sound) to display within the subscriber dialog box. You can set the formatsMask field to the following constants: kTEXTformatMask (1), kPICTformatMask (2), or ksndFormatMask (4). To support a combination of formats, add the constants together. For example, a formatsMask of 3 displays both graphics and text edition format types in the subscriber   dialog box.container    The edition container of the last edition published or subscribed to. You provide in this parameter the location and filename to use as the default edition to subscribe to. If the user clicks the Subscribe button, NewSubscriberDialog returns FALSE in the canceled field and returns the selected edition container for the new subscriber in the container field.     DESCRIPTIONThe NewSubscriberDialog function displays the subscriber dialog box on the user’s screen. The NewSubscriberDialog function (which is based on the CustomGetFile procedure described in the chapter “Standard File Package” in Inside Macintosh: Files) switches to the volume reference number and directory ID and selects the filename of the edition container that you specified in the container field of the reply parameter. Use the GetLastEditionContainerUsed function to get the edition container of the last edition that was either published or subscribed to, then set the container field to this edition container. This allows the user to publish and then easily subscribe.Note that if an edition does not contain either 'PICT', 'TEXT', or 'snd ' data, the NewSubscriberDialog function does not list the edition file in the new subscriber dialog box (unless you install an opener that can recognize the edition’s data in response to the eoCanSubscribe verb).RESULT CODESnoErr    0    No error    editionMgrInitErr    –450    Manager not initialized or could not load package    badSubPartErr    –454    Bad edition container spec    SEE ALSOFor an illustration of the new subscriber dialog box, see Figure 2-12 on page 2-37. For an example of the use of NewSubscriberDialog, see Listing 2-6 beginning on page 2-40. For a description of the edition container record, see page 2-71. For information on edition openers, see “Subscribing to Non-Edition Files” beginning on page 2-62. NewPublisherDialogWhen a user selects a portion of a document and then chooses the Create Publisher menu command, your application should call the NewPublisherDialog function to allow the user to choose a name and location of the edition to which your application writes the publisher data. Your application specifies a location and name to use as the default edition and provides a preview of the publisher data to the NewPublisherDialog function. FUNCTION NewPublisherDialog                         (VAR reply: NewPublisherReply): OSErr;reply    A new publisher reply record. You specify a location to use as the default edition container in the container field of this record. You also specify information in the usePart, preview, and previewFormat fields. The NewPublisherDialog function returns information concerning the user’s choice in the canceled, replacing, and container fields of this record.TYPE NewPublisherReply =     RECORD        canceled:                    Boolean;                    {user canceled dialog box}            replacing:                    Boolean;                    {user chose existing }                                                 { filename for an edition}        usePart:                    Boolean;                    {always false in version 7.0}        preview:                    Handle;                    {handle to 'prvw', 'PICT', }                                                { 'TEXT', or 'snd ' data}         previewFormat:                    FormatType;                    {type of preview}        container:                    EditionContainerSpec;                                                {edition chosen}    END;Field descriptionscanceled    The NewPublisherDialog function returns in this field a value that indicates whether the user canceled the dialog box. The function returns TRUE in the canceled field if the user canceled the dialog box. The function returns FALSE in this field if the user clicked the Publish button and returns in the container field the edition container for the new publisher.replacing    The NewPublisherDialog function returns TRUE in the replacing field if the user chose an existing filename from the list of available editions and confirmed this replacement. If the value of the replacing field is TRUE, do not call the CreateEditionContainerFile function. If the value of this field and the canceled field is FALSE, you can call CreateEditionContainerFile to create a new edition container.usePart    A value that must be set to FALSE before calling the NewPublisherDialog function.preview    A handle to 'prvw', 'PICT', 'TEXT', or 'snd ' data. The NewPublisherDialog function displays this data in the preview area of the dialog box.previewFormat    A value that indicates which type of data the handle in the preview field references.container    An edition container record that specifies the volume reference number, directory ID, and filename to use as the default edition to publish the data to. The NewPublisherDialog function returns in this field the edition container that the user selected. DESCRIPTIONThe NewPublisherDialog function displays the new publisher dialog box on the user’s screen. The NewPublisherDialog function (which is based on the CustomPutFile procedure described in the chapter “Standard File Package” in Inside Macintosh: Files) switches to the volume reference number and directory ID specified by the edition container, sets the editable text item to the filename specified by the edition container, and displays a preview of the publisher data in the new publisher dialog box. The NewPublisherDialog function handles all user interaction until the user clicks the Cancel or Publish button.You should deallocate the handle referenced by the preview field to free up memory.RESULT CODESnoErr    0    No error    editionMgrInitErr    –450    Manager not initialized or could not load package    badSubPartErr    –454    Bad edition container spec    SEE ALSOFor an illustration of the new publisher dialog box, see Figure 2-11 on page 2-29. For an example of the use of NewPublisherDialog, see Listing 2-4 beginning on page 2-33. For a description of the edition container record, see page 2-71. SectionOptionsDialogUse the SectionOptionsDialog function to display the publisher options and subscriber options dialog boxes on the user’s screen.FUNCTION SectionOptionsDialog                              (VAR reply: SectionOptionsReply): OSErr;reply    The reply parameter contains a section options reply record. You specify a handle to the publisher’s or subscriber’s section record in the sectionH field of this record. The SectionOptionsDialog function returns information concerning the user’s actions in the canceled, changed, and action fields.TYPE SectionOptionsReply =     RECORD        canceled:                Boolean;                        {user canceled dialog box}        changed:                Boolean;                        {changed the section record}        sectionH:                SectionHandle;                        {handle to the specified }                                                { section record}        action:                ResType;                        {action codes}    END;Field descriptionscanceled    The SectionOptionsDialog function returns in this field a value that indicates whether the user canceled the dialog box. The function returns TRUE in the canceled field if the user canceled the dialog box. Otherwise, the function returns FALSE in this field. changed    The SectionOptionsDialog function returns TRUE in this field if the user changed the section record. For example, the update mode may have changed. Otherwise, the function returns FALSE in this field. sectionH    A handle to the section record for the section the user selected.action    The SectionOptionsDialog function returns in this field the code for one of five user actions: action code 'read' for user selection of the Get Edition Now button, action code 'writ' for user selection of the Send Edition Now button, action code 'goto' for user selection of the Open Publisher button, action code 'cncl' for user selection of the Cancel Publisher or Cancel Subscriber button, or action code '    ' ($20202020) for user selection of the OK button.DESCRIPTIONThe SectionOptionsDialog function displays the appropriate options dialog box for the specified section record. The function displays information about the subscriber or publisher, such as its latest edition and current update mode setting, and allows the user to perform various actions. The SectionOptionsDialog function handles all user interaction until the user selects a button. The function returns the user’s action in the action field of the reply parameter; your application should then perform the corresponding action. RESULT CODESnoErr    0    No error    memFullErr    –108    Memory full    SEE ALSOFor illustrations of the section options dialog box, see Figure 2-13 through Figure 2-16 beginning on page 2-43. For an example of the use of SectionOptionsDialog, see Listing 2-8 beginning on page 2-46. For a description of the section record, see page 2-72. NewSubscriberExpDialog, NewPublisherExpDialog, SectionOptionsExpDialogThe NewSubscriberExpDialog, NewPublisherExpDialog, and SectionOptionsExpDialog functions are the same as the simple dialog functions but have five additional parameters. These additional parameters allow you to add items to the bottom of the dialog boxes, apply alternate mapping of events to item hits, apply alternate meanings to the item hits, and choose the location of the dialog boxes.FUNCTION NewSubscriberExpDialog                     (VAR reply: NewSubscriberReply; where: Point;                     expansionDITLresID: Integer;                      dlgHook: ExpDlgHookProcPtr;                      filterProc: ExpModalFilterProcPtr;                      yourDataPtr: UNIV Ptr): OSErr;FUNCTION NewPublisherExpDialog                     (VAR reply: NewPublisherReply; where: Point;                     expansionDITLresID: Integer;                      dlgHook: ExpDlgHookProcPtr;                      filterProc: ExpModalFilterProcPtr;                      yourDataPtr: UNIV Ptr): OSErr;FUNCTION SectionOptionsExpDialog                     (VAR reply: SectionOptionsReply; where: Point;                     expansionDITLresID: Integer;                      dlgHook: ExpDlgHookProcPtr;                      filterProc: ExpModalFilterProcPtr;                      yourDataPtr: UNIV Ptr): OSErr;reply    A new subscriber reply, new publisher reply, or section options reply record. You specify information in the fields of this record just as you do in the the corresponding fields of records used by NewSubscriberDialog, NewPublisherDialog, and SectionOptionsDialog.where    A point that specifies a location on the screen where the function displays the dialog box. You can automatically center the dialog box by passing (–1, –1) in the where parameter. expansionDITLresIDA value of 0 or a valid item list ('DITL') resource ID. This integer is the ID of a dialog item list whose items are appended to the end of the standard dialog item list. The dialog items keep their relative positions, but they are moved as a group to the bottom of the dialog box.dlgHook    A pointer to an expandable dialog hook function or NIL. An expandable dialog hook function is similar to a dialog hook function except that an expandable dialog hook function accepts an additional parameter. The NewSubscriberExpDialog, NewPublisherExpDialog, and SectionOptionsExpDialog functions call your expandable dialog hook function after each call to the ModalDialog procedure. The expandable dialog hook function should take the appropriate action, such as filling in a checkbox. The itemOffset parameter to the expandable dialog hook function is the number of items in the item list before your expansion dialog items. You need to subtract the item offset from the item hit to get the relative item number in the expansion item list. The expandable dialog hook function should return as its function result the absolute item number. filterProcA pointer to an expandable modal-dialog filter function or NIL. An expandable modal-dialog filter function is similar to a modal-dialog filter function or event filter function except that an expandable modal-dialog filter function accepts two extra parameters. The ModalDialog procedure calls the expandable modal-dialog filter function you provide in this parameter. An expandable modal-dialog filter function allows you to map real events (such as a mouse-down event) to an item hit (such as clicking a Cancel button). For instance, you may want to map a keyboard equivalent to an item hit.yourDataPtrReserved for your use. It is passed back to your hook and event filter function. This parameter does not have to be of type Ptr—it can be any 32-bit quantity that you want. In Pascal, you can pass yourDataPtr in register A6, and declare your dialog hook and event filter as local functions without the last parameter. The stack frame is set up properly for these functions to access their parent local variables.DESCRIPTIONThe NewPublisherExpDialog, NewSubscriberExpDialog, and SectionOptionsExpDialog functions display the appropriate dialog box, handle user interaction, and call any functions you have provided in the dlgHook and filterProc parameters.For the NewPublisherExpDialog and NewSubscriberExpDialog functions, all the pseudo-items for the Standard File Package such as hookFirstCall(–1), hookNullEvent(100), hookRebuildList(101), and hookLastCall(–2) can be used, as well as hookRedrawPreview(150).For the SectionOptionsExpDialog function, the only valid pseudo-items are hookFirstCall(–1), hookNullEvent(100), hookLastCall(–2), emHookRedrawPreview(150), emHookCancelSection(160), emHookGoToPublisher(161), emHookGetEditionNow(162), emHookSendEditionNow(162), emHookManualUpdateMode(163), and emHookAutoUpdateMode(164).If you provide an expandable dialog hook function, it must contain the following parameters:FUNCTION MyExpDlgHook (itemOffset: Integer; itemHit: Integer;                                theDialog: DialogPtr;                                  yourDataPtr: Ptr): Integer;If you provide an expandable modal-dialog filter function, it must contain the following parameters.FUNCTION MyExpModalFilter (theDialog: DialogPtr;                                     VAR theEvent: EventRecord;                                     itemOffset: Integer;                                     VAR itemHit: Integer;                                     yourDataPtr: Ptr): Boolean;SEE ALSOSee the chapter “Dialog Manager” in Inside Macintosh: Macintosh Toolbox Essentials for additional information on item lists. See the chapter “Standard File Package” in Inside Macintosh: Files for information on dialog hook and modal-dialog filter functions.Locating a Publisher and Edition From a SubscriberThe GetEditionInfo function returns information about a section’s edition such as its location, last modification date, creator, and type.Once you locate a section’s edition, you can use the GoToPublisherSection function to find the document containing the publisher.GetEditionInfoUse the GetEditionInfo function to obtain information about a section’s edition, such as its location, last modification date, creator, and type.FUNCTION GetEditionInfo                            (sectionH: SectionHandle;                              VAR editionInfo: EditionInfoRecord): OSErr;sectionH    A handle to the section record for a given section. editionInfoAn edition information record. The GetEditionInfo function returns the public information contained in the section’s control block.DESCRIPTIONThe Edition Manager ensures that the existing edition name corresponds to the Finder’s existing edition name. If the controlBlock field of the section record is set to NIL or the edition cannot be located, the GetEditionInfo function returns an fnfErr result code.The GetEditionInfo function returns information about the section’s edition in a data structure of type EditionInfoRecord.TYPE EditionInfoRecord =     RECORD        crDate:                TimeStamp;                            {date edition container }                                                    { was created}        mdDate:                TimeStamp;                            {date of last change}        fdCreator:                OSType;                            {file creator}        fdType:                OSType;                            {file type}        container:                EditionContainerSpec;                            {the edition}    END;Field descriptionscrDate    The creation date of the edition. mdDate    The modification date of the edition.fdCreator    The creator of the edition file. fdType    The file type of the edition file. container    An edition container record, which specifies the volume reference number, directory ID, filename, script, and part number for the edition.RESULT CODESnoErr    0    No error    fnfErr    –43    Not registered or file moved    editionMgrInitErr    –450    Manager not initialized    SEE ALSOFor an example of the use of GetEditionInfo, see Listing 2-8 beginning on page 2-46. For another use of this function, see “Canceling Sections Within Documents” beginning on page 2-48. For a description of the edition container record, see page 2-71. GoToPublisherSectionWhen the user wants to locate the publisher for a particular subscriber (by clicking Open Publisher in the subscriber options dialog box), the SectionOptionsDialog function returns the action code 'goto' in the action field of the section options reply record. When you receive this action code, you should open the document containing the publisher. First, use the GetEditionInfo function to find the edition container. Then use the GoToPublisherSection function to open the document containing the publisher.FUNCTION GoToPublisherSection                                 (container: EditionContainerSpec): OSErr;container    An edition container record, which specifies volume reference number, directory ID, and filename of the subscriber’s edition. You obtain the edition container by calling the GetEditionInfo function. DESCRIPTIONThe GoToPublisherSection function resolves the alias in the edition to find the document containing its publisher. In general, this function internally uses the GetStandardFormats function to get the alias to the publisher document and then resolves the alias. It next sends the Finder an Apple event to open the document (which launches its application if necessary) and, after the publisher is registered, sends a Section Scroll event to the publisher.As an optimization, if there is a registered publisher, the GoToPublisherSection function simply sends a Section Scroll event to the publisher. If the edition does not contain an alias and there are no registered publishers, then the GoToPublisherSection function sends an Open Documents event to open the edition to the creating application.If the edition container is not an edition file (as is the case when you are using bottlenecks to subscribe to non-edition files), the GoToPublisherSection function sends the Finder an Apple event to open that file. RESULT CODESnoErr    0    No error    fnfErr    –43    File not found    editionMgrInitErr    –450    Manager not initialized    badSubPartErr    –454    Invalid edition container    SEE ALSOFor illustrations of the section options dialog box for subscribers, see Figure 2-15 on page 2-44 and Figure 2-16 on page 2-45. For an example of responding to the action code 'goto', see Listing 2-8 beginning on page 2-46. For a description of the edition container record, see page 2-71.Edition Container FormatsThe Edition Manager calls the GetStandardFormats function to get the alias used in the GoToPublisherSection function and to get the preview shown in the subscriber dialog box. You probably do not need to call this function directly.GetStandardFormatsYou probably do not need to call the GetStandardFormats function directly because the Edition Manager calls this function.FUNCTION GetStandardFormats                     (container: EditionContainerSpec;                      VAR previewFormat: FormatType;                     preview, publisherAlias, formats: Handle): OSErr;container    An edition container record that specifies the edition volume reference number, directory ID, filename, and part.previewFormatThe GetStandardFormats function returns in this parameter a handle to the first format of the requested format type that it finds in the edition. preview    A format type. The GetStandardFormats function looks for a format of the type specified in this parameter and returns in this parameter the format type of the first format that it finds. The function tries to find one of four formats: 'prvw', 'PICT', 'TEXT', or 'snd '. publisherAliasThe publisherAlias parameter reads the format kPublisherDocAliasFormat ('alis').formats    The formats parameter reads the virtual format kFormatListFormat ('fmts'). DESCRIPTIONYou should pass in valid handles for the formats that you want and NIL for the formats that you don’t want. The handles are resized to the size of the data. If one of the requested formats cannot be found, GetStandardFormats returns a noTypeErr result code. RESULT CODESnoErr    0    No error    noTypeErr    –102    Edition container not found    editionMgrInitErr    –450    Manager not initialized    Reading and Writing Non-Edition FilesThe Edition Manager never opens or closes an edition container directly—it calls the current edition opener. See “Subscribing to Non-Edition Files” beginning on page 2-62 for additional information.To override the standard opener function, create an opener function that contains the following parameters:FUNCTION MyOpener (selector: EditionOpenerVerb;                         VAR PB: EditionOpenerParamBlock): OSErr;When this function is called by the Edition Manager, the selector parameter is set to one of the edition opener verbs (eoOpen, eoClose, eoOpenNew, eoCloseNew, eoCanSubscribe). The PB parameter contains an edition opener parameter block record.Use the GetEditionOpenerProc function to locate the current edition opener and use the SetEditionOpenerProc function to provide your own edition opener. Use the CallEditionOpenerProc function to call an edition opener and use the CallFormatIOProc function to call a format I/O function.GetEditionOpenerProcUse the GetEditionOpenerProc function to locate the current edition opener.FUNCTION GetEditionOpenerProc                            (VAR opener: EditionOpenerProcPtr): OSErr;opener    The GetEditionOpenerProc function returns a pointer to the current edition opener function in this parameter.SetEditionOpenerProcUse the SetEditionOpenerProc function to provide your own edition opener.FUNCTION SetEditionOpenerProc                             (opener: EditionOpenerProcPtr): OSErr;opener    A pointer to the edition opener function that you are providing.CallEditionOpenerProcUse the CallEditionOpenerProc function to call an edition opener.FUNCTION CallEditionOpenerProc                             (selector: EditionOpenerVerb;                              VAR PB: EditionOpenerParamBlock;                             routine: EditionOpenerProcPtr): OSErr;selector    An edition opener verb. When the CallEditionOpenerProc function is called by the Edition Manager, the selector parameter is set to one of the edition opener verbs (eoOpen, eoClose, eoOpenNew, eoCloseNew, eoCanSubscribe). PB    An edition opener parameter block. routine    A pointer to an edition opener function.DESCRIPTIONThe Edition Manager calls an edition opener function whenever it needs to open or close an edition. The Edition Manager passes an edition opener parameter block as one of the parameters to an edition opener function. The edition opener parameter block is defined by this structure:TYPE EditionOpenerParamBlock =     RECORD        info:                    EditionInfoRecord;                            {edition container to }                                                        { be subscribed to}        sectionH:                    SectionHandle;                            {publisher or }                                                        { subscriber }                                                        { requesting open}        document:                    FSSpecPtr;                            {document passed}        fdCreator:                    OSType;                            {Finder creator type}        ioRefNum:                    LongInt;                            {reference number}        ioProc:                    FormatIOProcPtr;                            {routine to read }                                                        { formats}        success:                    Boolean;                            {reading or writing }                                                        { was successful}        formatsMask:                    SignedByte;                            {formats required to }                                                        { subscribe}    END;To override the standard reading and writing functions, you should create an I/O function that contains the following parameters.FUNCTION MyIO (selector: FormatIOVerb;                     VAR PB: FormatIOParamBlock): OSErr;Set the selector parameter to one of the format I/O verbs (ioHasFormat, ioReadFormat, ioNewFormat, ioWriteFormat). The PB parameter contains a format I/O parameter block record.SEE ALSOSee “Calling an Edition Opener” beginning on page 2-64 for additional information.CallFormatIOProcUse the CallFormatIOProc function to call a format I/O function.FUNCTION CallFormatIOProc (selector: FormatIOVerb;                                     VAR PB:FormatIOParamBlock;                                     routine: FormatIOProcPtr): OSErr;selector    A format I/O verb (ioHasFormat, ioReadFormat, ioNewFormat, ioWriteFormat). PB    A format I/O parameter block record.routine    A pointer to a format I/O function. DESCRIPTIONThe Edition Manager calls a format I/O function whenever it needs to read from or write to an edition. The Edition Manager passes a format I/O parameter block as one of the parameters to a format I/O procedure. The format I/O parameter block is defined by this structure:TYPE FormatIOParamBlock =     RECORD        ioRefNum:                    LongInt;                    {reference number}        format:                    FormatType;                    {edition format type}        formatIndex:                    LongInt;                    {opener-specific enumeration }                                                 { of formats}        offset:                    LongInt;                    {offset into format}        buffPtr:                    Ptr;                    {data starts here}        buffLen:                    LongInt;                    {length of data}    END;SEE ALSOSee “Calling a Format I/O Function” beginning on page 2-68 for additional information.Application-Defined RoutinesYour application can provide an edition opener function, format I/O function, expandable dialog hook function, and expandable modal-dialog filter function. For the routine declarations of the edition opener and format I/O functions, see “Reading and Writing Non-Edition Files” beginning on page 2-102. For the routine declarations of the expandable dialog hook and expandable modal-dialog filter functions, see the description of NewSubscriberExpDialog, NewPublisherExpDialog, and SectionOptionsExpDialog beginning on page 2-96. Summary of the Edition ManagerPascal SummaryConstantsCONST            {resource types}    rSectionType                                        = 'sect';                {resource type for a }                                                            { section}    {section types}    stSubscriber                                        = $01;                {subscriber section type}    stPublisher                                        = $0A;                {publisher section type}     {update modes}    sumAutomatic                                        = 0;                {subscriber receives new }                                                             { editions automatically}    sumManual                                        = 1;                {subscriber receives new }                                                             { editions manually}    pumOnSave                                        = 0;                {publisher sends new }                                                             { editions on save}    pumManual                                        = 1;                {publisher does not send }                                                             { new editions until user }                                                            { request}    {edition container subpart number}    kPartsNotUsed                                        = 0;                {edition is the whole file}    kPartNumberUnknown                                        = -1;                {not used in version 7.0}     {preview size}    kPreviewWidth                                        = 120;                {preview width}     kPreviewHeight                                        = 120;                {preview height}    {special formats}    kPublisherDocAliasFormat                                        = 'alis';                {alias record from the }                                                             { edition to publisher}     kPreviewFormat                                        = 'prvw';                {'PICT' thumbnail sketch}    kFormatListFormat                                        = 'fmts';                {list of all available }                                                            { formats and their sizes}    {bits for formatMask}    kPICTformatMask                                        = 1;                {graphics format}    kTEXTformatMask                                        = 2;                {text format}    ksndFormatMask                                        = 4;                {sound format}    {Finder types for edition files}    kPICTEditionFileType                                        = 'edtp';                {contains 'PICT', }    kTEXTEditionFileType                                        = 'edtt';                { 'TEXT', and }    ksndEditionFileType                                        = 'edts';                { 'snd ' file types}    kUnknownEditionFileType                                        = 'edtu';                {unknown file type}    {miscellaneous}    kFormatLengthUnknown                                        = -1;                    {length of format unknown}    {message IDs for Apple events sent by the Edition Manager}    sectionEventMsgClass                                        = 'sect';                {Apple events sent by the }                                                            { Edition Manager}    sectionReadMsgID                                        = 'read';                {Section Read events}    sectionWriteMsgID                                        = 'writ';                {Section Write events}    sectionScrollMsgID                                        = 'scrl';                {Section Scroll events}    sectionCancelMsgID                                        = 'cncl';                {Section Cancel events}    {refCon field when displaying stacked dialog boxes}    sfMainDialogRefCon                                        = 'stdf';                {new publisher and }                                                            { new subscriber}    sfNewFolderDialogRefCon                                        = 'nfdr';                {new folder}    sfReplaceDialogRefCon                                        = 'rplc';                {replace dialog}    sfStatWarnDialogRefCon                                        = 'stat';                {warning dialog}    sfErrorDialogRefCon                                        = 'err ';                {error dialog}    emOptionsDialogRefCon                                        = 'optn';                {options dialog}    emCancelSectionDialogRefCon                                        = 'cncl';                {cancel section}    emGotoPubErrDialogRefCon                                        = 'gerr';                {locate publisher}    {pseudo-item hits for dialogHooks}    emHookRedrawPreview                                        = 150;                {for NewPublisher or }                                                            { NewSubscriber dialogs}    emHookCancelSection                                        = 160;                {for SectionOptions dialog}    emHookGoToPublisher                                        = 161;                {for SectionOptions dialog}    emHookGetEditionNow                                        = 162;                {for SectionOptions dialog}    emHookSendEditionNow                                        = 162;                {for SectionOptions dialog}    emHookManualUpdateMode                                        = 163;                {for SectionOptions dialog}    emHookAutoUpdateMode                                        = 164;                {for SectionOptions dialog}Data TypesTYPE TimeStamp                                            = LongInt;                    {seconds since 1904}    EditionRefNum                                         = Handle;                     {for use in Edition I/O}    UpdateMode                                         = Integer;                    {sumAutomatic, }                                                                { sumManual, }                                                                 { pumOnSave, pumManual}    SectionType                                         = SignedByte;                    {stSubscriber or }                                                                { stPublisher}     FormatType                                         = PACKED ARRAY[1..4] OF CHAR;                                                                 {similar to ResType used }                                                                 { by the Scrap Manager}    SectionHandle                                        = ^SectionPtr;    SectionPtr                                        = ^SectionRecord;    SectionRecord                                         =     RECORD        version:                                    SignedByte;                    {always 1 in version 7.0}        kind:                                    SectionType;                    {publisher or subscriber}        mode:                                    UpdateMode;                    {automatic or manual}        mdDate:                                    TimeStamp;                    {last change to section}        sectionID:                                    LongInt;                    {application-specific, }                                                                { unique per document}        refCon:                                    LongInt;                    {application-specific}        alias:                                    AliasHandle;                    {handle to alias record}        {The following fields are private and are set up by the }        { RegisterSection function.}        subPart:                                    LongInt;                    {private}        nextSection:                                    SectionHandle;                    {private}        controlBlock:                                    Handle;                    {private}        refNum:                                    EditionRefNum;                    {private}    END;    EditionContainerSpecPtr =^EditionContainerSpec;    EditionContainerSpec =    RECORD        theFile:                                    FSSpec;                    {file containing edition }                                                                 { data}        theFileScript:                                     ScriptCode;                    {script code of filename}        thePart:                                    LongInt;                    {which part of file, }                                                                 { always kPartsNotUsed}        thePartName:                                    Str31;                    {reserved}        thePartScript:                                     ScriptCode;                    {reserved}    END;    FormatsAvailable = ARRAY[0..0] OF    RECORD        theType:                                    FormatType;                    {format type for an }                                                                { edition}        theLength:                                    LongInt;                    {length of edition format }                                                                { type}    END;    EditionInfoRecord =     RECORD        crDate:                                    TimeStamp;                    {date edition container }                                                                { was created}        mdDate:                                    TimeStamp;                    {date of last change}        fdCreator:                                    OSType;                    {file creator}        fdType:                                    OSType;                    {file type}        container:                                    EditionContainerSpec;                                                                {the edition}    END;    NewPublisherReply =     RECORD        canceled:                        Boolean;                            {user canceled dialog box}         replacing:                        Boolean;                            {user chose existing }                                                             { filename for an edition}        usePart:                        Boolean;                            {always FALSE in version 7.0}        preview:                        Handle;                            {handle to 'prvw', 'PICT',}                                                            { 'TEXT', or 'snd ' data}        previewFormat:                        FormatType;                            {type of preview}        container:                        EditionContainerSpec;                                                            {edition chosen}    END;    NewSubscriberReply =    RECORD        canceled:                        Boolean;                            {user canceled dialog box}        formatsMask:                        SignedByte;                            {formats required}        container:                         EditionContainerSpec;                                                            {edition selected}    END;    SectionOptionsReply =    RECORD        canceled:                        Boolean;                            {user canceled dialog box}        changed:                         Boolean;                            {changed the section }                                                            { record}        sectionH:                        SectionHandle;                            {handle to the specified }                                                            { section record}        action:                        ResType;                            {action codes}    END;    EditionOpenerVerb    = (eoOpen, eoClose, eoOpenNew, eoCloseNew,                                eoCanSubscribe);     EditionOpenerParamBlock =     RECORD        info:                        EditionInfoRecord;                            {edition container to }                                                            { be subscribed to}        sectionH:                        SectionHandle;                            {publisher or subscriber }                                                            { requesting open}        document:                        FSSpecPtr;                            {document passed}        fdCreator:                        OSType;                            {Finder creator type}        ioRefNum:                        LongInt;                            {reference number}        ioProc:                        FormatIOProcPtr;                            {routine to read formats}        success:                        Boolean;                            {reading or writing was }                                                            { successful}        formatsMask:                        SignedByte;                            {formats required to }                                                            { subscribe}    END;    FormatIOVerb     = (ioHasFormat, ioReadFormat, ioNewFormat, ioWriteFormat);    FormatIOParamBlock =     RECORD        ioRefNum:                        LongInt;                            {reference number}        format:                        FormatType;                            {edition format type}        formatIndex:                        LongInt;                            {opener-specific enumeration }                                                            { of formats}        offset:                        LongInt;                            {offset into format}        buffPtr:                        Ptr;                            {data starts here}        buffLen:                        LongInt;                            {length of data}END;Edition Manager RoutinesInitializing the Edition ManagerFUNCTION InitEditionPack     : OSErr;Creating and Registering a SectionFUNCTION NewSection    (container: EditionContainerSpec; sectionDocument: FSSpecPtr; kind: SectionType; sectionID: LongInt; initialMode: UpdateMode; VAR sectionH: SectionHandle): OSErr;FUNCTION RegisterSection    (sectionDocument: FSSpec; sectionH: SectionHandle; VAR aliasWasUpdated: Boolean): OSErr;FUNCTION UnRegisterSection    (sectionH: SectionHandle): OSErr;FUNCTION IsRegisteredSection(sectionH: SectionHandle): OSErr;FUNCTION AssociateSection    (sectionH: SectionHandle; newSectionDocument: FSSpecPtr): OSErr;Creating and Deleting an Edition ContainerFUNCTION CreateEditionContainerFile(editionFile: FSSpec; fdCreator: OSType; editionFileNameScript: ScriptCode): OSErr;FUNCTION DeleteEditionContainerFile(editionFile: FSSpec): OSErr;Setting and Getting a Format MarkFUNCTION SetEditionFormatMark(whichEdition: EditionRefNum; whichFormat: FormatType; setMarkTo: LongInt): OSErr;FUNCTION GetEditionFormatMark(whichEdition: EditionRefNum; whichFormat: FormatType; VAR currentMark: LongInt): OSErr; Reading in Edition DataFUNCTION OpenEdition    (subscriberSectionH: SectionHandle; VAR refNum: EditionRefNum): OSErr;FUNCTION EditionHasFormat    (whichEdition: EditionRefNum; whichFormat: FormatType; VAR formatSize: Size): OSErr; FUNCTION ReadEdition    (whichEdition: EditionRefNum; whichFormat: FormatType; buffPtr: UNIV Ptr; VAR buffLen: Size): OSErr;Writing out Edition DataFUNCTION OpenNewEdition    (publisherSectionH: SectionHandle; fdCreator: OSType; publisherSectionDocument: FSSpecPtr; VAR refNum: EditionRefNum): OSErr;FUNCTION WriteEdition    (whichEdition: EditionRefNum; whichFormat: FormatType; buffPtr: UNIV Ptr; buffLen: Size): OSErr;Closing an Edition After Reading or WritingFUNCTION CloseEdition    (whichEdition: EditionRefNum; successful: Boolean): OSErr;Displaying Dialog BoxesFUNCTION GetLastEditionContainerUsed(VAR container: EditionContainerSpec): OSErr;FUNCTION NewSubscriberDialog(VAR reply: NewSubscriberReply): OSErr;FUNCTION NewPublisherDialog    (VAR reply: NewPublisherReply): OSErr;FUNCTION SectionOptionsDialog(VAR reply: SectionOptionsReply): OSErr;FUNCTION NewSubscriberExpDialog(VAR reply: NewSubscriberReply; where: Point; expansionDITLresID: Integer; dlgHook: ExpDlgHookProcPtr; filterProc: ExpModalFilterProcPtr; yourDataPtr: UNIV Ptr): OSErr;FUNCTION NewPublisherExpDialog(VAR reply: NewPublisherReply; where: Point; expansionDITLresID: Integer; dlgHook: ExpDlgHookProcPtr; filterProc: ExpModalFilterProcPtr; yourDataPtr: UNIV Ptr): OSErr;FUNCTION SectionOptionsExpDialog(VAR reply: SectionOptionsReply; where: Point; expansionDITLresID: Integer; dlgHook: ExpDlgHookProcPtr; filterProc: ExpModalFilterProcPtr; yourDataPtr: UNIV Ptr): OSErr;Locating a Publisher and Edition From a SubscriberFUNCTION GetEditionInfo    (sectionH: SectionHandle; VAR editionInfo: EditionInfoRecord): OSErr;FUNCTION GoToPublisherSection(container: EditionContainerSpec): OSErr;Edition Container FormatsFUNCTION GetStandardFormats    (container: EditionContainerSpec; VAR previewFormat: FormatType; preview, publisherAlias, formats: Handle): OSErr;Reading and Writing Non-Edition filesFUNCTION GetEditionOpenerProc(VAR opener: EditionOpenerProcPtr): OSErr;FUNCTION SetEditionOpenerProc(opener: EditionOpenerProcPtr): OSErr;FUNCTION CallEditionOpenerProc(selector: EditionOpenerVerb; VAR PB: EditionOpenerParamBlock; routine: EditionOpenerProcPtr): OSErr;FUNCTION CallFormatIOProc    (selector: FormatIOVerb; VAR PB: FormatIOParamBlock; routine: FormatIOProcPtr): OSErr;Application-Defined RoutinesFUNCTION MyExpDlgHook    (itemOffset: Integer; itemHit: Integer; theDialog: DialogPtr; yourDataPtr: Ptr): Integer;FUNCTION MyExpModalFilter    (theDialog: DialogPtr; VAR theEvent: EventRecord; itemOffset: Integer; VAR itemHit: Integer; yourDataPtr: Ptr): Boolean;FUNCTION MyOpener    (selector: EditionOpenerVerb; VAR PB: EditionOpenerParamBlock): OSErr;FUNCTION MyIO    (selector: FormatIOVerb; VAR PB: FormatIOParamBlock): OSErr;C SummaryConstantsCONST        enum {    /*resource types*/    #define rSectionType                                         'sect'                /*resource type for a */                                                            /* section*/    /*section types*/    stSubscriber                                        = 0x01,                /*subscriber section type*/    stPublisher                                        = 0x0A,                /*publisher section type*/     /*update modes*/    sumAutomatic                                        = 0,                /*subscriber receives new */                                                             /* editions automatically*/    sumManual                                        = 1,                /*subscriber receives new */                                                             /* editions manually*/    pumOnSave                                        = 0,                /*publisher sends new */                                                             /* editions on save*/    pumManual                                        = 1,                /*publisher does not send */                                                             /* new editions until user */                                                            /* request*/    /*edition container subpart number*/    kPartsNotUsed                                        = 0,                /*edition is the whole file*/    kPartNumberUnknown                                        = -1,                /*not used in version 7.0*/     /*preview size*/    kPreviewWidth                                        = 120,                /*preview width*/     kPreviewHeight                                        = 120,                /*preview height*/    /*special formats*/    #define kPublisherDocAliasFormat                                         'alis'                /*alias record from the */                                                             /* edition to publisher*/     #define kPreviewFormat                                            'prvw'            /*'PICT' thumbnail sketch*/    #define kFormatListFormat                                             'fmts'            /*list of all available */                                                            /* formats and their sizes*/    /*bits for formatMask*/    kPICTformatMask                                        = 1,                /*graphics format*/    kTEXTformatMask                                        = 2,                /*text format*/    ksndFormatMask                                        = 4,                /*sound format*/    /*Finder types for edition files*/    #define kPICTEditionFileType                                             'edtp'            /*contains 'PICT', */    #define kTEXTEditionFileType                                             'edtt'            /* 'TEXT', and */    #define ksndEditionFileType                                             'edts'            /* 'snd ' file types*/    #define kUnknownEditionFileType                                             'edtu'            /*unknown file type*/    /*pseudo-item hits for dialogHooks*/    emHookRedrawPreview                                        = 150,                /*for NewPublisher or */                                                            /* NewSubscriber dialogs*/    emHookCancelSection                                        = 160,                /*for SectionOptions dialog*/    emHookGoToPublisher                                        = 161,                /*for SectionOptions dialog*/    emHookGetEditionNow                                        = 162,                /*for SectionOptions dialog*/    emHookSendEditionNow                                        = 162,                /*for SectionOptions dialog*/    emHookManualUpdateMode                                        = 163,                /*for SectionOptions dialog*/    emHookAutoUpdateMode                                        = 164                /*for SectionOptions dialog*/};    /*edition opener verbs*/enum {eoOpen, eoClose, eoOpenNew, eoCloseNew, eoCanSubscribe};enum {    /*refCon field when displaying stacked dialog boxes*/    #define emOptionsDialogRefCon                                                 'optn'                /*options dialog*/    #define emCancelSectionDialogRefCon                                                 'cncl'                /*cancel section*/    #define emGotoPubErrDialogRefCon                                                 'gerr'                /*locate publisher*/    kFormatLengthUnknown                                        = -1                 /*length of format unknown*/};    /*refCon field when displaying stacked dialog boxes*/    #define sfMainDialogRefCon                                         'stdf'                {new publisher and }                                                            { new subscriber}    #define sfNewFolderDialogRefCon                                        'nfdr'                {new folder}    #define sfReplaceDialogRefCon                                         'rplc'                {replace dialog}    #define sfStatWarnDialogRefCon     'stat'                                                    {warning dialog}    #define sfErrorDialogRefCon                                         'err '                {error dialog}    /*message IDs for Apple events sent by the Edition Manager*/    #define sectionEventMsgClass                                         'sect'                /*Apple events sent by the */                                                            /* Edition Manager*/    #define sectionReadMsgID                                         'read'                /*Section Read events*/    #define sectionWriteMsgID                                         'writ'                /*Section Write events*/    #define sectionScrollMsgID                                         'scrl'                /*Section Scroll events*/    #define sectionCancelMsgID                                         'cncl'                /*Section Cancel events*/Data Typestypedef unsigned long TimeStamp;                                                            /*seconds since 1904*/typedef Handle EditionRefNum;                            ‘                                /*used in Edition I/O*/typedef short UpdateMode;                                                            /*update mode: sumAutomatic, */                                                            /* sumManual, */                                                             /* pumOnSave, pumManual*/typedef char SectionType;                                                            /*one byte, stSubscriber */                                                            /* or stPublisher*/ typedef unsigned long FormatType;                                                            /*similar to ResType*/struct SectionRecord {    SignedByte version;                                                        /*always 1x01 in version 7.0*/    SectionType kind;                                                        /*stPublisher or */                                                            /* stSubscriber*/    UpdateMode mode;                                                        /*automatic or manual*/    TimeStamp mdDate;                                                        /*last change to section*/    long sectionID;                                                        /*application-specific, */                                                            /* unique per document*/    long refCon;                                                        /*application-specific*/    AliasHandle alias;                                                        /*handle to alias record*/    long subPart;                                                        /*private*/    struct SectionRecord **nextSection;                                                        /*private*/    Handle controlBlock;                                                        /*private*/    EditionRefNum refNum;                                                        /*private*/};typedef struct SectionRecord SectionRecord;typedef SectionRecord *SectionPtr, **SectionHandle;struct EditionContainerSpec {    FSSpec theFile;                                                        /*file containing */                                                             /* edition data*/    ScriptCode theFileScript;                                                         /*script code of filename*/    long thePart;                                                        /*which part of file, */                                                             /* always kPartsNotUsed*/    Str31 thePartName;                                                        /*reserved*/    ScriptCode thePartScript;                                                         /*reserved*/};typedef struct EditionContainerSpec EditionContainerSpec;typedef EditionContainerSpec *EditionContainerSpecPtr;struct EditionInfoRecord {    TimeStamp crDate;                                                    /*date edition container */                                                        /* was created*/    TimeStamp mdDate;                                                    /*date of last change*/    OSType fdCreator;                                                    /*file creator*/    OSType fdType;                                                    /*file type*/    EditionContainerSpec container;                                                    /*the edition*/};typedef struct EditionInfoRecord EditionInfoRecord;struct NewPublisherReply {    Boolean canceled;                                                    /*user canceled dialog box*/     Boolean replacing;                                                    /*user chose existing */                                                         /* filename for an edition*/    Boolean usePart;                                                    /*always FALSE in version */                                                         /* 7.0*/    Handle preview;                                                    /*handle to 'prvw', 'PICT',*/                                                        /* 'TEXT', or 'snd ' data*/    FormatType previewFormat;                                                    /*type of preview*/    EditionContainerSpec container;                                                    /*edition chosen*/};typedef struct NewPublisherReply NewPublisherReply;struct NewSubscriberReply {    Boolean canceled;                                                    /*user canceled dialog box*/    unsigned char formatsMask;                                                    /*formats required*/    EditionContainerSpec container;                                                     /*edition selected*/};typedef struct NewSubscriberReply NewSubscriberReply;struct SectionOptionsReply {    Boolean canceled;                                                    /*user canceled dialog box*/    Boolean changed;                                                     /*changed the section */                                                        /* record*/    SectionHandle sectionH;                                                    /*handle to the specified */                                                        /* section record*/    ResType action;                                                    /*action codes*/};typedef struct SectionOptionsReply SectionOptionsReply;typedef pascal Boolean (*ExpModalFilterProcPtr) (DialogPtr theDialog,                                                 EventRecord *theEvent, short itemOffset,                                                 short *itemHit, Ptr yourDataPtr);typedef pascal short (*ExpDlgHookProcPtr) (short itemOffset, short itemHit,                                                     DialogPtr theDialog, Ptr yourDataPtr);typedef unsigned char EditionOpenerVerb;    struct EditionOpenerParamBlock {    EditionInfoRecord info;                                                    /*edition container to */                                                        /* be subscribed to*/    SectionHandle sectionH;                                                    /*publisher or subscriber */                                                        /* requesting open*/    FSSpecPtr document;                                                    /*document passed*/    OSType fdCreator;                                                    /*Finder creator type*/    long ioRefNum;                                                    /*reference number*/    FormatIOProcPtr ioProc;                                                    /*routine to read formats*/    Boolean success;                                                    /*reading or writing was */                                                        /* successful*/    unsigned char formatsMask;                                                    /*formats required to */                                                        /* subscribe*/};typedef struct EditionOpenerParamBlock EditionOpenerParamBlock;typedef pascal short (*EditionOpenerProcPtr) (EditionOpenerVerb selector,                                                            FormatIOParamBlock *PB);enum {ioHasFormat, ioReadFormat, ioNewFormat, ioWriteFormat};typedef unsigned char FormatIOVerb;struct FormatIOParamBlock {    long ioRefNum;                                                    /*reference number*/    FormatType format;                                                    /*edition format type*/    long formatIndex;                                                    /* opener-specific */                                                         /* enumeration */                                                        /* of formats*/    unsigned long offset;                                                    /*offset into format*/    Ptr buffPtr;                                                    /*data starts here*/    unsigned long buffLen;                                                    /*length of data*/};typedef struct FormatIOParamBlock FormatIOParamBlock;typedef pascal short (*FormatIOProcPtr) (FormatIOVerb selector,                                                    FormatIOParamBlock *PB);Edition Manager RoutinesInitializing the Edition Managerpascal OSErr InitEditionPack    (void)Creating and Registering a Sectionpascal OSErr NewSection    (const EditionContainerSpec *container,const FSSpec *sectionDocument,SectionType kind, long sectionID,UpdateMode initialMode,SectionHandle *sectionH);pascal OSErr RegisterSection(const FSSpec *sectionDocument,SectionHandle sectionH,Boolean *aliasWasUpdated);pascal OSErr UnRegisterSection(SectionHandle sectionH);pascal OSErr IsRegisteredSection(SectionHandle sectionH);pascal OSErr AssociateSection(SectionHandle sectionH,const FSSpec *newSectionDocument);Creating and Deleting an Edition Containerpascal OSErr CreateEditionContainerFile(const FSSpec *editionFile, OSType fdCreator, ScriptCode editionFileNameScript);pascal OSErr DeleteEditionContainerFile(const FSSpec *editionFile);Setting and Getting a Format Markpascal OSErr SetEditionFormatMark(EditionRefNum whichEdition,FormatType whichFormat,unsigned long setMarkTo);pascal OSErr GetEditionFormatMark(EditionRefNum whichEdition,FormatType whichFormat,unsigned long *currentMark);Reading in Edition Datapascal OSErr OpenEdition    (SectionHandle subscriberSectionH, EditionRefNum *refNum);pascal OSErr EditionHasFormat(EditionRefNum whichEdition,FormatType whichFormat,Size *formatSize);pascal OSErr ReadEdition    (EditionRefNum whichEdition,FormatType whichFormat, void *buffPtr,Size *buffLen);Writing out Edition Datapascal OSErr OpenNewEdition    (SectionHandle publisherSectionH,OSType fdCreator,const FSSpec *publisherSectionDocument,EditionRefNum *refNum);pascal OSErr WriteEdition    (EditionRefNum whichEdition,FormatType whichFormat, const void *buffPtr, Size *buffLen);Closing an Edition After Reading or Writingpascal OSErr CloseEdition    (EditionRefNum whichEdition,Boolean successful);Displaying Dialog Boxespascal OSErr GetLastEditionContainerUsed(EditionContainerSpec *container);pascal OSErr NewSubscriberDialog(NewSubscriberReply *reply);pascal OSErr NewPublisherDialog(NewPublisherReply *reply);pascal OSErr SectionOptionsDialog(SectionOptionsReply *reply);pascal OSErr NewSubscriberExpDialog(NewSubscriberReply *reply, Point where,short expansionDITLresID,ExpDlgHookProcPtr dlgHook,ExpModalFilterProcPtr filterProc,void *yourDataPtr);pascal OSErr NewPublisherExpDialog(NewPublisherReply *reply, Point where,short expansionDITLresID,ExpDlgHookProcPtr dlgHook,ExpModalFilterProcPtr filterProc,void *yourDataPtr);pascal OSErr SectionOptionsExpDialog(SectionOptionsReply *reply, Point where, short expansionDITLresID,ExpDlgHookProcPtr dlgHook,ExpModalFilterProcPtr filterProc,void *yourDataPtr);Locating a Publisher and Edition From a Subscriberpascal OSErr GetEditionInfo    (const SectionHandle sectionH,EditionInfoRecord *editionInfo);pascal OSErr GoToPublisherSection(const EditionContainerSpec *container);Edition Container Formatspascal OSErr GetStandardFormats(const EditionContainerSpec *container,FormatType *previewFormat,Handle preview, Handle publisherAlias,Handle formats);Reading and Writing Non-Edition filespascal OSErr GetEditionOpenerProc(EditionOpenerProcPtr *opener);pascal OSErr SetEditionOpenerProc(EditionOpenerProcPtr opener);pascal OSErr CallEditionOpenerProc(EditionOpenerVerb selector,EditionOpenerParamBlock *PB,EditionOpenerProcPtr routine);pascal OSErr CallFormatIOProc(FormatIOVerb selector,FormatIOParamBlock *PB,FormatIOProcPtr routine);Application-Defined Routinespascal OSErr MyExpDlgHook    (short itemOffset, short itemHit,DialogPtr theDialog,Ptr yourDataPtr);pascal OSErr MyExpModalFilter(DialogPtr theDialog,EventRecord *theEvent,short itemOffset, short *itemHit, Ptr yourDataPtr);pascal OSErr MyOpener    (EditionOpenerVerb selector,EditionOpenerParamBlock *PB);pascal OSErr MyIO    (FormatIOVerb selector,FormatIOParamBlock *PB);Result CodesnoErr    0    No error    abortErr    –27    Publisher has written a new edition    dskFulErr    –34    Disk is full    nsvErr    –35    No such volume    ioErr    –36    I/O error    bdNamErr    –37    Bad filename    fnOpnErr    –38    File not open    eofErr    –39    No additional data in the format    fnfErr    –43    Edition container not found    flLckedErr    –45    Publisher writing to an edition    fBsyErr    –47    Section doing I/O    paramErr    –50    Invalid parameter    rfNumErr    –51    Bad edition reference number    permErr    –54    Not a subscriber    wrPermErr    –61    Not a publisher    noTypeErr    –102    Format not available    memFullErr    –108    Memory full    dirNFErr    –120    Directory not found    userCanceledErr    –128    User clicked Cancel in dialog box    editionMgrInitErr    –450    Manager not initialized or could not load package    badSectionErr    –451    Not a valid section type    notRegisteredSectionErr    –452    Not registered    badSubPartErr    –454    Bad edition container spec or invalid edition container    multiplePublisherWrn    –460    Already is a publisher    containerNotFoundWrn    –461    Alias was not resolved    notThePublisherWrn    –463    Not the publisher    Listing 3-0Table 3-0Introduction to Apple EventsContentsAbout Apple Events3-3Apple Events and Apple Event Objects3-6Apple Event Attributes and Parameters3-7Apple Event Attributes3-8Apple Event Parameters3-9Interpreting Apple Event Attributes and Parameters3-10Data Structures Within Apple Events3-12Descriptor Records3-12Keyword-Specified Descriptor Records3-15Descriptor Lists3-16Responding to Apple Events3-20Accepting and Processing Apple Events3-20About Apple Event Handlers3-23Extracting and Checking Data3-23Interacting With the User3-25Performing the Requested Action and Returning a Result3-25Creating and Sending Apple Events3-28Creating an Apple Event Record3-29Adding Apple Event Attributes and Parameters3-29Sending an Apple Event and Handling the Reply3-30Working With Object Specifier Records3-32Data Structures Within an Object Specifier Record3-34The Classification of Apple Event Objects3-39Object Classes3-39Properties and Elements3-42Finding Apple Event Objects3-46About the Apple Event Manager3-48Supporting Apple Events as a Server Application3-48Supporting Apple Events as a Client Application3-49Supporting Apple Event Objects3-49Supporting Apple Event Recording3-50Introduction to Apple EventsThis chapter introduces Apple events and the Apple Event Manager. Later chapters describe how your application can use the Apple Event Manager to respond to and send Apple events, locate Apple event objects, and record Apple events.The interapplication communication (IAC) architecture for Macintosh computers consists of five parts: the Edition Manager, the Open Scripting Architecture (OSA), the Apple Event Manager, the Event Manager, and the Program-to-Program Communications (PPC) Toolbox. The chapter “Introduction to Interapplication Communication” in this book provides an overview of the relationships among these parts. The Apple Event Registry: Standard Suites defines both the actions performed by the standard Apple events, or “verbs,” and the standard Apple event object classes, which can be used to create “noun phrases” describing objects on which Apple events act. If your application uses the Apple Event Manager to respond to some of these standard Apple events, you can make it scriptable—that is, capable of responding to scripts written in a scripting language such as AppleScript. In addition, your application can use the Apple Event Manager to create and send Apple events and to allow user actions in your application to be recorded as Apple events.Before you use this chapter or any of the other chapters about the Apple Event Manager, you should be familiar with the chapters “Event Manager” in Inside Macintosh: Macintosh Toolbox Essentials and “Process Manager” in Inside Macintosh: Processes. This chapter begins by describing Apple events and some of the data structures they contain. The rest of the chapter introduces the use of the Apple Event Manager ton    respond to Apple eventsn    send Apple events to request services or informationn    work with object specifier recordsn    classify Apple event objects n    locate Apple event objectsFinally, this chapter summarizes the tasks you can perform with the Apple Event Manager and explains where to locate information you need to perform those tasks.About Apple EventsAn Apple event is a high-level event that conforms to the Apple Event Interprocess Messaging Protocol. The Apple Event Manager uses the services of the Event Manager to send Apple events between applications on the same computer, between applications on remote computers, or from an application to itself.Applications typically use Apple events to request services and information from other applications or to provide services and information in response to such requests. Communication between two applications that support Apple events is initiated by a client application, which sends an Apple event to request a service or information. The application providing the service or the requested information is called a server application. The client and server applications can reside on the same local computer or on remote computers connected to a network. An application can also send Apple events to itself, thus acting as both client and server.   Figure 3-1 shows a common Apple event, the Open Documents event. The Finder is the client; it requests that the SurfWriter application open the documents named “Dec. Invoice” and “Nov. Invoice.” The SurfWriter application responds to the Finder’s request by opening windows for the specified documents.Figure 3-1    An Open Documents eventThe Finder is considered the client application for the Open Documents event shown in Figure 3-1 because the Finder initiates the request for a service. The Finder can also be considered the source application for the same Open Documents event. A source application for an Apple event is one that sends an Apple event to another application or to itself. Similarly, the SurfWriter application can be described as either the server application or the target application for the Open Documents event shown in Figure 3-1. A target application for an Apple event is the one addressed to receive the Apple event. The terms client application and source application are not always synonymous, nor are the terms server application and target application. Typically, an Apple event client application sends an Apple event requesting a service to an Apple event server application; in this case, the server application is the target application for the Apple event. A server application may return information to the client in a reply Apple event—in which case, the client application is the target application for the reply.  To perform the requested service—that is, to open the specified documents—the SurfWriter application shown in Figure 3-1 first uses the Apple Event Manager to identify the event (the Open Documents event) and to dispatch the event to SurfWriter’s handler for that Apple event. An Apple event handler is an application-defined function that extracts pertinent data from an Apple event, performs the requested action, and (usually) returns a result. In this case, SurfWriter’s Open Documents event handler examines the Apple event to determine which documents to open (Dec. Invoice and Nov. Invoice), then opens them as requested. To identify Apple events and respond appropriately, every application can rely on a vocabulary of standard Apple events that developers and Apple have established for all applications to use. These events are defined in the Apple Event Registry: Standard Suites. The standard suites, or groups of related Apple events that are usually implemented together, include the Required suite, the Core suite, and functional-area suites such as the Text suite and the Database suite. To function as a server application, your application should be able to respond to all the Apple events in the Required suite and any of those in the Core and functional-area suites that it is likely to receive. For example, most word-processing applications should be capable of responding to the Apple events in the Text suite, and most database applications should be capable of responding to those in the Database suite. If necessary, you can extend the definitions of the standard Apple events to match specific capabilities of your application. You can also define your own custom Apple events; however, before defining custom events, you should check with the Apple Event Registrar to find out whether you can adapt existing Apple event definitions or definitions still under development to the needs of your application. By supporting the standard Apple events in your application, you ensure that your application can communicate effectively with other applications that also support them. Instead of supporting many different custom events for a limited number of applications, you can support a relatively small number of standard Apple events that can be used by any number of applications. You can begin supporting Apple events by making your application a reliable server application: first for the required Apple events, then for the core and functional-area Apple events as appropriate. Once your application can respond to the appropriate standard Apple events, you can make it scriptable, or capable of responding to instructions written in a system-wide scripting language such as AppleScript. If necessary, your application can also send Apple events to itself or to other applications.“About the Apple Event Manager,” which begins on page 3-48, provides more information about the steps you need to take to support Apple events in your application. The next section, “Apple Events and Apple Event Objects,” describes how Apple events can describe data and other items within an application or its documents. Subsequent sections describe the basic organization of Apple events and the data structures from which they are constructed. Apple Events and Apple Event ObjectsThe Open Documents event shown in Figure 3-1, like the other three required events, specifies an action and the applications or documents to which that action applies. The Apple Event Registry: Standard Suites provides a vocabulary of actions for use by all applications. In addition to a vocabulary of actions, effective communication between applications requires a method of referring to windows, data (such as words or graphic elements), files, folders, volumes, zones, and other discrete items on which actions can be performed. The Apple Event Manager includes routines that allow any application to construct or interpret “noun phrases” that describe the objects on which Apple events act.Most of the Apple event definitions in the Apple Event Registry: Standard Suites include definitions of Apple event object classes, which are simply names for objects that can be acted upon by each kind of Apple event. An Apple event object is any distinct item supported by an application that can be described within an Apple event. Apple event objects can be anything that an application can locate on the basis of such a description, including items that a user can differentiate and manipulate while using an application, such as words, paragraphs, shapes, windows, or style formats. The definition for each Apple event object class in the Apple Event Registry: Standard Suites determines only how that kind of Apple event object should be described within an Apple event, not how it should be represented internally by an individual application. You do not have to write your application in an object-oriented programming language to support Apple event objects. Instead, you need to organize your application so that it can interpret a request for specific Apple event objects, locate the objects, and perform the requested action on them.Figure 3-2 shows a common Apple event, the Get Data event from the Core suite. In this example, the SurfCharter application is the client application; it requests data contained in a specific table in a SurfWriter document. To obtain the data it wants, the SurfCharter application must include a description of the data in the Get Data event it sends to SurfWriter. This description identifies the requested data as an Apple event object called a table. The table is named “Summary of Sales” and is located in a document named “Sales Report.” The SurfWriter application’s Get Data handler extracts information about the request, locates the specified table, and returns a result. The Apple Event Manager provides a reply Apple event to which the SurfWriter application adds the requested information in the form requested by the Get Data event. The Apple Event Manager sends the reply event back to the SurfCharter application, which can use the requested data in whatever way is appropriate—in this case, displaying it as a pie chart.Figure 3-2    A Get Data eventApple Event Attributes and ParametersWhen an application creates and sends an Apple event, the Apple Event Manager uses arguments passed to Apple Event Manager routines to construct the data structures that make up the Apple event. An Apple event consists of attributes (which identify the Apple event and denote its task) and, often, parameters (which contain information to be used by the target application). An Apple event attribute is a record that identifies the event class, event ID, target application, or some other characteristic of an Apple event. Taken together, the attributes of an Apple event denote the task to be performed on any data specified in the Apple event’s parameters. A client application can use Apple Event Manager routines to add attributes to an Apple event. After receiving an Apple event, a server application can use Apple Event Manager routines to extract and examine its attributes. An Apple event parameter is a record containing data that the target application uses. Unlike Apple event attributes (which contain information that can be used by both the Apple Event Manager and the target application), Apple event parameters contain data used only by the target application. For example, the Apple Event Manager uses the event class and event ID attributes to identify the server application’s handler for a specific Apple event, and the server application must have a handler to process the event identified by those attributes. By comparison, the list of documents contained in a parameter to an Open Documents event is used only by the server application. As with attributes, a client application can use Apple Event Manager routines to add parameters to an Apple event, and a server application can use Apple Event Manager routines to extract and examine the parameters of an Apple event it has received.Note that Apple event parameters are different from the parameters of Apple Event Manager functions. Apple event parameters are records used by the Apple Event Manager; function parameters are arguments you pass to the function or that the function returns to you. You can specify both Apple event parameters and Apple event attributes in parameters to Apple Event Manager functions. For example, the AEGetParamPtr function uses a buffer to return the data contained in an Apple event parameter. You can specify the Apple event parameter whose data you want in one of the parameters of the AEGetParamPtr function.Apple Event AttributesApple events are identified by their event class and event ID attributes. The event class is the attribute that identifies a group of related Apple events. The event class appears in the message field of the event record for an Apple event. For example, the four required Apple events have the value 'aevt' in the message fields of their event records. The value 'aevt' can also be represented by the kCoreEventClass constant. Several event classes are shown here:Event class    Value    Description    kCoreEventClass    'aevt'    A required Apple event    kAECoreSuite    'core'    A core Apple event    kAEFinderEvents    'FNDR'    An event that the Finder accepts    kSectionEventMsgClass    'sect'    An event sent by the Edition Manager    The event ID is the attribute that identifies the particular Apple event within its event class. In conjunction with the event class, the event ID uniquely identifies the Apple event and communicates what action the Apple event should perform. (The event IDs appear in the where field of the event record for an Apple event. For more information about event records, see the chapter “Event Manager” in Inside Macintosh: Macintosh Toolbox Essentials.) For example, the event ID of an Open Documents event has the value 'odoc' (which can also be represented by the kAEOpenDocuments constant). The kCoreEventClass constant in combination with the kAEOpenDocuments constant identifies the Open Documents event to the Apple Event Manager.Here are the event IDs for the four required Apple events:Event ID    Value    Description    kAEOpenApplication    'oapp'    Perform tasks required when a user opens your application without opening or printing any documents    kAEOpenDocuments    'odoc'    Open documents    kAEPrintDocuments    'pdoc'    Print documents    kAEQuitApplication    'quit'    Quit your application    In addition to the event class and event ID attributes, every Apple event must include an attribute that specifies the target application’s address. Remember that the target application is the one addressed to receive the Apple event. Your application can send an Apple event to itself or to another application (on the same computer or on a remote computer connected to the network).Every Apple event must include event class, event ID, and target address attributes. Some Apple events can include other attributes; see “Keyword-Specified Descriptor Records,” which begins on page 3-15, for a complete list.Apple Event ParametersAs with attributes, there are various kinds of Apple event parameters. A direct parameter usually specifies the data to be acted upon by the target application. For example, the direct parameter of the Print Documents event contains a list of documents. Some Apple events also take additional parameters, which the target application uses in addition to the data specified in the direct parameter. Thus, an Apple event for arithmetic operations might include additional parameters that specify operands in an equation. The Apple Event Registry: Standard Suites describes all parameters as either required or optional. A required parameter is one that must be present for the target application to carry out the task denoted by the Apple event. An optional parameter is a supplemental Apple Event parameter that also can be used to specify data to the target application. Optional parameters need not be included in an Apple event; default values for optional parameters are part of the event definition. The target application that handles the event must supply default values if the optional parameters are omitted.  Direct parameters are usually defined as required parameters in the Apple Event Registry: Standard Suites; additional parameters may be defined as either required or optional. However, the Apple Event Manager does not enforce the definitions of required and optional events. Instead, the source application specifies, when it sends the event, which Apple event parameters the target can treat as if they were optional.For more information about optional parameters, see “Specifying Optional Parameters for an Apple Event,” which begins on page 5-7.Interpreting Apple Event Attributes and ParametersFigure 3-3 shows the major Apple event attributes and direct parameter for the Open Documents event introduced in Figure 3-1.Figure 3-3    Major attributes and direct parameter of an Open Documents eventWhen the SurfWriter application receives any high-level event, it calls the AEProcessAppleEvent function to process the event. For an Apple event such as the Open Documents event shown in Figure 3-3, the AEProcessAppleEvent function uses the event class and event ID attributes to dispatch the event to the SurfWriter application’s Open Documents handler. In response, the Open Documents handler opens the documents specified in the direct parameter. The definition of a given Apple event in the Apple Event Registry: Standard Suites suggests how the source application can organize the data in the Apple event’s parameters and how the target application interprets that data. The data in an Apple event parameter may use standard or private data types and may include a description of an Apple event object. Each Apple event handler provided by an application should be written with the format of the expected data in mind.Apple events can use standard data types, such as strings of text, long integers, Boolean values, and alias records, for the corresponding data in Apple event parameters. For example, the Get Data event can contain an optional parameter specifying the form in which the requested data should be returned. This optional parameter always consists of a list of four-character codes denoting desired descriptor types in order of preference. Apple events can also use special data types defined by the Apple Event Manager. Apple event parameters often contain descriptions of Apple event objects. These descriptions make use of a standard classification scheme summarized in “The Classification of Apple Event Objects,” which begins on page 3-39.For example, every Get Data event includes a required parameter that describes the Apple event object containing the data requested by the client application. Thus, one application can send a Get Data event to another application, requesting, for instance, one paragraph of a document, the first and last paragraphs of a document, all pictures in the document, all paragraphs containing the word “sales,” or pages 10 through 12 of the document. Figure 3-4 shows the Apple event attributes and direct parameter for the Get Data event introduced in Figure 3-2. The direct parameter for the Get Data event sent by the SurfCharter application describes the requested Apple event object as a table called “Summary of Sales” in the document “Sales Report.” Both the table and the document are Apple event objects. The description of an Apple event object always includes a description of its location. In most cases, Apple event objects are located inside other Apple event objects.Figure 3-4    Major attributes and direct parameter of a Get Data eventTo process the information in the Get Data event, the SurfWriter application calls the AEProcessAppleEvent function. The AEProcessAppleEvent function uses the event class and event ID attributes to dispatch the event to the SurfWriter application’s handler for the Get Data Apple event. The SurfWriter application responds to the Get Data event by resolving the description of the Apple event object—that is, by using the AEResolve function, other Apple Event Manager routines, and its own application-defined functions to locate the table named “Summary of Sales.” After locating the table, SurfWriter adds a copy of the table’s data to the reply event, which the Apple Event Manager then sends to the SurfCharter application. The SurfCharter application then displays the data in its active window.  The next section, “Data Structures Within Apple Events,” describes the data structures the Apple Event Manager uses for Apple event attributes and parameters. Data Structures Within Apple EventsThe Apple Event Manager constructs its own internal data structures to contain the information in an Apple event. Neither the sender nor the receiver of an Apple event should manipulate data directly after it has been added to an Apple event; each should rely on Apple Event Manager functions to do so. This section describes the most important data structures used by the Apple event Manager to construct Apple events. The first structure described is the descriptor record, a data structure of type AEDesc. Applications may access the data in an individual descriptor record directly if it is not part of another Apple Event Manager data structure. In some cases it is convenient for the Apple Event Manager to describe descriptor records by data types that indicate their contents; thus, it also defines data structures such as type AEAddressDesc, AEDescList, and AERecord, which are descriptor records used to hold addresses, lists of other descriptor records, and Apple event parameters, respectively. These and most of the other data structures described in this section are formally defined as data structures of type AEDesc; they differ only in the purposes for which they are used.Descriptor RecordsDescriptor records are the building blocks used by the Apple Event Manager to construct Apple event attributes and parameters. A descriptor record is a data structure of type AEDesc; it consists of a handle to data and a descriptor type that identifies the type of the data to which the handle refers.TYPE AEDesc = RECORD                                            {descriptor record}    descriptorType:                        DescType;                {type of data}    dataHandle:                         Handle        ;        {handle to data}END;If a descriptor record exists separately from other Apple Event Manager data structures, it is possible to retrieve the data associated with its handle by dereferencing the handle twice. After a descriptor record has been added to any other Apple Event Manager data structure, you must use Apple Event Manager routines to extract data from the descriptor record.The descriptor type is a structure of type DescType, which in turn is of data type ResType—that is, a four-character code. Constants are usually used in place of these four-character codes when referring to descriptor types. Descriptor types represent various data types. Here are some of the major descriptor type constants, their values, and the kinds of data they identify.Descriptor type    Value    Description of data    typeBoolean    'bool'    1-byte Boolean value    typeChar    'TEXT'    Unterminated string    typeLongInteger    'long'    32-bit integer    typeShortInteger    'shor'    16-bit integer    typeMagnitude    'magn'    Unsigned 32-bit integer    typeAEList    'list'    List of descriptor records    typeAERecord    'reco'    List of keyword-specified descriptor records    typeAppleEvent    'aevt'    Apple event record    typeEnumerated    'enum'    Enumerated data    typeType    'type'    Four-character code     typeFSS    'fss '    File system specification    typeKeyword    'keyw'    Apple event keyword    typeNull    'null'    Nonexistent data (handle whose value is NIL)    For a complete list of the basic descriptor types used by the Apple Event Manager, see Table 4-2 on page 4-57.Figure 3-5 illustrates the logical arrangement of a descriptor record with a descriptor type of typeChar, which specifies that the data handle refers to an unterminated string (in this case, the text “Summary of Sales”).Figure 3-5    A descriptor record whose data handle refers to an unterminated stringFigure 3-6 illustrates the logical arrangement of a descriptor record with a descriptor type of typeType, which specifies that the data handle refers to a four-character code (in this case the constant kCoreEventClass, whose value is 'aevt'). This descriptor record can be used in an Apple event attribute that identifies the event class for any Apple event in the Core suite. Figure 3-6    A descriptor record whose data handle refers to event class dataEvery Apple event includes an attribute specifying the address of the target application. A descriptor record that contains an application’s address is called an address descriptor record.TYPE        AEAddressDesc = AEDesc;                                        {address descriptor record}The address in an address descriptor record can be specified as one of these four basic types (or as any other descriptor type you define that can be coerced to one of these types):Descriptor type    Value    Description    typeApplSignature    'sign'    Application signature    typeSessionID    'ssid'    Session reference number    typeTargetID    'targ'    Target ID record    typeProcessSerialNumber    'psn '    Process serial number    Like several of the other data structures defined by the Apple Event Manager for use in Apple event attributes and Apple event parameters, an address descriptor record is identical to a descriptor record of data type AEDesc; the only difference is that the data for an address descriptor record must always consist of an application’s address.   Keyword-Specified Descriptor RecordsAfter the Apple Event Manager has assembled the necessary descriptor records as the attributes and parameters of an Apple event, your application cannot examine the contents of the Apple event directly. Instead, your application must use Apple Event Manager routines to request each attribute and parameter by keyword. Keywords are arbitrary names used by the Apple Event Manager to keep track of various descriptor records. The AEKeyword data type is defined as a four-character code.TYPE        AEKeyword = PACKED ARRAY[1..4] OF Char;                                                     {keyword for a }                                                             { descriptor record}Constants are typically used for keywords. Here is a list of the keyword constants for Apple event attributes:Attribute keyword    Value    Description    keyAddressAttr     'addr'    Address of target or client application      keyEventClassAttr     'evcl'    Event class of Apple event     keyEventIDAttr    'evid'    Event ID of Apple event     keyEventSourceAttr    'esrc'    Nature of the source application    keyInteractLevelAttr    'inte'    Settings for allowing the Apple Event Manager to bring a server application to the foreground, if necessary, to interact with the user     keyMissedKeywordAttr    'miss'    Keyword for first required parameter remaining in an Apple event     keyOptionalKeywordAttr    'optk'    List of keywords for parameters of the Apple event that should be treated as optional by the target application    keyOriginalAddressAttr    'from'    Address of original source of Apple event if the event has been forwarded (available only in version 1.01 or later versions of the Apple Event Manager)      keyReturnIDAttr     'rtid'    Return ID for reply Apple event     keyTimeoutAttr    'timo'    Length of time, in ticks, that the client will wait for a reply or a result from the server     keyTransactionIDAttr    'tran'    Transaction ID identifying a series of Apple events      Here is a list of the keyword constants for commonly used Apple event parameters:Parameter keyword    Value    Description    keyDirectObject    '----'    Direct parameter     keyErrorNumber    'errn'    Error number parameter    keyErrorString    'errs'    Error string parameter    The Apple Event Registry: Standard Suites defines additional keyword constants for Apple event parameters that can be used with specific Apple events. The Apple Event Manager associates keywords with specific descriptor records by means of a keyword-specified descriptor record, a data structure of type AEKeyDesc that consists of a keyword and a descriptor record. TYPE        AEKeyDesc =     {keyword-specified descriptor record}RECORD    descKey:                    AEKeyword;                    {keyword}    descContent:                    AEDesc;                    {descriptor record}END;Figure 3-7 illustrates a keyword-specified descriptor record with the keyword keyEventClassAttr—the keyword that identifies an event class attribute. The figure shows the logical arrangement of the event class attribute for the Open Documents event shown in Figure 3-3 on page 3-10. The descriptor record in Figure 3-7 is identical to the one in Figure 3-6; its descriptor type is typeType, and the data to which its handle refers identifies the event class as kCoreEventClass. Figure 3-7    A keyword-specified descriptor record for the event class attribute of an Open Documents eventDescriptor ListsWhen extracting data from an Apple event, you use Apple Event Manager functions to copy data to a buffer specified by a pointer, or to return a descriptor record whose data handle refers to a copy of the data, or to return lists of descriptor records (called descriptor lists). As previously noted, the descriptor record (of data type AEDesc) is the fundamental structure in Apple events, and it consists of a descriptor type and a handle to data. A descriptor list is a data structure of type AEDescList defined by the data type AEDesc—that is, a descriptor list is a descriptor record whose data handle refers to a list of other descriptor records (unless it is an empty list).TYPE        AEDescList = AEDesc;                                    {list of descriptor records}Like several other Apple Event Manager data structures, a descriptor list is identical to a descriptor record of data type AEDesc; the only difference is that the data in a descriptor list must always consist of a list of other descriptor records. Figure 3-8 illustrates the logical arrangement of the descriptor list that specifies the direct parameter of the Open Documents event shown in Figure 3-3 on page 3-10. This descriptor list consists of a list of descriptor records that contain alias records to filenames. (See the chapter “Alias Manager” in Inside Macintosh: Files for a detailed description of alias records.)Figure 3-8    A descriptor list for a list of aliasesThe descriptor list in Figure 3-8 provides the data for a keyword-specified descriptor record. Keyword-specified descriptor records for Apple event parameters can in turn be combined in an AE record, which is a descriptor list of data type AERecord.TYPE        AERecord = AEDescList;                                        {list of keyword-specified }                                                { descriptor records}The handle for a descriptor list of data type AERecord refers to a list of keyword-specified descriptor records that can be used to construct Apple event parameters. The Apple Event Manager provides routines that allow your application to create AE records and extract data from them when creating or responding to Apple events. An AE record has the descriptor type typeAERecord and can be coerced to several other descriptor types. An Apple event record, which is different from an AE record, is another special descriptor list of data type AppleEvent and descriptor type typeAppleEvent.TYPE        AppleEvent = AERecord;                                        {list of attributes and     }                                                { parameters necessary for }                                                { an Apple event}An Apple event record describes a full-fledged Apple event. Like the data for an AE record, the data for an Apple event record consists of a list of keyword-specified descriptor records. Unlike an AE record, the data for an Apple event record is divided into two parts, one for attributes and one for parameters. This division within the Apple event record allows the Apple Event Manager to distinguish between an Apple event’s attributes and its parameters. Descriptor lists, AE records, and Apple event records are all descriptor records whose handles refer to a nested list of other descriptor records. The data associated with each data type may be organized differently and is used by the Apple Event Manager for different purposes. In each case, however, the data is identified by a handle in a descriptor record. This means that you can pass an Apple event record to any Apple Event Manager function that expects an AE record. Similarly, you can pass Apple event records and AE records, as well as descriptor lists and descriptor records, to any Apple Event Manager functions that expect records of data type AEDesc.When you use the AECreateAppleEvent function, the Apple Event Manager creates an Apple event record containing the attributes for an Apple event’s event class, event ID, target address, return ID, and transaction ID. You then use Apple Event Manager functions such as AEPutParamDesc and AEPutAttributeDesc to add or modify attributes and to add any necessary parameters to the Apple event. Figure 3-9 shows an example of a complete Apple event—a data structure of type AppleEvent containing a list of keyword-specified descriptor records that name the attributes and parameters of an Open Documents event. The figure includes the event class attribute shown in Figure 3-7 and the descriptor list shown in Figure 3-8, which forms the direct parameter—the keyword-specified descriptor record with the keyword keyDirectObject. The entire figure corresponds to the Open Documents event shown in Figure 3-3 on page 3-10.The next two sections, “Responding to Apple Events” and “Creating and Sending Apple Events,” provide a quick overview of the steps your application must take to respond to and send Apple events.Figure 3-9    Data structures within an Open Documents eventResponding to Apple EventsA client application typically uses the Apple Event Manager to create and send an Apple event requesting a service or information. A server application responds by using the Apple Event Manager to process the Apple event, extract data from the attributes and parameters of the Apple event, and if necessary add requested data to the reply event returned by the Apple Event Manager to the client application. The server usually provides its own Apple event handler for performing the action requested by the client’s Apple event. As its first step in supporting Apple events, your application should support the required Apple events sent by the Finder. If you plan to implement publish and subscribe capabilities, your application must also respond to the Apple events sent by the Edition Manager. Your application should also be able to respond to the standard Apple events that other applications are likely to send to it or that it can send to itself. This section provides a quick overview of the tasks your application must perform in responding to Apple events.To respond to Apple events, your application mustn    set the appropriate flags in its 'SIZE' resourcen    test for high-level events in its event loopn    provide Apple event handlers for the Apple events it supportsn    use the AEInstallEventHandler function to install its Apple event handlersn    use the AEProcessAppleEvent function to process Apple eventsBefore your application can respond to Apple events sent from remote computers, the user of your application must allow network users to link to your application. To do this, the user selects your application in the Finder, chooses Sharing from the File menu, and then clicks the Allow Remote Program Linking checkbox. If the user has not yet started program linking, the Sharing command offers to display the Sharing Setup control panel so that the user can start program linking. The user must also authorize remote users for program linking by using the Users & Groups control panel. Program linking and setting up authenticated sessions are described in the chapter “Program-to-Program Communications Toolbox” in this book.Accepting and Processing Apple EventsTo accept or send Apple events (or any other high-level events), you must set the appropriate flags in your application’s 'SIZE' resource and include code to handle high-level events in your application’s main event loop. Two flags in the 'SIZE' resource determine whether an application receives high-level events: n    The isHighLevelEventAware flag must be set for your application to receive any high-level events.n    The localAndRemoteHLEvents flag must be set for your application to receive high-level events sent from another computer on the network.An Apple event (like all high-level events) is identified by a message class of kHighLevelEvent in the what field of the event record. You test the what field of the event record to determine whether it contains the value represented by the kHighLevelEvent constant; if your application defines any high-level events other than Apple events, you should also test the message field of the event record to determine whether the high-level event is something other than an Apple event. If the high-level event is not one that you’ve defined for your application, assume that it is an Apple event. (You are encouraged to use Apple events instead of defining your own high-level events whenever possible.)After determining that an event is an Apple event, use the AEProcessAppleEvent function to let the Apple Event Manager identify the event. Figure 3-10 shows how the SurfWriter application accepts and begins to process an Apple event sent by the Finder.Figure 3-10    Accepting and processing an Open Documents eventThe AEProcessAppleEvent function first identifies the Apple event by examining the data in the event class and event ID attributes. The function then uses that data to call the Apple event handler that your application provides for that event. The Apple event handler extracts the pertinent data from the Apple event, performs the requested action, and returns a result. For example, if the event has an event class of kCoreEventClass and an event ID of kAEOpenDocuments, the AEProcessAppleEvent function calls your application’s handler for the Open Documents event. Before your application attempts to accept or process any Apple events, it must use the AEInstallEventHandler function to install Apple event handlers. This function installs handlers in an Apple event dispatch table for your application; the Apple Event Manager uses this table to map Apple events to handlers in your application. When your application calls the AEProcessAppleEvent function to process an Apple event, the Apple Event Manager checks the Apple event dispatch table and, if your application has installed a handler for that Apple event, calls that handler. Figure 3-11 shows how the flow of control passes from your application to the Apple Event Manager and back to your application.Figure 3-11    The Apple Event Manager calling the handler for an Open Documents eventAbout Apple Event HandlersYour Apple event handlers must generally perform the following tasks:n    extract the parameters and attributes from the Apple eventn    check that all the required parameters have been extractedn    locate any Apple event objects specified by object specifier records in the Apple event parametersn    if your application needs to interact with the user, use the AEInteractWithUser function to bring it to the foregroundn    perform the action requested by the Apple eventn    dispose of any copies of descriptor records that have been createdn    add information to the reply Apple event if requestedThis section describes how your application’s Apple event handlers can use the Apple Event Manager to accomplish some of these tasks. The chapter “Responding to Apple Events” in this book provides detailed information about handling Apple events and interacting with the user.Extracting and Checking DataYou must use Apple Event Manager functions to extract the data from Apple events. You can also use Apple Event Manager functions to extract data from descriptor records, descriptor lists, and AE records. Most of these routines are available in two forms: they either return a copy of the data in a buffer or return a copy of the descriptor record for the data, including a copy of the data. The following list shows the main functions you can use to access the data of an Apple event:Function    Description(continued)    AEGetParamPtr    Uses a buffer to return a copy of the data contained in an Apple event parameter. Usually used to extract data of fixed length or known maximum length; for example, to extract the result code from the keyErrorNumber parameter of a reply Apple event.    AEGetParamDesc    Returns a copy of the descriptor record or descriptor list for an Apple event parameter. Usually used to extract data of variable length; for example, to extract the descriptor list for a list of alias records specified in the direct parameter of the Open Documents event.    AEGetAttributePtr    Uses a buffer to return a copy of the data contained in an Apple event attribute. Used to extract data of fixed length or known maximum length; for example, to determine the source of an Apple event by extracting the data from the keyEventSourceAttr attribute.        continued    AEGetAttributeDesc    Returns a copy of the descriptor record for an attribute. Used to extract data of variable length; for example, to make a copy of a descriptor record containing the address of an application.    AECountItems    Returns the number of descriptor records in a descriptor list. Used, for example, to determine the number of alias records for documents specified in the direct parameter of the Open Documents event.    AEGetNthPtr    Uses a buffer to return a copy of the data for a descriptor record contained in a descriptor list. Used to extract data of fixed length or known maximum length; for example, to extract the name and location of a document from the descriptor list specified in the direct parameter of the Open Documents event.    AEGetNthDesc    Returns a copy of a descriptor record from a descriptor list. Used to extract data of variable length; for example, to get the descriptor record containing an alias record from the list specified in the direct parameter of the Open Documents event.    You can specify the descriptor type of the resulting data for these functions; if this type is different from the descriptor type of the attribute or parameter, the Apple Event Manager attempts to coerce it to the specified type. In the direct parameter of the Open Documents event, for example, each descriptor record in the descriptor list is an alias record; each alias record specifies a document to be opened. As explained in the chapter “Introduction to File Management” of Inside Macintosh: Files, all your application usually needs is the file system specification (FSSpec) record of the document. When you extract the descriptor record from the descriptor list, you can request that the Apple Event Manager return the data to your application as a file system specification record instead of an alias record.After extracting all known Apple event parameters, your handler should check that it retrieved all the parameters that the source application considered to be required. To do so, determine whether the keyMissedKeywordAttr attribute exists. If so, your handler has not retrieved all the required parameters, and it should return an error.Although the Apple Event Registry: Standard Suites defines Apple event parameters as either required or optional, the Apple Event Manager does not enforce the definitions of required and optional events. Instead, the source application specifies, when it sends the event, which Apple event parameters the target can treat as if they were optional. For more information about optional parameters, see “Specifying Optional Parameters for an Apple Event,” which begins on page 5-7.If any of the Apple event parameters include object specifier records, your handler should use the AEResolve function, other Apple Event Manager routines, and your own application-defined functions to locate the corresponding Apple event objects. For more information about locating Apple event objects, see “Working With Object Specifier Records,” which begins on page 3-32.Interacting With the UserIn some cases, the server may need to interact with the user when it handles an Apple event. For example, your handler for the Print Documents event may need to display a print options dialog box and get settings from the user before printing. By specifying flags to the AESetInteractionAllowed function, you can set preferences to allow user interaction with your application (a) only when your application is sending the Apple event to itself, (b) only when the client application is on the same computer as your application, or (c) for any event sent by any client application on any computer. In addition, your handler should always use the AEInteractWithUser function before displaying a dialog box or alert box or otherwise interacting with the user. The AEInteractWithUser function determines whether user interaction can occur and takes appropriate action depending on the circumstances.Both the client and server specify their preferences for user interaction: the client specifies whether the server should be allowed to interact with the user, and the server specifies when it allows user interaction while processing an Apple event. The Apple Event Manager does not allow a server application to interact with the user in response to a client application’s Apple event unless at least two conditions are met: First, the client application must set flags in the sendMode parameter of the AESend function indicating that user interaction is allowed. Second, the server application must either set no user interaction preferences, in which case AEInteractWithUser assumes that only interaction with a client on the local computer is allowed; or it must set flags to the AESetInteractionAllowed function indicating that user interaction is allowed. If these two conditions are met and if AEInteractWithUser determines that both the client and server applications allow user interaction under the current circumstances, AEInteractWithUser brings your application to the foreground if it isn’t already in the foreground. Your application can then display its dialog box or alert box or otherwise interact with the user. The AEInteractWithUser function brings your server application to the front either directly or after the user responds to a notification request.For detailed information about how to specify flags to the AESetInteractionAllowed function and how the Apple Event Manager determines whether user interaction is allowed, see the section “Interacting With the User,” which begins on page 4-45.Performing the Requested Action and Returning a ResultWhen your application responds to an Apple event, it should perform the standard action requested by that event. For example, your application should respond to the Open Documents event by opening the specified documents in titled windows just as if the user had selected each document from the Finder and then chosen Open from the File menu. Many Apple events can ask your application to return data. For instance, if your application is a spelling checker, the client application might expect your application to return data in the form of a list of misspelled words. Figure 3-14 on page 3-38 shows a similar example: a Get Data event that asks the server application to locate a specific Apple event object and return the data associated with it. If the client application requests a reply, the Apple Event Manager prepares a reply Apple event by passing a default reply Apple event to your handler. If the client application does not request a reply, the Apple Event Manager passes a null descriptor record—that is, a descriptor record of type typeNull whose data handle has the value NIL—to your handler instead of a default reply Apple event. The default reply Apple event has no parameters when it is passed to your handler, but your handler can add parameters to it. If your application is a spelling checker, for example, you can return a list of misspelled words in a parameter. However, your handler should check whether the reply Apple event exists before attempting to add any attributes or parameters to it. Any attempt to add an Apple event attribute or parameter to a null descriptor record generates an error. When you extract a descriptor record using the AEGetParamDesc, AEGetAttributeDesc, AEGetNthDesc, or AEGetKeyDesc function, the Apple Event Manager creates a copy of the descriptor record for you to use. When your handler is finished using a copy of a descriptor record, you should dispose of it—and thereby deallocate the memory used by its data—by calling the AEDisposeDesc function.NoteOutputs from functions such as AEGetKeyPtr and other routines whose names end in -Ptr use a buffer rather than a descriptor record to return data. Because these functions don’t require the use of AEDisposeDesc, it is preferable to use them for any data that is not identified by a handle.uYour Apple event handler should always set its function result either to noErr if it successfully handles the Apple event or to a nonzero result code if an error occurs. If your handler returns a nonzero result code, the Apple Event Manager adds a keyErrorNumber parameter to the reply Apple event (unless you have already added a keyErrorNumber parameter). This parameter contains the result code that your handler returns. The client should check whether the keyErrorNumber parameter exists to determine whether your handler performed the requested action. In addition to returning a result code, your handler can also return an error string in the keyErrorString parameter of the reply Apple event. The client can use this string in an error message to the user.If the client application requested a reply, the Apple Event Manager returns the reply Apple event, which is identified by the event class kCoreEventClass and by the event ID kAEAnswer. When the client has finished using the reply Apple event, it should dispose of both the reply event and the original event—and thereby deallocate the memory they use—by calling the AEDisposeDesc function. The Apple Event Manager takes care of disposing both the Apple event and the reply Apple event after a server application’s handler returns to AEProcessAppleEvent, but a server application is responsible for disposing of any Apple event data structures it creates while extracting data from the Apple event.Figure 3-12 shows the entire process of responding to an Apple event. Figure 3-12    Responding to an Open Documents event  When your handler returns a result code to the Apple Event Manager, you have finished your response to the client application’s Apple event.Creating and Sending Apple EventsYour application can use Apple events to request services or information from other applications, send information to other applications, or trigger actions within your application. For example, you can use the core Apple event Get Data to request specific data from another application’s documents. Similarly, you can use other Apple events to request services—for example, asking a spell-checking application to check the text in a document created by your application. Consult the Apple Event Registry: Standard Suites for the format and function of the standard Apple events that you want your application to send. To communicate with another application by sending an Apple event, your application mustn    set the appropriate flags in its 'SIZE' resourcen    create an Apple event record by calling the AECreateAppleEvent functionn    use Apple Event Manager functions to add parameters and any additional attributes to the Apple eventn    call the AESend function to send the Apple eventn    dispose of any copies of descriptor records that you have createdn    handle the reply Apple event (if necessary)The sections that follow describe how your application can use the Apple Event Manager to accomplish these tasks. The chapter “Creating and Sending Apple Events” in this book provides detailed information about creating and sending Apple events.To act as a server for your application, the target application must support high-level events and must be running. The server can be your own application, another application running on the user’s computer, or an application running on another user’s computer connected to the network. Your application should also allow the user to choose among the various applications available as servers. The PPCBrowser function allows users to select target applications on their own computers or on computers connected to the network. The PPCBrowser function presents a standard user interface for choosing a target application, much as the Standard File Package provides a standard user interface for opening and saving files. See the chapter “Program-to-Program Communications Toolbox” in this book for details on using the PPCBrowser function.If the server application is on a remote computer on a network, the user of that computer must allow program linking to the server application. The user of the server application does this by selecting the application icon in the Finder, choosing Sharing from the File menu, then clicking the Allow Remote Program Linking checkbox. If the user has not yet started program linking, the Sharing command offers to display the Sharing Setup control panel so that the user can start program linking. The user must also authorize remote users for program linking by using the Users & Groups control panel. Program linking and setting up authenticated sessions are described in the chapter “Program-to-Program Communications Toolbox” in this book.Creating an Apple Event RecordUse the AECreateAppleEvent function to create an Apple event record. Using the arguments you pass to the AECreateAppleEvent function, the Apple Event Manager constructs the data structures describing the event class, the event ID, and the target address attributes of an Apple event. The event class and event ID, of course, identify the particular event you wish to send. The target address identifies the intended recipient of the Apple event.You can specify two other attributes with the AECreateAppleEvent function: the reply ID and the transaction ID. For the reply ID attribute, you usually specify the kAutoGenerateReturnID constant to the AECreateAppleEvent function. This constant ensures that the Apple Event Manager generates a unique return ID for the reply Apple event returned from the server. For the transaction ID attribute, you usually specify the kAnyTransactionID constant, which indicates that this Apple event is not one of a series of interdependent Apple events.Adding Apple Event Attributes and ParametersThe Apple event record created with the AECreateAppleEvent function serves as a foundation for the Apple event you want to send. Descriptor records and descriptor lists are the building blocks from which the complete Apple event record is constructed. To create descriptor records and descriptor lists and add items to a descriptor list, use the following functions:Function    Description    AECreateDesc    Takes a descriptor type and a pointer to data and converts them into a descriptor record    AECreateList    Creates an empty descriptor list or AE record.    AEPutPtr    Takes a descriptor type and a pointer to data and adds the data to a descriptor list as a descriptor record; used, for example, to add to a descriptor list a number used as the parameter of an Apple event requesting a calculation.    AEPutDesc    Adds a descriptor record to a descriptor list; used, for example, to add to a descriptor list an alias record used as the direct parameter of an Apple event requesting file manipulation.    To add the remaining attributes and parameters necessary for your Apple event to the Apple event record, you can use these additional Apple Event Manager functions:Function    Description    AEPutParamPtr    Takes a keyword, descriptor type, and pointer to data and adds the data to an Apple event record as a parameter with the specified keyword (replacing any existing parameter with the same keyword); used, for example, to put numbers into the parameters of an Apple event that asks the server to perform a calculation.    AEPutParamDesc    Takes a keyword and a descriptor record and adds the descriptor record to an Apple event record as a parameter with the specified keyword (replacing any existing parameter with the same keyword); used, for example, to place a descriptor list containing alias records into the direct parameter of an Apple event that requests a server to manipulate files.    AEPutAttributePtr    Takes a keyword, descriptor type, and pointer to data and adds the descriptor record to an Apple event record as an attribute with the specified keyword (replacing any existing attribute with the same keyword); used, for example, to change the transaction ID of an Apple event record that is waiting to be sent.     AEPutAttributeDesc    Takes a keyword and a descriptor record and adds the descriptor record to an Apple event record as an attribute with the specified keyword (replacing any existing attribute with the same keyword); used, for example, to replace the descriptor record used for the target address attribute in an Apple event record waiting to be sent.    Apple event parameters for core events and functional-area events can include descriptions of Apple event objects in special descriptor records called object specifier records. For an overview of object specifier records, see “Working With Object Specifier Records,” which begins on page 3-32.Sending an Apple Event and Handling the ReplyAfter you add all the attributes and parameters required for the Apple event, use the AESend function to send the Apple event. The Apple Event Manager uses the Event Manager to transmit the Apple event to the server application.The AESend function requires that you specify whether your application should wait for a reply from the server. If you specify that you want a reply, the Apple Event Manager prepares a reply Apple event for your application by passing a default reply Apple event to the server. The Apple Event Manager returns any nonzero result code from the server’s handler in the keyErrorNumber parameter of the reply Apple event. The server can return an error string in the keyErrorString parameter of the reply Apple event. The server can also use the reply Apple event to return any data you requested—for example, the results of a numeric calculation or a list of misspelled words.You specify how your application should wait for a reply by using one of these flags in the sendMode parameter of the AESend function:Flag    Description    kAENoReply    Your application does not want a reply Apple event.    kAEQueueReply    Your application wants a reply Apple event; the reply appears in your event queue as soon as the server has the opportunity to process and respond to your Apple event.    kAEWaitReply    Your application wants a reply Apple event and is willing to give up the processor while waiting for the reply; for example, if the server application is on the same computer as your application, your application yields the processor to allow the server to respond to your Apple event.    If you specify the kAEWaitReply flag, you should provide an idle function. This function should process any non-high-level events that occur while your application is waiting for a reply. You supply a pointer to your idle function as a parameter to the AESend function. So that your application can process other Apple events while it is waiting for a reply, you can also specify an optional filter function to the AESend function.If you specify the kAENoReply flag, the reply Apple event prepared by the Apple Event Manager for the server application consists of a null descriptor record.If your Apple event may require the user to interact with the server application (for example, to specify print or file options), you can communicate your user interaction preferences to the server by specifying additional flags in the sendMode parameter of the AESend function. These flags specify the conditions, if any, under which the server application can interact with the user and, if interaction is allowed, whether the server should come directly to the foreground or post a notification request.The server application specifies its own preferences for user interaction by specifying flags to the AESetInteractionAllowed function, as described in the previous section. The interaction of the client and server applications’ preferences is explained in detail in “Interacting With the User,” which begins on page 4-45.After you send an Apple event, your application is responsible for disposing of the Apple event record—and thereby deallocating the memory its data uses—by calling the AEDisposeDesc function. If you create one descriptor record and add it to another, the Apple Event Manager adds a copy of the newly created one to the existing one and also makes a copy of the associated data. For example, you might use the AECreateDesc function to create a descriptor record that you wish to add to an Apple event. When you use the AEPutParamDesc function, it adds a copy of your newly created descriptor record, including its data, as a parameter to an existing Apple event. When you no longer need the original descriptor record, you should call AEDisposeDesc to dispose of it.Your application should dispose of all the descriptor records that are created for the purposes of adding parameters and attributes to an Apple event. You normally dispose of your Apple event and its reply after you receive a result from the AESend function. You should dispose of these even if AESend returns an error result. If you specify the kAEWaitReply flag, the reply Apple event is returned in a parameter you pass to the AESend function. If you specify the kAEQueueReply flag to the AESend function, the reply Apple event is returned in the event queue. In this case, the reply is identified by the event class kCoreEventClass and the event ID kAEAnswer. Your application processes reply events in its event queue in the same way that server applications process Apple events. Your application should check for the existence of the keyErrorNumber parameter of the reply Apple event to ensure that the server performed the requested action. The server can also return, in the keyErrorString parameter, any error messages you need to display to the user.Whenever a server application provides an error string, it should also provide an error number. However, you can’t count on all server applications to do so. The absence of the keyErrorNumber parameter doesn’t necessarily mean that there won’t an error string provided in the keyErrorString parameter. A client application should therefore check for both the keyErrorNumber and keyErrorString parameters before assuming that no error has occurred. If a string has been provided without an error number, an error has occurred. After extracting the information it needs from the reply event, your handler should dispose of the reply by calling the AEDisposeDesc function. Similarly, when your handler no longer needs descriptor records it has extracted from the reply, it should call AEDisposeDesc to dispose of them.The next section provides an overview of the way a source application identifies Apple event objects supported by a target application. If you are starting by supporting only the Required suite and the Apple events sent by the Edition Manager, you can skip the next section and go directly to “About the Apple Event Manager,” which begins on page 3-48. Working With Object Specifier RecordsMost of the standard Apple events allow the source application to refer, in an Apple event parameter, to Apple event objects within the target application or its documents. The Apple Event Manager allows applications to construct and interpret such references by means of a standard classification system for Apple event objects. This system, described in detail in the Apple Event Registry: Standard Suites, is summarized in “The Classification of Apple Event Objects,” which begins on page 3-39. A description in an Apple event parameter that uses this classification system takes the form of an object specifier record.An object specifier record is a descriptor record of descriptor type typeObjectSpecifier that describes the location of one or more Apple event objects: for example, the table “Summary of Sales” in the document “Sales Report,” or the third row in that table, or the last row of the column “Totals.” With the aid of application-defined functions, the Apple Event Manager can conduct a step-by-step search according to such instructions in an object specifier record, locating first the document, then the table, then other objects, and so on until the requested object has been identified. Object specifier records can specify many combinations of identifying characteristics that cannot be specified using one of the simple data types. This section introduces object specifier records and the organization of their data. You need to read this section (a) if you plan to support the Core suite or any of the standard functional-area suites and (b) if you want to make your application scriptable—that is, capable of responding to scripts written in a scripting language.IMPORTANTAn object specifier record identifies one or more Apple event objects among many; it contains a description of each object, not the object itself. An Apple event object described by an object specifier record exists only in the server application’s document or in the server application itself.sA client application cannot retrieve an Apple event object from a server application unless the server application can accurately locate it. Thus, to locate characters of a specific color, a server application must be able to identify a single character’s color; to locate a character in a cell, a server application must be able to locate both the table and the cell.A client application can create object specifier records for use as Apple event parameters. Scripting components can also create object specifier records as Apple event parameters for the Apple events they generate in the course of executing a script. A server application that receives an Apple event containing an object specifier record should resolve the object specifier record—that is, locate the requested Apple event objects. To respond to core and functional-area Apple events received by your application, you must first define a hierarchy of Apple event objects for your application that you want other applications or scripting languages to be able to describe. The Apple event objects for your application should be based as closely as possible on the standard object classes described by the Apple Event Registry: Standard Suites. After you have decided which of the standard Apple event objects make sense for your application, you can write functions that locate objects on the basis of information in an object specifier record. If you want your application to send specific Apple events to other applications, you must also write functions that can create object specifier records and add them to Apple events. Your application does not need to create object specifier records in order to be scriptable. However, to write functions that can help the Apple Event Manager resolve object specifier records, you need to know how they are constructed. “Finding Apple Event Objects,” which begins on page 3-46, provides an overview of the way the Apple Event Manager works with your application-defined functions to locate the Apple event objects described in an object specifier record. The chapter “Resolving and Creating Object Specifier Records” in this book describes in detail how to support object specifier records as a server or client application. Data Structures Within an Object Specifier RecordThe organization of the data for an object specifier record is nearly identical to that of the data for an AE record. An object specifier record is a structure of data type AEDesc whose data handle usually refers to four keyword-specified descriptor records describing one or more Apple event objects. An AE record is a structure of data type AERecord whose data handle refers to one or more Apple event parameters.The four keyword-specified descriptor records for an object specifier record provide information about the requested Apple event object or objects.Keyword    Description of data    keyAEDesiredClass    Four-character code indicating the object class ID    keyAEContainer    A description of the container for the requested object, usually in the form of another object specifier record    keyAEKeyForm    Four-character code for the key form, which indicates how to interpret the key data    keyAEKeyData    Key data, used to distinguish the desired Apple event object from other objects of the same object class in the same container    For example, the data for an object specifier record identifying a table named “Summary of Sales” in a document named “Sales Report” consists of four keyword-specified descriptor records that provide the following information:n    the object class ID for a tablen    another object specifier record identifying the document “Sales Report” as the container for the tablen    a key form constant indicating that the key data contains a namen    key data that consists of the string “Summary of Sales”The object class ID specifies the Apple event object class to which the object belongs. An Apple event object class is a category for Apple event objects that share specific characteristics (see “Apple Events and Apple Event Objects” on page 3-6). The characteristics of each object class are listed in the Apple Event Registry: Standard Suites. For example, the Core suite defines object classes for documents, paragraphs, words, windows, and floating windows. The first keyword-specified descriptor record in an object specifier record uses a four-character code or a constant to specify the object class ID. The object class for words, for example, can be identified by either the object class ID 'cwor' or the constant cWord. NoteThe object class ID identifies the object class of an Apple event object described in an object specifier record, whereas the event class and event ID identify an Apple event.uThe container for an Apple event object is usually another Apple event object. For example, the container for a document might be a window, and the container for characters, delimited items, or a word might be another word, a paragraph, or a document. The container is identified by the second keyword-specified descriptor record in an object specifier record; usually this is another object specifier record. The container can also be specified by a null descriptor record, which indicates a default container or a container already known to the Apple Event Manager.The descriptor record in an object specifier record that identifies an Apple event object’s container can in turn use another object specifier record to identify the container’s container, and so on until the Apple event object is fully specified. For example, an object specifier record identifying a paragraph might specify the paragraph’s container with another object specifier record that identifies a page. That object specifier record might in turn specify the page’s container with another object specifier record identifying a document. The ability to nest one object specifier record within another in this way makes it possible to identify elements such as “the first row in the table named ‘Summary of Sales’ in the document named ‘Sales Report.’” The key form and key data distinguish the desired Apple event object from other Apple event objects of the same object class. The key form describes the form the key data takes. The third keyword-specified descriptor record in an object specifier record usually specifies the key form with one of seven standard constants:Key form    Value    Corresponding key data    formPropertyID    'prop'    Property ID for an element’s property    formName    'name'    Element’s name    formUniqueID    'ID  '    A value that uniquely identifies an object within its container or across an application    formAbsolutePosition    'indx'    An integer or other constant indicating the position of one or more elements in relation to the beginning or end of their container    formRelativePosition    'rele'    A constant that specifies the element just before or after the container    formTest    'test'    Descriptor records that specify a test    formRange    'rang'    Descriptor records that specify a group of elements between two other elements     A key form of formPropertyID indicates key data that specifies a property. A property of an Apple event object is a specific characteristic of that object that can be identified by a constant. The properties associated with the object class for documents include the name of the document and a flag indicating whether the document has been modified since the last save. The properties associated with the object class for words include color, font, point size, and style.Figure 3-13 shows the structure of a typical object specifier record: four keyword-specified descriptor records that specify the class ID, the container, the key form, and the key data. These four keyword-specified descriptor records are the data for a descriptor record (AEDesc) of descriptor type typeObjectSpecifier. Note the similarities between the object specifier record shown in Figure 3-13 and the Apple event record shown in Figure 3-9 on page 3-19. Like an Apple event record or an AE record, an object specifier record consists of a list of keyword-specified descriptor records. Figure 3-13 shows the structure of a simple object specifier record that specifies the key form formPropertyID, formName, or formAbsolutePosition. For detailed information about the structure of object specifier records that specify the other key forms, see the chapter “Resolving and Creating Object Specifier Records” in this book. Figure 3-13    Data structures within a simple object specifier recordFigure 3-14 shows the object specifier record for the Get Data event previously illustrated in Figure 3-4 on page 3-11. The object class ID tells the SurfWriter application that the requested data is an element of class cTable. The container for the table is the document “Sales Report.” The key form is formName, which tells the server application that the key data identifies the Apple event object by name. The key data is the name of the table.Figure 3-14    An object specifier record in a Get Data eventTo add an object specifier record to an Apple event as one of its parameters, your application must first create the object specifier record. “Creating Object Specifier Records,” which begins on page 6-55, describes the Apple Event Manager routines for creating object specifier records.To respond to Apple events that include object specifier records, your application should use the standard classification system for Apple event objects and provide functions that can locate those objects within your application or its documents. The next section summarizes the classification of Apple event objects as defined in the Apple Event Registry: Standard Suites. The Classification of Apple Event ObjectsTo create or resolve object specifier records, your application should use the classification of Apple event objects defined by the Apple Event Registry: Standard Suites. This section summarizes the concepts that underlie that classification system. You should have a copy of the Apple Event Registry: Standard Suites available for reference purposes while you read this section.You do not need to write your application in an object-oriented programming language in order to support Apple event objects in your application. However, you must understand the classification system described in this section in order to classify Apple event objects in your application and to write routines that can locate them on the basis of information contained in object specifier records.Object ClassesExcept for the concept of inheritance, Apple event objects are different from the objects used in object-oriented programming languages. Apple event objects are distinct items in a server application or any of its documents that can be specified by an object specifier record in an Apple event sent by a client application. Apple event objects are often, but not always, items that a user can differentiate and manipulate within an application, such as words, paragraphs, shapes, windows, or style formats. Every Apple event object can be classified according to its object class, which defines both its characteristics and its behavior. The object classes listed in the Apple Event Registry: Standard Suites provide a method of describing Apple event objects that all applications can understand. Object classes permit more flexibility than simple descriptor types; for example, a word can be defined as a simple string, or it can be defined as an Apple event object with specific characteristics such as font or style.NoteThe definition of an object class only specifies conventions that determine how applications should handle Apple event objects that belong to that class. Your application must make sure that it uses the conventions correctly; they are not enforced by the Apple Event Manager.uEach object class is identified by a four-character object class ID, which can also be represented by a constant. Constants for object classes always begin with the letter c. The definition of an object class specifies its superclass, which is the object class from which a subclass (the class being defined) inherits some of its characteristics. Characteristics can also be inherited from special object classes, called abstract superclasses, that are used only in definitions of object classes and do not refer to real Apple event objects. The pattern of inheritance among object classes is called the object class inheritance hierarchy. Figure 3-15 shows a portion of this hierarchy. The abstract superclass cObject is at the top of the hierarchy and is therefore the only object class that has no superclass. At the next level are cText, which is a regular object class, and cOpenableObject, which is an abstract superclass. Both are subclasses of cObject and superclasses for their own subclasses. The object classes cWord, cItem, and cChar are all subclasses of cText. Similarly, cWindow, cDocument, and cFile are subclasses of cOpenableObject. Every object class inherits all the characteristics of its superclass and can also add characteristics of its own.Figure 3-15    Superclasses and subclassesHere are some of the object classes defined for the Core suite:Class    Class ID    Description    cChar    'cha '    Text characters    cDocument    'docu'    Macintosh documents    cFile    'cfil'    Macintosh files    cSelection    'csel'    User or application selections    cText    'ctxt'    Series of characters    cWindow    'cwin'    Standard Macintosh windows    Here are some of the object classes defined for the Text suite:Class    Class ID    Description    cChar    'cha '    Text characters    cLine    'clin'    Lines of text    cParagraph    'cpar'    Paragraphs    cText    'ctxt'    Series of characters    cTextFlow    'cflo'    Text flows    cWord    'cwor'    Words    As you can see, some object classes, such as cChar and cText, are defined in more than one suite. For example, the definition of the cText object class in the Text suite is an extension of the cText object class defined in the Core suite; it duplicates all the characteristics of the Core suite object class and adds some of its own. Like a word in a dictionary, one object class ID can have several related definitions. You can choose to support the definition that best suits your application; or, if necessary, you can create extensions of your own. The extension of an object class is different from inheritance between object classes. An extension of a standard object class provides additional ways of describing an Apple event object of that class, whereas the object class inheritance hierarchy determines the pattern of characteristics shared by different object classes. The definition of an object class always specifies a default descriptor type. Suppose, for example, that a client application sends a Get Data, Cut, or Copy event that specifies an Apple event object but does not specify a descriptor type for the returned data. In this case, the server application returns a descriptor record of the default descriptor type for the object class of the specified Apple event object. For example, the default descriptor type for Apple event objects of class cWord is typeIntlText, a descriptor type that specifies an undelimited string of characters in a specific language and script system. The client application can also request that the data be returned in a descriptor record of some other data type.The definition of an object class includes three lists of characteristics: properties, element classes, and Apple events that support the object class. (The next section describes properties and element classes.) Any or all of these characteristics may be inherited from a superclass. An Apple event is listed for an object class if its parameters can specify objects of that class. The definition for cWindow, for example, lists 12 Apple events, including the Open, Close, and Move events, whose parameters can include object specifier records that specify windows. The cWindow class inherits all of these Apple events from its abstract superclass, cOpenableObject.The Apple Event Registry: Standard Suites also defines primitive object classes, which describe Apple event objects that contain a single value. For example, the cBoolean, cLongInteger, and cAlias object classes are all primitive object classes. The object class ID for a primitive object class is the same as the four-character value of its descriptor type. Primitive object classes contain no properties; they contain only the value of the data.  Properties and ElementsThe properties listed for an object class can be used to identify characteristics of Apple event objects that belong to that class. Each property is identified by a four-character property ID, which can also be represented by a constant. Constants for properties always begin with the letter p.Here are constants and property IDs for some properties:Property    Property ID    Description    pName    'pnam'    Name of an Apple event object    pBounds    'pbnd'    Coordinates of a window    pVisible    'pvis'    Indicates whether a window is visible    pIsModal    'pmod'    Indicates whether a window is modal    pClass    'pcls'    Class ID of an Apple event object    pFont    'font'    Font    pTextStyle    'txst'    Text style    pColor    'colr'    Text color    pTextPointSize    'ptps'    Point size    pScriptTag    'psct'    Script system identifier    pFillColor    'flcl'    Fill color    The property of an Apple event object is itself defined as a single Apple event object whose container is the object to which the property belongs. For example, the pFont property of a word is defined by the name of a font, such as New York; the string that identifies the font is an Apple event object of class cText. The constant cProperty specifies the object class for any object specifier record that identifies a property. CONST cProperty = 'prop';An object specifier record for a property specifies cProperty as the object class ID, the Apple event object to which the property belongs as the container, formPropertyID as the key form, and a constant such as pFont as the key data.   The elements of a specific Apple event object are the other Apple event objects it contains, excluding those that define its properties. An object specifier record for an element specifies the Apple event object in which the element is located as the container and can specify any key form except formPropertyID. Each object class definition in the Apple Event Registry: Standard Suites includes a list of element classes, which are the object classes of the elements that an Apple event object can contain. An Apple event object contains exactly one of each of its properties, whereas it can contain no elements or many elements of the same element class. In general, a property of an object describes something about that object; a property can be examined or changed but never deleted. An element can be one or more discrete objects contained in another object and can usually be deleted. For example, because a paragraph can contain one or more words, one of the element classes listed for the object class cParagraph is the object class cWord. Individual words can be deleted from a paragraph. However, even though a word in a paragraph can be in a different font from the words around it, a paragraph can have only one pFont property. This property is defined as the font of the first character in the paragraph and consists of the name of a font. The paragraph’s pFont property can be changed but not removed.The properties and element classes listed for each object class definition in the Apple Event Registry: Standard Suites can be inherited from a superclass, or they can originate with a subclass. Figure 3-16 illustrates the object class inheritance hierarchy for the object class cWindow in the Core suite. Boldface terms in the figure represent those properties, element classes, or Apple events that are not inherited. The object class cWindow includes all the properties and Apple events of its superclass, cOpenableObject, which in turn includes all the properties and Apple events of its superclass, cObject. The object class cWindow also includes 11 properties and one element class that originate with cWindow and are not inherited. The pClass property—the property that specifies the four-character class ID—originates with cObject. Because the definitions of all object classes are ultimately derived from cObject, pClass is inherited by all object classes. The definition for cObject also lists ten Apple events, which include common events such as Get Data, Move, and Delete Element. Because cObject is at the top of the object class inheritance hierarchy, these ten Apple events can use object specifier records that describe Apple event objects of any object class as a direct parameter. Like all abstract superclasses, cObject does not correspond to a real Apple event object, so its definition does not list any element classes. Unlike any other object class, cObject is at the top of the object class inheritance hierarchy and therefore does not have a superclass. Figure 3-16    The object class inheritance hierarchy for the object class cWindowThe chain of containers that determine the location of one or more Apple event objects is called the container hierarchy. The container hierarchy, which specifies the location of real Apple event objects, is different from the object class inheritance hierarchy, which is an abstract concept that determines which properties, element classes, and Apple events an object class inherits from its superclass. For example, the container hierarchy for an Apple event object of class cWord can vary from one word to another, because various combinations of other Apple event objects, such as a document, a paragraph, a delimited string, or another word, can contain a word. Applications that support Apple event objects must be able to identify the order of several elements of the same class that are contained within another Apple event object. For example, each word in a paragraph should have an identifiable order, such as the 5th word or the 12th word. This allows other applications to identify Apple event objects by describing their absolute position within a container. Figure 3-17 shows an Apple event object of object class cWord—the word “Sales”—contained in another Apple event object of object class cParagraph. (Both these object classes are defined in the Text suite.) The figure shows only a portion of the container hierarchy for the word, since a complete description of the word would also include the containers that specify the location of the paragraph. Your application must take account of the definitions in the Apple Event Registry: Standard Suites for any object classes you want to support. For example, the definition for the object class cText lists paragraphs, lines, words, and characters as Apple event objects that can be contained in Apple event objects of class cText. To support Apple events that refer to elements of object class cText, your application should associate the cText object class with paragraphs, lines, words, and characters in its documents. The list of properties defined for class cText includes the properties pColor, pFont, pPointSize, pScriptTag, and pTextStyles. If you want to support Apple events that distinguish a boldface 12-point word of object class cText from an italic 14-point word, for example, your application must associate the point size and style of text in its documents with the properties pPointSize and pTextStyles defined for class cText. Figure 3-17    An Apple event object of class cWord contained in an Apple event object of class cParagraphFinding Apple Event ObjectsMost of the Apple events in the Core suite and the functional-area suites defined in the Apple Event Registry: Standard Suites can include parameters that consist of object specifier records. Your application’s handlers for these events can use the AEResolve function to resolve object specifier records: that is, to locate the Apple event objects they describe.The AEResolve function parses an object specifier record and performs related tasks that are the same for all object specifier records. When necessary, the AEResolve function calls application-defined functions to perform tasks that are unique to the application, such as locating a specific Apple event object in the application’s data structures.Your application can provide two kinds of application-defined functions for use by AEResolve. Object accessor functions locate Apple event objects. Every application that supports simple object specifier records must provide one or more object accessor functions. Object callback functions perform other tasks that only an application can perform, such as counting, comparing, or marking Apple event objects. Each time AEResolve calls one of your application’s object accessor functions successfully, the object accessor function returns a special descriptor record, called a token, that identifies either an element in a specified container or a property of a specified Apple event object. The token can be of any descriptor type, including descriptor types you define yourself. You install object accessor functions by using the AEInstallObjectAccessor function. Much like the AEInstallEventHandler function, AEInstallObjectAccessor uses an object accessor dispatch table to map requests for Apple event objects to the appropriate object accessor functions in your application. These requests refer to objects of a specified object class in containers identified by a token of a specified descriptor type.Responding to an Apple event that includes an object specifier record typically involves these steps:    1.    After determining that the event is an Apple event, your application calls AEProcessAppleEvent.    2.    The AEProcessAppleEvent function uses the Apple event dispatch table to dispatch the event to the your application’s handler for that event.    3.    The Apple event handler extracts the Apple event parameters, and passes the object specifier records they contain to AEResolve.    4.    The AEResolve function uses the object accessor dispatch table to call one or more object accessor functions, one at a time, that can identify the nested Apple event objects described by each object specifier record. Each object accessor function returns a token for the object it finds, which in turn helps to determine which object accessor function the AEResolve function will use to locate the next Apple event object.    5.    The AEResolve function returns the final token for the requested object to the application’s handler.The resolution of an object specifier record always begins with the outermost container it specifies. For example, to locate a table named “Summary of Sales” in the document named “Sales Report,” the AEResolve function first calls an object accessor function that can locate the document, then uses the token returned by that function to identify an object accessor function that can locate the table. It then returns the token for the table to the Apple event handler that called AEResolve.The chapter “Resolving and Creating Object Specifier Records” in this book describes in detail how to resolve object specifier records and how to write and install object accessor and object callback functions. About the Apple Event ManagerYou can use the Apple Event Manager ton    respond to Apple events as a server applicationn    create and send Apple events as a client applicationn    resolve and create object specifier recordsn    support Apple event recordingThis section briefly summarizes the steps involved in providing each kind of support and tells where to find the relevant information in this book.Supporting Apple Events as a Server ApplicationYou do not need to implement all Apple events at once. You can begin by supporting just the required events and, if necessary, the events sent by the Edition Manager. The beginning of the section “Handling Apple Events” on page 4-4 describes how to provide this minimal level of support.It is relatively easy to respond to the required events and the events sent by the Edition Manager. If, however, your application cannot respond to any other Apple events, other applications will not be able to request services that involve locating specific Apple event objects within your application or its documents, and users will not be able to control your application by executing scripts. To respond to Apple events it is likely to receive from other applications or from scripting components, your application must be able to respond to the appropriate core and functional-area Apple events. Once you have provided the basic level of support for the Required suite and for events sent by the Edition Manager, you shouldn    decide which other Apple event suites you want to supportn    define the hierarchy of Apple event objects within your application that you want scripting components or other applications to be able to identify—that is, which Apple event objects can be contained by other Apple event objects in your applicationn    write handlers for the Apple events you support, and install corresponding entries in your application’s Apple event dispatch tableTo decide which Apple event suites you want to support and how to define the hierarchy of Apple event objects in your application, consult the Apple Event Registry: Standard Suites and evaluate which Apple events and Apple event object classes make sense for your application. If necessary, you can extend the definitions of the standard Apple events and Apple events objects to cover special requirements of your application. It is better to extend the standard definitions rather than to define your own custom Apple events, because only those applications that choose to support your custom Apple events explicitly will be able to make use of them.The chapter “Responding to Apple Events” in this book describes how to write Apple event handlers and related routines. The chapter “Resolving and Creating Object Specifier Records” describes how to resolve object specifiers in an Apple event that describes Apple event objects in your application or its documents.If your application can respond to Apple events, you can make it scriptable simply by adding an 'aete' resource. Scripting components use your application’s 'aete' resource to obtain information about the Apple events and corresponding human-language terminology that your application supports. The chapter “Apple Event Terminology Resources” in this book describes how to optimize your implementation of Apple events for use by scripting components and how to create an 'aete' resource.Supporting Apple Events as a Client ApplicationBecause users can send Apple events to a variety of applications simply by executing a script, many applications have no need to send Apple events. However, if you want to factor your application for recording, or if you want your application to send Apple events directly to other applications, you can use Apple Event Manager routines to create and send Apple events. To send an Apple event, you mustn    create the Apple eventn    add parameters and attributesn    use the AESend function to send the eventThe chapter “Creating and Sending Apple Events” in this book describes how to perform these tasks.Supporting Apple Event ObjectsIf your application responds to core and functional-area Apple events, it must also be able to resolve object specifier records that describe the objects on which those Apple events can act. In addition to the tasks described in the chapter “Responding to Apple Events,” you must perform the following tasks to handle Apple events that contain object specifier records:n    Write object accessor functions that can locate the Apple event objects you support, and install corresponding entries in your application’s object accessor dispatch table.n    Write any object callback functions that you decide to provide. To handle object specifier records that specify a test, your application must provide at least two object callback functions: one that counts objects and one that compares them.n    Call AEResolve from your Apple event handlers whenever an Apple event parameter includes an object specifier record. The chapter “Resolving and Creating Object Specifier Records” describes how to perform these tasks. It also describes how applications that send Apple events to themselves or directly to other applications can create object specifier records.Supporting Apple Event RecordingIf you make your application scriptable, you may also want to make it recordable. Users of recordable applications can record their actions in the form of Apple events that a scripting component translates into a script. When a user executes a recorded script, the scripting component sends the same Apple events to the application in which they were recorded.To make your application recordable, you should use Apple events to report user actions to the Apple Event Manager in terms of Apple events. One way to do this is to separate the code that implements your application’s user interface from the code that actually performs work when the user manipulates the interface. This is called factoring your application. A factored application acts as both the client and server application for Apple events it sends to itself in response to user actions. When recording is turned on, the Apple Event Manager sends a copy of every event than an application sends to itself to the scripting component or other process that turned recording on.The chapter “Introduction to Scripting” in this book provides an overview of how to make your application both scriptable and recordable. The chapter “Recording Apple Events” describes how to factor your application for recording and explains the Apple Event Manager’s recording mechanism.Listing 4-0Table 4-0Responding to Apple EventsContentsHandling Apple Events4-4Accepting an Apple Event4-5Installing Entries in the Apple Event Dispatch Tables4-7Installing Entries for the Required Apple Events4-8Installing Entries for Apple Events Sent by the Edition Manager4-9How Apple Event Dispatching Works4-9Handling the Required Apple Events4-11Required Apple Events4-11Handling the Open Application Event4-14Handling the Open Documents Event4-15Handling the Print Documents Event4-17Handling the Quit Application Event4-19Handling Apple Events Sent by the Edition Manager4-20The Section Read, Section Write, and Section Scroll Events4-21Handling the Create Publisher Event4-22Getting Data Out of an Apple Event4-25Getting Data Out of an Apple Event Parameter4-26Getting Data Out of an Attribute4-28Getting Data Out of a Descriptor List4-31Writing Apple Event Handlers4-33Replying to an Apple Event4-36Disposing of Apple Event Data Structures4-39Writing and Installing Coercion Handlers4-41Interacting With the User4-45Setting the Client Application’s User Interaction Preferences4-46Setting the Server Application’s User Interaction Preferences4-48Requesting User Interaction4-49Reference to Responding to Apple Events4-56Data Structures Used by the Apple Event Manager4-56Descriptor Records and Related Data Structures4-56Apple Event Array Data Types4-60Routines for Responding to Apple Events4-61Creating and Managing the Apple Event Dispatch Tables4-61Dispatching Apple Events4-66Getting Data or Descriptor Records Out of Apple Event Parameters and Attributes4-68Counting the Items in Descriptor Lists4-74Getting Items From Descriptor Lists4-74Getting Data and Keyword-Specified Descriptor Records Out of AE Records4-78Requesting User Interaction4-81Requesting More Time to Respond to Apple Events4-84Suspending and Resuming Apple Event Handling4-85Getting the Sizes and Descriptor Types of Descriptor Records4-89Deleting Descriptor Records4-92Deallocating Memory for Descriptor Records4-93Coercing Descriptor Types4-94Creating and Managing the Coercion Handler Dispatch Tables4-96Creating and Managing the Special Handler Dispatch Tables4-99Getting Information About the Apple Event Manager4-103Application-Defined Routines4-104Summary of Responding to Apple Events4-108Pascal Summary4-108Constants4-108Data Types4-112Routines for Responding to Apple Events4-114Application-Defined Routines4-118C Summary4-118Constants4-118Data Types4-123Routines for Responding to Apple Events4-124Application-Defined Routines4-128Assembly-Language Summary4-128Trap Macros4-128Result Codes4-130Responding to Apple EventsThis chapter describes how your application can use the Apple Event Manager to respond to Apple events. Your application must be able to respond to the four required Apple events to take advantage of the launching and terminating mechanisms that are part of System 7 and later versions of system software. If your application provides publish and subscribe capabilities, it should also handle the events sent by the Edition Manager. To be scriptable, or capable of responding to Apple events sent by scripting components, your application should handle the appropriate core and functional-area Apple events.Before you read this chapter, you should be familiar with the chapters “Introduction to Interapplication Communication” and “Introduction to Apple Events” in this book. You should also have a copy of the Apple Event Registry: Standard Suites available for reference. Although the Apple events used by the Edition Manager are discussed in this chapter, you must refer to the chapter “Edition Manager” in this book for a full discussion of how to implement the Edition Manager’s publish and subscribe features.This chapter provides the basic information you need to make your application capable of responding to Apple events. To respond to core and functional-area Apple events, your application must also be able to resolve object specifier records. You should read the chapter “Resolving and Creating Object Specifier Records” before you write Apple event handlers for events that can contain object specifier records.The section “Handling Apple Events,” which begins on page 4-4, describes how ton    accept and process Apple eventsn    install entries in the Apple event dispatch tablesn    handle the required eventsn    handle events sent by the Edition Managern    get data out of an Apple eventn    write handlers that perform the action requested by an Apple eventn    reply to an Apple eventn    dispose of Apple event data structuresn    write and install coercion handlersThe section “Interacting With the User,” which begins on page 4-45, describes n    how a server application can interact with the user when processing an Apple eventn    how client applications set user interaction preferencesn    how the client application’s preferences and the server application’s preferences affect user interactionHandling Apple EventsYou do not need to implement all Apple events at once. If you want to begin by supporting only the required Apple events, you mustn    set bits in the 'SIZE' resource to indicate that your application supports high-level eventsn    include code to handle high-level events in your main event loopn    write routines that handle the required eventsn    install entries for the required Apple events in your application’s Apple event dispatch table The following sections explain how to perform these tasks: “Accepting an Apple Event,” which begins on page 4-5, “Installing Entries in the Apple Event Dispatch Tables,” which begins on page 4-7, and “Handling the Required Apple Events,” which begins on page 4-11.To respond to the Apple events sent by the Edition Manager in addition to the required events, you must install entries for the Section Read, Section Write, Section Scroll, and Create Publisher events in your application’s Apple event dispatch table and write the corresponding handlers, as described in “Handling Apple Events Sent by the Edition Manager” on page 4-20. To respond to core and functional-area Apple events, you must install entries and write handlers for those events. You must also make sure that your application can locate Apple event objects with the aid of the Apple Event Manager routines described in the chapter “Resolving and Creating Object Specifier Records.” These routines are currently available as the Object Support Library (OSL), which you must link with your application when you build it. The Apple Event Manager (excluding the OSL) is available only in System 7 and later versions of system software. Use the Gestalt function with the gestaltAppleEventsAttr selector to determine whether the Apple Event Manager is available. In the response parameter, the bit defined by the constant gestaltAppleEventsPresent is set if the Apple Event Manager is available.CONST        gestaltAppleEventsAttr  = 'evnt';                                                {Gestalt selector}        gestaltAppleEventsPresent = 0;                                                {if this bit is set, }                                                         { then the Apple Event }                                                        { Manager is available}To find out which version of the Apple Event Manager is available, you can use the AEManagerInfo function; for more information, see page 4-104.Accepting an Apple EventTo accept or send Apple events (or any other high-level events), you must set the appropriate flags in your application’s 'SIZE' resource and include code to handle high-level events in your application’s main event loop. Two flags in the 'SIZE' resource determine whether an application receives high-level events: n    The isHighLevelEventAware flag must be set for your application to receive any high-level events.n    The localAndRemoteHLEvents flag must be set for your application to receive high-level events sent from another computer on the network.Note that in order for your application to respond to Apple events sent from remote computers, the user of your application must also allow network users to link to your application. The user does this by selecting your application in the Finder, choosing Sharing from the File menu, and clicking the Allow Remote Program Linking checkbox. If the user has not yet started program linking, the Sharing command offers to display the Sharing Setup control panel so that the user can start program linking. The user must also authorize remote users for program linking by using the Users & Groups control panel. Program linking and setting up authenticated sessions are described in the chapter “Program-to-Program Communications Toolbox” in this book.For a complete description of the 'SIZE' resource, see the chapter “Event Manager” in Inside Macintosh: Macintosh Toolbox Essentials. Apple events (and other high-level events) are identified by a message class of kHighLevelEvent in the what field of the event record. You can test the what field of the event record to determine whether the event is a high-level event.Listing 4-1 is an example of a procedure called from an application’s main event loop to handle events, including high-level events. The procedure determines the type of event received and then calls another routine to take the appropriate action.Listing 4-1    A DoEvent procedurePROCEDURE DoEvent (event: EventRecord);BEGIN                    CASE event.what OF                                    {determine the type of event}        mouseDown:            DoMouseDown (event);        .        . {handle other kinds of events}        .        {handle high-level events, including Apple events}        kHighLevelEvent: DoHighLevelEvent (event);    END;END; Listing 4-2 is an example of a procedure that handles both Apple events and the high-level event identified by the event class mySpecialHLEventClass and the event ID mySpecialHLEventID. Note that, in most cases, you should use Apple events to communicate with other applications. Listing 4-2    A DoHighLevelEvent procedure for handling Apple events and other high-level eventsPROCEDURE DoHighLevelEvent (event: EventRecord);VAR    myErr: OSErr;BEGIN    IF (event.message = LongInt(mySpecialHLEventClass)) AND        (LongInt(event.where) = LongInt(mySpecialHLEventID))     THEN        {it's a high-level event that doesn't use AEIMP}        myErr := HandleMySpecialHLEvent(event)    ELSE        {otherwise, assume that the event is an Apple event}        myErr := AEProcessAppleEvent(event);        {check and handle error}    IF myErr <> noErr THEN DoError(myErr);END;If your application accepts high-level events that do not follow the Apple Event Interprocess Messaging Protocol (AEIMP), you must dispatch these high-level events before calling AEProcessAppleEvent. To dispatch high-level events that do not follow AEIMP, you should check the event class, the event ID, or both for each event to see whether your application can handle the event. After receiving a high-level event (and, if appropriate, checking whether it is a high-level event other than an Apple event), your application typically calls the AEProcessAppleEvent function. The AEProcessAppleEvent function determines the type of Apple event received, gets the event buffer that contains the parameters and attributes of the Apple event, and calls the corresponding Apple event handler in your application.You should provide an Apple event handler for each Apple event that your application supports. This handler is responsible for performing the action requested by the Apple event and if necessary can return data in the reply Apple event. If the client application requests a reply, the Apple Event Manager passes a default reply Apple event to your handler. If the client application does not request a reply, the Apple Event Manager passes a null descriptor record (a descriptor record of descriptor type typeNull and a data handle whose value is NIL) to your handler instead of a default reply Apple event.After your handler finishes processing the Apple event and adds any parameters to the reply Apple event, it must return a result code to AEProcessAppleEvent. If the client application is waiting for a reply, the Apple Event Manager returns the reply Apple event to the client.Installing Entries in the Apple Event Dispatch TablesWhen your application receives an Apple event, use the AEProcessAppleEvent function to retrieve the data buffer of the event and to route the Apple event to the appropriate Apple event handler in your application. Your application supplies an Apple event dispatch table to map the Apple events your application supports to the Apple event handlers provided by your application.To install entries in your application’s Apple event dispatch table, use the AEInstallEventHandler function. You usually install entries for all of the Apple events that your application accepts into your application’s Apple event dispatch table. To install an Apple event handler in your Apple event dispatch table, you must specifyn    the event class of the Apple eventn    the event ID of the Apple eventn    the address of the Apple event handler for the Apple eventn    a reference constantYou provide this information to the AEInstallEventHandler function. In addition, you indicate whether the entry should be added to your application’s Apple event dispatch table or to the system Apple event dispatch table. The system Apple event dispatch table is a table in the system heap that contains system Apple event handlers—handlers that are available to all applications and processes running on the same computer. The handlers in your application’s Apple event dispatch table are available only to your application. If AEProcessAppleEvent cannot find a handler for the Apple event in your application’s Apple event dispatch table, it looks in the system Apple event dispatch table for a handler (see “How Apple Event Dispatching Works” on page 4-9 for details). If it doesn’t find a handler for the event, it returns the errAEEventNotHandled result code. If you add a handler to the system Apple event dispatch table, the handler should reside in the system heap. If there was already an entry in the system Apple event dispatch table for the same event class and event ID, it is replaced unless you chain it to your system handler. See “Creating and Managing the Apple Event Dispatch Tables” on page 4-61 for details.Installing Entries for the Required Apple EventsListing 4-3 illustrates how to add entries for the required Apple events to your application’s Apple event dispatch table.Listing 4-3    Adding entries for the required Apple events to an application’s Apple event dispatch tablemyErr := AEInstallEventHandler(kCoreEventClass,                                          kAEOpenApplication,                                          @MyHandleOApp, 0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallEventHandler(kCoreEventClass,                                          kAEOpenDocuments,                                          @MyHandleODoc,0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallEventHandler(kCoreEventClass,                                          kAEPrintDocuments,                                          @MyHandlePDoc, 0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallEventHandler(kCoreEventClass,                                         kAEQuitApplication,                                         @MyHandleQuit, 0, FALSE); IF myErr <> noErr THEN DoError(myErr);  The code in Listing 4-3 creates entries for all four required Apple events in the Apple event dispatch table. (For examples of handlers that correspond to these entries, see “Handling the Required Apple Events,” which begins on page 4-11.) The first entry creates an entry for the Open Application event. The entry indicates the event class and event ID of the Open Application event, supplies the address of the handler for that event, and specifies 0 as the reference constant. The Apple Event Manager passes the reference constant to your handler each time your handler is called. Your application can use this reference constant for any purpose. If your application doesn’t use the reference constant, use 0 as the value. The last parameter to the AEInstallEventHandler function is a Boolean value that determines whether the entry is added to the system Apple event dispatch table or to your application’s Apple event dispatch table. To add the entry to your application’s Apple event dispatch table, use FALSE as the value of this parameter. If you specify TRUE, the entry is added to the system Apple event dispatch table. The code shown in Listing 4-3 adds entries to the application’s Apple event dispatch table.Installing Entries for Apple Events Sent by the Edition ManagerIf your application supports the Edition Manager, you should also add entries to your application’s Apple event dispatch table for the Apple events that your application receives from the Edition Manager. Listing 4-4 shows how to add these entries.Listing 4-4    Adding entries for Apple events sent by the Edition Manager to an application’s Apple event dispatch tablemyErr := AEInstallEventHandler(sectionEventMsgClass,                                          sectionReadMsgID,                                          @MyHandleSectionReadEvent,                                          0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallEventHandler(sectionEventMsgClass,                                          sectionWriteMsgID,                                          @MyHandleSectionWriteEvent,                                          0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallEventHandler(sectionEventMsgClass,                                            sectionScrollMsgID,                                          @MyHandleSectionScrollEvent,                                          0, FALSE);IF myErr <> noErr THEN DoError(myErr);See “Handling Apple Events Sent by the Edition Manager” on page 4-20 for the parameters associated with these events. See the chapter “Edition Manager” in this book for information on how your application should respond to the Apple events sent by the Edition Manager. How Apple Event Dispatching WorksIn addition to the Apple event handler dispatch tables, applications can add entries to a special handler dispatch table in either the application heap or the system heap. These dispatch tables are used for various specialized handlers; for more information, see “Creating and Managing the Special Handler Dispatch Tables,” which begins on page 4-99. When an application calls AEProcessAppleEvent, the function looks first in the application’s special handler dispatch table for an entry that was installed with the constant keyPreDispatch. If the application’s special handler dispatch table does not include such a handler or if the handler returns errAEEventNotHandled, the function looks in the application’s Apple event dispatch table for an entry that matches the event class and event ID of the specified Apple event. If the application’s Apple event dispatch table does not include such a handler or if the handler returns errAEEventNotHandled, the AEProcessAppleEvent function looks in the system special handler dispatch table for an entry that was installed with the constant keyPreDispatch. If the system special handler dispatch table does not include such a handler or if the handler returns errAEEventNotHandled, the function looks in the system Apple event dispatch table for an entry that matches the event class and event ID of the specified Apple event. If the system Apple event dispatch table does not include such a handler, the Apple Event Manager returns the result code errAEEventNotHandled to the server application and, if the client application is waiting for a reply, to the client application.sWARNINGBefore an application calls a system Apple event handler, system software has set up the A5 register for the calling application. For this reason, if you provide a system Apple event handler, it should never use A5 global variables or anything that depends on a particular context; otherwise, the application that calls the system handler may crash.sFor any entry in your Apple event dispatch table, you can specify a wildcard value for the event class, event ID, or both. You specify a wildcard by supplying the typeWildCard constant when installing an entry into the Apple event dispatch table. A wildcard value matches all possible values. Wildcards make it possible to supply one Apple event handler that dispatches several related Apple events. For example, if you specify an entry with the typeWildCard event class and the kAEOpenDocuments event ID, the Apple Event Manager dispatches Apple events of any event class with an event ID of kAEOpenDocuments to the handler for that entry. If you specify an entry with the kCoreEventClass event class and the typeWildCard event ID, the Apple Event Manager dispatches Apple events of the kCoreEventClass event class with any event ID to the handler for that entry. If you specify an entry with the typeWildCard event class and the typeWildCard event ID, the Apple Event Manager dispatches all Apple events of any event class and any event ID to the handler for that entry.If an Apple event dispatch table contains one entry for an event class and a specific event ID, and also contains another entry that is identical except that it specifies a wildcard value for either the event class or the event ID, the Apple Event Manager dispatches the more specific entry. For example, if an Apple event dispatch table includes one entry that specifies the event class as kAECoreSuite and the event ID as kAEDelete, and another entry that specifies the event class as kAECoreSuite and the event ID as typeWildCard, the Apple Event Manager will dispatch the Apple event handler associated with the entry that specifies the event ID as kAEDelete. IMPORTANTIMPORTANTIf your application sends Apple events to itself using a typeProcessSerialNumber address descriptor record with the lowLongOfPSN field set to kCurrentProcess, the Apple Event Manager jumps directly to the appropriate Apple event handler without going through the normal event-processing sequence. For this reason, your application will not appear to run more slowly when it sends Apple events to itself. For more information, see “Addressing an Apple Event for Direct Dispatching” on page 5-13.s Handling the Required Apple EventsThis section describes the required Apple events—the Apple events your application must support to be compatible with System 7 and later versions of system software—and the descriptor types for all parameters of the required Apple events. It also describes how to write the handlers for these events, and it provides sample code.To support the required Apple events, you must set the necessary flags in the 'SIZE' resource of your application, install entries in your application’s Apple event dispatch table, add code to the event loop of your application to recognize high-level events, and call the AEProcessAppleEvent function, as described in “Accepting an Apple Event,” which begins on page 4-5, and “Installing Entries in the Apple Event Dispatch Tables,” which begins on page 4-7. You must also write handlers for each Apple event; this section describes how to write these handlers.Required Apple EventsWhen a user opens or prints a file from the Finder, the Finder sets up the information your application uses to determine which files to open or print. In System 7 and later versions, if your application supports high-level events, the Finder communicates this information to your application through the required Apple events. The Finder sends these required Apple events to your application to request the corresponding actions:Apple event    Requested action    Open Application    Perform tasks your application normally performs when a user opens your application without opening or printing any documents    Open Documents    Open the specified documents     Print Documents    Print the specified documents    Quit Application    Perform tasks—such as releasing memory, requesting the user to save documents, and so on—associated with quitting before the Finder terminates your application    In System 7 and later versions, the Finder uses these events as part of the mechanisms for launching and terminating applications. When the Finder launches your application, the application receives the Open Application, Open Documents, or Print Documents event. When the Finder terminates your application, the application receives the Quit Application event. This method of communicating Finder information to your application replaces the mechanisms used in earlier versions of system software.Applications that do not support high-level events can still use the CountAppFiles, GetAppFiles, and ClrAppFiles procedures (or the GetAppParms procedure) to get the Finder information. See the chapter “Introduction to File Management” in Inside Macintosh: Files for information on these routines. To make your application compatible with System 7 and with earlier and later versions, you must support both the old and new mechanisms.Use the Gestalt function to determine whether the Apple Event Manager is present. If it is and the isHighLevelEventAware flag is set in your application’s 'SIZE' resource, your application receives the Finder information through the required Apple events. If your application accepts high-level events, it must be able to process the four required Apple events. Your application receives the required Apple events from the Finder in these situations:n    If your application is not open and the user opens your application from the Finder without opening or printing any documents, the Finder launches your application and sends it the Open Application event.n    If your application is not open and the user opens one of your application’s documents from the Finder, the Finder launches your application and sends it the Open Documents event.n    If your application is not open and the user prints one of your application’s documents from the Finder, the Finder launches your application and sends it the Print Documents event. Your application should print the selected documents and remain open until it receives a Quit Application event from the Finder.n    If your application is open and the user opens or prints any of your application’s documents from the Finder, the Finder sends your application the Open Documents or Print Documents event.n    If your application is open and the user chooses Restart or Shut Down from the Finder’s Special menu, the Finder sends your application the Quit Application event.Upon receiving any of the required Apple events, your application should perform the action requested by the event. Here is a summary of the contents of the required events and the actions they request applications to perform:Open Application—perform tasks associated with opening an application         Event class    kCoreEventClass    Event ID    kAEOpenApplication    Parameters    None    Requested action    Perform any tasks—such as opening an untitled document window—that you would normally perform when a user opens your application without opening or printing any documents.    Open Documents—open the specified documents            Event class        kCoreEventClass    Event ID        kAEOpenDocuments    Required parameter                Keyword:    keyDirectObject        Descriptor type:    typeAEList        Data:    A list of alias records for the documents to be opened    Requested action        Open the documents specified in the keyDirectObject parameter.    Print Documents—print the specified documents            Event class        kCoreEventClass    Event ID        kAEPrintDocuments    Required parameter                Keyword:    keyDirectObject        Descriptor type:    typeAEList        Data:    A list of alias records for the documents to be printed    Requested action        Print the documents specified in the keyDirectObject parameter without opening windows for the documents.     Quit Application—perform tasks associated with quitting(continued)        Event class    kCoreEventClass    Event ID    kAEQuitApplication    Parameters    None    Requested action    Perform any tasks that your application would normally perform when the user chooses Quit. Such tasks typically include asking the user whether to save documents that have been changed. When appropriate, the Finder sends this event to an application immediately after sending it a Print Documents event (unless the application was already open) or if the user chooses Restart or Shut Down from the Finder’s Special menu.    Your application needs to recognize only two descriptor types to handle the required Apple events: descriptor lists and alias records. The Open Documents event and Print Documents event use descriptor lists to store a list of documents to open. Each document is specified as an alias record in the descriptor list. You can retrieve the data that specifies the document to open as an alias record, or you can request that the Apple Event Manager coerce the alias record to a file system specification (FSSpec) record. The file system specification record provides a standard method of identifying files in System 7 and later versions. See Inside Macintosh: Files for a complete description of how to specify files using file system specification records.Handling the Open Application EventWhen the user opens your application, the Finder uses the Process Manager to launch your application. On startup, your application typically performs any needed initialization, and then begins to process events. If your application supports high-level events, and if the user opens your application without selecting any documents to open or print, your application receives the Open Application event.To handle the Open Application event, your application should do just what the user expects it to do when it is opened. For example, your application might open a new untitled window in response to an Open Application event.Listing 4-5 shows a handler that processes the Open Application event. This handler first calls an application-defined function called MyGotRequiredParams, which checks whether the Apple event contains any required parameters. If so, the handler returns an error, because by definition, the Open Application event should not contain any required parameters. Otherwise, the handler opens a new document window.Listing 4-5    A handler for the Open Application eventFUNCTION MyHandleOApp (theAppleEvent, reply: AppleEvent;                                handlerRefcon: LongInt): OSErr;VAR    myErr: OSErr;BEGIN    myErr := MyGotRequiredParams(theAppleEvent);    IF myErr = noErr THEN         DoNew;    MyHandleOApp := myErr;END;For a description of the MyGotRequiredParams function, see Listing 4-11 on page 4-35. For information about the reply and handlerRefcon parameters for an Apple event handler, see “Writing Apple Event Handlers” on page 4-33. Handling the Open Documents EventTo handle the Open Documents event, your application should open the documents that the Open Documents event specifies in its direct parameter. Your application extracts this information and then opens the specified documents. Listing 4-6 shows a handler for the Open Documents event. Listing 4-6    A handler for the Open Documents eventFUNCTION MyHandleODoc (theAppleEvent, reply: AppleEvent;                                  handlerRefcon: LongInt): OSErr;VAR    myFSS:                              FSSpec;    docList:                              AEDescList;    myErr, ignoreErr:                              OSErr;    index, itemsInList:                            LongInt;    actualSize:                              Size;    keywd:                              AEKeyword;    returnedType:                              DescType;BEGIN    {get the direct parameter--a descriptor list--and put it }    { into docList}    myErr := AEGetParamDesc(theAppleEvent, keyDirectObject,                                    typeAEList, docList);    IF myErr = noErr THEN     BEGIN        {check for missing required parameters}        myErr := MyGotRequiredParams(theAppleEvent);        IF myErr = noErr THEN         BEGIN            {count the number of descriptor records in the list}            myErr := AECountItems (docList, itemsInList);            IF myErr = noErr THEN                {now get each descriptor record from the list, }                { coerce the returned data to an FSSpec record, and }                { open the associated file}                FOR index := 1 TO itemsInList DO                BEGIN                    myErr := AEGetNthPtr(docList, index, typeFSS,                                                 keywd, returnedType, @myFSS,                                                 Sizeof(myFSS),actualSize);                    IF myErr = noErr THEN                    BEGIN                        myErr := MyOpenFile(@myFSS);                        IF myErr <> noErr THEN                             ; {handle error from MyOpenFile}                    END                    ELSE                        ; {handle error from AEGetNthPtr}                END; {of For index Do}        END        ELSE            ; {handle error from MyGotRequiredParams}        ignoreErr := AEDisposeDesc(docList);    END    ELSE        ; {failed to get direct parameter, handle error}    MyHandleODoc := myErr;END;The handler in Listing 4-6 first uses the AEGetParamDesc function to get the direct parameter (specified by the keyDirectObject keyword) out of the Apple event. The handler requests that AEGetParamDesc return a descriptor list in the docList variable. The handler then checks that it has retrieved all of the required parameters by calling the MyGotRequiredParams function. (See Listing 4-11 on page 4-35 for a description of this function.)Once the handler has retrieved the descriptor list from the Apple event, it uses AECountItems to count the number of descriptors in the list. Using the returned number as an index, the handler can get the data of each descriptor record in the list. This handler requests that the AEGetNthPtr function coerce the data in the descriptor record to a file system specification record. The handler can then use the file system specification record as a parameter to its own routine for opening files.For more information on the AEGetParamDesc function, see page 4-69. For more information on the AEGetNthPtr and AECountItems functions, see “Getting Data Out of a Descriptor List” on page 4-31.After extracting the file system specification record that describes the document to open, your application can use this record to open the file. For example, in Listing 4-6, the code passes the file system specification record to its routine for opening files, the MyOpenFile function. The MyOpenFile function should be designed so that it can be called in response to both the Open Documents event and to events generated by the user. For example, when the user chooses Open from the File menu, the code that handles the mouse-down event uses the StandardGetFile procedure to let the user choose a file; it then calls MyOpenFile, passing the file system specification record returned by StandardGetFile. By isolating code that performs a requested action from code that interacts with the user, you can easily adapt your application to handle Apple events that request the same action. Note the use of the AEDisposeDesc function to dispose of the descriptor list when your handler no longer requires the data in it. Your handler should also return a result code.Handling the Print Documents EventTo handle the Print Documents event, your application should extract information about the documents to be printed from the direct parameter, then print the specified documents. If your application can interact with the user, it should open windows for the documents, display a Print dialog box for the first document, and use the settings entered by the user for the first document to print all the documents. If user interaction is not allowed, your application may either return the error errAENoUserInteraction or print the documents using default settings. See “Interacting With the User,” which begins on page 4-45, for information about using the AEInteractWithUser function to interact with the user. Note that your application can remain open after processing the Print Documents event; when appropriate, the Finder sends your application a Quit Application event immediately after sending it a Print Documents event.The handler for the Print Documents event shown in Listing 4-7 is similar to the handler for the Open Documents event, except that it prints the documents referred to in the direct parameter.Listing 4-7    A handler for the Print Documents eventFUNCTION MyHandlePDoc (theAppleEvent, reply: AppleEvent;                               handlerRefcon: LongInt): OSErr;VAR    myFSS:                              FSSpec;    docList:                              AEDescList;    myErr, ignoreErr:                              OSErr;    index, itemsInList:                            LongInt;    actualSize:                              Size;    keywd:                              AEKeyword;    returnedType:                              DescType;BEGIN    {get the direct parameter--a descriptor list--and put it }    { into docList}    myErr := AEGetParamDesc(theAppleEvent, keyDirectObject,                                    typeAEList, docList);    IF myErr = noErr THEN     BEGIN        {check for missing required parameters}        myErr := MyGotRequiredParams(theAppleEvent);        IF myErr = noErr THEN         BEGIN            {count the number of descriptor records in the list}            myErr := AECountItems (docList, itemsInList);            IF myErr = noErr THEN                {now get each descriptor record from the list, }                { coerce the returned data to an FSSpec record, and }                { print the associated file}                FOR index := 1 TO itemsInList DO                BEGIN                    myErr := AEGetNthPtr(docList, index, typeFSS,                                                 keywd, returnedType, @myFSS,                                                 Sizeof(myFSS), actualSize);                    IF myErr = noErr THEN                    BEGIN                        myErr := MyPrintFile(@myFSS);                        IF myErr <> noErr THEN                             ; {handle error from MyOpenFile}                    END                    ELSE                        ; {handle error from AEGetNthPtr}                END; {of For index Do}        END        ELSE            ; {handle error from MyGotRequiredParams}        ignoreErr := AEDisposeDesc(docList);    END    ELSE        ; {failed to get direct parameter, handle error}    MyHandlePDoc := myErr;END;Handling the Quit Application EventTo handle the Quit Application event, your application should take any actions that are necessary before it is terminated (such as saving any open documents). Listing 4-8 shows an example of a handler for the Quit Application event.When appropriate, the Finder sends your application a Quit Application event immediately after a Print Documents event. The Finder also sends your application a Quit Application event if the user chooses Restart or Shut Down from the Finder’s Special menu. Listing 4-8    A handler for the Quit Application eventFUNCTION MyHandleQuit (theAppleEvent, reply: AppleEvent;                               handlerRefcon: LongInt): OSErr;VAR    myErr:                    OSErr;    userCanceled:                    Boolean;BEGIN    {check for missing required parameters}    myErr := MyGotRequiredParams(theAppleEvent);    IF myErr = noErr THEN     BEGIN        userCanceled := MyPrepareToTerminate;        IF userCanceled THEN            MyHandleQuit := kUserCanceled        ELSE            MyHandleQuit := noErr;    END    ELSE        MyHandleQuit := myErr;END;The handler in Listing 4-8 calls another function supplied by the application, the MyPrepareToTerminate function. This function saves the documents for any open windows and returns a Boolean value that indicates whether the user canceled the Quit operation. This is another example of isolating code for interacting with the user from the code that performs the requested action. By structuring your application in this way, you can use the same routine to respond to a user action (such as choosing the Quit command from the File menu) or to the corresponding Apple event. (For a description of the MyGotRequiredParams function, see “Writing Apple Event Handlers” on page 4-33.)IMPORTANTWhen your application is ready to quit, it should call the ExitToShell procedure from the main event loop, not from your handler for the Quit Application event. Your application should quit only after the handler returns noErr as its function result.sHandling Apple Events Sent by the Edition ManagerIf your application provides publish and subscribe capabilities, it should handle the Apple events sent by the Edition Manager in addition to the required Apple events. Your application should also handle the Create Publisher event, which is described in the “Handling the Create Publisher Event” section on page 4-22.The Edition Manager sends your application Apple events to communicate information about the publishers and subscribers in your application’s documents. Specifically, the Edition Manager uses Apple events to notify your application n    when the information in an edition is updatedn    when your application needs to write the data from a publisher to an editionn    when your application should locate a particular publisher and scroll through the document to that locationThe Section Read, Section Write, and Section Scroll EventsThe following descriptions identify the three Apple events sent by the Edition Manager—Section Read, Section Write, and Section Scroll—and the actions they tell applications to perform.Section Read—read information into the specified section (continued)            Event class        SectionEventMsgClass    Event ID        SectionReadMsgID    Required parameter                Keyword:    keyDirectObject        Descriptor type:    typeSectionH        Data:    A handle to the section record of the subscriber whose edition contains updated information    Requested action        Update the subscriber with the new information from the edition.    Section Write—write the specified section to an edition            Event class        SectionEventMsgClass    Event ID        SectionWriteMsgID    Required parameter                Keyword:    keyDirectObject        Descriptor type:    typeSectionH        Data:    A handle to the section record of the publisher    Requested action        Write the publisher’s data to its edition.    Section Scroll—scroll through the document to the specified section            Event class        SectionEventMsgClass    Event ID        SectionScrollMsgID    Required parameter                Keyword:    keyDirectObject        Descriptor type:    typeSectionH        Data:    A handle to the section record of the publisher to scroll to    Requested action        Scroll through the document to the publisher identified by the specified section record.     See the chapter “Edition Manager” in this book for details on how your application should respond to these events.Handling the Create Publisher EventIf your application supports publish and subscribe capabilities, it should also handle the Create Publisher event.Create Publisher—create a publisher            Event class        kAEMiscStdSuite    Event ID        kAECreatePublisher    Required parameter        None    Optional parameter                Keyword:    keyDirectObject        Descriptor type:    typeObjectSpecifier        Data:    An object specifier record that specifies the Apple event object or objects to publish. If this parameter is omitted, publish the current selection.    Optional parameter                Keyword:    keyAEEditionFileLoc        Descriptor type:    typeAlias        Data:    An alias record that contains the location of the edition container to create. If this parameter is omitted, use the default edition container.    Requested action        Create a publisher for the specified data using the specified loca-tion for the edition container. If the data isn’t specified, publish the current selection. If the location of the edition isn’t specified, use the default location.       When your application receives the Create Publisher event, it should create a publisher and write the publisher’s data to an edition. The data of the publisher, and the location and name of the edition, are defined by the Apple event. If the Create Publisher event includes a keyDirectObject parameter, then your application should publish the data contained in the parameter. If the keyDirectObject parameter is missing, then your application should publish the current selection. If the document doesn’t have a current selection, your handler for the event should return a nonzero result code.If the Create Publisher event includes a keyAEEditionFileLoc parameter, your application should use the location and name contained in the parameter as the default location and name of the edition. If the keyAEEditionFileLoc parameter is missing, your application should use the default location and name your application normally uses to specify the edition container.Listing 4-9 shows a handler for the Create Publisher event. This handler checks for the keyDirectObject parameter and the keyAEEditionFileLoc parameter. If either of these is not specified, the handler uses default values. The handler uses the application-defined function DoNewPublisher to create the publisher and its edition, create a section record, and update other data structures associated with the document. See the chapter “Edition Manager” in this book for an example of the DoNewPublisher function.Listing 4-9    A handler for the Create Publisher eventFUNCTION MyHandleCreatePublisherEvent (theAppleEvent,                                                    reply: AppleEvent;                                                     handlerRefcon: LongInt)                                                    : OSErr;VAR            myErr:                                 OSErr;    returnedType:                                DescType;    thePublisherDataDesc:                                AEDesc;    actualSize:                                 LongInt;    promptForDialog:                                Boolean;    thisDocument:                                 MyDocumentInfoPtr;    preview:                                 Handle;     previewFormat:                                 FormatType;     defaultLocation:                                 EditionContainerSpec;BEGIN    MyGetDocumentPtr(thisDocument);    myErr := AEGetParamDesc(theAppleEvent, keyDirectObject,                                     typeObjectSpecifier,                                     thePublisherDataDesc);    CASE myErr OF        errAEDescNotFound:         BEGIN            {use the current selection as the publisher and set up }            { info for later when DoNewPublisher displays preview}            preview := MyGetPreviewForSelection(thisDocument);            previewFormat := 'TEXT';        END;        noErr:             {use the data in keyDirectObject parameter as the }            { publisher (which is returned in the }            { thePublisherDataDesc variable), and set up info for }            { later when DoNewPublisher displays preview}            MySetInfoForPreview(thePublisherDataDesc, thisDocument,                                        preview, previewFormat);        OTHERWISE        BEGIN            MyHandleCreatePublisherEvent := myErr;            Exit(MyHandleCreatePublisherEvent);        END;     END;    myErr := AEDisposeDesc(thePublisherDataDesc);    myErr := AEGetParamPtr(theAppleEvent, keyAEEditionFileLoc,                                  typeFSS, returnedType,                                  @defaultLocation.theFile,                                 SizeOf(FSSpec), actualSize);    CASE myErr OF        errAEDescNotFound:             {use the default location as the edition container}                myErr := MyGetDefaultEditionSpec(thisDocument,                                                             defaultLocation);        noErr:         BEGIN                        {the keyAEEditionFileLoc parameter }                                { contains a default location}            defaultLocation.thePart := kPartsNotUsed;            defaultLocation.theFileScript := smSystemScript;        END;        OTHERWISE        BEGIN            MyHandleCreatePublisherEvent := myErr;            Exit(MyHandleCreatePublisherEvent);        END;     END;    myErr := MyGotRequiredParams(theAppleEvent);    IF myErr <> noErr THEN    BEGIN        MyHandleCreatePublisherEvent := myErr;        Exit(MyHandleCreatePublisherEvent);    END;    myErr := AEInteractWithUser(kAEDefaultTimeout, gMyNotifyRecPtr,                                             @MyIdleFunction);    IF myErr = noErr THEN promptForDialog := TRUE                          ELSE promptForDialog := FALSE;    myErr := DoNewPublisher(thisDocument, promptForDialog,                                     preview, previewFormat,                                     defaultLocation);    {add keyErrorNumber and keyErrorString parameters if desired}END;Note that the MyHandleCreatePublisherEvent handler in Listing 4-9 uses the AEInteractWithUser function to determine whether user interaction is allowed. If so, the handler sets the promptForDialog variable to TRUE, indicating that the DoNewPublisher function should display the publisher dialog box. If not, the handler sets the promptForDialog variable to FALSE, and the DoNewPublisher function does not prompt the user for the location or name of the edition. For more information about AEInteractWithUser, see “Interacting With the User,” which begins on page 4-45.  Getting Data Out of an Apple EventThe Apple Event Manager stores the parameters and attributes of an Apple event in a format that is internal to the Apple Event Manager. You use Apple Event Manager functions to retrieve the data from an Apple event and return it to your application in a format your application can use.Most of the functions that retrieve data from Apple event parameters and attributes are available in two forms: one that returns the desired data in a specified buffer and one that returns a descriptor record containing the same data. For example, the AEGetParamPtr function uses a specified buffer to return the data contained in an Apple event parameter, and the AEGetParamDesc function returns the descriptor record for a specified parameter. You can also use Apple Event Manager functions to get data out of descriptor records, descriptor lists, and AE records. You use similar functions to put data into descriptor records, descriptor lists, and AE records.When your handler receives an Apple event, you typically use the AEGetParamPtr, AEGetAttributePtr, AEGetParamDesc, or AEGetAttributeDesc function to get the data out of the Apple event.Some Apple Event Manager functions let your application request that the data be returned using any descriptor type, even if it is different from the original descriptor type. If the original data is of a different descriptor type, the Apple Event Manager attempts to coerce the data to the requested descriptor type. For example, the AEGetParamPtr function lets you specify the desired descriptor type of the resulting data as follows:VAR    theAppleEvent:                        AppleEvent;    returnedType:                         DescType;    multResult:                        LongInt;    actualSize:                         Size;    myErr:                         OSErr;myErr := AEGetParamPtr(theAppleEvent, keyMultResult,                               typeLongInteger, returnedType,                               @multResult, SizeOf(multResult),                              actualSize);In this example, the desired type is specified in the third parameter by the typeLongInteger descriptor type. This requests that the Apple Event Manager coerce the data to a long integer if it is not already of this type. To prevent coercion and ensure that the descriptor type of the result is of the same type as the original, specify typeWildCard for the third parameter.The Apple Event Manager returns, in the returnedType parameter, the descriptor type of the resulting data. This is useful information when you specify typeWildCard as the desired descriptor type; you can determine the descriptor type of the resulting data by examining this parameter.The Apple Event Manager can coerce many different types of data. For example, the Apple Event Manager can convert alias records to file system specification records, integers to Boolean data types, and characters to numeric data types, in addition to other data type conversions. For a complete list of the data types for which the Apple Event Manager provides coercion handling, see Table 4-1 on page 4-43.To perform data coercions that the Apple Event Manager doesn’t perform, you can provide your own coercion handlers. See “Writing and Installing Coercion Handlers,” which begins on page 4-41, for information on providing your own coercion handlers.Apple event parameters are keyword-specified descriptor records. You can use AEGetParamDesc to get the descriptor record of a parameter, or you can use AEGetParamPtr to get the data out of the descriptor record of a parameter. If an Apple event parameter consists of an object specifier record, you can use AEResolve and your own object accessor functions to resolve the object specifier record—that is, to locate the Apple event object it describes. For more information about AEResolve and object accessor functions, see “Writing Object Accessor Functions,” which begins on page 6-28. Attributes are also keyword-specified descriptor records, and you can use similar routines to get the descriptor record of an attribute or to get the data out of an attribute.The following sections show how to use the AEGetParamPtr, AEGetAttributePtr, AEGetParamDesc, or AEGetAttributeDesc function to get the data out of an Apple event.Getting Data Out of an Apple Event ParameterYou can use the AEGetParamPtr or AEGetParamDesc function to get the data out of an Apple event parameter. Use the AEGetParamPtr function (or the AEGetKeyPtr function, which works the same way) to return the data contained in a parameter. Use the AEGetParamDesc function when you need to get the descriptor record of a parameter or to extract the descriptor list from a parameter.For example, suppose you need to get the data out of a Section Read event. The Edition Manager sends your application a Section Read event to tell your application to read updated information from an edition into the specified subscriber. The direct parameter of the Apple event contains a handle to the section record of the subscriber. You can use the AEGetParamPtr function to get the data out of the Apple event.You specify the Apple event that contains the desired parameter, the keyword of the desired parameter, the descriptor type the function should use to return the data, a buffer to store the data, and the size of this buffer as parameters to the AEGetParamPtr function. The AEGetParamPtr function returns the descriptor type of the resulting data and the actual size of the data, and it places the requested data in the specified buffer.VAR    sectionH:                        SectionHandle;    theAppleEvent:                        AppleEvent;    returnedType:                         DescType;    actualSize:                         Size;    myErr:                         OSErr;myErr := AEGetParamPtr(theAppleEvent, keyDirectObject,                               typeSectionH, returnedType, @sectionH,                               SizeOf(sectionH), actualSize);In this example, the keyDirectObject keyword specifies that the AEGetParamPtr function should extract information from the direct parameter; AEGetParamPtr returns the data in the buffer specified by the sectionH variable. You can request that the Apple Event Manager return the data using the descriptor type of the original data or you can request that the Apple Event Manager coerce the data into a descriptor type that is different from the original. To prevent coercion, specify the desired descriptor type as typeWildCard.The typeSectionH descriptor type specifies that the returned data should be coerced to a handle to a section record. You can use the information returned in the sectionH variable to identify the subscriber and read in the information from the edition.In this example, the AEGetParamPtr function returns, in the returnedType variable, the descriptor type of the resulting data. The descriptor type of the resulting data matches the requested descriptor type unless the Apple Event Manager wasn’t able to coerce the data to the specified descriptor type or you specified the desired descriptor type as typeWildCard. If the coercion fails, the Apple Event Manager returns the errAECoercionFail result code.The AEGetParamPtr function returns, in the actualSize variable, the actual size of the data (that is, the size of coerced data, if any coercion was performed). If the value returned in this variable is greater than the amount your application allocated for the buffer to hold the returned data, your application can increase the size of its buffer to this amount, and get the data again. You can also choose to use the AEGetParamDesc function when your application doesn’t know the size of the data.In general, use the AEGetParamPtr function to extract data that is of fixed length or known maximum length, and the AEGetParamDesc function to extract data that is of variable length. The AEGetParamDesc function returns the descriptor record for an Apple event parameter. This function is useful, for example, for extracting a descriptor list from a parameter. You specify, as parameters to AEGetParamDesc, the Apple event that contains the desired parameter, the keyword of the desired parameter, the descriptor type the function should use to return the descriptor record, and a buffer to store the returned descriptor record. The AEGetParamDesc function returns the descriptor record using the specified descriptor type. For example, the direct parameter of the Open Documents event contains a descriptor list that specifies the documents to open. You can use the AEGetParamDesc function to get the descriptor list out of the direct parameter.VAR    docList:                        AEDescList;    theAppleEvent:                        AppleEvent;    myErr:                         OSErr;myErr := AEGetParamDesc(theAppleEvent, keyDirectObject,                                 typeAEList, docList);In this example, the Apple event specified by the variable theAppleEvent contains the desired parameter. The keyDirectObject keyword specifies that the AEGetParamDesc function should get the descriptor record of the direct parameter. The typeAEList descriptor type specifies that the descriptor record should be returned as a descriptor list. In this example, the AEGetParamDesc function returns a descriptor list in the docList variable.The descriptor list contains a list of descriptor records. To get the descriptor records and their data out of a descriptor list, use the AECountItems function to find the number of descriptor records in the list and then make repetitive calls to the AEGetNthPtr function to get the data out of each descriptor record. See “Getting Data Out of a Descriptor List” on page 4-31 for more information.Note that the AEGetParamDesc function copies the descriptor record from the parameter. When you’re done with a descriptor record that you obtained from AEGetParamDesc, you must dispose of it by calling the AEDisposeDesc function.If an Apple event parameter consists of an object specifier record, you can use AEResolve to resolve the object specifier record (that is, locate the Apple event object it describes), as explained in “Finding Apple Event Objects” on page 3-46.Getting Data Out of an AttributeYou can use the AEGetAttributePtr or AEGetAttributeDesc function to get the data out of the attributes of an Apple event. You specify, as parameters to AEGetAttributePtr, the Apple event that contains the desired attribute, the keyword of the desired attribute, the descriptor type the function should use to return the data, a buffer to store the data, and the size of this buffer. The AEGetAttributePtr function returns the descriptor type of the returned data and the actual size of the data and places the requested data in the specified buffer.For example, this code gets the data out of the keyEventSourceAttr attribute of an Apple event.VAR    theAppleEvent:                        AppleEvent;    returnedType:                         DescType;    sourceOfAE:                        Integer;    actualSize:                        Size;    myErr:                         OSErr;myErr := AEGetAttributePtr(theAppleEvent, keyEventSourceAttr,                                      typeShortInteger, returnedType,                                     @sourceOfAE, SizeOf(sourceOfAE),                                     actualSize); The keyEventSourceAttr keyword specifies the attribute from which to get the data. The typeShortInteger descriptor type specifies that the data should be returned as a short integer; the returnedType variable contains the actual descriptor type that is returned. You also must specify a buffer to hold the returned data and specify the size of this buffer. If the data is not already a short integer, the Apple Event Manager coerces it as necessary before returning it. The AEGetAttributePtr function returns, in the actualSize variable, the actual size of the returned data after coercion has taken place. You can check this value to make sure you got all the data.As with the AEGetParamPtr function, you can request that AEGetAttributePtr return the data using the descriptor type of the original data, or you can request that the Apple Event Manager coerce the data into a descriptor type that is different from the original. In this example, the AEGetAttributePtr function returns the requested data as a short integer in the sourceOfAE variable, and you can get information about the source of the Apple event by examining this value. You can test the returned value against the values defined by the data type AEEventSource.TYPE AEEventSource = (kAEUnknownSource, kAEDirectCall,                              kAESameProcess, kAELocalProcess,                              kAERemoteProcess);The constants defined by the data type AEEventSource have the following meanings:Constant     Meaning    kAEUnknownSource    Source of Apple event unknown    kAEDirectCall    A direct call that bypassed the PPC Toolbox    kAESameProcess    Target application is also the source application    kAELocalProcess    Source application is another process on the same computer as the target application    kAERemoteProcess    Source application is a process on a remote computer on the network    The next example shows how to use the AEGetAttributePtr function to get data out of the keyMissedKeywordAttr attribute. After your handler extracts all known parameters from an Apple event, it should check whether the keyMissedKeywordAttr attribute exists. If it does, then your handler did not get all of the required parameters.Note that if AEGetAttributePtr returns the errAEDescNotFound result code, then the keyMissedKeywordAttr attribute does not exist—that is, your application has extracted all of the required parameters. If AEGetAttributePtr returns noErr, then the keyMissedKeywordAttr attribute does exist—that is, your handler did not get all of the required parameters.myErr := AEGetAttributePtr(theAppleEvent, keyMissedKeywordAttr,                                     typeWildCard, returnedType, NIL, 0,                                     actualSize);The data in the keyMissedKeywordAttr attribute contains the keyword of the first required parameter, if any, that your handler didn’t retrieve. If you want this data returned, specify a buffer to hold it and specify the buffer size. Otherwise, as in this example, specify NIL as the buffer and 0 as the size of the buffer.This example shows how to use the AEGetAttributePtr function to get the address of the sender of an Apple event from the keyAddressAttr attribute of the Apple event:VAR    theAppleEvent:     AppleEvent;    returnedType:                     DescType;    addressOfAE:                     TargetID;    actualSize:                     Size;    myErr:                     OSErr;myErr := AEGetAttributePtr(theAppleEvent, keyAddressAttr,                                     typeTargetID, returnedType,                                     @addressOfAE, SizeOf(addressOfAE),                                     actualSize);The keyAddressAttr keyword specifies the attribute to get the data from. The typeTargetID descriptor type specifies that the data should be returned as a target ID record; the returnedType variable contains the actual descriptor type that is returned. You can examine the address returned in the addressOfAE variable to determine the sender of the Apple event.The target ID record returned in the addressOfAE variable contains the sender’s port name, port location, and session reference number. To get the process serial number for a process on the local machine, pass the port name returned in the target ID record to the GetProcessSerialNumberFromPortName function. You can then pass the process serial number to the GetProcessInformation function to find the creator signature for a given process. (For more information about these functions, see the chapter “Event Manager” in Inside Macintosh: Macintosh Toolbox Essentials.)For more information about target addresses, see “Specifying a Target Address” on page 5-10.Getting Data Out of a Descriptor ListYou can use the AECountItems function to count the number of items in a descriptor list, and you can use AEGetNthDesc or AEGetNthPtr to get a descriptor record or its data out of a descriptor list.The Open Documents event contains a direct parameter that specifies the list of documents to open. The list of documents is contained in a descriptor list. After extracting the descriptor list from the parameter, you can determine the number of items in the list and then extract each descriptor record from the descriptor list. See Figure 3-9 on page 3-19 for a depiction of the Open Documents event.For example, when your handler receives an Open Documents event, you can use the AEGetParamDesc function to return the direct parameter as a descriptor list. You can then use AECountItems to return the number of descriptor records in the list.VAR    theAppleEvent:                        AppleEvent;    docList:                        AEDescList;    itemsInList:                        LongInt;    myErr:                        OSErr;myErr := AEGetParamDesc(theAppleEvent, keyDirectObject,                                typeAEList, docList);myErr := AECountItems(docList, itemsInList);The AEGetParamDesc function returns, in the docList variable, a copy of the descriptor list from the direct parameter of the Open Documents event. You specify this list to the AECountItems function.You specify the descriptor list whose items you want to count in the first parameter to AECountItems. The Apple Event Manager returns, in the second parameter, the number of items in the list. When extracting the descriptor records from a list, you often use the number of items as a loop index. Here’s an example:FOR index := 1 TO itemsInList DO    BEGIN    {for each descriptor record in the list, get its data}    END;The format of the descriptor records in a descriptor list is private to the Apple Event Manager. You must use the AEGetNthPtr or AEGetNthDesc function to extract descriptor records from a descriptor list.  You specify the descriptor list that contains the desired descriptor records and an index as parameters to the AEGetNthPtr function. The index represents a specific descriptor record in the descriptor list. The AEGetNthPtr function returns the data for the descriptor record represented by the specified index. You also specify the descriptor type the function should use to return the data, a buffer to store the data, and the size of this buffer. If the specified descriptor record exists, the AEGetNthPtr function returns the keyword of the parameter, the descriptor type of the returned data, and the actual size of the data, and it places the requested data in the specified buffer.Here’s an example that uses the AEGetNthPtr function to extract an item from the descriptor list in the direct parameter of the Open Documents event:myErr := AEGetNthPtr(docList, index, typeFSS, keywd,                             returnedType, @myFSS, Sizeof(myFSS),                             actualSize);The docList variable specifies the descriptor list from the direct parameter of the Open Documents event. The index variable specifies the index of the descriptor record to extract. You can use the typeFSS descriptor type, as in this example, to specify that the data be returned as a file system specification record. The Apple Event Manager automatically coerces the original data type of the descriptor record from an alias record to a file system specification record. The AEGetNthPtr function returns the keyword of the parameter and the descriptor type of the resulting data in the keywd and returnedType variables, respectively. You also specify a buffer to hold the desired data and the size (in bytes) of the buffer. In this example, the myFSS variable specifies the buffer. The function returns the actual size of the data in the actualSize variable. If this size is larger than the size of the buffer you provided, you know that you didn’t get all of the data for the descriptor record.Listing 4-10 shows a more complete example of extracting the items from a descriptor list in the Open Documents event.Listing 4-10    Extracting items from a descriptor listVAR    index:                        LongInt;    itemsInList:                         LongInt;    docList:                        AEDescList;    keywd:                         AEKeyword;    returnedType:                         DescType;    myFSS:                        FSSpec;    actualSize:                         Size;    myErr:                         OSErr;FOR index := 1 TO itemsInList DO    BEGIN        myErr := AEGetNthPtr(docList, index, typeFSS, keywd,                                     returnedType, @myFSS, Sizeof(myFSS),                                     actualSize);        IF myErr <> noErr THEN DoError(myErr);        myErr := MyOpenFile(@myFSS);        IF myErr <> noErr THEN DoError(myErr);    END;myErr := AEDisposeDesc(docList);  Writing Apple Event HandlersFor each Apple event your application supports, you must provide a function called an Apple event handler. The AEProcessAppleEvent function calls one of your Apple event handlers when it processes an Apple event. Your Apple event handlers should perform any action requested by the Apple event, add parameters to the reply Apple event if appropriate, and return a result code.The Apple Event Manager uses dispatch tables to route Apple events to the appropriate Apple event handler. You must supply an Apple event handler for each entry in your application’s Apple event dispatch table. Each handler must be a function that uses this syntax:FUNCTION MyEventHandler (theAppleEvent: AppleEvent;                                  reply: AppleEvent;                                  handlerRefcon: LongInt): OSErr; The parameter theAppleEvent is the Apple event to handle. Your handler uses Apple Event Manager functions to extract any parameters and attributes from the Apple event and then performs the necessary processing. If any of the parameters include object specifier records, your handler should call AEResolve to resolve them—that is, to locate the Apple event objects they describe. For more information, see the chapter “Resolving and Creating Object Specifier Records” in this book.The reply parameter is the default reply provided by the Apple Event Manager. (“Replying to an Apple Event,” which begins on page 4-36, describes how to add parameters to the default reply.) The handlerRefcon parameter is the reference constant stored in the Apple event dispatch table entry for the Apple event. Your handler can check the reference constant, if necessary, for information about the Apple event.You can use the reference constant for anything you wish. For example, if you want to use the same handler for several Apple events, you can install entries for each event in your application’s Apple event dispatch table that specify the same handler but different reference constants. Your handler can then use the reference constant to distinguish the different Apple events it handles.To provide an Apple event handler in C, be sure to include the Pascal declaration before the handler declaration. This is the syntax for an Apple event handler in C: pascal OSErr MyEventHandler (const AppleEvent *theAppleEvent,                                       const AppleEvent *reply,                                       long handlerRefcon);After extracting all known parameters from the Apple event, every handler should determine whether the Apple event contains any further required parameters. Your handler can determine whether it retrieved all the required parameters by checking whether the keyMissedKeywordAttr attribute exists. If the attribute exists, then your handler has not retrieved all the required parameters and should immediately return an error. If the attribute does not exist, then the Apple event does not contain any more required parameters, although it may contain additional optional parameters.The Apple Event Manager determines which parameters are optional according to the keywords listed in the keyOptionalKeywordAttr attribute. The source application is responsible for adding these keywords to the keyOptionalKeywordAttr attribute, but is not required to do so, even if that parameter is listed in the Apple Event Registry: Standard Suites as an optional parameter. If the source application does not add the necessary keyword to the keyOptionalKeywordAttr attribute, the target application treats the parameter as required for that Apple event. If the target application supports the parameter, it should handle the Apple event as the source application expects. If the target application does not support the parameter and checks whether it has received all the required parameters, it finds that there’s another parameter that the client application considered required, and should return the result code errAEParamMissed without attempting to handle the event. Listing 4-11 shows a function that checks for a keyMissedKeywordAttr attribute. A handler calls this function after getting all the required parameters it knows about from an Apple event.Listing 4-11    A function that checks for a keyMissedKeywordAttr attributeFUNCTION MyGotRequiredParams (theAppleEvent: AppleEvent): OSErr;VAR    myErr:                        OSErr;    returnedType:                        DescType;    actualSize:                        Size;BEGIN    myErr := AEGetAttributePtr(theAppleEvent,                                          keyMissedKeywordAttr,                                            typeWildCard, returnedType,                                          NIL, 0, actualSize);    IF myErr = errAEDescNotFound THEN                                                     {you got all the required parameters}        MyGotRequiredParams := noErr    ELSE IF myErr = noErr THEN                                                      {you missed a required parameter}        MyGotRequiredParams := errAEParamMissed;END;The code in Listing 4-11 uses the AEGetAttributePtr function to get the keyMissedKeywordAttr attribute. This attribute contains the first required parameter, if any, that your handler didn’t retrieve. If AEGetAttributePtr returns the errAEDescNotFound result code, the Apple event doesn’t contain a keyMissedKeywordAttr attribute. If the Apple event doesn’t contain this attribute, then your handler has extracted all of the parameters that the client application considered required. If the AEGetAttributePtr function returns noErr as the result code, then the attribute does exist, meaning that your handler has not extracted all of the required parameters. In this case, your handler should return an error and not process the Apple event.The first remaining required parameter is specified by the data of the keyMissedKeywordAttr attribute. If you want this data returned, specify a buffer to hold the data. Otherwise, specify NIL as the buffer and 0 as the size of the buffer. If you specify a buffer to hold the data, you can check the value of the actualSize parameter to see if the data is larger than the buffer you allocated.For more information about specifying Apple event parameters as optional or required, see “Specifying Optional Parameters for an Apple Event” beginning on page 5-7. Replying to an Apple EventYour handler routine for a particular Apple event is responsible for performing the action requested by the Apple event, and can optionally return data in a reply Apple event. The Apple Event Manager passes a default reply Apple event to your handler. The default reply Apple event has no parameters when it is passed to your handler. Your handler can add parameters to the reply Apple event. If the client application requested a reply, the Apple Event Manager returns the reply Apple event to the client. The reply Apple event is identified by the kCoreEventClass event class and by the kAEAnswer event ID. If the client application specified the kAENoReply flag in the reply parameter of the AESend function, the Apple Event Manager passes a null descriptor record (a descriptor record of type typeNull whose data handle has the value NIL) to your handler instead of a default reply Apple event. Your handler should check the descriptor type of the reply Apple event before attempting to add any attributes or parameters to it. An attempt to add an Apple event attribute or parameter to a null descriptor record generates an error. If the client application requests a reply, the Apple Event Manager prepares a reply Apple event for the client by passing a default reply Apple event to your handler. The default reply Apple event has no parameters when it is passed to your handler. Your handler can add any parameters to the reply Apple event. If your application is a spelling checker, for example, you can return a list of misspelled words in a parameter. When your handler finishes processing an Apple event, it returns a result code to AEProcessAppleEvent, which returns this result code as its function result. If your handler returns a nonzero result code, and if you have not added your own keyErrorNumber parameter, the Apple Event Manager also returns this result code to the client application by putting the result code into a keyErrorNumber parameter for the reply Apple event. The client can check for the existence of this parameter to determine whether the handler performed the requested action.The client application specifies whether it wants a reply Apple event or not by specifying flags (represented by constants) in the sendMode parameter of the AESend function.If the client specifies the kAEWaitReply flag in the sendMode parameter, the AESend function does not return until the timeout specified by the timeoutInTicks parameter expires or the server application returns a reply. When the server application returns a reply, the reply parameter to AESend contains the reply Apple event that your handler returned to the AEProcessAppleEvent function. When the client application no longer needs the original Apple event and the reply event, it must dispose of them, but the Apple Event Manager disposes of both the Apple event and the reply event for the server application when the server’s handler returns to AEProcessAppleEvent.  If the client specified the kAEQueueReply flag, the client receives the reply event at a later time during its normal processing of other events. Your handler should always set its function result to noErr if it successfully handles the Apple event. If an error occurs, your handler should return either errAEEventNotHandled or some other nonzero result code. If the error occurs because your application cannot understand the event, return errAEEventNotHandled. This allows the Apple Event Manager to look for a handler in the system special handler or system Apple event dispatch tables that might be able to handle the event. If the error occurs because the event is impossible to handle as specified, return the result code returned by whatever function caused the failure, or whatever other result code is appropriate.For example, suppose your application receives a Get Data event requesting the name of the current printer, and your application cannot handle such an event. In this situation, you should return errAEEventNotHandled in case another handler available to the Apple Event Manager can handle the Get Data event. This strategy allows users to take advantage of system capabilities from within your application via system handlers. However, if your application cannot handle a Get Data event that requests the fifth paragraph in a document because the document contains only four paragraphs, you should return some other nonzero error, because further attempts to handle the event are pointless.If your Apple event handler calls the AEResolve function and AEResolve calls an object accessor function in the system object accessor dispatch table, your Apple event handler may not recognize the descriptor type of the token returned by the function. In this case, your handler should return the result code errAEUnknownObjectType. When your handler returns this result code, the Apple Event Manager attempts to locate a system Apple event handler that can recognize the token. For more information, see “Installing Entries in the Object Accessor Dispatch Tables,” which begins on page 6-21.The Apple Event Manager automatically adds any nonzero result code that your handler returns to a keyErrorNumber parameter in the reply Apple event. In addition to returning a result code, your handler can also return an error string in the keyErrorString parameter of the reply Apple event. Your handler should provide meaningful text in the keyErrorString parameter, so that the client can display this string to the user if desired. Listing 4-12 shows how to add the keyErrorString parameter to the reply Apple event. See “Adding Parameters to an Apple Event” on page 5-5 for a description of the AEPutParamPtr function.Listing 4-12    Adding the keyErrorString parameter to the reply Apple eventFUNCTION MyHandler (theAppleEvent: AppleEvent; reply: AppleEvent;                          handlerRefcon: LongInt): OSErr; VAR    myErr:                OSErr;    errStr:                Str255;BEGIN    {handle your Apple event here}    {if an error occurs when handling an Apple event, set the }    { function result and error string accordingly}    IF myErr <> noErr THEN    BEGIN        MyHandler := myErr;     {result code to be returned--the }                                    { Apple Event Manager adds this }                                    { result code to the reply Apple }                                    { event as the keyErrorNumber }                                    { parameter}        IF (reply.dataHandle <> NIL) THEN        {add error string parameter to the default reply}        BEGIN            {strings should normally be stored in resources}            errStr := 'Why error occurred';            myErr := AEPutParamPtr(reply, keyErrorString,                                             typeIntlText, @errStr[1],                                             length(errStr));        END;    END    ELSE        MyHandler := noErr;END;If your handler needs to return data to the client, it can add parameters to the reply Apple event. Listing 4-13 shows how a handler for the Multiply event (an imaginary Apple event that asks the server to multiply two numbers) might return the results of the multiplication to the client.Listing 4-13    Adding parameters to the reply Apple eventFUNCTION MyMultHandler (theAppleEvent: AppleEvent;                                 reply: AppleEvent;                                 handlerRefcon: LongInt): OSErr; VAR    myErr:                        OSErr;    number1,number2:                        LongInt;    replyResult:                        LongInt;    actualSize:                        Size;    returnedType:                        DescType;BEGIN    {get the numbers to multiply from the parameters of the }    { Apple event; put the numbers in the number1 and number2 }    { variables and then perform the requested multiplication}    myErr := MyDoMultiply(theAppleEvent, number1,                                     number2, replyResult);    IF myErr = noErr THEN         IF (reply.dataHandle <> NIL) THEN            {return result of the multiplication in the reply Apple }            { event}            myErr := AEPutParamPtr(reply, keyDirectObject,                                             typeLongInteger, @replyResult,                                             SizeOf(replyResult));    MyMultHandler := myErr;    {if an error occurs, set the error string }    { accordingly, as shown in Listing 4-12}END;Disposing of Apple Event Data StructuresWhenever a client application uses Apple Event Manager functions to create a descriptor record, descriptor list, or Apple event record, the Apple Event Manager allocates memory for these data structures in the client’s application heap. Likewise, when a server application extracts a descriptor record from an Apple event by using Apple Event Manager functions, the Apple Event Manager creates a copy of the descriptor record, including the data to which its handle refers, in the server’s application heap.Whenever you finish using a descriptor record or descriptor list that you have created or extracted from an Apple event, you should dispose of the descriptor record—and thereby deallocate the memory it uses—by calling the AEDisposeDesc function. If the descriptor record you pass to AEDisposeDesc (such as an Apple event record or an AE record) includes other nested descriptor records, one call to AEDisposeDesc will dispose of them all. When a client application adds a descriptor record to an Apple event (for example, when it creates a descriptor record by calling AECreateDesc and then puts a copy of it into a parameter of an Apple event by calling AEPutParamDesc), it is still responsible for disposing of the original descriptor record. After a client application has finished using both the Apple event specified in the AESend function and the reply Apple event, it should dispose of their descriptor records by calling AEDisposeDesc. The client application should dispose of them even if AESend returns a nonzero result code. The Apple event that a server application’s handler receives is a copy of the original event created by the client application. When a server application’s handler returns to AEProcessAppleEvent, the Apple Event Manager disposes of the server’s copy (in the server’s application heap) of both the Apple event and the reply event. The server application is responsible for disposing of any descriptor records created while extracting data from the Apple event or adding data to the reply event.In general, outputs from Apple Event Manager functions are your application’s responsibility. Once you finish using them, you should use AEDisposeDesc to dispose of any Apple event data structures created or returned by these functions:AECoerceDesc    AEDuplicateDesc    AECoercePtr    AEGetAttributeDesc    AECreateAppleEvent    AEGetKeyDesc    AECreateDesc    AEGetNthDesc    AECreateList    AEGetParamDesc    If you attempt to dispose of descriptor records returned by successful calls to these functions without using AEDisposeDesc, your application may not be compatible with future versions of the Apple Event Manager. However, if any of these functions return a nonzero result code, they return a null descriptor record, which does not need to be disposed of. Outputs from functions, such as AEGetKeyPtr, that use a buffer rather than a descriptor record to return data do not require the use of AEDisposeDesc. It is therefore preferable to use these functions for any data that is not identified by a handle. Some of the functions described in the chapter “Resolving and Creating Object Specifier Records” in this book also create descriptor records. If you set the disposeInputs parameter to FALSE for any of the following functions, you should dispose of any Apple event data structures that they create or return:CreateCompDescriptor    CreateObjSpecifier    CreateLogicalDescriptor    CreateRangeDescriptor     Your application is also responsible for disposing of some of the tokens it creates in the process of resolving an object specifier record. For information about token disposal, see “Defining Tokens” on page 6-39. Writing and Installing Coercion HandlersWhen your application extracts data from a parameter, it can request that the Apple Event Manager return the data using a descriptor type that is different from the original descriptor type. For example, when extracting data from the direct parameter of the Open Documents event, you can request that the alias records be returned as file system specification records. The Apple Event Manager can automatically coerce many different types of data from one to another. Table 4-1 on page 4-43 shows descriptor types and the kinds of coercion that the Apple Event Manager can perform.You can also provide your own routines, referred to as coercion handlers, to coerce data into any other descriptor type. To install your own coercion handlers, use the AEInstallCoercionHandler function. You specify as parameters to this functionn    the descriptor type of the data coerced by the handlern    the descriptor type of the resulting datan    the address of the coercion handler for this descriptor typen    a reference constantn    a Boolean value that indicates whether your coercion handler expects the data to be specified as a descriptor record or as a pointer to the actual datan    a Boolean value that indicates whether your coercion handler should be added to your application’s coercion dispatch table or the system coercion dispatch tableThe system coercion dispatch table is a table in the system heap that contains coercion handlers available to all applications and processes running on the same computer. The coercion handlers in your application’s coercion dispatch table are available only to your application. When attempting to coerce data, the Apple Event Manager first looks for a coercion handler in your application’s coercion dispatch table. If it cannot find a handler for the descriptor type, it looks in the system coercion dispatch table for a handler. If it doesn’t find a handler there, it attempts to use the default coercion handling described by Table 4-1 on page 4-43. If it can’t find an appropriate default coercion handler, it returns the errAECoercionFail result code. Any handler that you add to the system coercion dispatch table should reside in the system heap. If there was already an entry in the system coercion dispatch table for the same descriptor type, it is replaced. Therefore, if there is an entry in the system coercion dispatch table for the same descriptor type, you should chain it to your system coercion handler as explained in “Creating and Managing the Coercion Handler Dispatch Tables,” which begins on page 4-96.sWARNINGBefore an application calls a system coercion handler, system software has set up the A5 register for the calling application. For this reason, if you provide a system coercion handler, it should never use A5 global variables or anything that depends on a particular context; otherwise, the application that calls the system coercion handler may crash.sYou can provide a coercion handler that expects to receive the data in a descriptor record or a buffer referred to by a pointer. When you install your coercion handler, you specify how your handler wishes to receive the data. Whenever possible, you should write your coercion handler so that it can accept a pointer to the data, because it’s more efficient for the Apple Event Manager to provide your coercion handler with a pointer to the data.A coercion handler that accepts a pointer to data must be a function with the following syntax:FUNCTION MyCoercePtr (typeCode: DescType; dataPtr: Ptr;                              dataSize: Size; toType: DescType;                              handlerRefcon: LongInt;                             VAR result: AEDesc): OSErr; The typeCode parameter is the descriptor type of the original data. The dataPtr parameter is a pointer to the data to coerce; the dataSize parameter is the length, in bytes, of the data. The toType parameter is the desired descriptor type of the resulting data. The handlerRefcon parameter is a reference constant stored in the coercion table entry for the handler and passed to the handler by the Apple Event Manager whenever the handler is called. The result parameter is the descriptor record returned by your coercion handler.Your coercion handler should coerce the data to the desired descriptor type and return the data in the descriptor record specified by the result parameter. If your handler successfully performs the coercion, it should return the noErr result code; otherwise, it should return a nonzero result code.A coercion handler that accepts a descriptor record must be a function with the following syntax:FUNCTION MyCoerceDesc (theAEDesc: AEDesc; toType: DescType;                              handlerRefcon: LongInt;                              VAR result: AEDesc): OSErr;The parameter theAEDesc is the descriptor record that contains the data to be coerced. The toType parameter is the descriptor type of the resulting data. The handlerRefcon parameter is a reference constant stored in the coercion table entry for the handler and passed to the handler by the Apple Event Manager whenever the handler is called. The result parameter is the resulting descriptor record.Your coercion handler should coerce the data in the descriptor record to the desired descriptor type and return the data in the descriptor record specified by the result parameter. Your handler should return an appropriate result code.NoteTo ensure that no coercion is performed and that the descriptor type of the result is of the same descriptor type as the original, specify typeWildCard for the desired type.uTable 4-1 lists the descriptor types for which the Apple Event Manager provides coercion. Table 4-1    Coercion handling provided by the Apple Event Manager(continued)Original descriptor type of data to be coerced    Desired descriptor type    Description    typeChar    typeIntegertypeLongIntegertypeSMInttypeSMFloattypeShortIntegertypeFloattypeLongFloattypeShortFloattypeExtendedtypeComptypeMagnitude    Any string that is a valid representation of a number can be coerced into an equivalent numeric value.                                                                            typeIntegertypeLongInteger typeSMInttypeSMFloattypeShortIntegertypeFloattypeLongFloattypeShortFloattypeExtendedtypeComptypeMagnitude    typeChar    Any numeric descriptor type can be coerced into the equivalent text string.                                                                            typeIntegertypeLongInteger typeSMInttypeSMFloattypeShortInteger typeFloattypeLongFloattypeShortFloattypeExtendedtypeComptypeMagnitude    typeIntegertypeLongIntegertypeSMInttypeSMFloattypeShortIntegertypeFloattypeLongFloattypeShortFloattypeExtendedtypeComptypeMagnitude    Any numeric descriptor type can be coerced into any other numeric descriptor type.                                                                            typeChar    typeTypetypeEnumeratedtypeKeywordtypeProperty    Any four-character string can be coerced to one of these descriptor types.                                        typeEnumeratedtypeKeywordtypePropertytypeType    typeChar    Any of these descriptor types can be coerced to the equivalent text string.            continued    typeIntlText    typeChar    The result contains text only, without the script code or language code from the original descriptor record.    typeTrue    typeBoolean    The result is the Boolean value TRUE.    typeFalse    typeBoolean    The result is the Boolean value FALSE.    typeEnumerated    typeBoolean    The enumerated value 'true' becomes the Boolean value TRUE. The enumerated value 'fals' becomes the Boolean value FALSE.    typeBoolean    typeEnumerated    The Boolean value FALSE becomes the enumerated value 'fals'. The Boolean value TRUE becomes the enumerated value 'true'.    typeShortIntegertypeSMInt    typeBoolean    A value of 1 becomes the Boolean value TRUE. A value of 0 becomes the Boolean value FALSE.    typeBoolean    typeShortInteger typeSMInt    A value of FALSE becomes 0. A value of TRUE becomes 1.    typeAlias    typeFSS    An alias record is coerced into a file system specification record.    typeAppleEvent    typeAppParameters    An Apple event is coerced into a list of application parameters for the LaunchParamBlockRec parameter block.    any descriptor type    typeAEList    A descriptor record is coerced into a descriptor list containing a single item.    typeAEList    type of list item    A descriptor list containing a single descriptor record is coerced into a descriptor record.     NOTESome of the descriptor types listed in this table are synonyms; for example, the constants typeSMInt and typeShortInteger have the same four-character code, 'shor'.Interacting With the UserWhen your application receives an Apple event, it may need to interact with the user. For example, it may need to display a dialog box asking the user for additional information or confirmation. You must use the AEInteractWithUser function to make sure your application is in the foreground before it actually interacts with the user. Both the client application and the server application specify their preferences for user interaction. The AEInteractWithUser function checks the user interaction preferences set by each application. If both the client and the server allow user interaction, AEInteractWithUser usually posts a notification request, and the Notification Manager brings the server to the foreground after the user responds to the notification request. The AEInteractWithUser function can also bring the server application directly to the foreground, but only if the client application is the active application on the same computer and has set two flags in the sendMode parameter of the AESend function: the kAEWaitReply flag, which indicates that it is waiting for a reply, and the kAECanSwitchLayer flag, which indicates that it wants the server application to come directly to the foreground rather than posting a notification request.To specify its preferences for how the server application should interact with the user, the client application sets various flags in the sendMode parameter to AESend. The Apple Event Manager sets the corresponding flags in the keyInteractLevelAttr attribute of the Apple event.The server application sets its preferences with the AESetInteractionAllowed function. This function lets your application specify whether it allows interaction with the user as a result of receiving an Apple event from itself; from itself and other processes on the local computer; or from itself, local processes, and processes from another computer on the network.Your application calls the AEInteractWithUser function before interacting with the user. If AEInteractWithUser returns the noErr result code, then your application is currently in the front and free to interact with the user. If AEInteractWithUser returns the errAENoUserInteraction result code, the conditions didn’t allow user interaction and your application should not interact with the user.The rest of this section explains how to set user interactions for the client and server applications and the practical effect these settings have when a server needs to interact with a user.Setting the Client Application’s User Interaction PreferencesThe client application sets its user interaction preferences by setting flags in the sendMode parameter to the AESend function. The Apple Event Manager automatically adds the specified flags to the keyInteractLevelAttr attribute of the Apple event. These flags are represented by the following constants:Flag    Description    kAENeverInteract    The server application should never interact with the user in response to the Apple event. If this flag is set, AEInteractWithUser returns the errAENoUserInteraction result code. This flag is the default when an Apple event is sent to a remote application.    kAECanInteract    The server application can interact with the user in response to the Apple event—by convention, if the user needs to supply information to the server. If this flag is set and the server allows interaction, AEInteractWithUser either brings the server application to the foreground or posts a notification request. This flag is the default when an Apple event is sent to a local application.     kAEAlwaysInteract    The server application can interact with the user in response to the Apple event—by convention, whenever the server application normally asks a user to confirm a decision or interact in any other way, even if no additional information is needed from the user. If this flag is set and the server allows interaction, AEInteractWithUser either brings the server application to the foreground or posts a notification request.     For example, suppose a client application sends a Set Data event to a database application to change a customer’s address. The database application is configured to request user confirmation of changes to a customer’s record. In this case the client sets the kAECanInteract flag before sending the event. Thus, the database application attempts to interact with the user if interaction is allowed. If interaction is not allowed, the database makes the correction anyway without consulting the user. However, if the client application sends a Delete event to delete a customer’s record entirely and sets the kAEAlwaysInteract flag, the database application deletes the specified record only if it can interact with the user first and receives confirmation of the decision to delete a record. If interaction with the user is not allowed, the database application returns an error. By setting the kAEAlwaysInteract flag, the client application ensures that the entire record won’t be lost if the user sends the Delete event by mistake.If the client application doesn’t specify any of the three user interaction flags, the Apple Event Manager sets either the kAENeverInteract or the kAECanInteract flag in the keyInteractLevelAttr attribute of the Apple event, depending on the location of the server application. If the server application is on a remote computer, the Apple Event Manager sets the kAENeverInteract flag as the default. If the server application is on the local computer, the Apple Event Manager sets the kAECanInteract flag as the default.In addition to the three user interaction flags, the client application can set another flag in the sendMode parameter to AESend to request that the Apple Event Manager immediately bring the server application directly to the foreground instead of posting a notification request:Flag    Description    kAECanSwitchLayer    If both the client and server allow interaction, and if the client application is the active application on the local computer and is waiting for a reply (that is, it has set the kAEWaitReply flag), AEInteractWithUser brings the server directly to the foreground. Otherwise, AEInteractWithUser uses the Notification Manager to request that the user bring the server application to the foreground.      Note that although the kAECanSwitchLayer flag must be set for the Apple Event Manager to bring the server application directly to the foreground, setting it does not guarantee that the Apple Event Manager will bypass the notification request if user interaction is permitted. Another flag, the kAEWaitReply flag, must also be set in the sendMode parameter, and the client application must provide an idle function.The kAEWaitReply flag is one of three flags in the sendMode parameter that a client application can set to specify whether and how the client should wait for a reply. (For a description of these flags, see “Sending an Apple Event and Handling the Reply” on page 3-30.) If the client application is not waiting for a reply, the user may have continued with other work. An application switch at this point might be unexpected and would thus violate the principle of user control as described in Macintosh Human Interface Guidelines.If the client application sets the kAEWaitReply flag, it should also provide an idle function when it calls AESend so that it can handle events such as update events that it receives while waiting for the reply. Idle functions are described in “Writing an Idle Function,” which begins on page 5-21.When a server application calls AEInteractWithUser, the function first checks whether the kAENeverInteract flag in the keyInteractLevelAttr attribute of the Apple event is set. (The Apple Event Manager sets this attribute according to the flags specified in the sendMode parameter of AESend.) If the kAENeverInteract flag is set, AEInteractWithUser immediately returns the errAENoUserInteraction result code. If the client specified kAECanInteract or kAEAlwaysInteract, AEInteractWithUser checks the server’s preferences for user interaction. Setting the Server Application’s User Interaction PreferencesThe server sets its user interaction preferences by using the AESetInteractionAllowed function. This function specifies the conditions under which your application is willing to interact with the user.myErr := AESetInteractionAllowed(level);The level parameter is of type AEInteractAllowed. TYPE        AEInteractAllowed = (kAEInteractWithSelf,                                     kAEInteractWithLocal,                                     kAEInteractWithAll);You can specify one of these values for the interaction level:Flag    Description    kAEInteractWithSelf    Your server application can interact with the user in response to an Apple event only when your application is also the client application—that is, only when your application is sending the Apple event to itself.    kAEInteractWithLocal    Your server application can interact with the user in response to an Apple event only if the client application is on the same computer as your application. This is the default if the server application does not call the function AESetInteractionAllowed.    kAEInteractWithAll    Your server application can interact with the user in response to an Apple event sent by any client application on any computer.    If the server application does not set the user interaction level, AEInteractWithUser uses kAEInteractWithLocal as the value.If the application sends itself an Apple event (that is, if the application is both the client and the server) without setting the kAENeverInteract flag, AEInteractWithUser always allows user interaction. If the client application is a process on the local computer and specifies kAECanInteract or kAEAlwaysInteract, and if the server has set the interaction level to kAEInteractWithLocal or kAEInteractWithAll, then AEInteractWithUser allows user interaction. If the client is a process on a remote computer on the network and specifies kAECanInteract or kAEAlwaysInteract, AEInteractWithUser allows user interaction only if the server specified the kAEInteractWithAll flag for the interaction level. In all other cases, AEInteractWithUser does not allow user interaction.  Requesting User InteractionIf your server application needs to interact with the user for any reason, it must call the AEInteractWithUser function to make sure it is in the foreground before it actually interacts with the user. When AEInteractWithUser allows user interaction (based on the client’s and server’s preferences), AEInteractWithUser brings the server application to the foreground—either directly or after the user responds to a notification request—and then returns a noErr result code. If AEInteractWithUser brings the server to the foreground directly, the client returns to the foreground immediately after the server has finished interacting with the user. If AEInteractWithUser brings the server to the foreground after the user responds to a notification request, the server remains in the foreground after completing the user interaction.The AEInteractWithUser function specifies how long your handler is willing to wait for a response from the user. For example, if the timeout value is 900 ticks (15 seconds) and the Apple Event Manager posts a notification request, the Notification Manager begins to display a blinking icon in the upper-right corner of the screen, then removes the notification request (and the blinking icon) if the user does not respond within 15 seconds. (The discussion that follows describes some restrictions on the icons that can be displayed in this situation.)Note that the timeout value passed to the AEInteractWithUser function is separate from the timeout value passed to the AESend function, which specifies how long the client application is willing to wait for the reply or return receipt from the server application. If AEInteractWithUser does not receive a response from the user within the specified time, AEInteractWithUser returns errAETimeout. You may want to give the user a method of setting the interaction level. For example, some users may not want to be interrupted while background processing of an Apple event occurs, or they may not want to respond to dialog boxes when your application is handling Apple events sent from another computer.Listing 4-14 illustrates the use of the AEInteractWithUser function. You call this function before your application displays a dialog box or otherwise interacts with the user when processing an Apple event. You specify a timeout value, a pointer to a Notification Manager record, and the address of an idle function as parameters to AEInteractWithUser.Listing 4-14    Using the AEInteractWithUser functionmyErr := AEInteractWithUser(kAEDefaultTimeout, gMyNotifyRecPtr,                                      @MyIdleFunction);IF myErr <> noErr THEN    {the attempt to interact failed; do any error handling}    DoError(myErr)ELSE    {interact with the user by displaying a dialog box }    { or by interacting in any other way that is necessary}    DisplayMyDialogBox; You can set a timeout value, in ticks, in the first parameter to AEInteractWithUser. Use the kAEDefaultTimeout constant if you want the Apple Event Manager to use a default value for the timeout value. The Apple Event Manager uses a timeout value of about one minute if you specify this constant. You can also specify the kNoTimeOut constant if your application is willing to wait an indefinite amount of time for a response from the user. Usually you should provide a timeout value, so that your application can complete processing of the Apple event in a reasonable amount of time. If you specify NIL instead of a Notification Manager record in the second parameter of AEInteractWithUser, the Apple Event Manager looks for an application icon with the ID specified by the application’s bundle ('BNDL') resource and the application’s file reference ('FREF') resource. The Apple Event Manager first looks for an 'SICN' resource with the specified ID; if it can’t find an 'SICN' resource, it looks for the 'ICN#' resource and compresses the icon to fit in the menu bar. The Apple Event Manager won’t look for any members of an icon family other than the icon specified in the 'ICN#' resource.If the application doesn’t have 'SICN' or 'ICN#' resources, or if it doesn’t have a file reference resource, the Apple Event Manager passes NIL to the Notification Manager, and no icon appears in the upper-right corner of the screen. Therefore, if you want to display any icon other than those of type 'SICN' or 'ICN#', you must specify a notification record as the second parameter to the AEInteractWithUser function. NoteIf you want the Notification Manager to use a color icon when it posts a notification request, you should provide a Notification Manager record that specifies a 'cicn' resource.uThe AEInteractWithUser function posts a notification request only when user interaction is allowed and the kAECanSwitchLayer flag in the keyInteractLevelAttr attribute is not set.The last parameter to AEInteractWithUser specifies an idle function provided by your application. Your idle function should handle any update events, null events, operating-system events, or activate events while your application is waiting to be brought to the front. See “Writing an Idle Function” on page 5-21 for more information. Figure 4-1 illustrates a situation in which a client application (a forms application) might request a service from a server application (a database application). To perform this service, the server application must interact with the user.Figure 4-1    A document with a button that triggers a Get Data eventFigure 4-1 shows part of an electronic form used to enter information about an order received by telephone. If the customer has ordered from the company before, the user can quickly retrieve the customer’s address and telephone number by clicking the Retrieve Customer Info button. In response, the forms application sends a Get Data event to a database application (SurfDB) currently open on the same computer. The Get Data event sent by the forms application (the client application for the ensuing transaction) asks SurfDB (the server) to locate the customer’s name in a table of addresses and return the customer’s address. When the forms application receives the reply Apple event, it can add the address data to the appropriate fields in the order form.If SurfDB, as the server application, locates more than one entry for the specified customer name, it needs to interact with the user to determine which data to return in the reply Apple event. To interact with the user, the server application must be in the foreground, so that it can display a dialog box like the one shown in Figure 4-2.Figure 4-2    A server application displaying a dialog box that requests information from the userFigure 4-3, Figure 4-4, and Figure 4-5 illustrate two methods of dealing with this situation. Figure 4-3 shows the behavior of the server application that is common to both methods. In both cases, the server uses AESetInteractionAllowed to set its own interaction level to kAEInteractWithLocal. After calling AEResolve to locate the requested data, the server application discovers that two addresses match the name the user typed into the electronic form. The server then calls AEInteractWithUser with a timeout value of kAEDefaultTimeout so it can find out which address the user wants. Figure 4-3    Handling user interactionFigure 4-4 shows the circumstances in which the server application’s call to AEInteractWithUser shown in Figure 4-3 will cause the Apple Event Manager to bring the server application directly to the foreground. The client application sets the kAECanInteract, kAECanSwitchLayer, and kAEWaitReply flags in the sendMode parameter of the AESend function when it sends the Get Data event shown in the figure. These flags indicate that the client application expects the user to wait until the address appears in the appropriate fields of the electronic form before continuing with any other work. In this case, an automatic layer switch will not surprise the user and will avoid the additional user action required to respond to a notification request, so AEInteractWithUser brings the server application directly to the foreground and returns a noErr result code. The server application then displays the dialog box requesting that the user select the desired customer. After the user selects the desired customer and clicks OK, the server application’s Get Data event handler returns. The Apple Event Manager immediately brings the client application to the foreground, and the client application displays the requested customer information in the appropriate fields. Figure 4-4    Handling user interaction with the kAEWaitReply flag setFigure 4-5 shows the circumstances in which the server application’s call to AEInteractWithUser in Figure 4-3 will cause the Apple Event Manager to post a notification request rather than bringing the server application directly to the foreground. Figure 4-5    Handling user interaction with the kAEQueueReply flag set  The only difference between the Get Data event shown in Figure 4-4 and the Get Data event shown in Figure 4-5 is that the client application has set the kAEQueueReply flag instead of the kAEWaitReply flag in the sendMode parameter of AESend and has not set the kAECanSwitchLayer flag. This combination of flags indicates that the client application expects the user to continue filling in other parts of the form, such as the items being ordered; the address will just appear after a while, provided there is no duplicate name. In this case, an automatic layer switch would disrupt the user’s work. Instead of bringing the server application directly to the foreground, AEInteractWithUser uses the Notification Manager to post a notification request.After the user has responded to the request and has brought the server application to the foreground, AEInteractWithUser returns a noErr result code, and the server application displays the dialog box requesting that the user select the desired customer. When the user selects a customer and clicks OK, the server application’s Get Data event handler returns. Because the user brought the server to the foreground manually, the server remains in the foreground after the handler returns. Reference to Responding to Apple EventsThis section describes the basic Apple Event Manager data structures and routines that your application can use to respond to Apple events. It also describes the syntax for application-defined Apple event handlers and coercion handlers that your application can provide for use by the Apple Event Manager.For information about routines used to create and send Apple events, see the chapter “Creating and Sending Apple Events” in this book. For information about routines and data structures used with object specifier records, see the chapter “Resolving and Creating Object Specifier Records” in this book.Data Structures Used by the Apple Event ManagerThis section summarizes the major data structures used by the Apple Event Manager. For an overview of the relationships among these data structures, see “Data Structures Within Apple Events,” which begins on page 3-12.Descriptor Records and Related Data StructuresDescriptor records are the fundamental data structures from which Apple events are constructed. A descriptor record is a data structure of type AEDesc. TYPE AEDesc =     RECORD                                            {descriptor record}        descriptorType:                        DescType;                {type of data being passed}        dataHandle:                         Handle;                {handle to data being passed}    END;Field descriptionsdescriptorTypeA four-character string of type DescType that indicates the type of data being passed.dataHandle    A handle to the data being passed.The descriptor type is a structure of type DescType, which in turn is of data type ResType—that is, a four-character code. Constants, rather than these four-character codes, are usually used to refer to descriptor types. Table 4-2 lists the constants for the basic descriptor types used by the Apple Event Manager.Table 4-2    Descriptor types used by the Apple Event Manager (excluding those used with object specifier records)(continued)Descriptor type    Value    Description    typeBoolean    'bool'    Boolean value    typeChar    'TEXT'    Unterminated string    typeLongInteger    'long'    32-bit integer    typeInteger    'long'    32-bit integer    typeShortInteger    'shor'    16-bit integer    typeSMInt    'shor'    16-bit integer    typeLongFloat    'doub'    SANE double    typeFloat    'doub'    SANE double    typeShortFloat    'sing'    SANE single    typeSMFloat    'sing'    SANE single    typeExtended    'exte'    SANE extended    typeComp    'comp'    SANE comp    typeMagnitude    'magn'    Unsigned 32-bit integer    typeAEList    'list'    List of descriptor records    typeAERecord    'reco'    List of keyword-specified descriptor records    typeAppleEvent    'aevt'    Apple event record    typeTrue    'true'    TRUE Boolean value            continued    typeFalse    'fals'    FALSE Boolean value    typeAlias    'alis'    Alias record    typeEnumerated    'enum'    Enumerated data    typeType    'type'    Four-character code for event class or event ID    typeAppParameters    'appa'    Process Manager launch parameters    typeProperty    'prop'    Apple event property    typeFSS    'fss '    File system specification    typeKeyword    'keyw'    Apple event keyword    typeSectionH    'sect'    Handle to a section record    typeWildCard    '****'    Matches any type    typeApplSignature    'sign'    Application signature    typeSessionID    'ssid'    Session reference number    typeTargetID    'targ'    Target ID record    typeProcessSerialNumber    'psn '    Process serial number    typeNull    'null'    Nonexistent data (data handle is NIL)      For information about descriptor records and descriptor types used with object specifier records, see the chapter “Resolving and Creating Object Specifier Records” in this book. Apple event attributes, Apple event parameters, object specifier records, tokens, and most of the other data structures used by the Apple Event Manager are constructed from one or more descriptor records. The Apple Event Manager identifies the various parts of an Apple event by means of keywords associated with the corresponding descriptor records. The AEKeyword data type is defined as a four-character code.TYPE        AEKeyword = PACKED ARRAY[1..4] OF Char;Constants are typically used for keywords. A keyword combined with a descriptor record forms a keyword-specified descriptor record, which is defined by a data structure of type AEKeyDesc.TYPE        AEKeyDesc =         RECORD            descKey:                    AEKeyword;                    {keyword}            descContent:                    AEDesc;                    {descriptor record}        END;Field descriptionsField descriptionsdescKey    A four-character code of type AEKeyword that identifies the data in the descContent field.descContent    A descriptor record of type AEDesc.Every Apple event includes an attribute that contains the address of the target application. A descriptor record that contains an application’s address is called an address descriptor record.TYPE        AEAddressDesc = AEDesc;                                        {address descriptor record}Many Apple Event Manager functions take or return lists of descriptor records in a special descriptor record called a descriptor list. A descriptor list is a structure of data type AEDescList whose data consists of a list of other descriptor records.TYPE        AEDescList = AEDesc;                                        {list of descriptor records}Other Apple Event Manager functions take or return lists of keyword-specified descriptor records in the form of an AE record. An AE record is a structure of data type AERecord whose data handle refers to a list of keyword-specified descriptor records.TYPE        AERecord = AEDescList;                                        {list of keyword-specified }                                                { descriptor records}The handle for a descriptor list of data type AERecord refers to a list of keyword-specified descriptor records that specify Apple event parameters; they cannot specify Apple event attributes.Finally, a full-fledged Apple event, including both attributes and parameters, is an Apple event record, which is a structure of data type AppleEvent.TYPE        AppleEvent = AERecord;                                        {list of attributes and     }                                                { parameters for an Apple }                                                { event}The event class and event ID of an Apple event are specified in Apple Event Manager routines by structures of data types AEEventClass and AEEventID, respectively.TYPE AEEventClass = PACKED ARRAY[1..4] OF Char;TYPE AEEventID = PACKED ARRAY[1..4] OF Char;For more information about descriptor records and the other data structures described in this section, see “Data Structures Within Apple Events,” which begins on page 3-12. With the exception of array data records, which are described in the next section, the other Apple Event Manager data structures used in responding to Apple events are described in “Routines for Responding to Apple Events,” beginning on page 4-61, under the descriptions of the routines that use them.Apple Event Array Data TypesThe AEGetArray function (see page 4-77) creates a Pascal or C array that corresponds to an Apple event array in a descriptor list, and the AEPutArray function (see page 5-31) adds data specified in a buffer to a descriptor list as an Apple event array. You can use the data type AEArrayType to define the type of Apple event array you want to add to or obtain from a descriptor list.TYPE AEArrayType = (kAEDataArray, kAEPackedArray, kAEHandleArray,                          kAEDescArray, kAEKeyDescArray);When your application adds an Apple event array to a descriptor list, it provides the data for an Apple event array in an array data record, which is defined by the data type AEArrayData.TYPE AEArrayData =     RECORD                                        {data for an Apple event array}        CASE AEArrayType OF        kAEDataArray:            (AEDataArray:                         ARRAY[0..0] OF Integer);        kAEPackedArray:            (AEPackedArray:                         PACKED ARRAY[0..0] OF Char);        kAEHandleArray:            (AEHandleArray:                         ARRAY[0..0] OF Handle);        kAEDescArray:            (AEDescArray:                         ARRAY[0..0] OF AEDesc);        kAEKeyDescArray:            (AEKeyDescArray:                         ARRAY[0..0] OF AEKeyDesc);    END;The type of array depends on the data for the array:Array type    Description of Apple event array    kAEDataArray    Array items consist of data of the same size and same type, and are aligned on word boundaries.    kAEPackedArray    Array items consist of data of the same size and same type, and are packed without regard for word boundaries.    kAEHandleArray    Array items consist of handles to data of variable size and the same type.    kAEDescArray    Array items consist of descriptor records of different descriptor types with data of variable size.    kAEKeyDescArray    Array items consist of keyword-specified descriptor records with different keywords, different descriptor types, and data of variable size.    Array items in Apple event arrays of type kAEDataArray, kAEPackedArray, or kAEHandleArray must be factored—that is, contained in a factored descriptor list. Before adding array items to a factored descriptor list, you should provide both a pointer to the data that is common to all array items and the size of that common data when you first call AECreateList to create a factored descriptor list. When you call AEPutArray to add the array data to such a descriptor list, the Apple Event Manager automatically isolates the common data you specified in the call to AECreateList.When you call AEGetArray or AEPutArray, you specify a pointer of data type AEArrayDataPointer that points to a buffer containing the data for the array.TYPE AEArrayDataPointer = ^AEArrayData; For more information about using AECreateList to create factored descriptor lists for arrays, see page 5-28. For information about using AEGetArray and AEPutArray, see page 4-77 and page 5-31, respectively.  Routines for Responding to Apple EventsThis section describes the Apple Event Manager routines you can use to create and manage the Apple event dispatch tables, dispatch Apple events, extract information from Apple events, request user interaction, request more time to respond to Apple events, suspend and resume Apple event handling, delete descriptor records, deallocate memory for descriptor records, create and manage the coercion handler and special handler dispatch tables, and get information about the Apple Event Manager.Because the Apple Event Manager uses the services of the Event Manager, which in turn uses the services of the PPC Toolbox, the routines described in this section may return Event Manager and PPC Toolbox result codes in addition to the Apple Event Manager result codes listed.Creating and Managing the Apple Event Dispatch TablesAn Apple event dispatch table contains entries that specify the event class and event ID that refer to one or more Apple events, the address of the handler routine that handles those Apple events, and a reference constant. You can use the AEInstallEventHandler function to add entries to the Apple event dispatch table. This function sets up the initial mapping between the handlers in your application and the Apple events that they handle.To get the address of a handler currently in the Apple event dispatch table, use the AEGetEventHandler function. If you need to remove any of your Apple event handlers after the mapping between handlers and Apple events is established, you can use the AERemoveEventHandler function. AEInstallEventHandlerYou can use the AEInstallEventHandler function to add an entry to either your application’s Apple event dispatch table or the system Apple event dispatch table.FUNCTION AEInstallEventHandler (theAEEventClass: AEEventClass;                                          theAEEventID: AEEventID;                                           handler: EventHandlerProcPtr;                                           handlerRefcon: LongInt;                                          isSysHandler: Boolean): OSErr;theAEEventClassThe event class for the Apple event or events to be dispatched for this entry. The AEEventClass data type is defined as a four-character code:                TYPE AEEventClass = PACKED ARRAY[1..4] OF Char;theAEEventIDThe event ID for the Apple event or events to be dispatched for this entry. The AEEventID data type is defined as a four-character code:                TYPE AEEventID = PACKED ARRAY[1..4] OF Char;handler     A pointer to an Apple event handler for this dispatch table entry. Note that a handler in the system dispatch table must reside in the system heap; this means that if the value of the isSysHandler parameter is TRUE, the handler parameter should point to a location in the system heap. Otherwise, if you put your system handler code in your application heap, you must use AERemoveEventHandler to remove the handler before your application terminates.handlerRefcon A reference constant that is passed by the Apple Event Manager to the handler each time the handler is called. If your handler doesn’t use a reference constant, use 0 as the value of this parameter. isSysHandler Specifies the dispatch table to which you want to add the handler. If the value of isSysHandler is TRUE, the Apple Event Manager adds the handler to the system Apple event dispatch table. Entries in the system dispatch table are available to all applications. If the value of isSysHandler is FALSE, the Apple Event Manager adds the handler to your application’s Apple event dispatch table. The application’s dispatch table is searched first; the system dispatch table is searched only if the necessary handler is not found in your application’s dispatch table.DESCRIPTIONThe AEInstallEventHandler function creates an entry in the Apple event dispatch table. You must supply parameters that specify the event class, the event ID, the address of the handler that handles Apple events of the specified event class and event ID, and whether the handler is to be added to the system Apple event dispatch table or your application’s Apple event dispatch table. You can also specify a reference constant that the Apple Event Manager passes to your handler whenever your handler processes an Apple event.The parameters theAEEventClass and theAEEventID specify the event class and event ID of the Apple events to be handled by the handler for this dispatch table entry. For these parameters, you must provide one of the following combinations:n    the event class and event ID of a single Apple event to be dispatched to the handlern    the typeWildCard constant for theAEEventClass and an event ID for theAEEventID, which indicate that Apple events from all event classes whose event IDs match theAEEventID should be dispatched to the handlern    an event class for theAEEventClass and the typeWildCard constant for theAEEventID, which indicate that all events from the specified event class should be dispatched to the handlern    the typeWildCard constant for both the theAEEventClass and theAEEventID parameters, which indicates that all Apple events should be dispatched to the handler IMPORTANTIf you use the typeWildCard constant for either the theAEEventClass or the theAEEventID parameter (or for both parameters), the corresponding handler must return the error errAEEventNotHandled if it does not handle a particular event.sIf there was already an entry in the specified dispatch table for the same event class and event ID, it is replaced. Therefore, before installing a handler for a particular Apple event in the system dispatch table, use the AEGetEventHandler function (described next) to determine whether the table already contains a handler for that event. If an entry exists, AEGetEventHandler returns a reference constant and a pointer to that event handler. Chain the existing handler to your handler by providing pointers to the previous handler and its reference constant in the handlerRefcon parameter of AEInstallEventHandler. When your handler is done, use these pointers to call the previous handler. If you remove your system Apple event handler, be sure to reinstall the chained handler. SPECIAL CONSIDERATIONSBefore an application calls a system Apple event handler, system software has set up the A5 register for the calling application. For this reason, if you provide a system Apple event handler, it should never use A5 global variables or anything that depends on a particular context; otherwise, the application that calls the system handler may crash.RESULT CODESnoErr    0    No error    paramErr    –50    Parameter error (handler pointer is NIL or odd)    memFullErr    –108    Not enough room in heap zone    SEE ALSOFor more information about installing Apple event handlers, see “Installing Entries in the Apple Event Dispatch Tables,” which begins on page 4-7.AEGetEventHandlerYou can use the AEGetEventHandler function to get an entry from an Apple event dispatch table.FUNCTION AEGetEventHandler (theAEEventClass: AEEventClass;                                      theAEEventID: AEEventID;                                      VAR handler: EventHandlerProcPtr;                                         VAR handlerRefcon: LongInt;                                      isSysHandler: Boolean): OSErr;theAEEventClassThe value of the event class field of the dispatch table entry for the desired handler.theAEEventIDThe value of the event ID field of the dispatch table entry for the desired handler.handler    The AEGetEventHandler function returns, in this parameter, a pointer to the specified handler.handlerRefconThe AEGetEventHandler function returns, in this parameter, the reference constant from the dispatch table entry for the specified handler.isSysHandler Specifies the Apple event dispatch table from which to get the handler. If the value of isSysHandler is TRUE, the AEGetEventHandler function returns the handler from the system dispatch table. If the value is FALSE, AEGetEventHandler returns the handler from your application’s dispatch table.DESCRIPTIONThe AEGetEventHandler function returns, in the handler parameter, a pointer to the handler for the Apple event dispatch table entry you specify in the parameters theAEEventClass and theAEEventID. You can use the typeWildCard constant for either or both of these parameters; however, AEGetEventHandler returns an error unless an entry exists that specifies typeWildCard in exactly the same way. For example, if you specify typeWildCard in both the theAEEventClass parameter and the theAEEventID parameter, the Apple Event Manager will not return the first handler for any event class and event ID in the dispatch table; instead, the dispatch table must contain an entry that specifies type typeWildCard for both the event class and the event ID. RESULT CODESnoErr    0    No error    errAEHandlerNotFound    –1717    No handler found for an Apple event    SEE ALSOFor an explanation of wildcard values, see the description of the AEInstallEventHandler function on page 4-62.AERemoveEventHandlerYou can use the AERemoveEventHandler function to remove an entry from an Apple event dispatch table.FUNCTION AERemoveEventHandler (theAEEventClass: AEEventClass;                                          theAEEventID: AEEventID;                                          handler: EventHandlerProcPtr;                                          isSysHandler: Boolean): OSErr;theAEEventClassThe event class for the handler whose entry you want to remove from the dispatch table.theAEEventIDThe event ID for the handler whose entry you want to remove from the Apple event dispatch table.handler    A pointer to the handler to be removed. Although the parameters theAEEventClass and theAEEventID would be sufficient to identify the handler to be removed, providing the handler parameter is a recommended safeguard that ensures that you remove the correct handler. If the value of this parameter is NIL, the Apple Event Manager relies solely on the event class and event ID to identify the handler to be removed.isSysHandler Specifies the dispatch table from which to remove the handler. If the value of isSysHandler is TRUE, AERemoveEventHandler removes the handler from the system dispatch table. If the value is FALSE, AERemoveEventHandler removes the handler from your application’s dispatch table.DESCRIPTIONThe AERemoveEventHandler function removes the Apple event dispatch table entry you specify in the parameters theAEEventClass, theAEEventID, and handler. You can use the typeWildCard constant for the theAEEventClass or the theAEEventID parameter, or for both parameters; however, AERemoveEventHandler returns an error unless an entry exists that specifies typeWildCard in exactly the same way. For example, if you specify typeWildCard in both the theAEEventClass parameter and the theAEEventID parameter, the Apple Event Manager will not remove the first handler for any event class and event ID in the dispatch table; instead, the dispatch table must contain an entry that specifies type typeWildCard for both the event class and the event ID. RESULT CODESnoErr    0    No error    errAEHandlerNotFound    –1717    No handler found for an Apple event    SEE ALSOFor an explanation of wildcard values, see the description of the AEInstallEventHandler function on page 4-62.Dispatching Apple EventsAfter receiving a high-level event (and optionally determining whether it is a type of high-level event other than an Apple event that your application might support), your application typically calls the AEProcessAppleEvent function to determine the type of Apple event received and call the corresponding handler.AEProcessAppleEventYou can use the AEProcessAppleEvent function to call the appropriate handler for a specified Apple event.  FUNCTION AEProcessAppleEvent                                 (theEventRecord: EventRecord): OSErr;theEventRecordThe event record for the Apple event.DESCRIPTIONThe AEProcessAppleEvent function looks first in the application’s special handler dispatch table for an entry that was installed with the constant keyPreDispatch. If the application’s special handler dispatch table does not include such a handler or if the handler returns errAEEventNotHandled, the function looks in the application’s Apple event dispatch table for an entry that matches the event class and event ID of the specified Apple event. If the application’s Apple event dispatch table does not include such a handler or if the handler returns errAEEventNotHandled, the AEProcessAppleEvent function looks in the system special handler dispatch table for an entry that was installed with the constant keyPreDispatch. If the system special handler dispatch table does not include such a handler or if the handler returns errAEEventNotHandled, the function looks in the system Apple event dispatch table for an entry that matches the event class and event ID of the specified Apple event. If the system Apple event dispatch table does not include such a handler, the Apple Event Manager returns the result code errAEEventNotHandled to the server application and, if the client application is waiting for a reply, to the client application.If AEProcessAppleEvent finds an entry in one of the dispatch tables that matches the event class and event ID of the specified Apple event, it calls the corresponding handler.SPECIAL CONSIDERATIONSIf an Apple event dispatch table contains one entry for an event class and a specific event ID, and also contains another entry that is identical except that it specifies a wildcard value for either the event class or the event ID, the Apple Event Manager dispatches the more specific entry. For example, if an Apple event dispatch table includes one entry that specifies the event class as kAECoreSuite and the event ID as kAEDelete, and another entry that specifies the event class as kAECoreSuite and the event ID as typeWildCard, the Apple Event Manager dispatches the Apple event handler associated with the entry that specifies the event ID as kAEDelete.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    bufferIsSmall    –607    Buffer is too small    noOutstandingHLE    –608    No outstanding high-level event    errAECorruptData    –1702    Data in an Apple event could not be read    errAENewerVersion    –1706    Need a newer version of the Apple Event Manager    errAEEventNotHandled    –1708    Event wasn’t handled by an Apple event handler     SEE ALSOFor an example of the use of AEProcessAppleEvent, see Listing 4-2 on page 4-6. For a description of an Apple event handler, see page 4-105. For more information about event processing, see the chapter “Event Manager” in Inside Macintosh: Macintosh Toolbox Essentials.   Getting Data or Descriptor Records Out of Apple Event Parameters and AttributesThe Apple Event Manager provides four functions that allow you to get data from Apple event parameters and attributes. The AEGetParamPtr and AEGetParamDesc functions get data from a specified Apple event parameter. The AEGetAttributePtr and AEGetAttributeDesc functions get data from a specified Apple event attribute. AEGetParamPtrYou can use the AEGetParamPtr function to get a pointer to a buffer that contains the data from a specified Apple event parameter.FUNCTION AEGetParamPtr (theAppleEvent: AppleEvent;                                     theAEKeyword: AEKeyword;                                desiredType: DescType;                                 VAR typeCode: DescType; dataPtr: Ptr;                                 maximumSize: Size;                                 VAR actualSize: Size): OSErr;theAppleEventThe Apple event containing the desired parameter.theAEKeyword The keyword that specifies the desired parameter.desiredTypeThe desired descriptor type for the data to be returned; if the requested Apple event parameter is not of this type, the Apple Event Manager attempts to coerce it to this type. If the value of desiredType is typeWildCard, no coercion is performed, and the descriptor type of the returned data is the same as the descriptor type of the Apple event parameter. typeCode     The descriptor type of the returned data.dataPtr     A pointer to the buffer in which the returned data is stored.maximumSize The maximum length, in bytes, of the data to be returned. You must allocate at least this amount of storage for the buffer specified by the dataPtr parameter. actualSizeThe length, in bytes, of the data for the specified Apple event parameter. If this value is larger than the value of the maximumSize parameter, not all of the data for the parameter was returned.DESCRIPTIONThe AEGetParamPtr function uses a buffer to return the data from a specified Apple event parameter, which it attempts to coerce to the descriptor type specified by the desiredType parameter. RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAECoercionFail     –1700    Data could not be coerced to the requested descriptor type    errAEDescNotFound     –1701    Descriptor record was not found    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEReplyNotArrived    –1718    Reply has not yet arrived    SEE ALSOFor examples of the use of AEGetParamPtr, see “Getting Data Out of an Apple Event,” which begins on page 4-25.AEGetParamDescYou can use the AEGetParamDesc function to get the descriptor record for a specified Apple event parameter.  FUNCTION AEGetParamDesc (theAppleEvent: AppleEvent;                                  theAEKeyword: AEKeyword;                                  desiredType: DescType;                                  VAR result: AEDesc): OSErr;theAppleEventThe Apple event containing the desired parameter.theAEKeyword The keyword that specifies the desired parameter.desiredType The desired descriptor type for the descriptor record to be returned; if the requested Apple event parameter is not of this type, the Apple Event Manager attempts to coerce it to this type. If the value of desiredType is typeWildCard, no coercion is performed, and the descriptor type of the returned data is the same as the descriptor type of the Apple event parameter. result     The descriptor record from the desired Apple event parameter coerced to the descriptor type specified in desiredType.DESCRIPTIONThe AEGetParamDesc function returns, in the result parameter, the descriptor record for a specified Apple event parameter, which it attempts to coerce to the descriptor type specified by the desiredType parameter. Your application should call the AEDisposeDesc function to dispose of the resulting descriptor record after your application has finished using it.If AEGetParamDesc returns a nonzero result code, it returns a null descriptor record unless the Apple Event Manager is not available because of limited memory.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAECoercionFail     –1700    Data could not be coerced to the requested descriptor type    errAEDescNotFound     –1701    Descriptor record was not found    errAENotAEDesc    –1704    Not a valid descriptor record    errAEReplyNotArrived    –1718    Reply has not yet arrived    SEE ALSOFor an example of the use of AEGetParamDesc, see “Getting Data Out of an Apple Event Parameter,” which begins on page 4-26.   AEGetAttributePtrYou can use the AEGetAttributePtr function to get a pointer to a buffer that contains the data from a specified Apple event attribute.FUNCTION AEGetAttributePtr (theAppleEvent: AppleEvent;                                      theAEKeyword: AEKeyword;                                      desiredType: DescType;                                         VAR typeCode: DescType; dataPtr: Ptr;                                         maximumSize: Size;                                      VAR actualSize: Size): OSErr;theAppleEventThe Apple event containing the desired attribute.theAEKeywordThe keyword that specifies the desired attribute.    TYPE AEKeyword = PACKED ARRAY[1..4] OF Char;    The keyword can be any of the constants listed in the description that follows.desiredTypeThe desired descriptor type for the data to be returned; if the requested Apple event attribute is not of this type, the Apple Event Manager attempts to coerce it to this type. If the value of desiredType is typeWildCard, no coercion is performed, and the descriptor type of the returned data is the same as the descriptor type of the Apple event attribute. typeCode    The descriptor type of the returned data.dataPtr     A pointer to the buffer in which the returned data is stored.maximumSize The maximum length, in bytes, of the data to be returned. You must allocate at least this amount of storage for the buffer specified by the dataPtr parameter. actualSizeThe length, in bytes, of the data for the specified Apple event attribute. If this value is larger than the value of the maximumSize parameter, not all of the data for the attribute was returned.DESCRIPTIONThe AEGetAttributePtr function uses a buffer to return the data from an Apple event attribute with the specified keyword, which it attempts to coerce to the descriptor type specified by the desiredType parameter. You can specify the parameter theAEKeyWord using any of these constants:CONST    keyAddressAttr                                 = 'addr'; {address of target or }                                                 { client application}    keyEventClassAttr                                 = 'evcl'; {event class}    keyEventIDAttr                                = 'evid'; {event ID}    keyEventSourceAttr                                = 'esrc'; {nature of source }                                                 { application}    keyInteractLevelAttr                                = 'inte'; {settings to allow the }                                                 { Apple Event Manager to }                                                 { bring server application }                                                 { to the foreground}    keyMissedKeywordAttr                                = 'miss'; {first required parameter }                                                 { remaining in Apple event}    keyOptionalKeywordAttr                                = 'optk'; {list of optional }                                                 { parameters for Apple }                                                 { event}    keyOriginalAddressAttr                                = 'from';             {address of original source }                                                 { of Apple event; available }                                                 { beginning with version }                                                 { 1.01 of Apple Event }                                                 { Manager}         keyReturnIDAttr                                 = 'rtid'; {return ID for reply Apple }                                                 { event}    keyTimeoutAttr                                = 'timo'; {length of time in ticks }                                                 { that client will wait }                                                 { for reply or result from }                                                  { the server}    keyTransactionIDAttr                                = 'tran'; {transaction ID identifying }                                                 { a series of Apple events}RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAECoercionFail     –1700    Data could not be coerced to the requested descriptor type    errAEDescNotFound     –1701    Descriptor record was not found    errAENotAEDesc    –1704    Not a valid descriptor record    errAEReplyNotArrived    –1718    Reply has not yet arrived    SEE ALSOFor an example of the use of the AEGetAttributePtr function, see “Getting Data Out of an Attribute” and “Writing Apple Event Handlers,” which begin on page 4-28 and page 4-33, respectively.AEGetAttributeDescYou can use the AEGetAttributeDesc function to get the descriptor record for a specified Apple event attribute.   FUNCTION AEGetAttributeDesc (theAppleEvent: AppleEvent;                                       theAEKeyword: AEKeyword;                                       desiredType: DescType;                                           VAR result: AEDesc): OSErr;theAppleEventThe Apple event containing the desired attribute.theAEKeyword The keyword that specifies the desired attribute.    TYPE AEKeyword = PACKED ARRAY[1..4] OF Char;    The keyword can be any of the constants listed in the description of AEGetAttributePtr on page 4-71.desiredTypeThe desired descriptor type for the descriptor record to be returned; if the requested Apple event attribute is not of this type, the Apple Event Manager attempts to coerce it to this type. If the value of desiredType is typeWildCard, no coercion is performed, and the descriptor type of the returned data is the same as the descriptor type of the Apple event attribute. result     A copy of the descriptor record from the desired attribute coerced to the descriptor type specified by the desiredType parameter.DESCRIPTIONThe AEGetAttributeDesc function returns, in the result parameter, the descriptor record for the Apple event attribute with the specified keyword. Your application should call the AEDisposeDesc function to dispose of the resulting descriptor record after your application has finished using it.If AEGetAttributeDesc returns a nonzero result code, it returns a null descriptor record unless the Apple Event Manager is not available because of limited memory. RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAECoercionFail    –1700    Data could not be coerced to the requested descriptor type    errAEDescNotFound    –1701    Descriptor record was not found    errAENotAEDesc    –1704    Not a valid descriptor record    errAEReplyNotArrived    –1718    Reply has not yet arrived    Counting the Items in Descriptor ListsThe AECountItems function counts the number of descriptor records in any descriptor list, including an Apple event record.AECountItemsYou can use the AECountItems function to count the number of descriptor records in any descriptor list.FUNCTION AECountItems (theAEDescList: AEDescList;                               VAR theCount: LongInt): OSErr;theAEDescListThe descriptor list to be counted.theCount    The AECountItems function returns the number of descriptor records in the specified descriptor list in this parameter.RESULT CODESnoErr    0    No error    errAENotAEDesc    –1704    Not a valid descriptor record     SEE ALSOFor an example of the use of AECountItems, see “Getting Data Out of a Descriptor List,” which begins on page 4-31.Getting Items From Descriptor ListsThe Apple Event Manager provides three functions that allow you to get items from any descriptor list, including an Apple event record. The AEGetNthPtr and AEGetNthDesc functions give you access to the data in a descriptor list. The AEGetArray function gets data from an array contained in a descriptor list.AEGetNthPtrYou can use the AEGetNthPtr function to get a pointer to a buffer that contains a copy of a descriptor record from any descriptor list.FUNCTION AEGetNthPtr (theAEDescList: AEDescList; index: LongInt;                              desiredType: DescType;                              VAR theAEKeyword: AEKeyword;                              VAR typeCode: DescType; dataPtr: Ptr;                              maximumSize: Size;                              VAR actualSize: Size): OSErr;theAEDescListThe descriptor list containing the desired descriptor record.index    The position of the desired descriptor record in the list (for example, 2 specifies the second descriptor record).desiredTypeThe desired descriptor type for the copy of the descriptor record to be returned; if the desired descriptor record is not of this type, the Apple Event Manager attempts to coerce it to this type. If the value of desiredType is typeWildCard, no coercion is performed, and the descriptor type of the copied descriptor record is the same as the descriptor type of the original descriptor record.theAEKeywordThe keyword of the specified descriptor record, if you are getting data from a list of keyword-specified descriptor records; otherwise, AEGetNthPtr returns the value typeWildCard. typeCode    The descriptor type of the returned descriptor record.dataPtr     A pointer to the buffer in which the returned descriptor record is stored.maximumSizeThe maximum length, in bytes, of the data to be returned. You must allocate at least this amount of storage for the buffer specified by the dataPtr parameter.actualSizeThe length, in bytes, of the data for the specified descriptor record. If this value is larger than the value of the maximumSize parameter, not all of the data for the descriptor record was returned.DESCRIPTIONThe AEGetNthPtr function uses a buffer to return a specified descriptor record from a specified descriptor list; the function attempts to coerce the descriptor record to the descriptor type specified by the desiredType parameter.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAECoercionFail     –1700    Data could not be coerced to the requested descriptor type    errAEDescNotFound     –1701    Descriptor record was not found    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEReplyNotArrived    –1718    Reply has not yet arrived    SEE ALSOFor an example of the use of AEGetNthPtr, see Listing 4-10 on page 4-33.AEGetNthDescYou can use the AEGetNthDesc function to get a copy of a descriptor record from any descriptor list. FUNCTION AEGetNthDesc (theAEDescList: AEDescList; index: LongInt;                               desiredType: DescType;                               VAR theAEKeyword: AEKeyword;                               VAR result: AEDesc): OSErr;theAEDescList The descriptor list containing the desired descriptor record.index     The position of the desired descriptor record in the list (for example, 2 specifies the second descriptor record).desiredType The desired descriptor type for the copy of the descriptor record to be returned; if the desired descriptor record is not of this type, the Apple Event Manager attempts to coerce it to this type. If the value of desiredType is typeWildCard, no coercion is performed, and the descriptor type of the copied descriptor record is the same as the descriptor type of the original descriptor record.theAEKeywordThe keyword of the specified descriptor record, if you are getting data from a list of keyword-specified descriptor records; otherwise, AEGetNthDesc returns the value typeWildCard. result    A copy of the desired descriptor record coerced to the descriptor type specified by the desiredType parameter.DESCRIPTIONThe AEGetNthDesc function returns a specified descriptor record from a specified descriptor list.Your application should call the AEDisposeDesc function to dispose of the resulting descriptor record after your application has finished using it.If AEGetNthDesc returns a nonzero result code, it returns a descriptor record of descriptor type typeNull. A descriptor record of this type does not contain any data.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAECoercionFail     –1700    Data could not be coerced to the requested descriptor type    errAEDescNotFound     –1701    Descriptor record was not found    errAENotAEDesc    –1704    Not a valid descriptor record    errAEReplyNotArrived    –1718    Reply has not yet arrived     AEGetArrayYou can use the AEGetArray function to convert an Apple event array (an array created with the AEPutArray function and stored in a descriptor list) to the corresponding Pascal or C array and place the converted array in a buffer for which you have provided a pointer.FUNCTION AEGetArray (theAEDescList: AEDescList;                             arrayType: AEArrayType;                             arrayPtr: AEArrayDataPointer;                             maximumSize: Size;                             VAR itemType: DescType; VAR itemSize: Size;                             VAR itemCount: LongInt): OSErr;theAEDescList A descriptor list containing the desired array. If the array is of type kAEDataArray, kAEPackedArray, or kAEHandleArray, the descriptor list must be factored. arrayType     The Apple event array type to be converted. This is specified by one of the following constants: kAEDataArray, kAEPackedArray, kAEHandleArray, kAEDescArray, or kAEKeyDescArray.arrayPtr     A pointer to the buffer for storing the array.maximumSize The maximum length, in bytes, of the buffer for storing the array.itemType    For arrays of type kAEDataArray, kAEPackedArray, or kAEHandleArray, the AEGetArray function returns the descriptor type of the returned array items in this parameter. itemSize    For arrays of type kAEDataArray or kAEPackedArray, the AEGetArray function returns the size (in bytes) of the returned array items in this parameter.itemCount     The AEGetArray function returns the number of items in the resulting array in this parameter.DESCRIPTIONThe AEGetArray function uses a buffer identified by the pointer in the arrayPtr parameter to return the converted data for the Apple event array specified by the theAEDescList parameter. Even if the descriptor list that contains the array is factored, the converted data for each array item includes the data common to all the descriptor records in the list. The Apple Event Manager automatically reconstructs the common data for each item when you call AEGetArray.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEReplyNotArrived    –1718    Reply has not yet arrived    SEE ALSOFor more information about data types and constants used with AEGetArray, see “Apple Event Array Data Types” on page 4-60.For information about creating and factoring descriptor lists for Apple event arrays, see the description of AECreateList on page 5-28. For information about adding an Apple event array to a descriptor list, see the description of AEPutArray on page 5-31.Getting Data and Keyword-Specified Descriptor Records Out of AE RecordsThe Apple Event Manager provides two functions, AEGetKeyPtr and AEGetKeyDesc, that allow you to get data and descriptor records out of an AE record or an Apple event record.AEGetKeyPtrYou can use the AEGetKeyPtr function to get a pointer to a buffer that contains the data from a keyword-specified descriptor record. You can use this function to get data from an AE record or an Apple event record.FUNCTION AEGetKeyPtr (theAERecord: AERecord;                              theAEKeyword: AEKeyword;                              desiredType: DescType;                              VAR typeCode: DescType;                              dataPtr: Ptr; maximumSize: Size;                              VAR actualSize: Size): OSErr;theAERecord The AE record containing the desired data.theAEKeywordThe keyword that specifies the desired descriptor record.desiredTypeThe desired descriptor type for the data to be returned; if the requested data is not of this type, the Apple Event Manager attempts to coerce it to this type. If the value of desiredType is typeWildCard, no coercion is performed, and the descriptor type of returned data is the same as the descriptor type of the original data. typeCode    The descriptor type of the returned data.dataPtr     A pointer to the buffer for storing the data.maximumSize The maximum length, in bytes, of the data to be returned. You must allocate at least this amount of storage for the buffer specified by the dataPtr parameter.actualSizeThe length, in bytes, of the data for the keyword-specified descriptor record. If this value is larger than the value of the maximumSize parameter, not all of the data for the parameter was returned.DESCRIPTIONThe AEGetKeyPtr function uses a buffer to return the data from a keyword-specified Apple event parameter, which the function attempts to coerce to the descriptor type specified by the desiredType parameter. RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAECoercionFail     –1700    Data could not be coerced to the requested descriptor type    errAEDescNotFound     –1701    Descriptor record was not found    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEReplyNotArrived    –1718    Reply has not yet arrived    AEGetKeyDescYou can use the AEGetKeyDesc function to get the descriptor record for a keyword-specified descriptor record. You can use this function to get a descriptor record out of an AE record or an Apple event record.FUNCTION AEGetKeyDesc (theAERecord: AERecord;                               theAEKeyword: AEKeyword;                                  desiredType: DescType;                               VAR result: AEDesc): OSErr;theAERecord The AE record containing the desired descriptor record.theAEKeywordThe keyword that specifies the desired descriptor record.desiredTypeThe desired descriptor type for the descriptor record to be returned; if the requested descriptor record is not of this type, the Apple Event Manager attempts to coerce it to this type. If the value of desiredType is typeWildCard, no coercion is performed, and the descriptor type of the returned descriptor record is the same as the descriptor type of the original descriptor record.result    A copy of the keyword-specified descriptor record, coerced to the descriptor type specified in the desiredType parameter. DESCRIPTIONThe AEGetKeyDesc function returns a copy of the descriptor record for a keyword-specified descriptor record. Your application should call the AEDisposeDesc function to dispose of the resulting descriptor record after your application has finished using it. If AEGetKeyDesc returns a nonzero result code, it returns a descriptor record of descriptor type typeNull. A descriptor record of this type does not contain any data.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAECoercionFail    –1700    Data could not be coerced to the requested descriptor type    errAEDescNotFound    –1701    Descriptor record was not found    errAENotAEDesc    –1704    Not a valid descriptor record    errAEReplyNotArrived    –1718    Reply has not yet arrived     Requesting User InteractionThe Apple Event Manager provides three functions that allow you to set or request user interaction levels and to initiate user interaction when your application is the server application. The AESetInteractionAllowed and AEGetInteractionAllowed functions specify and return, respectively, the current user interaction preferences. Your application should call the AEInteractWithUser function before actually interacting with the user in response to an Apple event. AESetInteractionAllowedYou can use the AESetInteractionAllowed function to specify your application’s user interaction preferences for responding to an Apple event.FUNCTION AESetInteractionAllowed                                         (level: AEInteractAllowed): OSErr;level    The user interaction level to be set.DESCRIPTIONThe AESetInteractionAllowed function sets the user interaction level for a server application’s response to an Apple event. The level parameter must be one of three flags: kAEInteractWithSelf, kAEInteractWithLocal, or kAEInteractWithAll. Specifying the kAEInteractWithSelf flag allows the server application to interact with the user in response to an Apple event only when the client application and server application are the same—that is, only when the application is sending the Apple event to itself.Specifying the kAEInteractWithLocal flag allows the server application to interact with the user in response to an Apple event only if the client application is on the same computer as the server application; this is the default if the AESetInteractionAllowed function is not used.Specifying the kAEInteractWithAll flag allows the server application to interact with the user in response to an Apple event sent from any client application on any computer.RESULT CODEnoErr    0    No error    SEE ALSOFor more information about setting user preferences for a server application, see “Setting the Server Application’s User Interaction Preferences” on page 4-48.AEGetInteractionAllowedYou can use the AEGetInteractionAllowed function to get the current user interaction preferences for responding to an Apple event.FUNCTION AEGetInteractionAllowed                                 (VAR level: AEInteractAllowed): OSErr;level    The current user interaction level, using the data type AEInteractAllowed.    TYPE AEInteractAllowed = (kAEInteractWithSelf,                           kAEInteractWithLocal,                           kAEInteractWithAll);DESCRIPTIONThe AEGetInteractionAllowed function returns, in the level parameter, a value that indicates the user interaction preferences for responding to an Apple event. The value, set by a previous call to AESetInteractionAllowed, is one of the following flags: kAEInteractWithSelf, kAEInteractWithLocal, or kAEInteractWithAll. The default value of kAEInteractWithLocal is returned if your application has not used AESetInteractionAllowed to set the interaction level explicitly. The kAEInteractWithSelf flag indicates that the server application may interact with the user in response to an Apple event only when the client application and server application are the same—that is, only when the application is sending the Apple event to itself.The kAEInteractWithLocal flag indicates that the server application may interact with the user in response to an Apple event only if the client application is on the same computer as the server application. This is the default if your application has not used the AESetInteractionAllowed function to set the interaction level explicitly.The kAEInteractWithAll flag indicates that the server application may interact with the user in response to an Apple event sent from any client application on any computer.RESULT CODEnoErr    0    No error    AEInteractWithUserYou can use the AEInteractWithUser function to initiate interaction with the user when your application is a server application responding to an Apple event.FUNCTION AEInteractWithUser (timeOutInTicks: LongInt;                                       nmReqPtr: NMRecPtr;                                       idleProc: IdleProcPtr): OSErr;timeOutInTicks The amount of time (in ticks) that your handler is willing to wait for a response from the user. You can specify a number of ticks or use one of the following constants:    CONST kAEDefaultTimeout = -1; {value determined }                                                      { by AEM}      kNoTimeOut        = -2; {wait until reply }                              { comes back}nmReqPtr     A pointer to a Notification Manager record provided by your application. You can specify NIL for this parameter to get the default notification handling provided by the Apple Event Manager.idleProc     A pointer to your application’s idle function, which handles events while waiting for the Apple Event Manager to return control. DESCRIPTIONYour application should call the AEInteractWithUser function before displaying a dialog box or alert box or otherwise interacting with the user in response to an Apple event. If the user interaction preference settings permit the application to come to the foreground, this function brings your application to the front, either directly or by posting a notification request.Your application should normally pass a notification record in the nmReqPtr parameter rather than specifying NIL for default notification handling. If you specify NIL, the Apple Event Manager looks for an application icon with the ID specified by the application’s bundle ('BNDL') resource and the application’s file reference ('FREF') resource. The Apple Event Manager first looks for an 'SICN' resource with the specified ID; if it can’t find an 'SICN' resource, it looks for the 'ICN#' resource and compresses the icon to fit in the menu bar. The Apple Event Manager won’t look for any members of an icon family other than the icon specified in the 'ICN#' resource.If the application doesn’t have 'SICN' or 'ICN#' resources, or if it doesn’t have a file reference resource, the Apple Event Manager passes NIL to the Notification Manager, and no icon appears in the upper-right corner of the screen. Therefore, if you want to display any icon other than those of type 'SICN' or 'ICN#', you must specify a notification record as the second parameter to the AEInteractWithUser function.NoteNoteIf you want the Notification Manager to use a color icon when it posts a notification request, you should provide a Notification Manager record that specifies a 'cicn' resource.uThe AEInteractWithUser function checks whether the client application set the kAENeverInteract flag for the Apple event and, if so, returns an error. If not, then the AEInteractWithUser function checks the server application’s preference set by the AESetInteractionAllowed function and compares it against the source of the Apple event—that is, whether it came from the same application, another process on the same computer, or a process running on another computer. The AEInteractWithUser function returns the errAENoUserInteraction result code if the user interaction preferences don’t allow user interaction. If user interaction is allowed, the Apple Event Manager brings your application to the front, either directly or by posting a notification request. If AEInteractWithUser returns the noErr result code, then your application is in the foreground and is free to interact with the user.RESULT CODESnoErr    0    No error    errAETimeout    –1712    Apple event timed out    errAENoUserInteraction    –1713    No user interaction allowed    SEE ALSOFor information about idle functions, see “Writing an Idle Function” on page 5-21.For examples of the use of the AEInteractWithUser function, see “Interacting With the User,” which begins on page 4-45.Requesting More Time to Respond to Apple EventsThe AEResetTimer function resets the timeout value for an Apple event to its starting value. A server application can call this function when it knows it cannot fulfill a client application’s request (either by returning a result or by sending back a reply Apple event) before the client application is due to time out.AEResetTimerYou can use the AEResetTimer function to reset the timeout value for an Apple event to its starting value.FUNCTION AEResetTimer (reply: AppleEvent): OSErr;reply    The default reply for an Apple event, provided by the Apple Event Manager.DESCRIPTIONWhen your application calls AEResetTimer, the Apple Event Manager for the server application uses the default reply to send a Reset Timer event to the client application; the Apple Event Manager for the client application’s computer intercepts this Apple event and resets the client application’s timer for the Apple event. (The Reset Timer event is never dispatched to a handler, so the client application does not need a handler for it.)RESULT CODEnoErr    0    No error    errAEReplyNotValid    –1709    AEResetTimer was passed an invalid reply     Suspending and Resuming Apple Event HandlingWhen your application calls AEProcessAppleEvent and one of your event handlers is invoked, the Apple Event Manager normally assumes that your application has finished handling the event when the event handler returns. At this point, the Apple Event Manager disposes of the event. However, some applications, such as multi-session servers or any applications that implement their own internal event queueing, may need to defer handling of the event.The AESuspendTheCurrentEvent, AEResumeTheCurrentEvent, AESetTheCurrentEvent, and AEGetTheCurrentEvent functions described in this section allow you to suspend and resume Apple event handling, specify the Apple event to be handled, and identify an Apple event that is currently being handled. AESuspendTheCurrentEventYou can use the AESuspendTheCurrentEvent function to suspend the processing of the Apple event that is currently being handled. FUNCTION AESuspendTheCurrentEvent                                     (theAppleEvent: AppleEvent): OSErr;theAppleEventThe Apple event whose handling is to be suspended. Although the Apple Event Manager doesn’t need this parameter to identify the Apple event currently being handled, providing it is a safeguard that you are suspending the correct Apple event.DESCRIPTIONAfter a server application makes a successful call to the AESuspendTheCurrentEvent function, it is no longer required to return a result or a reply for the Apple event that was being handled. It can, however, return a result if it later calls the AEResumeTheCurrentEvent function to resume event processing.The Apple Event Manager does not automatically dispose of Apple events that have been suspended or their default replies. (The Apple Event Manager does, however, automatically dispose of a previously suspended Apple event and its default reply if the server later resumes processing of the Apple event by calling the AEResumeTheCurrentEvent function.) If your server application does not resume processing of a suspended Apple event, it is responsible for using the AEDisposeDesc function to dispose of both the Apple event and its default reply when your application has finished using them.SPECIAL CONSIDERATIONSIf your application suspends handling of an Apple event it sends to itself, the Apple Event Manager immediately returns from the AESend call with the error code errAETimeout, regardless of whether the kAEQueueReply, kAEWaitReply, or kAENoReply flags were set, even if the timeout parameter is set to kNoTimeOut. The routine calling AESend should take the timeout error as confirmation that the event was sent.As with other calls to AESend that return a timeout error, the handler continues to process the event nevertheless. The handler’s reply, if any, is provided in the reply event when the handling is completed. The Apple Event Manager provides no notification that the reply is ready. If no data has yet been placed in the reply event, the Apple Event Manager returns errAEReplyNotArrived when your application attempts to extract data from the reply.RESULT CODEnoErr    0    No error    AEResumeTheCurrentEventYou can use the AEResumeTheCurrentEvent function to inform the Apple Event Manager that your application wants to resume the handling of a previously suspended Apple event or that it has completed the handling of the Apple event.FUNCTION AEResumeTheCurrentEvent                                     (theAppleEvent, reply: AppleEvent;                                      dispatcher: EventHandlerProcPtr;                                      handlerRefcon: LongInt): OSErr;theAppleEventThe Apple event to be resumed.reply     The default reply provided by the Apple Event Manager for the Apple event.dispatcherOne of the following:n    a pointer to a routine for handling the eventn    the kAEUseStandardDispatch constant, which tells the Apple Event Manager to dispatch the resumed event using the standard dispatching scheme it uses for other Apple eventsn    the kAENoDispatch constant, which tells the Apple Event Manager that the Apple event has been completely processed and need not be dispatchedhandlerRefcon If the value of the dispatcher parameter is not kAEUseStandardDispatch, this parameter is the reference constant passed to the handler when the handler is called. If the value of the dispatcher parameter is kAEUseStandardDispatch, the Apple Event Manager ignores the handlerRefcon parameter and instead passes the reference constant stored in the Apple event dispatch table entry for the Apple event. (You may wish to pass the same reference constant that is stored in the Apple event dispatch table. If so, call the AEGetEventHandler function.)DESCRIPTIONWhen your application calls the AEResumeTheCurrentEvent function, the Apple Event Manager resumes handling the specified Apple event using the handler specified in the dispatcher parameter, if any. If kAENoDispatch is specified in the dispatcher parameter, AEResumeTheCurrentEvent simply informs the Apple Event Manager that the specified event has been handled.SPECIAL CONSIDERATIONSAn Apple event handler that suspends an event should not immediately call AEResumeTheCurrentEvent, or else the handler will generate an error. Instead, the handler should return just after suspending the event.When your application calls AEResumeTheCurrentEvent for an event that was not directly dispatched, the Apple Event Manager disposes of the event and the reply, just as it normally does, after the event handler returns to AEProcessAppleEvent. Make sure all processing involving the event or the reply has been completed before your application calls AEResumeTheCurrentEvent. Do not call AEResumeTheCurrentEvent for an event that was not suspended.When your application calls AEResumeTheCurrentEvent for an event that was directly dispatched, your application is responsible for disposing of the original event and the reply, since it is acts as both the server and the client.RESULT CODEnoErr    0    No error    AESetTheCurrentEventYou can use the AESetTheCurrentEvent function to specify the Apple event to be handled.FUNCTION AESetTheCurrentEvent (theAppleEvent: AppleEvent): OSErr;theAppleEventThe Apple event to be handled.DESCRIPTIONThere is usually no reason for your application to use the AESetTheCurrentEvent function. Instead of calling this function, your application should let the Apple Event Manager set the current Apple event through the dispatch tables.If you need to avoid the dispatch tables, you must use the AESetTheCurrentEvent function only in the following way:    1.    Your application suspends handling of an Apple event by calling the AESuspendTheCurrentEvent function.    2.    Your application calls the AESetTheCurrentEvent function. This informs the Apple Event Manager that your application is handling the suspended Apple event. In this way, any routines that call the AEGetTheCurrentEvent function can ascertain which event is currently being handled.    3.    When your application finishes handling the Apple event, it calls the AEResumeTheCurrentEvent function with the value kAENoDispatch to tell the Apple Event Manager that the event has been processed and need not be dispatched.RESULT CODEnoErr    0    No error    AEGetTheCurrentEventYou can use the AEGetTheCurrentEvent function to get the Apple event that is currently being handled. FUNCTION AEGetTheCurrentEvent                                 (VAR theAppleEvent: AppleEvent): OSErr;theAppleEventThe Apple event that is currently being handled; if no Apple event is currently being handled, AEGetTheCurrentEvent returns a null descriptor record in this parameter.DESCRIPTIONIn many applications, the handling of an Apple event involves one or more long chains of calls to internal routines. The AEGetTheCurrentEvent function makes it unnecessary for these calls to include the current Apple event as a parameter; the routines can simply call AEGetTheCurrentEvent to get the current Apple event when it is needed.You can also use the AEGetTheCurrentEvent function to make sure that no Apple event is currently being handled. For example, suppose your application always uses an application-defined routine to delete a file. That routine can first call AEGetTheCurrentEvent and delete the file only if AEGetTheCurrentEvent returns a null descriptor record (that is, only if no Apple event is currently being handled).RESULT CODEnoErr    0    No error    Getting the Sizes and Descriptor Types of Descriptor RecordsThe Apple Event Manager provides four routines that allow you to get the sizes and descriptor types of descriptor records that are not part of an Apple event record. The AESizeOfNthItem function returns the size and descriptor type of a descriptor record in a descriptor list.The AESizeOfKeyDesc function returns the size and descriptor type of a keyword-specified descriptor record in an AE record. You can get the size and descriptor type of an Apple event parameter or Apple event attribute using the AESizeOfParam and AESizeOfAttribute functions.AESizeOfNthItemYou can use the AESizeOfNthItem function to get the size and descriptor type of a descriptor record in a descriptor list. FUNCTION AESizeOfNthItem (theAEDescList: AEDescList;                                   index: LongInt; VAR typeCode: DescType;                                   VAR dataSize: Size): OSErr;theAEDescListThe descriptor list containing the descriptor record.index    The position of the descriptor record in the list (for example, 2 specifies the second descriptor record).typeCode     The descriptor type of the descriptor record.dataSize     The length (in bytes) of the data in the descriptor record.RESULT CODESnoErr    0    No error    errAEDescNotFound     –1701    Descriptor record was not found    errAEReplyNotArrived    –1718    Reply has not yet arrived     AESizeOfKeyDescYou can use the AESizeOfKeyDesc function to get the size and descriptor type of a keyword-specified descriptor record in an AE record. FUNCTION AESizeOfKeyDesc (theAERecord: AERecord;                                   theAEKeyword: AEKeyword;                                   VAR typeCode: DescType;                                   VAR dataSize: Size): OSErr;theAERecordThe AE record containing the desired keyword-specified descriptor record.theAEKeywordThe keyword that specifies the desired descriptor record.typeCode     The descriptor type of the keyword-specified descriptor record.dataSize     The length, in bytes of the data in the keyword-specified descriptor record.RESULT CODESnoErr    0    No error    errAEDescNotFound    –1701    Descriptor record was not found    errAENotAEDesc    –1704    Not a valid descriptor record    errAEReplyNotArrived    –1718    Reply has not yet arrived    AESizeOfParamYou can use the AESizeOfParam function to get the size and descriptor type of an Apple event parameter. FUNCTION AESizeOfParam (theAppleEvent: AppleEvent; theAEKeyword:                                 AEKeyword; VAR typeCode: DescType;                                 VAR dataSize: Size): OSErr;theAppleEventThe Apple event containing the parameter.theAEKeywordThe keyword that specifies the desired parameter.typeCode     The descriptor type of the Apple event parameter.dataSize     The length, in bytes, of the data in the Apple event parameter.RESULT CODESnoErr    0    No error    errAEDescNotFound    –1701    Descriptor record was not found    errAENotAEDesc    –1704    Not a valid descriptor record    errAEReplyNotArrived    –1718    Reply has not yet arrived    AESizeOfAttributeYou can use the AESizeOfAttribute function to get the size and descriptor type of an Apple event attribute.FUNCTION AESizeOfAttribute (theAppleEvent: AppleEvent;                                      theAEKeyword: AEKeyword;                                      VAR typeCode: DescType;                                      VAR dataSize: Size): OSErr;theAppleEventThe Apple event containing the desired attribute.theAEKeywordThe keyword that specifies the attribute.typeCode     The descriptor type of the attribute.dataSize     The length, in bytes, of the data in the attribute.RESULT CODESnoErr    0    No error    errAEDescNotFound    –1701    Descriptor record was not found    errAENotAEDesc    –1704    Not a valid descriptor record    errAEReplyNotArrived    –1718    Reply has not yet arrived       Deleting Descriptor RecordsThe Apple Event Manager provides three functions that allow you to delete descriptor records. The AEDeleteItem, AEDeleteKeyDesc, and AEDeleteParam functions allow you to delete descriptor records from a descriptor list, an AE record, and an Apple event parameter, respectively. AEDeleteItemYou can use the AEDeleteItem function to delete a descriptor record from a descriptor list. All subsequent descriptor records will then move up one place. FUNCTION AEDeleteItem (theAEDescList: AEDescList;                               index: LongInt): OSErr;theAEDescListThe descriptor list containing the descriptor record to be deleted.index    The position of the descriptor record to delete (for example, 2 specifies the second item).RESULT CODESnoErr    0    No error    errAEDescNotFound    –1701    Descriptor record was not found    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    AEDeleteKeyDescYou can use the AEDeleteKeyDesc function to delete a keyword-specified descriptor record from an AE record.FUNCTION AEDeleteKeyDesc (theAERecord: AERecord;                                   theAEKeyword: AEKeyword): OSErr;theAERecordThe AE record containing the keyword-specified descriptor record to be deleted.theAEKeywordThe keyword that specifies the descriptor record to be deleted.RESULT CODESnoErr    0    No error    errAEDescNotFound    –1701    Descriptor record was not found    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    AEDeleteParamYou can use the AEDeleteParam function to delete an Apple event parameter.FUNCTION AEDeleteParam (theAppleEvent: AppleEvent;                                 theAEKeyword: AEKeyword): OSErr;theAppleEventThe Apple event containing the parameter to be deleted.theAEKeywordThe keyword that specifies the parameter to be deleted.RESULT CODESnoErr    0    No error    errAEDescNotFound    –1701    Descriptor record was not found    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    Deallocating Memory for Descriptor RecordsThe AEDisposeDesc function deallocates the memory used by a descriptor record. Because all Apple event structures (except for keyword-specified descriptor records) are descriptor records, you can use AEDisposeDesc for any of them.AEDisposeDescYou can use the AEDisposeDesc function to deallocate the memory used by a descriptor record. FUNCTION AEDisposeDesc (VAR theAEDesc: AEDesc): OSErr;theAEDesc     The descriptor record to deallocate. The function returns a null descriptor record in this parameter. If you pass a null descriptor record in this parameter, AEDisposeDesc returns noErr.RESULT CODEnoErr    0    No error    SEE ALSOFor more information about using AEDisposeDesc, see “Disposing of Apple Event Data Structures,” which begins on page 4-39.Coercing Descriptor TypesThe Apple Event Manager provides two functions that allow you to coerce descriptor types. The AECoercePtr function takes a pointer to data and a desired descriptor type and attempts to coerce the data to a descriptor record of the desired descriptor type. The AECoerceDesc function attempts to coerce the data in an existing descriptor record to another descriptor type. AECoercePtrYou can use the AECoercePtr function to coerce data to a desired descriptor type. If successful, it creates a descriptor record containing the newly coerced data. FUNCTION AECoercePtr (typeCode: DescType; dataPtr: Ptr;                              dataSize: Size; toType: DescType;                              VAR result: AEDesc): OSErr;typeCode     The descriptor type of the source data.dataPtr     A pointer to the data to be coerced.dataSize     The length, in bytes, of the data to be coerced.toType    The desired descriptor type of the resulting descriptor record.result    The resulting descriptor record. DESCRIPTIONThe AECoercePtr function creates a new descriptor record by coercing the specified data to a descriptor record of the specified descriptor type. You should use the AEDisposeDesc function to dispose of the resulting descriptor record once you are finished using it.If AECoercePtr returns a nonzero result code, it returns a null descriptor record unless the Apple Event Manager is not available because of limited memory. RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAECoercionFail     –1700    Data could not be coerced to the requested descriptor type    SEE ALSOFor a description of the AEDisposeDesc function, see page 4-94.AECoerceDescYou can use the AECoerceDesc function to coerce the data in a descriptor record to another descriptor type. FUNCTION AECoerceDesc (theAEDesc: AEDesc; toType: DescType;                               VAR result: AEDesc): OSErr;theAEDesc    The descriptor record whose data is to be coerced.toType    The desired descriptor type of the resulting descriptor record.result    The resulting descriptor record.DESCRIPTIONThe AECoerceDesc function attempts to create a new descriptor record by coercing the specified descriptor record. Your application is responsible for using the AEDisposeDesc function to dispose of the resulting descriptor record once you are finished using it.If AECoerceDesc returns a nonzero result code, it returns a null descriptor record (a descriptor record of type typeNull, which does not contain any data) unless the Apple Event Manager is not available because of limited memory.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAECoercionFail    –1700    Data could not be coerced to requested descriptor type    SEE ALSOFor a list of the descriptor types for which the Apple Event Manager provides coercions, see Table 4-1, which begins on page 4-43.Creating and Managing the Coercion Handler Dispatch TablesThe Apple Event Manager provides three functions that allow you to create and manage the coercion handler dispatch tables. The AEInstallCoercionHandler function installs a coercion handler routine in either the application or system coercion dispatch table. The AEGetCoercionHandler function returns the handler for a specified descriptor type coercion. The AERemoveCoercionHandler function removes a coercion handler from either the application or system coercion table.AEInstallCoercionHandlerYou can use the AEInstallCoercionHandler function to install a coercion handler routine in either the application or system coercion handler dispatch table.FUNCTION AEInstallCoercionHandler (fromType: DescType;                                               toType: DescType;                                               handler: ProcPtr;                                               handlerRefcon: LongInt;                                               fromTypeIsDesc: Boolean;                                               isSysHandler: Boolean): OSErr;fromType     The descriptor type of the data coerced by the handler.toType     The descriptor type of the resulting data. If there was already an entry in the specified coercion handler table for the same source descriptor type and result descriptor type, the existing entry is replaced.handler     A pointer to the coercion handler. Note that a handler in the system coercion table must reside in the system heap; thus, if the value of the isSysHandler parameter is TRUE, the handler parameter should point to a location in the system heap. Otherwise, if you put your system handler code in your application heap, you should use AERemoveCoercionHandler to remove the handler when your application quits.handlerRefcon A reference constant passed by the Apple Event Manager to the handler each time the handler is called. If your handler doesn’t expect a reference constant, use 0 as the value of this parameter.fromTypeIsDesc Specifies the form of the data to be coerced. If the value of this parameter is TRUE, the coercion handler expects the data to be passed as a descriptor record. If the value is FALSE, the coercion handler expects a pointer to the data. Because it is more efficient for the Apple Event Manager to provide a pointer to data than to a descriptor record, all coercion routines should accept a pointer to data if possible.isSysHandler Specifies the coercion table to which the handler is added. If the value of this parameter is TRUE, the handler is added to the system coercion table and made available to all applications. If the value is FALSE, the handler is added to the application coercion table. Note that a handler in the system coercion table must reside in the system heap; thus, if the value of the isSysHandler parameter is TRUE, the handler parameter must point to a location in the system heap.DESCRIPTIONBefore using AEInstallCoercionHandler to install a handler for a particular descriptor type into the system coercion handler dispatch table, use the AEGetCoercionHandler function to determine whether the table already contains a coercion handler for that descriptor type. If an entry exists, AEGetCoercionHandler returns a reference constant and a pointer to that handler. Chain these to your coercion handler by providing, in the handlerRefcon parameter of AEInstallCoercionHandler, pointers to the previous handler and its reference constant. If your coercion handler returns the error errAECoercionFail, use these pointers to call the previous handler. If you remove your system coercion handler, be sure to reinstall the chained handlers.SPECIAL CONSIDERATIONSBefore an application calls a system coercion handler, system software has set up the A5 register for the calling application. For this reason, if you provide a system coercion handler, it should never use A5 global variables or anything that depends on a particular context; otherwise, the application that calls the system handler may crash.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    AEGetCoercionHandlerYou can use the AEGetCoercionHandler function to get the handler for a specified descriptor type coercion.FUNCTION AEGetCoercionHandler (fromType: DescType;                                          toType: DescType;                                          VAR handler: ProcPtr;                                          VAR handlerRefcon: LongInt;                                           VAR fromTypeIsDesc: Boolean;                                           isSysHandler: Boolean): OSErr;fromType    The descriptor type of the data coerced by the handler.toType     The descriptor type of the resulting data.handler     A pointer to the desired coercion handler.handlerRefcon The reference constant for the desired handler. The Apple Event Manager passes this reference constant to the handler each time the handler is called.fromTypeIsDesc If the AEGetCoercionHandler function returns TRUE in this parameter, the coercion handler expects the data to be passed as a descriptor record. If the function returns FALSE, the coercion handler expects a pointer to the data.isSysHandler Specifies the coercion table from which to get the handler. If the value of this parameter is TRUE, the handler is taken from the system coercion table. If the value is FALSE, the handler is taken from the application coercion table.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAEHandlerNotFound    –1717    No coercion handler found    AERemoveCoercionHandlerYou can use the AERemoveCoercionHandler function to remove a coercion handler from either the application or system coercion handler dispatch table.FUNCTION AERemoveCoercionHandler (fromType: DescType;                                              toType: DescType;                                              handler: ProcPtr;                                              isSysHandler: Boolean): OSErr;fromType     The descriptor type of the data coerced by the handler.toType     The descriptor type of the resulting data.handler    A pointer to the coercion handler. Although the fromType and toType parameters would be sufficient to identify the handler to be removed, providing the handler parameter is a safeguard to ensure that you remove the correct handler.isSysHandler The coercion table from which to remove the handler. If the value of this parameter is TRUE, the handler is removed from the system coercion table. If the value is FALSE, the handler is removed from the application coercion dispatch table.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAEHandlerNotFound    –1717    No coercion handler found    Creating and Managing the Special Handler Dispatch TablesThe Apple Event Manager provides three functions that allow you to create and manage the special handler dispatch tables. The AEInstallSpecialHandler function installs an entry for a special handler in either the application or system special handler dispatch table. The AEGetSpecialHandler function returns the handler for a specified special handler. The AERemoveSpecialHandler function removes a special handler from either the application or system special handler dispatch table. You can also use the AEInstallSpecialHandler, AEGetSpecialHandler, and AERemoveSpecialHandler functions to install, get, and remove object callback functions—including system object callback functions, which cannot be installed with the AESetObjectCallbacks function. When calling any of these three functions, use one of the following constants as the value of the functionClass parameter to specify the object callback function:Object callback function    Constant    Object-counting function    keyAECountProc    Object-comparison function    keyAECompareProc    Token disposal function    keyDiposeTokenProc    Error callback function    keyAEGetErrDescProc    Mark token function    keyAEMarkTokenProc    Object-marking function    keyAEMarkProc    Mark-adjusting function    keyAEAdjustMarksProc    You can also use the AERemoveSpecialHandler function to disable all the Apple Event Manager routines that support object specifier records. To do this, specify the constant keySelectProc in the functionClass parameter as described on page 4-102. AEInstallSpecialHandlerYou can use the AEInstallSpecialHandler function to install a special handler in either the application or system special handler dispatch table.FUNCTION AEInstallSpecialHandler (functionClass: AEKeyword;                                              handler: ProcPtr;                                              isSysHandler: Boolean): OSErr;functionClass The keyword for the special handler that is installed. The keyPreDispatch constant identifies a handler with the same parameters as an Apple event handler called immediately before the Apple Event Manager dispatches an Apple event. Any of the constants for object callback functions listed above can also be specified in this parameter. If there was already an entry in the specified special handler dispatch table for the same value of functionClass, it is replaced.handler     A pointer to the special handler. Note that a handler in the system special handler dispatch table must reside in the system heap; thus, if the value of the isSysHandler parameter is TRUE, the handler parameter should point to a location in the system heap. Otherwise, if you put your system handler code in your application heap, use AERemoveSpecialHandler to remove the handler when your application quits.isSysHandler The special handler dispatch table to which to add the handler. If the value of this parameter is TRUE, the handler is added to the system handler dispatch table and made available to all applications. If the value is FALSE, the handler is added to the application handler table.DESCRIPTIONThe AEInstallSpecialHandler function creates an entry in either your application’s special handler dispatch table or the system special handler dispatch table. You must supply parameters that specify the keyword for the special handler that is installed, the handler routine, and whether the handler is to be added to the system special handler dispatch table or your application’s special handler dispatch table.SPECIAL CONSIDERATIONSBefore an application calls a system special handler, system software has set up the A5 register for the calling application. For this reason, a system special handler should never use A5 global variables or anything that depends on a particular context; otherwise, the application that calls the system handler may crash.RESULT CODESnoErr    0    No error    paramErr    –50    Parameter error (handler pointer is NIL or odd)    memFullErr    –108    Not enough room in heap zone    errAENotASpecialFunction    –1714    Wrong keyword for a special function    AEGetSpecialHandlerYou can use the AEGetSpecialHandler function to get a specified special handler.FUNCTION AEGetSpecialHandler (functionClass: AEKeyword;                                         VAR handler: ProcPtr;                                         isSysHandler: Boolean): OSErr;functionClass The keyword for the special handler that is installed. The keyPreDispatch constant identifies a handler with the same parameters as an Apple event handler that is called immediately before the Apple Event Manager dispatches an Apple event. Any of the constants for object callback functions listed on page 4-100 can also be specified in this parameter. handler     A pointer to the special handler.isSysHandlerSpecifies the special handler dispatch table from which to get the handler. If the value of this parameter is TRUE, the handler is taken from the system special handler dispatch table. If the value is FALSE, the handler is taken from the application’s special handler dispatch table.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAENotASpecialFunction    –1714    Wrong keyword for a special handler    AERemoveSpecialHandlerYou can use the AERemoveSpecialHandler function to remove a handler from a special handler table.FUNCTION AERemoveSpecialHandler (functionClass: AEKeyword;                                             handler: ProcPtr;                                             isSysHandler: Boolean): OSErr;functionClass The keyword for the special handler to be removed. In addition to the constants for object callback functions listed on page 4-100, two other values are allowed for the functionClass parameter: keyPreDispatch and keySelectProc. The keyPreDispatch constant identifies a handler with the same parameters as an Apple event handler that is called immediately before the Apple Event Manager dispatches an Apple event. The keySelectProc constant indicates that you want to disable the Object Support Library—that is, all the routines described in the chapter “Resolving and Creating Object Specifier Records” in this book (see the description that follows for more information).handler     A pointer to the special handler to be removed. Although the functionClass parameter would be sufficient to identify the handler to be removed, providing the handler parameter is a safeguard that you remove the correct handler.isSysHandler Specifies the special handler dispatch table from which to remove the handler. If the value of this parameter is TRUE, the handler is taken from the system special handler dispatch table. If the value is FALSE, the handler is removed from the application special handler dispatch table.DESCRIPTIONIn addition to using the AERemoveSpecialHandler function to remove specific special handlers, you can use the function to disable, within your application only, all Apple Event Manager routines that support Apple event objects—that is, all the routines available to your application as a result of linking the Object Support Library (OSL) and calling the AEObjectInit function. An application that expects its copy of the OSL to move after it is installed—for example, an application that keeps it in a stand-alone code resource—would need to do this. When an application calls AEObjectInit to initialize the OSL, the OSL installs the addresses of its routines as extensions to the pack. If those routines move, the addresses become invalid.To disable the OSL, you should pass the keyword keySelectProc in the functionClass parameter, NIL in the handler parameter, and FALSE in the isSysHandler parameter. Once you have called the AERemoveSpecialHandler function with these parameters, subsequent calls by your application to any of the Apple Event Manager routines that support Apple event objects will return errors. To initialize the OSL after disabling it with the AERemoveSpecialHandler function, your application must call AEObjectInit again.If you expect to initialize the OSL and disable it several times, you should call AERemoveObjectAccessor to remove your application’s object accessor functions from your application’s object accessor dispatch table before you call AERemoveSpecialHandler. RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAENotASpecialFunction    –1714    Wrong keyword for a special function     Getting Information About the Apple Event ManagerThe AEManagerInfo routine allows you to get two kinds of information related to Apple events on the current computer: the number of processes currently recording Apple events and the version of the Apple Event Manager. If you decide to make your application recordable, this information may be useful when your application is responding to Apple events that it sends to itself.You can find out whether the Apple Event Manager is available in system software by using the Gestalt function. See page 4-4 for details.AEManagerInfoYou can use the AEManagerInfo function to obtain information about the version of the Apple Event Manager currently available or the number of processes that are currently recording Apple events. This function is available only in version 1.01 and later versions of the Apple Event Manager. FUNCTION AEManagerInfo (keyword: AEKeyword;                                 VAR result: LongInt): OSErr;keyword    A value that determines what kind of information AEManagerInfo returns. The value can be represented by one of these constants:    CONST keyAERecorderCount         = 'recr';                                       keyAEVersion                                   =     'vers'; result    If the value of the keyword parameter is keyAERecorderCount, this parameter is an integer that indicates the number of processes that are currently recording Apple events. If the value of the keyword parameter is keyAEVersion, this parameter is an integer that provides information about the version of the Apple Event Manager available on the current computer, using the same format as a 'vers' resource. RESULT CODEnoErr    0    No error    SEE ALSOFor information about using the AEManagerInfo function to check whether Apple event recording is on or not, see the chapter “Recording Apple Events” in this book.   For information about using Gestalt to determine whether the Apple Event Manager is available, see “Handling Apple Events” on page 4-4.For information about the 'vers' resource, see the chapter “Finder Interface” in Inside Macintosh: Macintosh Toolbox Essentials.Application-Defined RoutinesFor each Apple event your application supports, you must provide an Apple event handler. The AEProcessAppleEvent function calls one of your Apple event handlers when it processes an Apple event. An Apple event handler (MyEventHandler) should perform any action described by the Apple event, add parameters to the reply Apple event if appropriate, and return a result code.You can also provide your own coercion handlers to coerce data to descriptor types other than those for which the Apple Event Manager provides coercion handling. The MyCoercePtr function accepts a pointer to data and returns a descriptor record, and the MyCoerceDesc function accepts a descriptor record and returns a descriptor record.MyEventHandlerAn Apple event handler has the following syntax:FUNCTION MyEventHandler (theAppleEvent: AppleEvent;                                  reply: AppleEvent;                                  handlerRefcon: LongInt): OSErr;theAppleEventThe Apple event to handle.reply    The default reply Apple event provided by the Apple Event Manager.handlerRefconThe reference constant stored in the Apple event dispatch table for the Apple event.DESCRIPTIONAn Apple event handler should extract any parameters and attributes from the Apple event, perform the requested action, and add parameters to the reply Apple event if appropriate. Your handler should always set its function result to noErr if it successfully handles the Apple event. If an error occurs, your handler should return either errAEEventNotHandled or some other nonzero result code. If the error occurs because your application cannot understand the event, return errAEEventNotHandled, in case a handler in the system special handler or system Apple event dispatch tables might be able to handle the event. If the error occurs because the event is impossible to handle as specified, return the result code returned by whatever function caused the failure, or whatever other result code is appropriate.For example, suppose your application receives a Get Data event that requests the name of the current printer, and your application cannot handle such an event. In this situation, you should return errAEEventNotHandled in case another handler available to the Apple Event Manager can handle the event. This strategy allows users to take advantage of system capabilities from within your application via system handlers. However, if your application cannot handle a Get Data event that requests the fifth paragraph in a document because the document contains only four paragraphs, you should return some other nonzero error, because further attempts to handle the event are pointless.If your Apple event handler calls the AEResolve function and AEResolve calls an object accessor function in the system object accessor dispatch table, your Apple event handler may not recognize the descriptor type of the token returned by the function. In this case, your handler should return the result code errAEUnknownObjectType. When your handler returns this result code, the Apple Event Manager attempts to locate a system Apple event handler that can recognize the token. SEE ALSOFor more information about Apple event handlers, see “Writing Apple Event Handlers” on page 4-33.For a discussion of the dispatching of object accessor functions and the use of the result code errAEUnknownObjectType, see “Installing Entries in the Object Accessor Dispatch Tables,” which begins on page 6-21. MyCoercePtrA coercion handler that accepts a pointer to data has the following syntax:FUNCTION MyCoercePtr (typeCode: DescType; dataPtr: Ptr;                              dataSize: Size; toType: DescType;                              handlerRefcon: LongInt;                             VAR result: AEDesc): OSErr; typeCode    The descriptor type of the original data.dataPtr    A pointer to the data to coerce.dataSize    The length, in bytes, of the data to coerce.toType    The desired descriptor type for the resulting descriptor record.handlerRefconA reference constant that is stored in the coercion dispatch table entry for the handler and passed to the handler by the Apple Event Manager whenever the handler is called.result    The resulting descriptor record.DESCRIPTIONYour coercion handler should coerce the data to the desired descriptor type and return the resulting data in the descriptor record specified by the result parameter. Your handler should return the noErr result code if your handler successfully performs the coercion, and a nonzero result code otherwise.SEE ALSOFor more information, see “Writing and Installing Coercion Handlers” on page 4-41.MyCoerceDescA coercion handler that accepts a descriptor record has the following syntax:FUNCTION MyCoerceDesc (theAEDesc: AEDesc; toType: DescType;                                handlerRefcon: LongInt;                                 VAR result: AEDesc): OSErr;theAEDesc    The descriptor record that contains the data to be coerced.toType    The desired descriptor type for the resulting descriptor record.handlerRefconA reference constant that is stored in the coercion dispatch table entry for the handler and passed to the handler by the Apple Event Manager whenever the handler is called.result    The resulting descriptor record.DESCRIPTIONYour coercion handler should coerce the data in the descriptor record to the desired descriptor type and return the resulting data in the descriptor record specified by the result parameter. Your handler should return an appropriate result code.SEE ALSOFor more information, see “Writing and Installing Coercion Handlers” on page 4-41.Summary of Responding to Apple EventsPascal SummaryConstantsCONST            gestaltAppleEventsAttr                                    = 'evnt';                {selector for Apple events}    gestaltAppleEventsPresent                                    = 0;                {if this bit is set, then Apple }                                                        { Event Manager is available}    {Apple event descriptor types}    typeBoolean                                = 'bool';                    {1-byte Boolean value}    typeChar                                = 'TEXT';                    {unterminated string}    typeSMInt                                = 'shor';                    {16-bit integer}    typeInteger                                = 'long';                    {32-bit integer}    typeSMFloat                                = 'sing';                    {SANE single}    typeFloat                                = 'doub';                    {SANE double}    typeLongInteger                                = 'long';                    {32-bit integer}    typeShortInteger                                = 'shor';                    {16-bit integer}    typeLongFloat                                = 'doub';                    {SANE double}    typeShortFloat                                = 'sing';                    {SANE single}    typeExtended                                = 'exte';                    {SANE extended}    typeComp                                = 'comp';                    {SANE comp}    typeMagnitude                                = 'magn';                    {unsigned 32-bit integer}    typeAEList                                = 'list';                    {list of descriptor records}    typeAERecord                                = 'reco';                    {list of keyword-specified }                                                        { descriptor records}    typeAppleEvent                                = 'aevt';                    {Apple event record}    typeTrue                                = 'true';                    {TRUE Boolean value}    typeFalse                                = 'fals';                    {FALSE Boolean value}    typeAlias                                = 'alis';                    {alias record}    typeEnumerated                                = 'enum';                    {enumerated data}    typeType                                = 'type';                    {four-character code for }                                                        { event class or event ID}    typeAppParameters                                = 'appa';                    {Process Manager launch parameters}    typeProperty                                = 'prop';                    {Apple event property}    typeFSS                                = 'fss ';                    {file system specification}    typeKeyword                                = 'keyw';                    {Apple event keyword}    typeSectionH                                = 'sect';                    {handle to a section record}    typeWildCard                                = '****';                    {matches any type}    typeApplSignature                                = 'sign';                    {application signature}    typeSessionID                                = 'ssid';                    {session reference number}    typeTargetID                                = 'targ';                    {target ID record}    typeProcessSerialNumber                                = 'psn ';                    {process serial number}    typeNull                                = 'null';                    {NULL or nonexistent data}        {keywords for Apple event parameters}    keyDirectObject                                = '----';                    {direct parameter}    keyErrorNumber                                = 'errn';                    {error number parameter}    keyErrorString                                = 'errs';                    {error string parameter}    keyProcessSerialNumber                                = 'psn ';                    {process serial number param}    {keywords for Apple event attributes}    keyTransactionIDAttr                                = 'tran';                    {transaction ID}    keyReturnIDAttr                                = 'rtid';                    {return ID}    keyEventClassAttr                                 = 'evcl';                    {event class}    keyEventIDAttr                                = 'evid';                    {event ID}    keyAddressAttr                                = 'addr';                    {address of target or }                                                        { client application}    keyOptionalKeywordAttr                                = 'optk';                    {list of optional parameters }                                                        { for the Apple event}    keyTimeoutAttr                                = 'timo';                    {number of ticks the client }                                                        { will wait}    keyInteractLevelAttr                                 = 'inte';                    {settings to allow Apple Event }                                                        { Manager to bring server }                                                                            { to foreground}    keyEventSourceAttr                                = 'esrc';                    {nature of source }                                                        { application}    keyMissedKeywordAttr                                = 'miss';                    {first required parameter }                                                        { remaining in an Apple event}    keyOriginalAddressAttr                                = 'from';                    {address of original source; }                                                        { available only in version }                                                         { 1.01 and later versions of }                                                        { the Apple Event Manager}    {keywords for special handlers}    keyPreDispatch                                = 'phac';                    {identifies a handler routine }                                                        { called immediately before the }                                                        { Apple Event Manager dispatches }                                                        { an Apple event}    keySelectProc                                = 'selh';                     {selector used with }                                                        { AERemoveSpecialHandler to }                                                        { disable the OSL}    {keywords for use with AEManagerInfo; available only in version }    { 1.0.1 and later versions of the Apple Event Manager}    keyAERecorderCount                                 = 'recr';                    {keyword for recording info}    keyAEVersion                                 = 'vers';                    {keyword for version info}    {event class}    kCoreEventClass                                = 'aevt';                    {event class for required Apple }                                                        { events}    {event IDs for required Apple events}    kAEOpenApplication                                = 'oapp';                    {event ID for Open }                                                        { Application event}    kAEOpenDocuments                                = 'odoc';                    {event ID for Open Documents event}    kAEPrintDocuments                                = 'pdoc';                    {event ID for Print Documents }                                                        { event}    kAEQuitApplication                                = 'quit';                    {event ID for Quit Application }                                                        { event}    kAEAnswer                                = 'ansr';                    {event ID for Apple event replies}    kAEApplicationDied                                = 'obit';                    {event ID for Application Died }                                                        { event}    {constants for setting the sendMode parameter of AESend}    kAENoReply                                = $00000001;                    {client doesn't want reply}    kAEQueueReply                                = $00000002;                    {client wants server to }                                                        { reply in event queue}    kAEWaitReply                                = $00000003;                    {client wants a reply and }                                                        { will give up processor}    kAENeverInteract                                = $00000010;                    {server application should }                                                        { not interact with user }                                                        { for this Apple event}    kAECanInteract                                = $00000020;                    {server may interact with }                                                        { user for this Apple event }                                                        { to supply information}    kAEAlwaysInteract                                = $00000030;                    {server may interact with user }                                                        { for this Apple event even if }                                                        { no information is required}    kAECanSwitchLayer                                = $00000040;                    {server should come directly }                                                        { to foreground when appropriate}    kAEDontReconnect                                = $00000080;                    {don't reconnect if there }                                                        { is a PPC session closed error}    kAEWantReceipt                                = nReturnReceipt; {client wants return }                                                        { receipt}    kAEDontRecord                                = $00001000            ;        {don't record this event}    kAEDontExecute                                = $00002000;                    {don't excecute this event}    {constants for setting the sendPriority parameter of AESend}    kAENormalPriority                                = $00000000;                    {put event at the back of }                                                        { event queue}    kAEHighPriority                                = nAttnMsg;                    {put event at the front of }                                                        { the event queue}    {event IDs for recording events; available only in version 1.01 and }    { later versions of the Apple Event Manager}    kAEStartRecording                                = 'reca';                    {event ID for Start Recording }                                                        { event}    kAEStopRecording                                = 'recc';                    {event ID for Stop Recording }                                                        { event}    kAENotifyStartRecording                                = 'rec1';                    {event ID for Recording On event}    kAENotifyStopRecording                                = 'rec0';                    {event ID for Recording Off event}    kAENotifyRecording                                = 'recr';                    {event ID for Receive Recordable }                                                        { Event event}    {constant for the returnID parameter of AECreateAppleEvent}    kAutoGenerateReturnID                                = -1;                    {tells Apple Event Manager to }                                                        { generate a unique return ID}    {constant for transaction IDs}    kAnyTransactionID                                 = 0;                    {the Apple event is not }                                                        { part of a transaction}    {constants for timeout durations}    kAEDefaultTimeout                                = -1;                    {use default timeout value}    kNoTimeOut                                = -2;                    {never time out}    {constants for the dispatcher parameter of AEResumeTheCurrentEvent}    kAENoDispatch                                = 0;                    {don't redispatch the Apple event}    kAEUseStandardDispatch                                = -1;                    {redispatch the Apple event }                                                        { by using its entry in the }                                                        { Apple event dispatch table}Data TypesTYPE    AEEventClass =         PACKED ARRAY[1..4] OF Char;                                                    {event class for a high-level }                                                            { event}    AEEventID =         PACKED ARRAY[1..4] OF Char;                                                    {event ID for a high-level }                                                            { event}    AEKeyword =         PACKED ARRAY[1..4] OF Char;                                                    {keyword for a descriptor }                                                            { record}    DescType                                    = ResType;                    {descriptor type}    AEDesc =                                                         {descriptor record}    RECORD                descriptorType:                                 DescType;                    {type of data being passed}        dataHandle:                                 Handle;                    {handle to data being passed}    END;    AEKeyDesc =                                                         {keyword-specified }    RECORD                                                        { descriptor record}        descKey:                                AEKeyword;                    {keyword}        descContent:                                AEDesc    ;                {descriptor record}    END;    AEAddressDesc                                    = AEDesc;                    {address descriptor record}    AEDescList                                    = AEDesc;                    {list of descriptor records}    AERecord                                    = AEDescList;                    {list of keyword-specified }                                                            { descriptor records}    AppleEvent                                    = AERecord;                    {list of attributes and }                                                            { parameters necessary for }                                                            { an Apple event}    AESendMode                                    = LongInt;                    {flags that determine how }                                                            { an Apple event is sent}    AESendPriority                                    = Integer;                    {send priority of an Apple }                                                            { event}    AEInteractAllowed = (kAEInteractWithSelf, kAEInteractWithLocal,                                                   kAEInteractWithAll);                            {what processes may }                                                            { interact with the user}    AEEventSource = (kAEUnknownSource, kAEDirectCall, kAESameProcess,                                           kAELocalProcess, kAERemoteProcess);                                                            {the source of an Apple }                                                            { event}    AEArrayType = (kAEDataArray, kAEPackedArray, kAEHandleArray,                                     kAEDescArray, kAEKeyDescArray);                                                            {type of an Apple event array}    AEArrayData =     RECORD                                                        {data for an Apple event array}        CASE AEArrayType OF        kAEDataArray:            (AEDataArray:     ARRAY[0..0] OF Integer);        kAEPackedArray:            (AEPackedArray:     PACKED ARRAY[0..0] OF Char);        kAEHandleArray:            (AEHandleArray:     ARRAY[0..0] OF Handle);        kAEDescArray:            (AEDescArray:     ARRAY[0..0] OF AEDesc);        kAEKeyDescArray:            (AEKeyDescArray:     ARRAY[0..0] OF AEKeyDesc);    END;        AEArrayDataPointer = ^AEArrayData;    EventHandlerProcPtr = ProcPtr;                                                        {pointer to an Apple event }                                                            { handler}    IdleProcPtr = ProcPtr;                                                        {pointer to an application's }                                                            { idle function}    EventFilterProcPtr = ProcPtr;                                                        {pointer to an application's }                                                            { filter function}Routines for Responding to Apple EventsCreating and Managing the Apple Event Dispatch TablesFUNCTION AEInstallEventHandler(theAEEventClass: AEEventClass; theAEEventID: AEEventID; handler: EventHandlerProcPtr; handlerRefcon: LongInt; isSysHandler: Boolean): OSErr;FUNCTION AEGetEventHandler    (theAEEventClass: AEEventClass; theAEEventID: AEEventID; VAR handler: EventHandlerProcPtr; VAR handlerRefcon: LongInt; isSysHandler: Boolean): OSErr;FUNCTION AERemoveEventHandler(theAEEventClass: AEEventClass; theAEEventID: AEEventID; handler: EventHandlerProcPtr; isSysHandler: Boolean): OSErr;Dispatching Apple EventsFUNCTION AEProcessAppleEvent(theEventRecord: EventRecord): OSErr;Getting Data or Descriptor Records Out of Apple Event Parameters and AttributesFUNCTION AEGetParamPtr    (theAppleEvent: AppleEvent; theAEKeyword: AEKeyword; desiredType: DescType; VAR typeCode: DescType; dataPtr: Ptr; maximumSize: Size; VAR actualSize: Size): OSErr;FUNCTION AEGetParamDesc    (theAppleEvent: AppleEvent; theAEKeyword: AEKeyword; desiredType: DescType; VAR result: AEDesc): OSErr;FUNCTION AEGetAttributePtr    (theAppleEvent: AppleEvent; theAEKeyword: AEKeyword; desiredType: DescType; VAR typeCode: DescType; dataPtr: Ptr; maximumSize: Size; VAR actualSize: Size): OSErr;FUNCTION AEGetAttributeDesc    (theAppleEvent: AppleEvent; theAEKeyword: AEKeyword; desiredType: DescType; VAR result: AEDesc): OSErr;Counting the Items in Descriptor ListsFUNCTION AECountItems    (theAEDescList: AEDescList; VAR theCount: LongInt): OSErr;Getting Items From Descriptor ListsFUNCTION AEGetNthPtr    (theAEDescList: AEDescList; index: LongInt; desiredType: DescType; VAR theAEKeyword: AEKeyword; VAR typeCode: DescType; dataPtr: Ptr; maximumSize: Size; VAR actualSize: Size): OSErr;FUNCTION AEGetNthDesc    (theAEDescList: AEDescList; index: LongInt; desiredType: DescType; VAR theAEKeyword: AEKeyword; VAR result: AEDesc): OSErr;FUNCTION AEGetArray    (theAEDescList: AEDescList; arrayType: AEArrayType; arrayPtr: AEArrayDataPointer; maximumSize: Size; VAR itemType: DescType; VAR itemSize: Size; VAR itemCount: LongInt): OSErr;Getting Data and Keyword-Specified Descriptor Records Out of AE RecordsFUNCTION AEGetKeyPtr    (theAERecord: AERecord; theAEKeyword: AEKeyword; desiredType: DescType; VAR typeCode: DescType; dataPtr: Ptr; maximumSize: Size; VAR actualSize: Size): OSErr;FUNCTION AEGetKeyDesc    (theAERecord: AERecord; theAEKeyword: AEKeyword; desiredType: DescType; VAR result: AEDesc): OSErr;Requesting User InteractionFUNCTION AESetInteractionAllowed(level: AEInteractAllowed): OSErr;FUNCTION AEGetInteractionAllowed(VAR level: AEInteractAllowed): OSErr;FUNCTION AEInteractWithUser    (timeOutInTicks: LongInt; nmReqPtr: NMRecPtr; idleProc: IdleProcPtr): OSErr;Requesting More Time to Respond to Apple EventsFUNCTION AEResetTimer    (reply: AppleEvent): OSErr;Suspending and Resuming Apple Event HandlingFUNCTION AESuspendTheCurrentEvent    (theAppleEvent: AppleEvent): OSErr;FUNCTION AEResumeTheCurrentEvent(theAppleEvent, reply: AppleEvent;             dispatcher: EventHandlerProcPtr; handlerRefcon: LongInt): OSErr;FUNCTION AESetTheCurrentEvent(theAppleEvent: AppleEvent): OSErr;FUNCTION AEGetTheCurrentEvent(VAR theAppleEvent: AppleEvent): OSErr;Getting the Sizes and Descriptor Types of Descriptor RecordsFUNCTION AESizeOfNthItem    (theAEDescList: AEDescList; index: LongInt; VAR typeCode: DescType; VAR dataSize: Size): OSErr;FUNCTION AESizeOfKeyDesc    (theAERecord: AERecord; theAEKeyword: AEKeyword; VAR typeCode: DescType; VAR dataSize: Size): OSErr;FUNCTION AESizeOfParam    (theAppleEvent: AppleEvent; theAEKeyword: AEKeyword; VAR typeCode: DescType; VAR dataSize: Size): OSErr;FUNCTION AESizeOfAttribute    (theAppleEvent: AppleEvent; theAEKeyword: AEKeyword; VAR typeCode: DescType; VAR dataSize: Size): OSErr;Deleting Descriptor RecordsFUNCTION AEDeleteItem    (theAEDescList: AEDescList; index: LongInt): OSErr;FUNCTION AEDeleteKeyDesc    (theAERecord: AERecord; theAEKeyword: AEKeyword): OSErr;FUNCTION AEDeleteParam    (theAppleEvent: AppleEvent; theAEKeyword: AEKeyword): OSErr;Deallocating Memory for Descriptor RecordsFUNCTION AEDisposeDesc    (VAR theAEDesc: AEDesc): OSErr;Coercing Descriptor TypesFUNCTION AECoercePtr    (typeCode: DescType; dataPtr: Ptr; dataSize: Size; toType: DescType; VAR result: AEDesc): OSErr;FUNCTION AECoerceDesc    (theAEDesc: AEDesc; toType: DescType; VAR result: AEDesc): OSErr;Creating and Managing the Coercion Handler Dispatch TablesFUNCTION AEInstallCoercionHandler(fromType: DescType; toType: DescType; handler: ProcPtr; handlerRefcon: LongInt; fromTypeIsDesc: Boolean; isSysHandler: Boolean): OSErr;FUNCTION AEGetCoercionHandler(fromType: DescType; toType: DescType; VAR handler: ProcPtr; VAR handlerRefcon: LongInt; VAR fromTypeIsDesc: Boolean; isSysHandler: Boolean): OSErr;FUNCTION AERemoveCoercionHandler(fromType: DescType; toType: DescType; handler: ProcPtr; isSysHandler: Boolean): OSErr;Creating and Managing the Special Handler Dispatch TablesFUNCTION AEInstallSpecialHandler(functionClass: AEKeyword; handler: ProcPtr; isSysHandler: Boolean): OSErr;FUNCTION AEGetSpecialHandler(functionClass: AEKeyword; VAR handler: ProcPtr; isSysHandler: Boolean): OSErr;FUNCTION AERemoveSpecialHandler(functionClass: AEKeyword; handler: ProcPtr; isSysHandler: Boolean): OSErr;Getting Information About the Apple Event Manager{available only in version 1.01 and later versions of Apple Event Manager}FUNCTION AEManagerInfo     (keyword: AEKeyword; VAR result: LongInt): OSErr;Application-Defined RoutinesFUNCTION MyEventHandler    (theAppleEvent: AppleEvent; reply: AppleEvent; handlerRefcon: LongInt): OSErr; FUNCTION MyCoercePtr    (typeCode: DescType; dataPtr: Ptr; dataSize: Size; toType: DescType; handlerRefcon: LongInt; VAR result: AEDesc): OSErr; FUNCTION MyCoerceDesc    (theAEDesc: AEDesc; toType: DescType; handlerRefcon: LongInt; VAR result: AEDesc): OSErr;C SummaryConstantsenum {        #define gestaltAppleEventsAttr                                      'evnt'                /*selector for Apple events*/        gestaltAppleEventsPresent                                             = 0         /*if this bit is set, then */                                                            /* Apple Event Manager is */};                                                            /* available*/        /*Apple event descriptor types*/enum        {        typeBoolean                                = 'bool',                    /*1-byte Boolean value*/        typeChar                                = 'TEXT',                    /*unterminated string*/        typeSMInt                                = 'shor',                    /*16-bit integer*/        typeInteger                                = 'long',                    /*32-bit integer*/        typeSMFloat                                = 'sing',                    /*SANE single*/        typeFloat                                = 'doub',                    /*SANE double*/        typeLongInteger                                = 'long',                    /*32-bit integer*/        typeShortInteger                                = 'shor',                    /*16-bit integer*/        typeLongFloat                                = 'doub',                    /*SANE double*/        typeShortFloat                                = 'sing',                    /*SANE single*/        typeExtended                                = 'exte',                    /*SANE extended*/        typeComp                                = 'comp',                    /*SANE comp*/        typeMagnitude                                = 'magn',                    /*unsigned 32-bit integer*/        typeAEList                                = 'list',                    /*list of descriptor records*/        typeAERecord                                = 'reco',                    /*list of keyword-specified */                                                            /* descriptor records*/        typeAppleEvent                                = 'aevt',                    /*Apple event record*/        typeTrue                                = 'true',                    /*TRUE Boolean value*/        typeFalse                                = 'fals',                    /*FALSE Boolean value*/        typeAlias                                = 'alis',                    /*alias record*/        typeEnumerated                                = 'enum'                    /*enumerated data*/};enum {        typeType                                = 'type',                    /*four-character code for */                                                            /* event class or event ID*/        typeAppParameters                                = 'appa',                    /*Process Manager launch */                                                            /* parameters*/        typeProperty                                = 'prop',                    /*Apple event property*/        typeFSS                                = 'fss ',                    /*file system specification*/        typeKeyword                                = 'keyw',                    /*Apple event keyword*/        typeSectionH                                = 'sect',                    /*handle to a section record*/        typeWildCard                                = '****',                    /*matches any type*/        typeApplSignature                                = 'sign',                    /*application signature*/        typeSessionID                                = 'ssid',                    /*session ID*/        typeTargetID                                = 'targ',                    /*target ID record*/        typeProcessSerialNumber                                = 'psn ',                    /*process serial number*/        typeNull                                = 'null'                    /*NULL or nonexistent data*/};        /*keywords for Apple event parameters*/enum     {        keyDirectObject                                = '----',                    /*direct parameter*/        keyErrorNumber                                = 'errn',                    /*error number parameter*/        keyErrorString                                = 'errs',                    /*error string parameter*/        keyProcessSerialNumber                                = 'psn '                    /*process serial number param*/};        /*keywords for Apple event attributes*/enum     {        keyTransactionIDAttr                                = 'tran',                    /*transaction ID*/        keyReturnIDAttr                                = 'rtid',                    /*return ID*/        keyEventClassAttr                                 = 'evcl',                    /*event class*/        keyEventIDAttr                                = 'evid',                    /*event ID*/        keyAddressAttr                                = 'addr',                    /*address of target or */                                                            /* client application*/        keyOptionalKeywordAttr                                = 'optk',                    /*list of optional parameters */                                                            /* for the Apple event*/        keyTimeoutAttr                                = 'timo',                    /*number of ticks the client */                                                            /* will wait*/        keyInteractLevelAttr                                 = 'inte',                    /*settings to allow Apple */                                                            /* Event Mgr to bring */                                                                                /* server to foreground*/        keyEventSourceAttr                                = 'esrc',                    /*nature of source */                                                            /* application*/        keyMissedKeywordAttr                                = 'miss',                    /*first required parameter */                                                            /* remaining in an Apple */                                                            /* event*/        keyOriginalAddressAttr                                = 'from'                    /*address of original source; */                                                            /* available only in version */                                                             /* 1.01 and later versions of */                                                            /* the Apple Event Manager*/};                /*keywords for special handlers*/enum     {        keyPreDispatch                                = 'phac',                    /*identifies a handler */                                                            /* routine that is called */                                                            /* immediately before the */                                                            /* Apple Event Manager */                                                            /* dispatches an Apple event*/        keySelectProc                                = 'selh',                     /*selector used with */                                                            /* AERemoveSpecialHandler to */                                                            /* disable the OSL*/        /*keywords for use with AEManagerInfo, available only in version */        /* 1.0.1 and later versions of the Apple Event Manager*/        keyAERecorderCount                                 = 'recr',                    /*keyword for recording info*/        keyAEVersion                                 = 'vers',                    /*keyword for version info*/        /*event class*/        kCoreEventClass                                = 'aevt'                    /*event class for required */                                                            /* Apple events*/};        /*event IDs for required Apple events*/enum {        kAEOpenApplication                                = 'oapp',                    /*event ID for Open */                                                            /* Application event*/        kAEOpenDocuments                                = 'odoc',                    /*event ID for Open */                                                            /* Documents event*/        kAEPrintDocuments                                = 'pdoc',                    /*event ID for Print */                                                            /* Documents event*/        kAEQuitApplication                                = 'quit',                    /*event ID for Quit */                                                            /* Application event*/        kAEAnswer                                = 'ansr',                    /*event ID for Apple event */                                                            /* replies*/        kAEApplicationDied                                = 'obit'                    /*event ID for Application */                                                            /* Died event*/};        /*constants for setting the sendMode parameter of AESend*/enum {        kAENoReply                                = 0x00000001,                    /*client doesn't want reply*/        kAEQueueReply                                = 0x00000002,                    /*client wants server to */                                                            /* reply in event queue*/        kAEWaitReply                                = 0x00000003,                    /*client wants a reply and */                                                            /* will give up processor*/        kAENeverInteract                                = 0x00000010,                    /*server application should */                                                            /* not interact with user */                                                            /* for this Apple event*/        kAECanInteract                                = 0x00000020,                    /*server may interact with */                                                            /* user for this Apple event */                                                            /* to supply information*/        kAEAlwaysInteract                                = 0x00000030,                    /*server may interact with */                                                            /* user for this Apple event */                                                            /* even if no information */                                                            /* is required*/        kAECanSwitchLayer                                = 0x00000040,                    /*server should come */                                                            /* directly to foreground */                                                            /* when appropriate*/        kAEDontReconnect                                = 0x00000080,                    /*don't reconnect if there */                                                            /* is a PPC session closed */                                                            /* error*/        kAEWantReceipt                                = nReturnReceipt, /*client wants return */                                                            /* receipt*/        kAEDontRecord                                = 0x00001000,                    /*don't record this event*/        kAEDontExecute                                = 0x00002000,                    /*don't excecute this event*/        /*constants for setting the sendPriority parameter of AESend*/        kAENormalPriority                                = 0x00000000,                    /*post message at end of */                                                            /* event queue*/        kAEHighPriority                                = nAttnMsg                    /*post message at front of */                                                            /* event queue*/};        /*event IDs for recording events; available only in version 1.01 and */        /* later versions of the Apple Event Manager*/enum {        kAEStartRecording                                = 'reca'        ,            /*event ID for Start */                                                            /* Recording event*/        kAEStopRecording                                = 'recc',                    /*event ID for Stop */                                                            /* Recording event*/        kAENotifyStartRecording                                = 'rec1',                    /*event ID for Recording On*/                                                            /* event*/        kAENotifyStopRecording                                = 'rec0',                    /*event ID for Recording Off */                                                            /* event*/        kAENotifyRecording                                = 'recr'                    /*event ID for Receive */                                                            /* Recordable Event event*/};enum {        /*constant for the returnID parameter of AECreateAppleEvent*/        kAutoGenerateReturnID                                = -1,                    /*tells Apple Event Manager */                                                            /* to generate a unique */                                                            /* return ID*/        /*constant for transaction IDs*/        kAnyTransactionID                                 = 0,                    /*the Apple event is not */                                                            /* part of a transaction*/        /*constants for timeout durations*/        kAEDefaultTimeout                                = -1,                    /*use default timeout value*/        kNoTimeOut                                = -2    ,                /*never time out*/        /*constants for the dispatcher parameter of AEResumeTheCurrentEvent*/        kAENoDispatch                                = 0,                    /*don't redispatch the */                                                            /* Apple event*/        kAEUseStandardDispatch                                = -1                /*redispatch the Apple event */                                                            /* by using its entry in the */                                                            /* Apple event dispatch table*/};Data Typestypedef unsigned long AEEventClass;                                                            /*event class for a */                                                            /* high-level event*/typedef unsigned long AEEventID;                                                            /*event ID for a high-level */                                                            /* event*/typedef unsigned long AEKeyword;                                                            /*keyword for a descriptor */                                                            /* record*/typedef ResType DescType                                ;                            /*descriptor type*/struct AEDesc {                                                             /*descriptor record*/    DescType descriptorType;                                                         /*type of data being passed*/    Handle dataHandle;                                                        /*handle to data being passed*/};typedef struct AEDesc AEDesc;struct AEKeyDesc {                                                             /*keyword-specified */                                                            /* descriptor record*/    AEKeyword descKey;                                                        /*keyword*/    AEDesc descContent;                                                        /*descriptor record*/};typedef struct AEKeyDesc AEKeyDesc;typedef AEDesc AEAddressDesc;                                                            /*address descriptor record*/typedef AEDesc AEDescList;                                                            /*list of descriptor records*/typedef AEDescList AERecord;                                                            /*list of keyword-specified */                                                            /* descriptor records*/typedef AERecord AppleEvent;                                                            /*list of attributes and */                                                            /* parameters necessary for */                                                            /* an Apple event*/typedef long AESendMode;                                                            /*flags that determine how */                                                            /* an Apple event is sent*/typedef short AESendPriority;                                                            /*send priority of an Apple */                                                            /* event*/enum { kAEInteractWithSelf, kAEInteractWithLocal,         kAEInteractWithAll };                                                    /*what processes may */typedef unsigned char AEInteractAllowed;                                                            /* interact with the user*/enum { kAEUnknownSource, kAEDirectCall, kAESameProcess,             kAELocalProcess,          kAERemoteProcess };                                                    /*the source of an Apple */typedef unsigned char AEEventSource;                                                            /* event*/enum { kAEDataArray, kAEPackedArray, kAEHandleArray,        kAEDescArray, kAEKeyDescArray };                                                            /*type of an Apple event */typedef unsigned char AEArrayType;                                                            /* array*/union AEArrayData {                                                                 /*data for an Apple event */    short                kAEDataArray[1];                                            /* array*/    char                kAEPackedArray[1];    Handle                 kAEHandleArray[1];    AEDesc                 kAEDescArray[1];                            AEKeyDesc                kAEKeyDescArray[1];};typedef union AEArrayData AEArrayData;typedef AEArrayData *AEArrayDataPointer;typedef ProcPtr EventHandlerProcPtr;                                                            /*pointer to an Apple event */                                                            /* handler*/typedef ProcPtr IdleProcPtr;                                                            /*pointer to an application's */                                                            /* idle function*/typedef ProcPtr EventFilterProcPtr;                                                            /*pointer to an application's */                                                            /* filter function*/Routines for Responding to Apple EventsCreating and Managing the Apple Event Dispatch Tablespascal OSErr AEInstallEventHandler(AEEventClass theAEEventClass, AEEventID theAEEventID,EventHandlerProcPtr handler,long handlerRefcon, Boolean isSysHandler);pascal OSErr AEGetEventHandler(AEEventClass theAEEventClass,AEEventID theAEEventID,EventHandlerProcPtr *handler, long *handlerRefcon, Boolean isSysHandler);pascal OSErr AERemoveEventHandler(AEEventClass theAEEventClass,AEEventID theAEEventID,EventHandlerProcPtr handler, Boolean isSysHandler);Dispatching Apple Eventspascal  OSErr  AEProcessAppleEvent         (const EventRecord *theEventRecord);Getting Data or Descriptor Records Out of Apple Event Parameters and Attributespascal OSErr AEGetParamPtr    (const AppleEvent *theAppleEvent, AEKeyword theAEKeyword, DescType desiredType, DescType *typeCode, void* dataPtr, Size maximumSize, Size *actualSize);pascal OSErr AEGetParamDesc    (const AppleEvent *theAppleEvent, AEKeyword theAEKeyword, DescType desiredType, AEDesc *result);pascal OSErr AEGetAttributePtr(const AppleEvent *theAppleEvent, AEKeyword theAEKeyword, DescType desiredType, DescType *typeCode, void* dataPtr,Size maximumSize, Size *actualSize); pascal OSErr AEGetAttributeDesc(const AppleEvent *theAppleEvent, AEKeyword theAEKeyword, DescType desiredType, AEDesc *result);Counting the Items in Descriptor Listspascal OSErr AECountItems    (const AEDescList *theAEDescList, long *theCount);Getting Items From Descriptor Listspascal OSErr AEGetNthPtr    (const AEDescList *theAEDescList, long index, DescType desiredType, AEKeyword *theAEKeyword, DescType *typeCode, void* dataPtr,Size maximumSize, Size *actualSize);pascal OSErr AEGetNthDesc    (const AEDescList *theAEDescList, long index, DescType desiredType, AEKeyword *theAEKeyword, AEDesc *result);pascal OSErr AEGetArray    (const AEDescList *theAEDescList, AEArrayType arrayType, AEArrayDataPointer arrayPtr, Size maximumSize, DescType *itemType, Size *itemSize, long *itemCount);Getting Data and Keyword-Specified Descriptor Records Out of AE Recordspascal OSErr AEGetKeyPtr    (const AERecord *theAERecord, AEKeyword theAEKeyword, DescType desiredType, DescType *typeCode, void* dataPtr, Size maximumSize, Size *actualSize);pascal OSErr AEGetKeyDesc    (const AERecord *theAERecord, AEKeyword theAEKeyword, DescType desiredType, AEDesc *result);Requesting User Interactionpascal OSErr AESetInteractionAllowed(AEInteractAllowed level);pascal OSErr AEGetInteractionAllowed(AEInteractAllowed *level);pascal OSErr AEInteractWithUser(long timeOutInTicks, NMRecPtr nmReqPtr, IdleProcPtr idleProc);Requesting More Time to Respond to Apple Eventspascal OSErr AEResetTimer    (const AppleEvent *reply);Suspending and Resuming Apple Event Handlingpascal OSErr AESuspendTheCurrentEvent(const AppleEvent *theAppleEvent);pascal OSErr AEResumeTheCurrentEvent(const AppleEvent *theAppleEvent,const AppleEvent *reply,EventHandlerProcPtr dispatcher,long handlerRefcon);pascal OSErr AESetTheCurrentEvent(const AppleEvent *theAppleEvent);pascal OSErr AEGetTheCurrentEvent(AppleEvent *theAppleEvent);Getting the Sizes and Descriptor Types of Descriptor Recordspascal OSErr AESizeOfNthItem(const AEDescList *theAEDescList, long index, DescType *typeCode, Size *dataSize);pascal OSErr AESizeOfKeyDesc(const AERecord *theAERecord, AEKeyword theAEKeyword, DescType *typeCode, Size *dataSize);pascal OSErr AESizeOfParam    (const AppleEvent *theAppleEvent, AEKeyword theAEKeyword, DescType *typeCode, Size *dataSize);pascal OSErr AESizeOfAttribute(const AppleEvent *theAppleEvent, AEKeyword theAEKeyword, DescType *typeCode, Size *dataSize);Deleting Descriptor Recordspascal OSErr AEDeleteItem    (const AEDescList *theAEDescList, long index);pascal OSErr AEDeleteKeyDesc(const AERecord *theAERecord, AEKeyword theAEKeyword);pascal OSErr AEDeleteParam    (const AppleEvent *theAppleEvent, AEKeyword theAEKeyword);Deallocating Memory for Descriptor Recordspascal OSErr AEDisposeDesc    (AEDesc *theAEDesc);Coercing Descriptor Typespascal OSErr AECoercePtr    (DescType typeCode, const void* dataPtr, Size dataSize, DescType toType, AEDesc *result);pascal OSErr AECoerceDesc    (const AEDesc *theAEDesc, DescType toType, AEDesc *result);Creating and Managing the Coercion Handler Dispatch Tablespascal OSErr AEInstallCoercionHandler(DescType fromType, DescType toType, ProcPtr handler, long handlerRefcon, Boolean fromTypeIsDesc, Boolean isSysHandler);pascal OSErr AEGetCoercionHandler(DescType fromType, DescType toType, ProcPtr *handler, long *handlerRefcon, Boolean *fromTypeIsDesc, Boolean isSysHandler);pascal OSErr AERemoveCoercionHandler(DescType fromType, DescType toType, ProcPtr handler, Boolean isSysHandler);Creating and Managing the Special Handler Dispatch Tablespascal OSErr AEInstallSpecialHandler(AEKeyword functionClass, ProcPtr handler, Boolean isSysHandler);pascal OSErr AEGetSpecialHandler(AEKeyword functionClass, ProcPtr *handler, Boolean isSysHandler);pascal OSErr AERemoveSpecialHandler(AEKeyword functionClass, ProcPtr handler, Boolean isSysHandler);Getting Information About the Apple Event Manager/*available only in version 1.01 and later versions of Apple Event Manager*/pascal OSErr AEManagerInfo     (AEKeyword keyword, long *result);Application-Defined Routinespascal OSErr MyEventHandler    (const AppleEvent *theAppleEvent, const AppleEvent *reply, long handlerRefcon); pascal OSErr MyCoercePtr    (DescType typeCode, const void* dataPtr, Size dataSize, DescType toType, long handlerRefcon, AEDesc *result); pascal OSErr MyCoerceDesc    (const AEDesc *theAEDesc, DescType toType, long handlerRefcon, AEDesc *result);Assembly-Language SummaryTrap MacrosTrap Macros Requiring Routine Selectors_Pack8Selector    Routine    $011E    AESetInteractionAllowed    $0204    AEDisposeDesc    $0219    AEResetTimer    $021A    AEGetTheCurrentEvent    $021B    AEProcessAppleEvent    $021D    AEGetInteractionAllowed    $022B    AESuspendTheCurrentEvent    $022C    AESetTheCurrentEvent    $0407    AECountItems    $040E    AEDeleteItem    $0413    AEDeleteKeyDesc    $0413    AEDeleteParam    $0441    AEManagerInfo    $0500    AEInstallSpecialHandler    $0501    AERemoveSpecialHandler    $052D    AEGetSpecialHandler    $0603    AECoerceDesc    $061C    AEInteractWithUser    $0720    AERemoveEventHandler    $0723    AERemoveCoercionHandler    $0812    AEGetKeyDesc    $0812    AEGetParamDesc    $0818    AEResumeTheCurrentEvent    $0826    AEGetAttributeDesc    $0828    AESizeOfAttribute    $0829    AESizeOfKeyDesc    $0829    AESizeOfParam    $082A    AESizeOfNthItem    $091F    AEInstallEventHandler    $0921    AEGetEventHandler    $0A02    AECoercePtr    $0A22    AEInstallCoercionHandler    $0A0B    AEGetNthDesc    $0B24    AEGetCoercionHandler    $0D0C    AEGetArray    $0E11    AEGetKeyPtr    $0E11    AEGetParamPtr    $0E15    AEGetAttributePtr    $100A    AEGetNthPtr    Result CodesnoErr    0    No error    paramErr    –50    Parameter error (for example, value of handler pointer is NIL or odd)    eLenErr    –92    Buffer too big to send    memFullErr    –108    Not enough room in heap zone    userCanceledErr    –128    User canceled an operation    procNotFound    –600    No eligible process with specified process serial number    bufferIsSmall    –607    Buffer is too small    noOutstandingHLE    –608    No outstanding high-level event    connectionInvalid    –609    Nonexistent signature or session ID    noUserInteractionAllowed    –610    Background application sends event requiring authentication    noPortErr    –903    Client hasn’t set 'SIZE' resource to indicate awareness of high-level events    destPortErr    –906    Server hasn’t set 'SIZE' resource to indicate awareness of high-level events, or else is not present    sessClosedErr    –917    The kAEDontReconnect flag in the sendMode parameter was set, and the server quit and then restarted    errAECoercionFail    –1700    Data could not be coerced to the requested descriptor type    errAEDescNotFound    –1701    Descriptor record was not found    errAECorruptData    –1702    Data in an Apple event could not be read    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    errAENewerVersion    –1706    Need a newer version of the Apple Event Manager    errAENotAppleEvent    –1707    Event is not an Apple event    errAEEventNotHandled    –1708    Event wasn’t handled by an Apple event handler    errAEReplyNotValid    –1709    AEResetTimer was passed an invalid reply    errAEUnknownSendMode    –1710    Invalid sending mode was passed    errAEWaitCanceled    –1711    User canceled out of wait loop for reply or receipt    errAETimeout    –1712    Apple event timed out    errAENoUserInteraction    –1713    No user interaction allowed    errAENotASpecialFunction    –1714    The keyword is not valid for a special function    errAEParamMissed    –1715    Handler cannot understand a parameter the client considers required    errAEUnknownAddressType    –1716    Unknown Apple event address type    errAEHandlerNotFound    –1717    No handler found for an Apple event or a coercion, or no object callback function found    errAEReplyNotArrived    –1718    Reply has not yet arrived    errAEIllegalIndex    –1719    Not a valid list index    errAEImpossibleRange    –1720    The range is not valid because it is impossible for a range to include the first and last objects that were specified; an example is a range in which the offset of the first object is greater than the offset of the last object    errAEWrongNumberArgs    –1721    The number of operands provided for the kAENot logical operator is not 1    errAEAccessorNotFound    –1723    There is no object accessor function for the specified object class and token descriptor type    errAENoSuchLogical    –1725    The logical operator in a logical descriptor record is not kAEAnd, kAEOr, or kAENot    errAEBadTestKey    –1726    The descriptor record in a test key is neither a comparison descriptor record nor a logical descriptor record    errAENotAnObjectSpec    –1727    The objSpecifier parameter of AEResolve is not an object specifier record    errAENoSuchObject    –1728     A run-time resolution error, for example: object specifier record asked for the third element, but there are only two    errAENegativeCount    –1729     Object-counting function returned negative value    errAEEmptyListContainer    –1730    The container for an Apple event object is specified by an empty list    errAEUnknownObjectType    –1731    Descriptor type of token returned by AEResolve is not known to server application     errAERecordingIsAlreadyOn    –1732    Attempt to turn recording on when it is already on    Listing 5-0Table 5-0Creating and Sending Apple EventsContentsCreating an Apple Event5-3Adding Parameters to an Apple Event5-5Specifying Optional Parameters for an Apple Event5-7Specifying a Target Address5-10Creating an Address Descriptor Record5-11Addressing an Apple Event for Direct Dispatching5-13Sending an Apple Event5-13Dealing With Timeouts5-20Writing an Idle Function5-21Writing a Reply Filter Function5-24Reference to Creating and Sending Apple Events5-24Routines for Creating and Sending Apple Events5-25Creating Apple Events5-25Creating and Duplicating Descriptor Records5-26Creating Descriptor Lists and AE Records5-28Adding Items to Descriptor Lists5-29Adding Data and Descriptor Records to AE Records5-32Adding Parameters and Attributes to Apple Events5-33Sending Apple Events5-37Application-Defined Routines5-41Summary of Creating and Sending Apple Events5-44Pascal Summary5-44Constants5-44Data Types5-48Routines for Creating and Sending Apple Events5-50Application-Defined Routines5-51C Summary5-51Constants5-51Data Types5-56Routines for Creating and Sending Apple Events5-57Application-Defined Routines5-59Assembly-Language Summary5-59Trap Macros5-59Result Codes5-60Creating and Sending Apple EventsThis chapter describes how your application can use the Apple Event Manager to create and send Apple events. If you want to factor your application for recording, or if you want your application to send Apple events directly to other applications, you can use Apple Event Manager routines to create and send Apple events. Before you read this chapter, you should be familiar with the chapters “Introduction to Interapplication Communication,” “Introduction to Apple Events,” and “Responding to Apple Events” in this book. If you are factoring your application, you should also be familiar with the chapter “Recording Apple Events” in this book.This chapter provides the basic information you need to create and send Apple events from your application. To send core and functional-area Apple events, your application must also be able to create object specifier records. For information about object specifier records, see the chapter “Resolving and Creating Object Specifier Records” in this book.To allow your application to send Apple events to applications on other computers, you may wish to use the PPCBrowser function, which is described in the chapter “Program-to-Program Communications Toolbox” in this book.The first section in this chapter, “Creating an Apple Event,” describes how ton    create an Apple eventn    add parameters to an Apple eventn    specify optional Apple event parametersn    specify a target addressThe section “Sending an Apple Event” describes how to n    send an Apple eventn    deal with timeoutsn    write an idle functionn    write a reply filter functionCreating an Apple EventYou create an Apple event by using the AECreateAppleEvent function. You supply parameters that specify the event class and event ID, the target address, the return ID, and the transaction ID, and a buffer for the returned Apple event. The AECreateAppleEvent function creates and returns, in the buffer you specify, an Apple event with the attributes set as your application requested. You should not directly manipulate the contents of the Apple event; rather, use Apple Event Manager functions to add additional attributes or parameters to it.The example that follows creates an imaginary Multiply event using the AECreateAppleEvent function.myErr := AECreateAppleEvent(kArithmeticClass, kMultEventID,                                     targetAddress, kAutoGenerateReturnID,                                     kAnyTransactionID, theAppleEvent);  The event class, specified by the kArithmeticClass constant, identifies this event as belonging to a class of Apple events for arithmetic operations. The event ID specifies the particular Apple event within the class—in this case, an Apple event that performs multiplication.You specify the target of the Apple event in the third parameter to AECreateAppleEvent. The target address can identify an application on the local computer or another computer on the network. You can specify the address using a target ID record or session reference number. For processes on the local computer, you can also use a process serial number or application signature to specify the address. See “Specifying a Target Address” on page 5-10 for more information. In the fourth parameter, you specify the return ID of the Apple event, which associates this Apple event with the server’s reply. The AECreateAppleEvent function assigns the specified return ID value to the keyReturnIDAttr attribute of the Apple event. If a server returns a standard reply Apple event (that is, an event of event class 'aevt' and event ID 'ansr') in response to this event, the Apple Event Manager assigns the reply event the same return ID. When you receive a reply Apple event, you can check the keyReturnIDAttr attribute to determine which outstanding Apple event the reply is responding to. You can use the kAutoGenerateReturnID constant to request that the Apple Event Manager generate a return ID that is unique to this session for the Apple event. Otherwise, you are responsible for making it unique. The fifth parameter specifies the transaction ID attribute of the Apple event. A transaction is a sequence of Apple events that are sent back and forth between the client and server applications, beginning with the client’s initial request for a service. All Apple events that are part of one transaction must have the same transaction ID.You can use a transaction ID to indicate that an Apple event is one of a sequence of Apple events related to a single transaction. The kAnyTransactionID constant indicates that the Apple event is not part of a transaction.The AECreateAppleEvent function creates an Apple event with only the specified attributes and no parameters. To add parameters or additional attributes, you can use other Apple Event Manager functions.Adding Parameters to an Apple EventYou can use the AEPutParamPtr or AEPutParamDesc function to add parameters to an Apple event. When you use either of these functions, the Apple Event Manager adds the specified parameter to the Apple event. Use the AEPutParamPtr function when you want to add data specified in a buffer as the parameter of an Apple event. You specify the Apple event, the keyword of the parameter to add, the descriptor type, a buffer that contains the data, and the size of this buffer as parameters to the AEPutParamPtr function. The AEPutParamPtr function adds the data to the Apple event as a parameter with the specified keyword.For example, this code adds a parameter to the Multiply event using the AEPutParamPtr function:CONST        keyOperand1 = 'OPN1';VAR    number1:                        LongInt;    theAppleEvent:                        AppleEvent;    myErr:                        OSErr;number1 := 10;myErr := AEPutParamPtr(theAppleEvent, keyOperand1,                               typeLongInteger, @number1,                              SizeOf(number1));In this example, the Apple Event Manager adds the parameter containing the first number to the specified Apple event. Use the AEPutParamDesc function to add a descriptor record to an Apple event. The descriptor record you specify must already exist. To create or get a descriptor record, you can use the AECreateDesc, AEDuplicateDesc, and other Apple Event Manager functions that return a descriptor record.When you create a descriptor record using the AECreateDesc function, you specify the descriptor type, a buffer that contains the data, and the size of this buffer as parameters. The AECreateDesc function returns the descriptor record that describes the data.This example creates a descriptor record for the second parameter of the Multiply event:VAR    number2:                         LongInt;    multParam2Desc:                        AEDesc;    myErr:                        OSErr;number2 := 8;myErr := AECreateDesc(typeLongInteger, @number2, SizeOf(number2),                             multParam2Desc); In this example, the AECreateDesc function creates a descriptor record with the typeLongInteger descriptor type and the data identified in the number2 variable.Once you have created a descriptor record, you can use AEPutParamDesc to add the data to an Apple event parameter. You specify the Apple event to add the parameter to, the keyword of the parameter, and the descriptor record of the parameter as parameters to the AEPutParamDesc function.This example adds a second parameter to the Multiply event using the AEPutParamDesc function:CONST        keyOperand2 = 'OPN2';myErr := AEPutParamDesc(theAppleEvent, keyOperand2,                                 multParam2Desc);This example adds the keyOperand2 keyword and the descriptor record created in the previous example as the second parameter to the specified Apple event. You can also create a descriptor record without using Apple Event Manager routines. For example, this example generates an alias descriptor record from an existing alias handle:WITH myAliasDesc DO    BEGIN        descriptorType := typeAlias;        dataHandle := myAliasHandle;    END;Whatever method you use to create a descriptor record, you can add it to an Apple event parameter by using AEPutParamDesc.After adding parameters to an Apple event, you can send the Apple event using the AESend function. See “Sending an Apple Event,” which begins on page 5-13, for information about using this function.Specifying Optional Parameters for an Apple EventThe parameters for a given Apple event are listed in the Apple Event Registry: Standard Suites as either required or optional. Your application does not usually have to include Apple event parameters that are listed as optional; the target application uses default values for parameters that are listed as optional if your application does not provide them. The Apple Event Registry: Standard Suites defines the default value a target application should use for each optional parameter of a specific Apple event. The guidelines listed in the Apple Event Registry: Standard Suites for which parameters should be considered optional and which should be considered required are not enforced by the Apple Event Manager. Instead, the source application indicates which Apple event parameters it considers optional by listing the keywords for those parameters in the keyOptionalKeywordAttr attribute. The keyOptionalKeywordAttr attribute does not contain the optional parameters; it simply lists the keywords of any parameters for the Apple event that the source application wants to identify as optional. Although the source application is responsible for providing this information in the keyOptionalKeywordAttr attribute of an Apple event, it is not required to provide this attribute.If a keyword for an Apple event parameter is not included in the keyOptionalKeywordAttr attribute, the source application expects the target application to understand the Apple event parameter identified by that keyword. If a target application cannot understand the parameter, it should return the result code errAEParamMissed and should not attempt to handle the event.If a keyword for an Apple event parameter is included in the keyOptionalKeywordAttr attribute, the source application does not require the target application to understand the Apple event parameter identified by that keyword. If the target application cannot understand a parameter whose keyword is included in the keyOptionalKeywordAttr attribute, it should ignore that parameter and attempt to handle the Apple event as it normally does.A source application can choose not to list the keyword for an Apple event parameter in the keyOptionalKeywordAttr attribute even if that parameter is listed in the Apple Event Registry: Standard Suites as an optional parameter. This has the effect of forcing the target application to treat the parameter as required for a particular Apple event. If the target application supports the parameter, it should handle the Apple event as the client application expects. If the target application does not support the parameter and calls an application-defined routine such as MyGotRequiredParams to check whether it has received all the required parameters, it finds that there’s another parameter that the client application considered required, and should return the result code errAEParamMissed. If a source application wants a target application to attempt to handle an Apple event regardless of whether the target application supports a particular Apple event parameter included in that Apple event, the source application should list the keyword for that parameter in the keyOptionalKeywordAttr attribute. It is up to the source application to decide whether to list a parameter that is described as optional in the Apple Event Registry: Standard Suites in the keyOptionalKeywordAttr attribute of an Apple event. For example, suppose a source application has extended the definition of the Print event to include an optional keyColorOrGrayscale parameter that specifies printing in color or gray scale rather than black and white. The source application might decide whether or not to list the keyword keyColorOrGrayscale in the keyOptionalKeywordAttr attribute according to the characteristics of the print request. If the source application requires the target application to print a document in color, the source application could choose not to add the keyword keyColorOrGrayscale to the keyOptionalKeywordAttr attribute; in this case, only target applications that supported the keyColorOrGrayscale parameter would attempt to handle the event. If the source application does not require the document printed in color, it could choose to add the keyword keyColorOrGrayscale to the keyOptionalKeywordAttr attribute; in this case, the target application will attempt to handle the event regardless of whether it supports the keyColorOrGrayscale parameter.Your application can add optional parameters to an Apple event the same way it adds required parameters, using the AECreateDesc, AEPutParamPtr, and AEPutParamDesc functions as described in the previous section, “Adding Parameters to an Apple Event.” If your application chooses to provide the keyOptionalKeywordAttr attribute for an Apple event, it should first create a descriptor list that specifies the keywords of the optional parameters, then add it to the Apple event as a keyOptionalKeywordAttr attribute. Listing 5-1 shows an application-defined routine, MyCreateOptionalKeyword, that creates the keyOptionalKeywordAttr attribute for the Create Publisher event.Listing 5-1    Creating the optional keyword for the Create Publisher eventFUNCTION MyCreateOptionalKeyword                                (VAR createPubAppleEvent: AppleEvent)                                 : OSErr;VAR    optionalList:                    AEDescList;    myOptKeyword1:                    AEKeyword;    myOptKeyword2:                    AEKeyword;    myErr:                    OSErr;    ignoreErr:                    OSErr;BEGIN                                    myOptKeyword1 := keyDirectObject;    {create an empty descriptor list}    myErr := AECreateList(NIL, 0, FALSE, optionalList);    IF myErr = noErr THEN     BEGIN        {add the keyword of the first optional parameter}        myErr := AEPutPtr(optionalList, 1, typeKeyword,                                 @myOptKeyword1, SizeOf(myOptKeyword1));        IF myErr = noErr THEN         BEGIN            {add the keyword of the next optional parameter}            myOptKeyword2 := keyAEEditionFileLoc;            myErr := AEPutPtr(optionalList, 2, typeKeyword,                                     @myOptKeyword2, SizeOf(myOptKeyword2));        END;        IF myErr = noErr THEN             {create the keyOptionalKeywordAttr attribute and add it }            { to the Create Publisher event}            myErr :=     AEPutAttributeDesc(createPubAppleEvent,                                                 keyOptionalKeywordAttr,                                                  optionalList);    END;    ignoreErr := AEDisposeDesc(optionalList);    MyCreateOptionalKeyword := myErr;END;The MyCreateOptionalKeyword function shown in Listing 5-1 adds to a descriptor list the keyword of each parameter that the source application considers optional. Each keyword is added as a descriptor record with the descriptor type typeKeyword. The function specifies that the target application can handle the Create Publisher event without supporting parameters identified by the keywords keyDirectObject and keyAEEditionFileLoc. (These are the parameters that specify the Apple event object to publish and the location of the edition container; if these parameters are missing, the target application creates a publisher for the current selection using the application’s default edition container.) After adding these keywords to the descriptor list, the function creates the keyOptionalKeywordAttr attribute using the AEPutAttributeDesc function.Typically a target application does not examine the keyOptionalKeywordAttr attribute directly. Instead, a target application that supports a parameter listed as optional in the Apple Event Registry: Standard Suites attempts to extract it from the Apple event (using AEGetParamDesc, for example). If it can’t extract the parameter, the target application uses the default value, if any, listed in the Apple Event Registry. A target application can use the keyMissedKeywordAttr attribute to return the first required parameter (that is, considered required by the source application), if any, that it did not retrieve from the Apple event. The keyMissedKeywordAttr attribute does not return any parameters whose keywords are listed in the keyOptionalKeywordAttr attribute of the Apple event.        Specifying a Target AddressWhen you create an Apple event, you must specify the address of the target. The target address identifies the particular application or process to which you want to send the Apple event. You can send Apple events to applications on the local computer or on remote computers on the network. These are the descriptor types that identify the four methods of addressing an Apple event:typeApplSignature    The application signature of the target    typeSessionID    The session reference number of the target    typeTargetID    The target ID record of the target    typeProcessSerialNumber    The process serial number of the target    To address an Apple event to a target on a remote computer on the network, you must use either the typeSessionID or typeTargetID descriptor type.   If your application sends an Apple event to itself, it should address the Apple event using a process serial number of kCurrentProcess. This is the fastest way for your application to send an Apple event to itself. For more information, see “Addressing an Apple Event for Direct Dispatching” on page 5-13.You can use any of the four address types when sending an Apple event to another application on the local computer. The chapter “Event Manager” in Inside Macintosh: Macintosh Toolbox Essentials describes all four types of addresses. Your application can also use another address type if it provides a coercion handler that coerces the address type into one of the four address types that the Apple Event Manager recognizes. See “Writing and Installing Coercion Handlers,” which begins on page 4-41, for more information.To allow the user to choose the target of an Apple event, use the PPCBrowser function. This function presents a standard user interface for choosing a target application, much as the Standard File Package provides a standard user interface for opening and saving files. The PPCBrowser function returns, in a target ID record, information about the application the user chose. Listing 5-3 on page 5-12 shows how to use the PPCBrowser function to let the user choose a target. Creating an Address Descriptor RecordYou specify the address using an address descriptor record (a descriptor record of data type AEAddressDesc). You must create a descriptor record of this type and then add it to the Apple event using the AECreateAppleEvent function.You can use the AECreateDesc function to create address descriptor records for any of the four types of target addresses. Listing 5-2 shows four possible ways to create an address, each using a different address type.Listing 5-2    Creating a target addressPROCEDURE MySetTargetAddresses(VAR targetAddress1,                                            targetAddress2, targetAddress3,                                          targetAddress4: AEAddressDesc;                                          toTargetID: TargetID;                                           thePSN: ProcessSerialNumber;                                          theSignature: OSType;                                          theSessionRef: PPCSessRefNum);VAR    myErr:             OSErr;BEGIN    myErr := AECreateDesc(typeTargetID, @toTargetID,                                 SizeOf(toTargetID), targetAddress1);    myErr := AECreateDesc(typeProcessSerialNumber, @thePSN,                                  SizeOf(thePSN), targetAddress2);    myErr := AECreateDesc(typeApplSignature, @theSignature,                                  SizeOf(theSignature), targetAddress3);    myErr := AECreateDesc(typeSessionID, @theSessionRef,                                  SizeOf(theSessionRef), targetAddress4);    {add your own error checking}END;To create an address descriptor record, specify the following as parameters to AECreateDesc: the descriptor type for the address, a pointer to the buffer containing the address, and the size of the buffer. The AECreateDesc function returns an address descriptor record with the specified characteristics.After creating an address, you can specify it as a parameter to the AECreateAppleEvent function. See “Creating an Apple Event,” which begins on page 5-3, for an example using the AECreateAppleEvent function. When you specify an address to the AECreateAppleEvent function, the Apple Event Manager stores the address in the keyAddressAttr attribute of the Apple event. If you use the PPCBrowser function to allow the user to choose an Apple event’s target, your application must create a target ID record based on the user’s choice. Listing 5-3 shows how to create a target ID record using the information returned from the PPCBrowser function and create an address descriptor record using the AECreateDesc function.Listing 5-3    Specifying a target address in an Apple event by using the PPCBrowser functionFUNCTION MyGetTargetAddress (myPrompt: Str255; myAppStr: Str255;                                        VAR myPortInfo: PortInfoRec;                                         VAR targetAddress: AEAddressDesc;                                         VAR toTargetID: targetID): OSErr;VAR    myErr:            OSErr;BEGIN                            {use PPCBrowser to let user choose the target}    myErr := PPCBrowser(myPrompt, myAppStr, FALSE,                                 toTargetID.location,                                 myPortInfo, NIL, '');    MyGetTargetAddress := myErr;    IF myErr <> noErr THEN Exit(MyGetTargetAddress);    toTargetID.name := myPortInfo.name;    {create the descriptor record for the target address}    MyGetTargetAddress := AECreateDesc(typeTargetID, @toTargetID,                                                      SizeOf(toTargetID),                                                     targetAddress);END;See the chapter “Program-to-Program Communications Toolbox” in this book for more information on using the PPCBrowser function.Addressing an Apple Event for Direct DispatchingAs described in the chapter “Recording Apple Events” in this book, a recordable application must send itself Apple events in response to user actions. Your application can send itself Apple events by using an address descriptor record of descriptor type typeProcessSerialNumber with the lowLongOfPSN field set to kCurrentProcess and the highLongOfPSN set to 0. The Apple Event Manager processes such Apple events immediately, executing the appropriate Apple event handler directly without going through the normal event-processing sequence. For this reason, your application will not appear to run more slowly when it sends Apple events to itself.  Apple events your application sends to itself this way do not appear in your application’s high-level event queue. This not only speeds up delivery of the event but also avoids situations in which an Apple event sent in response to a user action arrives in the event queue after some other event that really occurred later than the user action. For example, suppose a user chooses Cut from the Edit menu and then clicks in another window. If the Cut event arrives in the queue after the window activate event, a selection in the wrong window might be cut.Your application can send events to itself using other forms of addressing, such as the true process serial number returned by GetCurrentProcess. Because direct dispatching avoids event sequence problems, applications should generally send events to themselves by using an address descriptor record of descriptor type typeProcessSerialNumber with the kCurrentProcess constant rather than using a true process serial number or an application signature. IMPORTANTWhen Apple event recording has been turned on, the Apple Event Manager records every event that your application sends to itself unless you specify the kAEDontRecord flag in the sendMode parameter of the AESend function.s Sending an Apple EventTo send an Apple event, you first create an Apple event, add parameters and attributes to it, and then use the AESend function to send it. When you send an Apple event, you specify various options to indicate how the server should handle the Apple event. You request a user interaction level from the server and specify whether the server can switch directly to the foreground if user interaction is needed, whether your application is willing to wait for a reply Apple event, whether reconnection is allowed, and whether your application wants a return receipt for the Apple event. You specify these options by setting flags in the sendMode parameter for AESend. Here are the constants that represent these flags:CONST         kAENoReply                        = $00000001;                {client doesn't want reply}        kAEQueueReply                        = $00000002;    {client wants Apple Event }                                                 { Manager to return }                                                { reply in event queue}        kAEWaitReply                        = $00000003;        {client wants a reply and }                                                { will give up processor}        kAENeverInteract                        = $00000010;        {server application }                                                { should not interact }                                                { with user for this }                                                { Apple event}        kAECanInteract                        = $00000020;    {server may interact with }                                                { user for this Apple }                                                { event to supply }                                                 { information}        kAEAlwaysInteract                        = $00000030;    {server may interact with }                                                { user for this Apple }                                                { event even if no }                                                { information                 is required}        kAECanSwitchLayer                        = $00000040;    {server should come }                                                { directly to foreground }                                                { when appropriate}        kAEDontReconnect                        = $00000080;    {don't reconnect if there }                                                { is a PPC session closed }                                                { error}        kAEWantReceipt                        = nReturnReceipt;                {client wants return }                                                      { receipt}        kAEDontRecord                        = $00001000;                {don’t record this event}        kAEDontExecute                        = $00002000;    {don’t execute this event}If you want your application to receive a reply Apple event, specify the kAEQueueReply or kAEWaitReply flag. If you want your application to receive the reply Apple event in its event queue, use kAEQueueReply. If you want your application to receive the reply Apple event in the reply parameter for AESend and you are willing to give up the processor while it is waiting for the reply, use kAEWaitReply. If you don’t want your application to receive a reply Apple event and your application doesn’t need to wait for the server to handle the Apple event, specify kAENoReply. NoteNoteBefore the Apple Event Manager sends a reply event back to the client application, the keyAddressAttr attribute contains the address of the client application. After the client receives the reply event, the keyAddressAttr attribute contains the address of the server application.uIf you specify kAENoReply or kAEQueueReply, the AESend function returns immediately after using the Event Manager to send the event. In this case, a noErr result code from AESend indicates that the Event Manager sent the Apple event; it does not mean that the server accepted or handled the Apple event. When AESend returns, the reply parameter does not contain valid data if your application specifies kAENoReply or kAEQueueReply. The kAENoReply flag indicates that the Apple Event Manager will not return the reply Apple event to your application. The kAEQueueReply flag indicates that you want your application to receive the reply via its event queue rather than the reply parameter of AESend. If you specify kAEQueueReply, you must install a handler for the reply Apple event (event class kCoreEventClass and event ID kAEAnswer). If you specify kAEWaitReply, the Apple Event Manager uses the Event Manager to send the event. The Apple Event Manager then calls the WaitNextEvent function on behalf of your application, causing your application to yield the processor and giving the server application a chance to receive and handle the Apple event. Your application continues to yield the processor until the server handles the Apple event or the request times out. If you specify kAEWaitReply, you must provide an idle function. This function should process any update events, null events, operating-system events, or activate events that occur while your application is waiting for a reply. See “Writing an Idle Function,” which begins on page 5-21, for sample code that shows an idle function. You use one of the three flags—kAENeverInteract, kAECanInteract, and kAEAlwaysInteract—to specify whether the server should interact with the user when handling the Apple event. Specify kAENeverInteract if the server should not interact with the user when handling the Apple event. You might specify this constant if you don’t want the user to be interrupted while the server is handling the Apple event.Use the kAECanInteract flag if the server should interact with the user when the user needs to supply information to the server. Use the kAEAlwaysInteract flag if the server should interact with the user whenever the server normally asks a user to confirm a decision or interact in any other way, even if no additional information is needed from the user. Note that it is the responsibility of the server and client applications to agree on how to interpret the kAEAlwaysInteract flag. If the client application does not set any one of the user interaction flags, the Apple Event Manager sets a default, depending on the location of the target of the Apple event. If the server application is on a remote computer, the Apple Event Manager sets the kAENeverInteract flag as the default. If the target of the Apple event is on the local computer, the Apple Event Manager sets the kAECanInteract flag as the default.The server application should call AEInteractWithUser if it needs to interact with the user. If both the client and the server allow user interaction, the Apple Event Manager attempts to bring the server to the foreground if it is not already the foreground process. If both the kAECanSwitchLayer and the kAEWaitReply flags are set, and if the client application is the active application on the local computer, the Apple Event Manager brings the server application directly to the front. Otherwise, the Apple Event Manager posts a notification request asking the user to bring the server application to the front, regardless of whether the kAECanSwitchLayer flag is set. This ensures that the user will not be interrupted by an unexpected application switch. You should specify the kAECanSwitchLayer flag only when the client and server applications reside on the same computer. In general, you should not set this flag if it would be confusing or inconvenient to the user for the server application to come to the front unexpectedly. This flag is ignored if you are sending an Apple event to a remote computer.Specify the kAEDontReconnect flag if the Apple Event Manager should not reconnect if it receives a session closed error from the PPC Toolbox. If you don’t set this flag, the Apple Event Manager automatically attempts to reconnect and reestablish the session.Specify the kAEWantReceipt flag if your application wants notification that the server application has accepted the Apple event. If you specify this flag, your application receives a return receipt as a high-level event.If you specify the kAEWantReceipt flag and the server application does not accept the Apple event within the time specified by the timeOutInTicks parameter to AESend, the AESend function returns a timeout error. Note that AESend also returns a timeout error if your application sets the kAEWaitReply flag and does not receive the reply Apple event within the time specified by the timeOutInTicks parameter.Specify the kAEDontRecord flag if your application is sending an Apple event to itself that you don’t want to be recorded. When Apple event recording has been turned on, every event that your application sends to itself will be automatically recorded by the Apple Event Manager except those sent with the kAEDontRecord flag set.Specify the kAEDontExecute flag if your application is sending an Apple event to itself for recording purposes only—that is, if you want the Apple Event Manager to send a copy of the event to the recording process but you do not want your application actually to receive the event. (For more information about when to use the kAEDontExecute flag, see the chapter “Recording Apple Events” in this book.)Listing 5-4 illustrates how to send a Multiply event (an imaginary Apple event for multiplying two long integers). It first creates an Apple event, adds parameters containing the numbers to multiply, then sends it, specifying various options. It also illustrates how to handle the reply Apple event that contains the result.NoteNoteIf you want to send Apple events, your application must set flags in its 'SIZE' resource indicating that it can handle high-level events, and it must provide handlers for the required Apple events. See “Accepting an Apple Event” on page 4-5 for information on setting the appropriate flags in the 'SIZE' resource and “Handling the Required Apple Events” on page 4-11 for information on supporting the required Apple events.uListing 5-4    Sending an Apple eventFUNCTION MySendMultiplyEvent (serverAddress: AEAddressDesc;                                        firstOperand: LongInt; secondOperand:                     LongInt;                                        VAR replyResultLongInt: LongInt): OSErr;CONST    kArithmeticClass                         =    'ARTH';             {event class for arithmetic }                                            { Apple events}    kMultiplyEventID                         =    'MULT';             {event ID for Multiply event}    keyMultOperand1                        =     'OPN1';            {keyword for first parameter}    keyMultOperand2                        =     'OPN2';             {keyword for second parameter}VAR    theAppleEvent:                         AppleEvent;    reply:                         AppleEvent;    returnedType:                        DescType;    actualSize:                         LongInt;    myErr:                        OSErr;    ignoreErr:                        OSErr;     errStr:                        Str255;    errNumber:                        LongInt;BEGIN    myErr := AECreateAppleEvent(kArithmeticClass, kMultiplyEventID,                                          serverAddress, kAutoGenerateReturnID,                                         kAnyTransactionID, theAppleEvent);    IF myErr = noErr THEN         {add the first operand}        myErr := AEPutParamPtr(theAppleEvent, keyMultOperand1,                                       typeLongInteger, @firstOperand,                                         SizeOf(firstOperand));    {add the second operand with the proper keyword}    IF myErr = noErr THEN        myErr := AEPutParamPtr(theAppleEvent, keyMultOperand2,                                       typeLongInteger, @secondOperand,                                       SizeOf(secondOperand));    IF myErr = noErr THEN        myErr := AESend(theAppleEvent, reply, kAEWaitReply +             kAENeverInteract,                          kAENormalPriority, 120, @MyIdleFunction, NIL);    IF myErr = noErr THEN {Apple event successfully sent}    BEGIN              {Check whether it was successfully handled-- }               { get result code returned by the server's handler}        myErr := AEGetParamPtr(reply, keyErrorNumber, typeLongInteger,                                       returnedType, @errNumber, SizeOf(errNumber),                                       actualSize);        IF (myErr = errAEDescNotFound) OR (errNumber = noErr) THEN        {if keyErrorNumber doesn't exist or server returned noErr }        { then the Apple event was successfully handled--the reply Apple }        { event contains the result in the direct parameter}            myErr := AEGetParamPtr(reply, keyDirectObject, typeLongInteger,                                           returnedType, @replyResultLongInt,                                          SizeOf(replyResultLongInt), actualSize)        ELSE        BEGIN            {server returned an error, so get error string}            myErr := AEGetParamPtr(reply, keyErrorString, typeChar,                                             returnedType, @errStr[1], SizeOf(errStr)-1,                                           actualSize);            IF myErr = noErr THEN            BEGIN                IF actualSize > 255 THEN                    actualSize := 255;                errStr[0] := chr(actualSize);                MyDisplayError(errStr);            END;        END;    ignoreErr := AEDisposeDesc(reply);    END    ELSE    BEGIN        {the Apple event wasn't successfully dispatched, }        { the request timed out, the user canceled, or other error}     END;    ignoreErr := AEDisposeDesc(theAppleEvent);    MySendMultiplyEvent := myErr;END;The code in Listing 5-4 first creates an Apple event with kArithmeticClass as the event class and kMultiplyEventID as the event ID. It also specifies the server of the Apple event. See “Specifying a Target Address” on page 5-10 for information on specifying a target address and “Creating an Apple Event,” which begins on page 5-3, for more information on creating an Apple event.The Multiply event shown in Listing 5-4 contains two parameters, each specifying a number to multiply. See “Adding Parameters to an Apple Event” on page 5-5 for examples of how to specify the parameters for the AEPutParamPtr function. After adding the parameters to the event, the code uses AESend to send the event. The first parameter to AESend specifies the Apple event to send—in this example, the Multiply event. The next parameter specifies the reply Apple event. This example specifies kAEWaitReply in the third parameter, indicating that the client is willing to yield the processor for the specified timeout value (120 ticks, or 2 seconds). The kAENeverInteract flag indicates that the server should not interact with the user when processing the Apple event. The fourth parameter specifies that the Multiply event is to be sent using normal priority (that is, placed at the end of the event queue). You can specify the kAEHighPriority flag to place the event in the front of the event queue, but this is not usually recommended.The next to last parameter specifies the address of an idle function. If you specify kAEWaitReply, you must provide an idle function. This function should process any update events, null events, operating-system events, or activate events that occur while your application is waiting for a reply. See “Writing an Idle Function,” which begins on page 5-21, for sample code that shows an idle function. The last parameter to AESend specifies a filter function. You can supply a filter function to filter high-level events that your application may receive while waiting for a reply Apple event. You can specify NIL for this parameter if you do not need to filter high-level events while waiting for a reply. See “Writing a Reply Filter Function” on page 5-24 for more information. If you specify kAEWaitReply, a noErr result code from AESend indicates that the Apple event was sent successfully, not that the server has completed the requested action successfully. Therefore, you should find out whether a result code was returned from the handler by checking the reply Apple event for the existence of either the keyErrorNumber or keyErrorString parameter. If the keyErrorNumber parameter does not exist or contains the noErr result code, you can use AEGetParamPtr to get the parameter you’re interested in from the reply Apple event. The MySendMultiplyEvent function in Listing 5-4 checks the function result of AESend. If it is noErr, MySendMultiplyEvent checks the keyErrorNumber parameter of the reply Apple event to determine whether the server successfully handled the Apple event. If this parameter exists and indicates that an error occurred, MySendMultiplyEvent gets the error string out of the keyErrorString parameter. Otherwise, the server performed the request, and the reply Apple event contains the answer to the multiplication request.When you have finished using the Apple event specified in the AESend function and no longer need the reply Apple event, you must dispose of both the original event and the reply by calling the AEDisposeDesc function.IMPORTANTIf your application sends Apple events to itself using a typeProcessSerialNumber address descriptor record with the lowLongOfPSN field set to kCurrentProcess, the Apple Event Manager jumps directly to the appropriate Apple event handler without going through the normal event-processing sequence. For this reason, your application will not appear to run more slowly when it sends Apple events to itself. For more information, see “Addressing an Apple Event for Direct Dispatching” on page 5-13.s Dealing With TimeoutsWhen your application calls AESend and chooses to wait for the server application to handle the Apple event, it can also specify the maximum amount of time it is willing to wait for a response. You can specify a timeout value in the timeOutInTicks parameter to AESend. You can either specify a particular length of time, in ticks, that your application is willing to wait, or you can specify the kNoTimeOut constant or the kAEDefaultTimeout constant. Use the kNoTimeOut constant to indicate that your application is willing to wait forever for a response from the server. You should use this value only if you are sure that the server will respond in a reasonable amount of time. You should also implement a method of checking whether the user wants to cancel. The idle function that you specify as a parameter to AESend should check the event queue for any instances of Command-period and immediately return TRUE as its function result if it finds a request to cancel in the event queue.Use the kAEDefaultTimeout constant if you want the Apple Event Manager to use a default timeout value. The Apple Event Manager uses a timeout value of about one minute if you specify this constant.If you set the kAEWaitReply flag and the server doesn’t have a handler for the Apple event, the server immediately returns the errAEEventNotHandled result code. If the server doesn’t respond within the length of time specified by the timeout value, AESend returns the errAETimeout result code and a reply Apple event that contains no data. This result code does not necessarily mean that the server failed to perform the requested action; it means only that the server did not complete processing within the specified time. The server might still be processing the Apple event, and it might still send a reply.If the server finishes processing the Apple event sometime after the time specified in the keyTimeoutAttr attribute has expired, it returns a reply Apple event to AEProcessAppleEvent. The Apple Event Manager then adds the actual data to the reply. Thus, your application can continue to check the reply Apple event to see if the server has responded, even after the time expires. If the server has not yet sent the reply when the client attempts to extract data from the reply Apple event, the Apple Event Manager functions return the errAEReplyNotArrived result code. After the reply Apple event returns from the server, the client can extract the data in the reply.Additionally, the server can examine the keyTimeoutAttr attribute of the Apple event to determine the timeout value specified by the client. You can use the value of this attribute as a rough estimate of how much time your handler has to respond. You can assume that your handler has less time to respond than the timeout value, because transmitting the Apple event uses some of the available time, as does transmitting the reply Apple event back to the client, and the event may have been in the queue for a while already.If you set the kAENoReply or kAEQueueReply flag, the Apple Event Manager ignores any timeout value you specify, because your application is not waiting for the reply. An attempt by the server to examine the keyTimeoutAttr attribute in this situation generates the error errAEDescNotFound.If your handler needs more time than is specified in the keyTimeoutAttr attribute, you can reset the timer by using the AEResetTimer function. This function resets the timeout value of an Apple event to its starting value.Writing an Idle FunctionThis section describes how to write an idle function for use with the AESend or AEInteractWithUser function.When your application sends an Apple event, you can set one of three flags in the sendMode parameter to AESend that specify how you want to deal with the reply: kAENoReply if you don’t want your application to receive a reply, kAEQueueReply if you want it to receive the reply in its event queue, or kAEWaitReply if you want the reply returned in the reply parameter of AESend and you are willing to give up the processor while your application is waiting for the reply.If you specify kAENoReply or kAEQueueReply, the AESend function returns immediately after using the Event Manager to send the event. If you specify kAEWaitReply, the AESend function does not return until either the server application finishes handling the Apple event or a specified amount of time expires. In this case the AESend function calls WaitNextEvent on behalf of your application. This yields the processor to other processes, so that the server has an opportunity to receive and process the Apple event sent by your application. While your application is waiting for a reply, it cannot receive events unless it provides an idle function.If you provide a pointer to an idle function as a parameter to the AESend function, AESend calls your idle function whenever an update event, null event, operating-system event, or activate event is received for your application. To allow your application to process high-level events that it receives while waiting for a reply, provide a reply filter function. See the next section, “Writing a Reply Filter Function,” for more information.Your application can yield the processor in a similar manner when it calls the AEInteractWithUser function. If AEInteractWithUser needs to post a notification request to bring your application to the front, your application yields the processor until the user brings your application to the front. To receive events while waiting for the user to bring your application to the front, you must provide an idle function.If you provide a pointer to an idle function as a parameter to the AEInteractWithUser function, AEInteractWithUser calls your idle function whenever an update event, null event, operating-system event, or activate event is received for your application.An idle function must use this syntax:FUNCTION MyIdleFunction (VAR event: EventRecord;                                 VAR sleepTime: LongInt;                                 VAR mouseRgn: RgnHandle): Boolean;The event parameter is the event record of the event to process. The sleepTime parameter and mouseRgn parameter are values that your idle function sets the first time it is called; thereafter they contain the values your function set. Your idle function should return a Boolean value that indicates whether your application wishes to continue waiting. Set the function result to TRUE if your application is no longer willing to wait for a reply from the server or for the user to bring the application to the front. Set the function result to FALSE if your application is still willing to wait.You use the sleepTime and mouseRgn parameters in the same way as the sleep and mouseRgn parameters of the WaitNextEvent function. Specify in the sleepTime parameter the amount of time (in ticks) during which your application agrees to relinquish the processor if no events are pending for it. In the mouseRgn parameter, you specify a screen region that determines the conditions under which your application is to receive notice of mouse-moved events. Your idle function receives mouse-moved events only if your application is the front application and the cursor strays outside the region you specify.Your idle function receives only update events, null events, operating-system events, and activate events. When your idle function receives a null event, it can use the idle time to update a status dialog box, animate cursors, or perform similar tasks. If your idle function receives any of the other events, it should handle the event as it normally would if received in its event loop.Listing 5-5 shows an example of an idle function for use with AESend or AEInteractWithUser. The idle function processes update events, null events, operating-system events, and activate events. The first time the function is called it receives a null event. At this time, it sets the sleepTime and mouseRgn parameters. The function continues to process events until the server finishes handling the Apple event or the user brings the application to the front.Your application should implement a method of checking whether the user wants to cancel. The MyCancelInQueue function in Listing 5-5 checks the event queue for any instances of Command-period and immediately returns TRUE as its function result if it finds a request to cancel in the event queue.Listing 5-5    An idle functionFUNCTION MyIdleFunction (VAR event: EventRecord;                                  VAR sleeptime: LongInt;                                  VAR mouseRgn: RgnHandle): Boolean;BEGIN    MyIdleFunction := FALSE;    {the MyCancelInQueue function checks for Command-period}    IF MyCancelInQueue THEN        BEGIN                                        MyIdleFunction := TRUE;            Exit(MyIdleFunction);        END;    CASE event.what OF        updateEvt,        activateEvt,                    {every idle function should handle }        osEvt:                    { these kinds of events}            BEGIN                MyAdjustCursor(event.where, gCursorRgn);                    DoEvent(event);            END;        nullEvent:            BEGIN                {set the sleepTime and mouseRgn parameters}                mouseRgn := gCursorRgn;                sleeptime := 10;                        {use the correct value for your }                                        { app}                                            DoIdle;                        {the application's idle handling}            END;    END; {of CASE}END;Writing a Reply Filter FunctionIf your application calls AESend and chooses to yield the processor to other processes while waiting for a reply, you can provide an idle function to process update, null, operating-system, and activate events, and you can provide a reply filter function to process high-level events. The previous section describes how an idle function processes events.Your reply filter function can process any high-level events that it is willing to handle while waiting for a reply Apple event. For example, your application can choose to handle Apple events from other processes while waiting. Note, however, that your application must maintain any necessary state information. Your reply filter function must not accept any Apple events that can change the state of your application and make it impossible to return to its previous state.A reply filter function must use this syntax:FUNCTION MyReplyFilter (VAR event: EventRecord;                                   returnID: LongInt;                                 transactionID: LongInt;                                sender: AEAddressDesc): Boolean;The event parameter is the event record for a high-level event. The next three parameters contain valid information only if the event is an Apple event. The returnID parameter is the return ID for the Apple event. The transactionID parameter is the transaction ID for the Apple event. The sender parameter contains the address of the application or process that sent the Apple event.Your reply filter function should return TRUE as the function result if you want to accept the Apple event; otherwise, it should return FALSE. If your filter function returns TRUE, the Apple Event Manager calls the AEProcessAppleEvent function on behalf of your application, and your handler routine is called to process the Apple event. In this case, make sure your handler is not called while it is still being used by an earlier call.Reference to Creating and Sending Apple EventsThis section describes the basic Apple Event Manager routines that your application can use to create and send Apple events. It also describes application-defined idle functions and reply filter functions that your application can provide for use by the Apple Event Manager. For information about data structures used with the routines described in this chapter, see the section “Data Structures Used by the Apple Event Manager,” which begins on page 4-56. Routines for Creating and Sending Apple EventsThis section describes the Apple Event Manager routines you can use to create Apple events, create and duplicate descriptor records, create and add items to descriptor lists and AE records, add parameters and attributes to Apple events, and send Apple events. The section “Routines for Responding to Apple Events,” which begins on page 4-61, describes other Apple Event Manager routines used for both responding to and creating Apple events. Creating Apple EventsThe AECreateAppleEvent function allows you to create an Apple event. AECreateAppleEventYou can use the AECreateAppleEvent function to create an Apple event with several important attributes but no parameters. You add parameters to the Apple event after you create it.FUNCTION AECreateAppleEvent (theAEEventClass: AEEventClass;                                       theAEEventID: AEEventID;                                       target: AEAddressDesc;                                       returnID: Integer;                                       transactionID: LongInt;                                       VAR result: AppleEvent): OSErr;theAEEventClass The event class of the Apple event to be created.theAEEventID The event ID of the Apple event to be created.target     The address of the server application. returnID    The return ID for the Apple event; if you specify kAutoGenerateReturnID, the Apple Event Manager assigns a return ID that is unique to the current session.transactionIDThe transaction ID for this Apple event. A transaction is a sequence of Apple events that are sent back and forth between the client and server applications, beginning with the client’s initial request for a service. All Apple events that are part of a transaction must have the same transaction ID.result     The AECreateAppleEvent function returns, in this parameter, the Apple event that it creates.DESCRIPTIONThe AECreateAppleEvent function creates an Apple event.Your application is responsible for using the AEDisposeDesc function to dispose of the Apple event when you no longer need it.If AECreateAppleEvent returns a nonzero result code, it returns a null descriptor record unless the Apple Event Manager is not available because of limited memory. RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    SEE ALSOSee “Creating an Apple Event,” which begins on page 5-3, for more information on how to create an Apple event.See “Specifying a Target Address” on page 5-10 for information on how to address an Apple event. Creating and Duplicating Descriptor RecordsThe AECreateDesc function converts data into a descriptor record, and the AEDuplicateDesc function makes a copy of a descriptor record.AECreateDescYou can use the AECreateDesc function to convert data into a descriptor record.FUNCTION AECreateDesc (typeCode: DescType; dataPtr: Ptr;                               dataSize:             Size; VAR result: AEDesc): OSErr;typeCode    The descriptor type for the descriptor record.dataPtr    A pointer to the data for the descriptor record.dataSize     The length, in bytes, of the data for the descriptor record.result    The descriptor record that the AECreateDesc function creates. DESCRIPTIONThe AECreateDesc function creates a new descriptor record that incorporates the specified data. Your application is responsible for using the AEDisposeDesc function to dispose of the resulting descriptor record when you no longer need it. You normally do this after receiving a result code from the AESend function.If AECreateDesc returns a nonzero result code, it returns a null descriptor record unless the Apple Event Manager is not available because of limited memory. RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    SEE ALSOFor examples of the use of AECreateDesc, see “Adding Parameters to an Apple Event,” which begins on page 5-5, and Listing 5-2 on page 5-11.AEDuplicateDescYou can use the AEDuplicateDesc function to make a copy of a descriptor record.FUNCTION AEDuplicateDesc (theAEDesc: AEDesc;                                  VAR result: AEDesc): OSErr;theAEDesc     The descriptor record to be duplicated.result    The duplicate descriptor record. DESCRIPTIONThe AEDuplicateDesc function creates a new descriptor record by copying the descriptor record from the parameter theAEDesc. Your application is responsible for using the AEDisposeDesc function to dispose of the resulting descriptor record when you no longer need it. You normally do this after receiving a result code from the AESend function.If AEDuplicateDesc returns a nonzero result code, it returns a null descriptor record unless the Apple Event Manager is not available because of limited memory. It is common for applications to send Apple events that have one or more attributes or parameters in common. For example, if you send a series of Apple events to the same application, the address attribute is the same. In these cases, the most efficient way to create the necessary Apple events is to make a template Apple event that you can then copy—by calling the AEDuplicateDesc function—as needed. You then fill in or change the remaining parameters and attributes of the copy, send the copy by calling AESend, and dispose of the copy—by calling AEDisposeDesc—after AESend returns a result code.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    Creating Descriptor Lists and AE RecordsThe AECreateList function allows you to create an empty descriptor list or AE record.AECreateListYou can use the AECreateList function to create an empty descriptor list or AE record.FUNCTION AECreateList (factoringPtr: Ptr; factoredSize: Size;                              isRecord: Boolean;                               VAR resultList: AEDescList): OSErr;factoringPtr A pointer to the data at the beginning of each descriptor that is the same for all descriptor records in the list. If there is no common data, or if you decide not to isolate the common data, specify NIL as the value of this parameter.factoredSizeThe size of the common data. If there is no common data, or if you decide not to isolate the common data, the value of factoredSize must be 0. (See the description that follows for more information.)isRecord     A Boolean value that specifies the kind of list to create. If you set it to TRUE, the Apple Event Manager creates an AE record. If you set it to FALSE, the Apple Event Manager creates a descriptor list.resultListThe descriptor list or AE record that the AECreateList function creates. DESCRIPTIONThe AECreateList function creates an empty descriptor list or AE record. Your application is responsible for using the AEDisposeDesc function to dispose of the resulting descriptor record when you no longer need it. You normally do this after receiving a result code from the AESend function.If you intend to use a descriptor list for a factored Apple event array, you must provide, in the factoringPtr parameter, a pointer to the data shared by all items in the array and, in the factoredSize parameter, the size of the common data. The common data must be 4, 8, or more than 8 bytes in length because it always consists of (a) the descriptor type (4 bytes); (b) the descriptor type (4 bytes) and the size of each item’s data (4 bytes); or (c) the descriptor type (4 bytes), the size of each item’s data (4 bytes), and some portion of the data itself (1 or more bytes).If AECreateList returns a nonzero result code, it returns a null descriptor record unless the Apple Event Manager is not available because of limited memory. RESULT CODESnoErr    0    No error    paramErr    –50    Parameter error (value of handler pointer is NIL or odd)    memFullErr    –108    Not enough room in heap zone    SEE ALSOFor an example of the use of AECreateList, see Listing 5-1 on page 5-9.For information about data types used with Apple event arrays, see “Apple Event Array Data Types” on page 4-60.Adding Items to Descriptor ListsThe Apple Event Manager provides three routines that allow you to add descriptor records to any descriptor list, including an Apple event record. The AEPutPtr function converts data specified in a buffer to a descriptor record and adds the descriptor record to a descriptor list. The AEPutDesc function adds a descriptor record to a descriptor list. The AEPutArray function puts the data for an Apple event array into a descriptor list. AEPutPtrYou can use the AEPutPtr routine to add data specified in a buffer to any descriptor list as a descriptor record.FUNCTION AEPutPtr (theAEDescList: AEDescList; index: LongInt;                         typeCode: DescType; dataPtr: Ptr;                          dataSize: Size): OSErr;theAEDescListThe descriptor list to which to add a descriptor record.index     The position of the descriptor record in the descriptor list. (For example, the value 2 specifies the second descriptor record in the list.) If there is already a descriptor record in the specified position, it is replaced. If the value of index is 0, the descriptor record is added to the end of the list.typeCode    The descriptor type for the resulting descriptor record.dataPtr     A pointer to the data for the descriptor record.dataSize    The length, in bytes, of the data for the descriptor record.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    errAEIllegalIndex    –1719    Not a valid list index    SEE ALSOFor an example of the use of AEPutPtr, see Listing 5-1 on page 5-9.AEPutDescYou can use the AEPutDesc function to add a descriptor record to any descriptor list.FUNCTION AEPutDesc (theAEDescList: AEDescList; index: LongInt;                           theAEDesc: AEDesc): OSErr;theAEDescListThe descriptor list to which to add a descriptor record.index     The position of the descriptor record in the descriptor list. (For example, the value 2 specifies the second descriptor record in the list.) If there is already a descriptor record in the specified position, it is replaced. If the value of index is 0, the descriptor record is added to the end of the list.theAEDesc     The descriptor record to be added to the list.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    errAEIllegalIndex    –1719    Not a valid list index    AEPutArrayYou can use the AEPutArray function to put the data for an Apple event array into any descriptor list.FUNCTION AEPutArray (theAEDescList: AEDescList;                             arrayType: AEArrayType;                              arrayPtr: AEArrayDataPointer;                             itemType: DescType;                              itemSize: Size; itemCount: LongInt): OSErr;theAEDescListThe descriptor list into which to put the Apple event array. If there are any items already in the descriptor list, they are replaced.arrayType    The Apple event array type to be created. This is specified by one of the following constants: kAEDataArray, kAEPackedArray, kAEHandleArray, kAEDescArray, or kAEKeyDescArray. arrayPtr     A pointer to the buffer containing the array.itemType     For arrays of type kAEDataArray, kAEPackedArray, or kAEHandleArray, the descriptor type of array items to be created. itemSize     For arrays of type kAEDataArray or kAEPackedArray, the size (in bytes) of the array items to be created.itemCount     The number of elements in the array.DESCRIPTIONWhen you use AEPutArray to put an array into a factored descriptor list, each array item must include the data that is common to all the descriptor records in the list. The Apple Event Manager automatically isolates the data you specified in the call to AECreateList that is common to all the elements of the array.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    SEE ALSOFor information about data types and constants used with AEPutArray, see “Apple Event Array Data Types” on page 4-60.For more information about creating descriptor lists for Apple event arrays, see the description of AECreateList on page 5-28. Adding Data and Descriptor Records to AE RecordsThe Apple Event Manager provides two routines that allow you to add data and descriptor records to AE records. The AEPutKeyPtr function takes a pointer to data, a descriptor type, and a keyword and converts them into a keyword-specified descriptor record that it adds to an AE record. The AEPutKeyDesc function takes a descriptor record and a keyword and converts them into a keyword-specified descriptor record that it adds to an AE record.   AEPutKeyPtrYou can use the AEPutKeyPtr function to add a pointer to data, a descriptor type, and a keyword to an AE record as a keyword-specified descriptor record. FUNCTION AEPutKeyPtr (theAERecord: AERecord;                              theAEKeyword: AEKeyword;                              typeCode: DescType; dataPtr: Ptr;                              dataSize: Size): OSErr;theAERecordThe AE record to which to add a keyword-specified descriptor record.theAEKeywordThe keyword that identifies the descriptor record. If the AE record already includes a descriptor record with this keyword, it is replaced.typeCode     The descriptor type for the keyword-specified descriptor record.dataPtr     A pointer to the data for the keyword-specified descriptor record.dataSize     The length, in bytes, of the data for the keyword-specified descriptor record.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    AEPutKeyDescYou can use the AEPutKeyDesc function to add a descriptor record and a keyword to an AE record as a keyword-specified descriptor record. FUNCTION AEPutKeyDesc (theAERecord: AERecord;                               theAEKeyword: AEKeyword;                               theAEDesc: AEDesc): OSErr;theAERecord The AE record to which to add the keyword-specified descriptor record.theAEKeyword The keyword specifying the descriptor record. If there was already a keyword-specified descriptor record with this keyword, it is replaced.theAEDesc     The descriptor record for the keyword-specified descriptor record.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    Adding Parameters and Attributes to Apple EventsThe Apple Event Manager provides four functions that allow you to add Apple event parameters and attributes to an Apple event. The AEPutParamPtr and AEPutParamDesc functions add parameters to a specified Apple event. The AEPutAttributePtr and AEPutAttributeDesc functions add attributes to a specified Apple event.AEPutParamPtrYou can use the AEPutParamPtr function to add a pointer to data, a descriptor type, and a keyword to an Apple event as an Apple event parameter.FUNCTION AEPutParamPtr (theAppleEvent: AppleEvent;                                 theAEKeyword: AEKeyword;                                 typeCode: DescType; dataPtr: Ptr;                                 dataSize: Size): OSErr;theAppleEventThe Apple event to which to add a parameter.theAEKeywordThe keyword for the parameter to be added. If the Apple event already included a parameter with this keyword, the parameter is replaced.typeCode    The descriptor type for the parameter.dataPtr    A pointer to the data for the parameter.dataSize    The length, in bytes, of the data for the parameter.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    SEE ALSOFor an example of the use of AEPutParamPtr, see “Adding Parameters to an Apple Event,” which begins on page 5-5.AEPutParamDescYou can use the AEPutParamDesc function to add a descriptor record and a keyword to an Apple event as an Apple event parameter.FUNCTION AEPutParamDesc (theAppleEvent: AppleEvent;                                  theAEKeyword: AEKeyword;                                  theAEDesc: AEDesc): OSErr;theAppleEventThe Apple event to which to add a parameter.theAEKeywordThe keyword for the parameter to be added. If the Apple event already included a parameter with this keyword, the parameter is replaced.theAEDesc     The descriptor record for the parameter.RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    SEE ALSOFor an example of the use of AEPutParamDesc, see “Adding Parameters to an Apple Event,” which begins on page 5-5.AEPutAttributePtrYou can use the AEPutAttributePtr function to add a pointer to data, a descriptor type, and a keyword to an Apple event as an attribute.FUNCTION AEPutAttributePtr (theAppleEvent: AppleEvent;                                     theAEKeyword: AEKeyword;                                      typeCode: DescType;                                      dataPtr: Ptr; dataSize: Size): OSErr;theAppleEvent The Apple event to which to add an attribute.theAEKeywordThe keyword for the attribute to be added.     TYPE AEKeyword = PACKED ARRAY[1..4] OF Char;    The keyword can be any of the constants listed in the description that follows. If the Apple event already included an attribute with this keyword, the attribute is replaced. typeCode    The descriptor type for the attribute.dataPtr     A pointer to the buffer containing the data to be assigned to the attribute.dataSize    The length, in bytes, of the data to be assigned to the attribute.DESCRIPTIONThe AEPutAttributePtr function adds the specified pointer to data, descriptor type, and keyword to the specified Apple event as an attribute. You can specify the parameter theAEKeyWord using any of the following constants:CONST    keyAddressAttr                                 = 'addr'; {address of target }                                                 { application}    keyEventClassAttr                                 = 'evcl'; {event class}    keyEventIDAttr                                = 'evid'; {event ID}    keyEventSourceAttr                                = 'esrc'; {source application}    keyInteractLevelAttr                                = 'inte'; {settings to allow the }                                                 { Apple Event Manager to }                                                 { bring server application }                                                 { to the foreground}    keyMissedKeywordAttr                                = 'miss'; {first required parameter }                                                 { remaining in Apple event}    keyOptionalKeywordAttr                                = 'optk'; {list of optional }                                                 { parameters for Apple }                                                 { event}    keyOriginalAddressAttr                                = 'from';             {address of original source }                                                 { of Apple event}         keyReturnIDAttr                                 = 'rtid'; {return ID for reply Apple }                                                 { event}    keyTimeoutAttr                                = 'timo'; {length of time in ticks }                                                 { that client will wait }                                                 { for reply or result from }                                                  { the server}    keyTransactionIDAttr                                = 'tran'; {transaction ID identifying }                                                 { a series of Apple events}RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAECoercionFail    –1700    Data could not be coerced to the requested descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    AEPutAttributeDescYou can use the AEPutAttributeDesc function to add a descriptor record and a keyword to an Apple event as an attribute.FUNCTION AEPutAttributeDesc (theAppleEvent: AppleEvent;                                      theAEKeyword: AEKeyword;                                       theAEDesc: AEDesc): OSErr;theAppleEventThe Apple event to which you are adding an attribute.theAEKeywordThe keyword for the attribute to be added.     TYPE AEKeyword = PACKED ARRAY[1..4] OF Char;    The keyword can be any of the constants listed in the description of AEPutAttributePtr on page 5-35. If the Apple event already included an attribute with this keyword, the attribute is replaced. theAEDesc    The descriptor record to be assigned to the attribute. The descriptor type of the specified descriptor record should match the defined descriptor type for that attribute. For example, the keyEventSourceAttr attribute has the typeShortInteger descriptor type.DESCRIPTIONThe AEPutAttributeDesc function takes a descriptor record and a keyword and adds them to an Apple event as an attribute. If the descriptor type required for the attribute is different from the descriptor type of the descriptor record, the Apple Event Manager attempts to coerce the descriptor record into the required type, with one exception: the Apple Event Manager does not attempt to coerce the data for an address attribute, thereby allowing applications to use their own address types. RESULT CODESnoErr    0    No error    memFullErr    –108    Not enough room in heap zone    errAECoercionFail    –1700    Data could not be coerced to the requested descriptor type     errAENotAEDesc    –1704    Not a valid descriptor record    SEE ALSOFor an example of the use of AEPutAttributeDesc, see Listing 5-1 on page 5-9. Sending Apple EventsThe AESend function allows you to send an Apple event that you have previously created with the AECreateAppleEvent function.  AESendYou can use the AESend function to send an Apple event.FUNCTION AESend (theAppleEvent: AppleEvent;                       VAR reply: AppleEvent; sendMode: AESendMode;                       sendPriority: AESendPriority;                       timeOutInTicks: LongInt; idleProc: IdleProcPtr;                       filterProc: EventFilterProcPtr): OSErr;theAppleEvent The Apple event to be sent.reply     The reply Apple event returned by the AESend function if you specify the kAEWaitReply flag in the sendMode parameter. (If you specify the kAEQueueReply flag in the sendMode parameter, you receive the reply Apple event in your event queue.) If you specify kAENoReply flag, the reply Apple event returned by this function is a null descriptor record. If you specify kAEWaitReply in the sendMode parameter, your application is responsible for using the AEDisposeDesc function to dispose of the descriptor record returned in the reply parameter.sendMode    Specifies the following: the reply mode for the Apple event (set with one of the constants kAENoReply, kAEQueueReply, or kAEWaitReply); the interaction level (set with one of the constants kAENeverInteract, kAECanInteract, or kAEAlwaysInteract, which represent flags in the keyInteractLevelAttr attribute); the application switch mode (set with the kAECanSwitchLayer constant); the reconnection mode (set with the kAEDontReconnect constant); and the return receipt mode (set with the kAEWantReceipt constant). You obtain the value for this parameter by adding the appropriate constants. (The description that follows provides more details about the sendMode flags.)sendPriority An integer of data type AESendPriority that specifies whether the Apple event is put at the back of the event queue (indicated by the kAENormalPriority flag) or at the front of the queue (indicated by the kAEHighPriority flag).  timeOutInTicks If the reply mode specified in the sendMode parameter is kAEWaitReply, or if a return receipt is requested, this parameter specifies the length of time (in ticks) that the client application is willing to wait for the reply or return receipt from the server application before timing out. Most applications should use the kAEDefaultTimeout constant, which tells the Apple Event Manager to provide an appropriate timeout duration. If the value of this parameter is kNoTimeOut, the Apple event never times out.idleProc     A pointer to a function that handles events (such as update, operating-system, activate, and null events) that your application receives while waiting for a reply. Your application can also perform other tasks (such as displaying a wristwatch or spinning beachball cursor) while waiting for a reply or a return receipt. Your application must provide an idle function if it specifies the kAEWaitReply flag in the sendMode parameter.filterProcA pointer to a function that accepts certain incoming Apple events that are received while the handler waits for a reply or a return receipt and filters out the rest.DESCRIPTIONYou can use one of the following flags in the sendMode parameter to specify the reply mode for an Apple event. Only one of these flags may be set.Flag    Description    kAENoReply    Your application does not want a reply Apple event; the server processes your Apple event as soon as it has the opportunity.    kAEQueueReply    Your application wants a reply Apple event; the reply appears in your event queue as soon as the server has the opportunity to process and respond to your Apple event.    kAEWaitReply    Your application wants a reply Apple event and is willing to give up the processor while waiting for the reply; for example, if the server application is on the same computer as your application, your application yields the processor to allow the server to respond to your Apple event. If you specify kAEWaitReply, you should provide an idle function.     You can communicate your user interaction preferences to the server application by specifying one of the following flags in the sendMode parameter. Only one of these flags may be set.Flag    Description    kAENeverInteract    The server application should never interact with the user in response to the Apple event. If this flag is set, AEInteractWithUser returns the errAENoUserInteraction result code. This flag is the default when an Apple event is sent to a remote application.    kAECanInteract    The server application can interact with the user in response to the Apple event—by convention, if the user needs to supply information to the server. If this flag is set and the server allows interaction, AEInteractWithUser either brings the server application to the foreground or posts a notification request. This flag is the default when an Apple event is sent to a local application.    kAEAlwaysInteract    The server application can interact with the user in response to the Apple event—by convention, whenever the server application normally asks a user to confirm a decision or interact in any other way, even if no additional information is needed from the user. If this flag is set and the server allows interaction, AEInteractWithUser either brings the server application to the foreground or posts a notification request.    The flags in the following list specify the application switch mode, the reconnection mode, and the return receipt mode. Any of these flags may be set.Flag    Description    kAECanSwitchLayer    If both the client and server allow interaction, and if the client application is the active application on the local computer and is waiting for a reply (that is, it has set the kAEWaitReply flag), AEInteractWithUser brings the server directly to the foreground. Otherwise, AEInteractWithUser uses the Notification Manager to request that the user bring the server application to the foreground.    kAEDontReconnect    The Apple Event Manager must not automatically try to reconnect if it receives a sessClosedErr result code from the PPC Toolbox.    kAEWantReceipt    The sender wants to receive a return receipt for this Apple event from the Event Manager. (A return receipt means only that the receiving application accepted the Apple event; the Apple event may or may not be handled successfully after it is accepted.) If the receiving application does not send a return receipt before the request times out, AESend returns errAETimeout as its function result.    If the Apple Event Manager cannot find a handler for an Apple event in either the application or system Apple event dispatch table, it returns the result code errAEEventNotHandled to the server application (as the result of the AEProcessAppleEvent function). If the client application is waiting for a reply, the Apple Event Manager also returns this result code to the client.The AESend function returns noErr as its function result if the Apple event was successfully sent by the Event Manager. A noErr result from AESend does not indicate that the Apple event was handled successfully; it indicates only that the Apple event was successfully sent by the Event Manager. If the handler returns a result code other than noErr, and if the client is waiting for a reply, it is returned in the keyErrorNumber parameter of the reply Apple event.If your application is sending an event to itself, you can set one of these flags to prevent the event from being recorded or to ask the Apple Event Manager to record the event without your application actually receiving it. Only one of these flags may be set.Flag    Description    kAEDontRecord    Your application is sending an event to itself but does not want the event recorded. When Apple event recording is on, the Apple Event Manager records a copy of every event your application sends to itself except for those events for which this flag is set.     kAEDontExecute    Your application is sending an Apple event to itself for recording purposes only—that is, you want the Apple Event Manager to send a copy of the event to the recording process but you do not want your application actually to receive the event.     RESULT CODESnoErr    0    No error    eLenErr    –92    Buffer too big to send    memFullErr    –108    Not enough room in heap zone    userCanceledErr    –128    User canceled an operation    procNotFound    –600    No eligible process with specified process serial number    connectionInvalid    –609    Nonexistent signature or session ID    noUserInteractionAllowed    –610    Background application sends event requiring authentication    noPortErr    –903    Client hasn’t set 'SIZE' resource to indicate awareness of high-level events    destPortErr    –906    Server hasn’t set 'SIZE' resource to indicate awareness of high-level events, or else is not present    sessClosedErr    –917    The kAEDontReconnect flag in the sendMode parameter was set and the server quit, then restarted    errAEEventNotHandled    –1708    Event wasn’t handled by an Apple event handler    errAEUnknownSendMode    –1710    Invalid sending mode was passed    errAEWaitCanceled    –1711    User canceled out of wait loop for reply or receipt    errAETimeout    –1712    Apple event timed out    errAEUnknownAddressType    –1716    Unknown Apple event address type    SEE ALSOFor more information on sending Apple events, see “Sending an Apple Event,” which begins on page 5-13.For information on writing an idle function, see “Writing an Idle Function,” which begins on page 5-21.For information on writing a reply filter function, see “Writing a Reply Filter Function,” which begins on page 5-24. For information on when to use the kAEDontExecute flag, see the chapter “Recording Apple Events” in this book.Application-Defined RoutinesIf your application sends an Apple event using AESend and is waiting for a reply, or if it calls AEInteractWithUser, you can provide an idle function to handle update events, null events, operating-system events, and activate events. You can also provide a reply filter function that can handle any high-level events that you want your application to handle while it is waiting for a reply or for user interaction.MyIdleFunctionAn idle function has the following syntax:FUNCTION MyIdleFunction (VAR event: EventRecord;                                 VAR sleepTime:         LongInt;                                 VAR mouseRgn: RgnHandle): Boolean;event    The event record of the event to process.sleepTime    Amount of time (in ticks) during which your application agrees to relinquish the processor if no events are pending.mouseRgn    A screen region that determines the conditions under which your application is to receive notice of mouse-moved events. DESCRIPTIONIf your application provides a pointer to an idle function (MyIdleFunction) as a parameter to AESend or AEInteractWithUser, the Apple Event Manager will call the idle function to handle any update event, null event, operating-system event, or activate event received for your application while it is waiting for a reply.Set the function result to TRUE if your application is no longer willing to wait for a reply from the server or for the user to bring the application to the front. Set the function result to FALSE if your application is still willing to wait.SEE ALSOFor more information, see “Writing an Idle Function,” which begins on page 5-21.MyReplyFilterA reply filter function has the following syntax: FUNCTION MyReplyFilter (VAR event: EventRecord;                                returnID: LongInt;                                 transactionID: LongInt;                                sender: AEAddressDesc): Boolean;event    The event record for a high-level event. The next three parameters contain valid information only if the event is an Apple event.returnID    Return ID for the Apple event.transactionIDTransaction ID for the Apple event.sender    Address of process that sent the Apple event.DESCRIPTIONIf your application provides a pointer to a reply filter function as a parameter to the AESend function, the reply filter function can process any high-level events that it is willing to handle while your application is waiting for a reply. Your reply filter function should return TRUE as the function result if you want to accept the Apple event; otherwise, it should return FALSE.SEE ALSOFor more information, see “Writing a Reply Filter Function” on page 5-24. Summary of Creating and Sending Apple EventsPascal SummaryConstantsCONST            gestaltAppleEventsAttr                                    = 'evnt';                {selector for Apple events}    gestaltAppleEventsPresent                                    = 0;                {if this bit is set, then Apple }                                                        { Event Manager is available}    {Apple event descriptor types}    typeBoolean                                = 'bool';                    {1-byte Boolean value}    typeChar                                = 'TEXT';                    {unterminated string}    typeSMInt                                = 'shor';                    {16-bit integer}    typeInteger                                = 'long';                    {32-bit integer}    typeSMFloat                                = 'sing';                    {SANE single}    typeFloat                                = 'doub';                    {SANE double}    typeLongInteger                                = 'long';                    {32-bit integer}    typeShortInteger                                = 'shor';                    {16-bit integer}    typeLongFloat                                = 'doub';                    {SANE double}    typeShortFloat                                = 'sing';                    {SANE single}    typeExtended                                = 'exte';                    {SANE extended}    typeComp                                = 'comp';                    {SANE comp}    typeMagnitude                                = 'magn';                    {unsigned 32-bit integer}    typeAEList                                = 'list';                    {list of descriptor records}    typeAERecord                                = 'reco';                    {list of keyword-specified }                                                        { descriptor records}    typeAppleEvent                                = 'aevt';                    {Apple event record}    typeTrue                                = 'true';                    {TRUE Boolean value}    typeFalse                                = 'fals';                    {FALSE Boolean value}    typeAlias                                = 'alis';                    {alias record}    typeEnumerated                                = 'enum';                    {enumerated data}    typeType                                = 'type';                    {four-character code for }                                                        { event class or event ID}    typeAppParameters                                = 'appa';                    {Process Manager launch parameters}    typeProperty                                = 'prop';                    {Apple event property}    typeFSS                                = 'fss ';                    {file system specification}    typeKeyword                                = 'keyw';                    {Apple event keyword}    typeSectionH                                = 'sect';                    {handle to a section record}    typeWildCard                                = '****';                    {matches any type}    typeApplSignature                                = 'sign';                    {application signature}    typeSessionID                                = 'ssid';                    {session reference number}    typeTargetID                                = 'targ';                    {target ID record}    typeProcessSerialNumber                                = 'psn ';                    {process serial number}    typeNull                                = 'null';                    {NULL or nonexistent data}        {keywords for Apple event parameters}    keyDirectObject                                = '----';                    {direct parameter}    keyErrorNumber                                = 'errn';                    {error number parameter}    keyErrorString                                = 'errs';                    {error string parameter}    keyProcessSerialNumber                                = 'psn ';                    {process serial number param}    {keywords for Apple event attributes}    keyTransactionIDAttr                                = 'tran';                    {transaction ID}    keyReturnIDAttr                                = 'rtid';                    {return ID}    keyEventClassAttr                                 = 'evcl';                    {event class}    keyEventIDAttr                                = 'evid';                    {event ID}    keyAddressAttr                                = 'addr';                    {address of target or }                                                        { client application}    keyOptionalKeywordAttr                                = 'optk';                    {list of optional parameters }                                                        { for the Apple event}    keyTimeoutAttr                                = 'timo';                    {number of ticks the client }                                                        { will wait}    keyInteractLevelAttr                                 = 'inte';                    {settings to allow Apple Event }                                                        { Manager to bring server }                                                                            { to foreground}    keyEventSourceAttr                                = 'esrc';                    {nature of source }                                                        { application}    keyMissedKeywordAttr                                = 'miss';                    {first required parameter }                                                        { remaining in an Apple event}    keyOriginalAddressAttr                                = 'from';                    {address of original source; }                                                        { available only in version }                                                         { 1.01 and later versions of }                                                        { the Apple Event Manager}    {keywords for special handlers}    keyPreDispatch                                = 'phac';                    {identifies a handler routine }                                                        { called immediately before the }                                                        { Apple Event Manager dispatches }                                                        { an Apple event}    keySelectProc                                = 'selh';                     {selector used with }                                                        { AERemoveSpecialHandler to }                                                        { disable the OSL}    {keywords for use with AEManagerInfo; available only in version }    { 1.0.1 and later versions of the Apple Event Manager}    keyAERecorderCount                                 = 'recr';                    {keyword for recording info}    keyAEVersion                                 = 'vers';                    {keyword for version info}    {event class}    kCoreEventClass                                = 'aevt';                    {event class for required Apple }                                                        { events}    {event IDs for required Apple events}    kAEOpenApplication                                = 'oapp';                    {event ID for Open }                                                        { Application event}    kAEOpenDocuments                                = 'odoc';                    {event ID for Open Documents event}    kAEPrintDocuments                                = 'pdoc';                    {event ID for Print Documents }                                                        { event}    kAEQuitApplication                                = 'quit';                    {event ID for Quit Application }                                                        { event}    kAEAnswer                                = 'ansr';                    {event ID for Apple event replies}    kAEApplicationDied                                = 'obit';                    {event ID for Application Died }                                                        { event}    {constants for setting the sendMode parameter of AESend}    kAENoReply                                = $00000001;                    {client doesn't want reply}    kAEQueueReply                                = $00000002;                    {client wants server to }                                                        { reply in event queue}    kAEWaitReply                                = $00000003;                    {client wants a reply and }                                                        { will give up processor}    kAENeverInteract                                = $00000010;                    {server application should }                                                        { not interact with user }                                                        { for this Apple event}    kAECanInteract                                = $00000020;                    {server may interact with }                                                        { user for this Apple event }                                                        { to supply information}    kAEAlwaysInteract                                = $00000030;                    {server may interact with user }                                                        { for this Apple event even if }                                                        { no information is required}    kAECanSwitchLayer                                = $00000040;                    {server should come directly }                                                        { to foreground when appropriate}    kAEDontReconnect                                = $00000080;                    {don't reconnect if there }                                                        { is a PPC session closed error}    kAEWantReceipt                                = nReturnReceipt; {client wants return }                                                        { receipt}    kAEDontRecord                                = $00001000            ;        {don't record this event}    kAEDontExecute                                = $00002000;                    {don't excecute this event}    {constants for setting the sendPriority parameter of AESend}    kAENormalPriority                                = $00000000;                    {put event at back of }                                                        { event queue}    kAEHighPriority                                = nAttnMsg;                    {put event at front of }                                                        { the event queue}    {event IDs for recording events; available only in version 1.01 and }    { later versions of the Apple Event Manager}    kAEStartRecording                                = 'reca';                    {event ID for Start Recording }                                                        { event}    kAEStopRecording                                = 'recc';                    {event ID for Stop Recording }                                                        { event}    kAENotifyStartRecording                                = 'rec1';                    {event ID for Recording On event}    kAENotifyStopRecording                                = 'rec0';                    {event ID for Recording Off event}    kAENotifyRecording                                = 'recr';                    {event ID for Receive Recordable }                                                        { Event event}    {constant for the returnID parameter of AECreateAppleEvent}    kAutoGenerateReturnID                                = -1;                    {tells Apple Event Manager to }                                                        { generate a unique return ID}    {constant for transaction IDs}    kAnyTransactionID                                 = 0;                    {the Apple event is not }                                                        { part of a transaction}    {constants for timeout durations}    kAEDefaultTimeout                                = -1;                    {use default timeout value}    kNoTimeOut                                = -2;                    {never time out}    {constants for the dispatcher parameter of AEResumeTheCurrentEvent}    kAENoDispatch                                = 0;                    {don't redispatch the Apple event}    kAEUseStandardDispatch                                = -1;                    {redispatch the Apple event }                                                        { by using its entry in the }                                                        { Apple event dispatch table}Data TypesTYPE    AEEventClass =         PACKED ARRAY[1..4] OF Char;                                                    {event class for a high-level }                                                            { event}    AEEventID =         PACKED ARRAY[1..4] OF Char;                                                    {event ID for a high-level }                                                            { event}    AEKeyword =         PACKED ARRAY[1..4] OF Char;                                                    {keyword for a descriptor }                                                            { record}    DescType                                    = ResType;                    {descriptor type}    AEDesc =                                                         {descriptor record}    RECORD                descriptorType:                                 DescType;                    {type of data being passed}        dataHandle:                                 Handle;                    {handle to data being passed}    END;    AEKeyDesc =                                                         {keyword-specified }    RECORD                                                        { descriptor record}        descKey:                                AEKeyword;                    {keyword}        descContent:                                AEDesc    ;                {descriptor record}    END;    AEAddressDesc                                    = AEDesc;                    {address descriptor record}    AEDescList                                    = AEDesc;                    {list of descriptor records}    AERecord                                    = AEDescList;                    {list of keyword-specified }                                                            { descriptor records}    AppleEvent                                    = AERecord;                    {list of attributes and }                                                            { parameters necessary for }                                                            { an Apple event}    AESendMode                                    = LongInt;                    {flags that determine how }                                                            { an Apple event is sent}    AESendPriority                                    = Integer;                    {send priority of an Apple }                                                            { event}    AEInteractAllowed = (kAEInteractWithSelf, kAEInteractWithLocal,                                 kAEInteractWithAll);                            {what processes may }                                                            { interact with the user}    AEEventSource = (kAEUnknownSource, kAEDirectCall, kAESameProcess,                          kAELocalProcess, kAERemoteProcess);                                                            {the source of an Apple }                                                            { event}    AEArrayType = (kAEDataArray, kAEPackedArray, kAEHandleArray,                        kAEDescArray, kAEKeyDescArray);                                                            {type of an Apple event array}    AEArrayData =     RECORD                                                        {data for an Apple event array}        CASE AEArrayType OF        kAEDataArray:            (AEDataArray:     ARRAY[0..0] OF Integer);        kAEPackedArray:            (AEPackedArray:     Packed Array[0..0] OF Char);        kAEHandleArray:            (AEHandleArray:     Array[0..0] OF Handle);        kAEDescArray:            (AEDescArray:     Array[0..0] OF AEDesc);        kAEKeyDescArray:            (AEKeyDescArray:     Array[0..0] OF AEKeyDesc);    END;        AEArrayDataPointer = ^AEArrayData;    EventHandlerProcPtr = ProcPtr;                                                        {pointer to an Apple event }                                                            { handler}    IdleProcPtr = ProcPtr;                                                        {pointer to an application's }                                                            { idle function}    EventFilterProcPtr = ProcPtr;                                                        {pointer to an application's }                                                            { filter function}Routines for Creating and Sending Apple EventsCreating Apple EventsFUNCTION AECreateAppleEvent    (theAEEventClass: AEEventClass; theAEEventID: AEEventID; target: AEAddressDesc; returnID: Integer; transactionID: LongInt; VAR result: AppleEvent): OSErr;Creating and Duplicating Descriptor RecordsFUNCTION AECreateDesc    (typeCode: DescType; dataPtr: Ptr; dataSize: Size; VAR result: AEDesc): OSErr;FUNCTION AEDuplicateDesc    (theAEDesc: AEDesc; VAR result: AEDesc): OSErr;Creating Descriptor Lists and AE RecordsFUNCTION AECreateList    (factoringPtr: Ptr; factoredSize: Size; isRecord: Boolean; VAR resultList: AEDescList): OSErr;Adding Items to Descriptor ListsFUNCTION AEPutPtr    (theAEDescList: AEDescList; index: LongInt; typeCode: DescType; dataPtr: Ptr; dataSize: Size): OSErr;FUNCTION AEPutDesc    (theAEDescList: AEDescList; index: LongInt; theAEDesc: AEDesc): OSErr;FUNCTION AEPutArray    (theAEDescList: AEDescList; arrayType: AEArrayType; arrayPtr: AEArrayDataPointer; itemType: DescType; itemSize: Size; itemCount: LongInt): OSErr;Adding Data and Descriptor Records to AE RecordsFUNCTION AEPutKeyPtr    (theAERecord: AERecord; theAEKeyword: AEKeyword; typeCode: DescType; dataPtr: Ptr; dataSize: Size): OSErr;FUNCTION AEPutKeyDesc    (theAERecord: AERecord; theAEKeyword: AEKeyword; theAEDesc: AEDesc): OSErr;Adding Parameters and Attributes to Apple EventsFUNCTION AEPutParamPtr    (theAppleEvent: AppleEvent; theAEKeyword: AEKeyword; typeCode: DescType; dataPtr: Ptr; dataSize: Size): OSErr;FUNCTION AEPutParamDesc    (theAppleEvent: AppleEvent; theAEKeyword: AEKeyword; theAEDesc: AEDesc): OSErr;FUNCTION AEPutAttributePtr    (theAppleEvent: AppleEvent; theAEKeyword: AEKeyword; typeCode: DescType; dataPtr: Ptr; dataSize: Size): OSErr;FUNCTION AEPutAttributeDesc    (theAppleEvent: AppleEvent; theAEKeyword: AEKeyword; theAEDesc: AEDesc): OSErr;Sending Apple EventsFUNCTION AESend    (theAppleEvent: AppleEvent; VAR reply: AppleEvent; sendMode: AESendMode; sendPriority: AESendPriority; timeOutInTicks: LongInt; idleProc: IdleProcPtr; filterProc: EventFilterProcPtr): OSErr;Application-Defined RoutinesFUNCTION MyIdleFunction    (VAR event: EventRecord;VAR sleepTime: LongInt; VAR mouseRgn: RgnHandle): Boolean;FUNCTION MyReplyFilter    (VAR event: EventRecord; returnID: LongInt; transactionID: LongInt; sender: AEAddressDesc): Boolean;C SummaryConstantsenum {        #define         gestaltAppleEventsAttr                                      'evnt'            /*selector for Apple events*/        gestaltAppleEventsPresent                                             = 0        /*if this bit is set, then */                                                            /* Apple Event Manager is */};                                                            /* available*/        /*Apple event descriptor types*/enum        {        typeBoolean                                = 'bool',                    /*1-byte Boolean value*/        typeChar                                = 'TEXT',                    /*unterminated string*/        typeSMInt                                = 'shor',                    /*16-bit integer*/        typeInteger                                = 'long',                    /*32-bit integer*/        typeSMFloat                                = 'sing',                    /*SANE single*/        typeFloat                                = 'doub',                    /*SANE double*/        typeLongInteger                                = 'long',                    /*32-bit integer*/        typeShortInteger                                = 'shor',                    /*16-bit integer*/        typeLongFloat                                = 'doub',                    /*SANE double*/        typeShortFloat                                = 'sing',                    /*SANE single*/        typeExtended                                = 'exte',                    /*SANE extended*/        typeComp                                = 'comp',                    /*SANE comp*/        typeMagnitude                                = 'magn',                    /*unsigned 32-bit integer*/        typeAEList                                = 'list',                    /*list of descriptor records*/        typeAERecord                                = 'reco',                    /*list of keyword-specified */                                                            /* descriptor records*/        typeAppleEvent                                = 'aevt',                    /*Apple event record*/        typeTrue                                = 'true',                    /*TRUE Boolean value*/        typeFalse                                = 'fals',                    /*FALSE Boolean value*/        typeAlias                                = 'alis',                    /*alias record*/        typeEnumerated                                = 'enum'                    /*enumerated data*/};enum {        typeType                                = 'type',                    /*four-character code for */                                                            /* event class or event ID*/        typeAppParameters                                = 'appa',                    /*Process Manager launch */                                                            /* parameters*/        typeProperty                                = 'prop',                    /*Apple event property*/        typeFSS                                = 'fss ',                    /*file system specification*/        typeKeyword                                = 'keyw',                    /*Apple event keyword*/        typeSectionH                                = 'sect',                    /*handle to a section record*/        typeWildCard                                = '****',                    /*matches any type*/        typeApplSignature                                = 'sign',                    /*application signature*/        typeSessionID                                = 'ssid',                    /*session ID*/        typeTargetID                                = 'targ',                    /*target ID record*/        typeProcessSerialNumber                                = 'psn ',                    /*process serial number*/        typeNull                                = 'null'                    /*NULL or nonexistent data*/};        /*keywords for Apple event parameters*/enum     {        keyDirectObject                                = '----',                    /*direct parameter*/        keyErrorNumber                                = 'errn',                    /*error number parameter*/        keyErrorString                                = 'errs',                    /*error string parameter*/        keyProcessSerialNumber                                = 'psn '                    /*process serial number param*/};        /*keywords for Apple event attributes*/enum     {        keyTransactionIDAttr                                = 'tran',                    /*transaction ID*/        keyReturnIDAttr                                = 'rtid',                    /*return ID*/        keyEventClassAttr                                 = 'evcl',                    /*event class*/        keyEventIDAttr                                = 'evid',                    /*event ID*/        keyAddressAttr                                = 'addr',                    /*address of target or */                                                            /* client application*/        keyOptionalKeywordAttr                                = 'optk',                    /*list of optional parameters */                                                            /* for the Apple event*/        keyTimeoutAttr                                = 'timo',                    /*number of ticks the client */                                                            /* will wait*/        keyInteractLevelAttr                                 = 'inte',                    /*settings to allow Apple */                                                            /* Event Mgr to bring */                                                                                /* server to foreground*/        keyEventSourceAttr                                = 'esrc',                    /*nature of source */                                                            /* application*/        keyMissedKeywordAttr                                = 'miss',                    /*first required parameter */                                                            /* remaining in an Apple */                                                            /* event*/        keyOriginalAddressAttr                                = 'from'                    /*address of original source; */                                                            /* available only in version */                                                             /* 1.01 and later versions of */                                                            /* the Apple Event Manager*/};                /*keywords for special handlers*/enum     {        keyPreDispatch                                = 'phac',                    /*identifies a handler */                                                            /* routine that is called */                                                            /* immediately before the */                                                            /* Apple Event Manager */                                                            /* dispatches an Apple event*/        keySelectProc                                = 'selh',                     /*selector used with */                                                            /* AERemoveSpecialHandler to */                                                            /* disable the OSL*/        /*keywords for use with AEManagerInfo, available only in version */        /* 1.0.1 and later versions of the Apple Event Manager*/        keyAERecorderCount                                 = 'recr',                    /*keyword for recording info*/        keyAEVersion                                 = 'vers',                    /*keyword for version info*/        /*event class*/        kCoreEventClass                                = 'aevt'                    /*event class for required */                                                            /* Apple events*/};        /*event IDs for required Apple events*/enum {        kAEOpenApplication                                = 'oapp',                    /*event ID for Open */                                                            /* Application event*/        kAEOpenDocuments                                = 'odoc',                    /*event ID for Open */                                                            /* Documents event*/        kAEPrintDocuments                                = 'pdoc',                    /*event ID for Print */                                                            /* Documents event*/        kAEQuitApplication                                = 'quit',                    /*event ID for Quit */                                                            /* Application event*/        kAEAnswer                                = 'ansr',                    /*event ID for Apple event */                                                            /* replies*/        kAEApplicationDied                                = 'obit'                    /*event ID for Application */                                                            /* Died event*/};        /*constants for setting the sendMode parameter of AESend*/enum {        kAENoReply                                = 0x00000001,                    /*client doesn't want reply*/        kAEQueueReply                                = 0x00000002,                    /*client wants server to */                                                            /* reply in event queue*/        kAEWaitReply                                = 0x00000003,                    /*client wants a reply and */                                                            /* will give up processor*/        kAENeverInteract                                = 0x00000010,                    /*server application should */                                                            /* not interact with user */                                                            /* for this Apple event*/        kAECanInteract                                = 0x00000020,                    /*server may interact with */                                                            /* user for this Apple event */                                                            /* to supply information*/        kAEAlwaysInteract                                = 0x00000030,                    /*server may interact with */                                                            /* user for this Apple event */                                                            /* even if no information */                                                            /* is required*/        kAECanSwitchLayer                                = 0x00000040,                    /*server should come */                                                            /* directly to foreground */                                                            /* when appropriate*/        kAEDontReconnect                                = 0x00000080,                    /*don't reconnect if there */                                                            /* is a PPC session closed */                                                            /* error*/        kAEWantReceipt                                = nReturnReceipt, /*client wants return */                                                            /* receipt*/        kAEDontRecord                                = 0x00001000,                    /*don't record this event*/        kAEDontExecute                                = 0x00002000,                    /*don't excecute this event*/        /*constants for setting the sendPriority parameter of AESend*/        kAENormalPriority                                = 0x00000000,                    /*post message at end of */                                                            /* event queue*/        kAEHighPriority                                = nAttnMsg                    /*post message at front of */                                                            /* event queue*/};        /*event IDs for recording events; available only in version 1.01 and */        /* later versions of the Apple Event Manager*/enum {        kAEStartRecording                                = 'reca'        ,            /*event ID for Start */                                                            /* Recording event*/        kAEStopRecording                                = 'recc',                    /*event ID for Stop */                                                            /* Recording event*/        kAENotifyStartRecording                                = 'rec1',                    /*event ID for Recording On */                                                            /* event*/        kAENotifyStopRecording                                = 'rec0',                    /*event ID for Recording Off */                                                            /* event*/        kAENotifyRecording                                = 'recr'                    /*event ID for Receive */                                                            /* Recordable Event event*/};enum {        /*constant for the returnID parameter of AECreateAppleEvent*/        kAutoGenerateReturnID                                = -1,                    /*tells Apple Event Manager */                                                            /* to generate a unique */                                                            /* return ID*/        /*constant for transaction IDs*/        kAnyTransactionID                                 = 0,                    /*the Apple event is not */                                                            /* part of a transaction*/        /*constants for timeout durations*/        kAEDefaultTimeout                                = -1,                    /*use default timeout value*/        kNoTimeOut                                = -2    ,                /*never time out*/        /*constants for the dispatcher parameter of AEResumeTheCurrentEvent*/        kAENoDispatch                                = 0,                    /*don't redispatch the */                                                            /* Apple event*/        kAEUseStandardDispatch                                = -1                /*redispatch the Apple event */                                                            /* by using its entry in the */                                                            /* Apple event dispatch table*/};Data Typestypedef unsigned long AEEventClass;                                                            /*event class for a */                                                            /* high-level event*/typedef unsigned long AEEventID;                                                            /*event ID for a high-level */                                                            /* event*/typedef unsigned long AEKeyword;                                                            /*keyword for a descriptor */                                                            /* record*/typedef ResType DescType                                ;                            /*descriptor type*/struct AEDesc {                                                             /*descriptor record*/    DescType descriptorType;                                                         /*type of data being passed*/    Handle dataHandle;                                                        /*handle to data being passed*/};typedef struct AEDesc AEDesc;struct AEKeyDesc {                                                             /*keyword-specified */                                                            /* descriptor record*/    AEKeyword descKey;                                                        /*keyword*/    AEDesc descContent;                                                        /*descriptor record*/};typedef struct AEKeyDesc AEKeyDesc;typedef AEDesc AEAddressDesc;                                                            /*address descriptor record*/typedef AEDesc AEDescList;                                                            /*list of descriptor records*/typedef AEDescList AERecord;                                                            /*list of keyword-specified */                                                            /* descriptor records*/typedef AERecord AppleEvent;                                                            /*list of attributes and */                                                            /* parameters necessary for */                                                            /* an Apple event*/typedef long AESendMode;                                                            /*flags that determine how */                                                            /* an Apple event is sent*/typedef short AESendPriority;                                                            /*send priority of an Apple */                                                            /* event*/enum { kAEInteractWithSelf, kAEInteractWithLocal,         kAEInteractWithAll };                                                    /*what processes may */typedef unsigned char AEInteractAllowed;                                                            /* interact with the user*/enum { kAEUnknownSource, kAEDirectCall, kAESameProcess,             kAELocalProcess,          kAERemoteProcess };                                                    /*the source of an Apple */typedef unsigned char AEEventSource;                                                            /* event*/enum { kAEDataArray, kAEPackedArray, kAEHandleArray,          kAEDescArray, kAEKeyDescArray };                                                    /*type of an Apple event */typedef unsigned char AEArrayType;                                                            /* array*/union     AEArrayData {                                                         /*data for an Apple event */    short         kAEDataArray[1];                                                /* array*/    char     kAEPackedArray[1];    Handle         kAEHandleArray[1];    AEDesc         kAEDescArray[1];    AEKeyDesc kAEKeyDescArray[1];};typedef union AEArrayData AEArrayData;typedef AEArrayData *AEArrayDataPointer;typedef ProcPtr EventHandlerProcPtr;                                                            /*pointer to an Apple event */                                                            /* handler*/typedef ProcPtr IdleProcPtr;                                                            /*pointer to an application's */                                                            /* idle function*/typedef ProcPtr EventFilterProcPtr;                                                            /*pointer to an application's */                                                            /* filter function*/Routines for Creating and Sending Apple EventsCreating Apple Eventspascal OSErr AECreateAppleEvent(AEEventClass theAEEventClass, AEEventID theAEEventID, const AEAddressDesc *target, short returnID, long transactionID, AppleEvent *result);Creating and Duplicating Descriptor Recordspascal OSErr AECreateDesc    (DescType typeCode, const void* dataPtr, Size dataSize, AEDesc *result);pascal OSErr AEDuplicateDesc(const AEDesc *theAEDesc, AEDesc *result);Creating Descriptor Lists and AE Recordspascal OSErr AECreateList    (const void* factoringPtr, Size factoredSize, Boolean isRecord, AEDescList *resultList);Adding Items to Descriptor Listspascal OSErr AEPutPtr    (const AEDescList *theAEDescList, long index, DescType typeCode, const void* dataPtr, Size dataSize);pascal OSErr AEPutDesc    (const AEDescList *theAEDescList, long index, const AEDesc *theAEDesc);pascal OSErr AEPutArray    (const AEDescList *theAEDescList, AEArrayType arrayType, const AEArrayDataPointer *arrayPtr, DescType itemType, Size itemSize, long itemCount);Adding Data and Descriptor Records to AE Recordspascal OSErr AEPutKeyPtr    (const AERecord *theAERecord, AEKeyword theAEKeyword, DescType typeCode, const void* dataPtr, Size dataSize);pascal OSErr AEPutKeyDesc    (const AERecord *theAERecord, AEKeyword theAEKeyword, const AEDesc *theAEDesc);Adding Parameters and Attributes to Apple Eventspascal OSErr AEPutParamPtr    (const AppleEvent *theAppleEvent, AEKeyword theAEKeyword, DescType typeCode, const void* dataPtr, Size dataSize);pascal OSErr AEPutParamDesc    (const AppleEvent *theAppleEvent, AEKeyword theAEKeyword, const AEDesc *theAEDesc);pascal OSErr AEPutAttributePtr(const AppleEvent *theAppleEvent, AEKeyword theAEKeyword, DescType typeCode, const void* dataPtr, Size dataSize);pascal OSErr AEPutAttributeDesc(const AppleEvent *theAppleEvent, AEKeyword theAEKeyword, const AEDesc *theAEDesc);Sending Apple Eventspascal OSErr AESend    (const AppleEvent *theAppleEvent, AppleEvent *reply, AESendMode sendMode, AESendPriority sendPriority, long timeOutInTicks, IdleProcPtr idleProc, EventFilterProcPtr filterProc);Application-Defined Routinespascal Boolean MyIdleFunction(const EventRecord *event,long *sleepTime, RgnHandle *mouseRgn);pascal Boolean MyReplyFilter(const EventRecord *event, long returnID, long transactionID,AEAddressDesc sender);Assembly-Language SummaryTrap MacrosTrap Macros Requiring Routine Selectors_Pack8Selector    Routine    $0405    AEDuplicateDesc    $0609    AEPutDesc    $0610    AEPutKeyDesc    $0610    AEPutParamDesc    $0627    AEPutAttributeDesc    $0706    AECreateList    $0825    AECreateDesc    $0A08    AEPutPtr    $0A0F    AEPutKeyPtr    $0A0F    AEPutParamPtr    $0A16    AEPutAttributePtr    $0B0D    AEPutArray    $0B14    AECreateAppleEvent    $0D17    AESend    Result CodesnoErr    0    No error    paramErr    –50    Parameter error (for example, value of handler pointer is NIL or odd)    eLenErr    –92    Buffer too big to send    memFullErr    –108    Not enough room in heap zone    userCanceledErr    –128    User canceled an operation    procNotFound    –600    No eligible process with specified process serial number    bufferIsSmall    –607    Buffer is too small    noOutstandingHLE    –608    No outstanding high-level event    connectionInvalid    –609    Nonexistent signature or session ID    noUserInteractionAllowed    –610    Background application sends event requiring authentication    noPortErr    –903    Client hasn’t set 'SIZE' resource to indicate awareness of high-level events    destPortErr    –906    Server hasn’t set 'SIZE' resource to indicate awareness of high-level events, or else is not present    sessClosedErr    –917    The kAEDontReconnect flag in the sendMode parameter was set, and the server quit and then restarted    errAECoercionFail    –1700    Data could not be coerced to the requested descriptor type    errAEDescNotFound    –1701    Descriptor record was not found    errAECorruptData    –1702    Data in an Apple event could not be read    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    errAENewerVersion    –1706    Need a newer version of the Apple Event Manager    errAENotAppleEvent    –1707    Event is not an Apple event    errAEEventNotHandled    –1708    Event wasn’t handled by an Apple event handler    errAEReplyNotValid    –1709    AEResetTimer was passed an invalid reply    errAEUnknownSendMode    –1710    Invalid sending mode was passed    errAEWaitCanceled    –1711    User canceled out of wait loop for reply or receipt    errAETimeout    –1712    Apple event timed out    errAENoUserInteraction    –1713    No user interaction allowed    errAENotASpecialFunction    –1714    The keyword is not valid for a special function    errAEParamMissed    –1715    Handler cannot understand a parameter the client considers required    errAEUnknownAddressType    –1716    Unknown Apple event address type    errAEHandlerNotFound    –1717    No handler found for an Apple event or a coercion, or no object callback function found    errAEReplyNotArrived    –1718    Reply has not yet arrived    errAEIllegalIndex    –1719    Not a valid list index    errAEImpossibleRange    –1720    The range is not valid because it is impossible for a range to include the first and last objects that were specified; an example is a range in which the offset of the first object is greater than the offset of the last object    errAEWrongNumberArgs    –1721    The number of operands provided for the kAENot logical operator is not 1    errAEAccessorNotFound    –1723    There is no object accessor function for the specified object class and token descriptor type    errAENoSuchLogical    –1725    The logical operator in a logical descriptor record is not kAEAnd, kAEOr, or kAENot    errAEBadTestKey    –1726    The descriptor record in a test key is neither a comparison descriptor record nor a logical descriptor record    errAENotAnObjectSpec    –1727    The objSpecifier parameter of AEResolve is not an object specifier record    errAENoSuchObject    –1728     A run-time resolution error, for example: object specifier record asked for the third element, but there are only two    errAENegativeCount    –1729     Object-counting function returned negative value    errAEEmptyListContainer    –1730    The container for an Apple event object is specified by an empty list    errAEUnknownObjectType    –1731    Descriptor type of token returned by AEResolve is not known to server application     errAERecordingIsAlreadyOn    –1732    Attempt to turn recording on when it is already on    Listing 6-0Table 6-0Resolving and Creating Object Specifier RecordsContentsResolving Object Specifier Records6-4Descriptor Records Used in Object Specifier Records6-8Object Class6-9Container6-9Key Form6-11Key Data6-12Key Data for a Property ID6-13Key Data for an Object’s Name6-14Key Data for a Unique ID6-14Key Data for Absolute Position6-14Key Data for Relative Position6-15Key Data for a Test6-15Key Data for a Range6-20Installing Entries in the Object Accessor Dispatch Tables6-21Installing Object Accessor Functions That Find Apple Event Objects6-23Installing Object Accessor Functions That Find Properties6-27Writing Object Accessor Functions6-28Writing Object Accessor Functions That Find Apple Event Objects6-29Writing Object Accessor Functions That Find Properties6-37Defining Tokens6-39Handling Whose Tests6-41Writing Object Callback Functions6-45Writing an Object-Counting Function6-48Writing an Object-Comparison Function6-50Writing Marking Callback Functions6-53Creating Object Specifier Records6-55Creating a Simple Object Specifier Record6-57Specifying the Container Hierarchy6-61Specifying a Property6-63Specifying a Relative Position6-64Creating a Complex Object Specifier Record6-64Specifying a Test6-64Specifying a Range6-72Reference to Resolving and Creating Object Specifier Records6-75Data Structures Used in Object Specifier Records6-75Routines for Resolving and Creating Object Specifier Records6-77Initializing the Object Support Library6-77Setting Object Accessor Functions and Object Callback Functions6-77Getting, Calling, and Removing Object Accessor Functions6-81Resolving Object Specifier Records6-85Deallocating Memory for Tokens6-87Creating Object Specifier Records6-88Application-Defined Routines6-94Object Accessor Functions6-94Object Callback Functions6-96Summary of Resolving and Creating Object Specifier Records6-104Pascal Summary6-104Constants6-104Data Types6-106Routines for Resolving and Creating Object Specifier Records6-106Application-Defined Routines6-108C Summary6-109Constants6-109Data Types6-111Routines for Resolving and Creating Object Specifier Records6-112Application-Defined Routines6-114Assembly-Language Summary6-115Trap Macros6-115Result Codes6-115Resolving and Creating Object Specifier RecordsThis chapter describes how your application can use the Apple Event Manager and application-defined functions to resolve object specifier records. Your application must be able to resolve object specifier records to respond to core and functional-area Apple events defined in the Apple Event Registry: Standard Suites. For example, after receiving a Get Data event that requests a table in a document, your application can use the Apple Event Manager and application-defined functions to parse the object specifier record in the direct parameter, locate the requested table, and send a reply Apple event containing the table’s data back to the application that requested it.This chapter also describes how your application can use the Apple Event Manager to create object specifier records. If you want to factor your application for Apple event recording, or if you want to send Apple events directly to other applications, you need to know how to create object specifier records.To use this chapter, you should be familiar with the chapters “Introduction to Apple Events” and “Responding to Apple Events” in this book. The section “Working With Object Specifier Records,” which begins on page 3-32, provides a general introduction to the subject.If you plan to create object specifier records, you should also be familiar with the chapter “Creating and Sending Apple Events.” If you are factoring your application, you should read the chapter “Recording Apple Events” before you write code for resolving or creating object specifier records.This chapter begins with an overview of the way your application works with the Apple Event Manager to resolve object specifier records. It then describesn    how the data in an object specifier record is organizedn    how to install entries in the object accessor tablesn    how to write object accessor and object callback functionsn    how to create an object specifier recordIMPORTANTVersions 1.0 and 1.01 of the Apple Event Manager do not include the routines for resolving and creating object specifier records described in this chapter. To use these routines with those versions of the Apple Event Manager, you must link the Object Support Library (OSL) with your application when you build it, and call the AEObjectInit function before calling any of the routines.s  Resolving Object Specifier RecordsIf an Apple event parameter consists of an object specifier record, your handler for the Apple event should resolve the object specifier record: that is, locate the Apple event objects it describes. The first step is to call the AEResolve function with the object specifier record as a parameter. The AEResolve function performs tasks that are required to resolve any object specifier record, such as parsing its contents, keeping track of the results of tests, and handling memory management. When necessary, AEResolve calls application-defined functions to perform tasks that are unique to the application, such as locating a specific Apple event object in the application’s data structures or counting the number of Apple event objects in a container.NoteObject specifier records are only valid while the Apple event that contains them is being handled. For example, if an application receives an Apple event asking it to cut row 5 of a table, what was row 6 then becomes row 5, and the original object specifier record that referred to row 5 no longer refers to the same row.uThe AEResolve function can call two kinds of application-defined functions. Object accessor functions locate Apple event objects. Object callback functions perform other tasks that only an application can perform, such as counting, comparing, or marking Apple event objects. This section provides an overview of the way AEResolve calls object accessor and object callback functions when it resolves object specifier records. Each time AEResolve calls one of your application’s object accessor functions successfully, the object accessor function should return a special descriptor record created by your application, called a token, that identifies either an element in a specified container or a property of a specified Apple event object. The Apple Event Manager examines the token’s descriptor type but does nothing with the token’s data. When it needs to refer to the object the token identifies, the Apple Event Manager simply passes the token back to your application. Each object accessor function provided by your application should either find elements of a given object class in a container identified by a token of a given descriptor type, or find properties of an Apple event object identified by a token of a specified descriptor type. The Apple Event Manager uses the object class ID and the descriptor type of the token that identifies the object’s container to determine which object accessor function to call.It is up to you to decide how many object accessor functions you need to write for your application. You can write one object accessor function that locates Apple event objects of several different object classes, or you can write separate object accessor functions for certain object classes. Similarly, you may want to use only one descriptor type for all the tokens returned by your object accessor functions, or you may want to use several descriptor types. The way you define your tokens depends on the needs of your application. You can use the AEInstallObjectAccessor function to create an object accessor dispatch table that the Apple Event Manager uses to map requests for Apple event objects to the appropriate object accessor function in your application. The Apple Event Manager uses the object class of each requested object and the descriptor type of the token that identifies the object’s container to determine which object accessor function to call. Depending on the container hierarchy for a given object specifier record and the way your application defines its object accessor functions, the Apple Event Manager may need to call a series of object accessor functions to resolve the nested object specifier records that describe an Apple event object’s container. For information about creating and using the object accessor dispatch table, see “Installing Entries in the Object Accessor Dispatch Tables,” which begins on page 6-21. Figure 6-1 illustrates the major steps involved in resolving an object specifier record. The SurfWriter application shown in Figure 6-1 receives a Get Data event whose direct parameter is an object specifier record for a table named “Summary of Sales” in a document named “Sales Report.” The SurfWriter application’s handler for the Get Data event calls the AEResolve function with the object specifier record as a parameter. The AEResolve function begins to parse the object specifier record. The first object accessor function that AEResolve calls is usually the function that can identify the Apple event object in the application’s default container—the outermost container in the container hierarchy. In Figure 6-1, the object specifier record for the document “Sales Report” specifies the default container, so the Apple Event Manager calls the object accessor function in the SurfWriter application that can locate a document in a container identified by a descriptor record of descriptor type typeNull. Figure 6-1    Resolving an object specifier record for a table in a documentAfter locating the document named “Sales Report,” the SurfWriter application returns a token to the Apple Event Manager—that is, a descriptor record that SurfWriter uses to identify the document. The Apple Event Manager examines the descriptor type of the token but does not need to know anything about the token’s data to continue parsing the object specifier record. Next, the Apple Event Manager calls the object accessor function that can identify a table in a container identified by a token of descriptor type typeMyDocToken. When the Apple Event Manager calls this object accessor function, it uses the token that describes the document to identify the table’s container. After the SurfWriter application has located the table named “Summary of Sales” in the document named “Sales Report,” it returns a token describing that table to the Apple Event Manager. After your application has successfully located an Apple event object, the Apple Event Manager disposes of all previous tokens returned during resolution of the object specifier record for the object. The Apple Event Manager disposes of tokens by calling either the AEDisposeDesc function or your application’s token disposal function, if you have provided one, which is an object callback function that disposes of a token. In Figure 6-1, the AEResolve function calls the SurfWriter application’s token disposal function to dispose of the token for the document after AEResolve receives the token for the table. After the SurfWriter application has disposed of the token for the document, the AEResolve function returns the result of the resolution—that is, the token for the requested table—to the handler in the SurfWriter application that originally called AEResolve. The Apple Event Manager can complete the cycle of parsing the object specifier record and calling the appropriate object accessor function to obtain a token as many times as necessary to identify every container in the container hierarchy and finish resolving an object specifier record, including disposing of the tokens for the containers. However, one token will always be left over—the token that identifies the requested Apple event object. After AEResolve returns this final token and your application performs the action requested by the Apple event, it is up to your application to dispose of the token. Your application can do so by calling the AEDisposeToken function, which in turn calls either AEDisposeDesc or your application’s token disposal function. You need to provide a token disposal function only if a call to AEDisposeDesc is not sufficient by itself to dispose of a token or if you provide marking callback functions, which are three object callback functions that allow your application to use its own marking scheme rather than tokens when identifying large groups of Apple event objects. Your application is not required to provide marking callback functions. To handle object specifier records that specify a test, your application must provide two object callback functions: (a) an object-counting function, which counts the number of elements of a given object class in a given container so that the Apple Event Manager can determine how many elements it must test to find the element or elements that meet a specified condition, and (b) an object-comparison function, which compares one element to another element or to a descriptor record and returns TRUE or FALSE. Your application may also provide an error callback function that can identify which descriptor record caused the resolution of an object specifier record to fail. Your application is not required to provide an error callback function.If your application resolves object specifier records without the help of the Apple Event Manager, it must extract the equivalent descriptor records and coerce them as necessary to get access to their data. The Apple Event Manager includes coercion handlers for these coercions; for information about this default coercion handling, see Table 4-1 on page 4-43.For more information about object accessor functions, see “Writing Object Accessor Functions,” which begins on page 6-28. For more information about object callback functions, see “Writing Object Callback Functions,” which begins on page 6-45.  The next section, “Descriptor Records Used in Object Specifier Records,” describes how the data in an object specifier record is interpreted by the Apple Event Manager.  Descriptor Records Used in Object Specifier RecordsAn object specifier record is a coerced AE record of descriptor type typeObjectSpecifier. The data to which its data handle refers consists of four keyword-specified descriptor records:Keyword    Value    Description of data    keyAEDesiredClass    'want'    A four-character code for the object class    keyAEContainer    'from'    An object specifier record (or in some cases a descriptor record with a handle whose value is NIL) that identifies the container for the requested objects    keyAEKeyForm    'form'    A four-character code for the key form    keyAEKeyData    'seld'    Data or nested descriptor records that specify a property, name, position, range, or test, depending on the key form    This section describes the descriptor types and data associated with each of these keywords. You need this information if your application resolves or creates object specifier records.For a summary of the descriptor types and key forms discussed in this section, see Table 6-11 on page 6-76. For an overview of object specifier records, see “Working With Object Specifier Records,” which begins on page 3-32.Object ClassThe object class of the requested objects is identified by an object class ID. The corresponding keyword-specified descriptor record takes this form: Keyword    Descriptor type    Data    keyAEDesiredClass    typeType    Object class ID    The Apple Event Registry: Standard Suites defines constants for the standard object class IDs.ContainerThe container for the requested objects is usually the object in which they are located. It can be identified in one of four ways:Keyword    Descriptor type    Data    keyAEContainer    typeObjectSpecifier    Object specifier record.        typeNull    Value of data handle is NIL. Specifies the default container at the top of the container hierarchy.        typeObjectBeingExamined    Value of data handle is NIL. Specifies the container for elements that are tested one at a time; used only within key data for key form formTest.        typeCurrentContainer    Value of data handle is NIL. Specifies a container for an element that demarcates one boundary in a range. Used only within key data for key form formRange.    The data that describes a container usually consists of another object specifier record. The ability to nest one object specifier record within another in this way makes it possible to identify a chain of containers that fully describes the location of one or more Apple event objects.For example, Figure 6-2 shows nested object specifier records that specify the first row of a table named “Summary of Sales” in a document named “Sales Report.” The container specified by the object specifier record at the bottom of the figure describes the outermost container in the container hierarchy—the container for the document “Sales Report.”  Because a container must be specified for each Apple event object in a container hierarchy, a null descriptor record (that is, a descriptor record whose descriptor type is typeNull and whose data handle has the value NIL) is used to specify the application’s default container—the outermost container for any container hierarchy in that application.    Figure 6-2    Nested object specifier records that specify a container hierarchyNoteThe format used in Figure 6-2 and similar figures throughout this chapter does not show the structure of the nested object specifier records as they exist within an Apple event. Instead, these figures show what you would obtain after calling AEGetKeyDesc repeatedly to extract the object specifier records from an Apple event record.When you call AEGetKeyDesc to extract a null descriptor record, the function returns a descriptor record of type AEDesc with a descriptor type of typeNull and a data handle whose value is 0.uThe object specifier data at the bottom of Figure 6-2 uses a null descriptor record to specify the document’s container—that is, the default container for the application. The object specifier record for the document identifies the document named “Sales Report”; the object specifier record for the table identifies the table named “Summary of Sales” in the document “Sales Report”; and the object specifier record for the row identifies the first row of the table named “Summary of Sales” in the document “Sales Report.”An object specifier record in an Apple event parameter almost always includes nested object specifier records that specify the container hierarchy for the requested Apple event object. For the nested object specifier records shown in Figure 6-2, the relationship between each Apple event object and its container is always simple containment: it is located inside its container. In other cases, the specified container may not actually contain the requested Apple event object. Instead, the relationship between a “container” and a specified object can be defined differently, depending on the key form. For example, the key form formRelativePosition indicates that the requested object is before or after its container. Object specifier records that specify the key form formTest or formRange require key data that consists of several nested descriptor records, including additional object specifier records that identify either a group of elements to be tested or the boundary elements that demarcate a range. These object specifier records use two special descriptor types to specify containers: typeObjectBeingExamined (see page 6-19), which specifies a container that changes as a group of elements are tested one at a time, and typeCurrentContainer (see page 6-20), which specifies the container for a boundary element in a range. Both of these descriptor types require a data handle whose value is NIL, since they act much like variables whose value is supplied by the Apple Event Manager according to other information provided in the container hierarchy. Key FormThe key form indicates how the key data should be interpreted. It can be specified by one of eight constants: Keyword    Descriptor type    Data    keyAEKeyForm    typeEnumerated    formPropertyIDformNameformUniqueIDformAbsolutePositionformRelativePositionformTestformWhoseformRange    The next section describes the key data that corresponds to each key form.Key DataThe nature of the information provided by the key data depends both on the specified key form and on the descriptor type of the descriptor record for the key data. Table 6-1 summarizes these relationships for the standard key forms. Table 6-1    Standard descriptor types used with keyAEKeyData(continued)Key form    Descriptor type    Data    formPropertyID     typeType    Property ID for an element’s property     formName    typeChar or other text type    Element’s name    formUniqueID    Any appropriate type    A value that uniquely identifies an object within its container or across an application     formAbsolutePosition    typeLongInteger    Offset from beginning (positive) or end (negative) of container        typeAbsoluteOrdinal    kAEFirstkAEMiddlekAELastkAEAnykAEAll    formRelativePosition    typeEnumerated    kAENextkAEPrevious    formTest    typeCompDescriptor    (see Table 6-2 on page 6-16)         typeLogicalDescriptor    (see Table 6-3 on page 6-17)    formRange    typeRangeDescriptor    (see Table 6-4 on page 6-20)     formWhose    typeWhoseDescriptor    (see Table 6-5 on page 6-42)     Most applications that resolve object specifier records need to support only the key forms formPropertyID, formName, formUniqueID, formAbsolutePosition, formRelativePosition, and formRange explicitly. You do not need to support these key forms for all object classes; for example, words usually do not have names, so most applications should return errAEEventNotHandled if they receive a request for a word by name. If your application provides an object-counting function and an object-comparison function in addition to the appropriate object accessor functions, the Apple Event Manager can handle formTest automatically.The Apple Event Manager uses the key form formWhose internally to optimize resolution of object specifier records that specify formTest. Applications that translate tests into their own query languages need to support formWhose explicitly. “Handling Whose Tests,” which begins on page 6-41, describes formWhose in detail.You can define custom key forms and the format for corresponding data for use by your own application if necessary. If you think you need to do this, check with the Apple Event Registrar first to find out whether existing key forms or others still under development can be adapted to the needs of your application. One simple kind of key form involves identifying an object on the basis of a specified property. For example, the corresponding data for key form formUniqueID (defined in the Apple Event Registry: Standard Suites) always consists of a unique ID for the requested object. This ID is stored as a property identified by the constant pID. The four-character code that corresponds to both formUniqueID and pID is 'ID  '. If you discover that you do need to define a custom key form based on a property, use the same four-character code for both the key form and the associated property. The rest of this section describes how the key data for the other key forms shown in Table 6-1 identifies Apple event objects.Key Data for a Property IDThe key data for formPropertyID is specified by a descriptor record of descriptor type typeType. The Apple Event Registry: Standard Suites defines constants for the standard property IDs.An object specifier record for a property specifies cProperty as the object class ID, an object specifier record for the object that contains the property as the container, formPropertyID as the key form, and a constant such as pFont as the key data. For example, if you were sending a Set Data event to change the font of a word to Palatino®, you could specify the data for the object specifier record in the direct parameter as follows:Keyword    Descriptor type    Data    keyAEDesiredClass    typeType    cProperty    keyAEContainer    typeObjectSpecifier    Object specifier record for word to which property belongs    keyAEKeyForm    typeEnumerated    formPropertyID    keyAEKeyData    typeType    pFont    In this example, the Set Data Apple event parameter identified by the keyword keyAETheData would specify Palatino as the value to which to set the specified property. The reply Apple event for a subsequent Get Data event that included an object specifier record for the same property would return Palatino in the parameter identified by the keyword keyAEResult.   Key Data for an Object’s NameThe key data for formName is specified by a descriptor record whose data consists of text, with a descriptor type such as typeChar or typeIntlText. Figure 6-2 on page 6-10 includes two object specifier records that specify formName.Key Data for a Unique IDThe key data for formUniqueID consists of a value that identifies an object. This ID must be unique either within the container, at a minimum, or unique across the application. A unique ID can be specified by a descriptor record of any appropriate type; for example, type typeInteger. Key Data for Absolute PositionThe key data for formAbsolutePosition consists of an integer that specifies either an offset or an ordinal position. For descriptor type typeLongInteger, the data is either a positive integer, indicating the offset of the requested element from the beginning of the container, or a negative integer, indicating its offset from the end of the container. The first object specifier record shown in Figure 6-2 on page 6-10 specifies formAbsolutePosition with key data that consists of the positive integer 1.For descriptor type typeAbsoluteOrdinal, the data consists of one of these constants: Constant    Meaning    kAEFirst    The first element in the specified container     kAEMiddle    The element in the middle of the specified container     kAELast    The last element in the specified container     kAEAny    A single element chosen at random from the specified container    kAEAll    All the elements in the specified container     If an object specifier record specifies kAEMiddle and the number of elements in the container is even, the Apple Event Manager rounds down; for example, the second word would be the “middle” word in a range of four words.Key Data for Relative PositionThe key data for formRelativePosition is specified by a descriptor record of type typeEnumerated whose data consists of one of these constants: Constant    Meaning    kAENext    The Apple event object after the specified container     kAEPrevious    The Apple event object before the specified container     The “container” can be a single Apple event object or a group of Apple event objects; the requested elements are located immediately before or immediately after it, not inside it. If your application can locate objects of the same class by absolute position, it can easily locate the same objects by relative position. For example, all applications that support formAbsolutePosition can easily locate the table immediately after a container specified as another table named “Summary of Sales.” Some applications may also be able to locate an object of one class before or after an object of another class. For example, a word processor might be able to locate the paragraph immediately after a container specified as a table named “Summary of Sales.”Key Data for a TestThe key data for formTest is specified by either a comparison descriptor record or a logical descriptor record. If your application provides an object-counting function and an object-comparison function in addition to the appropriate object accessor functions, the Apple Event Manager can handle formTest for you. Some applications may perform tests more efficiently by translating them into the application’s own query language. For information about handling tests yourself, see “Handling Whose Tests,” which begins on page 6-41.   The container for objects that pass a test can be one or more Apple event objects. The objects specified are those in the container that pass the test specified by the key data. For example, an object specifier record can describe “the first row in which the First Name column equals ‘John’ and the Last Name column equals ‘Chapman’ in the table ‘MyAddresses’ of the database ‘SurfDB.’” To resolve such an object specifier record, the Apple Event Manager must evaluate a logical expression that applies the logical operator AND to two separate comparisons for each row: a comparison of the First Name column to the word “John” and a comparison of the Last Name column to the word “Chapman.” The Apple Event Manager evaluates comparisons and logical expressions on the basis of the information in comparison descriptor records and logical descriptor records. A comparison descriptor record is a coerced AE record of type typeCompDescriptor that specifies an Apple event object and either another Apple event object or data for the Apple Event Manager to compare to the first object. The Apple Event Manager can also use the information in a comparison descriptor record to compare elements in a container, one at a time, either to an Apple event object or to data. The data for a comparison descriptor record consists of three keyword-specified descriptor records with the descriptor types and data shown in Table 6-2.Table 6-2    Keyword-specified descriptor records for typeCompDescriptorKeyword    Descriptor type    Data    keyAECompOperator    typeType    kAEGreaterThan kAEGreaterThanEqualskAEEqualskAELessThankAELessThanEqualskAEBeginsWithkAEEndsWithkAEContains    keyAEObject1    typeObjectSpecifier    Object specifier data         typeObjectBeingExamined    Value of data handle is NIL     keyAEObject2    typeObjectSpecifier    Object specifier data for object to be compared         typeObjectBeingExamined    Value of data handle is NIL        any other type (AEDesc)    Data to be compared     The keyword keyAEObject1 identifies a descriptor record for the element that is currently being compared to the object or data specified by the descriptor record for the keyword keyAEObject2. Either object can be described by a descriptor record of type typeObjectSpecifier or typeObjectBeingExamined. A descriptor record of typeObjectBeingExamined acts as a placeholder for each of the successive elements in a container when the Apple Event Manager tests those elements one at a time. The keyword keyAEObject2 can also be used with a descriptor record of any other descriptor type whose data is to be compared to each element in a container.You don’t have to support all the available comparison operators for all Apple event objects; for example, the “begins with” operator probably doesn’t make sense for objects of type cRectangle. It is up to you to decide which comparison operators are appropriate for your application to support, and how to interpret them. If necessary, you can define your own custom comparison operators. If you think you need to do this, check with the Apple Event Registrar first to find out whether existing definitions of comparison operators or definitions still under development can be adapted to the needs of your application.A logical descriptor record is a coerced AE record of type typeLogicalDescriptor that specifies a logical expression—that is, an expression that the Apple Event Manager evaluates to either TRUE or FALSE. The logical expression is constructed from a logical operator (one of the Boolean operators AND, OR, or NOT) and a list of logical terms to which the operator is applied. Each logical term in the list can be either another logical descriptor record or a comparison descriptor record. The Apple Event Manager short-circuits its evaluation of a logical expression as soon as one part of the expression fails a test. For example, if while testing a logical expression such as A AND B AND C the Apple Event Manager discovers that A AND B is not true, it will evaluate the expression to FALSE without testing C.The data for a logical descriptor record consists of two keyword-specified descriptor records with the descriptor types and data shown in Table 6-3.Table 6-3    Keyword-specified descriptor records for typeLogicalDescriptorKeyword    Descriptor type    Data    keyAELogicalOperator    typeEnumerated    kAEANDkAEORkAENOT    keyAELogicalTerms    typeAEList    One or more comparison or logical descriptor records    If the logical operator is AND or OR, the list can contain any number of logical terms, and the logical operator is applied to all the terms in the list. For example, the logical descriptor data shown in Figure 6-4 on page 6-19 consists of the logical operator AND and a list of logical terms that contains two comparison descriptor records. The entire logical descriptor record corresponds to the logical expression “the First Name column equals ‘John’ AND the Last Name column equals ‘Chapman.’” If the logical operator is NOT, the list must contain a single term. Figure 6-3 shows four object specifier records that specify the container hierarchy for the first row in the table “MyAddresses” of the database “SurfDB” that meets a test. The object specifier record at the top of Figure 6-3 specifies the first row contained in the set of rows that form its container. The container for the first row is specified by an object specifier record for a set of rows that meet a test. The two object specifier records at the bottom of Figure 6-3 specify the table named “MyAddresses,” which contains the rows to be tested, in the database named “SurfDB.” Figure 6-3    The container hierarchy for the first row in a table that meets a testThe object specifier record in Figure 6-3 for a set of rows that meet a test specifies formTest. The corresponding key data consists of the logical descriptor record shown in Figure 6-4, which applies the logical operator AND to two logical terms: a comparison descriptor record that specifies all the rows in the container (the table “MyAddresses”) in which the column named “First Name” equals “John,” and another comparison descriptor record that specifies all the rows in which the column named “Last Name” equals “Chapman.” A row in the table “MyAddresses” passes the test only if both comparison descriptor records evaluate as TRUE.Figure 6-4    A logical descriptor record that specifies a testThe keyword-specified descriptor records with the keyword keyAEObject1 in Figure 6-4 each consist of an object specifier record that identifies a column by name. The row for each column is specified by a descriptor record of typeObjectBeingExamined, which acts as a placeholder for each row as the Apple Event Manager tests successive rows in the table. The Apple event object specified by each of these object specifier records consists of a column in the row. The Apple Event Manager (with the help of an object-comparison function) compares the contents of the column in successive rows to the string identified by the keyword keyAEObject2 using the comparison operator identified by the keyword keyAECompOperator.  Key Data for a RangeThe key data for formRange is specified by a range descriptor record, which is a coerced AE record of type typeRangeDescriptor that identifies two Apple event objects marking the beginning and end of a range of elements. The data for a range descriptor record consists of two keyword-specified descriptor records with the descriptor types and data shown in Table 6-4. Table 6-4    Keyword-specified descriptor records in a descriptor record of type typeRangeDescriptorKeyword    Descriptor type    Data    keyAERangeStart    typeObjectSpecifier    An object specifier record for the first Apple event object in the desired range    keyAERangeStop    typeObjectSpecifier    An object specifier record for the last Apple event object in the desired range    The elements that identify the beginning and end of the range, which are known as boundary objects, do not have to belong to the same object class as the elements in the range itself. If the boundary objects belong to the same object class as the elements in the range, the boundary objects are included in the range. For example, the range of tables specified by boundary elements that are also tables would include the two boundary tables. The container for boundary objects is usually the same as the container for the entire range, in which case the container for a boundary object can be specified by a placeholder—that is, a descriptor record of type typeCurrentContainer whose data handle has the value NIL. When AEResolve calls an object accessor function to locate a range of objects, the Apple Event Manager replaces the descriptor record of type typeCurrentContainer with a token for the container of each boundary object. When using AEResolve to resolve the object specifier record, your application doesn’t need to examine the contents of this token, because the Apple Event Manager keeps track of it. If your application attempts to resolve some or all of the object specifier record without calling AEResolve, the application may need to examine the token before it can locate the boundary objects. The token provided by the Apple Event Manager for a boundary object’s container is a descriptor record of type typeToken whose data handle refers to a structure of type ccntTokenRecord.TYPE ccntTokenRecord = RECORD    tokenClass:                    DescType;                    {class ID of container }                                            { represented by token}    token:                    AEDesc;                    {token for current container}END;This data type is of interest only if you attempt to resolve an object specifier record for a range without calling AEResolve. Otherwise, the Apple Event Manager keeps track of the container.  Installing Entries in the Object Accessor Dispatch TablesIf the direct parameter for an Apple event consists of an object specifier record, your handler for the event should call the AEResolve function to resolve the object specifier record: that is, to find the Apple event objects or properties it describes. The AEResolve function resolves the object specifier record with the help of object accessor functions provided by your application. Your application installs entries for its object accessor functions in an object accessor dispatch table, which is used by the Apple Event Manager to map requests for Apple event objects or their properties to the appropriate object accessor functions. After being called by AEResolve, an object accessor function should return a token that identifies (in whatever manner is appropriate for your application) the specified Apple event object or property. An object accessor function also returns a result code that indicates whether it found the Apple event object or property. The token, which is a descriptor record of data type AEDesc, can be of any descriptor type, including descriptor types you define yourself. For an overview of the way AEResolve works with your application’s object accessor functions to locate Apple event objects, see “Resolving Object Specifier Records,” which begins on page 6-4.Each object accessor function provided by your application should either find elements of a specified object class contained in an Apple event object identified by a token of a specified descriptor type, or find properties of an Apple event object identified by a token of a specified descriptor type. To determine which object accessor function to dispatch, the Apple Event Manager uses the object class ID specified in an object specifier record and the descriptor type of the token that identifies the requested object’s container. For object accessor functions that find properties, you should specify the object class ID as the constant cProperty. To install entries in your application’s object accessor dispatch table, use the AEInstallObjectAccessor function. For each object class and property your application supports, you should install entries that specifyn    the object class of the requested Apple event object or propertyn    the descriptor type of the token used to identify the container for the requested Apple event object or propertyn    the address of the object accessor function that finds objects or properties of the specified object class in containers described by tokens of the specified descriptor typen    a reference constantYou provide this information in the first four parameters to the AEInstallObjectAccessor function. The fifth parameter allows you to indicate whether the entry should be added to your application’s object accessor dispatch table or the system object accessor dispatch table.The system object accessor dispatch table is a table in the system heap that contains object accessor functions available to all processes running on the same computer. The object accessor functions in your application’s object accessor dispatch table are available only to your application. If AEResolve cannot find an object accessor function for the Apple event object class in your application’s object accessor dispatch table, it looks in the system object accessor dispatch table. If it doesn’t find an object accessor function there either, it returns the result code errAEAccessorNotFound.  If AEResolve successfully calls the appropriate object accessor function in either the application object accessor dispatch table or the system object accessor dispatch table, the object accessor function returns a token and result code. The AEResolve function uses the token and result code to continue resolving the object specifier record. If, however, the token identifies the final Apple event object or property in the container hierarchy, AEResolve returns the token for the final resolution in the theToken parameter.If the AEResolve function calls an object accessor function in the system object accessor dispatch table, your Apple event handler may not recognize the descriptor type of the token returned by the function. If this happens, your handler should attempt to coerce the token to an appropriate descriptor type. If coercion fails, return the result code errAEUnknownObjectType. When your handler returns this result code, the Apple Event Manager attempts to locate a system Apple event handler that can recognize the token.It is up to you to decide how many object accessor functions you need to write and install for your application. You can install one object accessor function that locates Apple event objects of several different object classes, or you can write separate object accessor functions for certain object classes. Similarly, you may want to use only one descriptor type for all the tokens returned by your object accessor functions, or you may want to use several descriptor types. The sections that follow provide examples of alternative approaches.For more information about object accessor functions, see “Writing Object Accessor Functions,” which begins on page 6-28.Installing Object Accessor Functions That Find Apple Event ObjectsListing 6-1 demonstrates how to add entries to your application’s object accessor dispatch table for the object class cText and three of its element classes: the object classes cWord, cItem, and cChar. In this example, the container for each of these object classes is identified by a token that consists of a descriptor record of descriptor type typeMyText. Listing 6-1    Installing object accessor functions that find elements of different classes for container tokens of the same typemyErr := AEInstallObjectAccessor(cText, typeMyText,                                             @MyFindTextObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallObjectAccessor(cWord, typeMyText,                                             @MyFindWordObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallObjectAccessor(cItem, typeMyText,                                             @MyFindItemObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallObjectAccessor(cChar, typeMyText,                                             @MyFindCharObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);    The first call to AEInstallObjectAccessor in Listing 6-1 adds an entry to the application’s object accessor dispatch table. This entry indicates that the AEResolve function should call the MyFindTextObjectAccessor function when resolving any Apple event object with the cText object class and a container identified by a token of descriptor type typeMyText. The other calls to AEInstallObjectAccessor in Listing 6-1 add entries for Apple event objects of object classes cWord, cItem, and cChar in a container identified by a token of descriptor type typeMyText. For example, because all the entries created by the code in Listing 6-1 specify the descriptor type typeMyText for the token that identifies the container, the AEResolve function calls the MyFindWordObjectAccessor function to locate a requested word regardless of whether the container for the word is a run of text, another word, a paragraph, or an item. The fourth parameter for the AEInstallObjectAccessor function specifies a reference constant passed to your handler by the Apple Event Manager each time AEResolve calls your object accessor function. Your application can use this reference constant for any purpose. If your application doesn’t use the reference constant, you can use 0 as the value, as shown in Listing 6-1. The last parameter for the AEInstallObjectAccessor function is a Boolean value that determines whether the entry is added to the system object accessor dispatch table (TRUE) or to your application’s object accessor dispatch table (FALSE). If you add an object accessor function to the system object accessor dispatch table, the function that you specify must reside in the system heap. If there was already an entry in the system object accessor dispatch table for the same object class and container descriptor type, that entry is replaced unless you chain it to your system handler. You can do this the same way you chain a previously installed system Apple event handler to your own system handler. See the description of AEInstallEventHandler on page 4-62 for details.sWARNINGBefore an application calls a system object accessor function, system software has set up the A5 register for the calling application. For this reason, if you provide a system object accessor function, it should never use A5 global variables or anything that depends on a particular context; otherwise, the application that calls the system object accessor function may crash.sThe code shown in Listing 6-1 installs a separate object accessor function for each object class, even though the code specifies the same descriptor type for tokens that identify the containers for Apple event objects of each class. Most word-processing applications can specify the same object accessor function as well as the same token descriptor type for Apple event objects of these four classes, in which case the code shown in Listing 6-1 can be altered as shown in Listing 6-2.Listing 6-2    Installing one object accessor function that finds elements of different classes for container tokens of one typemyErr := AEInstallObjectAccessor(cText, typeMyText,                                             @MyFindTextObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallObjectAccessor(cWord, typeMyText,                                             @MyFindTextObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallObjectAccessor(cItem, typeMyText,                                             @MyFindTextObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallObjectAccessor(cChar, typeMyText,                                             @MyFindTextObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);In some situations you may want to write different object accessor functions to locate Apple event objects of the same object class in containers identified by tokens of different descriptor types. For example, the code in Listing 6-3 installs two different object accessor functions: one that finds a word in a container identified by a token of type typeMyTextToken, and one that finds a word in a container identified by a token of typeMyGraphicTextToken.Listing 6-3    Installing object accessor functions that find elements of the same class for container tokens of different typesmyErr := AEInstallObjectAccessor(cWord, typeMyTextToken,                                             @MyFindTextObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallObjectAccessor(cWord, typeMyGraphicTextToken,                                             @MyFindGrphcTextObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);Every application must provide one or more object accessor functions that can find Apple event objects in the default container, which is always identified by a token of descriptor type typeNull. Listing 6-4 demonstrates how to add entries to your application’s object accessor dispatch table for the object classes cWindow and cDocument. The container for each of these classes is identified by a token of descriptor type typeNull, which specifies an application’s default container.Listing 6-4    Installing object accessor functions that locate elements of different classes in the default containermyErr := AEInstallObjectAccessor(cWindow, typeNull,                                             @MyFindWindowObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);myErr := AEInstallObjectAccessor(cDocument, typeNull,                                             @MyFindDocumentObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);For any entry in your object accessor dispatch table, you can specify a wildcard value for the object class, for the descriptor type of the token used to identify the container, or for both. You specify a wildcard by supplying the typeWildCard constant when installing an entry into the object accessor dispatch table. A wildcard value matches all possible values.   If an object accessor dispatch table contains one entry for a specific object class and a specific token descriptor type, and another entry that is identical except that it specifies a wildcard value for either the object class or the token descriptor type, the Apple Event Manager dispatches the more specific entry. For example, if an object accessor dispatch table includes one entry that specifies the object class as cWord and the token descriptor type as typeMyTextToken, and another entry that specifies the object class as cWord and the token descriptor type as typeWildCard, the Apple Event Manager dispatches the object accessor function associated with the entry that specifies typeMyTextToken.If you specify typeWildCard as the first parameter and typeMyToken as the second parameter for the AEInstallObjectAccessor function and no other entry in the dispatch table matches more exactly, the Apple Event Manager calls the object accessor function that you specify in the third parameter when resolving Apple event objects of any object class in containers identified by tokens of the typeMyToken descriptor type.If you specify cText as the first parameter and typeWildCard as the second parameter for the AEInstallObjectAccessor function and no other entry in the dispatch table matches more exactly, the Apple Event Manager calls the object accessor function that you specify in the third parameter when resolving Apple event objects of the object class cText in containers identified by tokens of any descriptor type. If you specify typeWildCard for both the first and second parameters of the AEInstallObjectAccessor function and no other entry in the dispatch table matches more exactly, the Apple Event Manager calls the object accessor function that you specify in the third parameter when resolving Apple event objects of any object class in containers identified by tokens of any descriptor type. Once the Apple Event Manager finds a matching entry, whether exact or involving type typeWildCard, that is the only object accessor function it calls for that object class and token descriptor type. If that function fails, the Apple Event Manager won’t look for another matching entry in the same table.Installing Object Accessor Functions That Find PropertiesThe Apple event object to which a property belongs is that property’s container. You should add entries to your application’s object accessor dispatch table that specify object accessor functions for finding properties in containers identified by tokens of various descriptor types. Object specifier records do not specify a property’s specific object class; instead, they specify the constant cProperty as the class ID for any property. Similarly, you should specify the constant cProperty as the object class for an object accessor function that can find any property of a container identified by a token of a given descriptor type. If you need to install different object accessor routines for finding properties of Apple event objects that belong to different object classes, you must use different descriptor types for the tokens that represent those Apple event objects. For example, to specify an object accessor function that locates properties of Apple event objects identified by tokens of descriptor type typeMyToken, you can add a single entry to the object accessor dispatch table:myErr := AEInstallObjectAccessor(cProperty, typeMyToken,                                            @MyFindPropertyObjectAccessor,                                            0, FALSE);IF myErr <> noErr THEN DoError(myErr);The code in this example adds an object accessor function to the application’s object accessor dispatch table that can find any property of any container identified by a token of descriptor type typeMyToken. If the second parameter were specified as typeWildCard, the MyFindPropertyObjectAccessor function would have to be capable of finding any property of any Apple event object in your application except for those found by handlers with more specific entries in the object accessor dispatch table. Writing Object Accessor FunctionsIf the direct parameter for an Apple event consists of an object specifier record, your handler for the event should call the AEResolve function to resolve the object specifier record: that is, to find the Apple event objects or properties it describe. The AEResolve function resolves object specifier records with the help of object accessor functions provided by your application. For an overview of the way AEResolve works with your application’s object accessor functions to locate Apple event objects, see “Resolving Object Specifier Records,” which begins on page 6-4. This section describes how to write object accessor functions. You need to read this section if your application supports the Core suite or any of the functional-area suites in the Apple Event Registry: Standard Suites.Your application should provide object accessor functions that can find Apple event objects and their properties for all object classes supported by your application, including their corresponding properties and element classes. Because the Apple Event Manager dispatches object accessor functions according to the class ID of the requested Apple event object and the descriptor type of the token that identifies its container, you have a great deal of flexibility in deciding what object accessor functions you need to write for your application. The installation and dispatching of object accessor functions are described in “Installing Entries in the Object Accessor Dispatch Tables,” which begins on page 6-21.For example, if your application is a word processor, one object accessor function will probably work equally well for Apple event objects of object classes cParagraph, cItem, and cWord located in containers identified by tokens of descriptor type myTextToken. If you use a single descriptor type for tokens that identify any containers in which objects of these three object classes can be found, you can dispatch requests for all such elements to the same object accessor function. However, the same word processor might use one descriptor type for tokens identifying containers of class cCell and another descriptor type for tokens identifying containers of class cColumn—in which case it would need an object accessor function for each descriptor type.For each object class that your application supports, your application should also provide one object accessor function that can find all the properties of that object class, or one object accessor function that can find all the properties of several object classes.Here’s the declaration for a sample object accessor function:FUNCTION MyObjectAccessor (desiredClass: DescType;                                     containerToken: AEDesc;                                     containerClass: DescType;                                    keyForm: DescType; keyData: AEDesc;                                    VAR theToken: AEDesc;                                     theRefCon: LongInt): OSErr;The AEResolve function passes the following information to your object accessor function: the object class ID of the requested Apple event objects, the object class of their container, a token that identifies the specific container in which to look for them, the key form and key data that specify how to locate them, and the reference constant associated with the object accessor function. Your object accessor function uses this information to locate the requested objects. Most applications that resolve object specifier records need to support only the key forms formPropertyID, formName, formUniqueID, formAbsolutePosition, formRelativePosition, and formRange explicitly. You do not need to support these key forms for all object classes; for example, words usually do not have names, so most applications should return errAEEventNotHandled if they receive a request for a word by name. If your application provides an object-counting function and an object-comparison function in addition to the appropriate object accessor functions, the Apple Event Manager can handle formTest automatically.The Apple Event Manager uses the key form formWhose internally to optimize resolution of object specifier records that specify formTest. Only applications that translate tests into their own query languages need to support formWhose explicitly. “Handling Whose Tests,” which begins on page 6-41, describes formWhose in detail.If your object accessor function successfully locates the requested Apple event objects, your application should return the noErr result code and a token that identifies them. The token can be of any descriptor type, as long as it is a descriptor record. For example, to identify a file, your application might use a descriptor record of descriptor type typeAlias or typeFSS. To identify an open document, your application might define its own descriptor type, such as typeMyDocToken, for a descriptor record whose data handle refers to a pointer to a document record. For more information about tokens, see “Defining Tokens” on page 6-39. IMPORTANTObject accessor functions must not have side effects that change the number or order of elements in a container while an object specifier record is being resolved. If the number of elements in a container is changed during the resolution of an object specifier record, the Apple Event Manager may not be able to locate all the elements.sWriting Object Accessor Functions That Find Apple Event ObjectsThe first three listings in this section demonstrate how to write three object accessor functions that might be called in the following situation: An application receives a Get Data event with a direct parameter that consists of an object specifier record for the first word in the third paragraph of a document. The application’s handler for the Get Data event calls the AEResolve function to resolve the object specifier record. The AEResolve function first calls the application’s object accessor function for objects of class cDocument in containers identified by a token of descriptor type typeNull. The AEResolve function passes these values to the MyFindDocumentObjectAccessor function shown in Listing 6-5: in the desiredClass parameter, the constant cDocument; in the containerToken parameter, a descriptor record of descriptor type typeNull with a data handle whose value is NIL; in the containerClass parameter, the constant typeNull; in the keyForm parameter, the constant formName; in the keyData parameter, a descriptor record of descriptor type typeText whose data consists of the string "MyDoc"; and the reference constant specified in the application’s object accessor dispatch table.Listing 6-5    An object accessor function that locates Apple event objects of object class cDocumentFUNCTION MyFindDocumentObjectAccessor                                         (desiredClass: DescType;                                          containerToken: AEDesc;                                          containerClass: DescType;                                         keyForm: DescType; keyData: AEDesc;                                         VAR token: AEDesc;                                          theRefCon: LongInt): OSErr;VAR    docName:                        Str255;    actSize:                        Size;    foundDoc:                        Boolean;    foundDocRecPtr:                        MyDocumentRecordPtr;BEGIN    IF keyform = formName THEN    BEGIN        {get the name of the document from the key data}        MyGetStringFromDesc(keyData, docName, actSize);        {look for a document with the given name by }        { searching all document records}        MySearchDocRecs(docName, foundDocRecPtr, foundDoc);        IF NOT foundDoc THEN            MyFindDocumentObjectAccessor := kObjectNotFound        ELSE     {create token that identifies the document}            MyFindDocumentObjectAccessor :=                     AECreateDesc(typeMyDocToken, @foundDocRecPtr,                                        SizeOf(foundDocRecPtr), token);    END    {handle the other key forms you support}    ELSE        MyFindDocumentObjectAccessor := kKeyFormNotSupported;END;The MyFindDocumentObjectAccessor function uses the information in the keyForm and keyData parameters to find the specified document. If it finds the Apple event object, MyFindDocumentObjectAccessor returns a token of descriptor type typeMyDocToken to AEResolve. The data handle for this token refers to a pointer to a document record (see Figure 6-5 on page 6-39). The MyFindDocumentObjectAccessor function returns this token and the noErr result code to the AEResolve function.In the Get Data example, the token returned to AEResolve by the MyFindDocumentObjectAccessor function identifies the document “MyDoc.” The AEResolve function then calls the application’s object accessor function for objects of class cParagraph in containers identified by a token of descriptor type typeMyDocToken. In this case, AEResolve passes these values to the MyFindParaObjectAccessor function shown in Listing 6-6: in the desiredClass parameter, the constant cParagraph; in the containerToken parameter, the token returned by the MyFindDocumentObjectAccessor function; in the containerClass parameter, the constant cDocument; in the keyForm parameter, the constant formAbsolutePosition; in the keyData parameter, a descriptor record with the typeLongInteger descriptor type and data that consists of the value 3 (indicating the third paragraph); and the reference constant specified in the application’s object accessor dispatch table.Listing 6-6    An object accessor function that locates Apple event objects of object class cParagraphFUNCTION MyFindParaObjectAccessor (desiredClass: DescType;                                                 containerToken:     AEDesc;                                                 containerClass: DescType;                                                keyForm: DescType;                                                 keyData: AEDesc;                                                 VAR token: AEDesc;                                                 theRefCon: LongInt): OSErr;VAR    index:                        LongInt;    {MyFoundTextRecord is an application-defined data type }     { consisting of three fields: start, ending, and docPtr}     foundParaRec:                        MyFoundTextRecord;    foundParaStart:                        LongInt;    foundParaEnd:                        LongInt;    foundDocRecPtr:                        MyDocumentRecordPtr;    success:                        Boolean;BEGIN    IF keyForm = formAbsolutePosition THEN    BEGIN        {get the index of the paragraph from the key data}        MyGetIndexFromDesc(keyData, index);        {get the desired paragraph by index}        success := MyGetPara(index, containerToken, foundParaStart,                                     foundParaEnd, foundDocRecPtr);        IF NOT success THEN            MyFindParaObjectAccessor := kObjectNotFound        ELSE     {create token that identifies the paragraph}        BEGIN            foundParaRec.start := foundParaStart;            foundParaRec.ending := foundParaEnd;            foundParaRec.docPtr := foundDocRecPtr;            MyFindParaObjectAccessor :=                     AECreateDesc(typeMyTextToken, @foundParaRec,                                        SizeOf(foundParaRec), token);        END;    END        {handle the other key forms you support}    ELSE         MyFindParaObjectAccessor := kKeyFormNotSupported;END;The MyFindParaObjectAccessor function uses another application-defined function, MyGetPara, to search the data structures associated with the document and find the desired paragraph. If it finds the paragraph, MyGetPara returns a value that identifies the beginning of the paragraph, a value that identifies the end of the paragraph, and a pointer to the document (which MyGetPara gets from the containerToken parameter). The MyFindParaObjectAccessor function returns an application-defined token that contains this information. This token is of descriptor type typeMyTextToken; it describes a range of characters that can be used to identify any range of text, including a paragraph or a word. The MyFindParaObjectAccessor function returns this token and the noErr result code to the AEResolve function. In the Get Data example, the token returned to AEResolve by the MyFindParaObjectAccessor function identifies the third paragraph in the document “MyDoc.” The AEResolve function then calls the application’s object accessor function for objects of class cWord in containers identified by a token of descriptor type typeMyTextToken. In this case, the AEResolve function passes these values to the MyFindWordObjectAccessor function shown in Listing 6-7: in the desiredClass parameter, the constant cWord; in the containerToken parameter, the token returned by the MyFindParaObjectAccessor function (a token of descriptor type typeMyTextToken that identifies a paragraph); in the containerClass parameter, the constant cParagraph; in the keyForm parameter, the constant formAbsolutePosition; in the keyData parameter, a descriptor record with the typeLongInteger descriptor type and data that consists of the value 1 (indicating the first word); and the reference constant specified in the application’s object accessor dispatch table.The MyFindWordObjectAccessor function uses another application-defined function, MyGetWord, to search the paragraph to find the desired word. If it finds the word, MyGetWord returns a value that identifies the beginning of the word, a value that identifies the end of the word, and a pointer to the document (which MyGetWord gets from the containerToken parameter). The MyFindWordObjectAccessor function returns a token that contains this information. This token is also of descriptor type typeMyTextToken; in this case, the token identifies a specific word. The MyFindWordObjectAccessor function returns this token and the noErr result code to the AEResolve function, which in turn returns the token to the Get Data event handler that originally called AEResolve. Listing 6-7    An object accessor function that locates Apple event objects of object class cWordFUNCTION MyFindWordObjectAccessor                                         (desiredClass: DescType;                                          containerToken: AEDesc;                                          containerClass: DescType;                                         keyForm: DescType; keyData: AEDesc;                                         VAR token: AEDesc;                                          theRefCon: LongInt): OSErr;VAR    index:                        LongInt;    foundWordRec:                        MyFoundTextRecord;    foundWordStart:                        LongInt;    foundWordEnd:                        LongInt;    foundDocRecPtr:                        MyDocumentRecPtr;    success:                        Boolean;BEGIN    IF keyForm = formAbsolutePosition THEN    BEGIN        {get the index of the word from the key data}        MyGetIndexFromDesc(keyData, index);        {get the desired word by index}        success := MyGetWord(index, containerToken, foundWordStart,                                     foundWordEnd, foundDocRecPtr);        IF NOT success THEN            MyFindWordObjectAccessor := kObjectNotFound        ELSE     {create token that identifies the paragraph}        BEGIN            foundWordRec.start := foundWordStart;            foundWordRec.ending := foundWordEnd;            foundWordRec.docPtr := foundDocRecPtr;            MyFindWordObjectAccessor :=                     AECreateDesc(typeMyTextToken, @foundWordRec,                                        SizeOf(foundWordRec), token);        END;    END    {handle the other key forms you support}    ELSE         MyFindWordObjectAccessor := kKeyFormNotSupported;END;Listing 6-5 on page 6-30 shows an object accessor function that locates a document in the default container. Every application must provide one or more object accessor functions that can find Apple event objects in the default container, which is always identified by a descriptor record of descriptor type typeNull. Listing 6-8 provides another example of an object accessor function that locates an Apple event object in the default container. If the MyFindWindowObjectAccessor function shown in Listing 6-8 were installed in an application’s object accessor dispatch table, the AEResolve function would call it as necessary to locate an object of class cWindow in a container identified by a token of descriptor type typeNull.Listing 6-8    An object accessor function that locates Apple event objects of object class cWindowFUNCTION MyFindWindowObjectAccessor (desiredClass: DescType;                                                  containerToken: AEDesc;                                                  containerClass: DescType;                                                 keyForm: DescType;                                                  keyData: AEDesc;                                                 VAR token: AEDesc;                                                  theRefCon: LongInt): OSErr;VAR    windowName:                    Str255;    actSize:                    Size;    windTitle:                    Str255;    window:                    WindowPtr;    index, iLoop:                    Integer;    found:                    Boolean;BEGIN    IF keyForm = formName THEN    BEGIN        {get the name of the window to find from the keyData }        { parameter. MyGetStringFromDesc gets data out of an }        { AEDesc and returns a string and the string's size}        MyGetStringFromDesc(keyData, windowName, actSize);        {look for a window with the given name}        window := FrontWindow;        found := FALSE;        WHILE ((window <> NIL) AND (found = FALSE)) DO         BEGIN            GetWTitle(window, windTitle);            found := EqualString(windTitle, windowName, FALSE, TRUE);             IF NOT found THEN                window := WindowPtr(WindowPeek(window)^.nextWindow);        END;             {of while}    END {of formName}    ELSE    IF keyForm = formAbsolutePosition THEN        {find the window given an index in key data}            BEGIN            {get the index from the key data}                                MyGetIndexFromDesc(keyData, index);            found := FALSE;            iLoop := 0;            window := FrontWindow;            WHILE (window <> NIL) AND (found <> TRUE) DO            BEGIN                iLoop := iLoop +1;                IF iLoop = index THEN                    found := TRUE                ELSE                window := WindowPtr(WindowPeek(window)^.nextWindow);            END; {of while}        END     {of formAbsolutePosition}    {handle the other key forms you support}    ELSE    BEGIN        MyFindWindowObjectAccessor := kKeyFormNotSupported;        Exit(MyFindWindowObjectAccessor);    END;    IF window = NIL THEN        MyFindWindowObjectAccessor := kObjectNotFound    ELSE     {create token that identifies the window}        MyFindWindowObjectAccessor :=                     AECreateDesc(typeMyWindow, @window,                                         SizeOf(window), token);END;The keyForm parameter of the MyFindWindowObjectAccessor function describes how the function should interpret the keyData parameter. If the key form is formName, then the key data contains the name of the window to locate. If the key form is formAbsolutePosition, the key data contains the position of the window to locate in the window list; for example, a value of 1 identifies the frontmost window.The MyFindWindowObjectAccessor function supports only the formName and formAbsolutePosition key forms. Your object accessor functions should support all key forms that make sense for the kinds of objects the functions can locate.For the formName keyword, the MyFindWindowObjectAccessor function starts with the frontmost window and compares the window’s title to the name specified by the keyData parameter. It continues this search until it reaches either the end of the window list or finds a match. If the MyFindWindowObjectAccessor function finds a match, it uses the AECreateDesc function to create a descriptor record for the token, specifying the application-defined typeMyWindow descriptor type and the data for this descriptor type as a window pointer. The MyFindWindowObjectAccessor function then sets its function result appropriately, and the AEResolve function either returns this function result and token, or uses the returned token to request the next Apple event object in the container hierarchy, such as a document in the window. Writing Object Accessor Functions That Find PropertiesThe Apple event object to which a property belongs is that property’s container. Your application should provide an object accessor function for finding properties in containers identified by tokens of various descriptor types. Your application does not need to be given a property’s specific object class in order to find that property; instead, you can specify the object class ID for any property with the constant cProperty. Thus, you can write a single object accessor function that can find any property of an object identified by a token of a given descriptor type. To install such an object accessor function, you can add a single entry to the object accessor dispatch table that specifies the desired object class as cProperty for a given token descriptor type. For example, Listing 6-9 shows an object accessor function that identifies any property of a window.Listing 6-9    An object accessor function that identifies any property of a windowFUNCTION MyFindPropertyOfWindowObjectAccessor                                         (desiredClass: DescType;                                         containerToken:     AEDesc;                                         containerClass: DescType;                                        keyForm: DescType; keyData: AEDesc;                                        VAR token: AEDesc;                                         theRefCon: LongInt): OSErr;VAR    theProperty: DescType;BEGIN    MyFindPropertyOfWindowObjectAccessor := noErr;    MyGetPropFromKeyData(keyData, theProperty);    IF keyForm = formPropertyID THEN    BEGIN        IF theProperty = pName THEN            {create token that identifies name property of the }            { window}            MyCreateToken(typeMyWindowProp, containerToken, pName,                                 token)        ELSE        IF theProperty = pBounds THEN            {create token that identifies bounds property of the }            { window}            MyCreateToken(typeMyWindowProp, containerToken, pBounds,                                 token)        {create tokens for other properties as appropriate}        ELSE            MyFindPropertyOfWindowObjectAccessor :=                                                         kErrorPropNotFound;    END    ELSE        MyFindPropertyOfWindowObjectAccessor :=                                                         kKeyFormNotSupported;END; The MyFindPropertyOfWindowObjectAccessor function takes a token that identifies a window and creates a token that identifies the requested property of that window. See Figure 6-6 on page 6-40 for an illustration of the logical organization of a token of descriptor type typeMyWindowProp.This simplified example merely translates information about the requested property and the window to which it belongs into the form of a token of type typeMyWindowProp. This token can then be used by Apple event handlers to identify the corresponding window and its property, so that a handler can either retrieve the value of the property (for example, a Get Data handler) or change the value of the property (for example, a Set Data handler). Like other tokens, a token that identifies a property should always contain a reference to the corresponding property and the object to which it belongs—not a copy of the data for that object’s property. Defining TokensIt is up to you to decide how many token descriptor types you need to define for your application. In many cases you may be able to define one token that can identify Apple event objects of several different object classes, such as a token of type typeMyTextToken that identifies Apple event objects of object classes cText, cWord, cItem, and cChar. In other cases you may need to define specific token descriptor types for specific object classes.For example, the MyFindDocumentObjectAccessor routine shown in Listing 6-5 on page 6-30 returns a token of descriptor type typeMyDocToken, which identifies a document record.CONST                                             {application-defined token}    typeMyDocToken                            = 'docr';             {identifies a document record}Figure 6-5 shows the logical arrangement of a descriptor record of descriptor type typeMyDocToken whose data is specified by a pointer to a document record.Figure 6-5    Descriptor record for an application-defined token that identifies a documentThe MyFindPropertyOfWindowObjectAccessor routine shown in Listing 6-9 returns a token of descriptor type typeMyWindowProp for every property that it can locate.CONST                                             {application-defined token}    typeMyWindowProp                            = 'wprp';             {a window pointer and a }                                             { property ID}Figure 6-6 shows the logical arrangement of a descriptor record of descriptor type typeMyWindowProp that identifies the bounds property of a window. Its data consists of a window pointer and the constant pBounds. The application can use this token either to return or to change the window’s bounds setting, depending on the Apple event that specified the property. If the token specified pName instead, the application could use it either to return the window’s name as a string or to change the window’s name.Figure 6-6    Descriptor record for an application-defined token that identifies the pbounds property of a windowA token’s data should always contain a reference to the corresponding Apple event objects—not a copy of the data for those objects. This allows the same token to be used for both reading and writing tokens.It’s often possible to use the same token type for objects of several object classes, or for both an object of a given class and one of its properties. A token’s data is private to your application and can be organized in any way that is convenient.When an object accessor function that supports key form formRange locates a range of Apple event objects, it should normally return a descriptor list (AEDescList) of tokens for the individual objects. A typical exception is an object accessor function that returns a range of objects of class cText, which should return a single token representing the entire range. For example, an object accessor function that finds “all the characters from char 1 to char 1024” should return a token that consists of a list of 1024 objects, each of class cChar, whereas an object specifier function that finds “all the text from char 1 to char 1024” should return a single token for a single item of class cText that is 1024 characters long. A token is valid only until the Apple Event Manager has located the requested element in the container the token represents and returned another token for the element. The Apple Event Manager disposes of intermediate tokens after it finishes resolving an object specifier record, but one token is always left over—the token that identifies the specified Apple event object or objects. Your application should dispose of this final token by calling the AEDisposeToken function, which in turn calls your application’s token disposal function (if one exists), an optional object callback function that disposes of a token. See page 6-99 for the declaration of a token disposal function. If your application does not provide a token disposal function, the Apple Event Manager uses the AEDisposeDesc function to dispose of tokens. This function does the job as long as disposing of tokens involves nothing more than simply disposing of a descriptor record. Otherwise, you need to provide a custom token disposal function. For example, suppose the data field of a token descriptor record contains a handle to a block that in turn contains references to memory for the Apple event object referred to by the token. In this case, the application should provide a token disposal function that performs the tasks required to dispose of the token and any associated structures.  Handling Whose TestsIf your application provides an object-counting function and an object-comparison function in addition to the appropriate object accessor functions, the Apple Event Manager can resolve object specifier records that specify formTest without any other assistance from your application. The Apple Event Manager translates object specifier records of key form formTest into object specifier records of key form formWhose. This involves collapsing the key form and key data from two object specifier records in a container hierarchy into one object specifier record with the key form formWhose. Some applications may find it more efficient to translate whose tests into their own query languages rather than letting the Apple Event Manager handle the tests. This is useful only for applications that can make use of a test combined with either an absolute position or a range to locate objects. If you want the Apple Event Manager to let your application handle whose tests, set the kAEIDoWhose flag in the callbackFlags parameter of the AEResolve function. If for any reason one of your application’s object accessor functions chooses not to handle a particular whose descriptor record, it should return errAEEventNotHandled as the result code, and the Apple Event Manager will try again using the original object specifier records, just as if the kAEIDoWhose flag were not set.The key data for formWhose is specified by a whose descriptor record, which is a coerced AE record of descriptor type typeWhoseDescriptor. The data for a whose descriptor record consists of the two keyword-specified descriptor records shown in Table 6-5.   Table 6-5    Keyword-specified descriptor records for typeWhoseDescriptorKeyword    Descriptor type    Data    keyAEIndex    typeLongInteger     Offset of requested element in group of elements that pass a test          typeAbsoluteOrdinal    kAEFirstkAEMiddlekAELastkAEAnykAEAll        typeWhoseRange    Whose range descriptor record    keyAETest    typeCompDescriptor    Comparison descriptor record         typeLogicalDescriptor    Logical descriptor record    A whose descriptor record is never created directly by an application. The Apple Event Manager creates a whose descriptor record whenever an object specifier record of key form formTest is used to describe the container for elements described by an object specifier record of key form formAbsolutePosition or formRange, with some exceptions as noted in this section. For example, Figure 6-3 on page 6-18 shows four object specifier records that show the container hierarchy for the first row that meets a test in the table “MyAddresses” of the database “SurfDB.” The top two object specifier records in that figure use the key forms formAbsolutePosition and formTest to describe elements in a container. When it receives these two object specifier records, the Apple Event Manager collapses them into one, as shown in Figure 6-7. It then calls the application’s object-counting function to find out how many objects of class cRow the table contains and the object-comparison function to test the rows in the table until it finds the first row that passes the test. Figure 6-7    A container hierarchy created by the Apple Event Manager using a whose descriptor recordIf the elements to be tested are described by an object specifier record of key form formAbsolutePosition or formRange but are not of the same object class as their container, the Apple Event Manager cannot collapse the existing object specifier records into a whose descriptor record. Instead, the Apple Event Manager creates a whose descriptor record as if a third object specifier record of key form formAbsolutePosition and kAEAll were inserted between the object specifier record for the container and that for the tested elements. For example, the Apple Event Manager would interpret a request for “character 1 of word whose first letter = ‘a’” as “character 1 of every word whose first letter = ‘a’”.When an object specifier record of key form formTest is used to describe the container for elements described by an object specifier record of key form formRange, the Apple Event Manager will, under certain conditions, coerce the corresponding range descriptor record to a whose range descriptor record, which is a coerced AE record of typeWhoseRange. The data for a whose range descriptor record consists of two keyword-specified descriptor records with the descriptor types and data shown in Table 6-6. Table 6-6    Keyword-specified descriptor records for typeWhoseRangeKeyword    Descriptor type    Data    keyAEWhoseRangeStart    typeLongInteger     Offset of beginning of range        typeAbsoluteOrdinal    kAEFirstkAEMiddlekAELastkAEAnykAEAll    keyAEWhoseRangeStop    typeLongInteger     Offset of end of range        typeAbsoluteOrdinal    kAEFirstkAEMiddlekAELastkAEAnykAEAll     A whose range descriptor record describes the absolute position of the boundary elements, within the set of all elements that pass a test, that identify the beginning and end of the desired range.The Apple Event Manager coerces a range descriptor record to a whose range descriptor record if the specified container and its elements are of the same class, if the container for the specified range of elements is a group of Apple event objects that pass a test, and if the boundary objects in the original range descriptor record meet these conditions: n    Both boundary objects are of the same object class as the Apple event objects in the range they specify.n    The object specifier record for each boundary object specifies its container with a descriptor record of descriptor type typeCurrentContainer.n    The object specifier record for each boundary object specifies a key form of formAbsolutePosition. If these conditions are not met, the Apple Event Manager doesn’t create a whose range descriptor record. Instead, as described earlier in this section, the Apple Event Manager creates a whose descriptor record as if the original request specified every element that passed the test.If your application sets the kAEIDoWhose flag in the callbackFlags parameter of AEResolve, you should provide object accessor functions that can handle formWhose. These functions should coerce the whose descriptor record specified as key data for an object specifier record to an AE record and extract the data from the AE record by calling the AEGetKeyPtr and AEGetKeyDesc functions. If the keyword-specified descriptor record with the keyword keyAEIndex specifies descriptor type typeWhoseRange, your object accessor function must also coerce that descriptor record to an AE record and extract the data. Your object accessor function should then attempt to locate the requested objects and, if successful, return a token that identifies them.If your application sets the kAEIDoWhose flag and attempts to resolve every whose descriptor record it receives, the Apple Event Manager does not attempt to resolve object specifier records of any key form. The object-counting and object-comparison functions are never called, and your application is solely responsible for determining the formats and types of all tokens.  Writing Object Callback FunctionsIf an Apple event parameter consists of an object specifier record, your handler for the Apple event typically calls AEResolve to begin the process of locating the requested Apple event object or objects. In turn, AEResolve calls object accessor functions and, if necessary, object callback functions provided by your application.Every application that supports Apple event objects should provide object accessor functions that can locate Apple event objects belonging to any of the supported object classes. For an overview of the way AEResolve calls object accessor functions to locate Apple event objects described by object specifier records, see “Resolving Object Specifier Records,” which begins on page 6-4.In addition to object accessor functions, your application can provide up to seven object callback functions:n    An object-counting function counts the number of elements of a specified class in a specified container, so that the Apple Event Manager can determine how many elements it must examine to find the element or elements that pass a test. Your application must provide one object-counting function to handle object specifier records that specify tests. (See “Writing an Object-Counting Function,” which begins on page 6-48.)n    An object-comparison function compares one element either to another element or to a descriptor record and returns either TRUE or FALSE. Your application must provide one object-comparison function to handle object specifier records that specify tests. (See “Writing an Object-Comparison Function” on page 6-50.)n    A token disposal function disposes of a token after your application calls the AEDisposeToken function. If your application doesn’t provide a token disposal function, the Apple Event Manager uses the AEDisposeDesc function instead. Your application must provide a token disposal function if it requires more than a call to AEDisposeDesc to dispose of one of its tokens. This is true, for example, if your application supports marking by modifying its own data structures. (See page 6-99 for the declaration of a token disposal function.)n    An error callback function gives the Apple Event Manager an address to which to write the descriptor record it is currently working with if an error occurs while AEResolve is attempting to resolve an object specifier record. Your application is not required to provide an error callback function. (See page 6-100 for the declaration of an error callback function.)n    Three marking callback functions are used by the Apple Event Manager to get a mark token from your application, to mark specific Apple event objects, and to pare down a group of marked Apple event objects. Your application must provide all three marking functions if it supports marking. (See “Writing Marking Callback Functions” on page 6-53.)To make your object callback functions available to the Apple Event Manager, use the AESetObjectCallbacks function: myErr := AESetObjectCallbacks (@MyCompareObjects,                                         @MyCountObjects, @MyDisposeToken,                                         @MyGetMarkToken, @MyMark,                                          @MyAdjustMarks, @MyGetErrDesc);Each parameter to the AESetObjectCallbacks function consists of either a pointer to the corresponding application-defined function or NIL if no function is provided. The AESetObjectCallbacks function sets object callback functions that are available only to your application. To set system object callback functions, which are available to all applications and processes running on the same computer, use the AEInstallSpecialHandler function as described on page 4-100.To handle object specifier records that specify tests, your application must provide an object-counting function and an object-comparison function. The Apple Event Manager calls your application’s object-counting function to determine the number of Apple event objects in a specified container that need to be tested. The Apple Event Manager calls your application’s object-comparison function when it needs to compare one Apple event object to either another Apple event object or to a value in a descriptor record.If your application does not provide a token disposal function, the Apple Event Manager uses the AEDisposeDesc function to dispose of tokens. This function does the job as long as disposing of tokens involves nothing more than simply disposing of a descriptor record. Otherwise, you need to provide custom token disposal function. For example, suppose the data field of a token descriptor record contains a handle to a block that in turn contains references to storage for the Apple event object referred to by the token. In this case, the application can provide a token disposal function that performs the tasks required to dispose of the token and any associated structures.  Whenever more than one Apple event object passes a test, AEResolve can either return a list of tokens or make use of a target application’s ability to mark its own objects. Sometimes a list of tokens can become unmanageably large. For example, if a Get Data event asks for the names and addresses of all customers with a specified zip code who have purchased a specified product, the object accessor function that locates all the customers with the specified zip code might return a list of many thousands of tokens; the elements identified by those tokens would then have to be tested for the specified product. However, if your application uses some method of marking objects, you can choose simply to mark the requested objects rather than returning a list of tokens. “Writing Marking Callback Functions” on page 6-53 describes how to do this. If your application supports marking by modifying its own data structures, you must provide a token disposal function. When one of your application’s Apple event handlers calls the AEResolve function, the handler should pass a value in the callbackFlags parameter that specifies whether your application supports whose descriptor records or provides marking callback functions. You can add the following constants, as appropriate, to provide a value for the callbackFlags parameter: CONST kAEIDoMinimum                            =    $0000; {does not handle whose tests or }                                            { provide marking callbacks}        kAEIDoWhose                    =    $0001; {supports key form formWhose}        kAEIDoMarking                    =    $0004; {provides marking functions}For example, this code instructs the Apple Event Manager to call any marking functions previously set with the AESetObjectCallbacks function while resolving the object specifier record in the objectSpecifier parameter:VAR    objectSpecifier:    AEDesc;    resultToken:        AEDesc;    myErr:              OSErr;myErr := AEResolve(objectSpecifier, kAEIDoMarking, resultToken); If any of the marking callback functions are not installed, AEResolve returns the error errAEHandlerNotFound.IMPORTANTIf your application doesn’t specify kAEIDoWhose, the Apple Event Manager attempts to resolve all object specifier records of key form formTest. To do so, the Apple Event Manager uses your application’s object-counting and object-comparison functions, and returns a token of type typeAEList.If your application does specify kAEIDoWhose, the Apple Event Manager does not attempt to resolve object specifier records of any key form. In this case, the object-counting and object-comparison functions are never called; your application determines the formats and types of all tokens; and your application must interpret whose descriptor records created by the Apple Event Manager during the resolution of object specifier records. For more information, see “Handling Whose Tests,” which begins on page 6-41.sWriting an Object-Counting FunctionTo handle object specifier records that specify tests, your application should provide an object-counting function (unless it specifies kAEIDoWhose as just described). Your object-counting function should be able to count the number of elements of a given object class in a given container. For example, if your application supports Apple event objects that belong to the object class cText in the Text suite, your application should provide an object-counting function that can count Apple event objects of each element class listed in the definition of cText in the Apple Event Registry: Standard Suites. In this case, your application should provide an object-counting function that can count the number of words, items, or characters in a text object.You specify your object-counting function with the AESetObjectCallbacks function. Whenever it is resolving an object specifier record and it requires a count of the number of elements in a given container, the Apple Event Manager calls your object-counting function.Here’s the declaration for a sample object-counting function:FUNCTION MyCountObjects (desiredClass: DescType;                                  containerClass: DescType;                                 containerToken: AEDesc;                                  VAR result: LongInt): OSErr;The Apple Event Manager passes the following information to your object-counting function: the object class ID of the Apple event objects to count, the object class of their container, and a token identifying their container. (The container class can be useful if you want to use one token type for several object classes.) Your object-counting function uses this information to count the number of Apple event objects of the specified object class in the specified container. After counting the Apple event objects, your application should return the noErr result code and, in the result parameter, the number of Apple event objects counted. Listing 6-10 shows an application-defined function, MyCountObjects, that counts the number of objects for any object class supported by the application. Listing 6-10    An object-counting functionFUNCTION MyCountObjects (desiredClass: DescType; containerClass: DescType;                                  containerToken: AEDesc; VAR result: LongInt): OSErr;VAR    window: WindowPtr;BEGIN    result := 0;    IF desiredClass = cWindow THEN    BEGIN        IF containerClass = typeNull THEN        BEGIN            {count the number of windows}            window := FrontWindow;            WHILE window <> NIL DO                 BEGIN                    result := result + 1;                    window := WindowPtr(WindowPeek(window)^.nextWindow);                END; {of while}        END;         MyCountObjects := noErr;    END {of cWindow}    ELSE        IF desiredClass = cWord THEN            {count the number of words in the container}            MyCountObjects := MyCountWords(containerClass, containerToken,                                                         result)    ELSE        IF desiredClass =     cParagraph THEN            {count the number of paragraphs in the container}            MyCountObjects := MyCountParas(containerClass, containerToken,                                                         result)    ELSE        {this app does not support any other object classes}        MyCountObjects := kObjectClassNotFound;END;  Writing an Object-Comparison FunctionTo handle object specifier records that specify tests, your application should provide an object-comparison function (unless it specifies kAEIDoWhose as described on page 6-48). Your object-comparison function should be able to compare one Apple event object to another Apple event object or to another descriptor record. You specify your object-comparison function with the AESetObjectCallbacks function. Whenever it is resolving object specifier records and needs to compare the value of an Apple event object with another object or with data, the Apple Event Manager calls your object-comparison function.Here’s the declaration for a sample object-comparison function:FUNCTION MyCompareObjects (comparisonOperator: DescType;                                     object: AEDesc;                                    objectOrDescToCompare: AEDesc;                                     VAR result: Boolean): OSErr;The Apple Event Manager passes the following information to your object-comparison function: a comparison operator that specifies how the two objects should be compared, a token for the first Apple event object, and either a token that describes the Apple event object to compare or a descriptor record.It is up to your application to interpret the comparison operators it receives. The meaning of comparison operators differs according to the Apple event objects being compared, and not all comparison operators apply to all object classes. After successfully comparing the Apple event objects, your object-comparison function should return the noErr result code and, in the result parameter, a Boolean value specifying TRUE if the result of the comparison is true and FALSE otherwise. If for any reason your comparison function is unable to compare the specified Apple event objects, it should return the result code errAEEventNotHandled; then the Apple Event Manager will try an alternative method of comparing the Apple event objects, such as calling the equivalent system object-comparison function, if one exists.Your object-comparison function should be able to compare an Apple event object belonging to any object class with another Apple event object. Your function should also be able to compare two Apple event objects with different object classes, if appropriate. For example, an object-comparison function for a word-processing application might be asked to compare the First Name column of a specified row in a table with the first word on a specified page—that is, to compare an Apple event object of object class cColumn with an Apple event object of object class cWord. You must decide what kinds of comparisons make sense for your application.The Apple Event Registry: Standard Suites defines standard comparison operators. Here is a list of the constants that correspond to these comparison operators:CONST     kAEGreaterThan                            = '>   ';    kAEGreaterThanEquals                            = '>=  ';    kAEEquals                            = '=   ';        kAELessThan                            = '<   ';    kAELessThanEquals                            = '<=  ';    kAEBeginsWith                            = 'bgwt';    kAEEndsWith                            = 'ends';     kAEContains                            = 'cont';         The comparison operators always relate the first operand to the second. For example, the constant kAEGreaterThan means that the object-comparison function should determine whether or not the value of the first operand is greater than the value of the second operand. For more information, see page 6-90.Listing 6-11 shows an application-defined function, MyCompareObjects, that compares two Apple event objects of any object class supported by the application. Listing 6-11    Object-comparison function that compares two Apple event objectsFUNCTION MyCompareObjects (comparisonOperator: DescType;                                     theObject: AEDesc;                                    objectOrDescToCompare: AEDesc;                                     VAR result: Boolean): OSErr;BEGIN    result := FALSE;    {compare two objects for equivalence}    IF comparisonOperator =                         kAEEquals THEN        MyCompareObjects := MyCompEquals(theObject,                                                     objectOrDescToCompare,                                                     result)    ELSE        {compare two objects for greater than}        IF comparisonOperator =                         kAEGreaterThan THEN            MyCompareObjects := MyCompGreaterThan(theObject,                                                         objectOrDescToCompare,                                                        result)    ELSE        {compare two objects for less than}        IF comparisonOperator =                         kAELessThan THEN            MyCompareObjects := MyCompLessThan(theObject,                                                         objectOrDescToCompare,                                                        result)    ELSE    {this app does not support any other comparison operators}        MyCompareObjects := errAEEventNotHandled;END;The MyCompareObjects function calls a separate application-defined routine for each comparison operator. In each case, the application-defined routine that actually performs the comparison can compare an Apple event object with either another Apple event object or with a descriptor record’s data. If for any reason the comparison cannot be performed, the MyCompareObjects function returns the result code errAEEventNotHandled.  Writing Marking Callback FunctionsMarking callback functions allow applications such as databases that can mark their own objects to take advantage of that capability when resolving object specifier records. Instead of returning a list of tokens for a group of Apple event objects that pass a test, your application can simply mark the Apple event objects and return a token that identifies how they have been marked. In this way, you can speed the resolution of complex object specifier records and reduce the amount of memory you need to allocate for tokens. The use of marking callback functions is optional and usually makes sense if (a) you can reasonably expect that the tokens created in the process of resolving some object specifier records might not all fit in memory at once or (b) your application already uses a marking mechanism. If you want the Apple Event Manager to use marking callback functions provided by your application, you must add the kAEIDoMarking constant to the value of the callbackFlags parameter for the AEResolve function. If for any reason your application cannot mark a requested set of Apple event objects, it should return errAEEventNotHandled as the result code, and the Apple Event Manager will attempt to continue resolving the object specifier record by some other method, such as using a system marking function, if one exists. If your application supports marking callback functions, it must provide three functions with declarations that match these examples:FUNCTION MyGetMarkToken (containerToken: AEDesc;                                  containerClass: DescType;                                  VAR Result: AEDesc): OSErr;FUNCTION MyMark (theToken: AEDesc; markToken: AEDesc;                       markCount: LongInt): OSErr;FUNCTION MyAdjustMarks (newStart, newStop: LongInt;                                 markToken: AEDesc): OSErr;For more detailed information about these sample declarations, see “Object Callback Functions,” which begins on page 6-96.To resolve a given object specifier record with the aid of the marking callback functions provided by your application, the Apple Event Manager first calls your application’s mark token function (MyGetMarkToken), passing a token that identifies the container of the elements to be marked in the containerToken parameter and the container’s object class in the containerClass parameter. The mark token function returns a mark token. A mark token, like other tokens, can be a descriptor record of any type; however, unlike other tokens, it identifies the way your application marks Apple event objects during the current session while resolving a single test. A mark token does not identify a specific Apple event object; rather, it allows your application to associate a group of objects with a marked set.After it receives the mark token, the Apple Event Manager can call your application’s object-marking function (MyMark) repeatedly to mark specific Apple event objects. The Apple Event Manager passes the following information to your marking function: in the theToken parameter, a token for the object to be marked (obtained from the appropriate object accessor function); in the markToken parameter, the current mark token; and in the markCount parameter, the mark count. The mark count indicates the number of times the Apple Event Manager has called the marking function for the current mark token. Your application should associate the mark count with each Apple event object it marks. When the Apple Event Manager needs to identify either a range of elements or the absolute position of an element in a group of Apple event objects that pass a test, it can use your application’s mark-adjusting function (MyAdjustMarks) to unmark objects that it has previously marked. For example, suppose an object specifier record specifies “any row in the table ‘MyCustomers’ for which the City column is ‘San Francisco.’” The Apple Event Manager first uses the appropriate object accessor routine to locate all the rows in the table for which the City column is “San Francisco” and calls the application’s marking function repeatedly to mark them. It then generates a random number between 1 and the number of rows it found that passed the test and calls the application’s mark-adjusting function to unmark all the rows whose mark count does not match the randomly generated number. If the randomly chosen row has a mark count value of 5, the Apple Event Manager passes the mark-adjusting function 5 in both the newStart parameter and the newStop parameter, and the current mark token in the markToken parameter. The newStart and newStop parameters identify the beginning and end of the new set of marked objects that the mark-adjusting function will create by unmarking those previously marked objects not included in the new set. When the Apple Event Manager calls your mark-adjusting function, your application must dispose of any data structures that it may have created to mark the previously marked objects. The Apple Event Manager calls your mark-adjusting function only once for a given mark token. A mark token is valid until the Apple Event Manager either disposes of it (by calling AEDisposeToken) or returns it as the result of the AEResolve function. If the final result of a call to the AEResolve function is a mark token, the Apple event objects currently marked for that mark token are those specified by the object specifier record passed to AEResolve, and your application can proceed to do whatever the Apple event has requested. Note that your application is responsible for disposing of a final mark token with a call to AEDisposeToken, just as for any other final token.If your application supports marking, it should also provide a token disposal function. When the Apple Event Manager calls AEDisposeToken to dispose of a mark token that is not the final result of a call to AEResolve, the subsequent call to your token disposal function lets you know that you can unmark the Apple event objects marked with that mark token. A call to AEDisposeDesc to dispose of a mark token (which would occur if you did not provide a token disposal function) would leave the objects marked.   Creating Object Specifier RecordsIf your application creates and sends Apple events that require the target application to locate Apple event objects, your application must create object specifier records for those events. This section describes how to use the four keyword-specified descriptor records described in “Descriptor Records Used in Object Specifier Records,” which begins on page 6-8, to specify the object class ID, container, key form, and key data for an object specifier record. Because the internal structure of an object specifier record is nearly identical to the internal structure of an AE record, it is possible to use AECreateList, AEPutPtr, and AEPutKeyDesc to add the four keyword-specified descriptor records to an AE record, then use AECoerceDesc to coerce the AE record to a descriptor record of type typeObjectSpecifier. However, it is usually preferable to use the CreateObjSpecifier function to accomplish the same goal. The CreateObjSpecifier function adds the keyword-specified descriptor records directly to an object specifier record, thus eliminating several steps that are required if you create an AE record first. The instructions that follow make use of CreateObjSpecifier. To specify the class ID for an object specifier record, your application can specify the appropriate class ID value as the desiredClass parameter for the CreateObjSpecifier function, which uses it to create a keyword-specified descriptor record with the keyword keyAEDesiredClass as part of an object specifier record. To specify the container for an object specifier record, your application must create a keyword-specified descriptor record with the keyword keyAEContainer that fully describes the container of the Apple event object. Because this container is usually another Apple event object, the container is usually specified by another object specifier record. To specify the complete container hierarchy of an Apple event object, your application must create a series of nested object specifier records, starting with the object specifier record for the Apple event object whose container is outermost. With the exception of this first object specifier record, each object specifier record specifies another object specifier record in the chain as a container. For example, Figure 6-2 on page 6-10 shows a series of nested object specifier records that specify the first row of a table named “Summary of Sales” in a document named “Sales Report.” The logical organization of the same object specifier records is summarized in Table 6-7.Table 6-7    Nested object specifier records that describe a container hierarchyKeyword    Descriptor type    Data    keyAEDesiredClass    typeType    cRow    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cTable    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cDocument    keyAEContainer    typeNull    Data handle is NIL    keyAEKeyForm    typeEnumerated    formName    keyAEKeyData    typeChar    "Sales Report"    keyAEKeyForm    typeEnumerated    formName    keyAEKeyData    typeChar    "Summary of Sales"    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    1    NoteThe format used in Table 6-7 and similar tables throughout this chapter does not show the structure of nested object specifier records as they exist within an Apple event. Instead, this format shows what you would obtain after calling AEGetKeyDesc repeatedly to extract the object specifier records from an Apple event record.When you call AEGetKeyDesc to extract a null descriptor record, AEGetKeyDesc returns a descriptor record of type AEDesc with a descriptor type of typeNull and a data handle whose value is 0.uTo specify the default container for an object specifier record (such as the container for the document in Table 6-7), you can use AECreateDesc to create a null descriptor record, which you can then pass in the theContainer parameter of the CreateObjSpecifier function. The CreateObjSpecifier function uses the null descriptor record to create a keyword-specified descriptor record with the keyword keyAEContainer as part of an object specifier record. The object specifier record that specifies the default container is always the first record you create in a series of nested object specifier records that specifies the complete container hierarchy for an Apple event object. Each one in the series uses the previously created object specifier record to specify its container. As with the null descriptor record, you can pass an object specifier record as the second parameter to the CreateObjSpecifier function, which uses it to create a keyword-specified descriptor record with the keyword keyAEContainer.To specify the key form for an object specifier record, your application can specify a key form constant as the third parameter to the CreateObjSpecifier function, which uses it to create a keyword-specified descriptor record with the keyword keyAEKeyForm as part of an object specifier record. The standard key forms for object specifier records are summarized in Table 6-1 on page 6-12.For example, the key form for the object specifier records in Table 6-7 that specify the document and the table is formName. In other words, the key data identifies the document and the table by their names. Similarly, the key form for the object specifier record in Table 6-7 that specifies the first row in the table is formAbsolutePosition. In other words, the key data identifies the position of the row compared to other rows in the same container.To specify the key data for an object specifier record, your application must create a keyword-specified descriptor record with the keyword keyAEKeyData whose data handle refers to the appropriate data for the specified key form. You can use AECreateDesc, CreateCompDescriptor, CreateLogicalDescriptor, and related functions to create the descriptor record, which you can then pass in the fourth parameter of the CreateObjSpecifier function. The CreateObjSpecifier function uses this descriptor record to create a keyword-specified descriptor record with the keyword keyAEKeyData as part of an object specifier record.Creating a Simple Object Specifier RecordThis section shows how to use the CreateObjSpecifier function to create the object specifier record shown in Table 6-7. The CreateObjSpecifier function creates the necessary keyword-specified descriptor records for the class ID, container, key form, and key data and returns the resulting object specifier record as a descriptor record of type typeObjectSpecifier.Listing 6-12 shows how the CreateObjSpecifier function creates an object specifier record from parameters that an application specifies.Listing 6-12    Creating an object specifier record using CreateObjSpecifierVAR    desiredClass:                             DescType;     myObjectContainer:                             AEDesc;     myKeyForm:                             DescType;     myKeyDataDesc:                             AEDesc;     disposeInputs:                             Boolean;     myObjSpecRec:                             AEDesc;    myErr:                            OSErr;desiredClass := cRow;myObjectContainer := MyGetContainer;myKeyForm := formAbsolutePosition;myKeyDataDesc := MyGetKeyData;disposeInputs := TRUE;{create an object specifier record}myErr := CreateObjSpecifier(desiredClass, myObjectContainer,                                         myKeyForm, myKeyDataDesc,                                         disposeInputs, myObjSpecRec);The code shown in Listing 6-12 demonstrates how an application might use the CreateObjSpecifier function to create four keyword-specified descriptor records as part of a descriptor record of type typeObjectSpecifier. The CreateObjSpecifier function returns a result code of noErr if the object specifier record was successfully created. The object specifier record returned in the myObjSpecRec parameter describes an Apple event object of the class specified by the desiredClass parameter, located in the container specified by the myObjectContainer parameter, with the key form specified by the myKeyForm parameter and key data specified by the myKeyDataDesc parameter. You can specify TRUE in the disposeInputs parameter if you want the CreateObjSpecifier function to dispose of the descriptor records you created for the myObjectContainer and myKeyDataDesc parameters. If you specify FALSE, then your application is responsible for disposing of these leftover descriptor records. Listing 6-13 shows an application-defined function that uses CreateObjSpecifier to create an object specifier record for the first row in the table named “Summary of Sales” in the document “Sales Report,” then uses the object specifier record returned in the myObjSpecRec parameter as the direct parameter for a Get Data event. Listing 6-13    Using CreateObjSpecifier in an application-defined functionFUNCTION MyRequestRowFromTarget (targetAddress: AEAddressDesc;                                             VAR reply: AppleEvent): OSErr;VAR    desiredClass:                                 DescType;    myKeyForm:                                DescType;    myObjectContainer:                                AEDesc;    myObjSpecRec:                                 AEDesc;    myKeyDataDesc:                                AEDesc;    keyData:                                LongInt;    theAppleEvent:                                AppleEvent;    myErr:                                OSErr;    ignoreErr:                                OSErr;BEGIN    {initialize (set to null descriptor records) the two descriptor records }     { that must eventually be disposed of}    MyInit2DescRecs(myObjSpecRec, theAppleEvent);    desiredClass := cRow;                                                        {specify the class}                                                            {specify container for the row}    myErr := MyCreateTableContainer(myObjectContainer,                                                 'Summary of Sales', 'Sales Report');    IF myErr = noErr THEN     BEGIN        myKeyForm := formAbsolutePosition;                                                    {specify the key form}        keyData := 1;                                                    {specify the key data for row}        myErr := AECreateDesc(typeLongInteger, @keyData, Sizeof(keyData),                                         myKeyDataDesc);        IF myErr = noErr THEN            {create the object specifier record}            myErr := CreateObjSpecifier(desiredClass, myObjectContainer,                                                     myKeyForm, myKeyDataDesc,                                                     TRUE, myObjSpecRec);        IF myErr = noErr THEN            {myObjSpecRec now describes an Apple event object, and will become }             { direct parameter of a Get Data event; first create Get Data event}            myErr := AECreateAppleEvent(kAECoreSuite, kAEGetData, targetAddress,                                                     kAutoGenerateReturnID,                                                     kAnyTransactionID, theAppleEvent);        IF myErr = noErr THEN            {add myObjSpecRec as the direct parameter of the Get Data event}            myErr := AEPutParamDesc(theAppleEvent, keyDirectObject,                                            myObjSpecRec);        IF myErr = noErr THEN            myErr := AESend(theAppleEvent, reply, kAEWaitReply +                                  kAENeverInteract, kAENormalPriority, 120,                                  @MyIdleFunction, NIL);    END;    ignoreErr := AEDisposeDesc(myObjSpecRec);    ignoreErr := AEDisposeDesc(theAppleEvent);    MyRequestRowFromTarget := myErr;END;The MyRequestRowFromTarget function shown in Listing 6-13 specifies the class ID as cRow, indicating that the desired Apple event object is a row in a table. It uses the application-defined function MyCreateTableContainer to create an object specifier record for the table that contains the row, passing “Summary of Sales” and “Sales Report” as the second and third parameters to identify the name of the table and the name of the document that contains the table. (The next section, “Specifying the Container Hierarchy,” explains how to construct the MyCreateTableContainer function.) It then specifies the key form as the constant formAbsolutePosition, which indicates that the key data specifies the position of the row within its container; sets the keyData variable to 1, indicating the first row, and uses AECreateDesc to create a descriptor record for the key data; and uses CreateObjSpecifier to create the object specifier record that describes the desired word.The desired row is now fully described by the myObjSpecRec variable, which contains a descriptor record of type typeObjectSpecifier that contains the three nested object specifier records shown in Table 6-7 on page 6-56. After using AECreateAppleEvent to create a Get Data event, the MyRequestRowFromTarget function uses the AEPutParamDesc function to add the myObjSpecRec variable to the Get Data event as a direct parameter, then uses AESend to send the Get Data event.Note that the MyRequestRowFromTarget function begins by using the application-defined function MyInit2DescRecs to set myObjSpecRec and theAppleEvent to null descriptor records. These two functions must be disposed of whether the function is successful or not. By setting them to null descriptor records, the function can dispose of them at the end regardless of where an error may have occurred.Specifying the Container HierarchyBecause the container for an object specifier record usually consists of a chain of other object specifier records that specify the container hierarchy, your application must create all the object specifier records in the chain, starting with the record for the outermost container. Listing 6-14 and Listing 6-15 demonstrate how to use the CreateObjSpecifier function to create the first two object specifier records in such a chain: the records for a document and a table. Listing 6-14    Specifying a document containerFUNCTION MyCreateDocContainer (VAR myDocContainer: AEDesc;                                         docName: Str255): OSErr;VAR    myDocDescRec:                    AEDesc;    nullDescRec:                     AEDesc;    myErr:                    OSErr;BEGIN    {create a descriptor record for the name of the document}    myErr := AECreateDesc(typeChar, @docName[1],                                      Length(docName), myDocDescRec);    IF myErr = noErr THEN        {create a null descriptor record}        myErr := AECreateDesc(typeNull, NIL, 0, nullDescRec);    IF myErr = noErr THEN        {create an object specifier record to specify the }        { document object}        myErr := CreateObjSpecifier(cDocument, nullDescRec,                                              formName, myDocDescRec, TRUE,                                              myDocContainer);    MyCreateDocContainer := myErr;END;The function MyCreateDocContainer in Listing 6-14 creates an object specifier record that identifies a document by name. It starts by using the AECreateDesc function to create two descriptor records: one of type typeChar for the name of the document, and one of type typeNull for the null descriptor record that specifies the default container (because the document is not contained in any other Apple event object). These two descriptor records can then be used as parameters for the CreateObjSpecifier function, which returns an object specifier record (that is, a descriptor record of type typeObjectSpecifier) in the myDocContainer variable. The object specifier record specifies an Apple event object of the object class cDocument in the container specified by the nullDescRec variable with a key form of formName and the key data specified by the myDocDescRec variable. This object specifier can be used by itself to specify a document, or it can be used to specify the container for another Apple event object.Listing 6-15 shows an application-defined function, MyCreateTableContainer, that creates an object specifier record describing a table contained in a document. Listing 6-15    Specifying a table containerFUNCTION MyCreateTableContainer (VAR myTableContainer: AEDesc;                                            tableName: Str255;                                            docName: Str255): OSErr;VAR    myDocDescRec:                            AEDesc;    myTableDescRec:                            AEDesc;    myErr:                            OSErr;BEGIN    {create a container for the document}    myErr := MyCreateDocContainer(myDocDescRec, docName);    IF myErr = noErr THEN    BEGIN        {create the table container, }        { first specify the descriptor record for the key data}        myErr := AECreateDesc(typeChar, @tableName[1],                                         Length(tableName), myTableDescRec);        IF myErr = noErr THEN            myErr := CreateObjSpecifier(cTable, myDocDescRec,                                                formName, myTableDescRec,                                                 TRUE, myTableContainer);    END;    MyCreateTableContainer := myErr;END;The function MyCreateTableContainer in Listing 6-15 starts by using the function MyCreateDocContainer from Listing 6-14 to create an object specifier record that identifies the table’s container—the document in which the table is located. Then it uses the AECreateDesc function to create a descriptor record for the key data—a name that, when combined with the key form formName, will identify the table in the document. The object specifier record for the document and the descriptor record specifying the table’s name are passed to the function CreateObjSpecifier. It returns an object specifier record in the myTableContainer parameter that specifies an Apple event object of the object class cTable in the container specified by the MyDocDescRec variable with a key form of formName and the key data specified by the myTableDescRec variable. This object specifier record can be used by itself to specify a table, or it can be used to specify the container for another Apple event object.Listing 6-13 uses the MyCreateTableContainer function shown in Listing 6-15 to specify the container hierarchy illustrated in Table 6-7 on page 6-56. The nested object specifier records shown in Table 6-7 use the key forms formName and formRelativePosition. You can create key data for the key forms formPropertyID, formUniqueID, and formRelativePosition using similar techniques.    Specifying a PropertyThe key form formPropertyID allows your application to specify key data identifying a property of the object specified as a container. For example, an object specifier record that identifies the font property of a word specifies cProperty as the class ID, an object specifier record for the word as the property’s container, formPropertyID as the key form, and the constant pFont as the key data. Note that an object specifier record that identifies a property does not include a value for the property, such as Palatino. The value of a property is returned or set as a parameter of an Apple event. For example, an application that sends a Get Data event to get the pFont property of a word receives a value such as Palatino in the keyAEResult parameter of the reply event, and an application that sends a Set Data event to change the pFont property of a word specifies a font in the keyAEData parameter of the Set Data event. To specify the key data for a key form of formPropertyID, your application must create a descriptor record of typeType whose data consists of a constant specifying a property. You can use AECreateDesc to create a descriptor record that specifies the constant for a property, then use CreateObjSpecifier to add the descriptor record to an object specifier record as a keyword-specified descriptor record with the keyword keyAEKeyData.For more information about object specifier records that specify a property, see “Key Data for a Property ID” on page 6-13.Specifying a Relative PositionThe key form formRelativePosition allows your application to specify key data identifying an element or a set of elements that are immediately before or after the specified container. For example, if the container is a table, you could use a key form of formRelativePosition to specify the paragraph before or after the table. To specify the key data for a key form of formRelativePosition, your application must create a descriptor record of typeEnumerated whose data consists of a constant specifying either the element after (kAENext) or the element before (kAEPrevious) the specified container.You can use AECreateDesc to create a descriptor record that specifies one of these constants, then use CreateObjectSpecifier to add it to an object specifier record as a keyword-specified descriptor record with the keyword keyAEKeyData.For more information about object specifier records that specify a relative position, see “Key Data for Relative Position” on page 6-15.   Creating a Complex Object Specifier RecordThis section describes how to create object specifier records that specify a test or a range. You can specify the object class ID for these object specifier records the same way you would for any other object specifier record. When you create the other three keyword-specified descriptor records, however, you can use additional Apple Event Manager routines and descriptor types to specify any combination of Apple event objects. Specifying a TestThe key form formTest allows your application to specify key data that identifies one or more elements in the specified container that pass a test. To do so, your application must construct several interconnected descriptor records that specify comparisons and, if necessary, logical expressions. For example, to specify “the first row in which the First Name column equals ‘John’ and the Last Name column equals ‘Chapman’ in the table ‘MyAddresses’ of the database ‘SurfDB,’” your application must construct an object specifier record whose key data describes a logical expression that applies the logical operator AND to two separate comparisons for each row: a comparison of the First Name column to the word “John” and a comparison of the Last Name column to the word “Chapman.” The logical organization of the data for the object specifier record that specifies this test is summarized in Table 6-8 and Table 6-9. (It is also illustrated in Figure 6-3 and Figure 6-4, beginning on page 6-18.) The listings in the remainder of this section demonstrate how to create this object specifier record. For general information about the organization of key data for a test, see “Key Data for a Test,” which begins on page 6-15.Table 6-8    Object specifier record for the first row that meets a test in the table named “MyAddresses”Keyword    Descriptor type    Data    keyAEDesiredClass    typeType    cRow    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cRow    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cTable    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cDatabase    keyAEContainer    typeNull    Data handle is NIL    keyAEKeyForm    typeEnumerated    formName    keyAEKeyData    typeChar    "SurfDB"    keyAEKeyForm    typeEnumerated    formName    keyAEKeyData    typeChar    "MyAddresses"    keyAEKeyForm    typeEnumerated    formTest    keyAEKeyData    typeLogicalDescriptor    (see Table 6-9)    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    1    Table 6-9    Logical descriptor record that specifies a testKeyword    Descriptor type    Data    keyAELogicalOperator    typeEnumerated    kAEAnd    keyAELogicalTerms    typeAEList    (see indented records)        typeCompDescriptor    (see indented record)    keyAECompOperator    typeType    kAEEquals    keyAEObject1    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cColumn    keyAEContainer    typeObjectBeingExamined    Data handle is NIL    keyAEKeyForm    typeEnumerated    formName    keyAEKeyData    typeChar    "First Name"    keyAEObject2    typeChar    "John"        typeCompDescriptor    (see indented record)    keyAECompOperator    typeType    kAEEquals    keyAEObject1    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cColumn    keyAEContainer    typeObjectBeingExamined    Data handle is NIL    keyAEKeyForm    typeEnumerated    formName    keyAEKeyData    typeChar    "Last Name"    keyAEObject2    typeChar    "Chapman"    Because both the database and the table shown in Table 6-8 are specified by name, it would be convenient to have an application-defined routine that creates an object specifier record that uses the key form formName. The MyCreateFormNameObjSpecifier function shown in Listing 6-16 can be used for this purpose.Listing 6-16    Creating an object specifier record with the key form formNameFUNCTION MyCreateFormNameObjSpecifier                                (class: DescType; container: AEDesc;                                  keyDataName: str255;                                  VAR resultObjSpecRec: AEDesc): OSErr;VAR    keyDataDescRec: AEDesc;    myErr:                      OSErr;BEGIN    myErr := AECreateDesc(typeChar, @keyDataName[1],                                      Length(keyDataName), keyDataDescRec);    IF myErr = noErr THEN        myErr := CreateObjSpecifier(class, container, formName,                                                keyDataDescRec, TRUE,                                                resultObjSpecRec);    MyCreateFormNameObjSpecifier := myErr;END;The MyCreateFormNameObjSpecifier function shown in Listing 6-16 returns, in the resultObjSpecRec parameter, an object specifier record that describes an Apple event object of the class specified by the class parameter, located in the container specified by the container parameter, with the key form formName and key data specified by the keyDataName parameter. This function is used in Listing 6-19 on page 6-70 to create object specifier records that use the key form formName for the database and the table. The nested object specifier records shown in Table 6-9 specify “the rows in which the First Name column equals ‘John’ and the Last Name column equals ‘Chapman.’” To identify the rows that pass this test, the Apple Event Manager needs to evaluate two comparisons: the comparison of each row of the First Name column to the word “John,” and the comparison of each row of the Last Name column to the word “Chapman.”The Apple Event Manager uses the information in comparison descriptor records to compare the specified elements in a container, one at a time, either to another Apple event object or to the data associated with a descriptor record. The two comparison descriptor records you need to create for this example are summarized in Table 6-9 on page 6-66. You can use the CreateCompDescriptor function to create a comparison descriptor record, or you can create an AE record and use AECoerceDesc to coerce it to a comparison descriptor record. Listing 6-17 shows an example of an application-defined routine that creates an object specifier record and a descriptor record of typeChar, then uses the CreateCompDescriptor function to add them to a comparison descriptor record. Listing 6-17    Creating a comparison descriptor recordFUNCTION MyCreateComparisonDescRec (VAR compDesc: AEDesc;                                                colName: str255;                                                 name: str255): OSErr;VAR    logicalContainer, colNameDesc, nameDesc:                                                         AEDesc;    myObjectExaminedContainer:                                                         AEDesc;    myErr:                                                        OSErr;BEGIN    {create the object specifier record for keyAEObject1; }    { first create container}    myErr := AECreateDesc(typeObjectBeingExamined, NIL, 0,                                    myObjectExaminedContainer);    {create key data}    IF myErr = noErr THEN        myErr := AECreateDesc(typeChar, @colName[1],                                     Length(colName), colNameDesc);    {now create the object specifier record}    IF myErr = noErr THEN        myErr := CreateObjSpecifier(cColumn,                                             myObjectExaminedContainer,                                              formName, colNameDesc, TRUE,                                             logicalContainer);    {create the descriptor record for keyAEObject2}    IF myErr = noErr THEN        myErr := AECreateDesc(typeChar, @name[1], Length(name),                                      nameDesc);    {create the first logical term (comp descriptor record)}    IF myErr = noErr THEN        myErr := CreateCompDescriptor(kAEEquals, logicalContainer,                                                nameDesc, TRUE, compDesc);    MyCreateComparisonDescRec := myErr;END; The MyCreateComparisonDescRec function takes two strings and uses them to create a comparison descriptor record. The string passed in the second parameter specifies the name of the column whose contents should be compared to the string passed in the third parameter. First, the MyCreateComparisonDescRec function uses AECreateDesc to create a descriptor record of typeObjectBeingExamined, which is returned in the variable myObjectExaminedContainer. Next, AECreateDesc creates a descriptor record of descriptor type typeChar, whose data consists of the string in the variable colName, and which is returned in the variable colNameDesc. The code then passes the variables myObjectExaminedContainer and colNameDesc to the CreateObjSpecifier function, which uses them to create an object specifier record, returned in the logicalContainer variable, that becomes the keyword-specified descriptor record with the keyword keyAEObject1.Next, the MyCreateComparisonDescRec function uses AECreateDesc and the name parameter to create the descriptor record for keyAEObject2, which AECreateDesc returns in the nameDesc variable. Finally, the code passes the constant kAEEquals, the variable logicalContainer, and the variable nameDesc to the CreateCompDescriptor function, which creates a comparison descriptor record that allows the Apple Event Manager (with the help of object-comparison functions provided by the server application) to determine whether the specified column in the row currently being checked equals the specified string. You can use the MyCreateComparisonDescRec function to create both the descriptor records of type typeCompDescriptor shown in Table 6-9 on page 6-66. These descriptor records provide two logical terms for a logical descriptor record. The entire logical descriptor record corresponds to the logical expression “the First Name column equals ‘John’ AND the Last Name column equals ‘Chapman.’”  You can use the CreateLogicalDescriptor function to create a logical descriptor record, or you can create an AE record and use the AECoerceDesc function to coerce it to a comparison descriptor record. Listing 6-18 shows an application-defined function that adds two comparison descriptor records to a descriptor list, then uses the CreateLogicalDescriptor function to create a logical descriptor record whose logical terms are the two comparison descriptor records.Listing 6-18    Creating a logical descriptor recordFUNCTION MyCreateLogicalDescRec (VAR compDesc1, compDesc2: AEDesc;                                            logicalOperator: DescType;                                            VAR logicalDesc: AEDesc): OSErr;VAR    logicalTermsList: AEDescList;    myErr:                         OSErr;BEGIN    {create a logical descriptor record that contains two }    { comparison descriptor records}    {first create a list}    myErr := AECreateList(NIL, 0, FALSE, logicalTermsList);    IF myErr = noErr THEN        myErr := AEPutDesc(logicalTermsList, 1, compDesc1);    IF myErr = noErr THEN        myErr := AEPutDesc(logicalTermsList, 2, compDesc2);    IF myErr = noErr THEN        myErr := AEDisposeDesc(compDesc1);    IF myErr = noErr THEN        myErr := AEDisposeDesc(compDesc2);    IF myErr = noErr THEN        myErr := CreateLogicalDescriptor(logicalTermsList,                                                    logicalOperator, TRUE,                                                    logicalDesc);    MyCreateLogicalDescRec := myErr;END;Listing 6-19 uses the application-defined functions shown in Listing 6-16, Listing 6-17, and Listing 6-18 to build the object specifier record illustrated in Table 6-8 and Table 6-9.  Listing 6-19    Creating a complex object specifier recordFUNCTION MyCreateObjSpecRec (VAR theResultObj: AEDesc): OSErr;VAR    nullContainer, databaseContainer, tableContainer:                                                                     AEDesc;    compDesc1, compDesc2:                                                                     AEDesc;    logicalTestDesc, rowTestContainer, rowOffset:                                                                     AEDesc;    myErr:                                                                     OSErr;BEGIN    {create a null container}    myErr := AECreateDesc(typeNull, NIL, 0, nullContainer);    {create a container for the database}    IF myErr = noErr THEN        myErr := MyCreateFormNameObjSpecifier(cDatabase, nullContainer,                                                          'SurfDB', databaseContainer);    {create a container for the table}    IF myErr = noErr THEN        myErr := MyCreateFormNameObjSpecifier(cTable, databaseContainer,                                                           'MyAddresses', tableContainer);    {create a container for the row--an object specifier record that }    { specifies a test (the row whose First Name column = 'John' and }    { Last Name column = 'Chapman')}    {create the first comparison descriptor record}    IF myErr = noErr THEN        myErr := MyCreateComparisonDescRec(compDesc1, 'First Name', 'John');     {create the second comparison descriptor record}    IF myErr = noErr THEN        myErr := MyCreateComparisonDescRec(compDesc2, 'Last Name', 'Chapman');     {create the logical descriptor record}    IF myErr = noErr THEN        myErr := MyCreateLogicalDescRec(compDesc1, compDesc2, kAEAND,                                                     logicalTestDesc);    {now create the object specifier record that specifies the test}    IF myErr = noErr THEN        myErr := CreateObjSpecifier(cRow, tableContainer, formTest,                                             logicalTestDesc, TRUE, rowTestContainer);    {create the object specifier record for the Apple event object}    {first, create the descriptor record for the key data}    IF myErr = noErr THEN        myErr := CreateOffsetDescriptor (1, rowOffset);    {now create the object specifier record}    IF myErr = noErr THEN        myErr := CreateObjSpecifier (cRow, rowTestContainer,                                                 formAbsolutePosition, rowOffset,                                                 TRUE, theResultObj);    MyCreateObjSpecRec := myErr;END;The MyCreateObjSpecRec function shown in Listing 6-19 begins by using AECreateDesc to create a null descriptor record, then uses the MyCreateFormNameObjSpecifier function (shown in Listing 6-16) to specify the default container for the database named “SurfDB.” The code then calls the MyCreateFormNameObjSpecifier function again, this time passing the object specifier record for SurfDB to specify the container for the table “MyAddresses.” The next two calls are both to the MyCreateComparisonDescRec function (shown in Listing 6-17), which creates the comparison descriptor records that allow the Apple Event Manager to compare the First Name column and Last Name column to the names “John” and “Chapman,” respectively. The next call passes these two comparison descriptor records to the MyCreateLogicalDescRec function (shown in Listing 6-18) in the compDesc1 and compDesc2 variables. Now all the components of the logical descriptor record are ready to assemble. The next call, to CreateObjSpecifier, specifies the logical descriptor record in the logicalTestDesc variable as the key data for the object specifier record that specifies the test. A call to the Apple Event Manager routine CreateOffsetDescriptor then creates an offset descriptor record that contains the integer 1. Finally, the code passes the offset descriptor record to the CreateObjSpecifier function in the rowOffset variable to create the final object specifier record, which describes the requested row as the first row that passes the test.The CreateOffsetDescriptor function creates a descriptor record of type typeLongInteger that can be used as the key data with a key form of formAbsolutePosition to indicate an element’s offset within its container. A positive integer indicates an offset from the beginning of the container (the first element has an offset of 1), and a negative integer indicates an offset from the end of the container (the last element has an offset of –1). Using CreateOffsetDescriptor accomplishes the same thing as setting a variable to an integer and passing the variable to AECreateDesc to create a descriptor record of type typeLongInteger.    Specifying a RangeThe key form formRange allows your application to specify key data that identifies a range of elements in the specified container. To do so, your application must first create a range descriptor record. The Apple Event Manager uses a range descriptor record to identify the two Apple event objects that specify the beginning and end of a range of elements. For example, an object specifier record for a range of text in a document could specify the table named “Summary of Sales” as the first boundary object and the figure named “Best-Selling Widgets for 1991” as the second boundary object for a range that consists of all the text between the table and the figure. Any word processor that keeps track of the relative positions of text, tables, and figures should be capable of supporting such a request. Table 6-10 summarizes the logical organization of the data for the object specifier record that specifies this range. For general information about the organization of data within a range descriptor record, see “Key Data for a Range” on page 6-20.Table 6-10    A range descriptor recordKeyword    Descriptor type    Data    keyAERangeStart    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cTable    keyAEContainer    typeCurrentContainer    Data handle is NIL    keyAEKeyForm    typeEnumerated    formName    keyAEKeyData    typeChar    "Summary of Sales"    keyAERangeStop    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cFigure    keyAEContainer    typeCurrentContainer    Data handle is NIL    keyAEKeyForm    typeEnumerated    formName    keyAEKeyData    typeChar    "Best-Selling Widgets for 1991"    You can use the CreateRangeDescriptor function to create a range descriptor record, or you can create an AE record and use AECoerceDesc to coerce it to a range descriptor record. Listing 6-20 provides an example of an application-defined routine that creates two object specifier records, then uses the CreateRangeDescriptor function to add them to a range descriptor record.The container for the boundary objects in the range descriptor record created by Listing 6-20 is the same as the container for the range itself. The object specifier record for the range’s container is added to an object specifier record of key form formRange at the same time that the range descriptor record is added as key data. The container for the two boundary objects can therefore be specified in the range descriptor record by a descriptor record of type typeCurrentContainer whose data handle has the value NIL. The Apple Event Manager interprets this as a placeholder for the range’s container when it is resolving the range descriptor record.Listing 6-20    Creating a range descriptor recordFUNCTION MyCreateRangeDescriptor (VAR rangeDescRec: AEDesc): OSErr;VAR    rangeStart:                             AEDesc;    rangeEnd:                            AEDesc;    currentContainer:                            AEDesc;    tableNameDescRec    :                        AEDesc;    figureNameDescRec    :                        AEDesc;    myErr:                            OSErr;BEGIN{create the object specifier record for the start of the range }{ (the table named 'Summary of Sales' in 'MyDoc' document)}    {create a descriptor record of type typeCurrentContainer}    myErr := AECreateDesc(typeCurrentContainer, NIL, 0, currentContainer);    {create the object specifier record}    IF myErr = noErr THEN        myErr := MyCreateNameDescRec(tableNameDescRec,                                                 'Summary of Sales');    IF myErr = noErr THEN    myErr := CreateObjSpecifier(cTable, currentContainer, formName,                                             tableNameDescRec, FALSE, rangeStart);        myErr := AEDisposeDesc(tableNameDescRec);    {create the object specifier record for the end of the range }    { (the figure named 'Best-Selling Widgets...' in 'MyDoc') }    IF myErr = noErr THEN        myErr := MyCreateNameDescRec(figureNameDescRec,                                                 'Best-Selling Widgets for 1991');    IF myErr = noErr THEN        myErr := CreateObjSpecifier(cFigure, currentContainer, formName,                                             figureNameDescRec, TRUE, rangeEnd);    {now create the range descriptor record}    IF myErr = noErr THEN        myErr := CreateRangeDescriptor(rangeStart, rangeEnd, TRUE,                                                     rangeDescRec);    MyCreateRangeDescriptor := myErr;END;After creating a descriptor record of type typeCurrentContainer and a descriptor record for the first table’s name, Listing 6-20 uses the CreateObjSpecifier function to create an object specifier record that identifies the beginning of the range. The parameters to CreateObjSpecifier specify that the beginning of the range is an Apple event object of the object class cTable in the current container, with a key form of formName and key data that identifies the table by name. A second call to CreateObjSpecifier creates the object specifier record that identifies the end of the range—an Apple event object of the cFigure object class in the current container, with a key form of formName and key data that identifies the figure by name. Finally, the code in Listing 6-20 uses the CreateRangeDescriptor function to create the range descriptor record, using the two previously created object specifier records to specify the beginning and end of the range.  Reference to Resolving and Creating Object Specifier RecordsThis section describes the Apple Event Manager routines your application can use to resolve and create object specifier records. It also describes application-defined object accessor functions and object callback functions that your application can provide for use by the Apple Event Manager in resolving object specifier records. The first section, “Data Structures Used in Object Specifier Records,” summarizes the descriptor types and associated data that can be used in an object specifier record. “Routines for Resolving and Creating Object Specifier Records,” which begins on page 6-77, describes the Apple Event Manager routines you use to initialize the Object Support Library, resolve object specifier records, set and manipulate object accessor functions, deallocate memory for tokens, and create object specifier records. “Application-Defined Routines,” which begins on page 6-94, describes the object accessor functions and object callback functions that a server application can provide.Data Structures Used in Object Specifier RecordsThe data for object specifier records can be specified using a variety of descriptor records and descriptor types. These are described in detail in “Descriptor Records Used in Object Specifier Records,” which begins on page 6-8, and summarized in Table 6-11.Table 6-11    Keyword-specified descriptor records for typeObjectSpecifier(continued)(continued)Keyword    Descriptor type    Data    keyAEDesiredClass    typeType    Object class ID    keyAEContainer    typeObjectSpecifier    Object specifier record        typeNull    Data handle is NIL. Specifies the default container at the top of the container hierarchy.        typeObjectBeingExamined    Data handle is NIL. Specifies the container for elements that are tested one at a time; used only with formTest.         typeCurrentContainer    Data handle is NIL. Specifies a container for an element that demarcates one boundary in a range. Used only with formRange.     keyAEKeyForm    typeEnumerated    formPropertyIDformNameformUniqueIDformAbsolutePositionformRelativePositionformTestformRangeformWhose     keyAEKeyData        (See indented key forms)    for formPropertyID    typeType    Property ID for an element’s property    for formName    typeChar or other text type    Element’s name    for formUniqueID    Any appropriate type    Element’s unique ID    for formAbsolutePosition    typeLongInteger    Offset from beginning (positive) or end (negative) of container        typeAbsoluteOrdinal    kAEFirst kAEMiddlekAELastkAEAnykAEAll    for formRelativePosition    typeEnumerated    kAENextkAEPrevious     for formTest    typeCompDescriptor    (See Table 6-2 on page 6-16)        typeLogicalDescriptor    (See Table 6-3 on page 6-17)    for formRange    typeRangeDescriptor    (See Table 6-4 on page 6-20)    for formWhose    typeWhoseDescriptor    (See Table 6-5 on page 6-42)    Routines for Resolving and Creating Object Specifier RecordsThis section describes routines for initializing the Object Support Library, resolving object specifier records, setting and manipulating object accessor functions, deallocating memory for tokens, and creating object specifier records.Initializing the Object Support LibraryYou should call the AEObjectInit function to initialize the Apple Event Manager routines that handle object specifier records and Apple event objects. To make these routines available to your application with version 1.01 and earlier versions of the Apple Event Manager, you must also link the Apple Event Object Support Library with your application when you build it.AEObjectInitYou use the AEObjectInit function to initialize the Object Support Library.FUNCTION AEObjectInit: OSErr; DESCRIPTIONYou must call this function before calling any of the Apple Event Manager routines that describe or manipulate Apple event objects.RESULT CODESnoErr    0    No error occurred    memFullErr    –108    Not enough room in heap zone    errAENewerVersion    –1706    Need a newer version of the Apple Event Manager    Setting Object Accessor Functions and Object Callback FunctionsThe Apple Event Manager provides two routines that allow you to specify the object accessor functions and object callback functions provided by your application. The AEInstallObjectAccessor function adds an entry for an object accessor function to either the application’s object accessor dispatch table or the system object accessor dispatch table. The AESetObjectCallbacks function allows you to specify the object callback functions to be called for your application. AEInstallObjectAccessorYou can use the AEInstallObjectAccessor function to add an entry for an object accessor function to either the application’s object accessor dispatch table or the system object accessor dispatch table.  FUNCTION AEInstallObjectAccessor (desiredClass: DescType;                                              containerType: DescType;                                              theAccessor: AccessorProcPtr;                                              accessorRefcon: LongInt;                                              isSysHandler: Boolean): OSErr;desiredClassThe object class of the Apple event objects to be located by the object accessor function for this table entry.containerTypeThe descriptor type of the token used to specify the container for the desired objects. The object accessor function finds objects in containers specified by tokens of this type.theAccessorA pointer to the object accessor function for this table entry. Note that an object accessor function listed in the system dispatch table must reside in the system heap; thus, if the value of the isSysHandler parameter is TRUE, the theAccessor parameter should point to a location in the system heap. Otherwise, if you put your system object accessor function in your application heap, you must call AERemoveObjectAccessor to remove the function before your application terminates.accessorRefconA reference constant passed by the Apple Event Manager to the object accessor function whenever the function is called. If your object accessor function doesn’t use a reference constant, use 0 as the value of this parameter. To change the value of the reference constant, you must call AEInstallObjectAccessor again.isSysHandlerA value that specifies the object accessor dispatch table to which the entry is added. If the value of isSysHandler is TRUE, the Apple Event Manager adds the entry to the system object accessor dispatch table. Entries in the system object accessor dispatch table are available to all applications running on the same computer. If the value is FALSE, the Apple Event Manager adds the entry to your application’s object accessor table. When searching for object accessor functions, the Apple Event Manager searches the application’s object accessor dispatch table first; it searches the system object accessor dispatch table only if the necessary function is not found in your application’s object accessor dispatch table.DESCRIPTIONThe AEInstallObjectAccessor function adds an entry to either the application or system object accessor dispatch table. You must supply parameters that specify the object class of the Apple event objects that the object accessor function can locate, the descriptor type of tokens for containers in which the object accessor function can locate objects, the address of the object accessor function for which you are adding an entry, and whether the entry is to be added to the system object accessor dispatch table or your application’s object accessor dispatch table. You can also specify a reference constant that the Apple Event Manager passes to your object accessor function each time the Apple Event Manager calls the function.RESULT CODESnoErr    0    No error occurred    paramErr    –50    The handler pointer is NIL or odd, or AEObjectInit was not called before this function    SEE ALSOFor more information about installing object accessor functions, see “Installing Entries in the Object Accessor Dispatch Tables,” which begins on page 6-21.  For a description of the AERemoveObjectAccessor function, see page 6-84.AESetObjectCallbacksYou can use the AESetObjectCallbacks function to specify the object callback functions to be called for your application.  FUNCTION AESetObjectCallbacks (myCompareProc, myCountProc,                                          myDisposeTokenProc,                                         myGetMarkTokenProc, myMarkProc,                                         myAdjustMarksProc,                                         myGetErrDescProc: ProcPtr): OSErr;myCompareProcEither a pointer to the object-comparison function provided by your application or NIL if no function is provided.myCountProcEither a pointer to the object-counting function provided by your application or NIL if no function is provided.myDisposeTokenProcEither a pointer to the token disposal function provided by your application or NIL if no function is provided.myGetMarkTokenProcEither a pointer to the function for returning a mark token provided by your application or NIL if no function is provided.myMarkProc    Either a pointer to the object-marking function provided by your application or NIL if no function is provided.myAdjustMarksProcEither a pointer to the mark-adjusting function provided by your application or NIL if no function is provided.myGetErrDescProcEither a pointer to the error callback function provided by your application or NIL if no function is provided.DESCRIPTIONYour application can provide only one each of the object callback functions specified by AESetObjectCallbacks: one object-comparison function, one object-counting function, and so on. As a result, each of these callback functions must perform the requested task (comparing, counting, and so on) for all the object classes that your application supports. In contrast, your application may provide many different object accessor functions if necessary, depending on the object classes and token types your application supports.To replace object callback routines that have been previously installed, you can make another call to AESetObjectCallbacks. Each additional call to AESetObjectCallbacks replaces any object callback functions installed by previous calls to AESetObjectCallbacks. You cannot use AESetObjectCallbacks to replace system object callback routines or object accessor functions. Only those routines you specify are replaced; to avoid replacing existing callback functions, specify a value of NIL for the functions you don’t want to replace.RESULT CODESnoErr    0    No error occurred    paramErr    –50    The handler pointer is NIL or odd, or AEObjectInit was not called before this function    memFullErr    –108    There is not enough room in heap zone    errAENotASpecialFunction    –1714    The keyword is not valid for a special function    SEE ALSOFor information about writing object callback functions, see “Application-Defined Routines,” which begins on page 6-94.To install system object callback functions, use the AEInstallSpecialHandler function described on page 4-100.  Getting, Calling, and Removing Object Accessor FunctionsThe Apple Event Manager provides three functions that allow you to get, call, and remove object accessor functions that you have installed in either the system or application object accessor dispatch table with the AEInstallObjectAccessor function. The AEGetObjectAccessor and AECallObjectAccessor functions get and call object accessor functions installed in the dispatch table you specify, and AERemoveObjectAccessor removes an installed function.AEGetObjectAccessorYou can use the AEGetObjectAccessor function to get a pointer to an object accessor function and the value of its reference constant. FUNCTION AEGetObjectAccessor (desiredClass: DescType;                                         containerType: DescType;                                        VAR theAccessor: AccessorProcPtr;                                        VAR accessorRefcon: LongInt;                                         isSysHandler: Boolean): OSErr;desiredClassThe object class of the Apple event objects located by the requested object accessor function. This parameter can also contain the constant typeWildCard or the constant cProperty.containerTypeThe descriptor type of the token that identifies the container for the objects located by the requested object accessor function. This parameter can also contain the constant typeWildCard.theAccessorThe AEGetObjectAccessor function returns a pointer to the requested object accessor function in this parameter.accessorRefconThe AEGetObjectAccessor function returns the reference constant from the object accessor dispatch table entry for the specified object accessor function in this parameter.isSysHandlerA value that specifies the object accessor table from which to get the object accessor function and its reference constant. If the value of isSysHandler is TRUE, AEGetObjectAccessor gets the function from the system object accessor dispatch table. If the value of isSysHandler is FALSE, AEGetObjectAccessor gets the function from the application’s object accessor dispatch table.DESCRIPTIONThe AEGetObjectAccessor function returns a pointer to the object accessor function installed for the object class specified in the desiredClass parameter and the descriptor type specified in the containerType parameter. It also returns the reference constant associated with the specified function. You must supply a value in the isSysHandler parameter that specifies which object accessor dispatch table you want to get the function from. Calling AEGetObjectAccessor does not remove the object accessor function from an object accessor dispatch table.To get an object accessor function whose entry in an object accessor dispatch table specifies typeWildCard as the object class, you must specify typeWildCard as the value of the desiredClass parameter. Similarly, to get an object accessor function whose entry in an object accessor dispatch table specifies typeWildCard as the descriptor type of the token used to specify the container, you must specify typeWildCard as the value of the containerType parameter.To get an object accessor function whose entry in an object accessor dispatch table specifies cProperty (a constant used to specify a property of any object class), you must specify cProperty as the desiredClass parameter. RESULT CODESnoErr    0    No error occurred    paramErr    –50    AEObjectInit was not called before this function was called    errAEAccessorNotFound    –1723    There is no object accessor function for the specified object class and container type      AECallObjectAccessorYou can use the AECallObjectAccessor function to invoke one of your application’s object accessor functions. FUNCTION AECallObjectAccessor (desiredClass: DescType;                                          containerToken: AEDesc;                                          containerClass: DescType;                                          keyForm: DescType;                                          keyData: AEDesc;                                          VAR theToken: AEDesc): OSErr;desiredClassThe object class of the desired Apple event objects.containerTokenThe token that identifies the container for the desired objects.containerClassThe object class of the container for the desired objects.keyForm    The key form specified by the object specifier record for the object or objects to be located.keyData    The key data specified by the object specifier record for the object or objects to be located.theToken    The object accessor function that is invoked returns a token specifying the desired object or objects in this parameter.DESCRIPTIONIf you want your application to do some of the Apple event object resolution normally performed by the AEResolve function, you can use AECallObjectAccessor to invoke an object accessor function. This might be useful, for example, if you have installed an object accessor function using typeWildCard for the AEInstallObjectAccessor function’s desiredClass parameter and typeAEList for the containerType parameter. To return a list of tokens for a request like “every line that ends in a period,” the object accessor function can create an empty list, then call AECallObjectAccessor for each requested element, adding tokens for each element to the list one at a time. The parameters of AECallObjectAccessor are identical to the parameters of an object accessor function, with one exception: the parameter that specifies the reference constant passed to the object accessor function whenever it is called is added by the Apple Event Manager when it calls the object accessor function.To call an object accessor function whose entry in an object accessor dispatch table specifies typeWildCard as the object class, you must specify typeWildCard as the value of the desiredClass parameter. To call an object accessor function whose entry in an object accessor dispatch table specifies cProperty, you must specify cProperty as the desiredClass parameter. RESULT CODESIn addition to the following result codes, AECallObjectAccessor returns any other result codes returned by the object accessor function that is called.noErr    0    No error occurred    paramErr    –50    AEObjectInit was not called before this function was called    errAEAccessorNotFound    –1723    No object accessor was found     AERemoveObjectAccessorYou can use the AERemoveObjectAccessor function to remove an object accessor function from an object accessor dispatch table.  FUNCTION AERemoveObjectAccessor (desiredClass: DescType;                                             containerType: DescType;                                             theAccessor: AccessorProcPtr;                                             isSysHandler: Boolean): OSErr;desiredClassThe object class of the Apple event objects located by the object accessor function. The desiredClass parameter can also contain the constant typeWildCard or the constant cProperty.containerTypeThe descriptor type of the token that identifies the container for the objects located by the object accessor function. The containerType parameter can also contain the constant typeWildCard.theAccessorA pointer to the object accessor function you want to remove. Although the parameters desiredClass and containerType would be sufficient to identify the function to be removed, providing the parameter theAccessor guarantees that you remove the correct function. If this parameter does not contain a pointer to the object accessor function you want to remove, its value should be NIL.isSysHandlerA value that specifies the object accessor dispatch table from which to remove the object accessor function. If the value of isSysHandler is TRUE, AEGetObjectAccessor removes the routine from the system object accessor dispatch table. If the value is FALSE, AEGetObjectAccessor removes the routine from the application object accessor dispatch table.DESCRIPTIONThe AERemoveObjectAccessor function removes the object accessor function you have installed for the object class specified in the desiredClass parameter and the descriptor type specified in the containerType parameter. To remove an object accessor function whose entry in an object accessor dispatch table specifies typeWildCard as the object class, you must specify typeWildCard as the value of the desiredClass parameter. Similarly, to remove an object accessor function whose entry in an object accessor dispatch table specifies typeWildCard as the descriptor type of the token used to specify the container for the desired objects, you must specify typeWildCard as the value of the containerType parameter.To remove an object accessor function whose entry in an object accessor dispatch table specifies cProperty (a constant used to specify a property of any object class), you must specify cProperty as the desiredClass parameter. RESULT CODESnoErr    0    No error occurred    paramErr    –50    AEObjectInit was not called before this function was called    errAEAccessorNotFound    –1723    There is no object accessor function for the specified object class and container type      Resolving Object Specifier RecordsIf an Apple event parameter consists of an object specifier record, your handler for the event typically calls the AEResolve function to begin the process of resolving the object specifier record. AEResolveYou can use the AEResolve function to resolve an object specifier record in an Apple event parameter.FUNCTION AEResolve (objectSpecifier: AEDesc;                           callbackFlags: Integer;                           VAR theToken: AEDesc): OSErr;objectSpecifierThe object specifier record to be resolved.callbackFlagsA value that determines what additional assistance, if any, your application can give the Apple Event Manager when it parses the object specifier record. The value is specified by adding the following constants, as appropriate:                CONST            kAEIDoMinimum                    = $0000;                {supports minimum }                                                                { callbacks only}                            kAEIDoWhose                    = $0001;                {supports formWhose}                            kAEIDoMarking                    = $0004;                {provides marking }                                                                { functions} theToken    The AEResolve function returns, in this parameter, a token that identifies the Apple event objects specified by the objectSpecifier parameter. Your object accessor functions may need to create many tokens to resolve a single object specifier record; this parameter contains only the final token that identifies the requested Apple event object. If an error occurs, AEResolve returns a null descriptor record.DESCRIPTIONThe AEResolve function resolves the object specifier record passed in the objectSpecifier parameter with the help of the object accessor functions and object callback functions provided by your application. RESULT CODESnoErr    0    No error occurred    paramErr    –50    AEObjectInit was not called before   this function was called    errAEHandlerNotFound    –1717    The necessary object callback function was not found (this result is returned only for object callback functions; errAEAccessorNotFound [–1723] is returned when an object accessor function is not found)    errAEImpossibleRange    –1720    The range is not valid because it is impossible for a range to include the first and last objects that were specified; an example is a range in which the offset of the first object is greater than the offset of the last object    errAEWrongNumberArgs    –1721    The number of operands provided for the kAENOT logical operator is not 1    errAEAccessorNotFound    –1723    There is no object accessor function for the specified object class and token descriptor type    errAENoSuchLogical    –1725    The logical operator in a logical descriptor record is not kAEAND, kAEOR, or kAENOT    errAEBadTestKey    –1726    The descriptor record in a test key is neither a comparison descriptor record nor a logical descriptor record    errAENotAnObjectSpec    –1727    The objSpecifier parameter of AEResolve is not an object specifier record    errAENegativeCount    –1729    An object-counting function returned a negative result    errAEEmptyListContainer    –1730    The container for an Apple event object is specified by an empty list    In addition to the result codes listed here, AEResolve also returns any result code returned by one of your application’s object accessor functions or object callback functions. For example, an object accessor function can return errAENoSuchObject (–1728) when it can’t find an Apple event object, or it can return more specific result codes.If any object accessor function or object callback function returns a result code other than noErr or errAEEventNotHandled, AEResolve immediately disposes of any existing tokens and returns. The result code it returns in this case is the result code returned by the object accessor function or the object callback function. SEE ALSOFor an overview of the way AEResolve works with object accessor functions, see “Resolving Object Specifier Records,” which begins on page 6-4.Deallocating Memory for TokensWhenever the AEResolve function returns a final token to your event handler as the result of the resolution of an object specifier record passed to AEResolve, your application can call the AEDisposeToken function to deallocate the memory used by the token. AEDisposeTokenYou can use the AEDisposeToken function to deallocate the memory used by a token.FUNCTION AEDisposeToken (VAR theToken: AEDesc): OSErr;theToken    The token to be disposed of.DESCRIPTIONWhen your application calls the AEDisposeToken function, the Apple Event Manager first calls your application’s token disposal function, if you have provided one. If you haven’t provided a token disposal function, or if your application’s token disposal function returns errAEEventNotHandled as the function result, the Apple Event Manager calls the system token disposal function if one is available. If there is no system token disposal function or the function returns errAEEventNotHandled as the function result, the Apple Event Manager calls the AEDisposeDesc function to dispose of the token.RESULT CODESIn addition to the following result codes, AEDisposeToken also returns result codes returned by the token disposal function that disposed of the token.noErr    0    No error occurred    paramErr    –50    AEObjectInit was not called before this function was called    notASpecialFunction    –1714    The keyword is not valid for a special function    SEE ALSOFor information about writing a token disposal function, see page 6-99. Creating Object Specifier RecordsThe Apple Event Manager provides five functions that you can use to create some of the components of an object specifier record or to assemble an object specifier record: n    The CreateOffsetDescriptor function creates an offset descriptor record, which specifies the position of an element in relation to the beginning or end of its container.n    The CreateCompDescriptor function creates a comparison descriptor record, which specifies how to compare one or more Apple event objects with either another Apple event object or a descriptor record.n    The CreateLogicalDescriptor function creates a logical descriptor record, which specifies a logical operator and one or more logical terms for the Apple Event Manager to evaluate.n    The CreateRangeDescriptor function creates a range descriptor record, which specifies a series of consecutive elements in the same container.n    The CreateObjSpecifier function assembles an object specifier record, which identifies one or more Apple event objects, from other descriptor records.Instead of using these functions, you can create the corresponding descriptor records yourself using the AECreateDesc function, add them to an AE record using other Apple Event Manager routines, and coerce the AE record to a descriptor record of type typeObjectSpecifier. However, in most cases it is easier to use the functions listed in this section. All of these functions except for CreateOffsetDescriptor include a disposeInputs parameter. If the value of this parameter is TRUE, the function automatically disposes of any descriptor records you have provided as parameters to the function. If the value is FALSE, the application must dispose of the records itself. A value of FALSE may be more efficient for some applications because it allows them to reuse descriptor records.For more information about these functions and examples of their use, see “Creating Object Specifier Records,” which begins on page 6-55.CreateOffsetDescriptorYou can use the CreateOffsetDescriptor function to create an offset descriptor record. FUNCTION CreateOffsetDescriptor (theOffset: LongInt;                                             VAR theDescriptor: AEDesc)                                             : OSErr;theOffset    A positive integer that specifies the offset from the beginning of the container (the first element has an offset of 1), or a negative integer that specifies the offset from the end (the last element has an offset of –1).theDescriptorThe offset descriptor record created by CreateOffsetDescriptor.DESCRIPTIONThe CreateOffsetDescriptor function creates an offset descriptor record that specifies the position of an element in relation to the beginning or end of its container.RESULT CODESnoErr    0    No error occurred    memFullErr    –108    Not enough room in heap zone     CreateCompDescriptorYou can use the CreateCompDescriptor function to create a comparison descriptor record.FUNCTION CreateCompDescriptor (comparisonOperator: DescType;                                         VAR operand1: AEDesc;                                          VAR operand2: AEDesc;                                          disposeInputs: Boolean;                                          VAR theDescriptor: AEDesc)                                         : OSErr;comparisonOperatorThe comparison operator for comparing the descriptor records in the operand1 and operand2 parameters. The operator is specified by the constants listed in the description that follows.operand1    An object specifier record.operand2    A descriptor record (which can be an object specifier record or any other descriptor record) whose value is to be compared to the value of operand1.disposeInputsA Boolean value indicating whether the function (TRUE) or your application (FALSE) should dispose of the descriptor records for the two operands.theDescriptorThe comparison descriptor record created by CreateCompDescriptor.DESCRIPTIONThe CreateCompDescriptor function creates a comparison descriptor record, which specifies how to compare one or more Apple event objects with either another Apple event object or a descriptor record.The actual comparison of the two operands is performed by the object-comparison function provided by the client application. The way a comparison operator is interpreted is up to each application.These are the currently defined standard comparison operators:Constant    Meaning    kAEGreaterThan    The value of operand1 is greater than the value of operand2.    kAEGreaterThanEquals    The value of operand1 is greater than or equal to the value of operand2.    kAEEquals    The value of operand1 is equal to the value of operand2.    kAELessThan    The value of operand1 is less than the value of operand2.    kAELessThanEquals    The value of operand1 is less than or equal to the value of operand2.    kAEBeginsWith    The value of operand1 begins with the value of operand2 (for example, the string "operand" begins with the string "opera").    kAEEndsWith    The value of operand1 ends with the value of operand2 (for example, the string "operand" ends with the string "and").    kAEContains    The value of operand1 contains the value of operand2 (for example, the string "operand" contains the string "era").    RESULT CODESnoErr    0    No error occurred    paramErr    –50    Error in parameter list    memFullErr    –108    Not enough room in heap zone    errAECoercionFail     –1700    Data could not be coerced to the requested Apple event data type    errAEWrongDataType    –1703    Wrong Apple event data type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    SEE ALSOFor an example of how to use the CreateCompDescriptor function to create a comparison descriptor record, see “Specifying a Test,” which begins on page 6-64. CreateLogicalDescriptorYou can use the CreateLogicalDescriptor function to create a logical descriptor record. FUNCTION CreateLogicalDescriptor                                         (VAR theLogicalTerms: AEDescList;                                          theLogicOperator: DescType;                                          disposeInputs: Boolean;                                          VAR theDescriptor: AEDesc): OSErr;theLogicalTermsA list containing comparison descriptor records, logical descriptor records, or both. If the value of the parameter theLogicOperator is kAEAND or kAEOR, the list can contain any number of descriptors. If the value of the parameter theLogicOperator is kAENOT, logically this list should contain a single descriptor record. However, the function will not return an error if the list contains more than one descriptor record for a logical operator of kAENOT.theLogicOperatorA logical operator represented by one of the following constants:                 CONST            kAEAND         = 'AND ';                            kAEOR         = 'OR  ';                            kAENOT         = 'NOT ';disposeInputsA Boolean value indicating whether the function (TRUE) or your application (FALSE) should dispose of the descriptor records in the other parameters.theDescriptorThe logical descriptor record created by CreateLogicalDescriptor.DESCRIPTIONThe CreateLogicalDescriptor function creates a logical descriptor record, which specifies a logical operator and one or more logical terms for the Apple Event Manager to evaluate.RESULT CODESnoErr    0    No error occurred    paramErr    –50    Error in parameter list    memFullErr    –108    Not enough room in heap zone    errAECoercionFail    –1700    Data could not be coerced to requested Apple event data type    errAEWrongDataType    –1703    Wrong Apple event data type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    SEE ALSOFor an example of how to use the CreateLogicalDescriptor function to create a logical descriptor record, see “Specifying a Test,” which begins on page 6-64. CreateRangeDescriptorYou can use the CreateRangeDescriptor function to create a range descriptor record. FUNCTION CreateRangeDescriptor (VAR rangeStart: AEDesc;                                           VAR rangeStop: AEDesc;                                           disposeInputs: Boolean;                                           VAR theDescriptor: AEDesc): OSErr;rangeStartAn object specifier record that identifies the first Apple event object in the range.rangeStop    An object specifier record that identifies the last Apple event object in the range.disposeInputsA Boolean value indicating whether the function (TRUE) or your application (FALSE) should dispose of the descriptor records for the rangeStart and rangeStop parameters. theDescriptorThe range descriptor record created by CreateRangeDescriptor.DESCRIPTIONThe CreateRangeDescriptor function creates a range descriptor record, which specifies a series of consecutive elements in the same container. Although the rangeStart and rangeStop parameters can be any object specifier records—including object specifier records that specify more than one Apple event object—most applications expect these parameters to specify single Apple event objects.RESULT CODESnoErr    0    No error occurred    paramErr    –50    Error in parameter list    memFullErr    –108    Not enough room in heap zone    errAECoercionFail    –1700    Data could not be coerced to the requested Apple event data type    errAEWrongDataType    –1703    Wrong Apple event data type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    SEE ALSOFor an example of how to use the CreateRangeDescriptor function to create a range descriptor record, see “Specifying a Range” on page 6-72. CreateObjSpecifierYou can use the CreateObjSpecifier function to create an object specifier record.FUNCTION CreateObjSpecifier (desiredClass: DescType;                                       VAR theContainer: AEDesc;                                       keyForm: DescType;                                       VAR keyData: AEDesc;                                       disposeInputs: Boolean;                                       VAR objSpecifier: AEDesc): OSErr;desiredClassThe object class of the desired Apple event objects.theContainerA description of the container for the requested object, usually in the form of another object specifier record.keyForm    The key form for the object specifier record.keyData    The key data for the object specifier record.disposeInputsA Boolean value indicating whether the function (TRUE) or your application (FALSE) should dispose of the descriptor records for the other parameters.objSpecifierThe object specifier record created by the CreateObjSpecifier function.DESCRIPTIONThe CreateObjSpecifier function assembles an object specifier record from the specified constants and other descriptor records.RESULT CODESnoErr    0    No error occurred    paramErr    –50    Error in parameter list    memFullErr    –108    Not enough room in heap zone    errAECoercionFail     –1700    Data could not be coerced to the requested Apple event data type    errAEWrongDataType    –1703    Wrong Apple event data type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    SEE ALSOFor information about how to assemble the components of an object specifier record with the CreateObjSpecifier function, see “Creating Object Specifier Records,” which begins on page 6-55.   Application-Defined RoutinesThe AEResolve function performs tasks that are required to resolve any object specifier record, such as parsing its contents, keeping track of the results of tests, and handling memory management. When necessary, AEResolve calls application-defined functions to perform tasks that are unique to the application, such as locating a specific Apple event object in the application’s data structures or counting the number of Apple event objects in a container. AEResolve can call two kinds of application-defined functions:n    Object accessor functions locate Apple event objects. Every application that supports simple object specifier records must provide one or more object accessor functions. n    Object callback functions perform other tasks that only an application can perform, such as counting, comparing, or marking Apple event objects. You can provide up to seven object callback functions, depending on the needs of your application.This section provides model declarations for the object accessor functions and object callback functions that your application can provide.Object Accessor FunctionsYou must provide one or more object accessor functions that can locate all the element classes and properties listed in the Apple Event Registry: Standard Suites for the object classes supported by your application. This section provides the routine declaration for an object accessor function.MyObjectAccessorObject accessor functions locate Apple event objects of a specified object class in a container identified by a token of a specified descriptor type. FUNCTION MyObjectAccessor (desiredClass: DescType;                                     containerToken: AEDesc;                                     containerClass: DescType;                                     keyForm: DescType; keyData: AEDesc;                                     VAR theToken: AEDesc;                                     theRefcon: LongInt): OSErr;desiredClassThe object class of the desired Apple event objects.containerTokenA token that specifies the container of the desired Apple event objects.containerClassThe object class of the container.keyForm    The key form specified by the object specifier record being resolved.keyData    The key data specified by the object specifier record being resolved.theToken    The token returned by the MyObjectAccessor function.theRefcon    A reference constant that the Apple Event Manager passes to the object accessor function each time it is called.DESCRIPTIONEach object accessor function provided by your application should either find elements of a specified object class or find properties of an Apple event object. The AEResolve function uses the object class ID of the specified Apple event object and the descriptor type of the token that identifies the object’s container to determine which object accessor function to call. To install an object accessor function either in your application’s object accessor dispatch table or in the system object accessor dispatch table, use the AEInstallObjectAccessor function, which is described on page 6-78. SPECIAL CONSIDERATIONSIf the Apple Event Manager receives the result code errAEEventNotHandled after calling an object accessor function, it attempts to use other methods of locating the requested objects, such as calling an equivalent system object accessor function. Thus, an object accessor function that can’t locate a requested object should return errAEEventNotHandled. This allows the Apple Event Manager to try other object accessor functions that may be available.RESULT CODESnoErr    0    No error occurred    errAEEventNotHandled    –1708    The object accessor function is unable to locate the requested Apple event object or objects    SEE ALSOFor information about installing object accessor functions, see “Installing Entries in the Object Accessor Dispatch Tables,” which begins on page 6-21.For information about writing object accessor functions, see “Writing Object Accessor Functions,” which begins on page 6-28. Object Callback FunctionsIf an Apple event parameter consists of an object specifier record, your handler for the Apple event typically calls AEResolve to begin the process of locating the requested Apple event objects. The AEResolve function in turn calls object accessor functions and, if necessary, object callback functions provided by your application when it needs the information they can provide.This section provides declarations for the seven object callback functions that your application can provide: the object-counting function (MyCountObjects), object-comparison function (MyCompareObjects), token disposal function (MyDisposeToken), error callback function (MyGetErrorDesc), mark token function (MyGetMarkToken), object-marking function (MyMark), and mark-adjusting function (MyAdjustMarks).For information about writing and installing object callback functions, see “Writing Object Callback Functions,” which begins on page 6-45. MyCountObjectsIf you want the Apple Event Manager to help your application resolve object specifier records of key form formTest (and if your application doesn’t specify kAEIDoWhose as described on page 6-48), you should provide an object-counting function and an object-comparison function. An object-counting function counts the number of Apple event objects of a specified class in a specified container. FUNCTION MyCountObjects (desiredClass: DescType;                                  containerClass: DescType;                                  theContainer: AEDesc;                                  VAR result: LongInt): OSErr;desiredClassThe object class of the Apple event objects to be counted.containerClassThe object class of the container for the Apple event objects to be counted.theContainerA token that identifies the container for the Apple event objects to be counted.result    Your object-counting function should return in this parameter the number of Apple objects of the specified class in the specified container.DESCRIPTIONThe Apple Event Manager calls your object-counting function when, in the course of resolving an object specifier record, the manager requires a count of the number of Apple event objects of a given class in a given container. SPECIAL CONSIDERATIONSIf the Apple Event Manager receives the result code errAEEventNotHandled after calling an object-counting function, it attempts to use other methods of counting the specified objects, such as calling an equivalent system object-counting function. Thus, an object-counting function that can’t count the specified objects should return errAEEventNotHandled. This allows the Apple Event Manager to try other object-counting functions that may be available.RESULT CODESnoErr    0    No error occurred    errAEEventNotHandled    –1708    The object-counting function is unable to count the specified Apple event objects    SEE ALSOFor more information, see “Writing an Object-Counting Function” on page 6-48. MyCompareObjectsIf you want the Apple Event Manager to help your application resolve object specifier records of key form formTest (and if your application doesn’t specify kAEIDoWhose as described on page 6-48), you should provide an object-counting function and an object-comparison function. After comparing one Apple event object to another or to the data for a descriptor record, an object-comparison function should return TRUE or FALSE in the result parameter. FUNCTION MyCompareObjects (comparisonOperator: DescType;                                     object: AEDesc;                                     objectOrDescToCompare: AEDesc;                                     VAR result: Boolean): OSErr;comparisonOperatorThe comparison operator. See the description of CreateCompDescriptor on page 6-89 for standard comparison operators at the time of publication of this book. The current version of the Apple Event Registry: Standard Suites lists all the constants for comparison operators.object    A token.objectOrDescToCompareA token or some other descriptor record that specifies either an Apple event object or a value to compare to the Apple event object specified by the object parameter.result    Your object-comparison function should return, in this parameter, a Boolean value that indicates whether the values of the object and objectOrDescToCompare parameters have the relationship specified by the comparisonOperator parameter (TRUE) or not (FALSE).DESCRIPTIONThe Apple Event Manager calls your object-comparison function when, in the course of resolving an object specifier record, the manager needs to compare an Apple event object with another or with a value.It is up to your application to interpret the comparison operators it receives. The meaning of comparison operators differs according to the Apple event objects being compared, and not all comparison operators apply to all object classes. SPECIAL CONSIDERATIONSIf the Apple Event Manager receives the result code errAEEventNotHandled after calling an object-comparison function, it attempts to use other methods of comparison, such as calling an equivalent system object-comparison function. Thus, an object-comparison function that can’t perform a requested comparison should return errAEEventNotHandled. This allows the Apple Event Manager to try other object-comparison functions that may be available.RESULT CODESnoErr    0    No error occurred    errAEEventNotHandled    –1708    The object-comparison function is unable to compare the specified Apple event objects    SEE ALSOFor more information, see “Writing an Object-Comparison Function” on page 6-50.MyDisposeTokenIf your application requires more than a call to the AEDisposeDesc function to dispose of a token, or if it supports marking callback functions, you must provide one token disposal function. A token disposal function disposes of a specified token. FUNCTION MyDisposeToken (VAR unneededToken: AEDesc): OSErr;unneededTokenThe token to dispose of.DESCRIPTIONThe Apple Event Manager calls your token disposal function whenever it needs to dispose of a token. It also calls your disposal function when your application calls the AEDisposeToken function. If your application does not provide a token disposal function, the Apple Event Manager calls AEDisposeDesc instead.Your token disposal function must be able to dispose of all of the token types used by your application. If your application supports marking, a call to MyDisposeToken to dispose of a mark token lets your application know that it can unmark the objects marked with that mark token. SPECIAL CONSIDERATIONSIf the Apple Event Manager receives the result code errAEEventNotHandled after calling a token disposal function, it attempts to dispose of the token by some other method, such as calling an equivalent system token disposal function if one is available or, if that fails, by calling AEDisposeDesc. Thus, a token disposal function that can’t dispose of a token should return errAEEventNotHandled. This allows the Apple Event Manager to try other token disposal functions that may be available.RESULT CODESnoErr    0    No error occurred    errAEEventNotHandled    –1708    The token disposal function is unable to dispose of the token    MyGetErrorDescIf you want to find out which descriptor record is responsible for an error that occurs during a call to the AEResolve function, you can provide an error callback function. An error callback function returns a pointer to an address. The Apple Event Manager uses this address to store the descriptor record it is currently working with if an error occurs during a call to AEResolve.FUNCTION MyGetErrorDesc (VAR errDescPtr: DescPtr): OSErr;errDescPtrA pointer to an address.DESCRIPTIONYour error callback function simply returns an address. Shortly after your application calls AEResolve, the Apple Event Manager calls your error callback function and writes a null descriptor record to the address returned, overwriting whatever was there previously. If an error occurs during the resolution of the object specifier record, the Apple Event Manager calls your error callback function again and writes the descriptor record—often an object specifier record—to the address returned. If AEResolve returns an error during the resolution of an object specifier record, this address contains the descriptor record responsible for the error.Normally you should maintain a single global variable of type AEDesc whose address your error callback function returns no matter how many times it is called. Be careful if you use any other method. When recovering from an error, the Apple Event Manager never writes to the address you provide unless it already contains a null descriptor record. Thus, if you don’t maintain a single global variable as just described, you should write null descriptor records to any addresses passed by your error callback function that are different from the addresses returned the first time your function is called after a given call to AEResolve.If the result code returned by the MyGetErrorDesc function has a nonzero value, the Apple Event Manager continues to resolve the object specifier record as if it had never called the error callback function.RESULT CODEnoErr    0    No error occurred     MyGetMarkTokenIf your application supports marking, you must provide one mark token function. A mark token function returns a mark token. FUNCTION MyGetMarkToken (containerToken: AEDesc;                                  containerClass: DescType;                                  VAR result: AEDesc): OSErr;containerTokenThe Apple event object that contains the elements to be marked with the mark token.containerClassThe object class of the container that contains the objects to be marked.result    Your mark token function should return a mark token in this parameter.DESCRIPTIONTo get a mark token, the Apple Event Manager calls your mark token function. Like other tokens, the mark token returned can be a descriptor record of any type; however, unlike other tokens, a mark token identifies the way your application will mark Apple event objects during the current session while resolving a single object specifier record that specifies the key form formTest. A mark token is valid until the Apple Event Manager either disposes of it (by calling AEDisposeToken) or returns it as the result of the AEResolve function. If the final result of a call to AEResolve is a mark token, the Apple event objects currently marked for that mark token are those specified by the object specifier record passed to AEResolve, and your application can proceed to do whatever the Apple event has requested. Note that your application is responsible for disposing of a final mark token with a call to AEDisposeToken, just as for any other final token.If your application supports marking, it should also provide a token disposal function modeled after the token disposal function described on page 6-99. When the Apple Event Manager calls AEDisposeToken to dispose of a mark token that is not the final result of a call to AEResolve, the subsequent call to your token disposal function lets you know that you can unmark the Apple event objects marked with that mark token. A call to AEDisposeDesc to dispose of a mark token (which would occur if you did not provide a token disposal function) would go unnoticed. RESULT CODESnoErr    0    No error occurred    errAEEventNotHandled    –1708    The mark token function is unable to return a mark token; if the Apple Event Manager gets this result, it attempts to get a mark token by calling the equivalent system marking callback function    SEE ALSOFor more information, see “Writing Marking Callback Functions,” which begins on page 6-53. MyMarkIf your application supports marking, you must provide one object-marking function. An object-marking function marks a specific Apple event object. FUNCTION MyMark (theToken: AEDesc; markToken: AEDesc;                       markCount: LongInt): OSErr;theToken    The token for the Apple event object to be marked.markToken    The mark token used to mark the Apple event object.markCount    The number of times MyMark has been called for the current mark token (that is, the number of Apple event objects that have so far passed the test, including the element to be marked).DESCRIPTIONTo mark an Apple event object using the current mark token, the Apple Event Manager calls the object-marking function provided by your application. In addition to marking the specified object, your MyMark function should record the mark count for each object that it marks. The mark count recorded for each marked object allows your application to determine which of a set of marked tokens pass a test, as described in the next section for the MyAdjustMarks function.RESULT CODESnoErr    0    No error occurred    errAEEventNotHandled    –1708    The MyMark function is unable to mark the specified Apple event object; if the Apple Event Manager gets this result, it attempts to mark the object by calling the equivalent system object-marking function    SEE ALSOFor more information, see “Writing Marking Callback Functions,” which begins on page 6-53.MyAdjustMarksIf your application supports marking, you must provide one mark-adjusting function. A mark-adjusting function adjusts the marks made with the current mark token. FUNCTION MyAdjustMarks (newStart, newStop: LongInt;                                 markToken: AEDesc): OSErr;newStart    The mark count value (provided when the MyMark callback routine was called to mark the object) for the first object in the new set of marked objects.newStop    The mark count value (provided when the MyMark callback routine was called to mark the object) for the last object in the new set of marked objects.markToken    The mark token for the marked objects.DESCRIPTIONWhen the Apple Event Manager needs to identify either a range of elements or the absolute position of an element in a group of Apple event objects that pass a test, it can use your application’s mark-adjusting function to unmark objects previously marked by a call to your marking function. For example, suppose an object specifier record specifies “any row in the table ‘MyCustomers’ for which the City column is ‘San Francisco.’” The Apple Event Manager first uses the appropriate object accessor function to locate all the rows in the table for which the City column is “San Francisco” and calls the application’s marking function repeatedly to mark them. It then generates a random number between 1 and the number of rows it found that passed the test and calls the application’s mark-adjusting function to unmark all the rows whose mark count does not match the randomly generated number. If the randomly chosen row has a mark count value of 5, the Apple Event Manager passes the value 5 to the mark-adjusting function in both the newStart parameter and the newStop parameter, and passes the current mark token in the markToken parameter. When the Apple Event Manager calls your MyAdjustMarks function, your application must dispose of any data structures that it created to mark the previously marked objects.RESULT CODESnoErr    0    No error occurred    errAEEventNotHandled    –1708    The MyAdjustMarks function is unable to adjust the marks as requested; if the Apple Event Manager gets this result, it attempts to adjust the marks by calling the equivalent system mark-adjusting function    SEE ALSOFor more information, see “Writing Marking Callback Functions” on page 6-53.  Summary of Resolving and Creating Object Specifier RecordsPascal SummaryConstantsCONST            gestaltAppleEventsAttr                                    = 'evnt';                {selector for Apple events}    gestaltAppleEventsPresent                                    = 0;                {if this bit is set, Apple }                                                        { Event Manager is available}    {logical operators for descriptor records with keyword }     { keyAELogicalOperator}    kAEAND                                =    'AND ';                    kAEOR                                =    'OR  ';    kAENOT                                =    'NOT ';    {absolute ordinals used as key data in an object specifier }     { record with key form formAbsolutePosition}    kAEFirst                                =    'firs';    kAELast                                =    'last';    kAEMiddle                                =    'midd';    kAEAny                                =    'any ';    kAEAll                                =    'all ';    {relative ordinals used as key data in an object specifier record }    { with key form formRelativePosition}    kAENext                                =    'next';    kAEPrevious                                =    'prev';        {keywords for object specifier records}     keyAEDesiredClass                                =    'want'; {object class ID}    keyAEContainer                                =    'from'; {description of container}    keyAEKeyForm                                =    'form'; {key form}    keyAEKeyData                                 =     'seld'; {key data for specified key form}    {keywords for range descriptor records}    keyAERangeStart                                =    'star';                {beginning of range}    keyAERangeStop                                =    'stop';                {end of range}        {values for the keyAEKeyForm field of an object specifier record}                             formAbsolutePosition                                 =    'indx'        ;        {for example, 1 = first }                                                        { element in container, -2 = }                                                        { second from end of container}    formRelativePosition                                =    'rele';                {key data specifies element }                                                        { before or after container}    formTest                                =    'test';                {key data specifies a test}    formRange                                =    'rang';                {key data specifies a range}    formPropertyID                                =    'prop';                {key data is property ID}    formName                                =    'name';                {key data is element's name}    {descriptor types used to identify Apple event objects}    typeObjectSpecifier                                 =     'obj ';                {object specifier record, often }                                                        { used as keyAEContainer}    typeObjectBeingExamined =                                  'exmn';                    {used as keyAEContainer}    typeCurrentContainer                                =    'ccnt';                {used as keyAEContainer}    typeToken                                =    'toke';                {substituted for 'ccnt' }                                                        { before accessor called}    typeAbsoluteOrdinal                                 =    'abso';                {formAbsolutePosition}    typeRangeDescriptor                                 =     'rang';                {formRange}    typeLogicalDescriptor                                =     'logi';                {formTest}    typeCompDescriptor                                =    'cmpd';                {formTest}    {various relevant keywords}    keyAECompOperator                                =    'relo';                {operator for comparison: }                                                        { '=', '<=', etc.}    keyAELogicalTerms                                =    'term';                {an AEList of terms to be }                                                        { related by 'logc' below}    keyAELogicalOperator                                =    'logc';                {kAEAND, kAEOR, or kAENOT}    keyAEObject1                                =    'obj1';                {first of two objects being }                                                        { compared; must be object }                                                        { specifier record}    keyAEObject2                                =    'obj2';                {the other object; may be }                                                        { simple descriptor record }                                                        { or object specifier record}    {special handler selectors used with AESetObjectCallbacks}    keyDisposeTokenProc                                =    'xtok';    keyAECompareProc                                 =     'cmpr';    keyAECountProc                                 =     'cont';    keyAEMarkTokenProc                                 =     'mkid';    keyAEMarkProc                                 =     'mark';    keyAEAdjustMarksProc                                 =     'adjm';    keyAEGetErrDescProc                                 =     'indc';    {additive values for callbackFlags parameter to AEResolve}    kAEIDoMinimum                                =    $0000;            {server does not support whose }                                                    { descriptor records or marking}    kAEIDoWhose                                =    $0001;            {server supports whose }                                                    { descriptor records}    kAEIDoMarking                                =    $0004;            {server supports marking}    {constants for whose descriptor records}    typeWhoseDescriptor                                =    'whos';            {whose descriptor record}    formWhose                                =    'whos';            {key form for key data of descriptor }                                                    { type typeWhoseDescriptor}    typeWhoseRange                                =    'wrng';             {whose range descriptor record}    keyAEWhoseRangeStart                                =    'wstr';            {beginning of range}    keyAEWhoseRangeStop                                =    'wstp';            {end of range}    keyAEIndex                                =    'kidx';            {index for whose descriptor record}    keyAETest                                =    'ktst';            {test for whose descriptor record}Data TypesTYPE    ccntTokenRecord =                                                     {used for rewriting tokens in }    RECORD                                                    { place of 'ccnt' descriptor }        tokenClass:                     DescType;                            { records; only of interest to }        token:                     AEDesc;                            { those who, when they get ranges }    END;                                                    { as key data in their object }                                                        { accessor functions, resolve }    ccntTokenRecPtr = ^ccntTokenRecord;                                                    { the object specifier records }    ccntTokenRecHandle = ^ccntTokenRecPtr;                                                    { for the end points manually}    DescPtr = ^AEDesc;    DescHandle = ^DescPtr;    AccessorProcPtr = ProcPtr;Routines for Resolving and Creating Object Specifier RecordsInitializing the Object Support LibraryFUNCTION AEObjectInit : OSErr;Setting Object Accessor Functions and Object Callback FunctionsFUNCTION AEInstallObjectAccessor(desiredClass: DescType; containerType: DescType; theAccessor: AccessorProcPtr; accessorRefcon: LongInt; isSysHandler: Boolean): OSErr;FUNCTION AESetObjectCallbacks(myCompareProc, myCountProc, myDisposeTokenProc,                                        myGetMarkTokenProc, myMarkProc,myAdjustMarksProc, myGetErrDescProc: ProcPtr): OSErr;Getting, Calling, and Removing Object Accessor FunctionsFUNCTION AEGetObjectAccessor(desiredClass: DescType; containerType: DescType;VAR theAccessor: AccessorProcPtr;VAR accessorRefcon: LongInt; isSysHandler: Boolean): OSErr;FUNCTION AECallObjectAccessor(desiredClass: DescType; containerToken: AEDesc;containerClass: DescType; keyForm: DescType; keyData: AEDesc; VAR theToken: AEDesc): OSErr;FUNCTION AERemoveObjectAccessor(desiredClass: DescType; containerType: DescType; theAccessor: AccessorProcPtr; isSysHandler: Boolean): OSErr;Resolving Object Specifier RecordsFUNCTION AEResolve     (objectSpecifier: AEDesc; callbackFlags: Integer;VAR theToken: AEDesc): OSErr;Deallocating Memory for TokensFUNCTION AEDisposeToken     (VAR theToken: AEDesc): OSErr;Creating Object Specifier RecordsFUNCTION CreateOffsetDescriptor(theOffset: LongInt; VAR theDescriptor: AEDesc): OSErr;FUNCTION CreateCompDescriptor(comparisonOperator: DescType;VAR operand1: AEDesc; VAR operand2: AEDesc; disposeInputs: Boolean; VAR theDescriptor: AEDesc): OSErr;FUNCTION CreateLogicalDescriptor(VAR theLogicalTerms: AEDescList; theLogicOperator: DescType; disposeInputs: Boolean; VAR theDescriptor: AEDesc): OSErr;FUNCTION CreateRangeDescriptor(VAR rangeStart: AEDesc; VAR rangeStop: AEDesc; disposeInputs: Boolean; VAR theDescriptor: AEDesc): OSErr;FUNCTION CreateObjSpecifier    (desiredClass: DescType;VAR theContainer: AEDesc; keyForm: DescType; VAR keyData: AEDesc; disposeInputs: Boolean; VAR objSpecifier: AEDesc): OSErr;Application-Defined RoutinesObject Accessor FunctionsFUNCTION MyObjectAccessor     (desiredClass: DescType; containerToken: AEDesc; containerClass: DescType; keyForm: DescType; keyData: AEDesc; VAR theToken: AEDesc; theRefcon: LongInt): OSErr;Object Callback FunctionsFUNCTION MyCountObjects    (desiredClass: DescType; containerClass: DescType; theContainer: AEDesc; VAR result: LongInt): OSErr;FUNCTION MyCompareObjects    (comparisonOperator: DescType; theobject: AEDesc; objectOrDescToCompare: AEDesc; VAR result: Boolean): OSErr;FUNCTION MyDisposeToken     (VAR unneededToken: AEDesc): OSErr;FUNCTION MyGetErrorDesc     (VAR errDescPtr: DescPtr): OSErr;FUNCTION MyGetMarkToken     (containerToken: AEDesc; containerClass: DescType; VAR result: AEDesc): OSErr;FUNCTION MyMark     (theToken: AEDesc; markToken: AEDesc;markCount: LongInt): OSErr;FUNCTION MyAdjustMarks     (newStart, newStop: LongInt; markToken: AEDesc): OSErr;C SummaryConstantsenum {        #define         gestaltAppleEventsAttr                                      'evnt'            /*selector for Apple events*/        gestaltAppleEventsPresent                                             = 0        /*if this bit is set, then */                                                            /* Apple Event Manager is */};                                                            /* available*//*logical operators for descriptor records with keyword */ /* keyAELogicalOperator*/#define kAEAND                                                'AND '                #define kAEOR                                                'OR  '#define kAENOT                                                'NOT '/*absolute ordinals used as key data in an object specifier */ /* record with key form formAbsolutePosition*/#define kAEFirst                                                'firs'#define kAELast                                                'last'#define kAEMiddle                                                'midd'#define kAEAny                                                'any '#define kAEAll                                                'all '/*relative ordinals used as key data in an object specifier record *//* with key form formRelativePosition*/#define kAENext                                                'next'#define kAEPrevious                                                'prev'/*keywords for object specifier records*/                                                             #define keyAEDesiredClass                                                'want'            /*object class ID*/#define keyAEContainer                                                'from'            /*description of container*/#define keyAEKeyForm                                                'form'            /*key form*/#define keyAEKeyData                                                  'seld'            /*key data for specified key */                                                            /* form*//*keywords for range descriptor records*/#define keyAERangeStart                                                'star'            /*beginning of range*/#define keyAERangeStop                                                'stop'            /*end of range*/    /*values for the keyAEKeyForm field of an object specifier record*/                         #define formAbsolutePosition                                                 'indx'             /*for example, 1 = first */                                                            /* element in container, -2 = */                                                            /* second from end of */                                                            /* container*/#define formRelativePosition                                                'rele'             /*key data specifies element */                                                            /* before or after container*/#define formTest                                                'test'            /*key data specifies a test*/#define formRange                                                'rang'             /*key data specifies a range*/#define formPropertyID                                                'prop'             /*key data is property ID*/#define formName                                                'name'             /*key data is element's name*//* descriptor types used to identify Apple event objects*/#define typeObjectSpecifier                                                  'obj '            /*object specifier record, */                                                            /* often used as */                                                            /* keyAEContainer*/#define typeObjectBeingExamined                                                 'exmn'            /*used as keyAEContainer*/#define typeCurrentContainer                                                'ccnt'            /*used as keyAEContainer*/#define typeToken                                                'toke'            /*substituted for 'ccnt' */                                                            /* before accessor called*/#define typeAbsoluteOrdinal                                                 'abso'            /*formAbsolutePosition*/#define typeRangeDescriptor                                                  'rang'            /*formRange*/#define typeLogicalDescriptor                                                 'logi'            /*formTest*/#define typeCompDescriptor                                                'cmpd'            /*formTest*//*various relevant keywords*/#define keyAECompOperator                                                'relo'            /*operator for comparison: */                                                            /* '=', '<=', etc.*/#define keyAELogicalTerms                                                'term'            /*an AEList of terms to be */                                                            /* related by 'logc' below*/#define keyAELogicalOperator                                                'logc'            /*kAEAND, kAEOR, or kAENOT*/#define keyAEObject1                                                'obj1'            /*first of two objects being */                                                            /* compared; must be object */                                                            /* specifier record*/#define keyAEObject2                                                'obj2'            /*the other object; may be */                                                            /* simple descriptor record */                                                            /* or object specifier record*//*special handler selectors used with AESetObjectCallbacks*/#define keyDisposeTokenProc                                                'xtok'#define keyAECompareProc                                                  'cmpr'#define keyAECountProc                                                  'cont'#define keyAEMarkTokenProc                                                  'mkid'#define keyAEMarkProc                                                  'mark'#define keyAEAdjustMarksProc                                                  'adjm'#define keyAEGetErrDescProc                                                  'indc'/*additive values for callbackFlags parameter to AEResolve*/#define kAEIDoMinimum                                                0x0000            /*server does not support */                                                            /* whose descriptor records */                                                            /* or marking*/#define kAEIDoWhose                                                0x0001            /*server supports whose */                                                            /* descriptor records*/#define kAEIDoMarking                                                0x0004            /*server supports marking*//*constants for whose descriptor records*/#define typeWhoseDescriptor                                                'whos'            /*whose descriptor record*/#define formWhose                                                'whos'            /*key form for key data of */                                                            /* descriptor type */                                                            /* typeWhoseDescriptor*/#define typeWhoseRange                                                'wrng'            /*whose range descriptor */                                                            /* record*/#define keyAEWhoseRangeStart                                                'wstr'            /*beginning of range*/#define keyAEWhoseRangeStop                                                'wstp'            /*end of range*/#define keyAEIndex                                                'kidx'            /*index for whose descriptor */                                                            /* record*/#define keyAETest                                                'ktst'            /*test for whose descriptor */                                                            /* record*/Data Typesstruct ccntTokenRecord                             {                                /*used for rewriting tokens */    DescType tokenClass                        ;                                /* in place of 'ccnt' */    AEDesc token                ;                                        /* descriptor records; only */};                                                            /* of interest to those who, */                                                            /* when they get ranges as */typedef struct ccntTokenRecord ccntTokenRecord,                                                             /* key data in their object */*ccntTokenRecPtr, **ccntTokenRecHandle;                                                            /* accessor functions, */                                                             /* resolve them manually*/typedef AEDesc *DescPtr, **DescHandle;/*typedefs providing type checking for procedure pointers*/typedef pascal OSErr (*accessorProcPtr) (DescType desiredClass,                                                        const AEDesc *container,                                                         DescType containerClass,                                                         DescType form,                                                        const AEDesc *selectionData,                                                         AEDesc *value, long LongInt);typedef pascal OSErr (*compareProcPtr)(DescType oper, const AEDesc *obj1,                                                    const AEDesc *obj2,                                                    Boolean *result);typedef pascal OSErr (*countProcPtr)(DescType desiredClass,                                                     DescType containerClass,                                                    const AEDesc *container,                                                     long *result);typedef pascal OSErr (*disposeTokenProcPtr)(AEDesc *unneededToken);typedef pascal OSErr (*getMarkTokenProcPtr)(const AEDesc *ContainerToken,                                                             DescType containerClass,                                                            AEDesc *result);typedef pascal OSErr (*getErrDescProcPtr)(DescPtr *appDescPtr);Routines for Resolving and Creating Object Specifier RecordsInitializing the Object Support Librarypascal OSErr AEObjectInit    ();Setting Object Accessor Functions and Object Callback Functionspascal OSErr AEInstallObjectAccessor(DescType desiredClass, DescType containerType,accessorProcPtr theAccessor,long accessorRefcon, Boolean isSysHandler);pascal OSErr AESetObjectCallbacks(compareProcPtr myCompareProc, countProcPtr myCountProc, disposeTokenProcPtr myDisposeTokenProc, getMarkTokenProcPtr myGetMarkTokenProc, markProcPtr myMarkProc, adjustMarksProcPtr myAdjustMarksProc, getErrDescProcPtr myGetErrDescProc);Getting, Calling, and Removing Object Accessor Functionspascal OSErr AEGetObjectAccessor(DescType desiredClass, DescType containerType,accessorProcPtr *theAccessor,long *accessorRefcon, Boolean isSysHandler);pascal OSErr AECallObjectAccessor(DescType desiredClass, const AEDesc *containerToken, DescType containerClass, DescType keyForm, const AEDesc *keyData, AEDesc *theToken);pascal OSErr AERemoveObjectAccessor(DescType desiredClass, DescType containerType,accessorProcPtr theAccessor, Boolean isSysHandler);Resolving Object Specifier Recordspascal OSErr AEResolve    (const AEDesc *objectSpecifier, short callbackFlags, AEDesc *theToken);Deallocating Memory for Tokenspascal OSErr AEDisposeToken    (AEDesc *theToken);Creating Object Specifier Recordspascal OSErr CreateOffsetDescriptor(long theOffset, AEDesc *theDescriptor);pascal OSErr CreateCompDescriptor(DescType comparisonOperator, AEDesc* operand1,AEDesc* operand2, Boolean                                             disposeInputs, AEDesc* theDescriptor);pascal OSErr CreateLogicalDescriptor(AEDescList *theLogicalTerms, DescType theLogicOperator, Boolean disposeInputs, AEDesc *theDescriptor);pascal OSErr CreateRangeDescriptor(AEDesc *rangeStart, AEDesc *rangeStop,Boolean disposeInputs, AEDesc *theDescriptor);pascal OSErr CreateObjSpecifier(DescType desiredClass, AEDesc *theContainer,DescType                                         keyForm, AEDesc *keyData, Boolean disposeInputs, AEDesc *objSpecifier);Application-Defined RoutinesObject Accessor Functionspascal OSErr MyObjectAccessor(DescType desiredClass, const AEDesc *containerToken, DescType containerClass, DescType keyForm, const AEDesc *keyData, AEDesc *theToken, long *theRefcon);Object Callback Functionspascal OSErr MyCountObjects    (DescType desiredClass, DescType containerClass, const AEDesc *theContainer, long *result);pascal OSErr MyCompareObjects(DescType comparisonOperator, const AEDesc *theObject, const AEDesc *objectOrDescToCompare, Boolean *result);pascal OSErr MyDisposeToken    (AEDesc *unneededToken);pascal OSErr MyGetErrorDesc    (DescPtr *errDescPtr);pascal OSErr MyGetMarkToken    (const AEDesc *containerToken, DescType containerClass, AEDesc *result);pascal OSErr MyMark    (const AEDesc *theToken, const AEDesc *markToken, long markCount);pascal OSErr MyAdjustMarks    (long newStart, long newStop, const AEDesc *markToken);Assembly-Language SummaryTrap MacrosTrap Macros Requiring Routine Selectors_Pack8Selector    Routine    $023A    AEDisposeToken    $0536    AEResolve    $0738    AERemoveObjectAccessor    $0937    AEInstallObjectAccessor    $0939    AEGetObjectAccessor    $0C3B    AECallObjectAccessor    $0E35    AESetObjectCallbacks    Result CodesnoErr    0    No error    paramErr    –50    Parameter error (for example, value of handler pointer is NIL or odd)    eLenErr    –92    Buffer too big to send    memFullErr    –108    Not enough room in heap zone    userCanceledErr    –128    User canceled an operation    procNotFound    –600    No eligible process with specified process serial number    bufferIsSmall    –607    Buffer is too small    noOutstandingHLE    –608    No outstanding high-level event    connectionInvalid    –609    Nonexistent signature or session ID    noUserInteractionAllowed    –610    Background application sends event requiring authentication    noPortErr    –903    Client hasn’t set 'SIZE' resource to indicate awareness of high-level events    destPortErr    –906    Server hasn’t set 'SIZE' resource to indicate awareness of high-level events, or else is not present    sessClosedErr    –917    The kAEDontReconnect flag in the sendMode parameter was set, and the server quit and then restarted    errAECoercionFail    –1700    Data could not be coerced to the requested descriptor type    errAEDescNotFound    –1701    Descriptor record was not found    errAECorruptData    –1702    Data in an Apple event could not be read    errAEWrongDataType    –1703    Wrong descriptor type    errAENotAEDesc    –1704    Not a valid descriptor record    errAEBadListItem    –1705    Operation involving a list item failed    errAENewerVersion    –1706    Need a newer version of the Apple Event Manager    errAENotAppleEvent    –1707    Event is not an Apple event    errAEEventNotHandled    –1708    Event wasn’t handled by an Apple event handler    errAEReplyNotValid    –1709    AEResetTimer was passed an invalid reply    errAEUnknownSendMode    –1710    Invalid sending mode was passed    errAEWaitCanceled    –1711    User canceled out of wait loop for reply or receipt    errAETimeout    –1712    Apple event timed out    errAENoUserInteraction    –1713    No user interaction allowed    errAENotASpecialFunction    –1714    The keyword is not valid for a special function    errAEParamMissed    –1715    Handler cannot understand a parameter the client considers required    errAEUnknownAddressType    –1716    Unknown Apple event address type    errAEHandlerNotFound    –1717    No handler found for an Apple event or a coercion, or no object callback function found    errAEReplyNotArrived    –1718    Reply has not yet arrived    errAEIllegalIndex    –1719    Not a valid list index    errAEImpossibleRange    –1720    The range is not valid because it is impossible for a range to include the first and last objects that were specified; an example is a range in which the offset of the first object is greater than the offset of the last object    errAEWrongNumberArgs    –1721    The number of operands provided for the kAENOT logical operator is not 1    errAEAccessorNotFound    –1723    There is no object accessor function for the specified object class and token descriptor type    errAENoSuchLogical    –1725    The logical operator in a logical descriptor record is not kAEAND, kAEOR, or kAENOT    errAEBadTestKey    –1726    The descriptor record in a test key is neither a comparison descriptor record nor a logical descriptor record    errAENotAnObjectSpec    –1727    The objSpecifier parameter of AEResolve is not an object specifier record    errAENoSuchObject    –1728     A run-time resolution error, for example: object specifier record asked for the third element, but there are only 2.    errAENegativeCount    –1729     Object-counting function returned negative value    errAEEmptyListContainer    –1730    The container for an Apple event object is specified by an empty list    errAEUnknownObjectType    –1731    Descriptor type of token returned by AEResolve is not known to server application     errAERecordingIsAlreadyOn    –1732    Attempt to turn recording on when it is already on    Listing 7-0Table 7-0Introduction to ScriptingContentsAbout Scripts and Scripting Components7-4Script Editors and Script Files7-6Scripting Components and Scriptable Applications7-8Scripting Components and Applications That Execute Scripts7-11Making Your Application Scriptable7-14About Apple Event Terminology Resources7-15How AppleScript Uses Terminology Information7-17Dynamic Loading of Terminology Information7-20Making Your Application Recordable7-20Manipulating and Executing Scripts7-22Compiling, Saving, Modifying, and Executing Scripts7-24Using a Script Context to Handle an Apple Event7-25Introduction to ScriptingThis chapter provides an overview of the tasks involved in making your application scriptable and recordable. This chapter also introduces some of the ways your application can use the Component Manager and scripting components to manipulate and execute scripts. The three chapters that follow provide detailed information, including sample code, about the topics introduced in this chapter.The chapter “Introduction to Interapplication Communication” in this book describes the Open Scripting Architecture (OSA) and its relationship to the Apple Event Manager and other parts of the IAC architecture. If your application supports the appropriate core and functional-area events defined in the Apple Event Registry: Standard Suites, you can make it scriptable (that is, capable of responding to Apple events sent by scripting components) by providing an Apple event terminology extension ('aete') resource. This chapter describes some of the tasks involved in making your application scriptable and introduces the 'aete' resource. The next chapter, “Apple Event Terminology Resources,” describes in detail how to create an 'aete' resource.This chapter also introduces Apple event recording and the use of the standard scripting component routines to manipulate and execute scripts. The chapter “Recording Apple Events” describes in detail how to make your application recordable, and the chapter “Scripting Components” describes how to use the standard scripting component routines.To use this chapter or any of the chapters that follow, you should be familiar with the chapters “Introduction to Apple Events” and “Responding to Apple Events” in this book. If you plan to make your application recordable, you should also read the chapters “Creating and Sending Apple Events” and “Resolving and Creating Object Specifier Records.”The AppleScript Software Developers’ Kit (available from APDA) provides development tools, sample applications, and information about the AppleScript language that you will find useful when you begin to apply the information in this chapter to your application. If you are developing a scripting component, you should provide support for the standard scripting component routines described in the chapter “Scripting Components,” and you should read the instructions for creating components in the chapter “Component Manager” in Inside Macintosh: More Macintosh Toolbox. This chapter begins with an overview of scripts and scripting components. The rest of the chapter describes how the OSA makes it possible to n    make your application scriptablen    make your application recordablen    have your application manipulate and execute scriptsAbout Scripts and Scripting ComponentsA script is any collection of data that, when executed by the appropriate program, causes a corresponding action or series of actions. The Open Scripting Architecture (OSA) provides a standard mechanism that allows users to control multiple applications with scripts written in a variety of scripting languages. Each scripting language has a corresponding scripting component. Each scripting component supports the standard scripting component routines described in the chapter “Scripting Components” in this book.  When a scripting component executes a script, it performs the actions described in the script, including sending Apple events to applications if necessary. Like other components that use the Component Manager, scripting components can provide their own routines in addition to the standard routines that must be supported by all components of the same type.Scripting components typically implement a text-based scripting language based on Apple events. For example, the AppleScript component implements AppleScript, the standard user scripting language defined by Apple Computer, Inc. This book uses AppleScript examples to demonstrate how applications can interact with scripting components.  Other scripting components may support the standard scripting component routines in different ways. Scripting components need not implement a text-based scripting language, or even one that is based on Apple events. For example, specialized scripting components can play sounds, execute XCMDs, or perform almost any other action when they execute scripts. This chapter describes three ways that you can take advantage of the OSA:n    You can make your application scriptable, or capable of responding to Apple events sent to it by a scripting component. An application is scriptable if itn    Responds to the appropriate standard Apple events as described in the chapter “Responding to Apple Events” in this book.n    Provides an Apple event terminology extension ('aete') resource describing the Apple events that your application supports and the user terminology that corresponds to those events. The 'aete' resource allows scripting components to interpret scripts correctly and send the appropriate Apple events to your application during script execution.n    You can make your application recordable—that is, capable of sending Apple events to itself to report user actions to the Apple Event Manager for recording purposes. After a user has turned on recording for a particular scripting component, the scripting component receives a copy of every subsequent Apple event that any application on the local computer sends to itself. The scripting component records such events in the form of a script. n    You can have your application manipulate and execute scripts with the aid of a scripting component. To do so, your application mustn    Use the Component Manager to open a connection with the appropriate component.n    Use the standard scripting component routines described in the chapter “Scripting Components” to record, edit, compile, save, load, or execute scripts.Users of scriptable applications can execute scripts to perform tasks that might otherwise be difficult to accomplish, especially repetitive or conditional tasks that involve multiple applications. For example, a user can execute an AppleScript script to locate database records with specific characteristics, create a series of graphs based on those records, import the graphs into a page-layout document, and send the document to a remote computer on the network via electronic mail. When a user executes such a script, the AppleScript component attempts to perform the actions the script describes, including sending Apple events when necessary. To respond appropriately to the Apple events sent to it by the AppleScript component, the database application in this example must be able to locate records with specific characteristics so that it can identify and return the requested data. These characteristics are described by an object specifier record that is part of an Apple event supported by the application. Also, the other applications involved must support Apple events that manipulate the data in the ways described in the script. Each application in this example must also provide an 'aete' resource describing the Apple events that the application supports and the user terminology that corresponds to those events, so that the AppleScript component can interpret the script correctly.Even with little or no knowledge of a particular scripting language, users of applications that are recordable as well as scriptable can record simple scripts. More knowledgeable users may also wish to record their actions as scripts with recordable applications and then edit or combine scripts as needed.An application that uses scripting components to manipulate and execute scripts need not be scriptable; however, if it is scriptable, it can execute scripts that control its own behavior. In other words, it can perform tasks by means of scripts and allow users to modify those scripts to suit their own needs.The next three sections provide an overview of the way scripting components can interact with applications.Script Editors and Script FilesA script editor is an application that allows users to record, edit, save, and execute scripts. For example, the AppleScript component uses the services of the Script Editor application.  Figure 7-1 shows an AppleScript script displayed in a Script Editor window. The Record, Stop, and Run buttons control a script in much the same way that the equivalent buttons on a cassette recorder control an audio tape. A script comment at the top of the window describes what the script does. Users with some knowledge of a text-based scripting language such as AppleScript can use Script Editor to modify recorded scripts or write their own scripts.Figure 7-1    A script window in the Script Editor applicationScript Editor provides entry-level scripting capabilities, but it is not intended for intensive script development. Users who wish to write complex scripts may replace Script Editor with more sophisticated editors that provide specialized debugging and development tools.  A script like the one in Figure 7-1 can be stored in a script file represented by an icon in the Finder, or it can be stored within an application or one of its documents. Figure 7-2 shows the four icons representing the files in which Script Editor stores scripts.Figure 7-2    Script file icons in the Finder and corresponding user actionsScript Editor and similar script-editing applications allow users to store scripts using three file types:n    A compiled script file has the file type 'osas' and contains the script data as a resource of type 'scpt'. Before executing the script in a compiled script file, a user must first open the script from the Finder or from an application such as Script Editor. After opening a compiled script in an application that supports script editing, the user can view the script, modify it if necessary, and execute it.n    A script application has the file type 'APPL' and contains the script data as a resource of type 'scpt'. Its kind is “application.” A script application takes one of two forms, each with its own icon:  n    A script application with the creator signature 'aplt'. A user double-clicks the icon to trigger the script.   n    A script application with the creator signature 'dplt'. A user can drag the icon for another file or a folder over this script application’s icon to trigger a script that acts on that object.   By default, when a user triggers the script in either kind of script application, a splash screen appears that allows the user either to quit or to run the script. Users can also save a script application in a form that bypasses the splash screen, running the script immediately after the user double-clicks its icon.n    A script text file contains only a plain-text version of uncompiled scripting-language statements. This format is useful primarily as a last resort for saving a script that can’t be compiled because of syntax errors or other problems. It is also useful for exchanging unstyled text with other text-based applications. A user must open a script text file in a script editor and successfully compile it before it will execute. Like sound resources, scripts can be stored within applications and documents as well as in distinct files that can be manipulated from the Finder. Your application can use the standard scripting component routines to manipulate and execute both its own internally stored scripts and scripts stored as separate files whose icons appear in the Finder. For more information about script storage formats, see “Saving Script Data” on page 10-12. The next two sections describe how scripting components interact with scriptable applications and with applications that execute scripts.Scripting Components and Scriptable ApplicationsScripting components control the behavior of scriptable applications by means of Apple events. For example, when the AppleScript component executes the AppleScript script shown in Figure 7-1, it sends the Apple events shown in Figure 7-3 to trigger the actions described by the script. The client application in this example would most commonly be a script editor but could also be any other application that uses standard scripting component routines to manipulate and execute scripts. Figure 7-3    How the AppleScript component executes a scriptAs described in the chapter “Introduction to Apple Events” in this book, a client application is any application that uses Apple events to request a service or information. A client application that executes a script does not send the corresponding Apple events itself; instead, it uses scripting component routines to manipulate and execute the script. The scripting component sends Apple events when necessary to trigger the actions described in the script. Similarly, a scriptable application that responds to the Apple events sent by a scripting component can be considered the server application for those Apple events. When a scripting component evaluates a script, it attempts to perform all the actions described in the script, including sending Apple events when necessary. In the example shown in Figure 7-3, the AppleScript component first performs the action described in the first tell statement: tell application "SurfWriter"    copy table "Summary of Sales" of document¬         "Sales Report" to Totalsend tellTo perform this action, the AppleScript component sends a Get Data event to the SurfWriter application requesting the data from the specified table. The SurfWriter application returns the data to the AppleScript component in a standard reply Apple event, and the AppleScript component sets the value of the variable Totals to the data returned by SurfWriter.Then the AppleScript component performs the action described in the second tell statement:tell application "SurfCharter"    copy Totals to Chart 1 of document "Sales Chart"end tellIn this case, the AppleScript component sends a Set Data event to the SurfCharter application that sets the specified chart to the value of the variable Totals. Both SurfWriter and SurfCharter are server applications for the Apple events sent by the AppleScript component, because they are performing services in response to requests made by the client application via the script.To send the appropriate Apple events to a scriptable application while executing a script, a scripting component must obtain information about the nature of that application’s support for Apple events and the human-language terminology to associate with those events. A scriptable application provides this information in the form of an Apple event terminology extension ('aete') resource. A scripting component uses both the 'aete' resource provided by a scriptable application and the Apple event user terminology ('aeut') resource provided by the scripting component itself to obtain the information it needs to execute a script that controls that application. See “Making Your Application Scriptable,” which begins on page 7-14, for an overview of the tasks you should perform to make your application scriptable and a more detailed description of the 'aete' and 'aeut' resources. See “Making Your Application Recordable” on page 7-20 for an overview of the tasks you should perform if you want your application to be recordable as well as scriptable.Scripting Components and Applications That Execute ScriptsTo store and execute scripts as a client application, your application must first establish a connection with a scripting component registered with the Component Manager on the same computer. Each scripting component can manipulate and execute scripts written in the corresponding scripting language when your application calls the standard scripting component routines.Your application can use scripting component routines ton    obtain a handle to a script in a form that can be saved, and load the script again when necessaryn    allow users to modify scripts that have been previously savedn    compile and execute scriptsn    redirect Apple events to script contextsn    supply application-defined functions for use by scripting componentsn    control the recording process directly, turning recording off and on and saving the recorded script for use by your applicationYour application can perform these tasks as a client application regardless of whether it is scriptable or recordable. If your application is scriptable, however, it can execute scripts that control its own behavior, thus acting as both the client application and the server application for the corresponding Apple events. For example, your application can allow users to associate a script with a custom menu command that performs a series of routine actions on a selected object, sets preferences, or automates other actions within your application.You can also use scripting component routines to execute scripts that perform tasks for your application with the aid of other applications. For example, a user of a word-processing application might be able to attach a script to a specific word so that the application executes the script whenever that word is double-clicked. Such a script could trigger Apple events that cause other applications to look up and display related information, run a QuickTime movie, perform a calculation, play a voice annotation, and so on. Your application can associate a script with either Apple event objects or application-defined objects. Almost any user action can be used to trigger such a script: choosing a menu command, clicking a button, tabbing from one table cell to another, and so on. The script can be executed directly by the application when it detects a triggering action; or, if the script is associated with an Apple event object in the form of a script context, it can be executed automatically when a specified Apple event performs an action on that object.The rest of this section describes one way that an application could execute such a script. Suppose a forms application allows users to create custom forms that can include scripts associated with specific fields on the form. These scripts are executed when the user presses Enter or Tab in the appropriate field. For the purposes of this example, it doesn’t matter whether a field with which a script is associated is an Apple event object (which can be described in an object specifier record) or some other application-defined object (which can’t be described in an object specifier record). A company could use the forms application to create a custom order form for taking telephone orders. If the customer has ordered from the company before, the user can quickly retrieve the customer’s address from the company database by typing the customer’s name in a field and pressing the Tab key. In response, the application executes the script associated with the field. The script might look like this in AppleScript:set custName to field "Customer Name"tell application SurfDB    copy the first record in the table MyAddresses ¬        whose cell "Customer Name" = custName to Addressend tellset field "Street" to item 2 of Addressset field "City" to item 3 of Addressset field "Zip" to item 4 of AddressTo execute such a script (or to manipulate it any other way, such as when the form is first created), the forms application must previously have established a connection with the appropriate scripting component—in this case, the AppleScript component. When the user enters a customer name and presses Tab, the forms application calls scripting component routines to execute the script. As shown in Figure 7-4, the AppleScript component first sends the forms application a Get Data event that requests the contents of the “Customer Name” field and sets the variable custName to that value. It then sends SurfDB a Get Data event that requests the appropriate address information and copies it to the variable Address. (The replies to the Get Data events are not shown in Figure 7-4.) Finally, the AppleScript component sends the forms application a Set Data event that copies the address information from the variable Address to the appropriate fields. The AppleScript component needs to maintain the binding of the variables custName and Address throughout execution of the script. Scripting components bind variables with the aid of a script context, which is a script that maintains context information for the execution of other scripts. An application specifies a script context when it executes a script. The forms application in Figure 7-4 provides a context for the scripting component to use whenever it executes a script associated with a button. Figure 7-4    How an application uses the AppleScript component to execute a scriptIn the example shown in Figure 7-4, the application executes the script directly when the cursor is in the appropriate field and the user presses Tab or Enter. Your application can also associate such a script with an object in the form of a script context, so that the script context is executed whenever a specified Apple event acts on the field. The section “Using a Script Context to Handle an Apple Event,” which begins on page 7-25, describes this approach in more detail. See “Manipulating and Executing Scripts,” which begins on page 7-22, for an overview of methods your application can use to save and load script data, compile source data, and perform other useful tasks with scripting component routines. The chapter “Scripting Components” in this book provides full implementation details, including sample code and human interface guidelines for associating scripts with objects. Making Your Application ScriptableTo make your application scriptable, you need to n    define a hierarchy of Apple event objects within your application that you want client applications to be able to identify—that is, which objects can be contained by other Apple event objects in your application, which properties each kind of object can have, and so onn    write Apple event handlers, object accessor functions, and other routines required to implement the Apple events and related object classes that you want to supportn    create an 'aete' resourceThe chapters “Introduction to Apple Events,” “Responding to Apple Events,” and “Resolving and Creating Object Specifier Records” in this book describe how to perform the first two tasks. The extent to which scripts can control your application depends mainly on the extent of your application’s support for Apple events. For example, if your application does not provide the Apple event handlers and object accessor functions required to locate and manipulate windows, users will not be able to use scripts to control your application’s windows. Although you should use the definitions in the Apple Event Registry: Standard Suites whenever possible, you have considerable freedom to extend or limit your implementation of the standard Apple events according to the needs of your application.The OSA makes it possible to design new kinds of applications that always operate in the background and can be controlled only by means of scripts. For example, it is possible to design a simple telecommunications program that can log on to a network, send and receive text files created by another application, and perform other basic operations in response to scripts without providing any other form of user interface. Such an application would not need to support Apple events that control window movement, the File menu, or the Edit menu; instead, it would need to support only those Apple events that execute its basic telecommunications operations.At the other extreme, some applications allow users to arrange windows, palettes, and dialog boxes on their screen in many different ways, or to customize menus or other aspects of the presentation of information. If such an application can respond to scripts that control windows, dialog boxes, specialized preferences, and other aspects of the presentation of information, it can allow users who might not otherwise explore those capabilities to take advantage of them. For example, a naive user could execute a script that sets up a powerful word processor with the appropriate menus, window and palette arrangement, and formatting templates for a particular task, such as producing a company newsletter.Scripting components use 'aeut' and 'aete' resources to associate Apple event codes supported by your application with corresponding human-language terms used in scripts that control your application. Each scripting component supplies an 'aeut' resource, and each scriptable application provides an 'aete' resource. The next section introduces the 'aeut' and 'aete' resources. About Apple Event Terminology ResourcesAs explained in the chapter “Introduction to Apple Events” in this book, applications can support different combinations of the standard suites of Apple events. Applications can also extend the definitions of individual Apple events and object classes, or define custom Apple events and object classes. Scripting components use the Apple event user terminology resources, 'aeut' and 'aete', to associate the IDs, keywords, and other codes used in Apple events with the corresponding human-language terms used in scripts that control your application.  The Apple event user terminology ('aeut') resource contains terminology information for all the standard suites of Apple events defined in the Apple Event Registry: Standard Suites. The resource consists of a sequence of concatenated arrays that map human-language names to each of the following:n    the ID defined for each suiten    the Apple events defined for each suiten    the parameters defined for each Apple eventn    the Apple event object classes defined for each suiten    the properties defined for each object classn    the elements defined for each object classn    the key forms defined for each element classn    the comparison operators defined for each suiten    the values for enumerators defined for each suiteEach scripting component provides its own 'aeut' resource. A scripting component can also provide different versions of the 'aeut' resource; for example, the user terminology provided by the 'aeut' resource for the AppleScript Japanese dialect component is in Japanese. The IDs, keywords, and other codes listed in the 'aeut' resource are based on the Apple Event Registry: Standard Suites and do not vary from one version to another.An 'aete' resource has the same format as the 'aeut' resource but serves a different purpose. Each scriptable application must include its own 'aete' resource describing which of the standard suites listed in the 'aeut' resource it supports and providing other application-specific information. Since the human-language equivalents for the standard suites are defined in the 'aeut' resource, applications that support standard suites without any modifications do not have to define such equivalents; instead, they can simply list, in the 'aete' resource, the suites they support. The scripting component associates the standard suites listed in the 'aete' resource with the corresponding Apple event descriptions in its 'aeut' resource. Applications can also use the 'aete' resource to describe extensions to the standard suites, such as additional parameters for standard Apple events, additional properties and element classes for the standard Apple event object classes, and additional key forms for each element class. Information about such extensions must be included in the appropriate arrays of the 'aete' resource, along with the equivalent human-language terms. Similarly, an application can use the 'aete' resource to describe the parts of each standard suite it supports (if it doesn’t support the entire suite) and any custom Apple events or Apple event object classes defined by the application. The human language in which your Apple event extensions or custom Apple events are displayed in scripts depends on the corresponding user terminology you specify in your application’s 'aete' resource. Therefore, if your application implements such extensions or custom Apple events, you must provide a separate version of this resource for each localized version of your application.Scripting components can use the information in the 'aete' and 'aeut' resources in a variety of ways. The next section, “How AppleScript Uses Terminology Information,” describes how the AppleScript component uses these resources when it executes or records a script. The next chapter, “Apple Event Terminology Resources,” describes how to create an 'aete' resource for your application.If you want users to be able to control your application with scripts written in the AppleScript scripting language, you also need to know how the AppleScript component interprets AppleScript commands that trigger Apple events. In this way, you can make sure you support Apple events and specify the user terminology for your 'aete' resource in a way that translates easily into AppleScript statements. The section “Defining Terminology for Use by the AppleScript Component,” which begins on page 8-3, discusses these issues. If you implement Apple events so that they translate into logical and useful AppleScript scripts, your implementation will probably work well with other scripting components that resemble AppleScript. How AppleScript Uses Terminology InformationThe manner in which the AppleScript component uses the information in 'aete' resources depends on specific characteristics of the AppleScript scripting language. An AppleScript expression consists of an internal compiled form and corresponding expressions in dialects, or versions of the AppleScript scripting language that resemble different human languages. Users can select the dialect they want to use from within the Script Editor application. If a script is displayed in a window and the user selects a different dialect, the AppleScript component converts the script to the new dialect. Users can install additional dialects as necessary.This section describes how the AppleScript component uses the information in the 'aeut' and 'aete' resources, not how it obtains that information. For a description of the methods available to scripting components for loading information from terminology resources, see “Dynamic Loading of Terminology Information” on page 7-20.Figure 7-5 shows how the AppleScript component uses information from its 'aeut' resource and an application’s 'aete' resource to execute a script that consists of AppleScript statements displayed in a script editor window. When a user executes the script from the script editor (for example, by pressing the Run button in the Script Editor application), the AppleScript component first compiles the script into the equivalent compiled expressions, using information from its 'aeut' resource and the application’s 'aete' resource to map application-specific terms in the script with the equivalent Apple events and Apple event parameters. The AppleScript component then evaluates each expression and performs actions or sends Apple events as appropriate. For example, the AppleScript component evaluates the expression2*3as the value 6. The AppleScript component can then decompile and display this value in the script editor window, assign it to a variable, or otherwise manipulate it according to the rest of the script. However, to compile the statementprint Chart 1 of document "Sales Report"the AppleScript component uses its 'aeut' resource and the SurfWriter application’s 'aete' resource to associate the terms used in the script with the Print Apple event, the object class for charts, and the object class for documents, so that it can describe the event accurately in the form of a compiled expression. When the AppleScript component evaluates the compiled expression, it creates and sends a Print event whose direct parameter is an object specifier record that the SurfWriter application can resolve as the specified chart. The SurfWriter application then handles the Apple event by printing the chart as requested.Figure 7-5    Role of the 'aete' and 'aeut' resources when the AppleScript component compiles and executes a scriptNote that although Figure 7-5 shows only one Apple event generated as a result of executing a script, the AppleScript component could also send a series of Apple events to several different applications, depending on the content of the script.A recordable application generally needs to be able to send itself a subset of the Apple events that it can handle as a scriptable application. A recordable event is any Apple event that any recordable application sends to itself while recording is turned on for the local computer (with the exception of events that the application explicitly identifies as not for recording purposes). After a user turns on recording from the Script Editor application, the Apple Event Manager sends copies of all recordable events to Script Editor. A scripting component previously selected by the user handles each copied event for Script Editor by translating the event and recording the translation as part of a Script Editor script. When a scripting component executes a recorded script, it sends the corresponding Apple events to the applications in which they were recorded.Every scripting component must be able to handle copies of recordable events sent to a recording process (such as Script Editor) by recording them in an appropriate form. For example, as shown in Figure 7-6, the AppleScript component records copies of recordable events in the form of compiled expressions. The AppleScript component can then use information from its 'aeut' resource and the application’s 'aete' resource to translate the compiled expressions into the appropriate human-language terms and display them as AppleScript statements in the script editor window. When the user opens a recorded script in Script Editor and presses Run, the AppleScript component recompiles the script if necessary and sends the Apple events described by the compiled expressions to the SurfWriter application, just as in Figure 7-5.Figure 7-6    Role of the 'aete' and 'aeut' resources when the AppleScript component records and decompiles a scriptIf the user copies a chart from one document to another document and the SurfWriter application performs this task by sending itself Apple events, the equivalent statements in the recorded script might look something like this:tell application "SurfWriter"    select Chart 1 of document "Sales Chart"    copy    select paragraph 3 of document "Monthly Report"    pasteend tellTo display these statements in the script editor window, the AppleScript component first translates the Set Data, Copy, and Paste Apple events sent by the recordable application into compiled expressions. It then uses information from its 'aeut' resource and the application’s 'aete' resource to decompile the compiled expressions and pass the equivalent source data to the script editor for display to the user. After completing a recording session, the user can edit and save the resulting script and execute it again at any time. As shown in Figure 7-5 and Figure 7-6, the AppleScript component uses information it obtains from the 'aeut' and 'aete' resources when it is compiling and decompiling scripts. Other scripting components might use the same information during execution or recording, or in other ways that are specific to each component.  Dynamic Loading of Terminology InformationWhen a scripting component needs information about the user terminology defined in your application’s 'aete' resource, it sends a Get AETE event to your application. If your application does not handle the Get AETE event, the scripting component reads the terminology information it needs directly from your application’s 'aete' resource. Your application does not need to handle the Get AETE event unless it provides separate 'aete' resources for plug-in components. If your application does provide separate plug-in components, the Get AETE event allows it to gather terminology information from the 'aete' resources for the components that are currently running and add that information to the reply event. If your application handles the Get AETE event, you must also provide a scripting size resource. A scripting size resource is a resource of type 'scsz' that provides information about an application’s capabilities and preferences for use by scripting components.To take advantage of dynamic loading, your application must be running. Note that if your application does not provide a handler for the Get AETE event, the scripting component can obtain terminology information directly from your application’s 'aete' resource even if your application is not running.  Making Your Application RecordableIf you decide to make your application scriptable, you can also make it recordable. A recordable application is an application that uses Apple events to report user actions to the Apple Event Manager for recording purposes. A recordable event is any Apple event that a recordable application sends to itself while recording is turned on for the local computer (with the exception of events sent with the kAEDontRecord flag set in the sendMode parameter of AESend). When a user turns on recording by clicking the Record button in the Script Editor application, the Apple Event Manager sends copies of all subsequent recordable events to Script Editor. The AppleScript component handles each copied event for Script Editor by translating it into compiled expressions and recording the compiled expressions as part of a script. (Figure 7-6 on page 7-19 shows how the AppleScript component uses the 'aete' and 'aeut' resources when it records a script.) The user can view the equivalent decompiled source data in Script Editor while the script is being recorded. When a user executes a recorded script, the AppleScript component sends the corresponding Apple events to the applications in which they were recorded.Applications generally have two parts: the code that implements the application’s user interface and the code that actually performs the work of the application when the user manipulates the interface. One way to make your application recordable is to separate these two parts of your application, using Apple events to connect user actions with the work your application performs. This is called factoring your application. In a fully factored application, almost all tasks are carried out in response to Apple events. The application translates low-level events that result in significant actions into recordable Apple events and then sends them to itself.Factoring your application is the recommended method of making your application recordable. However, it is also possible for your application to report user actions by means of Apple events even though it actually performs those actions by some means other than Apple events. You can indicate that you want the Apple Event Manager to record events in this manner, without executing them, by adding the constant kAEDontExecute to the sendMode parameter of AESend.Before you decide how to map the user’s potential actions to recordable Apple events supported by your application, you need to answer these questions:n    What are the significant (that is, undoable) actions a user can perform with your application that you want to record? n    Which actions can you execute by means of Apple events, and which actions should cause Apple events to be sent but not executed?n    How do you want to record actions that can be described in a scripting language in several different ways?For example, if your application is a word processor, the user’s selection of a range of text should probably not generate an Apple event, because users often select various different pieces of text before deciding to do something to the selection. However, if a user changes the font of a selection, a recordable word processor should generate a corresponding Apple event so that the scripting component can record the change. In general, a recordable application should generate Apple events for any user action that the user could reverse by choosing Undo. A recordable application can usually handle a greater variety of Apple events than it can record, because it must record the same action the same way every time even though Apple events might be able to trigger that action in several different ways.For more information about recordable applications, factoring, and the Apple Event Manager’s recording mechanism, see the chapter “Recording Apple Events” in this book. For a description of the role of the 'aete' and 'aeut' resources when the AppleScript component records a script, see “How AppleScript Uses Terminology Information,” which begins on page 7-17. Manipulating and Executing ScriptsYour application can use scripting component routines to manipulate and execute scripts written in any scripting language based on the OSA. This section describes how scripting components use script data and summarizes some of the tasks your application can perform by calling the standard scripting component routines.  Your application can manipulate and execute scripts regardless of whether it is scriptable or recordable. However, if your application is scriptable, you can easily make it capable of manipulating and executing scripts that control its own behavior. For example, the forms application shown in Figure 7-4 on page 7-13 uses standard scripting component routines to execute a script whenever the cursor is in the appropriate field and the user presses Enter or Tab. Applications can also use scripting component routines to allow users to edit, recompile, save, and load such scripts in order to adapt them to their own purposes.Before using any scripting component routines, your application must open a connection with at least one scripting component. After opening a connection with a component, your application receives a component instance that it can use as the first parameter for any scripting component routine. You can use the Component Manager to establish a connection with the generic scripting component or to establish an explicit connection with any other scripting component. Your application can open connections with different scripting components under different circumstances and, if necessary, simultaneously.To manipulate or execute scripts written in any scripting language based on the OSA, your application can open a connection with the generic scripting component. The generic scripting component in turn attempts to open connections dynamically with the appropriate scripting component for a given script. If your application opens a connection with the generic scripting component, it can load and execute scripts created by any scripting component that is registered with the Component Manager on the current computer. The generic scripting component also provides routines that allow you to determine which scripting component created a particular script and to perform other useful tasks when you are using multiple scripting components.To manipulate and execute scripts written in a single scripting language only, your application can open an explicit connection with the scripting component for that language. In this case your application can load and execute only those scripts that were created by that component; however, your application can also take advantage of additional routines and other special capabilities provided by the component.After your application has established a connection with the appropriate scripting component for an existing script, it can use the standard scripting component routines to execute scripts. A script that has not yet been compiled consists of source data, or statements in a scripting language. Before executing source data, your application must use scripting component routines to compile it so that the scripting component can keep track of it in memory and execute it.  Scripting components can refer to at least three kinds of script data in memory:n    A compiled script consists of compiled code that an application can decompile into source data or execute using the standard scripting component routines. n    A script value consists of an integer, a string, a Boolean value, constants, PICT data, or any other fixed data returned or used by a scripting component in the course of executing a script.n    A script context maintains context information for the execution of other scripts. A script context can also contain executable statements in a scripting language. Like a compiled script, a script context can be decompiled as source data.For example, a script context can contain user-defined handlers for specific Apple events. In AppleScript, a script context that contains such handlers or other executable statements is called a script object. Handlers in a script object resemble HyperTalk message handlers. They consist of AppleScript statements and have no corresponding entry in Apple event dispatch tables.   Scripting components keep track of script data in memory by means of script IDs of type OSAID. TYPE OSAID = LongInt;A scripting component assigns a script ID to a compiled script or script context whenever the component creates or loads the corresponding script data. The scripting component routines that compile, load, and execute scripts all return script IDs, and you must pass valid script IDs to many of the other routines that manipulate scripts. Applications most commonly use scripting component routines to n    compile source data and execute the resulting compiled script, so that a user can create a new script and execute it immediately from within the applicationn    get a handle to script data in a form that can be saved, and load and execute the script data again when necessaryn    allow users to modify a script, then recompile and save the scriptn    redirect Apple events to script contextsThe remainder of this section provides an overview of the scripting component routines you can use to perform these tasks. Your application can also use scripting component routines to n    get information about scriptsn    get information about scripting componentsn    coerce script values to descriptor records and vice versan    set a resume dispatch function and alternative send, create, and active functions for use by a scripting componentn    control the recording process directly, turning recording off and on and saving the recorded script for use by your applicationThe chapter “Scripting Components” in this book provides detailed information about using all the standard scripting component routines as well as additional routines provided by the AppleScript component and the generic scripting component.Compiling, Saving, Modifying, and Executing ScriptsThis section introduces some of the scripting component functions your application can use to compile, save, modify, and execute scripts.To create and execute a script using the Script Editor application, a user can type the script, then press the Run button to execute it. Your application can provide similar capabilities by using these functions to compile source data and execute the resulting compiled script:n    The OSACompile function takes a descriptor record with a handle to source data (usually text) and a script ID. If you specify kOSANullScript instead of an existing script ID, OSACompile returns a script ID for the new compiled script, which you can then pass to the OSAExecute function.n    The OSAExecute function takes a script ID for a compiled script and a script ID for a script context, executes the script, and returns a script ID for the resulting script value.The binding of any global variables in the compiled script is determined by the script context whose script ID you pass to OSAExecute. If you pass kOSANullScript instead of the script ID for a script context, the scripting component provides its own default context. If you want to provide your own script context rather than using the scripting component default context, you can use either OSACompile or OSAMakeContext to create a script context, which you can load and store just like a compiled script.After creating a script and trying it out, a user may want to save it for future use. Your application should normally save its scripts as script data rather than source data, so that it can reload and execute the data without recompiling it. Before saving script data, you must first call the OSAStore function to get a handle to the data in the form of a descriptor record. You can then save the data to disk as a resource or write it to the data fork of a document. To allow a user to reload and execute a previously compiled and saved script, your application can call these functions:n    The OSALoad function takes a descriptor record that contains a handle to the saved script data and returns a script ID for the compiled script.n    The OSAExecute function takes a script ID for a compiled script and a script ID for a script context, executes the script, and returns a script ID for the resulting script value.In most cases you will want to allow users to modify saved scripts and save them again. To allow a user to modify and save a compiled script, your application can call these functions:n    The OSAGetSource function takes a script ID and returns a descriptor record with a handle to the equivalent source data.n    The OSACompile function takes a descriptor record with a handle to source data and a script ID, and returns the same script ID updated so that it refers to the modified and recompiled script.n    The OSAStore function takes a script ID and returns a copy of the corresponding script data in the form of a storage descriptor record.You can pass the script ID for the compiled script to be modified to the OSAGetSource function, which returns a descriptor record with a handle to the equivalent source data. Your application can then present the source data to the user for editing. When the user has finished editing the source data, you can pass the modified source data and the original script ID to the OSACompile function to update the script ID so that it refers to the modified and recompiled script. Finally, to obtain a handle to the modified script data so you can save it in a resource or write it to the data fork of a document, you can pass the script ID for the modified compiled script to the OSAStore function. If your application has no further use for a compiled script or a resulting script value after successfully loading, saving, compiling, or executing a script, you can use the OSADispose function to release the memory assigned to them. The OSADispose function takes a script ID and releases the memory assigned to the corresponding script data. A script ID is no longer valid after the memory associated with it has been released. This means, for example, that a scripting component may assign a different script ID to the same compiled script each time you load it, and that a scripting component may reuse a script ID that is no longer associated with a specific script.“Using Scripting Component Routines,” which begins on page 10-7, provides more information about the standard scripting component routines described in this section. Using a Script Context to Handle an Apple EventOne way to associate a script with an object is to associate a script context with a specific Apple event object—that is, with any object in your application that can be identified by an object specifier record. When an Apple event acts on an Apple event object with which a script context is associated, your application attempts to use the script context to handle the Apple event. This approach can be useful if you want to associate many different scripts with many different kinds of objects. Figure 7-7 illustrates one way that an application can use a script context to handle an Apple event. This example shows how you can use a general Apple event handler to provide initial processing for all Apple events received by your application. If an Apple event acts on an object with which a script context is associated, the general handler attempts to use the script context to handle the event.The SurfWriter application in Figure 7-7 associates script contexts (called script objects in AppleScript) with geometric shapes such as circles or squares. These script contexts can contain one or more user-defined handlers for specific Apple events. For example, the script context shown in Figure 7-7 is associated with a circle and contains this handler:on move to {x, y}    continue move to {x, item 2 of position of this}end moveThis handler exists only as AppleScript statements in the script context and doesn’t have an entry in SurfWriter’s Apple event dispatch table. SurfWriter does have its own standard Apple event handlers installed in its Apple event dispatch table. When SurfWriter receives a Move event that acts on the circle with which this script context is associated, SurfWriter uses the handler in the script context to modify its own standard handling of the event. The rest of this section describes how this works.Figure 7-7    Using a handler in a script context to handle an Apple eventThe MyGeneralAppleEventHandler function in Figure 7-7 is installed in SurfWriter’s special handler dispatch table. Thus, MyGeneralAppleEventHandler provides initial processing for all Apple events received by SurfWriter. When it receives an Apple event, MyGeneralAppleEventHandler checks whether a script context is associated with the object on which the event acts. If so, MyGeneralAppleEventHandler passes the event and a script ID for the script context to the OSADoEvent function. If not, MyGeneralAppleEventHandler returns errAEEventNotHandled, which causes the Apple Event Manager to look for the appropriate handler in SurfWriter’s Apple event dispatch table.The OSADoEvent function looks for a handler in the specified script context that can handle the specified event. If the script context doesn’t include an appropriate handler, OSADoEvent returns errAEEventNotHandled. If the script context includes an appropriate handler (in this example, a handler that begins on move), OSADoEvent attempts to use the handler to handle the event.When it encounters the continue statement during execution of the on move handler shown in Figure 7-7, the AppleScript component calls SurfWriter’s resume dispatch function. A resume dispatch function takes an Apple event and invokes the application’s default handler for that event directly, bypassing the application’s special handler dispatch table and the MyGeneralAppleEventHandler handler (or its equivalent). In this case, the AppleScript component uses SurfWriter’s default Move handler to move the circle to a different location than the one specified in the original Move event. The location specified by {x, item 2 of position of this} has the same horizontal coordinate as the location specified by the original event, but specifies the circle’s original vertical coordinate (item 2 of the circle’s original position), thus constraining motion to a horizontal direction.The AppleScript component calls the resume dispatch function as soon as it encounters a continue statement during script execution. For example, if the handler in Figure 7-7 contained additional indented statements after the continue statement, the AppleScript component would proceed with the execution of those statements after calling the resume dispatch function successfully.A script context can modify the event and use the default Apple event handler to execute the modified event, as in this example; or it can override the default handler completely, performing some completely different action; or it can perform some action and then pass the original event to the application’s default handler to be handled in the usual way. Script contexts associated with Apple event objects thus provide a way for users to modify or override the way an application responds to a particular Apple event that manipulates those objects.A general Apple event handler can use the OSAExecuteEvent function instead of OSADoEvent to execute a script context. The main difference between these functions is is that OSAExecuteEvent returns the script ID for the resulting script value, whereas OSADoEvent returns a reply event.To create a script context, pass the source data for the scripting-language statements you want the script context to contain to OSACompile with the modeFlags parameter set to kOSACompileIntoContext. The resulting script context is identical to a script context returned by the OSAMakeContext function, except that it contains compiled statements.“Using a Script Context to Handle an Apple Event,” which begins on page 10-19, describes this method of executing a script in more detail.       Listing 8-0Table 8-0Apple Event Terminology ResourcesContentsDefining Terminology for Use by the AppleScript Component8-3Structure of Apple Event Terminology Resources8-8Creating an Apple Event Terminology Extension Resource8-13Supporting Standard Suites Without Extensions8-14Extending the Standard Suites8-16Supporting Subsets of Suites8-23Supporting New Suites8-23Handling the Get AETE Event8-23Reference to Apple Event Terminology Resources8-26Header Data for an Apple Event Terminology Resource8-27Suite Data for an Apple Event Terminology Resource8-27Event Data8-29Object Class Data8-36Comparison Operator Data8-42Enumeration and Enumerator Data8-43The Scripting Size Resource8-45Apple Event Terminology ResourcesThis chapter describes the resource structure used by both the 'aeut' and 'aete' resources and explains how to create an 'aete' resource for your application. It also explains how applications that support additional plug-in modules, each with its own 'aete' resource, can write a handler for the Get AETE event that collects the 'aete' resources from the modules that are currently running.Before you read this chapter, you should read the chapter “Introduction to Scripting” in this book and the chapters about the Apple Event Manager that are relevant to your application. The first section in this chapter describes how the AppleScript component interprets AppleScript statements that trigger Apple events. The first section also explains how to define both Apple events and the corresponding user terminology for your application in a way that translates easily into AppleScript statements. If you implement Apple events so that they translate into logical and useful AppleScript scripts, your implementation will probably work well with other scripting components that resemble AppleScript.The next two sections describe how ton    create an 'aete' resourcen    handle the Get AETE eventFor details about the structure of the data in an 'aeut' resource and an 'scsz' resource, see “Reference to Apple Event Terminology Resources,” which begins on page 8-26.Defining Terminology for Use by the AppleScript ComponentYou should keep two principles in mind when you are defining the Apple event object hierarchy and corresponding terminology for your application: n    Avoid defining new Apple events unless absolutely necessary. For example, instead of defining a custom Find event, use the Get Data event with whose tests. (For more information about whose tests, see the chapter “Resolving and Creating Object Specifier Records” in this book.)n    Use existing object classes, or if you must define your own, define them in a general fashion.This section describes how the terms you specify in your application’s 'aete' resource are used in AppleScript statements that control your application. Before you implement the Apple event object hierarchy for your application, try out your proposed user terminology in AppleScript statements that use the standard syntax forms described here. This will help you discover some of the advantages and disadvantages of both your proposed object hierarchy and the human-language terminology you are planning to use.Some AppleScript commands, such as if, repeat, and tell, are executed directly by the AppleScript component and do not correspond to Apple events. Other commands trigger Apple events when the AppleScript component evaluates them.AppleScriptcommand    Corresponding Apple event    open    Open    close    Close    save    Save    move    Move    delete    Delete    set    Set Data    The AppleScript component interprets the terms used in scripts according to rules defined by the AppleScript language. For example, the open command must be followed by an argument that specifies the objects to open, and the save command must be followed by an argument that specifies the objects to save. The AppleScript component uses the information in an application’s 'aete' resource to map the human-language terms used in these arguments to specific Apple event keywords and codes, so that it can construct object specifier records that describe the objects on which the Open and Save events act. In general, the syntax for AppleScript commands that trigger Apple events follows this pattern: event name expression parameter name expression . . . parameter name expressionThe underlined terms are supplied by the AppleScript component’s 'aeut' resource, by the application’s 'aete' resource, or by the 'aeut' resource available on the current computer. The argument that follows event name corresponds to the direct parameter for the event, if there is one. Each subsequent argument corresponds to an additional parameter. An argument that corresponds to a direct parameter can use any of the syntax forms shown in Table 8-1. These forms correspond to the key forms that can be used to identify the key data in an object specifier record.Table 8-1    Syntax for AppleScript arguments that correspond to direct parametersSyntax of argument    AppleScript example    Key form    property name     the font    formPropertyID    class name expression     table "Fred"table 4    formNameformAbsolutePosition    class name before | after expression     word after table 2    formRelativePosition    class name expression thru expression    words 1 thru 30    formRange    every class name whose expression    every word whose¬  font = "Palatino"    formWhose    expression of expression     first row of¬  table "Fred"    Any key form; sets container for elements or properties    If the Apple event object hierarchy for your application requires you to specify terms in your 'aete' resource that are not included in the 'aeut' resource, make sure those terms read naturally when they appear in AppleScript statements that use the syntax shown in Table 8-1. Any of the underlined terms in the table may be supplied by your application’s 'aete' resource.For example, in the AppleScript statement copy name to expressionthe argument name corresponds to a direct parameter that can use any of the syntax variations shown in Table 8-1. The word to and the expression that follows it correspond to an additional parameter that describes the location to which to copy the objects described by the direct parameter.Many AppleScript commands, including the copy command, take additional arguments that correspond to insertion location descriptor records, which are descriptor records of type typeInsertionLoc defined as part of the Core suite. An insertion location descriptor record is a coerced AE record that consists of two keyword-specified descriptor records with the following keywords:Keyword    Description    keyAEObject    An object specifier record that identifies a single container    keyAEPosition    A constant that specifies where to put the Apple event object described in an Apple event’s direct parameter in relation to the container specified in the descriptor record with the keyword keyAEObject     You can specify one of these constants for the data in a descriptor record identified by the keyword keyAEPosition:Constant    Meaning    kAEBefore    Before the container     kAEAfter    After the container    kAEBeginning    In the container and before all other elements of the same class as the object being inserted     kAEEnd    In the container and after all other objects of the same class as the object being inserted    kAEReplace    Replace the container    The syntax that corresponds to an insertion descriptor record can take any of the forms shown in Table 8-2.Table 8-2    Syntax for AppleScript arguments that correspond to insertion location descriptor recordsSyntax of argument    AppleScript example    keyAEPosition constant    before | after expression    before Figure 1    kAEBefore | kAEAfter    beginning of | end of expression    end of window 2    kAEBeginning | kAEEnd    expression    Figure 1    kAEReplace    For example, in the AppleScript statement copy Chart 1 of document "Sales Chart" to before Figure 1the term copy corresponds to a Clone event, and Chart 1 of document "Sales Chart" corresponds to the direct parameter for the Clone event. The term to is the human-language name specified by the 'aeut' resource for the additional parameter identified by the keyword kAEInsertHere, which always consists of an insertion location descriptor record. The term before corresponds to the constant kAEBefore in the descriptor record identified by the keyword keyAEPosition, and Figure 1 corresponds to the object specifier record identified by the keyword keyAEObject. The AppleScript component handles statements that describe the replacement of one object with another differently from statements that specify an insertion location before, after, at the beginning of, or at the end of an object. For example, in the statementcopy Chart 1 of document "Sales Chart" to Figure 1the term to is the human-language name for the additional parameter identified by the keyword kAEInsertHere. When to is followed immediately by an element expression like Figure 1, the Clone Apple event sent by the AppleScript component includes an additional parameter that consists of an object specifier record for Figure 1. When your application requests the parameter as an insertion location descriptor record, a system coercion handler installed by the AppleScript component converts the object specifier record to an insertion location descriptor record that specifies kAEReplace in the descriptor record identified by the keyword keyAEPosition.If your application defines any extensions to the standard Apple events or object classes that require the use of insertion locations, use standard insertion location descriptor records to specify them, and make sure your Apple event object hierarchy and the corresponding human terminology in your 'aete' resource allow the AppleScript component to translate insertion location descriptor records into meaningful statements in an AppleScript dialect. Unlike most other AppleScript commands, the copy command causes the AppleScript component to send different Apple events under different circumstances. In the examples just discussed, the copy command corresponds to a Clone event. However, after evaluating the statementstell application "SurfWriter"        copy table "Summary of Sales" of document¬            "Sales Report" to Totalsend tellthe AppleScript component sends a Get Data event and sets the variable Sales91 to the value of the returned data; and the statementstell application "SurfCharter"        copy Totals to Chart 1 of document "Sales Chart"end tellcause the AppleScript component to send a Set Data event that sets the data in the specified chart to the value of the variable Totals.All scriptable applications should support the Get Data, Set Data, and Clone events for all Apple event objects that a user might want to manipulate from a script with the copy command. Scriptable applications should also support the other core events and any appropriate functional-area events.If you find it difficult to come up with meaningful AppleScript statements based on your proposed implementation of Apple events, you may need to rethink your implementation.   Structure of Apple Event Terminology ResourcesTable 8-3 summarizes the resource structure used by both the 'aeut' and 'aete' resources. Each asterisk (*) in the table indicates the beginning of an array. Each array can contain any number of items, including both additional arrays and specific definitions (n).Table 8-3    Structure of the 'aeut' and 'aete' resourcesn Template version    n Language code    * Array of suites:                       n Suite information                               * Array of events:                                                          n Event information (including information about the direct parameter)                                                          * Array of other parameters:                                                                                     n Parameter information                               * Array of classes:                                                          n Class description                                                          * Array of properties:                                                                                     n Property information                                                          * Array of elements:                                                                                     n Element information                                                                                     * Array of key forms:                                                                                                                n Key form information                               * Array of comparison operators:                                                          n Comparison operator information                               * Array of enumerations:                                                          n Enumeration information                                                          * Array of enumerators:                                                                                     n Enumerator information    Listing 8-1 shows the resource type declaration in Rez format for the 'aeut' resource, which can also serve as a template for an 'aete' resource. (Rez is a resource compiler available with the MPW programming environment.) For complete descriptions of all the fields shown in Listing 8-1, see “Reference to Apple Event Terminology Resources,” beginning on page 8-26.Listing 8-1    Resource type declaration for the 'aeut' resource  type 'aeut' {    hex byte;                                            /*major version in binary-coded */                                                /* decimal (BCD)*/    hex byte;                                            /*minor version in BCD*/    integer            Language, english = 0, japanese = 11;                                                    /*language code*/    integer            Script, roman = 0;                                /*script code                */    integer = $$Countof(Suites);    array Suites {        pstring;                                        /*human-language name of suite    */        pstring;                                        /*suite description*/        align word;                                        /*alignment*/        literal longint;                                        /*suite ID*/        integer;                                        /*suite level                */        integer;                                        /*suite version*/        integer = $$Countof(Events);        array Events {            pstring;                                    /*human-language name of event*/            pstring;                                    /*event description*/            align word;                                    /*alignment*/            literal longint;                                    /*event class                */            literal longint;                                    /*event ID            */            literal longint                        noReply = 'null';                            /*reply type                */            pstring;                                    /*reply description                        */            align word;                                    /*alignment            */            boolean            replyRequired,                        /*if the reply is */                        replyOptional;                        /* required*/            boolean            singleItem,                        /*if the reply must be a list*/                        listOfItems;                                    boolean             notEnumerated,                        /*if the type is                     enumerated*/                        enumerated;                                    boolean            reserved;                        /*these 13 bits are reserved; */            boolean            reserved;                        /* set them to "reserved"*/            boolean            reserved;                                    boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved,                        /*if event is verb event or nonverb */                        nonVerbEvent;                        /* event; used by Japanese dialect*/            literal longint                        noParams = 'null'; /*direct param type*/            pstring;                                    /*direct param description*/            align word;                                    /*alignment*/            boolean            directParamRequired,                         /*if the direct param is required*/                        directParamOptional;            boolean             singleItem,                        /*if the param must be a list*/                        listOfItems;            boolean             notEnumerated,                        /*if the type is enumerated*/                        enumerated;            boolean            doesntChangeState,                         /*if the event changes server's state                                                */                        changesState;            boolean            reserved;                        /*these 12 bits are reserved;                                     */            boolean            reserved;                        /* set them to "reserved"        */            boolean            reserved;                                    boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved;            boolean            reserved;            integer = $$Countof(OtherParams);            array OtherParams {                pstring;                                /*human-language name for parameter*/                align word;                                /*alignment*/                literal longint;                                /*parameter keyword*/                literal longint;                                /*parameter type*/                pstring;                                /*parameter description*/                align word;                                /*alignment*/                boolean            required,                    /*if param is required*/                            optional;                boolean             singleItem,                    /*if the param must be a list*/                            listOfItems;                boolean             notEnumerated,                    /*if the type is enumerated                                    */                            enumerated;                boolean            isNamed,                    /*indicates if this should be the */                            isUnnamed;                    /* unnamed parameter; only one                                         */                                                /* parameter can be so marked; set to */                                                /* reserved if not required*/                boolean            reserved;                    /*these 9 bits are reserved                                    ; */                boolean            reserved;                    /* set them to "reserved"*/                boolean            reserved;                boolean            reserved;                boolean            reserved;                boolean            reserved;                boolean            reserved;                boolean            reserved;                boolean            reserved;                boolean            notFeminine,                    /*feminine; set to reserved if not                                                 */                            feminine;                    /* required*/                boolean            notMasculine,                    /*masculine            ; set to reserved if not                                 */                            masculine;                    /* required*/                boolean            singular,                            plural;                    /*plural*/            };        };        integer = $$Countof(Classes);        array Classes {            pstring;                                    /*human-language name for class*/            align word;                                    /*alignment*/            literal longint;                                    /*class ID*/            pstring;                                    /*class description                        */            align word;                                    /*alignment            */            integer = $$Countof(Properties);            array Properties {                pstring;                                /*human-language name for property*/                align word;                                /*alignment            */                literal longint;                                /*property ID                */                literal longint;                                /*property class                    */                pstring;                                /*property description*/                align word;                                /*alignment            */                boolean            reserved;                    /*reserved*/                boolean            singleItem,                    /*if the property must be a list                                        */                            listOfItems;                                    boolean            notEnumerated,                    /*if the type is                     enumerated*/                            enumerated;                                boolean            readOnly,                    /*can only read it*/                            readWrite;                    /*can read or write it*/                boolean            reserved;                    /*these 9 bits are reserved; */                boolean            reserved;                    /* set them to "reserved"                                */                boolean            reserved;                            boolean            reserved;                boolean            reserved;                boolean            reserved;                boolean            reserved;                boolean            reserved;                boolean            reserved;                                    boolean            notFeminine,                    /*feminine; set to reserved if not                                                 */                            feminine;                    /* required*/                boolean            notMasculine,                    /*masculine            ; set to reserved if not                                 */                            masculine;                    /* required*/                boolean            singular,                            plural;                    /*plural*/            };            integer = $$Countof(Elements);            array Elements {                literal longint;                                /*element class*/                integer = $$Countof(KeyForms);                array KeyForms {                                /*list of key forms                        */                    literal longint                                            formAbsolutePosition = 'indx',                    formName = 'name';                            /*key form ID*/                };            };        };        integer = $$Countof(ComparisonOps);        array ComparisonOps {            pstring;                                    /*human-language name for */                                                /* comparison operator            */            align word;                                    /*alignment*/            literal longint;                                    /*comparison operator ID                                */            pstring;                                    /*comparison operator description*/            align word;                                    /*alignment*/        };        integer = $$Countof(Enumerations);        array Enumerations {                                        /*list of enumerations*/            literal longint;                                    /*enumeration ID*/            integer = $$Countof(Enumerators);            array Enumerators {                                    /*list of enumerators*/                pstring;                                /*human-language name for enumerator    */                align word;                                /*alignment*/                literal longint;                                /*enumerator ID                    */                pstring;                                /*enumerator description                                */                align word;                                /*alignment            */            };        };    };}; Creating an Apple Event Terminology Extension ResourceScriptable applications must include an Apple event terminology extension ('aete') resource. You use an 'aete' resource to inform scripting components about the extent of your application’s support for the standard Apple event suites, any custom Apple events or Apple event objects defined by your application, and the corresponding human-language terms for use in scripts that control your application. The format of the 'aete' resource is identical to that of the 'aeut' resource, although it serves a different purpose. The 'aeut' resource maps human-language names to IDs, keywords, and other codes used in the Apple events described by the current edition of the Apple Event Registry: Standard Suites. The 'aete' resource for an application uses the same format to accomplish the following:n    Indicate when a set of definitions for a particular suite included in the 'aeut' resource is supported in its entirety by the application. For example, an application can indicate that it supports all of the 'aeut' resource definitions for the Required and Core suites simply by identifying the suite as a whole in its 'aete' resource; the detailed information for each standard suite does not need to be repeated.n    Describe extensions, if any, to the definitions included in the 'aeut' resource, such as additional parameters for standard Apple events, additional properties and element classes for standard object classes, and additional key forms for each element class. For example, an application can indicate that it supports all of the definitions for the Required and Core suites included in the 'aeut' resource, an additional parameter for one of the core events defined in the 'aeut' resource, and an additional property for one of the core object classes defined in the 'aeut' resource.n    Describe the standard Apple events and object classes that belong to suites the application does not support in their entirety.n    Describe the application’s custom suite—that is, the application’s custom Apple events and object classes, if any.By specifying a suite ID, suite level, and suite version, your application can indicate that it supports an entire suite. Because the 'aeut' resource provided by each scripting component lists the human-language terms for all the standard suites, you do not have to repeat this information if you support a suite in its entirety. If you support a subset of a standard suite, you must list all the Apple events, Apple event parameters, object classes, and so on and equivalent human-language terms for the parts of the suite your application does support.You can include at most one 'aete' resource per application or per module. The language code for this resource must match the language code of the language for which you are developing your application. Applications that support additional modules with their own 'aete' resources must provide an 'scsz' resource and handle the Get AETE event as described in “Handling the Get AETE Event,” which begins on page 8-23.IMPORTANTEach human-language term supported by an application should correspond to a unique Apple event ID, keyword, or other code in either the application’s 'aete' resource or the 'aeut' resource. For example, since the 'aeut' resource defines “size” as the human-language equivalent for the property identified by the four-character code 'ptsz' (the pPointSize property of text objects), an application’s 'aete' resource must not define “size” as the human-language equivalent for some other part of an Apple event or object class. However, more than one human-language term can correspond to the same Apple event ID or code. For example, an application’s 'aete' resource can define a second human-language term, “point size,” that corresponds to the Apple event identifier 'ptsz'.sThe AppleScript Software Developers’ Kit (available from APDA) includes a tool that allows you to specify your application’s support for Apple events and creates the equivalent 'aete' resource. The previous section, “Structure of Apple Event Terminology Resources,” describes the basic format used by both the 'aeut' and 'aete' resources. The sections that follow provide examples of 'aete' resources that can be generated with the tools in the AppleScript Software Developers’ Kit. Supporting Standard Suites Without ExtensionsTo indicate that your application supports a standard suite in its entirety, without any extensions, your 'aete' resource needs to provide only the information that identifies the suite. For example, Listing 8-2 shows the Rez input for an 'aete' resource provided by an application that supports the entire Required and Core suites with no omissions or extensions.Every 'aete' resource must provide the major and minor version numbers for the content of the resource (1 and 0 in Listing 8-2) and the language code (English in Listing 8-2). For each suite that an application supports in its entirety, without extensions, the 'aete' resource provides only the name, suite description, suite ID, suite level (1 for all current suites), and suite version (1 for all current suites). If the 'aete' resource provides an empty string as the human-language name for such a suite, a scripting component uses the name provided for the corresponding suite by the 'aeut' resource. If an application does not extend or omit any of the definitions in a standard suite, a scripting component can get the rest of the information about the suite—its event and object class definitions, comparison operators, and enumerated groups—from the 'aeut' resource. The corresponding arrays in the 'aete' resource can therefore be left empty.Note that the Rez input for resources does not include the align word fields shown in the 'aeut' resource type declaration in Listing 8-1. Rez takes care of word alignment automatically.Listing 8-2    Rez input for an 'aete' resource for an application that supports the Required and Core suites in their entiretyresource 'aete' (0, "JustTwoSuites") {    1,                                                     /*major version in BCD*/    0,                                                     /*minor version in BCD*/    english,                                                     /*language code*/    roman,                                                    /*script code*/    {    /*array Suites: 2 elements*/        /*[1]*/        "",                                             /*human-language name for suite; */                                                    /* 'aeut' supplies "Required Suite"*/                   "Events that every application should support",                                                                 /*suite description*/        kAERequiredSuite,                                                 /*suite code*/        1,                                                 /*suite level*/        1,                                                 /*suite version*/        {    /*array Events: 0 elements*/        },        {    /*array Classes: 0 elements*/        },        {    /*array ComparisonOps: 0 elements*/        },        {    /*array Enumerations: 0 elements*/        },        /*[2]*/        "",                                                 /*human-language name for suite; */                                                        /* 'aeut' supplies "Core Suite"*/                                        "Suite that applies to all applications",                                                         /*suite description*/        kAECoreSuite,                                                 /*suite code*/        1,                                                /*suite level*/        1,                                                /*suite version*/        {    /*array Events: 0 element*/        },        {    /*array Classes: 0 elements*/        },        {    /*array ComparisonOps: 0 elements*/        },        {    /*array Enumerations: 0 elements*/        }    }}; Extending the Standard SuitesIf, like the 'aete' resource shown in Listing 8-2, your application’s 'aete' resource indicates that you support an entire standard suite, the scripting component automatically makes use of all the terminology for that suite provided by its 'aeut' resource. For this reason, you can easily extend the definitions for a suite that your application supports in its entirety: just provide arrays in the 'aete' resource for the definitions not already included in the 'aeut' resource. For example, if you’re extending the definition of an event to support a single additional parameter, you should provide an array of parameters that includes one item: the description of the new parameter. Similarly, if you’re not extending the contents of a particular array, you don’t need to include the array in the 'aete' resource. Although an array of descriptions in an 'aete' resource need not include descriptions that are already provided by the 'aeut' resource, you must include information that defines the position of the array in relation to the other information in the 'aete' resource. As Table 8-3 on page 8-8 shows, you can nest the arrays in an 'aete' resource within other arrays: for example, an array of parameters is part of the description of an event, and the event description is, in turn, part of the array of event descriptions for a suite.To add a description of a single new parameter to the definition of an Apple event in a suite that your application supports in its entirety, you need to providen    an array of parameters containing one element: the description of the new parametern    information that identifies the event definition to which you’re adding the parametern    information that identifies the suite containing the eventListing 8-3 illustrates how this works. This Rez input adds two new parameters (“number of copies” and “print quality”) to the Print Documents event in the Required suite, one enumeration (three values for the “print quality” parameter of the Print Documents event) to the Required suite, and a new property (“first indent”) to the cParagraph class in the Text suite. It also adds a plural synonym for the cParagraph class: the word “paragraphs.” Listing 8-3    Rez input for an 'aete' resource that extends the definitions of the Required, Core, and Text suites#define keyMyNumberOfCopies                                         'numc'#define keyMyPrintQuality                                         'prtq'#define typePrintQuality                                        'pqen'#define kFast                                         'fast'#define kNormal                                         'nrml'#define kHighQuality                                          'hiql'#define pFirstIndent                                        'indt'resource 'aete' (0, "SuiteExtensions") {    1,                                                     /*major version in BCD*/    0,                                                     /*minor version in BCD*/    english,                                                     /*language code*/    roman,                                                    /*script code*/    {    /*array Suites: 3 elements*/        /*[1]*/        "",                                             /*human-language name for suite; */                                                    /* 'aeut' supplies "Required Suite"*/                        "Events that every application should support",                                                                 /*suite description*/        kAERequiredSuite,                                                 /*suite code*/        1,                                                 /*suite level*/        1,                                                 /*suite version*/        {    /*array Events: 1 element*/            /*[1]*/            "",                                         /*human-language name for event; */                                                    /* 'aeut' supplies "Print Documents"*/                            "Print the specified list of documents",                                                             /*event description*/            kCoreEventClass,                                            /*event class*/            kAEPrintDocuments,                                            /*event ID*/            noReply,                                            /*reply type*/            "",                                            /*reply description*/            replyOptional,                                            /*reply is optional*/            singleItem,                                            /*reply must be single item*/            notEnumerated,                                             /*type is not enumerated*/            reserved,                                            /*these 13 bits are reserved*/            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            typeAlias,                                            /*direct parameter type*/            "List of documents to print",                                            /*direct parameter description*/            directParamRequired,                                            /*direct parameter is required*/            listOfItems,                                            /*direct parameter must be list*/            notEnumerated,                                            /*type is not enumerated*/            doesntChangeState,                                            /*event does not change */                                                        /* server's state*/            reserved,                                            /*these 12 bits are reserved*/            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            reserved,            {    /*array OtherParams: these fields describe the additional */                /* parameters Number of Copies and Print Quality to the */                /* standard Print Documents event*/                /*[1]*/                "number of copies",                                    /*human-language name for parameter*/                keyMyNumberOfCopies,                                        /*parameter keyword*/                typeShortInteger,                                        /*parameter type*/                "Number of copies to print",                                        /*parameter description*/                optional,                                        /*parameter is optional*/                singleItem,                                        /*parameter must be single item*/                notEnumerated,                                        /*type is not enumerated*/                reserved,                                        /*these 13 bits are reserved*/                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                /*[2]*/                "print quality",                                    /*human-language name for parameter*/                keyMyPrintQuality,                                        /*parameter keyword*/                typePrintQuality,                                        /*parameter type*/                "The quality of the printing",/*parameter description*/                optional,                                        /*parameter is optional*/                singleItem,                                        /*parameter must be single item*/                enumerated,                                        /*type is enumerated*/                reserved,                                        /*these 13 bits are reserved*/                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved            }        },        {    /*array Classes: 0 elements*/        },        {    /*array ComparisonOps: 0 elements*/        },        {    /*array Enumerations: 1 element*/            /*these fields add the 'pqen' enumeration to the Required suite*/            /*[1]*/            typePrintQuality,                                            /*enumeration ID*/            {    /*array Enumerators: 3 elements*/                /*[1]*/                "Fast",                                        /*enumerator name*/                kFast,                                        /*enumerator ID*/                "Print as quickly as possible",/*enumerator description    */                /*[2]*/                "Normal",                                        /*enumerator name*/                kNormal,                                        /*enumerator ID*/                "Print at normal speed",                                         /*enumerator description    */                /*[3]*/                "High-Quality",                                        /*enumerator name*/                kHighQuality,                                        /*enumerator ID*/                "Print at highest quality possible"                                         /*enumerator description    */            }        },        /*[2]*/        "",                                                 /*human-language name for suite; */                                                        /* 'aeut' supplies "Core Suite"*/                        "Suite that applies to all applications",                                                                 /*suite description*/        kAECoreSuite,                                                /*suite code*/        1,                                                 /*suite level*/        1,                                                 /*suite version*/        {    /*array Events: 0 elements*/        },        {    /*array Classes: 0 elements*/        },        {    /*array ComparisonOps: 0 elements*/        },        {    /*array Enumerations: 0 elements*/        },        /*[3]*/        "",                                                 /*human-language name for suite; */                                                        /* 'aeut' supplies "Text Suite"*/                        "A set of basic classes for text processing",                                                                /*suite description*/        kAETextSuite,                                                /*suite code*/        1,                                                 /*suite level*/        1,                                                 /*suite version*/        {    /*array Events: 0 elements*/        },        {    /*array Classes: 1 element*/            /*[1]*/            "paragraph",                                             /*human-language name for class*/            cParagraph,                                            /*class ID*/            "A paragraph",                                            /*class description*/            {    /*array Properties: 1 element*/                /*[1]*/                "first indent",                                    /*human-language name for property*/                pFirstIndent,                                        /*property ID*/                cLongInteger,                                        /*property class*/                "First indent of paragraph in points",/*property description*/                reserved,                                        /*reserved*/                singleItem,                                        /*property is single item*/                notEnumerated,                                        /*type is not enumerated*/                readWrite,                                        /*property can be modified*/                reserved,                                        /*these 12 bits are reserved*/                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved            },            {    /*array Elements: 0 elements*/            },            "paragraphs",                                        /*human-language name for class*/            cParagraph            ,                            /*class ID*/            "Every paragraph",                                        /*class description*/            {    /*array Special Properties: 1 element*/                /*[1]*/                "",                                    /*human-language name for property*/                kAESpecialClassProperties,                                        /*property ID*/                cType,                                        /*property class*/                "",                                         /*property description*/                reserved,                                        /*reserved*/                singleItem,                                        /*property is single item*/                notEnumerated,                                        /*type is not enumerated*/                readOnly,                                        /*property cannot be modified*/                reserved,                                        /*these 11 bits are reserved*/                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                reserved,                plural                                        /*human-language name is */                                                        /* plural form*/            },            {    /*array Elements: 0 elements*/            },        },        {    /*array ComparisonOps: 0 elements*/        },        {    /*array Enumerations: 0 elements*/         }    }};In Listing 8-3, the possible values for the “print quality” parameter belong to an enumeration. This is indicated by the term enumerated in the parameter description. For this reason, the parameter type field contains the ID for the enumeration—typePrintQuality.Listing 8-3 also adds a plural synonym for “paragraph” to the array of classes: the word “paragraphs.” Note that this is listed as if it were an additional class, except that it also specifies cParagraph as the class ID. The first property listed for the synonym has property ID kAESpecialClassProperties. This property describes characteristics of the class as a whole; the last flag bit for this property is set to plural, indicating that the term paragraphs is a plural term for the specified class. This property must always be the first property listed for a class. For more information about the kAESpecialClassProperties property, see “Property Data,” which begins on page 8-38.An enumeration is described only by its ID; its declaration does not include a name or description field. However, a name, value, and description must be provided for each of the enumerators in an enumeration.You can use the method illustrated in Listing 8-3 only to add to the definitions of Apple events and Apple event object classes, not to support subsets of them. For example, to support only a subset of the parameters of an Apple event or only some of the elements or properties of an existing object class, you must list all the definitions from that suite that you do support. The next section, “Supporting Subsets of Suites,” provides more information about how to do this.Human-language names for Apple events, object classes, and so on (including extensions) can include both uppercase and lowercase letters and spaces. For comparison purposes, case doesn’t matter. However, note that the human-language names defined in Listing 8-3 are all lowercase. This convention ensures that scripts in which these terms appear won’t have capital letters in unexpected places.Scripting components that get identifiers or strings from user terminology resources are free to change the identifiers or strings as necessary (eliminating spaces, converting identifiers to all uppercase or lowercase, or changing the identifiers altogether) to meet the requirements of a particular task. Supporting Subsets of SuitesYour application is not required to support all the definitions in a suite. If you wish to support a subset of the definitions in one or more standard suites, you can collect individual definitions from any number of suites in a placeholder suite whose suite ID is the application’s signature or typeWildCard ('****'). When you support a subset of a suite, you must provide all the definitions you want to support in your 'aete' resource. Supporting New SuitesIf your application defines its own custom Apple events or other Apple event constructs, you should include a separate suite section for the suite in the 'aete' resource. You should use your application’s signature for both the suite ID and the class ID of all events in the suite.    Handling the Get AETE EventA scripting component sends the Get AETE event to an application when it needs information about the user terminology specified by the application. For example, the AppleScript component sends the Get AETE event when it first attempts to compile a tell statement that specifies a particular application. If your application does not handle the Get AETE event, the scripting component reads the terminology information it needs directly from your application’s 'aete' resource. Applications that support additional plug-in modules, each with its own 'aete' resource, must provide an 'scsz' resource and a handler for the Get AETE event that collects the 'aete' resources from the modules that are currently running.If your application does provide separate plug-in modules, the Get AETE event allows it to gather information from the 'aete' resources for the modules that are currently running and return the terminology information along with your application’s built-in terminology information to the scripting component in the reply event.Here is a summary of the structure of a Get AETE event:Get AETE—Get an application’s 'aete' resource            Event class        kASAppleScriptClass    Event ID        kGetAETE    Required parameter                Keyword:    keyDirectObject        Descriptor type:    typeInteger        Data:    Language code    Required reply parameter                Keyword:    keyDirectObject        Descriptor type:    typeAEList or typeAETE        Data:    The application’s terminologies    Description        Sent by a scripting component to an application when the scripting component needs information about the application’s user terminology     Your application can’t handle the Get AETE event unless it is running. If your application doesn’t provide a handler for the Get AETE event, the scripting component can obtain terminology information directly from your application’s 'aete' resource even if your application is not running.If your application handles the Get AETE event, it must also provide a scripting size resource. A scripting size resource is a resource of type 'scsz' that provides information about an application’s capabilities for use by scripting components. It allows your application to declare whether it needs the Get AETE event and to specify preferences for the sizes of the portion of your application’s heap used by a scripting component. For information about the 'scsz' resource, see “The Scripting Size Resource” on page 8-45. A handler for the Get AETE event should perform the following tasks:n    Obtain the language code specified by the event.n    Create a descriptor list to hold the 'aete' resources.n    Collect the 'aete' resources from all the application’s plug-in modules that are currently running, including the application itself, and add them to the list. n    Add the list to the reply Apple event.Listing 8-4 provides an example of a handler for the Get AETE event. Listing 8-4    A handler for the Get AETE event FUNCTION MyGetAETE (theAE: AppleEvent; theReply: AppleEvent;                             refCon: LongInt): OSErr;VAR    theList:                     AEDescList;    returnedType:                    DescType;    actualSize:                    Size;    languageCode:                    Integer;    myErr:                    OSErr;BEGIN    MyGetAETE := errAEEventNotHandled;    languageCode := 0;    {if a reply was not requested, then don't handle}    IF theReply.dataHandle = NIL THEN        Exit(MyGetAETE);    {get the language code that AppleScript is requesting so that         }    { this function can return the aete of a specified language}    myErr := AEGetParamPtr(theAE, keyDirectObject,                                     typeLongInteger, returnedType,                                     @languageCode, sizeOf(LongInt),                                     actualSize);    IF myErr <> noErr THEN        Exit(MyGetAETE);    {create a list}    myErr := AECreateList(NIL, 0, FALSE, theList);    IF myErr <> noErr THEN        Exit(MyGetAETE);    {get the requested 'aete' resources and put in the list--the }    { MyGrabAETE application-defined function does this}    {your code should iterate all of your installed code }    { extensions and add the aete for each that matches the }    { language code requested}    myErr := MyGrabAETE(languageCode, theList);    IF myErr <> noErr THEN    BEGIN        myErr := AEDisposeDesc(theList);        Exit(MyGetAETE);    END;    {add list to reply Apple event}    myErr := AEPutParamDesc(theReply, keyDirectObject, theList);    myErr := AEDisposeDesc(theList);    myGetAETE := myErr;END;The MyGetAETE handler in Listing 8-4 begins by setting the function result to errAEEventNotHandled. The function is set to this result if for any reason the handler doesn’t successfully handle the event, so that a system handler provided by the scripting component can at least read the terminology information directly from the application’s own 'aete' resource. The handler in Listing 8-4 then checks the language code specified by the event. After checking to make sure the reply exists, the handler creates a list and uses the application-defined function MyGrabAETE to collect all the appropriate terminology information and append it to the list. The MyGetAETE handler then adds the list to the reply event.  Reference to Apple Event Terminology ResourcesListing 8-1 on page 8-9 shows the complete resource type declaration in Rez format for the 'aeut' resource. The same resource structure is used by both the 'aeut' and 'aete' resources. Figure 8-1 shows the format of a compiled 'aeut' or 'aete' resource. Figure 8-1    Structure of an 'aeut' or 'aete' resourceAn 'aeut' or 'aete' resource contains the following:n    a header containing the version and language code of the template and a count of the number of suites the resource describesn    a variable number of suite descriptionsThe sections that follow describe the content of the header and each suite description in detail.Header Data for an Apple Event Terminology ResourceThe header for an 'aeut' or 'aete' resource specifies the version of its contents, the language of the human-language equivalents contained in the resource, a script code, and a count of the number of suites the resource describes. Figure 8-2 shows the header format. Figure 8-2    Structure of the header data in an 'aeut' or 'aete' resourceThe header contains the following items:n    The major version number of the content of the resource in binary-coded decimal (the major version number for the first release of the 'aeut' resource is 1). The major and minor versions describe the content of the resource, not its template. You can use these fields to provide version numbers for the content of your application’s 'aete' resource.n    The minor version number of the template in binary-coded decimal (the minor version number for the first release of the 'aeut' resource is 0).n    The language code for the resource. Inside Macintosh: Text provides a list of language codes. This code must be the same as the resource ID for the resource. n    The script code for the resource, taken from the list of script codes provided in Inside Macintosh: Text. n    A count of the number of suites described by the resource.Suite Data for an Apple Event Terminology ResourceEach item in the array of suites for an 'aeut' or 'aete' resource includes information about the suite ID, level, and version and four arrays that specify the events, object classes, comparison operators, and enumerations for that suite. Figure 8-3 shows the format of this suite data.Figure 8-3    Structure of suite data in an 'aeut' or 'aete' resourceThe data for each suite consists of the following items:n    The human-language name of the suite. This is a Pascal string that can include any characters, including uppercase and lowercase letters and spaces. If the 'aete' resource specifies the name as an empty string, the scripting component looks up, in its 'aeut' resource, the suite name and other suite data that correspond to the specified suite ID, suite level, and suite version. This strategy simplifies specification of an entire suite and facilitates localization, since the human-language name is provided by the 'aeut' resource. If the 'aete' resource specifies a name other than the name provided by the 'aeut' resource for the same suite ID, suite level, and suite version, the scripting component uses the new name with the same suite data from the 'aeut' resource. Unless you are defining a custom suite, you should specify an empty string for the name of a suite.n    A human-language description of the suite. This is a Pascal string that can include any characters. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.n    A four-character ID that distinguishes the suite from all other suites defined in either the 'aeut' or 'aete' resources. This value is normally the same as the event class for the Apple events in the suite. If the 'aete' resource specifies a standard suite name but a suite ID that is different from the suite ID for the standard suite of that name described in the 'aeut' resource, the scripting component uses the new suite ID with the standard suite data for the specified name. In general, you should use the standard suite ID for any standard suite that you support. If your application uses a custom suite, you should use your application’s signature as the event class for the events in the suite and, in addition, as its suite ID. When you register your application’s signature with Developer Technical Support, the corresponding event class is automatically registered for your application, and only you can register events that belong to that event class. For information about registering Apple events, contact the Apple Event Registrar.n    The level and version of the suite. For the first version of any suite, the level is usually 1 (indicating that it is the suite that contains the most basic definitions) and the version is 1 (the version of this suite level). More advanced suites (such as a suite for performing more sophisticated text manipulation than the current Text suite allows) will have level numbers greater than 1. All currently defined suites have a level of 1 and a version of 1. n    A count of the events defined for this suite and an array of event definitions.n    A count of the object classes defined for this suite and an array of class definitions.n    A count of the comparison operators defined for this suite and an array of comparison operator definitions.n    A count of the enumerations defined for this suite and an array of enumeration definitions. Event DataEach item in the array of events for a suite specified in an 'aeut' or 'aete' resource includes information about the event, the reply, and the direct parameter, and an array that specifies the additional parameters for the event. Figure 8-4 shows the format of this event data.Figure 8-4    Structure of event data in an 'aeut' or 'aete' resourceThe data for each event consists of the following items:n    The human-language name of the event. This is a Pascal string that can include any characters, including uppercase and lowercase letters and spaces. If the 'aete' resource specifies the name as an empty string, the scripting component looks up, in its 'aeut' resource, the event name and other event data that correspond to the specified event class and event ID. This strategy facilitates localization, since the human-language name is provided by the 'aeut' resource. In this case the scripting component will use the standard data from the 'aeut' resource for the event plus the data provided by the 'aete' resource for any additional parameters.If the 'aete' resource specifies a name other than the name provided by the 'aeut' resource for the same event class and event ID, the scripting component uses the new name with the same suite data from the 'aeut' resource. You should specify an empty string for the name of any standard event that your application lists explicitly in its 'aete' resource.n    A human-language description of the event. This is a Pascal string that can include any characters. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.n    The four-character event class for the event. If the 'aete' resource specifies a standard event name and an event class other than the event class for the equivalent standard event, the scripting component uses the new event class with the standard event data for the specified name. You should specify the standard event class for any standard event that your application lists explicitly in its 'aete' resource. n    The four-character event ID for the event. If the 'aete' resource specifies a standard event name and an event ID other than the event ID for the equivalent standard event, the scripting component uses the new event ID with the standard event data for the specified name. You should specify the standard event ID for any standard event that your application lists explicitly in its 'aete' resource.n    A four-character descriptor type for the direct parameter of the reply. If the event never needs a reply, or if the reply does not include a direct parameter, this value must be typeNull. Otherwise, the meaning of this field varies according to the values of two of the flags that follow. One flag specifies whether the parameter is a list (singleItem or listOfItems), and the other specifies whether the values for the parameter are enumerated (enumerated or notEnumerated):n    If the parameter is not a list and its values are not enumerated, this value is the descriptor type for the direct parameter.n    If the parameter is a list and its values are not enumerated, this value is the descriptor type for each of the items in the list. (If not all the items in the list are of the same descriptor type, the flag specifying whether the value is a list must have the value singleItem, and the value of this field must be typeAEList.)n    If the parameter is not a list and its values are enumerated, this value is the four-character code for the enumeration defined in either the 'aete' or 'aeut' resource that contains the allowable values for the parameter. (If the values are enumerated but the enumeration is not defined in either the 'aete' or 'aeut' resource, the flag specifying whether the parameter’s values are enumerated must have the value notEnumerated, and the value of this field must be typeEnumerated.)n    If the parameter is a list and its values are enumerated, this value is the four-character code for the enumeration defined in the same resource that contains the allowable values for all of the items in the list. All items in the list must have one of these enumerated values.n    A human-language description of the direct parameter of the reply. This is a Pascal string that can include any characters. Although the reply may include other parameters, only the direct parameter of the reply is described here. When the resource description is compiled, the resource compiler aligns the string on a word boundary.n    Flags that specify the following as Boolean values:n    Whether the direct parameter of the reply is required (replyRequired) or optional (replyOptional).n    Whether the direct parameter of the reply is a single item (singleItem) or a list of items (listOfItems). (See the earlier description of the reply event’s four-character descriptor type for information about how this value changes the meaning of the reply type.)n    Whether named constants, called enumerators, are specified as the only valid values for the direct parameter of the reply (enumerated or notEnumerated). (See the earlier description of the four-character descriptor type for the reply event’s direct parameter for information about how this value changes the meaning of the direct parameter type.) For information about specifying enumerators, see “Enumeration and Enumerator Data” on page 8-43.n    Following 5 bits are reserved for future use. The values of these bits must be set to reserved.n    Following 7 bits are reserved for future use as dialect-specific flags. The values of these bits must be set to reserved.n    Whether the event is a nonverb event (nonVerbEvent). This bit is used by dialects such as the AppleScript Japanese dialect that make this distinction. For all other dialects, set the value of this bit to reserved.n    A four-character descriptor type for the direct parameter of the event. If the event never has a direct parameter, this value must be typeNull. Otherwise, the meaning of this field varies according to the values of two of the flags that follow. One flag specifies whether the parameter is a list (singleItem or listOfItems), and the other specifies whether the values for the parameter are enumerated (enumerated or notEnumerated):n    If the parameter is not a list and its values are not enumerated, this value is the descriptor type for the direct parameter.n    If the parameter is a list and its values are not enumerated, this value is the descriptor type for each of the items in the list. (If not all the items in the list are of the same descriptor type, the flag specifying whether the value is a list must have the value singleItem, and the value of this field must be typeAEList.)n    If the parameter is not a list and its values are enumerated, this value is the four-character code for the enumeration defined in either the 'aete' or 'aeut' resource that contains the allowable values for the parameter. (If the values are enumerated but the enumeration is not defined in either the 'aete' or 'aeut' resource, the flag specifying whether the parameter’s values are enumerated must have the value notEnumerated, and the value of this field must be typeEnumerated.)n    If the parameter is a list and its values are enumerated, this value is the four-character code for the enumeration defined in the same resource that contains the allowable values for all of the items in the list. The values of the items in the list must all be one of these enumerated values.n    A human-language description of the direct parameter. This is a Pascal string that can include any characters. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.n    Flags that specify the following as Boolean values:n    Whether the direct parameter of the event is required (directParamRequired) or optional (directParamOptional).n    Whether the direct parameter of the event is a single item (singleItem) or a list of items (listOfItems). (See the earlier description of the direct parameter’s four-character descriptor type for information about how this value changes the meaning of the direct parameter type.)n    Whether named constants, called enumerators, are specified as the only valid values for the direct parameter (enumerated or notEnumerated). (See the earlier description of the direct parameter’s four-character descriptor type for information about how this value changes the meaning of the direct parameter type.) For information about specifying enumerators, see “Enumeration and Enumerator Data” on page 8-43.n    Whether receiving this event changes (changesState) or doesn’t change (doesntChangeState) the internal state of the receiving application. Events that only get information do not change the state of the application, whereas events such as Cut and Move do.n    Following 4 bits are reserved for future use. The values of these bits must be set to reserved.n    Following 8 bits are reserved for future use as dialect-specific flags. The values of these bits must be set to reserved.n    A count of the additional parameters described for this event and an array of additional parameter definitions.Additional Parameter DataEach item in the array of additional parameters for an event specified in an 'aeut' resource includes information about a single additional parameter. Figure 8-5 shows the format of additional parameter data in an 'aeut' or 'aete' resource. Figure 8-5    Structure of additional parameter data in an 'aeut' or 'aete' resourceThe data for each additional parameter consists of the following items:n    The human-language name of the parameter. This is a Pascal string that can include any characters, including uppercase and lowercase letters and spaces. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.If the 'aete' resource specifies the name of an additional parameter as an empty string, the scripting component looks up, in its 'aeut' resource, the parameter name and other parameter data that correspond to the specified parameter keyword. If the 'aete' resource specifies a name other than the name provided by the 'aeut' resource for the same parameter keyword, the scripting component uses the new name with the same parameter data from the 'aeut' resource. You should specify an empty string for the name of any standard additional parameter that you list explicitly in an 'aete' resource.n    The four-character keyword for the parameter. If the 'aete' resource specifies a standard parameter name and a parameter keyword other than the keyword for the equivalent standard parameter, the scripting component uses the new parameter keyword with the standard parameter data for the specified name. You should specify the standard parameter keyword for any standard additional parameter that you list explicitly in an 'aete' resource.n    A four-character descriptor type for the parameter. The meaning of this field varies according to the values of two of the flags that follow. One flag specifies whether the parameter is a list (singleItem or listOfItems), and the other specifies whether the values for the parameter are enumerated (enumerated or notEnumerated):n    If the parameter is not a list and its values are not enumerated, this value is the descriptor type for the direct parameter.n    If the parameter is a list and its values are not enumerated, this value is the descriptor type for each of the items in the list. (If not all the items in the list are of the same descriptor type, the flag specifying whether the value is a list must have the value singleItem, and the value of this field must be typeAEList.)n    If the parameter is not a list and its values are enumerated, this value is the four-character code for the enumeration defined in either the 'aete' or 'aeut' resource that contains the allowable values for the parameter. (If the values are enumerated but the enumeration is not defined in either the 'aete' or 'aeut' resource, the flag specifying whether the parameter’s values are enumerated must have the value notEnumerated, and the value of this field must be typeEnumerated.)n    If the parameter is a list and its values are enumerated, this value is the four-character code for the enumeration defined in the same resource that contains the allowable values for all of the items in the list. The values of the items in the list must all be one of these enumerated values.n    A human-language description of the parameter. This is a Pascal string that can include any characters. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.n    Flags that specify the following as Boolean values:n    Whether the parameter is required (required) or optional (optional).n    Whether the parameter is a single item (singleItem) or a list of items (listOfItems). (See the earlier description of the additional parameter’s four-character descriptor type for information about how this value changes the meaning of the parameter type.)n    Whether named constants, called enumerators, are specified as the only valid values for the parameter (enumerated or notEnumerated). (See the earlier description of the parameter’s four-character descriptor type for information about how this value changes the meaning of the parameter type.) For information about specifying enumerators, see “Enumeration and Enumerator Data” on page 8-43.n    Whether the parameter is the event’s only unnamed parameter (isUnNamed) or is named (isNamed). This bit is used by dialects such as AppleScript Japanese that make this distinction. For all other dialects, set the value of this bit to reserved.n    Following 4 bits are reserved for future use. The values of these bits must be set to reserved.n    Following 8 bits are reserved for future use as dialect-specific flags. The values of these bits must be set to reserved.“Extending the Standard Suites,” which begins on page 8-16, includes sample Rez input for an 'aete' resource that adds new parameters to a standard Apple event.Object Class DataEach item in the array of object classes for a suite includes information about the class and arrays that specify the properties and elements for that class. Figure 8-6 shows the format of the object class data in an 'aeut' or 'aete' resource. Figure 8-6    Structure of object class data in an 'aeut' or 'aete' resource The data for each object class consists of the following items:n    The human-language name of the object class. This is a Pascal string that can include any characters, including uppercase and lowercase letters and spaces. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.If the 'aete' resource specifies the name of an object class as an empty string, the scripting component looks up, in its 'aeut' resource, the class name and other object class data that correspond to the specified class ID. If the 'aete' resource specifies a name other than the name provided by the 'aeut' resource for the same class ID, the scripting component uses the new name with the same object class data from the 'aeut' resource. You should specify an empty string for the name of any standard object class that you list explicitly in an 'aete' resource.n    The four-character class ID for the object class. If the 'aete' resource specifies a standard object class name and a class ID other than the class ID for the equivalent standard object class, the scripting component uses the new class ID with the standard object class data for the specified name. You should specify the standard class ID for any standard object class that you list explicitly in an 'aete' resource.n    A human-language description of the class. This is a Pascal string that can include any characters. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.n    A count of the properties described for this class and an array of property definitions.n    A count of the element classes described for this class and an array of element class definitions.To define characteristics of an object class (for instance, whether an object of that class is a single item or a list of items, whether it is singular or plural, and so on), your application’s 'aete' resource must define a special property of property ID kAESpecialClassProperties as the first property in the array of properties. Because object class data does not include flag bits, the flag bits of this property are used to specify attributes for the class to which the property belongs. The next section describes how this property is defined and used. Property DataEach item in the array of properties for an object class includes information about a single property. Figure 8-7 shows the format of the property data in an 'aeut' or 'aete' resource. Figure 8-7    Structure of property data in an 'aeut' or 'aete' resourceThe data for each property consists of the following items:n    The human-language name of the property. This is a Pascal string that can include any characters, including uppercase and lowercase letters and spaces. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.If the 'aete' resource specifies the name of a property as an empty string, the scripting component looks up, in its 'aeut' resource, the property name and other property data that correspond to the specified property ID. If the 'aete' resource specifies a name other than the name provided by the 'aeut' resource for the same property ID, the scripting component uses the new name with the same property data from the 'aeut' resource. You should specify an empty string for the name of any standard property that you list explicitly in an 'aete' resource.n    The four-character property ID for the property. If the 'aete' resource specifies a standard property name and a property ID other than the property ID for the equivalent standard property, the scripting component uses the new property ID with the standard property data for the specified name. You should specify the standard property ID for any standard property that you list explicitly in an 'aete' resource.n    A four-character class ID for the object class to which the property belongs. The meaning of this field varies according to the values of two of the flags that follow. One flag specifies whether the property is a list (singleItem or listOfItems), and the other specifies whether the values for the parameter are enumerated (enumerated or notEnumerated):n    If the property is not a list and its values are not enumerated, this value is the class ID for the property.n    If the property is a list and its values are not enumerated, this value is the class ID for each of the items in the list. (If not all the items in the list are of the same descriptor type, the flag specifying whether the value is a list must have the value singleItem, and the value of this field must be cAEList.)n    If the property is not a list and its values are enumerated, this value is the four-character code for the enumeration defined in either the 'aete' or 'aeut' resource that contains the allowable values for the property. (If the values are enumerated but the enumeration is not defined in either the 'aete' or 'aeut' resource, the flag specifying whether the property’s values are enumerated must have the value notEnumerated, and the value of this field must be typeEnumerated.)n    If the parameter is a list and its values are enumerated, this value is the four-character code for the enumeration defined in the same resource that contains the allowable values for all of the items in the list. The values of the items in the list must all be one of these enumerated values.n    A human-language description of the property. This is a Pascal string that can include any characters. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.n    Flags that specify the following as Boolean values:n    The first bit is reserved for future use. Its value must be set to reserved.n    Whether the property is a single item (singleItem) or a list of items (listOfItems). (See the earlier description of the property’s four-character class ID for information about how this value changes the meaning of the class ID.)n    Whether named constants, called enumerators, are specified as the only valid values for the property (enumerated or notEnumerated). (See the earlier description of the property’s four-character class ID for information about how this value changes the meaning of the class ID.) For information about specifying enumerators, see “Enumeration and Enumerator Data” on page 8-43.n    Whether the property’s value can (readWrite) or cannot (readOnly) be set by the Set Data Apple event.n    Following 4 bits are reserved for future use.n    Following 5 bits are reserved for future use as dialect-specific flags.n    Whether the human-language name of the property is feminine (feminine) or not (notFeminine). This bit is used by dialects such as the AppleScript French dialect that make this distinction. For all other dialects, set the value of this bit to reserved.n    Whether the human-language name of the property is masculine (masculine) or not (notMasculine). This bit is used by dialects such as AppleScript French that make this distinction. For all other dialects, set the value of this bit to reserved.n    Whether the human-language name of the property is singular (singular) or plural (plural). This bit is used by dialects such as AppleScript French that make this distinction. If you set this bit to reserved, the scripting component will assign it the value singular.“Extending the Standard Suites,” which begins on page 8-16, includes sample Rez input for an 'aete' resource that adds a new property to a standard object class.The array of properties in an 'aeut' resource begins with a definition of a special property that describes characteristics of the class as a whole using the flags in the definition of that property. A property used in this way to define characteristics of a class must be defined first in the array of properties for that class and must specify kAESpecialClassProperties ('c@#!') as the property ID, cType as the property class, and an empty string for the property name and property description. If you don’t define such a property for a class in your application’s 'aete' resource, the scripting component will assign that class the default values specified by the first constant for each flag bit in the Rez declaration for the 'aeut' resource. (See Listing 8-1, which begins on page 8-9, for the 'aeut' resource type declaration.) Element Class DataEach item in the array of elements for an object class includes information about a single element class and an array of key forms for that element class. Figure 8-8 shows the format of the object class data in an 'aeut' or 'aete' resource. Figure 8-8    Structure of element class data in an 'aeut' or 'aete' resourceThe following statements are included for each element class in the array of element classes for an object class:n    The four-character class ID for the element’s object class.n    A count of key forms that apply to elements of this class within objects of the class for which these element classes are defined, followed by an array of key forms. Each item in the array must be a value from a special 'kfrm' enumeration. (The 'aeut' resource includes enumerators for the standard key forms defined in the Apple Event Registry: Standard Suites; an 'aete' resource can contain 'kfrm' enumerators for additional key forms that are specific to an application. For information about defining enumerators and enumerations, see “Enumeration and Enumerator Data” on page 8-43.) The enumerators for a 'kfrm' enumeration can include 'indx' (for the key form formAbsolutePosition), 'name' (for the key form formName), 'ID  ' (for the key form formUniqueID), 'prop' (for the key form formPropertyID), 'rang' (for the key form formRange), 'rele' (for the key form formRelativePosition), and 'test' (for the key form formTest).No names or descriptions are provided for element classes, because elements are specified by their object classes, and the declaration of each object class includes the name and description of the class. Comparison Operator DataEach item in the array of comparison operators for a suite includes information about a single comparison operator. Figure 8-9 shows the format of the comparison operator data in an 'aeut' or 'aete' resource. NoteThe AppleScript component currently doesn’t use information about comparison operators. Other scripting components may use this information.uFigure 8-9    Structure of comparison operator data in an 'aeut' or 'aete' resource The data for each comparison operator consists of the following items:n    The human-language name of the comparison operator. This is a Pascal string that can include any characters, including uppercase and lowercase letters and spaces. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.If the 'aete' resource specifies the name of a comparison operator as an empty string, the scripting component looks up, in its 'aeut' resource, the comparison operator name and other comparison operator data that correspond to the specified comparison operator ID. If the 'aete' resource specifies a name other than the name provided by the 'aeut' resource for the same comparison operator ID, the scripting component uses the new name with the same comparison operator data from the 'aeut' resource. You should specify an empty string for the name of any standard comparison operator that you list explicitly in an 'aete' resource.n    The four-character comparison operator ID for the property. If the 'aete' resource specifies a standard comparison operator name and a comparison operator ID other than the comparison operator ID for the equivalent standard comparison operator, the scripting component uses the new comparison operator ID with the standard comparison operator data for the specified name. You should specify the standard comparison operator ID for any standard comparison operator that you list explicitly in an 'aete' resource.n    A human-language description of the comparison operator. This is a Pascal string that can include any characters. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.“Extending the Standard Suites,” which begins on page 8-16, includes sample Rez input for an 'aete' resource that adds a comparison operator to a standard suite. Enumeration and Enumerator Data Each item in the array of enumerations for a suite includes information about a single enumeration and an array of enumerators for that enumeration.Figure 8-10 shows the format of the enumeration data in an 'aeut' or 'aete' resource. Figure 8-10    Structure of enumeration data in an 'aeut' or 'aete' resourceThe data for each enumeration consists of the following items:n    a four-character enumeration IDn    a count of constants, known as enumerators, that specify the allowable values for the enumeration, and an array of enumeratorsFigure 8-11 shows the format of the enumerator data.Figure 8-11    Structure of enumerator data in an 'aeut' or 'aete' resourceThe data for each enumerator consists of the following items:n    The human-language name of the enumerator. This is a Pascal string that can include any characters, including uppercase and lowercase letters and spaces. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.If the 'aete' resource specifies the name of an enumerator as an empty string, the scripting component looks up, in its 'aeut' resource, the enumerator name and other enumerator data that correspond to the specified enumerator ID. If the 'aete' resource specifies a name other than the name provided by the 'aeut' resource for the same enumerator ID, the scripting component uses the new name with the same enumerator data from the 'aeut' resource. You should specify an empty string for the name of any standard enumerator that you list explicitly in an 'aete' resource.n    The four-character enumerator ID for the enumerator. If the 'aete' resource specifies a standard enumerator name and an enumerator ID other than the enumerator ID for the equivalent standard enumerator, the scripting component uses the new enumerator ID with the standard enumerator data for the specified name. You should specify the standard enumerator ID for any standard enumerator that you list explicitly in an 'aete' resource.n    A human-language description of the enumerator. This is a Pascal string that can include any characters. When the resource description is compiled, the resource compiler pads the string and aligns the next field on a word boundary.“Extending the Standard Suites,” which begins on page 8-16, includes sample Rez input for an 'aete' resource that specifies an enumeration and an array of enumerators.  The Scripting Size ResourceIf your application handles the Get AETE event, you must provide a scripting size resource. A scripting size resource is a resource of type 'scsz' that provides information about an application’s capabilities for use by scripting components. It also allows your application to specify preferences for the sizes of the portion of your application’s heap used by a scripting component for its application-specific heap and stack. Listing 8-5 shows the resource type declaration in Rez format for the 'scsz' resource. Listing 8-5    Resource type declaration for the 'scsz' resourcetype 'scsz' {    boolean            dontReadExtensionTerms, /*if application needs */                 readExtensionTerms;                                /* Get AETE event*/    boolean            reserved;    boolean            reserved;    boolean            reserved;    boolean            reserved;    boolean            reserved;    boolean            reserved;    boolean            reserved;    boolean            reserved;    boolean            reserved;    boolean            reserved;    boolean            reserved;    boolean            reserved;    boolean            reserved;    boolean            reserved;    boolean            reserved;/*memory sizes are in bytes; 0 means use default*/    unsigned longint                        minStackSize;                            /*minimum stack size*/    unsigned longint                        preferredStackSize;                            /*preferred stack size*/    unsigned longint                        maxStackSize;                            /*maximum stack size*/    unsigned longint                        minHeapSize;                            /*minimum heap size*/    unsigned longint                        preferredHeapSize;                            /*preferred stack size*/    unsigned longint                        maxHeapSize;                            /*maximum heap size*/};The data for an 'scsz' resource consists of the following items:n    Flags that specify Boolean values:n    Whether the scripting component should (readExtensionTerms) or shouldn’t (dontReadExtensionTerms) read the application’s terminology information directly from its 'aete' resource. If the application is not running, this flag allows a scripting component to determine whether it should read the application’s terminology information without sending it a Get AETE event.n    The following 15 bits are reserved for future use. Their values must be set to reserved.n    The minimum size for the portion of the application’s heap used by the scripting component’s application-specific stackn    The preferred size for the portion of the application’s heap used by the scripting component’s application-specific stackn    The maximum size for the portion of the application’s heap used by the scripting component’s application-specific stackn    The minimum size for the portion of the application’s heap used by the scripting component’s application-specific heapn    The preferred size for the portion of the application’s heap used by the scripting component’s application-specific heapn    The maximum size for the portion of the application’s heap used by the scripting component’s application-specific heapIf you specify 0 for any of the fields that specify memory size or number of script IDs, the scripting component uses its own default values for those fields. The AppleScript component provides a function, ASInit, that allows your application to initialize the component with desired values for memory sizes or number of script IDs. If your application doesn’t call ASInit, the AppleScript component initializes itself using either the values specified in the application’s 'scsz' resource or, for those values not provided by the 'scsz' resource, default values provided by the AppleScript component. For more information about ASInit, see “Initializing AppleScript” on page 10-80.  Listing 9-0Table 9-0Recording Apple EventsContentsAbout Recordable Applications9-3Factoring Your Application for Recording9-6Factoring the Quit Command and the New Command9-6Sending Apple Events Without Executing Them9-12What to Record9-14Recording User Actions9-15Recording the Selection of Text Objects9-18Recording Insertion Points9-23Recording Typing9-27Recording the Selection of Nontext Objects9-30Identifying Objects9-32Moving the Selection During Recording9-34Recording Interactions With Dialog Boxes9-35How Apple Event Recording Works9-35Recording Apple EventsThis chapter describes the general characteristics of a recordable application and provides some examples of how to factor your application for recording. It also provides guidelines to help you decide which user actions to record and how to record them. Before you read this chapter, you should read the chapter “Introduction to Scripting” in this book. To factor your application, you must know how to respond to Apple events, create and send Apple events, and resolve and create object specifier records. For comprehensive information about implementing Apple events, see the chapters “Introduction to Apple Events,” “Responding to Apple Events,” “Creating and Sending Apple Events,” and “Resolving and Creating Object Specifier Records” in this book.The first three sections in this chapter providen    a description of the basic requirements for recordable applicationsn    examples of how to begin factoring your applicationn    guidelines for what to recordThe fourth section describes how Apple event recording works. You need to read it only if you are developing a script editor, an application that can initiate recording, or a scripting component.About Recordable ApplicationsA recordable application is an application that uses Apple events to report user actions to the Apple Event Manager for recording purposes. One way to do this is to separate the code that implements your application’s user interface from the code that actually performs work when the user manipulates the interface. This is called factoring your application. A factored application translates low-level events generated by the user into recordable Apple events that the application sends to itself to perform tasks.A recordable event is any Apple event that any recordable application sends to itself while recording is turned on for the local computer, with the exception of events that are sent with the kAEDontRecord flag set in the sendMode parameter of AESend. A recording process is any process (for example, the Script Editor application) that can turn recording on and off and can receive and record recordable Apple events. After Apple event recording has been turned on by a recording process, the Apple Event Manager sends that process copies of all recordable Apple events on the local computer. For example, when a user presses the Record button in the Script Editor application, it calls a scripting component routine to turn on recording for the AppleScript component (or any other scripting component). While recording is on, the Apple Event Manager sends Script Editor copies of all subsequent recordable Apple events, which Script Editor records (with the aid of the scripting component) in the form of a compiled script. After turning off recording from Script Editor, the user can edit or execute the recorded script.Although factoring your application is the recommended method of making your application recordable, it is also possible to report user actions by means of Apple events only when Apple event recording is turned on, even though the application may respond to those actions by some means other than Apple events. In effect, the application uses Apple events to describe user actions without actually using the events to perform the action. To indicate that you want the Apple Event Manager to send a copy of a recordable event to the recording process without actually sending the event to your application, add the constant kAEDontExecute to the sendMode parameter of the AESend function.Even in a factored application, it may not always be possible to send an Apple event that actually executes the task initiated by the user. For example, if the user types some text, it is more practical to use standard TextEdit or QuickDraw routines to draw the text than to send a separate Apple event each time the user presses a key. In this case, the application can draw the text as it is typed in the most convenient manner available; then, when the user finishes typing a sequence of characters—by clicking the mouse button while the cursor is somewhere else in the document or performing some other action—the application can create an Apple event that corresponds to the typing and add the constant kAEDontExecute to the sendMode parameter when it sends the Apple event. If your application needs to know when Apple event recording is turned on and off, it should install handlers for the Recording On and Recording Off events.Recording On—perform actions associated with beginning of recording session         Event class    kCoreEventClass    Event ID    kAENotifyStartRecording    Parameters    None    Description    Sent by the Apple Event Manager to all running processes on the local computer to inform them that recording has been turned on    Recording Off—perform actions associated with end of recording session         Event class    kCoreEventClass    Event ID    kAENotifyStopRecording    Parameters    None    Description    Sent by the Apple Event Manager to all running processes on the local computer to inform them that recording has been turned off    When a recording process turns on recording, the Apple Event Manager sends all running processes on the local computer a Recording On event. When a user turns off recording, the Apple Event Manager sends all running processes the Recording Off event with the kAEWaitReply flag set. If an application has stored some data (for instance, keystrokes) that needs to be recorded as an Apple event, this is the last chance to send an event for recording purposes. If your application needs to know which recording process has turned recording on or off, it can check the keyOriginalAddressAttr attribute of the Recording On or Recording Off event for the address of the recording process. Factoring your application is the recommended method of making your application recordable because it guarantees that any action a user can perform via your application’s user interface can also be accomplished via Apple events. Factoring also allows you to avoid duplicating code within your application. Instead of using one piece of code to respond to some user action within your application, and another piece of code to respond to the equivalent Apple event, you can use the same code to respond to the Apple event, whether it is sent by your application in response to a user action, by some other application, or by a scripting component in the course of executing a script. The next section, “Factoring Your Application for Recording,” provides some examples of how to go about factoring your application. Regardless of how you factor your application, making it recordable requires you to make decisions about the most useful methods of recording user actions that can be described in several different ways in scripts. If a user moves a window, for example, the window can be described in the corresponding recorded script as window 1, or the window named Fred, or the first window. Although the OSA permits recording at a high level and thus avoids many of the problems users encounter with applications that record low-level events such as keystrokes and mouse clicks, scripting components cannot predict what information a user cares about in a given situation. Therefore, a recordable application should send Apple events that correspond to the simplest possible statements in a scripting language. “What to Record,” which begins on page 9-14, provides some general guidelines for making these kinds of decisions.“How Apple Event Recording Works,” which begins on page 9-35, describes the Apple Event Manager’s recording mechanism in more detail, including the role of the Recording On and Recording Off events. Factoring Your Application for RecordingThe recommended way to make your application recordable, or capable of sending Apple events to itself whenever a user performs a significant action, is to factor the code that controls your application’s user interface from the code that responds to the user’s manipulation of the interface. A fully factored application translates user actions into Apple events that the application sends to itself to initiate tasks.  The examples that follow demonstrate how to factor code that responds to relatively simple user actions such as creating a new document or moving a window. They are intended only to illustrate the general approach you should take; many of the decisions you will need to make while factoring will be unique to your application. “What to Record,” which begins on page 9-14, provides guidelines for deciding which user actions to record and how to record them. For examples of factored applications, see the AppleScript Software Developers’ Kit. If you are factoring an existing application, it’s usually a good idea to begin with the required Apple events and any other Apple events that you plan to send in order to execute commands in the File menu. You can then proceed to other menu commands and mouse actions. If you are designing a new application and want to make it recordable, you should build factoring into every aspect of your application design.Factoring the Quit Command and the New CommandThis section demonstrates how to factor two File menu commands: Quit and New. When the user chooses a menu command, an application first determines which one was chosen and then performs the action associated with that command. For example, when a user chooses Quit from the File menu, an application that is not factored simply calls an application-defined DoQuit routine. Because Quit Application is one of the required Apple events, it is relatively easy for most applications that support Apple events to factor the code that responds to the Quit command.After a factored application has determined that the user has chosen the Quit command, it sends the Quit Application event to itself by calling its MyDoMenuQuit routine.PROCEDURE MyDoMenuQuit;VAR    myErr: OSErr;BEGIN    myErr := MySendAEQuit(kAEAskUser);    {handle any errors}END;The MyDoMenuQuit routine in turn calls the MySendAEQuit routine shown in Listing 9-1, which creates the Quit Application event and sends it. Listing 9-1    A function used by a factored application to send itself a Quit Application eventFUNCTION MySendAEQuit (saveOpt: DescType): OSErr;VAR     myAppleEvent, defReply:                                AppleEvent;    myErr, ignoreErr:                                OSErr;BEGIN    {create Quit event}    myErr := AECreateAppleEvent(kCoreEventClass,                                             kAEQuitApplication,                                             gSelfAddrDesc,                                             kAutoGenerateReturnID,                                             kAnyTransactionID, myAppleEvent);    IF myErr = noErr THEN        {add optional parameter that specifies whether this app }        { should prompt user if window is dirty}        myErr := AEPutParamPtr(myAppleEvent, keyAESaveOptions,                                         typeEnumerated, @saveOpt,                                        SizeOf(saveOpt));    IF myErr = noErr THEN             {send event}        myErr := AESend(myAppleEvent, defReply,                                 kAENoReply+kAEAlwaysInteract,                                kAENormalPriority, kAEDefaultTimeOut,                                NIL, NIL);    MySendAEQuit := myErr;    ignoreErr := AEDisposeDesc(myAppleEvent);END;The input to the MySendAEQuit routine is a constant that indicates whether to save dirty windows without asking the user (kAEYes), quit without saving dirty windows (kAENo), or ask the user whether each dirty window should be saved (kAEAskUser). In this example, the constant kAEAskUser passed to the MySendAEQuit routine indicates that the user will be asked whether each dirty window should be saved. After the application receives the Quit Application event, the MyHandleQuit handler shown in Listing 9-2 performs all the actions associated with that event, such as saving any open documents. (Note that your application should call the ExitToShell procedure from the main event loop, not from your handler for the Quit Application event.)Listing 9-2    A routine used by a factored application to handle a Quit Application eventFUNCTION MyHandleQuit (theAppleEvent, reply: AppleEvent;                                handlerRefcon: LongInt): OSErr;VAR    userCanceled:                                Boolean;    saveOpt, returnedType:                                DescType;    actSize:                                Size;    myErr:                                OSErr;BEGIN    {check for missing required parameters}    myErr := MyGotRequiredParams(theAppleEvent);    IF myErr = noErr THEN    BEGIN        {pick up optional save parameter}        saveOpt := kAEAskUser;                                {the default}        myErr := AEGetParamPtr(theAppleEvent, keyAESaveOptions,                                         typeEnumerated, returnedType,                                        @saveOpt, SizeOf(saveOpt), actSize);        IF myErr = errAEDescNotFound THEN             myErr := noErr;        MyHandleQuit := myErr;        IF myErr = noErr THEN        BEGIN            userCanceled := MyPrepareToTerminate(saveOpt);            IF userCanceled THEN                 MyHandleQuit := kUserCanceled;        END;    END    ELSE        MyHandleQuit := myErr;END;The handler in Listing 9-2 calls another function supplied by the application, the MyPrepareToTerminate function. When the value of the optional parameter that specifies how to deal with dirty windows equals kAEAskUser, this function asks the user whether to save each dirty window and returns a Boolean value that indicates whether the user canceled the Quit request. It also responds appropriately to the other possible values of the optional parameter.If recording has been turned on for a scripting component (for example, after a user clicks the Record button in the Script Editor application) and the user quits the application, the Apple Event Manager automatically sends the scripting component a copy of the Quit Application event sent by the MySendAEQuit routine. The scripting component records the event in a compiled script. When a user executes the recorded script, the scripting component sends the same Quit Application event to the application, which calls the MyHandleQuit function and responds to the event just as if the user had chosen Quit from the File menu.  After you have factored the commands associated with required Apple events for an existing application, you can move on to the other commands in the File menu, such as New. After a factored application has determined that the user has chosen New, it calls its MyDoMenuNew routine, which sends the Create Element event to the application.PROCEDURE MyDoMenuNew;VAR    myErr := OSErr;BEGIN    myErr := MySendAECreateElement(gNullDesc, cDocument);    {handle any errors}END;The container for the new element is the application’s default container, specified by a null descriptor record, and the desired class is cDocument. The MyDoMenuNew routine in turn calls the MySendAECreateElement routine shown in Listing 9-3, which creates the Apple event and sends it. Listing 9-3    A routine used by a factored application to send itself a Create Element eventFUNCTION MySendAECreateElement (cont: AEDesc;                                           elemClass: DescType): OSErr; VAR     myAppleEvent, defReply:                                AppleEvent;    myErr, ignoreErr:                                OSErr;BEGIN    {create Create Element event}    myErr := AECreateAppleEvent(kCoreEventClass, kAECreateElement,                                            gSelfAddrDesc,                                            kAutoGenerateReturnID,                                            kAnyTransactionID, myAppleEvent);    IF myErr = noErr THEN        {add parameter that specifies insertion location for the }        { new element}        myErr :=  AEPutParamDesc(myAppleEvent,keyAEInsertHere,cont);    IF myErr = noErr THEN         {add parameter that specifies new element's object class}        myErr := AEPutParamPtr(myAppleEvent, keyAEObjectClass,                                      typeType, @elemClass,                                      SizeOf(elemClass));    IF myErr = noErr THEN        {send the event}        myErr := AESend(myAppleEvent, defReply,                                 kAENoReply+kAECanInteract,                                                         kAENormalPriority, kAEDefaultTimeOut, NIL,                                 NIL);    MySendAECreateElement := myErr;    ignoreErr := AEDisposeDesc(myAppleEvent); {must dispose of }                                                            { event}END;For the purposes of this example, the routine shown in Listing 9-3 sends only the required parameters and can only create a new active window with the default name. After the application receives the Create Element event, its MyHandleCreateElement handler performs the requested action, as shown in Listing 9-4. In this case, it creates a new active window with a default title.Listing 9-4    The Create Element event handler for a factored applicationFUNCTION MyHandleCreateElement (theAppleEvent: AppleEvent;                                           reply: AppleEvent;                                           handlerRefCon: LongInt): OSErr;VAR    myCont:                                     AEDesc;    returnedType    , newElemClass:                                 DescType;    actSize:                                     Size;    contClass:                                     DescType;    window:                                     WindowPtr;    myErr:                                     OSErr;BEGIN    {get the parameters out of the event}    {first get the direct parameter, which specifies insertion }    { location for new window--that is, frontmost window}    myCont.dataHandle := NIL;    myErr := AEGetParamDesc(theAppleEvent, keyAEInsertHere,                                     typeWildCard, myCont);    IF myErr = noErr THEN        {get the other required parameter, which specifies class }        { cDocument when MyHandleCreateElement creates a new window}        myErr := AEGetParamPtr(theAppleEvent, keyAEObjectClass,                                         typeType, returnedType,                                        @newElemClass,                                         SizeOf(newElemClass), actSize);    IF myErr = noErr THEN        myErr := MyGotRequiredParams(theAppleEvent);    MyHandleCreateElement := myErr;    IF myErr = noErr THEN    BEGIN        {check container and class, just to make sure}        IF (myCont.descriptorType <> typeNull) OR (newElemClass <>                 cDocument) THEN             MyHandleCreateElement := kWrongContainerOrElement        ELSE            {MyNewWindow creates a new window with a default name }            { and returns a pointer to it in the window parameter}            MyHandleCreateElement := MyNewWindow(window);                                                END;    myErr := AEDisposeDesc(myCont);    {if your app sends a reply in response to the Create Element }    { event, then set up the reply event as appropriate}END; If recording has been turned on for a scripting component (for example, after a user clicks the Record button in the Script Editor application), the Apple Event Manager automatically sends the scripting component a copy of the Create Element event sent by the MySendAECreateElement routine. The scripting component records the Apple event as a statement in a compiled script. When a user executes the recorded script, the scripting component sends the same Create Element event to the application, which calls its MyHandleCreateElement handler and responds to the event just as if the user had chosen New from the File menu. Sending Apple Events Without Executing ThemIf an application is fully factored, it carries out almost all the tasks a user can perform by sending itself Apple events in the manner illustrated by the listings in the preceding sections. However, in some cases it may not be practical to send an Apple event that actually executes a task performed by the user. For example, if the user drags a window by its title bar from one position to another, it is inefficient to send a series of Apple events that move the window through a series of positions until the user releases the mouse button. Instead, your application can call the Window Manager routine DragWindow to allow the user to drag the window to a new position. Until the user releases the mouse button, it’s not possible to send a single Apple event that drags the window to the new position, because the new position is not yet known. When DragWindow returns, the window has already been dragged to its new position, and its window record has been updated. At this point your application can send itself the Set Data event that performs the same action; but to avoid repeating the action that was just performed with DragWindow, you should add the kAEDontExecute constant to the sendMode parameter of the AESend function when you send the event. The Apple Event Manager then sends the Set Data event to the recording process, if any, but does not send it to the application. Listing 9-5 shows an application-defined routine, MyDoDragWindow, that illustrates this approach. The MyDoDragWindow routine calls DragWindow in the usual way, then uses another application-defined routine, MyCreateAESetWindowPos, and the AESend function to create and send a Set Data Apple event that sets the window position to the new location. However, because the window has already been moved, there is no need to execute the Set Data event. To send the event for recording purposes without actually executing it, the MyDoDragWindow routine adds the kAEDontExecute constant to the sendMode parameter of the AESend function when it sends the Set Data event. Listing 9-5    A routine used by a factored application to handle window movementPROCEDURE MyDoDragWindow (theWindow: WindowPtr; startPt: Point;                                   boundsRect: Rect);VAR     newPos:                    Point;    index:                    Integer;    theAppleEvent:                    AppleEvent;    reply:                    AppleEvent;    myErr:                    OSErr;BEGIN    DragWindow(theWindow, startPt, boundsRect);    newPos := WindowPeek(theWindow)^.contRgn^^.rgnBBox.topLeft;        index := MyIndexFromWndwPtr(theWindow);    MyCreateAESetWindowPos(index, newPos, theAppleEvent);    myErr := AESend(theAppleEvent, reply, kAENoReply +                             kAECanInteract + kAEDontExecute,                            kAENormalPriority, kAEDefaultTimeout, NIL,                             NIL);END;If recording has been turned on and the user moves a window, the Apple Event Manager automatically sends the scripting component a copy of the Set Data event sent by the MyDoDragWindow routine but does not send the event to the application. The scripting component records the event as a statement in a compiled script. When a user executes the recorded script, the scripting component sends the same Set Data event to the application. The application’s handler for the Set Data event then changes the position of the window.  What to RecordFactoring an application involves making decisions about which user actions generate Apple events, about the content of those events, and about when to send events for recording purposes. For example, the preceding section, “Sending Apple Events Without Executing Them,” describes how an application should generate an Apple event that corresponds to a change in the position of a window. Other actions can be more complicated to define in terms of Apple events. This section provides general guidelines for deciding which user actions should generate Apple events and how those events should be defined.When the user records a series of actions as a script, playing the recorded script back later in exactly the same circumstances must produce exactly the same result. If the circumstances at execution time are similar but not exactly the same as when the script was recorded, the script should also work correctly. However, certain differences will always lead to unexpected results or cause execution to fail.The goal of these guidelines is to help you create scripts that will work correctly in the largest number of circumstances with the fewest post-recording changes by the user. To accomplish this goal, a recordable application should send itself Apple events that describe as specifically as possible the user’s actions in the application’s domain without making guesses about the user’s intentions.The way your application uses Apple events to record a user’s actions depends in part on the kind of script being recorded. From the user’s perspective, there are at least three kinds of scripts:n    A script application. The icons for these files appear in the Finder, for example, in the Apple Menu Items folder or the Startup Items folder. n    A script that functions like a menu command, usually acting on the current selection in the current application, and stored either as a compiled script file that appears in the Finder or as a script stored within an application or one of its documents. n    A script that is “embedded” in an application—that is, explicitly associated with something in a document, such as a field in a form, a cell or row of a spreadsheet, or a button.The recording guidelines in the sections that follow apply to the recording of scripts that function like menu commands and scripts that are embedded in an application. Because such scripts are executed under a user’s direct control, the user expects their execution to cause something to happen, possibly changing the current selection, the Clipboard, or the active window.The execution of a script application, however, may cause a scripting component to send events to one or more applications intermittently without the user’s knowledge. If the script in a script application refers to the current selection, the Clipboard, or the active window, its execution may interfere with other tasks being performed by the user or tasks performed during the execution of other scripts. To create a script application and ensure that it works correctly when executed, a scripter may need to modify the script after it has been recorded.For example, to eliminate references to the Clipboard, a scripter can use a script variable as a user-defined Clipboard and convert Cut, Copy, and Paste statements to appropriate combinations of Move, Copy, New, and Delete statements, while supplying the previously defined selection as the argument. It may also be necessary to convert a description such as “the front document” to a specific filename or a variable.Recording User ActionsTwo general guidelines apply to the recording of all user actions:n    Send Apple events that correspond to simple statements in a script rather than compound statements.n    Don’t record superfluous actions.In most cases, if the user performs several related actions, your application should send Apple events for each action rather than saving the actions and creating an event that combines them. For example, if the user selects some text, cuts it, and then pastes it somewhere else, your application should send itself four events that correspond to these actions:    1.    Select the text    2.    Cut    3.    Set the insertion point    4.    PasteThus, if the user selects characters 5 through 20 of the frontmost document, chooses the Cut command from the Edit menu, places the insertion point after character 72, and chooses the Paste command, your application should send the following events. n    A Select event (event class kAEMiscStandards, event ID kAESelect) with this direct parameter:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cChar    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cDocument    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    1    keyAEKeyForm    typeEnumerated    formRange    keyAEKeyData    typeRangeDescriptor    (see indented record)    keyAERangeStart    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cChar    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    5    keyAERangeStop    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cChar    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    20    n    A Cut event (event class kAEMiscStandards, event ID kAECut)n    A Select event with this direct parameter:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cInsertionLoc    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cChar    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cDocument    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    1    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    72    keyAEKeyForm    typeEnumerated    formRelativePosition    keyAEKeyData    typeEnumerated    kAEAfter    n    A Paste eventNoteThe format used for the direct parameters in this example and throughout this chapter does not show the structure of the direct parameters as they exist within the Apple events. Instead, this format shows what you would obtain after calling AEGetKeyDesc repeatedly to extract the nested descriptor records from the Apple events.When you call AEGetKeyDesc to extract the descriptor record that specifies an application’s default container, AEGetKeyDesc returns a descriptor record of type AEDesc with a descriptor type of typeNull and a data handle whose value is 0.uThe first Select event in this example sets the application’s pSelection property (that is, the current selection) to the objects identified by the object specifier record in the direct parameter—characters 5 through 20. The second Select event places the insertion point after the object identified by the object specifier in the direct parameter—after character 72.You could also interpret these four actions as a single Move event that simply moves characters 5 through 20 to after character 72. A user could write such a statement in a script, but for recording purposes four separate events correspond more precisely to the user’s actions. For example, if the user performed another paste operation after the first four actions, a Move event would not produce the correct results.It is equally important for a recordable application not to send superfluous events. For example, your application should not send an event every time the user makes a selection. Instead, it should keep track of the most recent selection made. When the user performs some action on the selection, the application should send an event that sets the selection followed by the event that corresponds to the action taken by the user. However, if the user doesn’t perform an action on the selection, the application should not send an event.IMPORTANTIf something is already selected when recording begins, your application should not record that selection. Subsequent user actions should be recorded assuming that there is a selection. By not recording the current selection, you allow the user to record scripts that work, without further modification, much like menu commands that operate on the current selection.sThe example just discussed assumes that the application has multiple documents. In such an application, document 1 is always the document in the frontmost window. The examples that follow are simplified, as if they were generated by an application like TeachText that can have only one document open at a time and can therefore locate objects such as characters in the default container. For more complex applications that locate text in cells, documents, and other containers, you must specify additional containers as appropriate.Recording the Selection of Text ObjectsWhen your application needs to record a selection that the user has made by dragging through a range of text, it should send itself a Select event that selects a range of characters. For example, a Select event with this direct parameter selects characters 80 through 764:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cChar    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formRange    keyAEKeyData    typeRangeDescriptor    (see indented record)    keyAERangeStart    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cChar    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    80    keyAERangeStop    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cChar    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    764    It is sufficient to record such a text selection as a range of characters. However, recording selections in other units can make the corresponding scripts easier to read. If you decide to record text selections in other units, keep these guidelines in mind:n    Use the largest whole unit that completely describes the selection.n    Do not mix units.n    Use units appropriate to the method of selection.n    Use logical units rather than units that vary with reformatting.n    Don’t try to guess the user’s intentions.The rest of this section provides examples of how to apply these guidelines.If you do record text selections in units other than characters, record each selection in terms of the largest whole unit that completely describes the selection. For example, suppose the user selects characters 115 through 170 by dragging. Further, suppose the selected characters are exactly the same as words 33 through 50 and also the same as paragraph 2. In this case your application should send itself a Select event with this direct parameter:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cParagraph    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    2    However, if the selected characters don’t match a larger unit exactly—for example, if paragraph 2 is larger than the selection or the selection is a portion of two paragraphs— use the largest unit available, in this case words. For example, a Select event with this direct parameter selects word 33 through word 45: Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cText    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formRange    keyAEKeyData    typeRangeDescriptor    (see indented record)    keyAERangeStart    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cWord    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    33    keyAERangeStop    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cWord    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    45    Do not mix units. You should not send Apple events that define selections like character 2 of word 3 of line 5 of paragraph 2 in document “MyDocument.” Instead, define selections as simply as possible; for example, character 45 in the document “MyDocument.”When the user selects text by double-clicking it, your application should send a Select event that specifies words. For example, your application should send a Select event with this direct parameter when the user double-clicks word 5:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cWord    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    5     If the user double-clicks word 5 and then extends the selection through word 9, your application should send a Select event with this direct parameter:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cText    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formRange    keyAEKeyData    typeRangeDescriptor    (see indented record)    keyAERangeStart    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cWord    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    5    keyAERangeStop    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cWord    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    9    If your application supports selection of a paragraph, for example by clicking the left margin, triple-clicking, or some other action, your application should send a Select event that selects the paragraph. For example, a Select event with this direct parameter selects paragraph 2:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cParagraph    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    2    If your application supports the selection of other units (for instance, cells, rows, and columns in a spreadsheet; embedded graphics in a word processor; or buttons) and if users can select a range of such units, your application should record using those units when appropriate. For example, a Select event with this direct parameter selects row 5 through row 23:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cRow    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formRange    keyAEKeyData    typeRangeDescriptor    (see indented record)    keyAERangeStart    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cRow    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    5    keyAERangeStop    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cRow    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    23    A Select event with this direct parameter selects the second 'PICT' image:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cPICT    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    2    When the user chooses a Select All command, your application should send a Select event with this direct parameter to select the contents of the document:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cProperty    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formPropertyID    keyAEKeyData    typeLongInteger    pContents    Units that vary with reformatting, such as lines and pages in a text document, are not as useful as logical units that describe the data more precisely. Whenever possible, use logical units such as character, word, paragraph, section, and so on.Don’t try to guess the user’s intentions. For example, if a selection can be described as either “word 14” or as “the third bold word in paragraph 3,” use the simpler description. If you guess the user’s intentions, you will be wrong often enough to cause the user to distrust the recording process.Recording Insertion PointsThe insertion point and a selection are synonymous in the Macintosh Operating System. However, scripting languages need a way of specifying a zero-width selection. Sometimes the best way to specify an insertion location is in relation to another object; for example, “after word 5.” This section describes recommended methods of specifying an insertion point in a recordable event.The insertion point can be specified in Apple events by either an insertion location descriptor record (typeInsertionLocation) or an object specifier record (typeObjectSpecifier) that specifies the class cInsertionLoc and the key form formRelativePosition. The Move, Clone, and Create events accept an insertion location descriptor record; other events, including Select and Set Data, require an object specifier record. Five constants can be used to describe an insertion point in relation to an object or container: Constant    Corresponding insertion point    kAEReplace    The specified object will be replaced if not qualified by one of the other phrases    kAEBefore    Just before the specified object (either type typeObjectSpecifier or type typeInsertionLocation)    kAEAfter    Just after the specified object (either type typeObjectSpecifier or type typeInsertionLocation)    kAEBeginning    In the specified container and before all other elements of the same class in that container (type typeInsertionLocation only)    kAEEnd    In the specified container and after all other elements of the same class in that container     For more information about the way AppleScript uses insertion location descriptor records, see “Defining Terminology for Use by the AppleScript Component,” which begins on page 8-3, and the Apple Event Registry: Standard Suites. The rest of this section provides examples of object specifier records used to specify insertion points.Users usually insert objects after some other object. So, unless the insertion point is clearly at the beginning or end of a container or identifies an object to be replaced, use the constant kAEAfter to record the location. For example, if the user places the insertion point after character 2, your application should send a Select event with this direct parameter:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cInsertionLoc    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cChar    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    2    keyAEKeyForm    typeEnumerated    formRelativePosition    keyAEKeyData    typeEnumerated    kAEAfter    If the selection is not 0 characters wide, the user is replacing the selection with another object, so you can specify the location simply as the object specifier record for the object to be replaced.If the user clicks the white space after a paragraph somewhere in the middle of the document, defining the insertion point becomes more complex because different applications deal with this situation in different ways. Some place the insertion point at the end of the current paragraph, while others place the insertion point at the beginning of the next paragraph. Depending on the way your application handles this situation, you should use an object specifier record that specifies either kAEBeginning or kAEEnd.Remember that the Select event requires an object specifier record. Thus, if you want to place the insertion point at the beginning of a paragraph, use an object specifier record that specifies a location just before the first item of the paragraph, rather than an insertion location descriptor record. For example, a Select event with this direct parameter places the insertion point just before the first item of paragraph 3:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cInsertionLoc    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cItem    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cParagraph    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    3    keyAEKeyForm    typeType    formAbsolutePosition    keyAEKeyData    typeLongInteger    1    keyAEKeyForm    typeEnumerated    formRelativePosition    keyAEKeyData    typeEnumerated    kAEPrevious    If the user clicks the left edge of the first line in a paragraph, thus setting the insertion point before the beginning of the paragraph, you should use a similar strategy. However, this is the only situation in which you should use kAEPrevious.When the insertion point is at the end of a document record, use an object specifier record that specifies the location after the last item in the document.For example, a Select event with this direct parameter places the insertion point just after the last item in a document:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cInsertionLoc    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cItem    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    -1    keyAEKeyForm    typeEnumerated    formRelativePosition    keyAEKeyData    typeEnumerated    kAENext     A Select event with this direct parameter places the insertion point just after the last item in paragraph 3:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cInsertionLoc    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cParagraph    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    3    keyAEKeyForm    typeEnumerated    formRelativePosition    keyAEKeyData    typeEnumerated    kAENext    Recording TypingIn general, to record typing your application should send itself a Set Data event that sets the contents of the selection. The data should be unstyled text. When your application handles the Set Data event, it should apply the styles that prevail at the insertion point. If your application supports styled text, you need to decide how to apply styles to new text and how to record style changes to selected text. Follow these general guidelines for recording typing: n    When the user sets an insertion point and types new text, use the styles defined for the text just before the insertion location.n    When a user selects text and changes its style, apply the changes to the selection.n    If a user types or pastes new text into a selection, place the insertion point after the new text.The rest of this section provides examples of how to apply these guidelines.Suppose the user sets an insertion point and then types something. Your application should use the style, font, size, and other characteristics of the text just before the insertion point for the new text, and it should record only the new characters inserted. For example, to place the insertion point after word 30 and insert the text “This is the new text,” your application can send a Select event followed by a Set Data event:n    A Select event with this direct parameter places the insertion point after word 30:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cInsertionLoc    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cWord    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    30    keyAEKeyForm    typeEnumerated    formRelativePosition    keyAEKeyData    typeEnumerated    kAENext    n    A Set Data event (event class kAECoreSuite, event ID kAESetData) with these parameters (keyDirectObject and keyAEData) sets the selection to the new text:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cProperty    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cProperty    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formPropertyID    keyAEKeyData    typeLongInteger    pSelection    keyAEKeyForm    typeEnumerated    formPropertyID    keyAEKeyData    typeType    pContents    keyAEData    typeChar    "This is the new text"    Notice that the Select event in this example causes your application to set its pSelection property (the current selection) to the location specified by the object specifier record in the direct parameter—that is, after word 30. The Set Data event then sets the contents of the selection to a text string. The pContents property specified by the object specifier record in the direct parameter of the Set Data event represents the contents of the selection, and the text string in the keyAEData parameter is the text to which the selection’s contents is to be set. At this stage, the insertion point is after word 35—the last word added by typing. If the user now selects one of the new words, say word 34, and changes the style to boldface and the font to Helvetica®, send a Select event and two Set Data events to record the action:n    A Select event with this direct parameter selects word 34:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cWord    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    34    n    A Set Data event with these parameters sets the style of the selection to boldfaceKeyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cProperty    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cProperty    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formPropertyID    keyAEKeyData    typeLongInteger    pSelection    keyAEKeyForm    typeType    formPropertyID    keyAEKeyData    typeType    pTextStyles    keyAEData    typeEnumerated    kAEBold    :n    A Set Data event with these parameters sets the font of the selection to Helvetica: Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cProperty    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cProperty    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formPropertyID    keyAEKeyData    typeLongInteger    pSelection    keyAEKeyForm    typeEnumerated    formPropertyID    keyAEKeyData    typeType    pFont    keyAEData    typeChar    "Helvetica"    After these three events are sent, word 34 remains selected. Thus, subsequent user actions upon the same selection do not require your application to send an additional event to set the selection. Your application should maintain the selection as long as the selected text is not replaced. If the user types or pastes new text into the selection, your application should place the insertion point after the new text. Such a strategy might result in a series of events like these:n    A Set Data event with these parameters sets the contents of a selection to “More new text”:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cProperty    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cProperty    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formPropertyID    keyAEKeyData    typeLongInteger    pSelection    keyAEKeyForm    typeEnumerated    formPropertyID    keyAEKeyData    typeType    pContents    keyAEData    typeChar    "More new text"    n    Two Paste events paste the contents of the Clipboard twice after the new text. Recording the Selection of Nontext ObjectsThe selection of nontext objects differs from the selection of text objects mainly in the way a recordable application specifies the objects. For example, if the user is working in a table or spreadsheet and selects row 5, column 3, your application can send a Select event with this direct parameter:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cRow    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cColumn    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    3    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    5    When recording a range of cells, use a range of rows through a range of columns. For example, if the user selects row 5 column 3 through row 6 column 4, specify columns 3 through 4 of rows 5 through 6 by sending a Select event with this direct parameter:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cRow    keyAEContainer    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cColumn    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formRange    keyAEKeyData    typeRangeDescriptor    (see indented record)    keyAERangeStart    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cColumn    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    3    keyAERangeStop    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cColumn    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    4    keyAEKeyForm    typeEnumerated    formRange    keyAEKeyData    typeRangeDescriptor    (see indented record)    keyAERangeStart    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cRow    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    5    keyAERangeStop    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cRow    keyAEContainer    typeCurrentContainer    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    6    In some drawing and layout applications, users are used to dealing with insertion points at specific locations rather than relative to other objects. For example, setting an insertion point in a recordable drawing application might cause the application to send itself a Select event that places the insertion location at (235, 330)—that is, the location defined by a vertical coordinate of 235 and a horizontal coordinate of 330. A Select event that does this could have this direct parameter:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cInsertionLocation    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeAEList    (see indented record)        typeLongInteger    235        typeLongInteger    330    Notice that the key data corresponds to an application’s extension of the standard interpretation of key form formAbsolutePosition. To set a selection that consists of noncontiguous objects, an application should send events that correspond to statements like these:select {¬    row 5 thru 6 of column 3 thru 4, ¬    row 22 of column 6}select {circle 2, rectangle 12, text frame 2}select {file "Guidelines", file "Test Results"} Identifying ObjectsThe way a recordable application identifies objects can involve assumptions about the user’s criteria for selecting those objects. In general, such assumptions should be avoided. Follow these guidelines for identifying objects:n    If you aren’t absolutely certain of the user’s criteria for selecting an object, identify the object by name.n    If the object doesn’t have a name, identify it by index.n    Determine the index based on the order in which a user would see the objects when reading a document.n    Identify windows and open documents on which actions are taken as the frontmost window or document.The rest of this section provides examples of how to apply these guidelines.Suppose a user is working with an electronic mail application that permits a variety of sorting methods for messages received. If the user is currently looking at messages sorted by date and then deletes the second message in the list, that message should be identified by name rather than by date. Use an object’s name in any situation where it is not completely clear which identifying criteria the user had in mind.Suppose a user has used the application’s Find command to locate all messages created on a certain date. In this case it might be appropriate to identify “every message whose creation date . . .” in the corresponding Apple event. However, if the user did not ask for all messages created on that date, you can’t be sure whether the user really wanted every message or only a particular one. For instance, perhaps the user couldn’t remember the name, but only an approximate date. In this case a recordable application should identify the message by name.Just as names are more specific and usually more desirable than whose tests, names are usually more specific and more readable than identifiers or indices. However, some objects may not have a name, only some other identifier or an index. Even though an identifier is more specific than an index, a logically defined index of position is more readable and is therefore recommended. For example, if a document contains unnamed illustrations, the user is more likely to identify a figure by index (order from the beginning of the file) than identifier (such as order created).Suppose a document contains two figures that appear at first glance to be side by side, except that the right one is slightly taller and therefore begins higher on the page than the left one. In cases such as this, your application should determine the index based on the order in which the user would see the objects when reading a document. For Roman script systems, this means reading from left to right and from top to bottom. In the example just described, the leftmost, shorter figure would have a lower figure number than the rightmost, taller one.When your application needs to refer to a window or a document, it should identify the object with an object specifier record that corresponds to the first, or front, window:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cWindow    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formAbsolutePosition    keyAEKeyData    typeLongInteger    1    This strategy allows users to record scripts that will work on any window, regardless     of its name. Similarly, events that act on an open document should identify it as “document 1.”It is usually possible to describe objects in several different ways. If an object has a unique name, use that. For example, instead of an object specifier record that describes “column number 7,” use one that describes “the column named ‘March’”:Keyword    Descriptor type    Data    keyDirectObject    typeObjectSpecifier    (see indented record)    keyAEDesiredClass    typeType    cColumn    keyAEContainer    typeNull    No data    keyAEKeyForm    typeEnumerated    formName    keyAEKeyData    typeLongInteger    "March"    It may be that such an object could also be described in a more complex manner, such as picture 1 of paragraph 302 of chapter 2. But complex descriptions like this should be used only as a last resort if no simpler name is available.In general, be as specific as possible when you identify a selection in a recordable event. The user can generalize as necessary by editing the recorded script.Moving the Selection During RecordingIf recording is turned on and the user makes a selection, performs some action, and then makes a different selection, your application must make a decision: should it record the second selection in absolute terms or relative to the first selection? That is, should the corresponding AppleScript statement beselect insertion location before paragraph 5orselect insertion location before paragraph after selectionBoth statements may be appropriate under different conditions. But suppose that the user had selected paragraph 3 and now selects paragraph 12 or picture 3. Relative addressing doesn’t make sense in these situations because the distance involved is too great or the unit is different. When you can’t be sure of the user’s intent, you should use absolute addressing. You can safely use relative addressing only when the user moves the selection or insertion point by only one unit, as with the arrow keys.Even the use of the arrow keys does not guarantee that you can use relative addressing. For example, suppose that the user has selected cell 5 of row 2 in a spreadsheet and then presses the Left Arrow key three times. In this case, it is best to send Apple events equivalent to the statementselect cell 3 of row 2rather than the statementsselect the cell before selectionselect the cell before selectionselect the cell before selectionUsing relative addressing in certain circumstances may minimize the amount of editing that the user must do after recording a script. However, recordable applications are not required to use relative addressing.Recording Interactions With Dialog BoxesWhen executing scripts, users normally do not want to see dialog boxes. Therefore, your application should record information specified by the user in dialog boxes rather than sending events that would cause the dialog boxes to appear during script execution.For example, suppose a user chooses the Close command and the standard save changes dialog box appears. If the user then clicks Save, your application should send a Close event that corresponds to a statement like this:close document "MyDoc" saving YesAny settings in a dialog box that the user does not change (such as the range of pages to print in a Print dialog box) should not be recorded. How Apple Event Recording WorksScripting components use the Apple Event Manager’s recording mechanism to allow a recording process such as the Script Editor application to control recording into scripts. Script editors and applications that provide their own recording capabilities can take advantage of the recording mechanism via standard scripting component routines. This section describes how scripting components use Apple event recording. You need to read this section if you are developing a scripting component or a script-editing application, or if you want your application to initiate and control Apple event recording. For information about using the standard scripting component routines to turn recording off and on, see “Recording Scripts” on page 10-26.When a user turns on recording for a recording process (for example, by clicking the Record button in Script Editor), the recording process calls a scripting component routine (OSAStartRecording) to turn recording on. The scripting component responds by sending a Start Recording event to the recording process (or any running process on the local computer). Start Recording—begin sending copies of recordable events to recording process        Event class    kCoreEventClass    Event ID    kAEStartRecording    Parameters    None    Description    Sent by a scripting component to the recording process (or to any running process on the local computer), but handled by the Apple Event Manager. The Apple Event Manager responds by turning on recording and sending a Recording On event to all running processes on the local computer. This event must be addressed using a process serial number (PSN); it should never be sent to an address specified as kCurrentProcess.    The recording process should not handle the Start Recording event. Instead, the Apple Event Manager handles it by sending a Recording On event to all running processes on the local computer and sending copies of all subsequent recordable events to the recording process. (The Recording On event is described on page 9-4.) If an application that supports Apple events is launched on a computer for which recording is turned on, the Apple Event Manager will also send it a Recording On event for each recording process that is currently recording.The recording process receives recordable events by means of a Receive Recordable Event handler—that is, a handler installed in the Apple event dispatch table for event class kCoreEventClass and event ID kAENotifyRecording. Scripting components install this handler on behalf of a recording process when recording is first turned on and remove the handler when recording is turned off. Much like a handler for event class typeWildCard and event ID typeWildCard, the Receive Recordable Event handler handles all recordable events sent to the recording process by the Apple Event Manager. Any other Apple events received by the recording process are dispatched in the usual manner. The Receive Recordable Event handler handles recordable events by recording them in the script specified by the recording process’s call to OSAStartRecording.Receive Recordable Event—receive and record a copy of a recordable event        Event class    kCoreEventClass    Event ID    kAENotifyRecording    Parameters    Same as Apple event being recorded    Description    Wildcard event class and event ID handled by a recording process in order to receive and record copies of recordable events sent to it by the Apple Event Manager. Scripting components install a handler for this event on behalf of a recording process when recording is turned on and remove the handler when recording is turned off.    Whenever the Receive Recordable Event handler receives a recordable event, the scripting component sends your application a Recorded Text event. The Recorded Text event contains the decompiled source data for the recorded event in the form of styled text. For a description of the Recorded Text event, see “Recording Scripts” on page 10-26.When a user turns off recording (for example, by clicking Script Editor’s Stop button), the recording process calls a scripting component routine (OSAStopRecording) to turn recording off. The scripting component responds by sending a Stop Recording event to the recording process (or any running process on the local computer). Stop Recording—stop sending copies of recordable events to recording process        Event class    kCoreEventClass    Event ID    kAEStopRecording    Parameters    None    Description    Sent by a scripting component to the recording process (or to any running process on the local computer), but handled by the Apple Event Manager. The Apple Event Manager responds by sending a Recording Off event to all running processes on the local computer. This event must be addressed using a process serial number (PSN); it should never be sent to an address specified as kCurrentProcess.    Like the Start Recording event, the Stop Recording event is handled by the Apple Event Manager. The Apple Event Manager responds by sending a Recording Off event to all running processes on the local computer. (The Recording Off event is described on page 9-4.)Recording continues, and the recording process may continue to receive recordable events, until the Apple Event Manager has notified all running processes that recording has been turned off for that recording process. The Apple Event Manager sends all running processes the Recording Off event with the kAEWaitReply flag set. If an application has stored some data (for instance, keystrokes) that needs to be recorded as an Apple event, this is the last chance for the application to send the event for recording purposes. Recording stops only after the Apple Event Manager returns a reply for the Stop Recording event. The Apple Event Manager supports multiple simultaneous recording processes. A Stop Recording event sent for one of them does not affect the others. If your application needs to know which of several recording processes has turned recording on or off, it can check the keyOriginalAddressAttr attribute of the Recording On or Recording Off event for the address of the recording process.If the Apple Event Manager does not receive a Stop Recording event for a recording process that quits unexpectedly, the applications being recorded don’t find out immediately. When it attempts to send a copy of a recordable event to a recording process that is no longer active, the Apple Event Manager sends a Recording Off event to all running processes on behalf of that recording process and specifies the address for that process in the keyOriginalAddressAttr attribute. If a recording process that quits is the only actively recording process, recording stops completely after the Apple Event Manager has informed all running processes that recording has been turned off.    Listing 10-0Table 10-0Scripting ComponentsContentsConnecting to a Scripting Component10-3Using Scripting Component Routines10-7Compiling and Executing Source Data10-7Saving Script Data10-12Storage Formats for Script Data10-12Resource and File Types for Script Data10-13Loading and Executing Script Data10-14Modifying and Recompiling a Compiled Script10-17Using a Script Context to Handle an Apple Event10-19Supplying a Resume Dispatch Function10-21Supplying an Alternative Active Function10-23Supplying Alternative Create and Send Functions10-24Alternative Create Functions10-24Alternative Send Functions10-25Recording Scripts10-26Writing a Scripting Component10-27Scripting Components Reference10-28Data Structures10-29Required Scripting Component Routines10-30Saving and Loading Script Data10-30Executing and Disposing of Scripts10-33Setting and Getting Script Information10-41Manipulating the Active Function10-45Optional Scripting Component Routines10-46Compiling Scripts10-47Getting Source Data10-51Coercing Script Values10-52Manipulating the Create and Send Functions10-55Recording Scripts10-59Executing Scripts in One Step10-61Manipulating Dialects10-67Using Script Contexts to Handle Apple Events10-71AppleScript Component Routines10-80Initializing AppleScript10-80Getting and Setting Styles for Source Data10-82Generic Scripting Component Routines10-84Getting and Setting the Default Scripting Component10-86Using Component-Specific Routines10-87Routines Used by Scripting Components10-92Manipulating Trailers for Generic Storage Descriptor Records10-92Application-Defined Routines10-94Summary of Scripting Components10-99Pascal Summary10-99Constants10-99Data Types10-105Required Scripting Component Routines10-106Optional Scripting Component Routines10-107AppleScript Component Routines10-110Generic Scripting Component Routines10-110Routines Used by Scripting Components10-111Application-Defined Routines10-111C Summary10-112Constants10-112Data Types10-118Required Scripting Component Routines10-119Optional Scripting Component Routines10-120AppleScript Component Routines10-123Generic Scripting Component Routines10-123Routines Used by Scripting Components10-124Application-Defined Routines10-124Result Codes10-125Scripting ComponentsThis chapter describes how your application can use the Component Manager and scripting components to manipulate and execute scripts.Before you read this chapter, you should read the chapter “Introduction to Scripting” in this book and the chapters about the Apple Event Manager that are relevant to your application. Your application can use the standard scripting component data structures and routines described in this chapter to manipulate scripts written in any scripting language based on the Open Scripting Architecture (OSA). Your application need not be scriptable or recordable to use these routines. However, if your application is scriptable, you can easily make it capable of manipulating and executing scripts that control its own behavior.The first section in this chapter describes how to establish a connection with a scripting component. The next two sections providen    examples of how to use the standard scripting component routinesn    information for developers of scripting componentsThe section “Scripting Components Reference” describes, in addition to the standard scripting component routines, routines provided by the AppleScript component, routines provided by the generic scripting component, and routines called by scripting components.If you are developing a scripting component, you should also read the instructions for creating components in the chapter “Component Manager” in Inside Macintosh: More Macintosh Toolbox. Connecting to a Scripting ComponentTo manipulate and execute scripts written in different scripting languages, your application can use Component Manager routines either to open a connection with each corresponding scripting component individually or to open a single connection with the generic scripting component. The generic scripting component, in turn, attempts to open connections dynamically with the appropriate scripting component for each script. By opening a connection with the generic scripting component, your application can load and execute scripts created by any scripting component that is registered with the Component Manager on the current computer.In general, you should use the generic scripting component to execute and manipulate existing scripts and a specific scripting component when you create new scripts. When you call OSACompile or OSAStartRecording, the generic scripting component examines the script ID to determine which scripting component to use. If instead of a script ID you pass the constant kOSANullScript to these routines, the generic scripting component uses its current default scripting component. Each instance of the generic scripting component has its own default scripting component. From the user’s point of view, the default scripting component corresponds to the scripting language selected in the Script Editor application when the user first creates a new script. The generic scripting component provides routines you can use to get and set the default scripting component, determine which scripting component created a particular script, and perform other useful tasks when you are using multiple scripting components. See the section “Generic Scripting Component Routines,” which begins on page 10-84, for descriptions of these routines.You can use the Component Manager function OpenComponent to open a connection to a scripting component you specify with the component identifier returned by the FindNextComponent function. You can also use the OpenDefaultComponent function to open a scripting component without calling the FindNextComponent function. The OpenComponent and OpenDefaultComponent functions return a component instance. This value identifies your application’s connection to a component. You must supply this value whenever you call a standard scripting component routine. NoteYour application may maintain several connections to a single component, or it may have connections to several components at the same time. Because some scripting components (including the current version of AppleScript) can execute only one script at a time per component instance, a multithreaded application must provide a separate component instance for each script that it compiles or executes while it is simultaneously executing other scripts.uThe Component Manager type code for scripting components that support the routines described in this chapter is 'osa ', and the subtype code for the generic scripting component is 'scpt'.  CONST    kOSAComponentType                                                    = 'osa ';    kOSAGenericscriptingComponentSubtype                                                    = 'scpt';You can open a connection to a scripting component by calling the OpenDefaultComponent function, which returns a component instance. For example, this code opens a connection with the generic scripting component and stores the returned value in an application-defined variable:VAR    gScriptingComponent: ComponentInstance;{open connection to generic scripting component}gScriptingComponent := OpenDefaultComponent(kOSAComponentType,                                  kOSAGenericscriptingComponentSubtype);The generic scripting component in turn opens connections with other scripting components as necessary. The generic scripting component provides routines you can use to get instances of other scripting components when you want to use component-specific routines.It is also possible to open an explicit connection directly with a specific scripting component such as AppleScript:VAR    gScriptingComponent: ComponentInstance;{open connection to AppleScript component}gScriptingComponent := OpenDefaultComponent(kOSAComponentType,                                                            kAppleScriptSubtype);The scripting component routines described in this chapter include eight groups of optional routines that scripting components can support. If necessary, you can use the FindNextComponent function and other Component Manager routines to find a scripting component that supports a specific group of routines or to determine whether a particular scripting component supports a specific group of routines. When you call FindNextComponent, you can provide, in a component description record (a data structure of type ComponentDescription), information about the scripting component you wish to find. The flag bits in the componentFlags field of a component description record provide this information. To find a scripting component that supports a specific group of optional routines, you can specify one or more of these constants in the componentFlags field: CONST    kOSASupportsCompiling                                     = $0002;    kOSASupportsGetSource                                     = $0004;     kOSASupportsAECoercion                                     = $0008;     kOSASupportsAESending                                     = $0010;     kOSASupportsRecording                                     = $0020;     kOSASupportsConvenience                                    = $0040;     kOSASupportsDialects                                     = $0080;     kOSASupportsEventHandling                                     = $0100; The routines that correspond to these constants are described in “Optional Scripting Component Routines,” which begins on page 10-46. NoteAlthough the generic scripting component supports all the scripting component routines represented by these flags, the support it can actually provide depends on the individual components with which it opens connections.uListing 10-1 shows how you can use these flags and the FindNextComponent function to locate a scripting component with specific characteristics. The componentFlags field of the component description record passed to FindNextComponent specifies the flags kOSASupportsCompiling and kOSASupportsGetSource. Because the componentFlagsMask field also specifies these flags, the FindNextComponent function locates a scripting component that supports these routines, regardless of whether or not it supports any others. The FindNextComponent function returns a component identifier that you can then use to get more information about the component or to open it. Listing 10-1    Locating a scripting component that supports specific optional routinesFUNCTION MyConnectToScripting (VAR scriptingComponent: ComponentInstance)                                        : OSAError;VAR    descr, descr2:                     componentDescription;    comp:                    component;    myErr:                     OSErr;BEGIN    {fill in the fields of the component description record}    {first specify component type, subtype, and manufacturer}    descr.componentType := kOSAComponentType; {must be scripting component}    descr.componentSubType := OSType(0); {any OSA component matching spec}    descr.componentManufacturer := OSType(0); {don't care about manufacturer}        {specify component flags and flags mask}    descr.componentFlags := kOSASupportsCompiling + kOSASupportsGetSource;    descr.componentFlagsMask :=         kOSASupportsCompiling + kOSASupportsGetSource;    {locate and open the specified component}    comp := FindNextComponent(Component(0), descr); {0 indicates all }                                                                    { registered components }                                                                    { will be searched}    {check whether the found component is the generic scripting component; }    { if so, skip it and find the next matching component}    myErr := GetComponentInfo(comp, descr2, NIL, NIL, NIL);    IF descr2.componentSubType = kOSAGenericScriptingComponentSubtype THEN        comp := FindNextComponent(comp, descr);    IF comp = 0 THEN         MyConnectToScripting := kComponentNotFound    ELSE     BEGIN        scriptingComponent := OpenComponent(comp);        IF scriptingComponent = 0 THEN             MyConnectToScripting := kComponentNotFound        ELSE             MyConnectToScripting := noErr;    END;END;Because the generic scripting component supports all the standard scripting component routines, the MyConnectToScripting function in Listing 10-1 checks whether the found component is the generic scripting component and, if so, skips it. If for any reason FindNextComponent can’t locate and open a scripting component that supports the specified routines, MyConnectToScripting returns the application-defined constant kComponentNotFound.For more information about locating and opening components with specific characteristics, see the chapter “Component Manager” in Inside Macintosh: More Macintosh Toolbox.  Using Scripting Component RoutinesThe following sections describe how to use some of the standard scripting component routines to manipulate and execute scripts from within your application. For an overview of these routines, see “Manipulating and Executing Scripts,” which begins on page 7-22.The first section describes how to compile and execute source data for a script. The remaining sections describe how you can use scripting component routines to n    get a handle to a compiled script and save the data as a resourcen    load and execute a previously saved and compiled scriptn    load, modify, recompile, and save a compiled scriptn    redirect Apple events to handlers in script contextsn    supply a resume dispatch functionn    supply an alternative active functionn    supply alternative send and create functionsn    record Apple events in compiled scripts and display equivalent source data to the userCompiling and Executing Source DataThis section describes how you can use scripting component routines to obtain source data from users, compile the source data, and execute the compiled script. To create and execute a script using the Script Editor application, a user can type the script, then click the Run button to execute it. Your application can provide similar capabilities.To allow users to write a new script and then execute it, your application must use scripting component routines to compile and execute the source data. To compile source data in a new script with a new script ID, pass the constant kOSANullScript (rather than an existing script ID) in the last parameter of the OSACompile function. This causes OSACompile to return a new script ID in the same parameter.To execute a compiled script, your application must specify, in addition to the script ID for the compiled script, a script context: either the corresponding scripting component’s default context or a script ID for the global context created by that scripting component. Script contexts maintain state information for the execution of scripts. Your application can use script contexts to control the binding of variables used in scripts that it executes. For example, if your application saves its own global context and reuses it every time a script is executed, the binding of variables used in the script is maintained after the user restarts the computer. If your application does not specify a script context, the AppleScript component uses a single default context whenever it executes the script. A scripting component’s default context binds the variables used in the script only until the user quits the application.To specify a scripting component’s default context, pass the constant kOSANullScript in the third parameter of the OSAExecute function; to specify some other global context, pass its script ID in the third parameter.  The MyDoNewScript procedure in Listing 10-2 allows a user to type a script in the appropriate scripting language, then compiles the script, executes the compiled script using a global context provided by the application, and displays the result to the user.The MyDoNewScript procedure begins by calling the OSAScriptingComponentName function to obtain the name of the scripting component specified by gScriptingComponent. This name is passed to the application-defined function MyGetUserScriptText.NoteIf you are using the generic scripting component, you can use the OSAGetDefaultComponent function to get the subtype code for the default scripting component (that is, the scripting component used by the generic scripting component for new scripts). You can then get an instance of the default scripting component by passing its subtype code to OSAGetScriptingComponent. Finally, you can pass that instance to OSAScriptingComponentName to obtain the default scripting component’s name. For more information about the default scripting component and routines you can use with the generic scripting component, see “Generic Scripting Component Routines,” which begins on page 10-84.u The MyGetUserScriptText function displays the name of the scripting language to use in a script-editing window or message box that allows the user to type and execute a new script. After it obtains the source data for the new script, the MyDoNewScript procedure sets the scriptID variable to kOSANullScript. The procedure then passes the source data and scriptID to the OSACompile function. When the script ID passed to OSACompile is kOSANullScript, OSACompile returns, in the same parameter, a new script ID for the resulting compiled script. The MyDoNewScript procedure then passes the new script ID to the OSAExecute function.In addition to a component instance and the script ID for the compiled script to be executed, OSAExecute takes a script ID for a script context and a parameter that contains the mode flags, if any, for script execution. In Listing 10-2, the script ID passed to OSAExecute for the script context is gContext, a global context provided by the application. The constant kOSAModeNull in the next parameter indicates that no mode flags are set for script execution. Listing 10-2    A routine that compiles and executes source dataPROCEDURE MyDoNewScript;VAR    componentName, scriptText, resultText:                                                    AEDesc;    scriptID, resultID        :                                            OSAID;    myOSAErr, ignoreErr:                                                    OSAError;BEGIN    {get the scripting component's name so you can show }    { the user which scripting language to use                                            }    myOSAErr := OSAScriptingComponentName(gScriptingComponent,                                                         componentName);    IF myOSAErr = noErr THEN    BEGIN                {get the user's script text, then compile it}        MyGetUserScriptText(componentName, scriptText);        {to create a new compiled script using the user's script }        { text, pass kOSANullScript to OSACompile as the script ID }        { for the script to be compiled}        scriptID := kOSANullScript;        myOSAErr := OSACompile(gScriptingComponent, scriptText,                                         kOSAModeNull, scriptID);        ignoreErr := AEDisposeDesc(scriptText);    END;    IF myOSAErr = noErr THEN    BEGIN        {execute the script in a global context                        }        myOSAErr := OSAExecute(gScriptingComponent, scriptID,                                         gContext, kOSAModeNull, resultID);        ignoreErr := OSADispose(gScriptingComponent, scriptID);        IF myOSAErr = noErr THEN        BEGIN            {convert the script value returned by OSAExecute to }            { text that can be displayed to the user}            myOSAErr := OSADisplay(gScriptingComponent, resultID,                                         typeChar, kOSAModeNull, resultText);            ignoreErr := OSADispose(gScriptingComponent, resultID);            {show result to user}            MyShowUserResult(resultText);            ignoreErr := AEDisposeDesc(resultText);        END;    END;    IF myOSAErr = errOSAScriptError THEN         MyGetScriptErrorInfo;END;  If script execution is successful, the MyDoNewScript procedure passes the script ID for the resulting script value to the OSADisplay function and calls the MyShowUserResult procedure to display the script value to the user. It also disposes of the script data for the compiled script. If OSAExecute or OSACompile returns the result code errOSAScriptError, the MyDoNewScript procedure calls the MyGetScriptErrorInfo procedure shown in Listing 10-3, which uses the OSAScriptError function to obtain more information about the error.Whenever a scripting component routine returns the result code errOSAScriptError, you can use OSAScriptError to obtain more information about the error. The second parameter of the OSAScriptError function is a constant that specifies the kind of error information to be returned, and the third parameter is the descriptor type for the descriptor record in which the additional error information will be returned.The MyGetScriptErrorInfo procedure in Listing 10-3 calls OSAScriptError three times: once to obtain an error number for either a system error or a scripting component error, once to obtain a text description of the error, and once to obtain error-range information. (For more information about specifying descriptor types for OSAScriptError, see page 10-37.) Finally, the MyGetScriptErrorInfo procedure extracts the starting and ending positions of the error range in the source data and calls the application-defined procedure MyIndicateError to display the error information to the user. Note that your application is responsible for disposing of any descriptor records that are created. You should use the OSACompile and OSAExecute functions as shown in Listing 10-2 if you expect the user to execute the compiled script several times or manipulate it in some other way. If you want to compile and execute a script just one time and don’t need to keep the compiled script in memory after it has been executed, you can use either OSACompileExecute or OSADoScript if these functions are supported by the scripting component you specify.  The OSACompileExecute function takes a component instance, a descriptor record for the source data to be compiled and executed, a context ID, and a modeFlags parameter. It executes the resulting compiled script, disposes of the compiled script, and returns the script ID for the resulting script value. The OSADoScript function takes a component instance, a descriptor record for source data, a context ID, a text descriptor type, and a modeFlags parameter. It compiles and executes the script, returns a descriptor record for the text that corresponds to the resulting script value, and disposes of both the compiled script and the script value. Listing 10-3    A procedure that uses OSAScriptError to get information about an execution errorPROCEDURE MyGetScriptErrorInfo; TYPE    OSErrPtr                    = ^OSErr;    OSErrHandle                    = ^OSErrPtr;VAR    errorMessage:                                        Handle;    startPos, endPos:                                        Integer;    desc, recordDesc:                                         AEDesc;    actualType:                                         DescType;    actualSize:                                        Size;    scriptErr, myErr, ignoreErr:                                        OSErr;    myOSAErr:                                        OSAError; BEGIN    myOSAErr := OSAScriptError(gScriptingComponent,                                     kOSAErrorNumber, typeShortInteger,                                     desc);    scriptErr := OSErrHandle(desc.dataHandle)^^;    ignoreErr := AEDisposeDesc(desc);    myOSAErr := OSAScriptError(gScriptingComponent,                                     kOSAErrorMessage, typeChar, desc);    errorMessage := desc.dataHandle;    myOSAErr := OSAScriptError(gScriptingComponent,                                     kOSAErrorRange, typeOSAErrorRange,                                     desc);    myErr := AECoerceDesc (desc, typeAERecord, recordDesc);    ignoreErr := AEDisposeDesc(desc);    myErr := AEGetKeyPtr(recordDesc, keySourceStart,                                 typeShortInteger, actualType,                                Ptr(@startPos), sizeOf(startPos),                                actualSize);    myErr := AEGetKeyPtr(recordDesc, keySourceEnd,                                 typeShortInteger, actualType,                                Ptr(@endPos), sizeOf(endPos),                                actualSize);    ignoreErr := AEDisposeDesc(recordDesc);    MyIndicateError(scriptErr, errorMessage, startPos, endPos);    {add your own error checking}END;  Saving Script DataAfter creating a new script (or after modifying a previously saved script), a user may want to save it. IMPORTANTYour application should usually save scripts as script data rather       than source data, so that it can reload and execute the data without compiling it.sBefore saving script data, your application can use the OSAStore function to obtain a handle to the data. The OSAStore function takes four input parameters: a component instance that identifies a connection with a scripting component, a script ID for the script data to be stored, a desired descriptor type for the descriptor record to be returned, and a parameter that contains mode flags for use by individual scripting components. It returns a descriptor record for the script data in the fifth parameter.The sections that follow describe the storage formats used by OSAStore and the resource and file types for script data.Storage Formats for Script DataThe descriptor record returned by OSAStore can be either a generic storage descriptor record or a component-specific storage descriptor record:n    A generic storage descriptor record is a special kind of descriptor record of type typeOSAGenericStorage that can be used to store script data created by any scripting component.n    A component-specific storage descriptor record is a descriptor record whose descriptor type is the scripting component subtype value for the scripting component that created the script data. Figure 10-1 illustrates the logical arrangement of a generic storage descriptor record. The descriptor type for a generic storage descriptor record is always typeOSAGenericStorage, and the data referred to by the descriptor record’s handle is always followed by a trailer containing the subtype value for the scripting component that created the script data. Figure 10-1    A generic storage descriptor recordFigure 10-2 illustrates the logical arrangement of a component-specific storage descriptor record. The descriptor type for a component-specific storage descriptor record is the subtype value for the scripting component that created the script data, and the data referred to by the descriptor record’s handle consists of the script data only, with no trailer.Figure 10-2    A component-specific storage descriptor recordIn most cases it is safest to request a handle to script data in the form of a generic storage descriptor record, regardless of the scripting component subtype you pass to the OSAStore function.If the presence of the trailer in a generic storage descriptor record does not interfere with the script data, that data may be used for a wide variety of purposes. For example, if an application uses script IDs to refer to XCMDs, it can call OSAStore with a desired type of typeOSAGenericStorage. The data for the resulting descriptor record consists of the XCMD data followed by a trailer indicating that the script data was created by a scripting component that executes XCMDs. Because the trailer does not interfere with the use of the data, the data may actually be used as an XCMD. Thus, an application can save XCMDs as script data and load and execute them after it has opened a connection with the generic scripting component.However, in some cases adding a trailer to script data may interfere with script execution. For example, suppose the data for a generic storage descriptor record consists of sound data. If a scripting component attempts to play the data from beginning to end as sound data, the trailer will interfere with the resulting sound. In this case, an application must open an explicit connection with a scripting component that can play sounds before saving the data, and then call OSAStore with a desired type that consists of the subtype for that scripting component. Resource and File Types for Script DataWhen the OSAStore function returns a descriptor record of the specified type, your application can save the descriptor record’s data as a resource of type 'scpt' or write it to the data fork of a document. The generic scripting component subtype, the generic storage descriptor type, and the resource type for stored script data all have the same value, though they serve different purposes.CONST    kOSAGenericScriptingComponentSubtype = 'scpt';       kOSAScriptResourceType = kOSAGenericScriptingComponentSubtype        ;    typeOSAGenericStorage = kOSAScriptResourceType;If you want to save script data as a compiled script file or as a script application, save it as a resource of type 'scpt'. The Script Editor application uses resource ID 128, but you can use any valid resource ID. Save the script comment that accompanies the script data as resources of type 'TEXT' and 'styl' with resource ID 1128. (See Figure 7-1 on page 7-6 for an example of a script comment.) Each script file can contain only one script and one script comment. The file type for a compiled script file should be 'osas'. A script application has the file type 'APPL'. If a script application has the creator signature 'aplt', a user can initiate execution of the script it contains by opening it from the Finder. If a script application has the creator signature 'dplt' and contains a user-defined handler for the Open Documents event, a user can initiate execution of the handler by dragging a document or folder icon over the script application’s icon. For more information about the file formats used for script files, see “Script Editors and Script Files” on page 7-6. Script applications must include a 'SIZE' resource and two 'CODE' resources with resource IDs 0 and 1. These resources should be identical to those in the sample script application files provided by Apple Computer, Inc. (except that you can change the size of the memory partition). The 'CODE' resources contain bootstrap code that instantiates the script application component. The script application component, which is registered with the Component Manager at startup, provides the code that loads the script to be run and passes the resulting script ID to the appropriate component.When the user opens a script application from the Finder, the Finder sends the script application an Open Application event. If the scripting component that created the script supports OSAExecuteEvent, the script application component passes the Open Application event and the script ID for the script to OSAExecuteEvent. If the scripting component doesn’t support OSAExecuteEvent, the script application component passes the script ID to OSAExecute.  Loading and Executing Script DataFigure 7-4 on page 7-13 illustrates how an application might execute a script whenever the user presses the Tab key after entering a customer’s name in the “Customer Name” field of an electronic form. To execute a script in response to some user action, your application must be able to load and execute the script data for a compiled script.  This section describes how to load and execute a previously compiled and saved script. The next section, “Modifying and Recompiling a Compiled Script,” describes how to allow a user to modify a compiled script.The OSALoad function takes three input parameters: a component instance that identifies a connection with a scripting component; a descriptor record that contains a handle to the script data to be loaded; and a parameter that contains flags for use by individual scripting components. The function returns, in the fourth parameter, a script ID for the script data. When your application calls OSALoad with a component instance that identifies a connection with the generic scripting component, the generic scripting component in turn uses a connection with the scripting component that created the script data (if that component is registered with the Component Manager on the local computer). If the descriptor record passed to OSALoad is of type typeOSAGenericStorage, the generic scripting component uses the trailer that follows the script data to determine which scripting component to open a connection with. If the descriptor record’s type is the subtype value for some other scripting component, the generic scripting component does not look for a trailer and uses the descriptor type to identify the scripting component. When your application calls OSALoad with a component instance that identifies a connection to any scripting component other than the generic scripting component, that component can load script data only if it was saved as the data for a descriptor record whose descriptor type matches the scripting component’s subtype. In this case, however, your application easily can take advantage of additional routines and other special capabilities provided by that scripting component.It is also possible to call OSALoad using the generic scripting component, then use generic scripting component routines to identify the specific component associated with the loaded script. This allows you to use component-specific routines with a script originally loaded by the generic scripting component. For information about how to do this, see “Routines Used by Scripting Components,” which begins on page 10-92.The OSALoad function returns a script ID for the loaded script data. The generic scripting component always associates the returned script ID with the scripting component that created the script. In this way, it can use a connection with that component again whenever the client application passes the returned script ID to other scripting component routines.Listing 10-4 shows a procedure that loads and executes a script. The MyLoadAndExecute procedure takes a handle to script data that was previously saved using a generic storage descriptor record, obtains a script ID for the equivalent compiled script, executes the compiled script in the default context, and disposes of both the compiled script and the resulting script value ID. If the OSAExecute function returns a script execution error, MyLoadAndExecute obtains further information about the error and displays it to the user. Listing 10-4    A routine that loads and executes script data previously saved using a generic storage descriptor recordPROCEDURE MyLoadAndExecute (scriptData: Handle);VAR    scriptDesc:                                         AEDesc;    scriptID, resultID:                                         OSAID;    scriptText:                                         AEDesc;    myOSAErr, ignoreErr:                                         OSAError;BEGIN    {load the script data}    scriptDesc.descriptorType := typeOSAGenericStorage;    scriptDesc.dataHandle := scriptData;    myOSAErr := OSALoad(gScriptingComponent, scriptDesc,                                 kOSAModeNull, scriptID);    IF myOSAErr = noErr THEN     BEGIN        {execute the resulting compiled script in the default }        { context}                         myOSAErr := OSAExecute(gScriptingComponent, scriptID,                                     kOSANullScript, kOSAModeNull,                                     resultID);        ignoreErr := OSADispose(gScriptingComponent, scriptID);        ignoreErr := OSADispose(gScriptingComponent, resultID);    END;    IF myOSAErr = errOSAScriptError THEN         MyGetScriptErrorInfo;END;The OSALoad function in Listing 10-4 takes a component instance, a generic storage descriptor record for the script data to be loaded, and a parameter that contains the mode flags, if any, for loading the script. In this case the constant kOSAModeNull indicates that no mode flags are set. The OSALoad function returns a script ID for the resulting compiled script, which the MyLoadAndExecute procedure then passes to the OSAExecute function.In addition to a component instance and the script ID for the compiled script to be executed, the OSAExecute function takes a script ID for a context and a parameter that contains the mode flags, if any, for script execution. In Listing 10-4, the script ID passed to OSAExecute for the script context is kOSANullScript, indicating that the scripting component can use its default context to bind any variables. The constant kOSAModeNull in the next parameter indicates that no mode flags are set for script execution. After disposing of the compiled script and the resulting script value, MyLoadAndExecute checks the result code returned by OSAExecute. If it is errOSAScriptError, MyLoadAndExecute calls the MyGetScriptErrorInfo procedure (see Listing 10-3 on page 10-11), which in turn uses the OSAScriptError function to obtain more information about the error.You can use the OSALoad and OSAExecute functions as shown in Listing 10-4 if you expect the user to execute the compiled script several times or manipulate it in some other way. If you want to load and execute a script just one time and don’t need to keep the compiled script in memory after it has been executed, you can use OSALoadExecute instead of OSALoad, OSAExecute, and OSADispose. This function takes a component instance, a descriptor record for the script data to be loaded and executed, a context ID, and a modeFlags parameter. The OSALoadExecute function executes the resulting compiled script, disposes of the compiled script, and returns the script ID for the resulting script data.   Modifying and Recompiling a Compiled ScriptIn addition to loading and executing a previously compiled and saved script as described in the previous section, your application can use the scripting component routines described in this section to decompile a compiled script, display the equivalent source data to users for editing, and recompile the source data after editing is completed. For example, if a user wants to change the script shown in Figure 7-4 on page 7-13 so that it refers to some other database or looks up other information in addition to the customer’s address, the forms application can use scripting component routines to display the compiled script to the user and recompile it after the user has modified it. You can use the OSAGetSource function to obtain the source data for a compiled script. The OSAGetSource function takes a component instance, a script ID for the compiled script, and the desired type of the resulting descriptor record. If you specify a component instance that identifies a connection with the generic scripting component, you can use OSAGetSource to get the source data for any compiled script created by a scripting component that is registered with the Component Manager on the local computer. If you specify a component instance that identifies an explicit connection with a scripting component, you can use OSAGetSource only to get the source data for scripts that were compiled by that scripting component.The MyEditGenericScript procedure in Listing 10-5 shows how you can use the OSAGetSource function with a component instance that identifies a connection to the generic scripting component. The MyEditGenericScript function gets the source data for a compiled script, allows the user to edit it, and recompiles the script so the original script ID refers to the recompiled script data.Listing 10-5    A routine that displays a compiled script for editing and recompiles itPROCEDURE MyEditGenericScript (scriptID: OSAID);VAR    scriptText:                     AEDesc;    myOSAErr:                     OSAError;    ignoreErr:                    OSErr;BEGIN    {first get the source data}    myOSAErr := OSAGetSource(gScriptingComponent, scriptID,                                         typeChar, scriptText);    {call the application's primitive text editor}    MyEditText(scriptText.dataHandle);    {now compile the edited script data in scriptText using }    { the scripting component that originally created it; }    { passing the original script ID to OSACompile causes }    { OSACompile to replace the original script with the new one}     myOSAErr := OSACompile(gScriptingComponent, scriptText,                                     kOSAModeNull, scriptID);    ignoreErr := AEDisposeDesc(scriptText);    IF myOSAErr = errOSAScriptError THEN         MyGetScriptErrorInfo;END; After obtaining the source data for the script, the MyEditGenericScript procedure calls the MyEditText function, which displays the application’s own primitive text editor and allows the user to edit the source data. After the user has finished editing the script, MyEditGenericScript passes the edited text and the script ID for the original compiled script to the OSACompile function, which updates the script ID so that it refers to the modified and recompiled script. The kOSAModeNull constant passed in the third parameter of OSACompile indicates that no mode flags are specified for compilation.If the OSACompile function returns errOSAScriptError, the MyEditGenericScript procedure calls the MyGetScriptErrorInfo procedure shown in Listing 10-3 on page 10-11 to obtain information about the error. After script data has changed as shown in Listing 10-5, your application should save the modified script data. Listing 10-6 shows how this could be done from a function that loads script data, calls the MyEditGenericScript procedure shown in Listing 10-5 to modify and recompile the script, then saves the modified script data.Listing 10-6    A function that loads and modifies script data, then saves it using a generic storage descriptor recordFUNCTION MyLoadAndModifyScriptData (resourceID: Integer)                                                : OSAError;VAR    scriptDesc:                         AEDesc;    storageDescRec:                        AEDesc;    scriptID:                        OSAID;    myOSAErr:                        OSAError;    ignoreErr:                        OSErr;    myHndl:                        Handle;BEGIN    scriptDesc.descriptorType := typeOSAGenericStorage;    scriptDesc.dataHandle := GetResource(kOSAScriptResourceType,                                                         resourceID);    myOSAErr := OSALoad(gGenericScriptingComponent, scriptDesc,                                kOSAModeNull, scriptID);    MyEditGenericScript (scriptID);    myOSAErr := OSAStore(gScriptingComponent, scriptID,                                 typeOSAGenericStorage, kOSAModeNull,                                storageDescRec);    MyWriteResource(storageDescRec.dataHandle, resourceID);    ignoreErr := AEDisposeDesc(scriptDesc);    ignoreErr := AEDisposeDesc(storageDescRec); END;Using a Script Context to Handle an Apple EventThe preceding sections describe how you can load, compile, modify, and execute scripts under circumstances determined by your application. Your application can use these techniques to associate a script with an Apple event object or application object and execute the script when the user manipulates the object in some way.   Another way to execute a script is to use a script context (called a script object in AppleScript) to handle an Apple event. To do this, your application passes both the event and the script context to OSAExecuteEvent or OSADoEvent. You can also associate script contexts with Apple event objects—that is, objects in your application that can be identified by object specifier records. If an Apple event acts on an object with which a script context is associated, your application attempts to use the script context to handle the Apple event.For example, Figure 7-7 on page 7-26 shows how you can use a general Apple event handler to provide initial processing for all Apple events received by your application. Listing 10-7 shows an example of such a handler. You install a general Apple event handler like the one in Listing 10-7 in your application’s special handler dispatch table using the constant keyPreDispatch: myErr := AEInstallSpecialHandler(keyPreDispatch,                                         @MyGeneralAppleEventHandler,                                          FALSE);When it receives an Apple event, the MyGeneralAppleEventHandler function in Listing 10-7 first extracts the event’s direct parameter. It then calls another application-defined function, MyGetAttachedScript, which checks whether the direct parameter contains an object specifier record, calls AEResolve to locate the corresponding Apple event object, and returns a script ID for any script context attached to that object.If a script context is associated with the object, MyGeneralAppleEventHandler passes the script context’s script ID and the Apple event to the OSADoEvent function. Otherwise, MyGeneralAppleEventHandler returns errAEEventNotHandled, which causes the Apple Event Manager to look for an appropriate handler in the application’s Apple event dispatch table or elsewhere using standard Apple event dispatching.The OSADoEvent function in Listing 10-7 takes a component instance that identifies a connection with the generic scripting component. (If it has not already done so, the generic scripting component in turn opens a connection with the scripting component that created the script context.) In addition to the component instance, the Apple event, and the script ID for the script context, OSADoEvent takes a parameter that indicates no mode flags are set and a VAR parameter that contains any reply Apple event returned as a result of handling the event. If the scripting component determines that a script context can’t handle the specified event (for example, if an AppleScript script context doesn’t include statements that handle the event), OSADoEvent returns errAEEventNotHandled. If OSADoEvent attempts to use the script context to handle the event, the function returns a reply event that contains either the resulting script value or, if an error occurred, information about the error.The script context shown in Figure 7-7 contains an AppleScript handler for the Move event. Such handlers exist only as AppleScript statements in a script context and do not have corresponding entries in an application’s Apple event dispatch table. However, a handler in a script context can modify or override the actions performed by an application’s standard Apple event handlers installed in its Apple event dispatch table. The next section, “Supplying a Resume Dispatch Function,” describes how this works.Listing 10-7    A general Apple event handler that uses the OSADoEvent functionFUNCTION MyGeneralAppleEventHandler (event: AppleEvent;                                                  reply: AppleEvent;                                                 refcon: LongInt): OSErr;VAR    dp, resultDesc:                         AEDesc;    scriptID:                        OSAID;    myErr, ignoreErr: OSErr;    myOSAErr:                        OSAError;BEGIN    {get the direct parameter}    myErr := AEGetParamDesc(event, keyDirectObject, typeWildCard,                                     dp);    {get script ID for script context attached to object }    { specified in direct parameter}    IF MyGetAttachedScript(dp, scriptID) THEN         {execute the handler in the script context handler and, if }        { necessary, the default Apple event handler}        myOSAErr := OSADoEvent(gScriptingComponent, event,                                         scriptID,     kOSAModeNull, reply)    ELSE        myOSAErr := errAEEventNotHandled;    ignoreErr := AEDisposeDesc(dp);    MyGeneralAppleEventHandler := OSErr(myOSAErr);END; For more information about OSADoEvent, OSAExecuteEvent, and other routines related to the use of script contexts to handle Apple events, see page 10-71.Supplying a Resume Dispatch FunctionEvery scripting component calls a resume dispatch function during script execution if the script contains the equivalent of an AppleScript continue statement within an event handler. (See Figure 7-7 on page 7-26 for an example.) The resume dispatch function dispatches the event specified by the script directly to the application’s standard handler for that event. Thus, if the script context passed to OSADoEvent in Listing 10-7 specifies that the event passed in the event parameter should be continued—that is, handled by the application’s standard Apple event handler for that event—the scripting component passes the event to the resume dispatch function currently set for that instance of the scripting component. The resume dispatch function attempts to redispatch the event to the handler installed in the application’s Apple event dispatch table for that event. If the call to the resume dispatch function is successful, execution of the script proceeds from the point at which the resume dispatch function was called. If the call to the resume dispatch function is not successful, OSADoEvent returns errAEEventNotHandled in the keyErrorNumber parameter of the reply event. (Other routines that execute scripts, such as OSAExecute or OSAExecuteEvent, return errOSAScriptError in this situation, and a subsequent call to OSAScriptError with kOSAErrorNumber in the selector parameter returns errAEEventNotHandled.)Some scripting components may provide routines that allow your application to set or get the pointer to the resume dispatch function used by a specified instance of a scripting component.TYPE AEHandlerProcPtr = EventHandlerProcPtr;A resume dispatch function takes the same parameters as an Apple event handler. FUNCTION MyResumeDispatch (theAppleEvent: AppleEvent;                                      reply: AppleEvent; refCon: LongInt)                                    :OSErr;To set the resume dispatch function for a scripting component, call OSASetResumeDispatchProc; to get the current dispatch function for a scripting component, call OSAGetResumeDispatchProc. If you do not set a resume dispatch function for a scripting component, it uses standard Apple event dispatching to dispatch the event, starting with the special handler dispatch table.You can install a resume dispatch function using the OSASetResumeDispatchProc function. However, if you are using a general handler similar to that in Listing 10-7 on page 10-21 and you can rely on standard Apple event dispatching to dispatch the event correctly, you don’t need to provide a resume dispatch function. Instead, you can specify kOSAUseStandardDispatch as the resume dispatch function and the constant kOSADontUsePhac as the reference constant when you call OSASetResumeDispatchProc.myErr := OSASetResumeDispatchProc(gScriptingComponent,                     kOSAUseStandardDispatch, kOSADontUsePhac);This causes the Apple Event Manager to redispatch events that would otherwise be passed to a resume dispatch function using standard Apple event dispatching—except that the Apple Event Manager bypasses your application’s special handler dispatch table and thus won’t call your general Apple event handler recursively.When a scripting component calls your resume dispatch function, the A5 register is set up for your application, and your application is the current process.   Supplying an Alternative Active FunctionEvery scripting component calls an active function periodically during script compilation and execution. All scripting components support routines that allow your application to set or get the pointer to the active function used by that scripting component.TYPE OSAActiveProcPtr = ProcPtr;A pointer of type OSAActiveProcPtr points to a MyActiveProc function that takes a reference constant as a parameter. FUNCTION MyActiveProc(refCon: LongInt): OSErr;If you want your application to get time periodically during script compilation and execution for tasks such as spinning the cursor or checking for system-level errors, you should provide an alternative active function that performs those tasks. To set an alternative active function, call OSASetActiveProc; to get the current active function, call OSAGetActiveProc. If you do not set an alternative active function for a scripting component, it uses its own default active function. A scripting component’s default active function allows a user to cancel script execution by pressing Command-period and calls WaitNextEvent to give other processes time.Your alternative active function can in turn call the scripting component’s default active function. To do this, your application can call OSAGetActiveProc before calling OSASetActiveProc to set the alternative active function, then call the default active function directly when necessary. Some scripting components may also supply building-block routines that your application can use to construct an alternative active function.Multithreaded applications may need to give time to other threads while one thread is waiting for the scripting component to complete compilation or execution of a script. You can provide an alternative send function and an idle function that allows threads to be switched (see “Alternative Send Functions” on page 10-25). However, the Apple Event Manager calls an idle function only after an Apple event has been sent, whereas a scripting component calls an active function at regular intervals throughout script compilation and execution. Thus, to give time to multiple threads, you may want to provide an alternative active function in addition to an alternative send function and an idle function. When a scripting component calls your alternative active function, the A5 register is set up for your application, and your application is the current process. Supplying Alternative Create and Send FunctionsEvery scripting component calls a create function whenever it creates an Apple event during script execution, and a send function whenever it sends an Apple event. Scripting components that use Apple events during script compilation, including AppleScript, also call create and send functions during compilation. Some scripting components may provide routines that allow your application to set or get the pointers to the create and send functions used by that scripting component. If your application does not set alternative send and create functions, the scripting component uses the standard Apple Event Manager functions AESend and AECreateAppleEvent, which it calls with its own default parameters.A scripting component that supports the routines you can use to set or get alternative create and send functions has the kOSASupportsAESending bit set in its component description record. For more information about using the Component Manager to find a scripting component that supports specific routines, see “Connecting to a Scripting Component,” which begins on page 10-3.When a scripting component calls your alternative send or create function, the A5 register is set up for your application, and your application is the current process. Alternative Create FunctionsA scripting component that allows your application to set or get its create function uses a pointer to identify the current create function.TYPE AECreateAppleEventProcPtr = ProcPtr;A pointer of type AECreateAppleEventProcPtr points to a MyAECreateProc function that takes the same parameters as the AECreate function plus a reference constant. FUNCTION MyAECreateProc (theAEEventClass: AEEventClass;                                  theAEEventID: AEEventID;                                  target: AEAddressDesc;                                  returnID: Integer;                                  transactionID: LongInt;                                  VAR result: AppleEvent;                                 refCon: LongInt): OSErr; Your application can use an alternative create function to gain control over the creation and addressing of Apple events. This can be useful, for example, if your application needs to add its own transaction code to the event.To set an alternative create function, call OSASetCreateProc; to get the current create function, call OSAGetCreateProc. If you do not set an alternative create function for a scripting component, it uses the standard Apple Event Manager function AECreateAppleEvent, which it calls with its own default parameters.Your alternative create function can in turn call the scripting component’s default create function. To do this, your application can call OSAGetCreateProc before calling OSASetCreateProc to set the alternative create function, then call the default create function directly when necessary. Alternative Send FunctionsA scripting component that allows your application to set or get its send function uses a pointer to identify the current send function. TYPE AESendProcPtr = ProcPtr;A pointer of type AESendProcPtr points to a MyAESendProc function that takes the same parameters as the AECreate function plus a reference constant. FUNCTION MyAESendProc (theAppleEvent: AppleEvent;                               VAR reply: AppleEvent;                               sendMode: AESendMode;                               sendPriority: AESendPriority;                               timeOutInTicks: LongInt;                               idleProc: IdleProcPtr;                               filterProc: EventFilterProcPtr;                              refCon: LongInt): OSErr; Your application can use an alternative send function to perform almost any action instead of or in addition to sending Apple events. For example, it can modify Apple events before sending them, save copies of Apple events before sending them, or substitute some other specialized mechanism for sending Apple events. To set an alternative send function, call OSASetSendProc; to get the current send function, call OSAGetSendProc. If you do not set an alternative send function for a scripting component, it uses the standard Apple Event Manager function AESend, which it calls with its own default parameters.Your alternative send function can in turn call the scripting component’s default send function. To do this, your application can call OSAGetSendProc before calling OSASetSendProc to set the alternative send function, then call the default send function directly when necessary. After a scripting component successfully calls a send function, the scripting component proceeds with script execution. If a call to a send function is not successful, the scripting component returns errOSAScriptError, and a subsequent call to OSAScriptError with kOSAErrorNumber in the selector parameter returns errAEEventNotHandled. Multithreaded applications need to allow other threads to execute while one thread is waiting for the response to an Apple event. You can accomplish this by supplying an idle function for your alternative send function that allows threads to be switched and by setting the kAEQueueReply flag in the sendMode parameter of the send function. However, if the call to the send function specifies the kAENoReply flag, be careful not to override it, because the user may have explicitly requested that no reply be returned or the 'aete' resource may indicate that the application cannot reply to that event. NoteThe Apple Event Manager calls an idle function only after an Apple event has been sent, whereas a scripting component calls an active function at regular intervals throughout script compilation and execution. Thus, to give time to multiple threads, you may want to provide an alternative active function in addition to an alternative send function and an idle function.uSome scripting components (including the current version of AppleScript) can execute only one script at a time per component instance. For this reason, a multithreaded application must provide a separate component instance for each script that it compiles or executes while it is also compiling or executing other scripts.You should follow the rules for setting sendMode flags described in the chapter “Creating and Sending Apple Events” in this book when you set flags for the sendMode parameter of an alternative send function. Keep these additional guidelines in mind:n    If the target application is on the local computer, you can set the kAECanInteract and kAECanSwitchLayer flags.n    If the target application is on the local computer and the user has requested no reply, set the kAENoReply, kAECanInteract, and kAECanSwitchLayer flags.n    If the target application is on a remote computer, set the kAENeverInteract flag and do not set the kAECanSwitchLayer flag.  Recording ScriptsIf you want your application to record Apple events in the form of a compiled script, or if you are writing a script-editing application like Script Editor, you can use the OSAStartRecording and OSAStopRecording functions to start and stop recording into a specified script ID on a single computer. Both functions take a component instance and a script ID for a compiled script. When your application calls OSAStartRecording, the scripting component identified by the component instance sends a Start Recording event to your application and installs a Receive Recordable Event handler in your application’s Apple event dispatch table. When your application calls OSAStopRecording, the scripting component removes the handler.An application acting as a recording process in this manner should not provide a handler for the Start Recording event. Instead, the Apple Event Manager receives the event and responds by sending a Recording On event to all running processes on the local computer. Thereafter, the Apple Event Manager sends copies of subsequent recordable events to the recording process, whose previously installed Receive Recordable Event handler, much like a handler for event class typeWildCard and event ID typeWildCard, handles those recordable events by recording them in the compiled script specified in the call to OSAStartRecording.Whenever the Receive Recordable Event handler receives a recordable event, the scripting component sends your application a Recorded Text event. The Recorded Text event contains the decompiled source data for the recorded event in the form of styled text. Recorded Text—append styled text to script editor window             Event class        kOSASuite    Event ID        kOSARecordedText    Required parameter                Keyword:    keyDirectObject        Descriptor type:    typeStyledText or any other text descriptor type        Data:    Decompiled source data for recorded event    Description        Sent by a scripting component to a recording process for each event recorded after a call to OSAStartRecording      If your want your application to display the source data for recorded events as they are recorded, you must provide a handler for the Recorded Text event. For more information about the Receive Recordable Event handler and Apple event recording, see “How Apple Event Recording Works,” which begins on page 9-35.Writing a Scripting ComponentIt is possible to create scripting components that execute a variety of scripts, including scripts that can be “run” in some sense but do not consist of statements in a scripting language. For example, script data can consist of an XCMD or even sound data that the appropriate scripting component can trigger or play back when it executes the script (see “Storage Formats for Script Data,” which begins on page 10-12). If you are developing a scripting component, you should read the instructions for creating components in the chapter “Component Manager” in Inside Macintosh: More Macintosh Toolbox. Every scripting component should also n    Provide a component name in the scripting component’s component resource that will make sense when displayed to users.n    Support the standard scripting component routines described in “Required Scripting Component Routines,” which begins on page 10-30.n    Support some, all, or none of the optional scripting component routines, as appropriate for the tasks to be performed by the scripting component. These routines are described in “Optional Scripting Component Routines,” which begins on page 10-46.n    Use the three OSA routines OSAGetStorageType, OSAAddStorageType, and OSARemoveStorageType to inspect, add, or remove the trailers appended to script data in generic storage descriptor records. These routines are described in “Manipulating Trailers for Generic Storage Descriptor Records,” which begins on page 10-92.n    Send the Get AETE event when necessary. This event is described in “Handling the Get AETE Event,” which begins on page 8-23.Scripting Components ReferenceThis section describes the standard scripting component data structures and routines your application can use to manipulate and execute scripts. This section also describes additional routines provided by the AppleScript scripting component and three routines called by scripting components.The first section, “Data Structures,” describes the principal data types used by scripting component routines. “Required Scripting Component Routines,” which begins on page 10-30, describes the standard scripting component routines that all scripting components must support. “Optional Scripting Component Routines,” which begins on page 10-46, describes additional standard scripting component routines that scripting components are not required to support. Your application can use the Component Manager to find a scripting component that supports specific optional routines or to determine whether a particular scripting component supports a specific group of routines. For information about how to do this, see “Connecting to a Scripting Component,” which begins on page 10-3. “AppleScript Component Routines,” which begins on page 10-80, describes additional routines supported by the AppleScript component. “Generic Scripting Component Routines” which begins on page 10-84, describes routines you can use to get instances of specific components and perform other useful tasks when you are using multiple scripting components. “Routines Used by Scripting Components,” which begins on page 10-92, describes three routines that all scripting components can use to manipulate trailers for generic storage descriptor records.Data StructuresThis section describes the principal data structures and Component Manager type codes used by the standard scripting component routines. Data structures used by individual routines are described with the appropriate routines in the sections that follow.The Component Manager type code for components that support the standard scripting component routines is 'osa ', and the subtype code for the generic scripting component is 'scpt'.CONST    kOSAComponentType                                                    = 'osa ';    kOSAGenericScriptingComponentSubtype                                                    = 'scpt';Because all results returned by the Component Manager are of type ComponentResult (a long integer), scripting components also define this type for result codes.TYPE    OSAError = ComponentResult;Scripting components keep track of script data in memory by means of script IDs of type OSAID.TYPE OSAID = LongInt; A scripting component assigns a script ID when it creates the associated script data (that is, a compiled script, a script value, a script context, or other kinds of script data supported by a scripting component) or loads it into memory. The scripting routines that create, load, compile, and execute scripts all return script IDs, and your application must pass valid script IDs to the other routines that manipulate scripts. A script ID remains valid until a client application calls OSADispose to reclaim the memory used for the corresponding script data. If the execution of a script does not result in a value, OSAExecute returns the constant kOSANullScript as the script ID. If a client application passes kOSANullScript to the OSAGetSource function instead of a valid script ID, the scripting component should display a null source description (possibly an empty text string). If a client application passes kOSANullScript to OSAStartRecording, the scripting component creates a new compiled script for editing or recording.CONST     kOSANullScript     = 0;Required Scripting Component RoutinesThis section describes the routines that all scripting components must support. Your application can use these routines to save and load script data, execute and dispose of scripts, get script information, and manipulate the active function. “Optional Scripting Component Routines,” which begins on page 10-46, describes additional routines your application can use with scripting components that support them.Saving and Loading Script DataThe OSAStore function takes a script ID and returns a copy of the corresponding script data in the form of a storage descriptor record. You can then save the script data as a resource or write it to the data fork of a document. The OSALoad function takes script data in a storage descriptor record and returns a script ID. OSAStoreYou can use the OSAStore function to get a handle to script data in the form of a storage descriptor record.   FUNCTION OSAStore(scriptingComponent: ComponentInstance;                         scriptID: OSAID;                         desiredType: DescType;                        modeFlags: LongInt;                        VAR resultingScriptData: AEDesc): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptIDThe script ID for the script data for which to obtain a data handle. desiredTypeThe desired type of the descriptor record to be returned. If you want to store the script data in the form used by a generic storage descriptor record, specify typeOSAGenericStorage.modeFlags    Information used by individual scripting components. To avoid setting any mode flags, specify kOSAModeNull. To indicate that only the minimum script data required to run the script should be returned, pass kOSAModePreventGetSource in this parameter. (In this case the script data returned is not identical to the compiled script data and can’t be used to generate source data.) If the scriptID parameter identifies a script context, you can pass kOSAModeDontStoreParent in this parameter to store the script context without storing its parent context.resultingScriptDataThe resulting descriptor record.DESCRIPTIONThe OSAStore function writes script data to a descriptor record so that the data can later be saved in a resource or written to the data fork of a document. You can then reload the data for the descriptor record as a compiled script (although possibly with a different script ID) by passing the descriptor record to OSALoad. If you want the returned script data to be as small as possible and you are sure that you won’t need to display the source data to the user, specify the kOSAModePreventGetSource flag in the modeFlags parameter. If the scriptID parameter identifies a script context and you don’t want the returned script data to include the associated parent context, specify the kOSAModeDontStoreParent flag in the modeFlags parameter.The desired type is either typeOSAGenericStorage (for a generic storage descriptor record) or a specific scripting component subtype value (for a component-specific storage descriptor record).To store either a generic storage descriptor record or a component-specific storage descriptor record with your application’s resources, use 'scpt' as the resource type. The generic scripting component subtype, the generic storage descriptor type, and the resource type for stored script data all have the same value, though they serve different purposes.CONST     kOSAGenericScriptingComponentSubtype = 'scpt';    kOSAScriptResourceType = kOSAGenericScriptingComponentSubtype;    typeOSAGenericStorage = kOSAScriptResourceType;RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    errOSABadStorageType    –1752    Desired type not supported by this scripting component       badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor more information about storage formats for script data, see “Saving Script Data” on page 10-12.For an example of the use of OSAStore, see Listing 10-6 on page 10-19. OSALoadYou can use the OSALoad function to load script data. FUNCTION OSALoad(scriptingComponent: ComponentInstance;                       scriptData: AEDesc;                      modeFlags: LongInt;                      VAR resultingScriptID: OSAID): OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptDataThe descriptor record containing the script data to be loaded.modeFlags    Information used by individual scripting components. To avoid setting any mode flags, specify kOSAModeNull. To indicate that only the minimum script data required to run the script should be loaded, pass kOSAModePreventGetSource in this parameter.resultingScriptIDThe returned script ID for the compiled script.DESCRIPTIONThe OSALoad function loads script data and returns a script ID. The generic scripting component uses the descriptor record in the scriptData parameter to determine which scripting component should load the script. If the descriptor record is of type typeOSAGenericStorage, the generic scripting component uses the trailer at the end of the script data to identify the scripting component. If the descriptor record’s type is the subtype value for another scripting component, the generic scripting component uses the descriptor type to identify the scripting component. If you want the script ID returned by OSALoad to identify only the minimum script data required to run the script and you are sure that you won’t need to display the source data to the user, specify the kOSAModePreventGetSource flag in the modeFlags parameter. Scripting components other than the generic scripting component can load script data only if it has been saved in a descriptor record whose descriptor type matches the scripting component’s subtype.Script data may change after it has been loaded—for example, if your application allows the user to edit a script’s source data. To test whether script data has been modified, pass its script ID to OSAGetScriptInfo. If it has changed, you can call OSAStore again to obtain a handle to the modified script data and save it. RESULT CODESnoErr    0    No error    errOSACorruptData    –1702    Corrupt data    errOSASystemError    –1750    General scripting system error    errOSABadStorageType    –1752    Script data not for this scripting component       errOSADataFormatObsolete    –1758    Data format is obsolete    errOSADataFormatTooNew    –1759    Data format is too new    badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor more information about the way scripting components interpret script data, see “Saving Script Data” on page 10-12. For examples of the use of OSALoad, see Listing 10-4 on page 10-16 and Listing 10-6 on page 10-19.Executing and Disposing of ScriptsTo execute a script, your application must first obtain a valid script ID for a compiled script or script context. You can use either the OSALoad function described in the preceding section or the optional OSACompile function described on page 10-48 to obtain a script ID. The OSAExecute function takes a script ID for a compiled script or script context and returns a script ID for a script value. The OSADisplay function converts a script value to text that your application can later display to the user. If the OSAExecute function returns errOSAScriptError, you can use the OSAScriptError function to get more information about the error.When your application no longer needs the script data associated with a specific script ID, you can use the OSADispose function to release the memory the script data occupies.OSAExecuteYou can use the OSAExecute function to execute a compiled script or a script context. FUNCTION OSAExecute(scriptingComponent: ComponentInstance;                          compiledScriptID: OSAID;                          contextID: OSAID;                          modeFlags: LongInt;                          VAR resultingScriptValueID: OSAID): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).compiledScriptIDThe script ID for the compiled script to be executed.contextID    The script ID for the context to be used during script execution. The constant kOSANullScript in this parameter indicates that the scripting component should use its default context.modeFlags    Information used by individual scripting components. To avoid setting mode flag values, specify kOSAModeNull. Other possible mode flags are listed in the description that follows. resultingScriptValueIDThe script ID for the script value returned.DESCRIPTIONThe OSAExecute function executes the compiled script identified by the compiledScriptID parameter, using the script context identified by the contextID parameter to maintain state information, such as the binding of variables, for the compiled script. After successfully executing a script, OSAExecute returns the script ID for a resulting script value, or, if execution does not result in a value, the constant kOSANullScript.  You can use the OSACoerceToDesc function to coerce the resulting script value to a descriptor record of a desired descriptor type, or the OSADisplay function to obtain the equivalent source data for the script value. You can control the way in which the scripting component executes a script by adding any of these flags to the modeFlags parameter:Flag    Description    kOSAModeNeverInteract    Adds kAENeverInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCanInteract    Adds kAECanInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeAlwaysInteract    Adds kAEAlwaysInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCantSwitchLayer    Prevents use of kAECanSwitchLayer in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    kOSAModeDontReconnect    Adds kAEDontReconnect to sendMode parameter of AESend for events sent when script is executed.    kOSAModeDoRecord    Prevents use of kAEDontRecord in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    If the result code returned by OSAExecute is a general result code, there was some problem in arranging for the script to be run. If the result code is errOSAScriptError, an error occurred during script execution. In this case, you can obtain more detailed error information by calling OSAScriptError.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    errOSAScriptError    –1753    Error occurred during execution    badComponentInstance    $80008001    Invalid component instance     SEE ALSOFor information about the OSAGetSource and OSACoerceToDesc functions, see page 10-51 and page 10-54, respectively. For examples of the use of the OSAExecute function, see Listing 10-2 on page 10-9 and Listing 10-4 on page 10-16.For more information about resume dispatch functions, see “Supplying a Resume Dispatch Function,” which begins on page 10-21, and the description of a resume dispatch function on page 10-97.OSADisplayYou can use the OSADisplay function to convert a script value to text. Your application can then use its own routines to display this text to the user.FUNCTION OSADisplay(scriptingComponent: ComponentInstance;                          scriptValueID: OSAID;                           desiredType: DescType;                          modeFlags: LongInt;                          VAR resultingText: AEDesc): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptValueIDThe script ID for the script value to coerce.desiredTypeThe desired text descriptor type, such as typeChar, for the resulting descriptor record.modeFlags    Information used by individual scripting components. To avoid setting any mode flags, specify kOSAModeNull. To make the resulting text readable by humans only, so that it can’t be recompiled, specify kOSAModeDisplayForHumans.resultingTextThe resulting descriptor record.DESCRIPTIONThe OSADisplay function coerces the script value identified by scriptValueID to a descriptor record of the text type specified by the desiredType parameter, if possible. Valid types include all the standard text descriptor types defined in the Apple Event Registry: Standard Suites, plus any special types supported by the scripting component.Unlike OSAGetSource, OSADisplay can coerce only script values and always produces a descriptor record of a text descriptor type. In addition, if you specify the mode flag kOSAModeDisplayForHumans, the resulting text cannot be recompiled.SPECIAL CONSIDERATIONSIf you want to get a script value in a form that you can display for humans to read, use OSADisplay. If you want the descriptor type of the descriptor record returned in the resultingText parameter to be the same as the descriptor type returned by a scripting component, use OSACoerceToDesc and specify typeWildCard as the desired type.RESULT CODESnoErr    0    No error    errOSACantCoerce    –1700    Desired type not supported by scripting component    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor descriptions of the OSAGetSource and OSACoerceToDesc functions, see page 10-51 and page 10-54, respectively.For an example of the use of OSADisplay, see Listing 10-2 on page 10-9. OSAScriptErrorYou can use the OSAScriptError function to get information about errors that occur during script execution.FUNCTION OSAScriptError(scriptingComponent: ComponentInstance;                                selector: OSType;                                desiredType: DescType;                                VAR resultingErrorDescription: AEDesc)                                : OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).selector    A value that determines what OSAScriptError returns. The value can be one of these constants:                 CONST                    kOSAErrorNumber                                    = 'errn';                    kOSAErrorMessage                                    = 'errs';                    kOSAErrorBriefMessage                                    = 'errb';                    kOSAErrorApp                                    = 'erap';                    kOSAErrorPartialResult                                    = 'ptlr';                    kOSAErrorOffendingObject                                    = 'erob';                    kOSAErrorRange                                    = 'erng';desiredTypeThe desired descriptor type of the resulting descriptor record. The description that follows explains how this is determined by the value passed in the selector parameter. resultingErrorDescriptionThe resulting descriptor record.DESCRIPTIONWhenever the OSAExecute function returns the error errOSAScriptError, you can use the OSAScriptError function to get more specific information about the error from the scripting component that encountered it. (This information remains available only until the next call to the same scripting component.) The information returned by OSAScriptError depends on the value passed in the selector parameter, which also determines the descriptor type you should specify in the desiredType parameter.Constant    Information returned in resultingErrorDescription parameter    kOSAErrorNumber    Error number for either system error or scripting component error. The value of desiredType must be typeShortInteger.     kOSAErrorMessage    Error message associated with error number, including both the name of the application and a description of the error. This constant is sufficient for simple error reporting. The value of desiredType must be typeChar or another text descriptor type.     kOSAErrorBriefMessage    Brief error message associated with error number, excluding the name of the application, any partial result, and the offending object. The value of desiredType must be typeChar or another text descriptor type.     kOSAErrorApp    Either the name or the process serial number (PSN) of the application that received the error, if it was the result of sending an Apple event. The value of desiredType must be typeProcessSerialNumber (for the PSN) or a text descriptor type such as typeChar (for the name).     kOSAErrorPartialResult    Partial result returned after a call to AESend that failed. This consists of a reply parameter that contains some but not all of the information requested.The value of desiredType must be typeBest (for the best type) or typeWildCard (for the default type).     kOSAErrorOffendingObject    An object specifier record for the object that caused the error. The value of desiredType must be typeObjectSpecifier, typeBest, or typeWildCard. For some scripting components, including AppleScript, these three values are equivalent.     kOSAErrorRange    Range of source data in which error occurred. The value of desiredType must be typeOSAErrorRange.      Every scripting component should support calls to OSAScriptError that pass kOSAErrorNumber, kOSAErrorMessage, or kOSAErrorPartialResult in the selector parameter. Some scripting components may also support calls that pass other values in the selector parameter, including kOSAErrorRange, which provides start and end positions delimiting the errant expression in the source data. If the value of the selector parameter is kOSAErrorRange, the value of desiredType must be typeOSAErrorRange. CONST typeOSAErrorRange                                            = 'erng';A descriptor record of type typeOSAErrorRange is an AE record that consists of two descriptor records of typeShortInteger specified by these keywords:CONST    keyOSASourceStart                            = 'srcs'; {start of error range}    keyOSASourceEnd                            = 'srce'; {end of error range}If the value of the selector parameter is kOSAErrorNumber, scripting components may return, in the resultingErrorDescription parameter, one of these general error codes: errOSACantCoerce    –1700    Same as errAECoercionFail; can’t coerce data to requested descriptor type    errOSACantAccess    –1728    Same as errAENoSuchObject; runtime error in resolution of object specifier record    errOSAGeneralError    –2700    General runtime error     errOSADivideByZero    –2701    Attempt to divide by zero    errOSANumericOverflow    –2702    Numeric overflow    errOSACantLaunch    –2703    Can’t launch specified file because it isn’t an application    errOSAAppNotHighLevelEventAware    –2704    Doesn’t respond to Apple events    errOSACorruptTerminology    –2705    The application has a corrupted 'aete' resource    errOSAStackOverflow    –2706    Stack overflow    errOSAInternalTableOverflow    –2707    Internal table overflow     errASDataBlockTooLarge    –2708    Attempt to create a value larger than the allowable size    errOSATypeError    –1703    Same as errAEWrongDataType; wrong descriptor type    errOSAMessageNotUnderstood    –1708    Same as errAEEventNotHandled; event not handled or message not understood    errOSAUndefinedMessage    –1717    Same as errAEHandlerNotFound; handler not found for message    errOSAIllegalIndex    –1728    Same as errAEIllegalIndex; not a valid index    errOSAIllegalRange    –2720    Same as errAEImpossibleRange; range of specified objects not possible    errOSASyntaxError    –2740    General syntax error    errOSASyntaxTypeError    –2741    Syntax error; parser expected one type but found another    errOSATokenTooLong    –2742    Identifier too long            continued    errOSAMissingParameter    –1701    Same as errAEDescNotFound; descriptor record not found    errOSAParameterMismatch    –1721    Same as errAEWrongNumberArgs; wrong number of arguments    errOSADuplicateParameter    –2750    Parameter specified more than once    errOSADuplicateProperty    –2751    Property specified more than once    errOSADuplicateHandler    –2752    Handler defined more than once    errOSAUndefinedVariable    –2753    Undefined variable    errOSAInconsistentDeclarations    –2754    Inconsistent declarations    errOSAControlFlowError    –2755    Control flow error    Although scripting components are not required to support these error codes, their use simplifies error handling for applications that run scripts created by multiple components. If the value of the selector parameter is kOSAErrorNumber, the AppleScript component may return, in the resultingErrorDescription parameter, one of these error codes:errAECantConsiderAndIgnore    –2720    Can’t both consider and ignore a parameter    errASCantCompareMoreThan32k    –2721    Can’t compare text larger than 32K     errASCantCompareMixedScripts    –2722    Can’t compare text from different script systems    errASTerminologyNestingTooDeep    –2760    Tell statements nested too deeply    errASInconsistentNames    –2780    Syntax error; names at beginning and end of handler are inconsistent (AppleScript English dialect only)     SPECIAL CONSIDERATIONSIf you call OSAScriptError using an instance of the generic scripting component, the generic scripting component uses the same instance of a scripting component that it used for the previous call.RESULT CODESnoErr    0    No error    errOSACantCoerce    –1700    Desired type not supported by scripting component    errOSASystemError    –1750    General scripting system error    errOSABadSelector    –1754    Selector value not supported by scripting component     badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor an example of the use of OSAScriptError, see Listing 10-3 on page 10-11.OSADisposeYou can use the OSADispose function to reclaim the memory occupied by script data.FUNCTION OSADispose(scriptingComponent: ComponentInstance;                           scriptID: OSAID): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptID    The script ID for the script data to be disposed of.DESCRIPTIONThe OSADispose function releases the memory assigned to the script data identified by the scriptID parameter. The script ID passed to the OSADispose function is no longer valid if the function returns successfully. A scripting component can then reuse that script ID for other script data. A call to OSADispose returns noErr if the script ID is kOSANullScript, although it does not dispose of anything. RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    badComponentInstance    $80008001    Invalid component instance    Setting and Getting Script InformationThe OSASetScriptInfo function sets various kinds of information about script data, and the OSAGetScriptInfo function returns information about script data. The kind of information these functions set or get depends on constants you pass to the functions.OSASetScriptInfoYou can use OSASetScriptInfo to set information about script data according to the value you pass in the selector parameter.FUNCTION OSASetScriptInfo(scriptingComponent: ComponentInstance;                                  scriptID: OSAID;                                   selector: OSType;                                  value: LongInt): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptID    The script ID for the script data whose information is to be set.selector    A value that determines what kind of information OSASetScriptInfo sets. All scripting components can accept this value:                CONST kOSAScriptIsModified                                                = 'modi';    The kOSAScriptIsModified constant indicates that the count of changes since the script data was loaded or created should be set to the value in the value parameter. The AppleScript component provides limited support for this constant.value    The value to set.DESCRIPTIONThe OSASetScriptInfo function sets script information according to the value you pass in the selector parameter. If you use the kOSAScriptIsModified constant, OSASetScriptInfo sets a value that indicates how many times the script data has been modified since it was created or passed to OSALoad. Some scripting components may provide additional constants.SPECIAL CONSIDERATIONSAlthough you can specify kOSAScriptIsModified when you are using the AppleScript component without generating an error, the current version of AppleScript doesn’t actually set a value for the count of changes since the script data was loaded or created. For more information, see the description of OSAGetScriptInfo that follows.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    errOSABadSelector    –1754    Selector value not supported by scripting component    badComponentInstance    $80008001    Invalid component instance    OSAGetScriptInfoYou can use OSAGetScriptInfo to obtain information about script data according to the value you pass in the selector parameter. FUNCTION OSAGetScriptInfo(scriptingComponent: ComponentInstance;                                  scriptID: OSAID;                                   selector: OSType;                                   VAR result: LongInt): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptID    The script ID for the script data about which to obtain information.selector    A value that determines what kind of information OSAGetScriptInfo returns. The value can be one of these constants:                 CONST        kOSAScriptIsModified                                            = 'modi';                         kOSAScriptIsTypeCompiledScript                                            = 'cscr';                         kOSAScriptIsTypeScriptValue                                            = 'valu';                         kOSAScriptIsTypeScriptContext                                            = 'cntx';                         kOSAScriptBestType                                            = 'best';                         kOSACanGetSource                                            = 'gsrc';     The AppleScript component provides limited support for the constant kOSAScriptIsModified (see page 10-44). In addition to the standard constants, the AppleScript component also supports this constant:                CONST kASHasOpenHandler                                            = 'hsod'; result    The requested information, which you can coerce to the appropriate descriptor type for the value specified in the selector parameter.DESCRIPTIONThe OSAGetScriptInfo function returns various results according to the value you pass in the selector parameter.Value of selector parameter    Information returned in the result parameter(continued)    kOSAScriptIsModified    Long integer that indicates the number of times the script data has been modified since it was passed to OSALoad.    kOSAScriptIsTypeCompiledScript    Boolean value that indicates whether or not the script data is a compiled script.        continued    kOSAScriptIsTypeScriptValue    Boolean value that indicates whether or not the script data is a script value.    kOSAScriptIsTypeScriptContext    Boolean value that indicates whether or not the script data is a script context.    kOSAScriptBestType    A descriptor type that you can pass to OSACoerceToDesc.    kOSACanGetSource    Boolean value that indicates whether the script data can be successfully passed to OSAGetSource.    The AppleScript component also provides this constant for use in the selector parameter.Value of selector parameter    Information returned in the result parameter    kASHasOpenHandler    Boolean value that indicates whether a script context with the specified script ID contains a handler for the Open Documents event. If the script ID doesn’t identify a script context, OSAGetScriptInfo returns the result code errOSAIllegalAccess.    SPECIAL CONSIDERATIONSAlthough you can specify kOSAScriptIsModified when you are using the AppleScript component without generating an error, the current version of AppleScript interprets this request conservatively. The AppleScript component stores script data in a network of interlocking structures, and running a script can cause any of these structures to be modified. If you pass a script ID is to OSAGetScriptInfo with kOSAScriptIsModified as the value of the selector parameter, the AppleScript component returns 1 if there is any possibility that the script data or related structures may have been modified, and 0 if there is no possibility that they have been modified.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    errOSABadSelector    –1754    Selector value not supported by scripting component    badComponentInstance    $80008001    Invalid component instance      Manipulating the Active FunctionThe OSASetActiveProc and OSAGetActiveProc functions allow your application to set or to get a pointer to the active function called periodically by the scripting component during script execution. To get time periodically during script execution for its own purposes, your application can substitute its own active function for use by the scripting component. If you do not specify an active function, the scripting component uses its default active function, which allows a user to cancel script execution. The functions described in this section use the following type for pointers to active functions:TYPE OSAActiveProcPtr = ProcPtr;For more information about active functions, see “Supplying an Alternative Active Function” on page 10-23.OSASetActiveProcYou can use the OSASetActiveProc routine to set the active function that a scripting component calls periodically while executing a script.FUNCTION OSASetActiveProc(scriptingComponent: ComponentInstance;                                  activeProc: OSAActiveProcPtr;                                  refCon: LongInt): OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).activeProcA pointer to the active function to set. If the value of this parameter is NIL, OSASetActiveProc sets the scripting component’s default active function.refCon    A reference constant to be associated with the active function. This parameter can be used for many purposes; for example, it could contain a handle to data used by the active function. RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance    OSAGetActiveProcYou can use the OSAGetActiveProc function to get a pointer to the active function that a scripting component is currently using. FUNCTION OSAGetActiveProc(scriptingComponent: ComponentInstance;                                  VAR activeProc: OSAActiveProcPtr;                                  VAR refCon: LongInt): OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).activeProcThe OSAGetActiveProc function returns in this parameter a pointer to the active function currently set for the specified scripting component.refCon    The OSAGetActiveProc function returns in this parameter the reference constant associated with the active function for the specified scripting component.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error     badComponentInstance    $80008001    Invalid component instance    Optional Scripting Component RoutinesThis section describes eight groups of optional routines that scripting components can support. Your application can use the Component Manager to find a scripting component that supports a specific group of routines or to determine whether a particular scripting component supports a specific group of routines. To specify one or more groups of routines for the Component Manager, use the following constants to set the equivalent bits in the componentFlags field of a component description record:CONST    kOSASupportsCompiling                                     = $0002;    kOSASupportsGetSource                                     = $0004;    kOSASupportsAECoercion                                    = $0008;    kOSASupportsAESending                                     = $0010;    kOSASupportsRecording                                     = $0020;    kOSASupportsConvenience                                    = $0040;    kOSASupportsDialects                                     = $0080;    kOSASupportsEventHandling                                     = $0100;Each of these flags identifies one of the groups of routines that are described in the sections that follow. For information about using these constants to locate scripting components that support specific groups of optional routines, see “Connecting to a Scripting Component,” which begins on page 10-3.Compiling ScriptsScripting components can provide three optional routines that get the name of a scripting component, compile a script, and update a script ID. To obtain the name of a scripting component in a form that you can coerce to text, you can use the OSAScriptingComponentName function. The OSACompile function compiles source data and returns a script ID, and the OSACopyID function updates the script data associated with one script ID with the script data associated with another script ID.A scripting component that supports the routines in this section has the kOSASupportsCompiling bit set in the componentFlags field of its component description record. OSAScriptingComponentNameYou can use the OSAScriptingComponentName function to get the name of a scripting component.FUNCTION OSAScriptingComponentName            (scriptingComponent: ComponentInstance;             VAR resultingScriptingComponentName: AEDesc): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).resultingScriptingComponentNameThe name of the scripting component; or, if the component is the generic scripting component, the name of the default scripting component.DESCRIPTIONThe OSAScriptingComponentName function returns a descriptor record that you can coerce to a text descriptor type such as typeChar. This can be useful if you want to display the name of the scripting language in which the user should write a new script.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor an example of the use of OSAScriptingComponentName, see Listing 10-2 on page 10-9.OSACompileYou can use the OSACompile function to compile the source data for a script and obtain a script ID for a compiled script or a script context.FUNCTION OSACompile (scriptingComponent: ComponentInstance;                             sourceData: AEDesc; modeFlags: LongInt;                            VAR previousAndResultingScriptID: OSAID)                            : OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).sourceDataA descriptor record containing suitable source data for the specified scripting component.modeFlags    Information used by individual scripting components. To avoid setting mode flag values, specify kOSAModeNull. Other possible mode flags are listed in the description that follows. previousAndResultingScriptIDThe script ID for the resulting compiled script. If the value of this parameter on input is kOSANullScript, OSACompile returns a new script ID for the compiled script data. If the value of this parameter on input is an existing script ID, OSACompile updates the script ID so that it refers to the newly compiled script data.DESCRIPTIONYou can pass a descriptor record containing source data suitable for a specific scripting component (usually text) to the OSACompile function to obtain a script ID for the equivalent compiled script or script context. To compile the source data as a script context for use with OSAExecuteEvent or OSADoEvent, you must set the kOSACompileIntoContext flag, and the source data should include appropriate handlers.After you have successfully compiled the script, you can use the returned script ID to refer to the compiled script when you call OSAExecute and other scripting component routines.You can control the way a compiled script is executed by adding any of these flags to the modeFlags parameter:Flag    Description    kOSAModePreventGetSource    Compiled script consists of only the minimum script data required to run the script. It will cause an error if passed to OSAGetSource.    kOSACompileIntoContext    The OSACompile function returns a script context instead of a compiled script.    kOSAModeAugmentContext    Script data associated with script ID passed in previousAndResultingCompiledScriptID is augmented rather than replaced with the new compiled script. Specifying this flag automatically invokes the kOSAModeCompileIntoContext mode flag. If you redefine variables, handlers, and so on that were previously defined in the script context, the new definitions will replace the old ones.    kOSAModeNeverInteract    Adds kAENeverInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCanInteract    Adds kAECanInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeAlwaysInteract    Adds kAEAlwaysInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeDontReconnect    Adds kAEDontReconnect to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCantSwitchLayer    Prevents use of kAECanSwitchLayer in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    kOSAModeDoRecord    Prevents use of kAEDontRecord in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).     SPECIAL CONSIDERATIONSIf you use OSACompile with an instance of the generic scripting component and pass kOSANullScript in the previousAndResultingScriptID parameter, the generic scripting component uses the default scripting component to compile the script. If you’re recompiling a script, specify the original script ID in the previousAndResultingScriptID parameter. The generic scripting component uses the script ID to determine which scripting component it should use to compile the script.RESULT CODESnoErr    0    No error    errOSACantCoerce    –1700    Source data incompatible with scripting component    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    errOSAScriptError    –1753    Source data invalid (syntax error)     badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor an example of the use of OSACompile to update an existing script ID, see Listing 10-5 on page 10-18. For an example of the use of OSACompile to obtain a new script ID, see Listing 10-2 on page 10-9.For more information about the default scripting component associated with any instance of the generic scripting component, see “Generic Scripting Component Routines,” which begins on page 10-84. OSACopyIDYou can use the OSACopyID function to update script data after editing or recording and to perform undo or revert operations on script data.FUNCTION OSACopyID(scriptingComponent    : ComponentInstance;                         fromID: OSAID;                         VAR toID: OSAID): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).fromID    The script ID for script data that you want to be associated with the script ID in the toID parameter.toID    The script ID for the script data to be replaced. If the value of this parameter is kOSANullScript, the OSACopyID function returns a new script ID.DESCRIPTIONThe OSACopyID function replaces the script data identified by the script ID in the toID parameter with the script data identified by the script ID in the fromID parameter.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    badComponentInstance    $80008001    Invalid component instance    Getting Source DataThe OSAGetSource function returns the source data that corresponds to the script data identified by a script ID. The source data it returns can in turn be passed to OSACompile.A scripting component that supports the OSAGetSource function has the kOSASupportsGetSource bit set in the componentFlags field of its component description record. OSAGetSourceYou can use the OSAGetSource function to decompile the script data identified by a script ID and obtain the equivalent source data.FUNCTION OSAGetSource(scriptingComponent: ComponentInstance;                             scriptID: OSAID;                              desiredType: DescType;                             VAR resultingSourceData: AEDesc): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptID    The script ID for the script data to decompile. If you pass kOSANullScript in this parameter, OSAGetSource returns a null source description (such as an empty text string). desiredTypeThe desired descriptor type of the resulting descriptor record, or typeBest if any type will do.resultingSourceDataThe resulting descriptor record.DESCRIPTIONThe OSAGetSource function decompiles the script data identified by the specified script ID and returns a descriptor record containing the equivalent source data. The source data returned need not be exactly the same as the source data originally passed to OSACompile—for example, white space and formatting might be different—but it should be a reasonable equivalent suitable for user viewing and editing. The difference between OSACoerceToDesc and OSAGetSource is that OSAGetSource creates source data that can be displayed to a user or compiled and executed to generate an appropriate value, whereas OSACoerceToDesc actually returns the value. For example, if you call OSAGetSource and specify a string value, it returns the text surrounded by quotation marks (so that it can be properly compiled). If you call OSACoerceToDesc and specify a string value, it simply returns the text.The main difference between OSADisplay and OSAGetSource is that OSAGetSource can coerce any form of script data using a variety of descriptor types, whereas OSADisplay can coerce only script values and always produces a descriptor record of a text descriptor type. RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    errOSASourceNotAvailable    –1756    Source data not available    badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor an example of the use of OSAGetSource, see Listing 10-5 on page 10-18.Coercing Script ValuesScripting components can provide support for two optional routines, OSACoerceFromDesc and OSACoerceToDesc, which coerce data in a descriptor record to a script value and coerce a script value to data in a descriptor record, respectively.A scripting component that supports the routines in this section has the kOSASupportsAECoercion bit set in the componentFlags field of its component description record.OSACoerceFromDescYou can use the OSACoerceFromDesc function to obtain the script ID for a script value that corresponds to the data in a descriptor record.FUNCTION OSACoerceFromDesc                        (scriptingComponent: ComponentInstance;                         scriptData: AEDesc; modeFlags: LongInt;                         VAR resultingScriptValueID: OSAID): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptDataA descriptor record containing the script data to be coerced.modeFlags    Information used by individual scripting components. To avoid setting mode flag values, specify kOSAModeNull. If the scriptData parameter contains an Apple event, you can use any of the mode flags listed in the description that follows. resultingScriptValueIDThe resulting script ID for a script value.DESCRIPTIONThe OSACoerceFromDesc function coerces the descriptor record in the scriptData parameter to the equivalent script value and returns a script ID for that value. If you pass OSACoerceFromDesc an Apple event in the scriptData parameter, it returns a script ID for the equivalent compiled script in the resultingScriptValueID parameter. In this case you can specify any of the modeFlags values used by OSACompile to control the way the compiled script is executed:Flag    Description(continued)    kOSAModePreventGetSource    Compiled script consists of only the minimum script data required to run the script. It will cause an error if passed to OSAGetSource.    kOSACompileIntoContext    The OSACoerceFromDesc function returns a script context instead of a compiled script.    kOSAModeNeverInteract    Adds kAENeverInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCanInteract    Adds kAECanInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeAlwaysInteract    Adds kAEAlwaysInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeDontReconnect    Adds kAEDontReconnect to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCantSwitchLayer    Prevents use of kAECanSwitchLayer in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    kOSAModeDoRecord    Prevents use of kAEDontRecord in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).     SPECIAL CONSIDERATIONSIf you call OSACoerceFromDesc using an instance of the generic scripting component, the generic scripting component uses the default scripting component to perform the coercion.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error     badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor more information about the default scripting component associated with any instance of the generic scripting component, see “Generic Scripting Component Routines,” which begins on page 10-84. OSACoerceToDescYou can use the OSACoerceToDesc function to coerce a script value to a descriptor record of a desired descriptor type.FUNCTION OSACoerceToDesc(scriptingComponent: ComponentInstance;                                 scriptValueID: OSAID;                                  desiredType: DescType;                                 modeFlags: LongInt;                                 VAR result: AEDesc): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptValueIDThe script ID for the script value to coerce.desiredTypeThe desired descriptor type of the resulting descriptor record.modeFlags    Information used by individual scripting components. To avoid setting mode flag values, specify kOSAModeNull. result    The resulting descriptor record.DESCRIPTIONThe OSACoerceToDesc function coerces the script value identified by scriptValueID to a descriptor record of the type specified by the desiredType parameter, if possible. Valid types include all the standard descriptor types defined in the Apple Event Registry: Standard Suites, plus any special types supported by the scripting component.SPECIAL CONSIDERATIONSIf you want the descriptor type of the descriptor record returned in the result parameter to be the same as the descriptor type returned by a scripting component, use OSACoerceToDesc and specify typeWildCard as the desired type. If you want to get a script value in a form that you can display for humans to read, use OSADisplay. RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor a description of OSADisplay, see page 10-35.  Manipulating the Create and Send FunctionsSome scripting components provide routines that allow your application to set or get pointers to the create and send functions used by the scripting component when it sends and creates Apple events during script execution. If you do not set the pointers that specify these functions, the scripting component uses the standard AECreateAppleEvent and AESend functions with default parameters.To gain control over the creation and addressing of Apple events, your application can provide its own create function for use by scripting components. To set a new create function, call the OSASetCreateProc function; to get the current create function, call OSAGetCreateProc.The send function provided by your application can perform almost any action instead of or in addition to sending Apple events; for example, it can be used to facilitate concurrent script execution. To set a new send function, call the OSASetSendProc function; to get the current send function, call OSAGetSendProc.The functions described in this section use the following types for pointers to the create and send functions:TYPE     AESendProcPtr = ProcPtr;    AECreateAppleEventProcPtr = ProcPtr;For more information about create and send functions, see “Supplying Alternative Create and Send Functions,” which begins on page 10-24. Scripting components that support manipulation of the create and send functions also support the OSASetDefaultTarget function, which allows you to set the default application to which Apple events are sent.A scripting component that supports the functions described in this section has the kOSASupportsAESending bit set in the componentFlags field of its component description record.OSASetCreateProcYou can use the OSASetCreateProc function to specify a create function that a scripting component should use instead of the Apple Event Manager’s AECreateAppleEvent function when creating Apple events.FUNCTION OSASetCreateProc(scriptingComponent: ComponentInstance;                                  createProc: AECreateAppleEventProcPtr;                                  refCon: LongInt): OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).createProcA pointer to the create function to set.refCon    A reference constant.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance    OSAGetCreateProcYou can use the OSAGetCreateProc function to get a pointer to the create function that a scripting component is currently using to create Apple events.FUNCTION OSAGetCreateProc(scriptingComponent: ComponentInstance;                            VAR createProc: AECreateAppleEventProcPtr;                            VAR refCon: LongInt): OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).createProcThe OSAGetCreateProc function returns, in this parameter, a pointer to the create function currently set for the specified scripting component.refCon    The OSAGetCreateProc function returns, in this parameter, the reference constant associated with the create function for the specified scripting component.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance    OSASetSendProcYou can use the OSASetSendProc function to specify a send function that a scripting component should use instead of the Apple Event Manger’s AESend function when sending Apple events. FUNCTION OSASetSendProc(scriptingComponent: ComponentInstance;                                sendProc: AESendProcPtr;                                 refCon: LongInt): OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).sendProc    A pointer to the send function to set.refCon    A reference constant.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance    OSAGetSendProcYou can use the OSAGetSendProc function to get a pointer to the send function that a scripting component is currently using.FUNCTION OSAGetSendProc(scriptingComponent: ComponentInstance;                                VAR sendProc: AESendProcPtr;                                VAR refCon: LongInt): OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).sendProc    The OSAGetSendProc function returns, in this parameter, a pointer to the send function currently set for the specified scripting component.refCon    The OSAGetSendProc function returns, in this parameter, the reference constant associated with the send function for the specified scripting component.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance    OSASetDefaultTargetYou can use the OSASetDefaultTarget function to set the default target application for Apple events.FUNCTION OSASetDefaultTarget                                (scriptingComponent: ComponentInstance;                                 target: AEAddressDesc): OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).target    The address of the application that is being made the default application. If you pass a null descriptor record in this parameter, the scripting component treats the current process as the default target.DESCRIPTIONThe OSASetDefaultTarget function establishes the default target application for Apple event sending and the default application from which the scripting component should obtain terminology information. For example, AppleScript statements that refer to the default application do not need to be enclosed in tell/end tell statements. If your application doesn’t call this function, or if you pass a null descriptor record in the target parameter, the scripting component treats the current process (that is, the application that calls OSAExecute or related routines) as the default target application.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance    Recording ScriptsThe OSAStartRecording function turns on the Apple Event Manager’s recording mechanism and specifies a script in which subsequent recordable Apple events are recorded. The scripting component sends the recording process (for example, a script editor) a Recorded Text event that contains the decompiled equivalent for each recordable event it receives. The script editor can then display the decompiled script in a script editor window if a window for that script is currently open. Recording continues until a call to OSAStopRecording turns recording off. Script editors use these routines to allow users to control recording. Any application can use these routines to provide its own script-recording interface.For more information about the Apple event recording mechanism, see the chapter “Recording Apple Events” in this book. For more information about the Recorded Text event, see “Recording Scripts” on page 10-26.A scripting component that supports the functions described in this section has the kOSASupportsRecording bit set in the componentFlags field of its component description record.OSAStartRecordingYou can use the OSAStartRecording routine to turn on Apple event recording and record subsequent Apple events in a compiled script.FUNCTION OSAStartRecording                        (scriptingComponent: ComponentInstance;                         VAR compiledScriptToModifyID: OSAID): OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).compiledScriptToModifyIDThe script ID for the compiled script in which to record.DESCRIPTIONThe OSAStartRecording routine turns on Apple event recording. Subsequent Apple events are recorded (that is, appended to any existing statements) in the compiled script specified by the compiledScriptToModifyID parameter. If the source data for the compiled script is currently displayed in a script editor’s window, the script editor’s handler for the Recorded Text event should display each new statement in the window as it is recorded. Users should not be able to change a script that is open in a script editor window while it is being recorded into.To record into a new compiled script, pass the constant kOSANullScript in the compiledScriptToModifyID parameter. The scripting component should respond by creating a new compiled script and recording into that.SPECIAL CONSIDERATIONSThe generic scripting component uses its default scripting component to create and record into a new compiled script.RESULT CODESnoErr    0    No error    errAERecordingIsAlreadyOn    –1732    Attempt to turn recording on when it is already on for a recording process    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor more information about the default scripting component associated with any instance of the generic scripting component, see “Generic Scripting Component Routines,” which begins on page 10-84. OSAStopRecordingYou can use the OSAStopRecording function to turn off Apple event recording.FUNCTION OSAStopRecording(scriptingComponent: ComponentInstance;                                  compiledScriptID: OSAID): OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).compiledScriptIDA script ID for the compiled script into which Apple events are being recorded.DESCRIPTIONThe OSAStopRecording function turns off recording. If the script is not currently open in a script editor window, the compiledScriptToModifyID parameter supplied to OSAStartRecording is then augmented to contain the newly recorded statements. If the script is currently open in a script editor window, the script data that corresponds to the compiledScriptToModifyID parameter supplied to OSAStartRecording is updated continuously until the client application calls OSAStopRecording. If the compiled script identified by the script ID in the compiledScriptID parameter is not being recorded into or recording is not currently on, OSAStopRecording returns noErr.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    badComponentInstance    $80008001    Invalid component instance     Executing Scripts in One StepThe OSALoadExecute, OSACompileExecute, and OSADoScript functions combine the capabilities of several other scripting component functions so that an application can execute a script in a single step. You can use these functions if you know that the script data to be executed will be executed only once.A scripting component that supports the functions described in this section has the kOSASupportsConvenience bit set in the componentFlags field of its component description record. OSALoadExecuteYou can use the OSALoadExecute function to load and execute a script in a single step rather than calling OSALoad and OSAExecute.FUNCTION OSALoadExecute (scriptingComponent: ComponentInstance;                                 scriptData: AEDesc;                                  contextID: OSAID; modeFlags: LongInt;                                  VAR resultingScriptValueID: OSAID)                                  : OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptDataThe descriptor record identifying the script data to be loaded and executed.contextID    The script ID for the context to be used during script execution. The constant kOSANullScript in this parameter indicates that the scripting component should use its default context.modeFlags    Information used by individual scripting components. To avoid setting mode flag values, specify kOSAModeNull. Other possible mode flags are listed in the description that follows. resultingScriptValueIDThe script ID for the script value returned.DESCRIPTIONThe OSALoadExecute function loads script data and executes the resulting compiled script, using the script context identified by the contextID parameter to maintain state information such as the binding of variables. After successfully executing the script, OSALoadExecute disposes of the compiled script and returns either the script ID for the resulting script value or, if execution does not result in a value, the constant kOSANullScript. You can control the way in which the scripting component executes a script by adding any of these flags to the modeFlags parameter:Flag    Description(continued)    kOSAModeNeverInteract    Adds kAENeverInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCanInteract    Adds kAECanInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeAlwaysInteract    Adds kAEAlwaysInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCantSwitchLayer    Prevents use of kAECanSwitchLayer in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    kOSAModeDontReconnect    Adds kAEDontReconnect to sendMode parameter of AESend for events sent when script is executed.    kOSAModeDoRecord    Prevents use of kAEDontRecord in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    If the result code returned by OSALoadExecute is a general result code, there was some problem in arranging for the script to be run. If the result code is errOSAScriptError, an error occurred during script execution. In this case, you can obtain more detailed error information by calling OSAScriptError.RESULT CODESnoErr    0    No error    errOSACorruptData    –1702    Same as errAECorruptData    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    errOSABadStorageType    –1752    Script data not for this scripting component    errOSAScriptError    –1753    Error occurred during execution    errOSADataFormatObsolete    –1758    Data format is obsolete    errOSADataFormatTooNew    –1759    Data format is too new    badComponentInstance    $80008001    Invalid component instance    OSACompileExecuteYou can use the OSACompileExecute routine to compile and execute a script in a single step rather than calling OSACompile and OSAExecute.FUNCTION OSACompileExecute                         (scriptingComponent: ComponentInstance;                         sourceData: AEDesc;                          contextID: OSAID; modeFlags: LongInt;                          VAR resultingScriptValueID: OSAID): OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).sourceDataA descriptor record identifying suitable source data for the specified scripting component.contextID    The script ID for the context to be used during script execution. The constant kOSANullScript in this parameter indicates that the scripting component should use its default context.modeFlags    Information used by individual scripting components. To avoid setting mode flag values, specify kOSAModeNull. Other possible mode flags are listed in the description that follows. resultingScriptValueIDThe script ID for the script value returned.DESCRIPTIONThe OSACompileExecute function compiles source data and executes the resulting compiled script, using the script context identified by the contextID parameter to maintain state information such as the binding of variables. After successfully executing the script, OSACompileExecute disposes of the compiled script and returns either the script ID for the resulting script value or, if execution does not result in a value, the constant kOSANullScript.You can control the way in which the scripting component executes a script by adding any of these flags to the modeFlags parameter:Flag    Description    kOSAModeNeverInteract    Adds kAENeverInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCanInteract    Adds kAECanInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeAlwaysInteract    Adds kAEAlwaysInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCantSwitchLayer    Prevents use of kAECanSwitchLayer in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    kOSAModeDontReconnect    Adds kAEDontReconnect to sendMode parameter of AESend for events sent when script is executed.    kOSAModeDoRecord    Prevents use of kAEDontRecord in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    If the result code returned by OSACompileExecute is a general result code, there was some problem in arranging for the script to be run. If the result code is errOSAScriptError, an error occurred during script execution. In this case, you can obtain more detailed error information by calling OSAScriptError.RESULT CODESnoErr    0    No error    errOSACantCoerce    –1700    Data could not be coerced to the requested data type    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    errOSAScriptError    –1753    Source data invalid (syntax error) or an execution error occurred    badComponentInstance    $80008001    Invalid component instance    OSADoScriptYou can use the OSADoScript routine to compile and execute a script and convert the resulting script value to text in a single step rather than calling OSACompile, OSAExecute, and OSADisplay.FUNCTION OSADoScript (scriptingComponent: ComponentInstance;                             sourceData: AEDesc;                              contextID: OSAID; desiredType: DescType;                              modeFlags: LongInt;                              VAR resultingText: AEDesc): OSAError;scriptingComponent A component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).sourceDataA descriptor record identifying suitable source data for the specified scripting component.contextID    The script ID for the context to be used during script execution. The constant kOSANullScript in this parameter indicates that the scripting component should use its default context.desiredTypeThe desired text descriptor type, such as typeChar, for the resulting descriptor record.modeFlags    Information used by individual scripting components. To avoid setting mode flag values, specify kOSAModeNull. Other possible mode flags are listed in the description that follows. resultingTextThe resulting descriptor record.DESCRIPTIONCalling the OSADoScript function is equivalent to calling OSACompile followed by OSAExecute and OSADisplay. After compiling the source data, executing the compiled script using the script context identified by the contextID parameter, and returning the text equivalent of the resulting script value in the resultingText parameter, OSADoScript disposes of both the compiled script and the resulting script value.You can control the way in which the scripting component executes the script by adding any of these flags to the modeFlags parameter:Flag    Description    kOSAModeNeverInteract    Adds kAENeverInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCanInteract    Adds kAECanInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeAlwaysInteract    Adds kAEAlwaysInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCantSwitchLayer    Prevents use of kAECanSwitchLayer in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    kOSAModeDontReconnect    Adds kAEDontReconnect to sendMode parameter of AESend for events sent when script is executed.    kOSAModeDoRecord    Prevents use of kAEDontRecord in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    kOSAModeDisplayForHumans    Resulting text is readable by humans only and cannot be recompiled by OSACompile.    If the result code returned by OSADoScript is a general result code, there was some problem in arranging for the script to be run. If the result code is errOSAScriptError, an error occurred during script execution, and the resultingText parameter contains the error message associated with the error. In this case, you can obtain more detailed error information by calling OSAScriptError.RESULT CODESnoErr    0    No error    errOSACantCoerce    –1700    Data could not be coerced to the requested data type    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    errOSAScriptError    –1753    Source data invalid (syntax error) or an execution error occurred    badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor more information about resume dispatch functions, see “Supplying a Resume Dispatch Function,” which begins on page 10-21, and the description of a resume dispatch function on page 10-97.Manipulating DialectsScripting components that provide several dialects may provide five functions that allow you to switch between dialects dynamically and get information about currently available dialects. The codes for specific dialects are provided by the scripting component.The OSASetCurrentDialect function sets the current dialect, and the OSAGetCurrentDialect function gets the dialect code for the current dialect. The OSAAvailableDialectCodeList function returns a list of codes for a scripting component’s dialects. You can pass any of these codes to the OSAGetDialectInfo function to get information about a specific dialect.Instead of using the OSAAvailableDialectCodeList and OSAGetDialectInfo functions, you can use the OSAAvailableDialects function to get a descriptor list that contains information about all of the currently available dialects for a scripting component. However, it is usually more convenient to get information about just one dialect.A scripting component that supports the functions described in this section has the kOSASupportsDialects bit set in the componentFlags field of its component description record.OSASetCurrentDialectYou can use the OSASetCurrentDialect function to set the current dialect for a scripting component.FUNCTION OSASetCurrentDialect                                (scriptingComponent: ComponentInstance;                                  dialectCode: Integer): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).dialectCodeThe code for the dialect to be set.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSANoSuchDialect    –1757    Invalid dialect code    badComponentInstance    $80008001    Invalid component instance    OSAGetCurrentDialectYou can use the OSAGetCurrentDialect function to get the dialect code for the dialect currently being used by a scripting component.FUNCTION OSAGetCurrentDialect                        (scriptingComponent            : ComponentInstance;                         VAR resultingDialectCode    : Integer): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).resultingDialectCodeThe OSAGetCurrentDialect function returns, in this parameter, the code for the current dialect of the specified scripting component.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSANoSuchDialect    –1757    Invalid dialect code    badComponentInstance    $80008001    Invalid component instance    OSAAvailableDialectCodeListYou can use the OSAAvailableDialectCodeList function to obtain a descriptor list containing dialect codes for each of a scripting component’s currently available dialects. FUNCTION OSAAvailableDialectCodeList                    (scriptingComponent                : ComponentInstance;                     VAR resultingDialectCodeList    : AEDesc): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).resultingDialectCodeListThe returned descriptor list. DESCRIPTIONEach item in the descriptor list returned by OSAAvailableDialectCodeList is a descriptor record of descriptor type typeInteger containing a dialect code for one of the specified scripting component’s currently available dialects. Dialect codes are defined by individual scripting components. You can pass any dialect code you obtain using OSAAvailableDialectCodeList to OSAGetDialectInfo to get information about the corresponding dialect.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error     badComponentInstance    $80008001    Invalid component instance    OSAGetDialectInfoYou can use the OSAGetDialectInfo function to get information about a specified dialect provided by a specified scripting component.OSAGetDialectInfo (scriptingComponent: ComponentInstance;                          dialectCode: Integer; selector: OSType;                         VAR resultingDialectInfo: AEDesc): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).dialectCodeA code for the dialect about which you want information. You can obtain a list of a scripting component’s dialect codes by calling OSAAvailableDialectCodeList. selector    A constant that indicates what kind of information you want OSAGetDialectInfo to return in the result parameter. This constant determines the descriptor type for the descriptor record returned. See the description that follows for a list of the standard constants you can specify in this parameter.resultingDialectInfoA descriptor record containing the requested information. The descriptor record’s descriptor type corresponds to the constant specified in the selector parameter. DESCRIPTIONAfter you obtain a list of dialect codes by calling OSAAvailableDialectCodeList, you can pass any of those codes to OSAGetDialectInfo to get information about the corresponding dialect. The descriptor type of the descriptor record returned by OSAGetDialectInfo depends on the constant specified in the selector parameter. All scripting components support the following constants for this parameter:CONST    keyOSADialectName                                 = 'dnam';            {used with descriptor record }                                                { of any text type, such as }                                                { type typeChar}    keyOSADialectLangCode                                 = 'dlcd';            {used with descriptor record }                                                { of type typeShortInteger}    keyOSADialectScriptCode                     = 'dscd';                        {used with descriptor record }                                                { of type typeShortInteger}Individual scripting components may allow you to specify additional constants.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSABadSelector    –1754    Invalid selector    errOSANoSuchDialect    –1757    Invalid dialect code    badComponentInstance    $80008001    Invalid component instance    OSAAvailableDialectsYou can use the OSAAvailableDialects function to obtain a descriptor list containing information about each of the currently available dialects for a scripting component.  FUNCTION OSAAvailableDialects                    (scriptingComponent                : ComponentInstance;                     VAR resultingDialectInfoList    : AEDesc): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).resultingDialectInfoListThe returned descriptor list. DESCRIPTIONEach item in the list returned by OSAAvailableDialects is an AE record of descriptor type typeOSADialectInfo.CONST typeOSADialectInfo                     = 'difo';Each descriptor record in the descriptor list contains, at a minimum, four keyword-specified descriptor records with the following keywords:CONST    keyOSADialectName                                 = 'dnam';            {used with descriptor record }                                                { of any text type, such as }                                                { type typeChar}    keyOSADialectCode                                 = 'dcod';            {used with descriptor record }                                                { of type typeShortInteger}    keyOSADialectLangCode                                 = 'dlcd';            {used with descriptor record }                                                { of type typeShortInteger}    keyOSADialectScriptCode                     = 'dscd';                        {used with descriptor record }                                                { of type typeShortInteger}Rather than calling OSAAvailableDialects to obtain complete dialect information for a scripting component, it is usually more convenient to call OSAAvailableDialectCodeList to get a list of codes for a scripting component’s dialects, then call OSAGetDialectInfo to get information about the specific dialect you’re interested in.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error      badComponentInstance    $80008001    Invalid component instance    Using Script Contexts to Handle Apple EventsThe optional routines described in this section allow your application to use script contexts to handle Apple events. One way to do this is to install a general Apple event handler in your application’s special handler dispatch table. The general Apple event handler provides initial handling for every Apple event received by your application. (For an example of such a handler, see “Using a Script Context to Handle an Apple Event” on page 10-19.)The general Apple event handler extracts the event’s direct parameter, obtains a script ID for the script context associated with the object described in the direct parameter, and passes the Apple event and the script ID to either OSAExecuteEvent or OSADoEvent. The main difference between these two functions is that OSAExecuteEvent returns a script ID for the resulting script value, whereas OSADoEvent returns a reply Apple event that includes either the resulting script value or information about any errors that occurred.If the scripting component determines that a script context can’t handle the specified event (for example, if an AppleScript script context doesn’t include statements that handle the event), OSAExecuteEvent and OSADoEvent return errAEEventNotHandled. This causes the Apple Event Manager to look for an appropriate handler in the application’s Apple event dispatch table or elsewhere, using standard Apple event dispatching. If the scripting component determines that a script context passed to OSAExecuteEvent or OSADoEvent can handle the event, the function attempts to use the script context for that purpose.Script contexts can in turn pass an event to a resume dispatch function with a statement that’s equivalent to an AppleScript continue statement. The OSASetResumeDispatchProc and OSAGetResumeDispatchProc functions allow your application to set and get pointers to the resume dispatch function used by a scripting component. These functions use the following type for a pointer to a resume dispatch function:TYPE AEHandlerProcPtr = EventHandlerProcPtr;A resume dispatch function takes the same parameters as an Apple event handler and dispatches an event to an application’s standard handler for that event.If you need to create a new, empty script context, you can use the OSAMakeContext function.A scripting component that supports the functions described in this section has the kOSASupportsEventHandling bit set in the componentFlags field of its component description record.OSASetResumeDispatchProcYou can use the OSASetResumeDispatchProc function to set the resume dispatch function called by a scripting component during execution of an AppleScript continue statement or its equivalent. FUNCTION OSASetResumeDispatchProc                                 (scriptingComponent: ComponentInstance;                                  resumeDispatchProc: AEHandlerProcPtr;                                  refCon: LongInt): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).resumeDispatchProcYou can specify one of the following in this parameter:n    a pointer to a resume dispatch functionn    the kOSAUseStandardDispatch constant, which causes the Apple Event Manager to dispatch the event using standard Apple event dispatching  n    the kOSANoDispatch constant, which tells the Apple Event Manager that the processing of the Apple event is complete and that it does not need to be dispatchedrefCon    A reference constant. Specify kOSADontUsePhac in this parameter and kOSAUseStandardDispatch in the resumeDispatchProc parameter to request standard Apple event dispatching excluding the special handler dispatch table.DESCRIPTIONThe OSASetResumeDispatchProc function sets the resume dispatch function that the specified instance of a scripting component calls during execution of an AppleScript continue statement or its equivalent. The resume dispatch function should dispatch the event to the application’s standard handler for that event.If you are using a general handler similar to that in Listing 10-7 on page 10-21 for preliminary processing of Apple events, and if you can rely on standard Apple event dispatching to dispatch the event correctly, you don’t need to provide a resume dispatch function. Instead, you can specify kOSAUseStandardDispatch as the value of the resumeDispatchProc parameter and the constant kOSADontUsePhac as the value of the refCon parameter. This causes the Apple Event Manager to use standard Apple event dispatching except that it bypasses your application’s special handler dispatch table and thus won’t call your general Apple event handler recursively.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor more information about resume dispatch functions, see “Supplying a Resume Dispatch Function” on page 10-21 and the description of a resume dispatch function on page 10-97.OSAGetResumeDispatchProcYou can use the OSAGetResumeDispatchProc function to get the resume dispatch function currently being used by a scripting component instance during execution of an AppleScript continue statement or its equivalent.FUNCTION OSAGetResumeDispatchProc                             (scriptingComponent: ComponentInstance;                              VAR resumeDispatchProc: AEHandlerProcPtr;                              VAR refCon: LongInt): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).resumeDispatchProcThe OSAGetResumeDispatchProc function returns a pointer to the resume dispatch function for the specified scripting component in this parameter. If no resume dispatch function has been registered, OSAGetResumeDispatchProc returns kOSAUseStandardDispatch (the default). refCon    The OSAGetResumeDispatchProc function returns the reference constant associated with the resume dispatch function in this parameter.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance    OSAExecuteEventYou can use the OSAExecuteEvent function to handle an Apple event with the aid of a script context and obtain a script ID for the resulting script value.FUNCTION OSAExecuteEvent(scriptingComponent    : ComponentInstance;                                 theAppleEvent        : AppleEvent;                                 contextID            : OSAID;                                 modeFlags            : LongInt;                                 VAR resultingScriptValueID: OSAID)                                 : OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).theAppleEventThe Apple event to be handled.contextID    The script ID for the script context to be used to handle the Apple event.modeFlags    Information used by individual scripting components. To avoid setting any mode flags, specify kOSAModeNull. Other possible mode flags are listed in the description that follows.resultingScriptValueIDA script ID for the resulting script value.DESCRIPTIONThe OSAExecuteEvent function attempts to use the script context specified by the contextID parameter to handle the Apple event specified by the theAppleEvent parameter. If the scripting component determines that the script context can’t handle the event (for example, if a script written in AppleScript doesn’t include statements that handle the event), OSAExecuteEvent immediately returns errAEEventNotHandled rather than errOSAScriptError.If the scripting component determines that the script context can handle the event, OSAExecuteEvent executes the script context’s handler and returns the resulting script ID. If execution of the script context’s handler for the event generates an error, OSAExecuteEvent returns errOSAScriptError, and you can get more detailed error information by calling the OSAScriptError function.You can control the way in which the scripting component executes a script context by adding any of these flags to the modeFlags parameter:Flag    Description    kOSAModeNeverInteract    Adds kAENeverInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCanInteract    Adds kAECanInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeAlwaysInteract    Adds kAEAlwaysInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCantSwitchLayer    Prevents use of kAECanSwitchLayer in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    kOSAModeDontReconnect    Adds kAEDontReconnect to sendMode parameter of AESend for events sent when script is executed.    kOSAModeDoRecord    Prevents use of kAEDontRecord in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    If the script context identified by the contextID parameter specifies that the Apple event should be passed to the application’s default handler for that event (for example, with an AppleScript continue statement), OSAExecuteEvent passes the event to the resume dispatch function currently being used by the scripting component. The resume dispatch function dispatches the event directly to the application’s standard handler for that event (that is, without calling OSAExecuteEvent again). If the contextID parameter is kOSANullScript, the OSAExecuteEvent function passes the event directly to the resume dispatch function. If a call to the resume dispatch function is successful, execution of the script context proceeds from the point at which the resume dispatch function was called.IMPORTANTThe OSAExecuteEvent function can generate the result code errAEEventNotHandled in at least two ways. If the scripting component determines that a script context doesn’t declare a handler for a particular event, OSAExecuteEvent immediately returns errAEEventNotHandled. If a scripting component calls its resume dispatch function during script execution and the application’s standard handler for the event fails to handle it, OSAExecuteEvent returns errOSAScriptError and a call to OSAScriptError with kOSAErrorNumber in the selector parameter returns errAEEventNotHandled as the resulting error description.sRESULT CODESnoErr    0    No error    errAEEventNotHandled    –1708    Script context doesn’t contain handler for event    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    errOSAScriptError    –1753    Error occurred during execution or because of an attempt to pass event to a NIL resume dispatch function    badComponentInstance    $80008001    Invalid component instance    OSADoEventYou can use the OSADoEvent function to handle an Apple event with the aid of a script context and obtain a reply event.FUNCTION OSADoEvent(scriptingComponent    : ComponentInstance;                          theAppleEvent        : AppleEvent;                          contextID            : OSAID;                          modeFlags            : LongInt;                          VAR reply: AppleEvent): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).theAppleEventThe Apple event to be handled.contextID    The script ID for the script context to be used to handle the Apple event.modeFlags    Information used by individual scripting components. To avoid setting any mode flags, specify kOSAModeNull. Other possible mode flags are listed in the description that follows.reply    The reply Apple event.DESCRIPTIONThe OSADoEvent function resembles both OSADoScript and OSAExecuteEvent. However, unlike OSADoScript, the script OSADoEvent executes must be in the form of a script context, and execution is initiated by an Apple event. Unlike OSAExecuteEvent, OSADoEvent returns a reply Apple event rather than the script ID of the resulting script value.The OSADoEvent function, like OSAExecuteEvent, attempts to use the script context specified by the contextID parameter to handle the Apple event specified by the theAppleEvent parameter. If the scripting component determines that the script context can’t handle the event (for example, if a script written in an AppleScript dialect doesn’t include statements that handle the event), OSADoEvent immediately returns errAEEventNotHandled rather than errOSAScriptError.If the scripting component determines that the script context can handle the event, OSADoEvent executes the script context’s handler for the event and returns the resulting script ID. The OSADoEvent function returns a reply event that contains either the resulting script value or, if an error occurred during script execution, information about the error. If the error errOSAScriptError occurs during script execution, OSADoEvent calls OSAScriptError and returns the appropriate error information in the reply. The OSADoEvent function never returns errOSAScriptError.You can control the way in which the scripting component executes a script context by adding any of these flags to the modeFlags parameter:Flag    Description(continued)    kOSAModeNeverInteract    Adds kAENeverInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeCanInteract    Adds kAECanInteract to sendMode parameter of AESend for events sent when script is executed.    kOSAModeAlwaysInteract    Adds kAEAlwaysInteract to sendMode parameter of AESend for events sent when script is executed.        continued    kOSAModeCantSwitchLayer    Prevents use of kAECanSwitchLayer in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    kOSAModeDontReconnect    Adds kAEDontReconnect to sendMode parameter of AESend for events sent when script is executed.    kOSAModeDoRecord    Prevents use of kAEDontRecord in sendMode parameter of AESend for events sent when script is executed (the opposite of the Apple Event Manager’s interpretation of the same bit).    If the script context specifies that the Apple event should be passed to the application’s standard handler for that event (for example, with an AppleScript continue statement), OSADoEvent passes the event to the resume dispatch function currently being used by the scripting component. The resume dispatch function dispatches the event directly to the application’s standard handler for that event (that is, without calling OSADoEvent again). If the contextID parameter is kOSANullScript, the OSADoEvent function passes the event directly to the resume dispatch function. If the call to the resume dispatch function is successful, execution of the script context proceeds from the point at which the resume dispatch function was called. IMPORTANTLike OSAExecuteEvent, OSADoEvent can generate the result code errAEEventNotHandled in at least two ways. If the scripting component determines that a script context doesn’t declare a handler for a particular event, OSADoEvent immediately returns errAEEventNotHandled. If a scripting component calls its resume dispatch function during script execution and the application’s standard handler for the event fails to handle it, OSADoEvent returns errAEEventNotHandled in the reply Apple event.sRESULT CODESnoErr    0    No error    errAEEventNotHandled    –1708    Script context doesn’t contain handler for event    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor an example of the use of OSADoEvent, see Listing 10-7 on page 10-21.OSAMakeContextYou can use the OSAMakeContext function to get a script ID for a new script context. FUNCTION OSAMakeContext(scriptingComponent            : ComponentInstance;                                contextName: AEDesc;                                parentContext: OSAID;                                VAR resultingContextID: OSAID): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).contextNameName of new context. Some scripting components may use context names for semantic purposes. If the value of this parameter is typeNull, OSAMakeContext creates an unnamed context.parentContextExisting context from which new context inherits bindings. If the value of this parameter is kOSANullScript, the new context does not inherit bindings from any other context.resultingContextIDA script ID for the resulting script context.DESCRIPTIONThe OSAMakeContext function creates a new script context that you may pass to OSAExecute or OSAExecuteEvent. The new script context inherits the bindings of the script context specified in the parentContext parameter.SPECIAL CONSIDERATIONSIf you call OSAMakeContext using an instance of the generic scripting component, the generic scripting component uses the default scripting component to create the new script context.RESULT CODESnoErr    0    No error    errOSACantCoerce    –1700    Invalid context name    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    badComponentInstance    $80008001    Invalid component instance D      SEE ALSOTo compile existing source data into a script context, use OSACompile as described on page 10-48.AppleScript Component RoutinesThe AppleScript component provides routines for initializing the AppleScript component and manipulating the styles used to display AppleScript statements in a script. These routines are used primarily by script editors and other applications that display source data to users. Initializing AppleScriptBefore you call any of the standard scripting component routines, you can call the ASInit function to initialize the AppleScript component with desired application-specific stack and heap sizes. If you don’t call ASInit, the AppleScript component initializes itself using either the values specified in the application’s 'scsz' resource or, for those values not provided by the 'scsz' resource, default values provided by the AppleScript component.ASInitYou can use the ASInit function to initialize the AppleScript component.FUNCTION ASInit (scriptingComponent: ComponentInstance;                       modeFlags: LongInt;                       minStackSize: LongInt;                       preferredStackSize: LongInt;                       maxStackSize: LongInt;                      minHeapSize: LongInt;                      preferredHeapSize: LongInt;                      maxHeapSize: LongInt): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).modeFlags    Reserved for future use. Set to kOSAModeNull.minStackSizeThe minimum size for the portion of the application’s heap used by the AppleScript component’s application-specific stack. preferredStackSizeThe preferred size for the portion of the application’s heap used by the AppleScript component’s application-specific stack.maxStackSizeThe maximum size for the portion of the application’s heap used by the AppleScript component’s application-specific stack.minHeapSizeThe minimum size for the portion of the application’s heap used by the AppleScript component’s application-specific heap.preferredHeapSizeThe preferred size for the portion of the application’s heap used by the AppleScript component’s application-specific heap.maxHeapSizeThe maximum size for the portion of the application’s heap used by the AppleScript component’s application-specific heap.DESCRIPTIONYour application should set the modeFlags parameter to kOSAModeNull. You can use the other parameters to specify memory sizes for the portion of your application’s heap used by the AppleScript component for its application-specific heap and stack. If your application sets any of these parameters to 0, the AppleScript component uses the corresponding value in your application’s 'scsz' resource. If that value is also set to 0, the AppleScript component uses the corresponding default value:CONST    kASDefaultMinStackSize                                            = 1 * 1024;    kASDefaultPreferredStackSize                                            = 4 * 1024;    kASDefaultMaxStackSize                                            = 16 * 1024;    kASDefaultMinHeapSize                                            = 4 * 1024;    kASDefaultPreferredHeapSize                                            = 64 * 1024;    kASDefaultMaxHeapSize                                            = 32 * 1024 * 1024;If your application doesn’t call ASInit explicitly, the AppleScript component initializes itself using the values specified in your application’s 'scsz' resource when your application first calls any scripting component routine. If any of these values are set to 0, the AppleScript component uses the corresponding default value.If your application doesn’t call ASInit explicitly and doesn’t call any scripting component routines, the AppleScript component will not be initialized. For example, if your application opens and closes the AppleScript component or calls Component Manager routines such as OpenDefaultComponent or FindNextComponent but doesn’t call any scripting component routines, the AppleScript component is not initialized. When the AppleScript component is initialized, it uses your application’s high memory to create the blocks that it locks for its own use. If you expect to lock any portion of high memory for a shorter time than you expect the AppleScript component to be available, you should call ASInit explicitly.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance    Getting and Setting Styles for Source DataThe ASGetSourceStyles and ASSetSourceStyles functions allow you to get and set the script format styles currently used by the AppleScript component to display scripts. To obtain a list of style names formatted according to the script format styles currently used by the AppleScript component, use the ASGetSourceStyleNames function.ASGetSourceStylesYou can use the ASGetSourceStyles function to get the script format styles currently used by the AppleScript component to display scripts.FUNCTION ASGetSourceStyles                         (scriptingComponent: ComponentInstance;                         VAR resultingSourceStyles: STHandle): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).resultingSourceStylesA handle to a style element array defined by the TextEdit data type TEStyleTable that defines the styles used for different kinds of AppleScript terms. DESCRIPTIONThe ASGetSourceStyles function returns a style element array that defines the nine styles used for AppleScript terms. You can use these index constants to identify individual styles returned in the resultingSourceStyles parameter:CONST    kASSourceStyleUncompiledText                                             = 0;    kASSourceStyleNormalText                                            = 1;    kASSourceStyleLanguageKeyword                                            = 2;    kASSourceStyleApplicationKeyword                                            = 3;    kASSourceStyleComment                                            = 4;    kASSourceStyleLiteral                                            = 5;    kASSourceStyleUserSymbol                                            = 6;    kASSourceStyleObjectSpecifier                                            = 7;    kASNumberOfSourceStyles                                            = 8;Other AppleScript dialects may define additional styles. When you have finished using the style element array, you must dispose of it.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor information about the TEStyleTable array, see Inside Macintosh: Text.ASSetSourceStylesYou can use the ASSetSourceStyles function to set the script format styles used by the AppleScript component to display scripts.FUNCTION ASSetSourceStyles (scriptingComponent: ComponentInstance;                                     sourceStyles: STHandle): OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).sourceStylesA handle to a style element array defined by the TextEdit data type TEStyleTable that defines the nine styles used for different kinds of AppleScript terms. The style for each kind of term should be identified according to the index constants listed for ASGetSourceStyles on page 10-82.DESCRIPTIONThe ASSetSourceStyles function sets the script format styles used to display scripts. If you pass a NIL handle in the sourceStyles parameter, the AppleScript component uses its default styles.After you have set the script format styles, you must dispose of the style element array you used to specify them.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance    SEE ALSOFor information about the TEStyleTable array, see Inside Macintosh: Text.ASGetSourceStyleNamesYou can use the ASGetSourceStyleNames function to obtain a list of style names that are each formatted according to the script format styles currently used by the AppleScript component.FUNCTION ASGetSourceStyleNames                         (scriptingComponent: ComponentInstance;                         modeFlags: LongInt;                          VAR resultingSourceStyleNameList: AEDescList)                         : OSAError;scriptingComponentA component instance created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).modeFlags    Reserved for future use. Set to kOSAModeNull.resultingSourceStyleNameListList of style names (for example, “Uncompiled Text,” “Normal Text”) that are each formatted according to the current script format styles. The order of the names corresponds to the order of the source style constants listed for ASGetSourceStyles on page 10-82.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    badComponentInstance    $80008001    Invalid component instance      Generic Scripting Component RoutinesTo manipulate and execute scripts written in different scripting languages, your application can either open a connection with each corresponding scripting component individually or open a single connection with the generic scripting component. For information about how to connect with scripting components, see “Connecting to a Scripting Component,” which begins on page 10-3.If you open a connection with the generic scripting component, it in turn attempts to open connections dynamically with the appropriate scripting component for each script that it executes or manipulates. To provide this capability, the generic scripting component must be able to determine which scripting component created any script ID passed as a parameter to a standard scripting component routine. Because different scripting components may end up using the same script ID to refer to different scripts, the generic scripting component uses its own generic script IDs. The generic scripting component translates generic scripting IDs into the corresponding component-specific script IDs and vice versa when necessary.   A generic script ID is a script ID of type GenericID.TYPE GenericID = OSAID;You don’t need to know in detail how the generic scripting component keeps track of script IDs. However, you should be aware that the script IDs to which your application refers when it uses the generic scripting component are not the same as the script IDs used by scripting components that actually manipulate and execute scripts.If you are writing a script editor or recorder, you must pass the existing script ID to OSACompile or OSAStartRecording when you are recompiling or recording into an existing script. This ensures that the script is recompiled or recorded using the same scripting component that originally created the script. If instead you pass kOSANullScript to these routines, the new script is compiled or recorded using the default scripting component. Each instance of the generic scripting component has its own default scripting component. The section “Getting and Setting the Default Scripting Component,” which follows, describes routines provided by the generic scripting component that allow you to get and set the default scripting component.The generic scripting component supports the standard scripting component routines. However, most scripting components also support their own component-specific routines. You can’t use the generic scripting component to call a component-specific routine. Instead, you must use an instance of the specific scripting component that supports the routine. To facilitate the use of component-specific routines, the generic scripting component allows you to identify the scripting component that created stored script data, get an instance of a specified scripting component, and convert between generic script IDs and component-specific script IDs. The section “Using Component-Specific Routines,” which begins on page 10-87, describes the generic scripting component routines that allow you to perform these tasks.Some generic scripting component routines take or return a component subtype of type ScriptingComponentSelector.TYPE ScriptingComponentSelector = OSType; You can use subtype codes of this type to identify specific scripting components.Getting and Setting the Default Scripting ComponentThe default scripting component for any instance of the generic scripting component is initially AppleScript, but you can change it if necessary. The OSAGetDefaultScriptingComponent and OSASetDefaultScriptingComponent functions allow you to get and set the default scripting component. OSAGetDefaultScriptingComponentYou can use the OSAGetDefaultScriptingComponent function to get the subtype code for the default scripting component associated with an instance of the generic scripting component. FUNCTION OSAGetDefaultScriptingComponent                    (genericScriptingComponent: ComponentInstance;                     VAR scriptingSubType: ScriptingComponentSelector)                     : OSAError;genericScriptingComponentA component instance for the generic scripting component, created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4). scriptingSubTypeThe function returns, in this parameter, the subtype code for the default scripting component associated with the instance of the generic scripting component specified in the genericScriptingComponent parameter.DESCRIPTIONThe OSAGetDefaultScriptingComponent function returns the subtype code for the default scripting component. This is the scripting component that will be used by OSAStartRecording, OSACompile, or OSACompileExecute if no existing script ID is specified. From the user’s point of view, the default scripting component corresponds to the scripting language selected in the Script Editor application when the user first creates a new script.Each instance of the generic scripting component has its own default scripting component, which is initially AppleScript. You can use OSASetDefaultScriptingComponent to change the default scripting component. RESULT CODESnoErr    0    No error    errOSACantOpenComponent    –1762    Can’t connect to scripting component    badComponentInstance    $80008001    Invalid component instance    OSASetDefaultScriptingComponentYou can use the OSASetDefaultScriptingComponent function to set the default scripting component associated with an instance of the generic scripting component.FUNCTION OSASetDefaultScriptingComponent                    (genericScriptingComponent: ComponentInstance;                     scriptingSubType: ScriptingComponentSelector)                     : OSAError;genericScriptingComponentA component instance for the generic scripting component, created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptingSubTypeThe subtype code for the scripting component you want to set as the default.DESCRIPTIONThe OSASetDefaultScriptingComponent function sets the default scripting component for the specified instance of the generic scripting component to the scripting component identified by the scriptingSubType parameter.Each instance of the generic scripting component has its own default scripting component, which is initially AppleScript. You can use OSAGetDefaultScriptingComponent to get the current default scripting component for an instance of the generic scripting component. RESULT CODESnoErr    0    No error    errOSACantOpenComponent    –1762    Specified component subtype hasn’t been registered    badComponentInstance    $80008001    Invalid component instance      Using Component-Specific RoutinesYou can’t use the generic scripting component to call a component-specific routine. Instead, you must use an instance of the specific scripting component that supports the routine. To facilitate the use of component-specific routines, the generic scripting component allows you to identify the scripting component that created stored script data, get an instance of a specified scripting component, and convert between generic script IDs and component-specific script IDs.If you want to identify the scripting component that created a storage descriptor record but don’t want to load the script, use the OSAGetScriptingComponentFromStored function. When you need to use a specific scripting component, the OSAGetScriptingComponent function allows you to get a component instance for that scripting component.The OSAGenericToRealID and OSARealToGenericID functions allow you to convert between generic script IDs and component-specific script IDs.OSAGetScriptingComponentFromStoredYou can use the OSAGetScriptingComponentFromStored routine to get the subtype code for a scripting component that created a storage descriptor record.FUNCTION OSAGetScriptingComponentFromStored                    (genericScriptingComponent: ComponentInstance;                                 scriptData: AEDesc;                     VAR scriptingSubType: ScriptingComponentSelector)                     : OSAError;genericScriptingComponentA component instance for the generic scripting component, created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptDataEither a generic storage descriptor record or a component-specific storage descriptor record.scriptingSubTypeThe function returns, in this parameter, a subtype code identifying the scripting component that created the descriptor record specified by the scriptData parameter.DESCRIPTIONThe OSAGetScriptingComponentFromStored function returns, in the scriptingSubType parameter, the subtype code for the scripting component that created the script data specified by the scriptData parameter. The generic scripting component automatically identifies the appropriate scripting component for you when you use it to call OSALoad. By calling OSAGetScriptingComponentFromStored, you can determine, without loading a script, which scripting component created the script data.RESULT CODESnoErr    0    No error    errOSACantOpenComponent    –1762    Can’t connect to scripting component    badComponentInstance    $80008001    Invalid component instance    OSAGetScriptingComponentYou can use the OSAGetScriptingComponent function to get the instance of a scripting component for a specified subtype.FUNCTION OSAGetScriptingComponent                    (genericScriptingComponent: ComponentInstance;                     scriptingSubType: ScriptingComponentSelector;                     VAR scriptingInstance: ComponentInstance)                     : OSAError;genericScriptingComponentA component instance for the generic scripting component, created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).scriptingSubTypeA subtype code for a scripting component.scriptingInstanceThe function returns, in this parameter, a component instance for the scripting component identified by the scriptingSubType parameter.DESCRIPTIONYou can’t use the generic scripting component with component-specific routines. Instead, use an instance of the specific scripting component, which you can obtain with OSAGetScriptingComponent. The OSAGetScriptingComponent function returns, in the scriptingInstance parameter, an instance of the scripting component identified by the scriptingSubType parameter. Each instance of the generic scripting component keeps track of a single instance of each component subtype, so OSAGetScriptingComponent always returns the same instance of a specified scripting component that the generic scripting component uses for standard scripting component routines.For example, you can use OSAGetDefaultComponent to get the subtype code for the default scripting component (that is, the scripting component used by the generic scripting component for new scripts). You can then get an instance of the default scripting component by passing its subtype code to OSAGetScriptingComponent. Finally, you can pass that instance to OSAScriptingComponentName to obtain the default scripting component’s name so you can display it to the user. Similarly, you can pass kAppleScriptSubtype in the scriptingSubType parameter to obtain an instance of the AppleScript component. This is necessary, for example, to call AppleScript-specific routines such as ASGetSourceStyles.RESULT CODESnoErr    0    No error    errOSACantOpenComponent    –1762    Can’t connect to scripting component    badComponentInstance    $80008001    Invalid component instance    SEEALSOFor descriptions of the OSAGetDefaultScriptingComponent and OSAScriptingComponentName functions, see page 10-86 and page 10-47, respectively. OSAGenericToRealIDYou can use the OSAGenericToRealID function to convert a generic script ID to the corresponding component-specific script ID. FUNCTION OSAGenericToRealID                    (genericScriptingComponent: ComponentInstance;                     VAR theScriptID: OSAID;                     VAR theExactComponent: ComponentInstance)                     : OSAError;genericScriptingComponentA component instance for the generic scripting component, created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).theScriptIDThe generic script ID that you want to convert. The OSAGenericToRealID function returns, in this parameter, the component-specific script ID that corresponds to the generic script ID that you pass in this parameter.theExactComponentThe OSAGenericToRealID function returns, in this parameter, the component instance that created the script ID returned in the theScriptID parameter.DESCRIPTIONYou can’t use the generic scripting component and a generic script ID with component-specific routines. Instead, you can use the component instance and script ID returned by OSAGenericToRealID.Given a generic script ID (that is, a script ID returned by a call to a standard component routine via the generic scripting component), the OSAGenericToRealID function returns the equivalent component-specific script ID and the component instance that created that script ID. The OSAGenericToRealID function modifies the script ID in place, changing the generic script ID you pass in the theScriptID parameter to the corresponding component-specific script ID. RESULT CODESnoErr    0    No error    errOSACantOpenComponent    –1762    Can’t connect to scripting component    badComponentInstance    $80008001    Invalid component instance    OSARealToGenericIDYou can use the OSARealToGenericID function to convert a component-specific script ID to the corresponding generic script ID. FUNCTION OSARealToGenericID                    (genericScriptingComponent: ComponentInstance;                                 VAR theScriptID: OSAID;                     theExactComponent: ComponentInstance)                     : OSAError;genericScriptingComponentA component instance for the generic scripting component, created by a prior call to the Component Manager function OpenDefaultComponent or OpenComponent (see page 10-4).theScriptIDThe component-specific script ID that you want to convert. You must have obtained this script ID from the scripting component instance passed in the theExactComponent parameter. The OSARealToGenericID function returns, in this parameter, the generic script ID that corresponds to the component-specific script ID that you pass in this parameter.theExactComponentA scripting component instance returned by a generic scripting component routine. DESCRIPTIONThe OSARealToGenericID function performs the reverse of the task performed by OSAGenericToRealID. Given a component-specific script ID and an exact scripting component instance (that is, the component instance that created the component-specific script ID), the OSARealToGenericID function returns the corresponding generic script ID. The OSARealToGenericID function modifies the script ID in place, changing the component-specific script ID passed in the theScriptID parameter to the corresponding generic script ID.You’ll need to do this if you have obtained a component-specific script ID using an exact scripting component instance and you want to refer to the same script in calls that use an instance of the generic scripting component. You can’t use a component-specific script ID with the generic scripting component.The script ID you pass in the theScriptID parameter must be a component-specific script ID obtained from a scripting component instance known to the generic scripting component. You can obtain such an instance by calling either OSAGetScriptingComponent or OSAGenericToRealID.RESULT CODESnoErr    0    No error    errOSAComponentMismatch    –1761    The theScriptID and theExactComponent parameters are for two different scripting components    errOSACantOpenComponent    –1762    Can’t connect to scripting component    badComponentInstance    $80008001    Invalid component instance    Routines Used by Scripting ComponentsScripting components can call three routines to manipulate the trailers for generic storage descriptor records. “Writing a Scripting Component” on page 10-27 provides general guidelines for writing a scripting component.Manipulating Trailers for Generic Storage Descriptor RecordsAll scripting components must use the OSAGetStorageType, OSAAddStorageType, and OSARemoveStorageType functions described in this section to add, remove, and inspect the trailers appended to script data in generic storage descriptor records. For more information about generic storage descriptor records, see “Saving Script Data,” which begins on page 10-12.OSAGetStorageTypeYou can use the OSAGetStorageType function to retrieve the scripting component subtype from the script trailer appended to the script data in a generic storage descriptor record.FUNCTION OSAGetStorageType(scriptData: Handle;                                     VAR type: DescType): OSErr;scriptData A handle to the script data.type    The descriptor type specified in the script data trailer.DESCRIPTIONThe OSAGetStorageType function retrieves the scripting component subtype from the trailer. If no trailer can be found, OSAGetStorageType returns the error errOSABadStorageType.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSABadStorageType    –1752    Bad storage type    OSAAddStorageTypeYou can use the OSAAddStorageType routine to add a trailer to the script data in a generic storage descriptor record.FUNCTION OSAAddStorageType(scriptData: Handle;                                     type: DescType): OSErr;scriptData     A handle to the script data.type    The descriptor type to be specified in the trailer added to the script data. DESCRIPTIONThe OSAAddStorageType routine attaches a trailer to a handle (consequently expanding the data to which the handle refers) or updates an existing trailer.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSABadStorageType    –1752    Bad storage type    OSARemoveStorageTypeYou can use the OSARemoveStorageType routine to remove a trailer from the script data in a generic storage descriptor record.FUNCTION OSARemoveStorageType (scriptData: Handle): OSErr;scriptDataA handle to the script data.DESCRIPTIONThe OSARemoveStorageType routine removes an existing trailer (reducing the handle's size). If no trailer can be found, then the handle is not modified, and noErr is returned.RESULT CODESnoErr    0    No error    errOSASystemError    –1750    General scripting system error    errOSABadStorageType    –1752    Bad storage type    Application-Defined RoutinesYour application can provide alternative active, send, and create functions for use by scripting components during script execution. All scripting components support routines that allow you to set and get the current active function called periodically by the scripting component during script execution. Some scripting components also support routines that allow you to set and get the current send and create functions used by the scripting component when it creates and sends Apple events during script execution.This section provides the syntax declarations for the active, send, create, and resume dispatch functions. When a scripting component calls any of these functions, the A5 register is set up for your application, and your application is the current process.MyActiveProcYour application can provide an alternative active function that performs periodic tasks during script compilation such as checking for Command-period, spinning the cursor, and checking for system-level errors. FUNCTION MyActiveProc (refCon: LongInt): OSErr;refCon    A reference constant.DESCRIPTIONEvery scripting component calls an active function periodically during script compilation and execution and provides routines that allow your application to set or get the pointer to the active function. If you don’t set an alternative active function for a scripting component, it uses its own default active function. A scripting component’s default active function allows a user to cancel script execution by pressing Command-period and calls WaitNextEvent to give other processes time.SEE ALSOFor descriptions of the scripting component routines you can use to set or get the pointer to a scripting component’s active function, see “Manipulating the Active Function” on page 10-45.For a discussion of the role of an active function, see “Supplying an Alternative Active Function” on page 10-23.MyAECreateProcYour application can provide an alternative create function to gain control over the creation and addressing of Apple events. This can be useful, for example, if your application needs to add its own transaction code to the event. An alternative create function takes the same parameters as the AECreateAppleEvent function plus a reference constant. FUNCTION MyAECreateProc (theAEEventClass: AEEventClass;                                  theAEEventID: AEEventID;                                  target: AEAddressDesc;                                  returnID: Integer;                                  transactionID: LongInt;                                  VAR result: AppleEvent;                                 refCon: LongInt): OSErr;DESCRIPTIONEvery scripting component calls a create function whenever it creates an Apple event during script execution and provides routines that allow you to set or get the pointer to the create function.If you don’t set an alternative create function for a scripting component, it uses the standard Apple Event Manager function AECreateAppleEvent, which it calls with its own default parameters.SEE ALSOFor descriptions of the scripting component routines you can use to set or get the pointer to a scripting component’s create function, see “Manipulating the Create and Send Functions,” which begins on page 10-55.For information about create functions, see “Alternative Create Functions” on page 10-24.For a description of the parameters for the AECreateAppleEvent function, see “Creating Apple Events,” which begins on page 5-25. MyAESendProcYour application can provide an alternative send function that performs almost any action instead of or in addition to sending Apple events. For example, before sending an Apple event, an alternative send function can modify the event or save a copy of the event. An alternative send function takes the same parameters as the AESend function plus a reference constant. FUNCTION MyAESendProc (theAppleEvent: AppleEvent;                               VAR reply: AppleEvent;                               sendMode: AESendMode;                               sendPriority: AESendPriority;                               timeOutInTicks: LongInt;                               idleProc: IdleProcPtr;                               filterProc: EventFilterProcPtr;                              refCon: LongInt): OSErr;DESCRIPTIONEvery scripting component calls a send function whenever it sends an Apple event during script execution and provides routines that allow you to set or get the pointer to the send function.If you don’t set an alternative send function for a scripting component, it uses the standard Apple Event Manager function AESend, which it calls with its own default parameters.SEE ALSOFor descriptions of the scripting component routines you can use to set or get the pointer to a scripting component’s send function, see “Manipulating the Create and Send Functions,” which begins on page 10-55.For more information about send functions, see “Alternative Send Functions” on page 10-25.For a description of the parameters for the AESend function, see “Sending Apple Events,” which begins on page 5-37.MyResumeDispatchYour application can provide a resume dispatch function that a scripting component calls during script execution to dispatch Apple events directly to an application’s default handler for an Apple event. A resume dispatch function takes the same parameters as an Apple event handler.FUNCTION MyResumeDispatch (theAppleEvent: AppleEvent;                                     reply: AppleEvent; refCon: LongInt)                                    : OSErr;theAppleEventThe Apple event to be dispatched.reply    The default reply Apple event provided by the Apple Event Manager.refCon    The reference constant stored in the Apple event dispatch table for the Apple event.DESCRIPTIONIf a script specifies that the Apple event should be passed to an application’s standard handler for that event (for example, with an AppleScript continue statement), the scripting component executing the script passes the event to the resume dispatch function currently being used by the scripting component. The resume dispatch function should dispatch the event directly to the application’s standard handler for that event. If you use script contexts to handle Apple events, you may need to provide a resume dispatch function.If you can rely on standard Apple event dispatching to dispatch the event correctly, you don’t need to provide a resume dispatch function. Instead, you can use the OSASetResumeDispatchProc routine to specify that the Apple Event Manager should use standard Apple event dispatching instead of a resume dispatch function.SEE ALSOFor a description of the OSASetResumeDispatchProc function, see page 10-72.For a discussion of the use of script contexts to handle Apple events, see “Using a Script Context to Handle an Apple Event” on page 10-19.Summary of Scripting ComponentsPascal SummaryConstantsCONST    {Component Manager type and subtype codes}    kOSAComponentType                                                    = 'osa ';                    kOSAGenericScriptingComponentSubtype                                                    = 'scpt';    {null script ID passed to OSAExecute, OSAGetSource, or OSAStartRecording}     kOSANullScript                                                    = 0;            {empty script}    {mode flag that indicates a routine's default mode settings are to be }    { used}    kOSAModeNull                                                    = 0;    kOSANullMode                                                    = 0;    {mode flag used with OSAStore to store a script context without storing }    { its parent context}    kOSAModeDontStoreParent                                                    = $00004000;    {mode flag used with OSAStore, OSALoad, or OSACompile to request }     { minimum script data}    kOSAModePreventGetSource                                                    = $00000001;        {mode flags used with OSACompile, OSAExecute, OSALoadExecute, }    { OSACompileExecute, OSADoScript, OSAExecuteEvent, and OSADoEvent}    {these mode flags cause the scripting component to set the corresponding }    { sendMode flags when it sends the event}    kOSAModeNeverInteract                                                    = kAENeverInteract                        ;                kOSAModeCanInteract                                                    = kAECanInteract                    ;                kOSAModeAlwaysInteract                                                    = kAEAlwaysInteract;                                        kOSAModeDontReconnect                                                    = kAEDontReconnect;    {this mode flag causes the scripting component not to set the }     { kAECanSwitchLayer sendMode flag when it sends the event}    kOSAModeCantSwitchLayer                                                    = $00000040;                        {this mode flag causes the scripting component not to set the }     { kAEDontRecord sendMode flag when it sends the event}    kOSAModeDoRecord                                                    = $00001000;    {mode flags used with OSACompile}    {this mode flag causes OSACompile to compile the source data as a script }     { context}    kOSAModeCompileIntoContext                                                    = $00000002;    {this mode flag causes OSACompile to augment the script data for a }     { script context rather than replacing it}    kOSAModeAugmentContext                                                    = $00000004;    {mode flags used with OSADisplay or OSADoScript to indicate that output }    { needs to be readable by humans only and does not have to be recompiled }    { by OSACompile}     kOSAModeDisplayForHumans                                                    = $00000008;    {suite and event code for the Recorded Text event}    kOSASuite                                                    = 'ascr';    kOSARecordedText                                                    = 'recd';    {resource type for stored script data}    kOSAScriptResourceType = kOSAGenericScriptingComponentSubtype        ;    {descriptor type for generic storage descriptor records}    typeOSAGenericStorage                                                     = kOSAScriptResourceType;    {descriptor types and error range keywords for OSAScriptError}    kOSAErrorNumber                                                    = 'errn'; {returns error number}    kOSAErrorMessage                                                    = 'errs'; {returns error message}    kOSAErrorBriefMessage                                                    = 'errb'; {returns brief error }                                                                     { message}    kOSAErrorApp                                                    = 'erap'; {returns PSN or name of }                                                                     { errant application}    kOSAErrorPartialResult                                                    = 'ptlr'; {returns partial }                                                                     { result, if any}    kOSAErrorOffendingObject                                                    = 'erob'; {returns info about }                                                                     { offending object, if }                                                                     { any}    kOSAErrorRange                                                    = 'erng'; {returns error range}    typeOSAErrorRange                                                     = 'erng'; {descriptor type for }                                                                     { error range}    keyOSASourceStart                                                    = 'srcs'; {start of error range}    keyOSASourceEnd                                                    = 'srce'; {end of error range}    {if selector parameter of kOSAScriptError is kOSAErrorNumber, scripting }    { components may return any of these error codes}    {dynamic errors}    errOSACantCoerce                                                    = errAECoercionFail;    errOSACantAccess                                                    = errAENoSuchObject;    errOSAGeneralError                                                    = -2700;    errOSADivideByZero                                                    = -2701;    errOSANumericOverflow                                                    = -2702;    errOSACantLaunch                                                    = -2703;    errOSAAppNotHighLevelEventAware                                                    = -2704;    errOSACorruptTerminology                                                    = -2705;    errOSAStackOverflow                                                    = -2706;    errOSAInternalTableOverflow                                                    = -2707;    errOSADataBlockTooLarge                                                    = -2708;    {component-specific dynamic script errors: -2720 through -2739}    {static errors}    errTypeError                                                    = errAEWrongDataType;    errOSAMessageNotUnderstood                                                    = errAEEventNotHandled;    errOSAUndefinedMessage                                                    = errAEHandlerNotFound;    errOSAIllegalIndex                                                    = errAEIllegalIndex;    errOASIllegalRange                                                    = errAEImpossibleRange;    errOSASyntaxError                                                    = -2740;    errOSASyntaxTypeError                                                     = -2741;    errOSATokenTooLong                                                    = -2742;    errOSAMissingParameter                                                    = errAEDescNotFound;    errOSAParameterMismatch                                                     = errAEWrongNumberArgs;    errOSADuplicateParameter                                                    = -2750;    errOSADuplicateProperty                                                    = -2751;    errOSADuplicateHandler                                                    = -2752;    errOSAUndefinedVariable                                                    = -2753;    errOSAInconsistentDeclarations                                                    = -2754;    errOSAControlFlowError                                                    = -2755;    {component-specific static script errors: -2760 through -2779}    {dialect-specific script errors: -2780 through -2799}    {descriptor type for each item in list returned by OSAAvailableDialects}        typeOSADialectInfo                                                     = 'difo';     {keywords for descriptor record of descriptor type typeOSADialectInfo; }    { these can also be used in selector parameter of OSAGetDialectInfo}    keyOSADialectName                                                     = 'dnam'; {used with descriptor }                                                                     { record of any text }                                                                     { type, such as typeChar}    keyOSADialectCode                                                     = 'dcod'; {used with descriptor }                                                                     { record of type }                                                                     { typeShortInteger}    keyOSADialectLangCode                                                    = 'dlcd'; {used with descriptor }                                                                     { record of type }                                                                     { typeShortInteger}    keyOSADialectScriptCode                                                    = 'dscd'; {used with descriptor }                                                                     { record of type }                                                                     { typeShortInteger}    {constants for use with OSASetResumeDispatchProc}    kOSAUseStandardDispatch                                                    = kAEUseStandardDispatch;    kOSANoDispatch                                                    = kAENoDispatch;    kOSADontUsePhac                                                    = $0001;    {selectors for use with OSAGetScriptInfo}    kOSAScriptIsModified                                                    = 'modi';    kOSAScriptIsTypeCompiledScript                                                    = 'cscr';    kOSAScriptIsTypeScriptValue                                                    = 'valu';    kOSAScriptIsTypeScriptContext                                                    = 'cntx';    kOSAScriptBestType                                                    = 'best';    kOSACanGetSource                                                    = 'gsrc';    {OSA component flags}    kOSASupportsCompiling                                                     = $0002;    kOSASupportsGetSource                                                     = $0004;    kOSASupportsAECoercion                                                    = $0008;    kOSASupportsAESending                                                     = $0010;    kOSASupportsRecording                                                     = $0020;    kOSASupportsConvenience                                                     = $0040;    kOSASupportsDialects                                                     = $0080;    kOSASupportsEventHandling                                                     = $0100;    {component selectors}    {basic scripting}    kOSASelectLoad                                                = $0001;    kOSASelectStore                                                = $0002;    kOSASelectExecute                                                = $0003;    kOSASelectDisplay                                                = $0004;    kOSASelectScriptError                                                = $0005;    kOSASelectDispose                                                = $0006;    kOSASelectSetScriptInfo                                                = $0007;    kOSASelectGetScriptInfo                                                = $0008;    kOSASelectSetActiveProc                                                = $0009;    kOSASelectGetActiveProc                                                = $000A;    {compiling}    kOSASelectScriptingComponentName                                                = $0102;    kOSASelectCompile                                                = $0103;    kOSASelectCopyID                                                = $0104;    {getting source data}    kOSASelectGetSourc                        e                        = $0201;    {coercing script values}    kOSASelectCoerceFromDesc                                                = $0301;    kOSASelectCoerceToDesc                                                = $0302;    {manipulating send and create functions}    kOSASelectSetSendProc                                                = $0401;    kOSASelectGetSendProc                                                = $0402;    kOSASelectSetCreateProc                                                = $0403;    kOSASelectGetCreateProc                                                = $0404;    kOSASelectSetDefaultTarget                                                = $0405;    {recording}    kOSASelectStartRecording                                                = $0501;    kOSASelectStopRecording                                                = $0502;    {convenience}    kOSASelectLoadExecute                                                = $0601;    kOSASelectCompileExecute                                                = $0602;    kOSASelectDoScript                                                = $0603;    {manipulating dialects}    kOSASelectSetCurrentDialect                                                = $0701;    kOSASelectGetCurrentDialect                                                = $0702;    kOSASelectAvailableDialects                                                = $0703;    kOSASelectGetDialectInfo                                                = $0704;    kOSASelectAvailableDialectCodeList                                                = $0705;    {executing Apple event handlers in script contexts}    kOSASelectSetResumeDispatchProc                                                = $0801;    kOSASelectGetResumeDispatchProc                                                = $0802;    kOSASelectExecuteEvent                                                = $0803;    kOSASelectDoEvent                                                = $0804;    kOSASelectMakeContext                                                = $0805;    {scripting-component-specific selectors begin with this value}    kOSASelectComponentSpecificStart                                                = $1001;{*******AppleScript component constants*******}    typeAppleScript                                                = 'ascr';    {Component Manager subtype for AppleScript component}    kAppleScriptSubtype                                                = typeAppleScript;    {AppleScript constant for storage descriptor records}    typeASStorage                                                = typeAppleScript;    {AppleScript constant for the selector parameter of OSAGetScriptInfo}    kASHasOpenHandler                                                = 'hsod';    {AppleScript component selectors}    kASSelectInit                                                = $1001;    kASSelectSetSourceStyles                                                = $1002;    kASSelectGetSourceStyles                                                = $1003;    kASSelectGetSourceStyleNames                                                = $1004;    {default initialization parameters for AppleScript}    kASDefaultMinStackSize                                                = 1 * 1024;    kASDefaultPreferredStackSize                                                = 4 * 1024;    kASDefaultMaxStackSize                                                = 16 * 1024;    kASDefaultMinHeapSize                                                = 4 * 1024;    kASDefaultPreferredHeapSize                                                = 64 * 1024;    kASDefaultMaxHeapSize                                                = 32 * 1024 * 1024;    {AppleScript source style flags}    kASSourceStyleUncompiledText                                                      = 0;    kASSourceStyleNormalText                                                     = 1;    kASSourceStyleLanguageKeyword                                                     = 2;    kASSourceStyleApplicationKeyword                                                     = 3;    kASSourceStyleComment                                                     = 4;    kASSourceStyleLiteral                                                     = 5;    kASSourceStyleUserSymbol                                                     = 6;    kASSourceStyleObjectSpecifier                                                     = 7;    kASNumberOfSourceStyles                                                     = 8;    {if selector parameter of kOSAScriptError is kOSAErrorNumber, }    { AppleScript component may return any of these error codes}    errASCantConsiderAndIgnore                                                     = -2720;    errASCantCompareMoreThan32k                                                     = -2721;    errASCantCompareMixedScripts                                                     = -2722;    errASTerminologyNestingTooDeep                                                     = -2760;    errASInconsistentNames                                                     = -2780; {English dialect}{*******generic scripting component constants*******}    {component version this header file describes}    kGenericComponentVersion                                                     = $0100;    {generic scripting component selectors}    kGSSSelectGetDefaultScriptingComponent                                                      = $1001;    kGSSSelectSetDefaultScriptingComponent                                                     = $1002;    kGSSSelectGetScriptingComponent                                                     = $1003;    kGSSSelectGetScriptingComponentFromStored                                                     = $1004;    kGSSSelectGenericToRealID                                                     = $1005;    kGSSSelectRealToGenericID                                                     = $1006;Data TypesTYPE    OSAID                                        = LongInt;                          {script ID}    OSAError                                        = ComponentResult; {type for result codes}    {pointers for application-defined functions}    OSAActiveProcPtr                                         = ProcPtr;    AESendProcPtr                                        = ProcPtr;     AECreateAppleEventProcPtr                                         = ProcPtr;    AEHandlerProcPtr                                        = EventHandlerProcPtr;    {generic scripting component data types}    ScriptingComponentSelector = OSType;    GenericID                                    = OSAID;Required Scripting Component RoutinesSaving and Loading Script DataFUNCTION OSAStore    (scriptingComponent: ComponentInstance; scriptID: OSAID; desiredType: DescType;modeFlags: LongInt;VAR resultingScriptData: AEDesc): OSAError;FUNCTION OSALoad    (scriptingComponent: ComponentInstance; scriptData: AEDesc;modeFlags: LongInt;VAR resultingScriptID: OSAID): OSAError;Executing and Disposing of ScriptsFUNCTION OSAExecute    (scriptingComponent: ComponentInstance;compiledScriptID: OSAID;contextID: OSAID;modeFlags: LongInt;VAR resultingScriptValueID    : OSAID): OSAError;FUNCTION OSADisplay    (scriptingComponent: ComponentInstance;scriptValueID: OSAID; desiredType: DescType;modeFlags: LongInt;VAR resultingText: AEDesc): OSAError;FUNCTION OSAScriptError    (scriptingComponent: ComponentInstance;selector: OSType;desiredType: DescType;VAR resultingErrorDescription: AEDesc): OSAError;FUNCTION OSADispose    (scriptingComponent: ComponentInstance; scriptID: OSAID): OSAError;Setting and Getting Script InformationFUNCTION OSASetScriptInfo    (scriptingComponent: ComponentInstance;scriptID: OSAID; selector: OSType;value: LongInt): OSAError;FUNCTION OSAGetScriptInfo    (scriptingComponent: ComponentInstance;scriptID: OSAID; selector: OSType;VAR result: LongInt): OSAError;Manipulating the Active FunctionFUNCTION OSASetActiveProc    (scriptingComponent: ComponentInstance;activeProc: OSAActiveProcPtr;refCon: LongInt): OSAError;FUNCTION OSAGetActiveProc    (scriptingComponent: ComponentInstance;VAR activeProc: OSAActiveProcPtr;VAR refCon: LongInt): OSAError;Optional Scripting Component RoutinesCompiling ScriptsFUNCTION OSAScriptingComponentName(scriptingComponent: ComponentInstance;VAR resultingScriptingComponentName: AEDesc): OSAError;FUNCTION OSACompile    (scriptingComponent: ComponentInstance; sourceData: AEDesc; modeFlags: LongInt;VAR previousAndResultingScriptID: OSAID): OSAError;FUNCTION OSACopyID    (scriptingComponent    : ComponentInstance;fromID: OSAID; VAR toID: OSAID): OSAError;Getting Source DataFUNCTION OSAGetSource    (scriptingComponent: ComponentInstance;scriptID: OSAID; desiredType: DescType;VAR resultingSourceData: AEDesc): OSAError;Coercing Script ValuesFUNCTION OSACoerceFromDesc    (scriptingComponent: ComponentInstance;scriptData: AEDesc; modeFlags: LongInt;VAR resultingScriptValueID: OSAID): OSAError;FUNCTION OSACoerceToDesc    (scriptingComponent: ComponentInstance;scriptValueID: OSAID; desiredType: DescType; modeFlags: LongInt;VAR result: AEDesc): OSAError;Manipulating the Create and Send FunctionsFUNCTION OSASetCreateProc    (scriptingComponent: ComponentInstance;createProc: AECreateAppleEventProcPtr;refCon: LongInt): OSAError;FUNCTION OSAGetCreateProc    (scriptingComponent: ComponentInstance;VAR createProc: AECreateAppleEventProcPtr;VAR refCon: LongInt): OSAError;FUNCTION OSASetSendProc    (scriptingComponent: ComponentInstance;sendProc: AESendProcPtr; refCon: LongInt): OSAError;FUNCTION OSAGetSendProc    (scriptingComponent: ComponentInstance;VAR sendProc: AESendProcPtr;VAR refCon: LongInt): OSAError;FUNCTION OSASetDefaultTarget(scriptingComponent: ComponentInstance;target: AEAddressDesc): OSAError;Recording ScriptsFUNCTION OSAStartRecording    (scriptingComponent: ComponentInstance;VAR compiledScriptToModifyID: OSAID): OSAError;FUNCTION OSAStopRecording    (scriptingComponent: ComponentInstance;                                 compiledScriptID: OSAID):     OSAError;Executing Scripts in One StepFUNCTION OSALoadExecute    (scriptingComponent: ComponentInstance; scriptData: AEDesc;contextID: OSAID; modeFlags: LongInt;VAR resultingScriptValueID: OSAID): OSAError;FUNCTION OSACompileExecute    (scriptingComponent: ComponentInstance; sourceData: AEDesc;contextID: OSAID; modeFlags: LongInt;VAR resultingScriptValueID: OSAID): OSAError;FUNCTION OSADoScript    (scriptingComponent: ComponentInstance; sourceData: AEDesc;contextID: OSAID;desiredType: DescType; modeFlags: LongInt;VAR resultingText: AEDesc): OSAError;Manipulating DialectsFUNCTION OSASetCurrentDialect(scriptingComponent: ComponentInstance;dialectCode        : Integer): OSAError;FUNCTION OSAGetCurrentDialect(scriptingComponent            : ComponentInstance;VAR resultingDialectCode    : Integer): OSAError;FUNCTION OSAAvailableDialectCodeList(scriptingComponent                : ComponentInstance;VAR resultingDialectCodeList    : AEDesc): OSAError;FUNCTION OSAGetDialectInfo    (scriptingComponent                : ComponentInstance;dialectCode    : Integer; selector: OSType;VAR resultingDialectInfo: AEDesc): OSAError;FUNCTION OSAAvailableDialects(scriptingComponent                : ComponentInstance;VAR resultingDialectCodeList    : AEDesc): OSAError;Using Script Contexts to Handle Apple EventsFUNCTION OSASetResumeDispatchProc(scriptingComponent: ComponentInstance;resumeDispatchProc: AEHandlerProcPtr;refCon: LongInt): OSAError;FUNCTION OSAGetResumeDispatchProc(scriptingComponent: ComponentInstance;VAR resumeDispatchProc: AEHandlerProcPtr;VAR refCon: LongInt): OSAError;FUNCTION OSAExecuteEvent    (scriptingComponent: ComponentInstance;theAppleEvent: AppleEvent;contextID: OSAID; modeFlags: LongInt;VAR resultingScriptValueID: OSAID): OSAError;FUNCTION OSADoEvent    (scriptingComponent: ComponentInstance;theAppleEvent: AppleEvent;contextID: OSAID; modeFlags: LongInt;VAR reply: AppleEvent): OSAError;FUNCTION OSAMakeContext    (scriptingComponent            : ComponentInstance;contextName: AEDesc;parentContext: OSAID;VAR resultingContextID: OSAID): OSAError;AppleScript Component RoutinesInitializing AppleScriptFUNCTION ASInit    (scriptingComponent        : ComponentInstance;modeFlags: LongInt;minStackSize            : LongInt;preferredStackSize    : LongInt;maxStackSize            : LongInt;minHeapSize            : LongInt;preferredHeapSize    : LongInt;maxHeapSize            : LongInt)    : OSAError;Getting and Setting Styles for Source DataFUNCTION ASGetSourceStyles    (scriptingComponent            : ComponentInstance;VAR resultingSourceStyles    : STHandle): OSAError;FUNCTION ASSetSourceStyles    (scriptingComponent        : ComponentInstance;sourceStyles            : STHandle): OSAError;FUNCTION ASGetSourceStyleNames(scriptingComponent: ComponentInstance;modeFlags: LongInt;VAR resultingSourceStyleNamesList: AEDescList): OSAError;Generic Scripting Component RoutinesGetting and Setting the Default Scripting ComponentFUNCTION OSAGetDefaultScriptingComponent(genericScriptingComponent: ComponentInstance;VAR scriptingSubType: ScriptingComponentSelector): OSAError;FUNCTION OSASetDefaultScriptingComponent(genericScriptingComponent: ComponentInstance;scriptingSubType: ScriptingComponentSelector): OSAError;Using Component-Specific RoutinesFUNCTION OSAGetScriptingComponentFromStored(genericScriptingComponent: ComponentInstance;scriptData: AEDesc; VAR scriptingSubType: ScriptingComponentSelector): OSAError;FUNCTION OSAGetScriptingComponent(genericScriptingComponent: ComponentInstance;scriptingSubType: ScriptingComponentSelector;VAR scriptingInstance: ComponentInstance): OSAError;FUNCTION OSAGenericToRealID    (genericScriptingComponent: ComponentInstance;VAR theScriptID: OSAID; VAR theExactComponent: ComponentInstance): OSAError;FUNCTION OSARealToGenericID    (genericScriptingComponent: ComponentInstance;VAR theScriptID: OSAID; theExactComponent: ComponentInstance): OSAError;Routines Used by Scripting ComponentsManipulating Trailers for Generic Storage Descriptor RecordsFUNCTION OSAGetStorageType    (scriptData: Handle; VAR type: DescType): OSErr;FUNCTION OSAAddStorageType    (scriptData: Handle; type: DescType): OSErr;FUNCTION OSARemoveStorageType(scriptData: Handle): OSErr;Application-Defined RoutinesFUNCTION MyActiveProc    (refCon: LongInt): OSErr;FUNCTION MyAECreateProc     (theAEEventClass: AEEventClass; theAEEventID: AEEventID; target: AEAddressDesc; returnID: Integer; transactionID: LongInt; VAR result: AppleEvent; refCon: LongInt): OSErr;FUNCTION MyAESendProc     (theAppleEvent: AppleEvent; VAR reply: AppleEvent; sendMode: AESendMode; sendPriority: AESendPriority; timeOutInTicks: LongInt; idleProc: IdleProcPtr; filterProc: EventFilterProcPtr;refCon: LongInt): OSErr;FUNCTION MyResumeDispatch    (theAppleEvent: AppleEvent; reply: AppleEvent; refCon: LongInt): OSErr;C SummaryConstants/*Component Manager type and subtype codes*/#define kOSAComponentType                                                    'osa '                #define kOSAGenericScriptingComponentSubtype                                                 'scpt'/*null script ID passed to OSAExecute, OSAGetSource, or OSAStartRecording*/ #define kOSANullScript                                                    ((OSAID) 0)/*mode flag that indicates a routine's default mode settings are to be used*/#define kOSAModeNull                                                    0            #define kOSANullMode                                                    0/*mode flag used with OSAStore to store a script context without storing *//* its parent context*/#define kOSAModeDontStoreParent                                                    0x00004000/*mode flag used with OSAStore, OSALoad, or OSACompile to request */ /* minimum script data*/#define kOSAModePreventGetSource                                                    0x00000001/*mode flags used with OSACompile, OSAExecute, OSALoadExecute, *//* OSACompileExecute, OSADoScript, OSAExecuteEvent, and OSADoEvent*//*these mode flags cause the scripting component to set the corresponding *//* sendMode flags when it sends the event*/#define kOSAModeNeverInteract                                                    kAENeverInteract                                    #define kOSAModeCanInteract                                                    kAECanInteract                                    #define kOSAModeAlwaysInteract                                                    kAEAlwaysInteract                                    #define kOSAModeDontReconnect                                                    kAEDontReconnect/*this mode flag causes the scripting component not to set the */ /* kAECanSwitchLayer sendMode flag when it sends the event*/#define kOSAModeCantSwitchLayer                                                    0x00000040/*this mode flag causes the scripting component not to set the */ /* kAEDontRecord sendMode flag when it sends the event*/#define kOSAModeDoRecord                                                    0x00001000/*mode flags used with OSACompile*//*this mode flag causes OSACompile to compile the source data as a script */ /* context*/#define kOSAModeCompileIntoContext                                                    0x00000002/*this mode flag causes OSACompile to augment the script data for a script */ /* context rather than replacing it*/#define kOSAModeAugmentContext                                                    0x00000004/*mode flags used with OSADisplay or OSADoScript to indicate that output *//* needs to be readable by humans only and does not have to be recompiled *//* by OSACompile*/ #define kOSAModeDisplayForHumans                                                    0x00000008/*suite and event code for the Recorded Text event*/#define kOSASuite                                                    'ascr'#define kOSARecordedText                                                    'recd'/*resource type for stored script data*/#define kOSAScriptResourceType                                                    kOSAGenericScriptingComponentSubtype        /*descriptor type for generic storage descriptor records*/#define typeOSAGenericStorage                                                     kOSAScriptResourceType/*descriptor types and error range keywords for OSAScriptError*/#define kOSAErrorNumber                                                    'errn'            /*returns error number*/#define kOSAErrorMessage                                                    'errs'            /*returns error message*/#define kOSAErrorBriefMessage                                                    'errb'            /*returns brief error */                                                                /* message*/#define kOSAErrorApp                                                    'erap'            /*returns PSN or name of */                                                                /* errant application*/#define kOSAErrorPartialResult                                                    'ptlr'            /*returns partial result, */                                                                /* if any*/#define kOSAErrorOffendingObject                                                    'erob'            /*returns info about */                                                                /* offending object, if any*/#define kOSAErrorRange                                                    'erng'            /*returns error range*/#define typeOSAErrorRange                                                     'erng'            /*descriptor type for */                                                                /* error range*/#define keyOSASourceStart                                                    'srcs'            /*start of error range*/#define keyOSASourceEnd                                                    'srce'            /*end of error range*//*if selector parameter of kOSAScriptError is kOSAErrorNumber, scripting *//* components may return any of these error codes*/ /*dynamic errors*/#define errOSACantCoerce                                                                errAECoercionFail#define errOSACantAccess                                                                errAENoSuchObject#define errOSAGeneralError                                                                 -2700#define errOSADivideByZero                                                                 -2701#define errOSANumericOverflow                                                                 -2702#define errOSACantLaunch                                                                 -2703#define errOSAAppNotHighLevelEventAware                                                                 -2704#define errOSACorruptTerminology                                                                 -2705#define errOSAStackOverflow                                                                 -2706#define errOSAInternalTableOverflow                                                                 -2707#define errOSADataBlockTooLarge                                                                 -2708/*component-specific dynamic script errors: -2720 through -2739*//*static errors*/#define errTypeError                                                                 errAEWrongDataType#define errOSAMessageNotUnderstood                                                                 errAEEventNotHandled#define errOSAUndefinedMessage                                                                 errAEHandlerNotFound#define errOSAIllegalIndex                                                                 errAEIllegalIndex#define errOASIllegalRange                                                                 errAEImpossibleRange#define errOSASyntaxError                                                                 -2740#define errOSASyntaxTypeError                                                                  -2741#define errOSATokenTooLong                                                                 -2742#define errOSAMissingParameter                                                                 errAEDescNotFound#define errOSAParameterMismatch                                                                  errAEWrongNumberArgs#define errOSADuplicateParameter                                                                 -2750#define errOSADuplicateProperty                                                                 -2751#define errOSADuplicateHandler                                                                 -2752#define errOSAUndefinedVariable                                                                 -2753#define errOSAInconsistentDeclarations                                                                 -2754#define errOSAControlFlowError                                                                 -2755/*component-specific static script errors: -2760 through -2779*//*dialect-specific script errors: -2780 through -2799*//*descriptor type for each item in list returned by OSAAvailableDialects*/#define typeOSADialectInfo                                                     'difo'            /*keywords for descriptor record of descriptor type typeOSADialectInfo; *//* these can also be used in selector parameter of OSAGetDialectInfo*/#define keyOSADialectName                                                     'dnam'            /*used with descriptor */                                                                /* record of any text */                                                                /* type, such as typeChar*/#define keyOSADialectCode                                                     'dcod'            /*used with descriptor */                                                                /* record of type */                                                                /* typeShortInteger*/#define keyOSADialectLangCode                                                    'dlcd'            /*used with descriptor */                                                                /* record of type */                                                                /* typeShortInteger*/#define keyOSADialectScriptCode                                                    'dscd'            /*used with descriptor */                                                                /* record of type */                                                                /* typeShortInteger*//*constants for use with OSASetResumeDispatchProc*/#define kOSAUseStandardDispatch                                                    kAEUseStandardDispatch#define kOSANoDispatch                                                    kAENoDispatch#define kOSADontUsePhac                                                    $0001/*selectors for use with OSAGetScriptInfo*/#define kOSAScriptIsModified                                                    'modi'#define kOSAScriptIsTypeCompiledScript                                                    'cscr'#define kOSAScriptIsTypeScriptValue                                                    'valu'#define kOSAScriptIsTypeScriptContext                                                    'cntx'#define kOSAScriptBestType                                                    'best'#define kOSACanGetSource                                                    'gsrc'/*OSA component flags*/#define kOSASupportsCompiling                                                     0x0002#define kOSASupportsGetSource                                                     0x0004#define kOSASupportsAECoercion                                                    0x0008#define kOSASupportsAESending                                                     0x0010#define kOSASupportsRecording                                                     0x0020#define kOSASupportsConvenience                                                     0x0040#define kOSASupportsDialects                                                     0x0080#define kOSASupportsEventHandling                                                     0x0100/*component selectors*//*basic scripting*/#define kOSASelectLoad                                                    0x0001#define kOSASelectStore                                                    0x0002#define kOSASelectExecute                                                    0x0003#define kOSASelectDisplay                                                    0x0004#define kOSASelectScriptError                                                    0x0005#define kOSASelectDispose                                                    0x0006#define kOSASelectSetScriptInfo                                                    0x0007#define kOSASelectGetScriptInfo                                                    0x0008#define kOSASelectSetActiveProc                                                    0x0009#define kOSASelectGetActiveProc                                                    0x000A/*compiling*/#define kOSASelectScriptingComponentName                                                     0x0102#define kOSASelectCompile                                                    0x0103#define kOSASelectCopyID                                                    0x0104/*getting source data*/#define kOSASelectGetSourc                        e                            0x0201/*coercing script values*/#define kOSASelectCoerceFromDesc                                                    0x0301#define kOSASelectCoerceToDesc                                                    0x0302/*manipulating send and create functions*/#define kOSASelectSetSendProc                                                    0x0401#define kOSASelectGetSendProc                                                    0x0402#define kOSASelectSetCreateProc                                                    0x0403#define kOSASelectGetCreateProc                                                    0x0404#define kOSASelectSetDefaultTarget                                                    0x0405/*recording*/#define kOSASelectStartRecording                                                    0x0501#define kOSASelectStopRecording                                                    0x0502/*convenience*/#define kOSASelectLoadExecute                                                    0x0601#define kOSASelectCompileExecute                                                    0x0602#define kOSASelectDoScript                                                    0x0603/*manipulating dialects*/#define kOSASelectSetCurrentDialect                                                    0x0701#define kOSASelectGetCurrentDialect                                                    0x0702#define kOSASelectAvailableDialects                                                    0x0703#define kOSASelectGetDialectInfo                                                    0x0704#define kOSASelectAvailableDialectCodeList                                                     0x0705/*executing Apple event handlers in script contexts*/#define kOSASelectSetResumeDispatchProc                                                        0x0801#define kOSASelectGetResumeDispatchProc                                                        0x0802#define kOSASelectExecuteEvent                                                        0x0803#define kOSASelectDoEvent                                                        0x0804#define kOSASelectMakeContext                                                        0x0805/*scripting-component-specific selectors are added beginning with this *//* value*/#define kOSASelectComponentSpecificStart                                                         0x1001/********AppleScript component constants********/#define     typeAppleScript                                                        'ascr'/*Component Manager subtype for AppleScript component*/#define     kAppleScriptSubtype                                                        typeAppleScript/*AppleScript constant for storage descriptor records*/#define     typeASStorage                                                        typeAppleScript/*AppleScript constant for the selector parameter of OSAGetScriptInfo*/#define kASHasOpenHandler                                                            'hsod'/*AppleScript component selectors*/#define kASSelectInit                                                            0x1001#define kASSelectSetSourceStyles                                                            0x1002#define kASSelectGetSourceStyles                                                            0x1003#define kASSelectGetSourceStyleNames                                                            0x1004/*default initialization parameters for AppleScript*/#define kASDefaultMinStackSize                                                            1 * 1024#define kASDefaultPreferredStackSize                                                            4 * 1024#define kASDefaultMaxStackSize                                                            16 * 1024#define kASDefaultMinHeapSize                                                            4 * 1024#define kASDefaultPreferredHeapSize                                                            64 * 1024#define kASDefaultMaxHeapSize                                                            32 * 1024 * 1024/*AppleScript source style flags*/#define kASSourceStyleUncompiledText                                                             0#define kASSourceStyleNormalText                                                            1#define kASSourceStyleLanguageKeyword                                                            2#define kASSourceStyleApplicationKeyword                                                            3#define kASSourceStyleComment                                                            4#define kASSourceStyleLiteral                                                            5#define kASSourceStyleUserSymbol                                                            6#define kASSourceStyleObjectSpecifier                                                            7#define kASNumberOfSourceStyles                                                            8/*if selector parameter of kOSAScriptError is kOSAErrorNumber, AppleScript *//* component may return any of these error codes*/ #define errASCantConsiderAndIgnore                                                                -2720#define errASCantCompareMoreThan32k                                                                -2721#define errASCantCompareMixedScripts                                                                 -2722#define errASTerminologyNestingTooDeep                                                                 -2760#define errASInconsistentNames                                                                 -2780 /*English dialect*//*******generic scripting component constants*******//*component version this header file describes*/kGenericComponentVersion                                                                 0x0100/*generic scripting component selectors*/#define kGSSSelectGetDefaultScriptingComponent                                                                0x1001#define kGSSSelectSetDefaultScriptingComponent                                                                 0x1002#define kGSSSelectGetScriptingComponent                                                                0x1003#define kGSSSelectGetScriptingSystemFromStored                                                                0x1004#define kGSSSelectGenericToRealID                                                                0x1005#define kGSSSelectRealToGenericID                                                                0x1006Data Typestypedef unsigned long                                            OSAID    ;                    /*script ID*/typedef ComponentResult                                             OSAError        ;                /*type for result codes*//*pointers for application-defined functions*/typedef pascal OSErr (*OSAActiveProcPtr) (long refCon);typedef pascal OSErr (*AESendProcPtr)                                      (const AppleEvent                *            theAppleEvent,                                        AppleEvent* reply, AESendMode                             sendMode,                                        AESendPriority sendPriority,                                        long timeOutInTicks, IdleProcPtr             idleProc,                                        EventFilterProcPtr filterProc, long                             refCon);typedef pascal OSErr (*AECreateAppleEventProcPtr)                                                              (AEEventClass theAEEventClass,                                        AEEventID theAEEventID,                                        const AEAddressDesc*                            target, short returnID,                                        long transactionID, AppleEvent*             result,                                        long refCon);typedef pascal OSErr (*AEHandlerProcPtr)                                      (const AppleEvent* the AppleEvent,                                        AppleEvent* reply, long refCon);/*generic scripting component data types*/typedef OSType ScriptingComponentSelector;typedef OSAID GenericID;Required Scripting Component RoutinesSaving and Loading Script Datapascal OSAError OSAStore    (ComponentInstance scriptingComponent, OSAID scriptID, DescType desiredType,long modeFlags, AEDesc* resultingScriptData);pascal OSAError OSALoad    (ComponentInstance scriptingComponent, const AEDesc* scriptData, long modeFlags,OSAID* resultingScriptID);Executing and Disposing of Scriptspascal OSAError OSAExecute    (ComponentInstance scriptingComponent,OSAID compiledScriptID, OSAID contextID,long modeFlags, OSAID* resultingScriptValueID    );pascal OSAError OSADisplay    (ComponentInstance scriptingComponent,OSAID scriptValueID, DescType desiredType,long modeFlags, AEDesc* resultingText);pascal OSAError OSAScriptError(ComponentInstance scriptingComponent,OSType selector, DescType desiredType,AEDesc* resultingErrorDescription);pascal OSAError OSADispose    (ComponentInstance scriptingComponent, OSAID scriptID);Setting and Getting Script Informationpascal OSAError OSASetScriptInfo(ComponentInstance scriptingComponent,OSAID scriptID, OSType selector, long value);pascal OSAError OSAGetScriptInfo(ComponentInstance scriptingComponent,OSAID scriptID, OSType selector, long* result);Manipulating the Active Functionpascal OSAError OSASetActiveProc(ComponentInstance scriptingComponent,OSAActiveProcPtr activeProc, long refCon);pascal OSAError OSAGetActiveProc(ComponentInstance scriptingComponent,OSAActiveProcPtr* activeProc, long* refCon);Optional Scripting Component RoutinesCompiling Scriptspascal OSAError OSAScriptingComponentName(ComponentInstance scriptingComponent,AEDesc* resultingScriptingComponentName);pascal OSAError OSACompile    (ComponentInstance scriptingComponent, const AEDesc* sourceData,long modeFlags,OSAID* previousAndResultingScriptID);pascal OSAError OSACopyID    (ComponentInstance scriptingComponent,OSAID fromID, OSAID* toID);Getting Source Datapascal OSAError OSAGetSource(ComponentInstance scriptingComponent,OSAID scriptID, DescType desiredType,AEDesc* resultingSourceData);Coercing Script Valuespascal OSAError OSACoerceFromDesc(ComponentInstance scriptingComponent,const AEDesc* scriptData, long modeFlags,OSAID* resultingScriptValueID);pascal OSAError OSACoerceToDesc(ComponentInstance scriptingComponent,OSAID scriptValueID, DescType desiredType,long modeFlags, AEDesc* result);Manipulating the Create and Send Functionspascal OSAError OSASetCreateProc(ComponentInstance scriptingComponent,AECreateAppleEventProcPtr createProc,long refCon);pascal OSAError OSAGetCreateProc(ComponentInstance scriptingComponent,AECreateAppleEventProcPtr* createProc,long* refCon);pascal OSAError OSASetSendProc(ComponentInstance scriptingComponent,AESendProcPtr sendProc, long refCon);pascal OSAError OSAGetSendProc(ComponentInstance scriptingComponent,AESendProcPtr* sendProc, long* refCon);pascal OSAError OSASetDefaultTarget(ComponentInstance scriptingComponent,const AEAddressDesc* target);Recording Scriptspascal OSAError OSAStartRecording(ComponentInstance scriptingComponent,OSAID* compiledScriptToModifyID);pascal OSAError OSAStopRecording(ComponentInstance scriptingComponent, OSAID compiledScriptID);Executing Scripts in One Steppascal OSAError OSALoadExecute(ComponentInstance scriptingComponent,const AEDesc* scriptData, OSAID contextID,long modeFlags, OSAID* resultingScriptValueID);pascal OSAError OSACompileExecute(ComponentInstance scriptingComponent,const AEDesc* sourceData, OSAID contextID,long modeFlags, OSAID* resultingScriptValueID);pascal OSAError OSADoScript    (ComponentInstance scriptingComponent,const AEDesc* sourceData, OSAID contextID,DescType desiredType, long modeFlags,AEDesc* resultingText);Manipulating Dialectspascal OSAError OSASetCurrentDialect(ComponentInstance scriptingComponent,short dialectCode);pascal OSAError OSAGetCurrentDialect(ComponentInstance scriptingComponent,short* resultingDialectCode);pascal OSAError OSAAvailableDialectCodeList(ComponentInstance scriptingComponent                ,AEDesc* resultingDialectCodeList);pascal OSAError OSAGetDialectInfo(ComponentInstance scriptingComponent,short dialectCode, OSType selector,AEDesc* resultingDialectInfo);pascal OSAError OSAAvailableDialects(ComponentInstance scriptingComponent                ,AEDesc* resultingDialectInfoList    );Using Script Contexts to Handle Apple Eventspascal OSAError OSASetResumeDispatchProc(ComponentInstance scriptingComponent    ,AEHandlerProcPtr resumeDispatchProc,long refCon);pascal OSAError OSAGetResumeDispatchProc(ComponentInstance scriptingComponent    ,AEHandlerProcPtr* resumeDispatchProc,long* refCon);pascal OSAError OSAExecuteEvent(ComponentInstance scriptingComponent    ,const AppleEvent* theAppleEvent,OSAID contextID, long modeFlags,OSAID* resultingScriptValueID);pascal OSAError OSADoEvent    (ComponentInstance scriptingComponent    ,const AppleEvent* theAppleEvent,OSAID contextID, long modeFlags,AppleEvent* reply);pascal OSAError OSAMakeContext(ComponentInstance scriptingComponent,const AEDesc* contextName,OSAID parentContext, OSAID* resultingContextID);AppleScript Component RoutinesInitializing AppleScriptpascal OSAError ASInit    (ComponentInstance scriptingComponent        ,long modeFlags, long minStackSize,long preferredStackSize, long maxStackSize,long minHeapSize, long preferredHeapSize,long maxHeapSize);Getting and Setting Styles for Source Datapascal OSAError ASGetSourceStyles(ComponentInstance scriptingComponent,STHandle* resultingSourceStyles);pascal OSAError ASSetSourceStyles(ComponentInstance scriptingComponent,STHandle sourceStyles);pascal OSAError ASGetSourceStyleNames(ComponentInstance scriptingComponent,long modeFlags,AEDescList* resultingSourceStyleNamesList);Generic Scripting Component RoutinesGetting and Setting the Default Scripting Componentpascal OSAError OSAGetDefaultScriptingComponent(ComponentInstance genericScriptingComponent, ScriptingComponentSelector* scriptingSubType);pascal OSAError OSASetDefaultScriptingComponent(ComponentInstance genericScriptingComponent,ScriptingComponentSelector scriptingSubType);Using Component-Specific Routinespascal OSAError OSAGetScriptingComponentFromStored(ComponentInstance genericScriptingComponent,const AEDesc *scriptData, ScriptingComponentSelector scriptingSubType);pascal OSAError OSAGetScriptingComponent(ComponentInstance genericScriptingComponent,ScriptingComponentSelector scriptingSubType,ComponentInstance* scriptingInstance);pascal OSAError OSAGenericToRealID(ComponentInstance genericScriptingComponent,OSAID *theScriptID, ComponentInstance *theExactComponent);pascal OSAError OSARealToGenericID(ComponentInstance genericScriptingComponent,OSAID *theScriptID, ComponentInstance theExactComponent);Routines Used by Scripting ComponentsManipulating Trailers for Generic Storage Descriptor Recordspascal OSErr OSAGetStorageType(Handle scriptData, DescType* type);pascal OSErr OSAAddStorageType(Handle scriptData, DescType type);pascal OSErr OSARemoveStorageType(Handle scriptData);Application-Defined Routinespascal OSErr MyActiveProc    (long refCon);pascal OSErr MyAECreateProc(AEEventClass theAEEventClass,AEEventID theAEEventID, AEAddressDesc target,short returnID, long transactionID,AppleEvent* result, long refCon);pascal OSErr MyAESendProc    (AppleEvent theAppleEvent, AppleEvent* reply,AESendMode sendMode,AESendPriority sendPriority,long timeOutInTicks, IdleProcPtr idleProc,EventFilterProcPtr filterProc, long refCon);pascal OSErr MyResumeDispatch(const AppleEvent* theAppleEvent,AppleEvent* reply, long refCon);Result CodesnoErr    0    No error    errOSACantCoerce     –1700    Same as errAECoercionFail; data could not be coerced to the requested data type    errOSACorruptData    –1702    Same as errAECorruptData     errAEEventNotHandled    –1708    Event wasn’t handled by an Apple event handler    errAERecordingIsAlreadyOn    –1732    Attempt to turn recording on when it is already on for a recording process    errOSASystemError    –1750    General scripting system error    errOSAInvalidID    –1751    Invalid script ID    errOSABadStorageType    –1752    Illegal storage type    errOSAScriptError    –1753    Error occurred during compilation or execution    errOSABadSelector    –1754    Selector not supported by scripting component    errOSASourceNotAvailable    –1756    Source data not available    errOSANoSuchDialect    –1757    Invalid dialect code    errOSADataFormatObsolete    –1758    Data format is obsolete    errOSADataFormatTooNew    –1759    Data format is too new    errOSAComponentMismatch    –1761    Generic scripting component error; parameters are for two different scripting components instead of the same one    errOSACantOpenComponent    –1762    Generic scripting component error; can’t connect to scripting component    badComponentInstance    $80008001    Invalid component instance     Listing 11-0Program-to-Program Communications ToolboxContentsAbout the PPC Toolbox11-4Ports, Sessions, and Message Blocks11-4Setting Up Authenticated Sessions11-6Using the PPC Toolbox11-10PPC Toolbox Calling Conventions11-14Specifying Port Names and Location Names11-17Opening a Port11-20Browsing for Ports Using the Program Linking Dialog Box11-22Obtaining a List of Available Ports11-27Preparing for a Session11-29Initiating a PPC Session11-29Receiving Session Requests11-35Accepting or Rejecting Session Requests11-37Exchanging Data During a PPC Session11-39Reading Data From an Application11-40Sending Data to an Application11-42Ending a Session and Closing a Port11-43Invalidating Users11-44PPC Toolbox Reference11-46Data Structures11-46The PPC Toolbox Parameter Block11-46The PPC Port Record11-48The Location Name Record11-49The Port Information Record11-50PPC Toolbox Routines11-50Initializing the PPC Toolbox11-51Using the Program Linking Dialog Box11-51Obtaining a List of Ports11-54Opening and Closing a Port11-56Starting and Ending a Session11-59Receiving, Accepting, and Rejecting a Session11-66Reading and Writing Data11-71Locating a Default User and Invalidating a User11-75Application-Defined Routines11-77Completion Routines for PPC Toolbox Routines11-77Port Filter Functions11-78Summary of the PPC Toolbox11-80Pascal Summary11-80Constants11-80Data Types11-81PPC Toolbox Routines11-87Application-Defined Routines11-88C Summary11-89Constants11-89Data Types11-90PPC Toolbox Routines11-95Application-Defined Routines11-96Assembly-Language Summary11-96Trap Macros11-96Result Codes11-97Program-to-Program Communications ToolboxThis chapter describes how you can use the Program-to-Program Communications (PPC) Toolbox to send and receive low-level message blocks between applications.The PPC Toolbox can be used by different applications located on the same computer or across a network of Macintosh computers. The PPC Toolbox is available only in System 7 or later. To test for the existence of the PPC Toolbox, use the Gestalt function, described in Inside Macintosh: Operating System Utilities.Read this chapter if you want your application to transmit and receive data from other applications that support the PPC Toolbox. Applications that utilize the PPC Toolbox must be open and connected to each other to exchange data. The PPC Toolbox allows you to send large amounts of data to other applications; it is typically useful for code that is not event-based. The PPC Toolbox is called by the Macintosh Operating System and can also be called by applications, device drivers, desk accessories, or other programs.The PPC Toolbox provides a method of communication that is particularly useful for applications that are specifically designed to work together and are dependent on each other for information. For example, suppose one user organizes large amounts of data using a database application and another user filters and plots the same data using a plotting application. If both applications use the PPC Toolbox, these two applications can directly transmit data to each other when both applications are open and connected to each other.You can also use the PPC Toolbox if your application communicates with other applications using high-level events or Apple events, and your application allows the user to choose another application to communicate with. You can use a PPC Toolbox routine that provides a standard user interface to display a dialog box that lists other applications that are available to exchange information. See “Browsing for Ports Using the Program Linking Dialog Box” beginning on page 11-22 for detailed information. See the chapter “Event Manager” in Inside Macintosh: Macintosh Toolbox Essentials for information on high-level events, and see earlier chapters in this book for information on Apple events. The PPC Toolbox uses the AppleTalk Data Stream Protocol (ADSP) and the Name-Binding Protocol (NBP). For detailed information on ADSP and NBP, see Inside Macintosh: Networking.NoteThe sample applications “store data,” “display data,” “send and receive,” “make memo,” and “spell quick” used in this chapter are not actual products of Apple Computer, Inc. They are used for illustrative purposes only.uAbout the PPC ToolboxThe PPC Toolbox provides you with the ability to n    exchange data with other open applications on the same computer or across a network of Macintosh computersn    browse through a listing of applications that are available to exchange datan    verify user identities for communication across a networkTo utilize the PPC Toolbox to exchange data between open applications, each application involved must support the PPC Toolbox.This chapter first defines the main elements of the PPC Toolbox and then discusses how ton    set up your application for communicationn    use security features prior to establishing communicationn    locate other applications that can exchange datan    initiate communication between applicationsn    accept or reject incoming communications requestsn    transmit and receive data between applicationsn    terminate communication between applicationsPorts, Sessions, and Message BlocksTo initiate communication between applications, you must first open a port. A port is a portal through which your application can exchange information with another application. A port is designated by a port name and a location name.A port name is a unique identifier for a particular application on a computer. The port name contains a name string, a type string, and a script code for localization. The location name identifies the location of the computer on the network. The location name contains an object string, a type string, and a zone. An application can specify an alias location name by modifying its type string.Your application can open as many ports as it requires as long as each port name is unique within a particular computer. See “Specifying Port Names and Location Names” beginning on page 11-17 for detailed information on port names and location names. Through its port, an open application can communicate with another open application during a session. One port can support any number of communication sessions. During a session, an application sends and receives data in the form of a message block. The PPC Toolbox treats each block of data as a byte stream and delivers it in the same sequence in which it was sent.The words port name, location name, session, and message block are programmatic terms. You should not use them in the user interface of your application or in your user documentation. Instead, refer to a file that contains executable code as an application program. An application program that opens and uses PPC ports supports program linking. When you link two application programs together, you are forming a program link. A link allows two application programs to communicate with each other—you unlink two application programs when you break the link between them. You can compare the link between two application programs to the communication established using telephones. For example, a program link is similar to a telephone connection that enables various forms of communication such as human-to-human, modem-to-modem, and facsimile machine–to–facsimile machine.        Figure 11-1 shows a database application on one computer that has initiated a session with a spreadsheet application located on another computer on the network.Figure 11-1    A PPC Toolbox session between two applicationsThe database application’s port name consists of “store data” (the name string) and “database” (the type string). Its location name consists of “Jane Doe’s Macintosh” (the object string), “PPCToolBox” (the type string), and “twilight” (the AppleTalk zone). The spreadsheet application’s port name consists of “display data” (the name string) and “spreadsheet” (the type string). Its location name consists of “Joe Smith’s Macintosh” (the object string), “PPCToolBox” (the type string), and “loading” (the AppleTalk zone).Setting Up Authenticated SessionsNetwork communication must be active to initiate sessions with other computers across a network. The user must activate AppleTalk in the Chooser and enable program linking using the Sharing Setup control panel located in the Control Panels folder inside the System Folder. Figure 11-2 displays the icon for the Sharing Setup control panel. Figure 11-2    The icon for the Sharing Setup control panelFigure 11-3 shows the Sharing Setup control panel.Figure 11-3    The Sharing Setup control panelTo permit other computers to initiate sessions with the owner’s computer, the owner of the computer must click the Start button underneath Program Linking (Start toggles with Stop). The Sharing Setup control panel then indicates “Program linking is on. Click Stop to prevent other users from linking to your shared programs.” To prevent other computers from initiating sessions, an owner simply clicks Stop underneath Program Linking. The Sharing Setup control panel then indicates “Program linking is off. Click Start to allow other users to link to your shared programs.” Clicking the Start or Stop button also enables or disables the transmission of incoming Apple events across the network.If a user clicks the Stop button while there are active incoming sessions (sessions initiated by other users), an alert box (shown in Figure 11-4) appears on the user’s screen.Figure 11-4    The session termination alert boxIf a user clicks OK, all active sessions initiated by other users are immediately terminated. Note that it is still possible for the owner of the computer to initiate sessions, even though other users may not initiate sessions with the owner’s computer.The PPC Toolbox establishes the identity of users through the process of authentication. The authentication mechanism of the PPC Toolbox identifies each user through an assigned name and password. Each session initiated with a port that is located on a remote computer requires authentication (unless guest access is enabled) before a session is permitted. Sessions between applications located on the same computer never require authentication.A computer’s owner can establish access for other users and guests by opening the Users & Groups control panel located in the Control Panels folder. The Users & Groups control panel allows an owner to specify the names and passwords of other users whose computers can initiate sessions with his or her ports across the network. When the computer’s owner opens the Users & Groups control panel, the Guest icon appears. If the owner’s name is specified in the Sharing Setup control panel, an icon with the owner’s name also appears.To specify a particular new user, the owner chooses New User from the File menu. The owner should type in the user’s name. When the owner opens a user icon in the Users & Groups control panel, the Finder displays the users and groups dialog box on the owner’s screen. Figure 11-5 shows the users and groups dialog box for a particular user.Figure 11-5    The users and groups dialog boxTo permit authenticated session requests, the owner can specify a password for each user. The owner allows other users to utilize the PPC Toolbox by clicking the checkbox under Program Linking. If the owner clicks the checkbox again, all active sessions initiated by this particular user are immediately terminated. The user termination alert box (shown in Figure 11-6) is displayed as a warning.Figure 11-6    The user termination alert boxWhen the owner opens a Guest icon in the Users & Groups control panel, the Finder displays the guest dialog box on the owner’s screen. Authentication is not required if the owner permits guest access. Figure 11-7 shows the guest dialog box. Figure 11-7    The guest dialog boxBy clicking the checkbox under Program Linking, the owner permits guests to communicate using the PPC Toolbox or Apple events.Consider this example of the authentication process: one user decides to make a dictionary service available to other users. A second user wishes to employ this service in a word-processing program. Assuming both programs support the PPC Toolbox, the word-processing program attempts to gain access to the dictionary service that is open on the first user’s computer by initiating a session. When the word-processing application requests a session, the PPC Toolbox attempts to authenticate the second user by requesting a user name and a password (unless guest access is enabled). If the authentication process verifies the user’s identity and the dictionary application accepts the request for a session, a session is established and the second user can access the dictionary’s data.Figure 11-8 illustrates the authentication process that occurs when a user attempts to initiate a session.Figure 11-8    The PPC Toolbox authentication processUsing the PPC ToolboxThis section describes how to n    use PPC Toolbox calling conventionsn    open a portn    list all available port locations on the networkn    indicate that a port is available to accept session requestsn    initiate a sessionn    accept and reject session requestsn    read and write data during a sessionn    end a session after data is transmitted and receivedn    close a port when it is no longer needed to transmit or receive datan    invalidate usersTo begin, you must determine whether the PPC Toolbox is available on the user’s computer system by using the Gestalt function with the selector gestaltPPCToolboxAttr. A noErr result code indicates that the PPC Toolbox is present.The Gestalt function returns a combination of the following constants in the response parameter: gestaltPPCToolboxPresent, gestaltPPCSupportsRealTime, gestaltPPCSupportsOutGoing, and gestaltPPCSupportsIncoming.The PPC Toolbox currently supports only sessions in real time. The Gestalt function returns gestaltPPCSupportsRealTime by default. If this bit is not set, you need to initialize the PPC Toolbox.The Gestalt function returns gestaltPPCSupportsOutGoing to indicate support of outgoing sessions across a network of Macintosh computers. If this bit is not set, the user hasn’t enabled AppleTalk in the Chooser.The Gestalt function returns gestaltPPCSupportsIncoming if the user has enabled program linking in the Sharing Setup control panel. If this bit is not set, the user either hasn’t enabled AppleTalk in the Chooser or hasn’t enabled program linking in the Sharing Setup control panel.Use the PPCInit function to initialize the PPC Toolbox.err := PPCInit;Listing 11-1 illustrates how you use the PPCInit function to initialize the PPC Toolbox.Listing 11-1    Initializing the PPC Toolbox using the PPCInit functionFUNCTION MyPPCInit: OSErr;VAR    PPCAttributes: LongInt;    err:                     OSErr;BEGIN    err := Gestalt(gestaltPPCToolboxAttr, PPCAttributes);    IF err = noErr THEN                                        {PPC Toolbox is present}    BEGIN        IF BAND(PPCAttributes, gestaltPPCSupportsRealTime) = 0 THEN        BEGIN                                MyPPCInit := PPCInit;                                {initialize the PPC Toolbox}            {test the attributes for the PPC Toolbox}            err := Gestalt(gestaltPPCToolboxAttr, PPCAttributes);        END;        IF BAND(PPCAttributes, gestaltPPCSupportsOutGoing) <> 0 THEN            {ports can be opened to the outside world}        ELSE            {it's likely that AppleTalk is disabled, so you }            ;        { may want to tell the user to activate AppleTalk }                    { from the Chooser}        IF BAND(PPCAttributes, gestaltPPCSupportsIncoming) <> 0 THEN            {ports can be opened with location names that the }            { outside world can see}        ELSE            {it's likely that program linking is disabled, so }            ;        { you may want to tell the user to start program }                    { linking from the Sharing Setup control panel}    END    ELSE        MyPPCInit := err;END;        Figure 11-9 illustrates a spreadsheet application (on the left) that has initiated a session with a database application (on the right) to exchange data using the PPC Toolbox. This figure includes an example of the sequence of PPC Toolbox routines executed by these applications. Detailed descriptions of the functions appear in the sections that follow.Figure 11-9    Database and spreadsheet applications using the PPC ToolboxTo establish a session, each application must first open a port using the PPCOpen function. The spreadsheet application prepares to receive session requests by calling the PPCInform function. Before initiating a session or opening a port, the database application can let the user browse through the list of available ports (using the PPCBrowser function). If the user decides to communicate with the spreadsheet application, the database application initiates a session with the spreadsheet application’s port using the StartSecureSession function. After the PPC Toolbox authenticates the user name and password of the initiating port, the spreadsheet application accepts the session request (using the PPCAccept function).Once the session is established, the applications exchange information in the form of message blocks (using the PPCRead and PPCWrite functions). During a session, an application can both read from and write message blocks to another application. After the information exchange is done, each application ends the session (PPCEnd) and then closes its port (PPCClose) when it quits.The PPCOpen function returns a port reference number. The port reference number is a reference number for the port through which you are requesting a session. The database application uses the port reference number in subsequent calls to the StartSecureSession and PPCClose functions. The StartSecureSession function returns a session reference number. The session reference number is used to identify the session during the exchange of data. It is used in subsequent calls to the PPCWrite, PPCRead, and PPCEnd functions.The PPCOpen function returns a port reference number that the spreadsheet uses in subsequent calls to the PPCInform and PPCClose functions. The PPCInform function returns a session reference number that is used in subsequent calls to the PPCAccept, PPCRead, PPCWrite, and PPCEnd functions.PPC Toolbox Calling ConventionsMost PPC Toolbox functions can execute synchronously (meaning that the application cannot continue until the function completes execution) or asynchronously (meaning that the application is free to perform other tasks while the function is executing). The PPC Toolbox functions that can only be executed synchronously include PPCInit, PPCBrowser, StartSecureSession, DeleteUserIdentity, and GetDefaultUser. All other PPC Toolbox functions can execute asynchronously or synchronously. Here’s an example: FUNCTION PPCFunction (pb: PPCParamBlockPtr;                              async: Boolean): OSErr;The pb parameter should point to a PPC parameter block. Set the async parameter to TRUE if you want the function to execute asynchronously; set it to FALSE if you want the function to execute synchronously.NoteThe PPCInform, PPCRead, and PPCWrite functions should always be executed asynchronously, because they require interaction from the other application in the session before they complete execution.uThe PPCParamBlockRec data type defines the PPC parameter block.TYPE PPCParamBlockRec =     RECORD        CASE Integer OF        0: (openParam:                            PPCOpenPBRec);                            {PPCOpen params}        1: (informParam:                            PPCInformPBRec);                            {PPCInform params}        2: (startParam:                            PPCStartPBRec);                            {PPCStart params}        3: (acceptParam:                            PPCAcceptPBRec);                            {PPCAccept params}        4: (rejectParam:                            PPCRejectPBRec);                            {PPCReject params}        5: (writeParam:                            PPCWritePBRec);                            {PPCWrite params}        6: (readParam:                            PPCReadPBRec);                            {PPCRead params}        7: (endParam:                            PPCEndPBRec);                            {PPCEnd params}        8: (closeParam:                            PPCClosePBRec);                            {PPCClose params}        9: (listPortsParam:                            IPCListPortsPBRec);                            {IPCListPorts }                                                                { params}    END;For an illustration of the fields of each individual parameter block (such as PPCInformPBRec or IPCListPortsPBRec), see Figure 11-18 on page 11-47.Your application transfers ownership of the PPC parameter block (and any buffers or records pointed to by the PPC parameter block) to the PPC Toolbox until a PPC function completes execution. Once the function completes, ownership of the parameter block (and any buffers or records it points to) is transferred back to your application. If a PPC Toolbox function is executed asynchronously, your program cannot alter memory that might be used by the PPC Toolbox until that function completes.A PPC Toolbox function that is executed asynchronously must specify NIL or the address of a completion routine in the ioCompletion field of the PPC parameter block. You should use the ioResult field to determine the actual result code when an asynchronously executed PPC Toolbox function completes.If you specify NIL in the ioCompletion field, you should poll the ioResult field of the PPC parameter block after the function is called to determine whether the PPC function has completed the requested operation. You should poll the ioResult field within the event loop of your application. If the ioResult field contains a value other than 1, the function has completed execution. Note that you must not poll the ioResult field at interrupt time to determine whether the function has completed execution.If you specify a completion routine in the ioCompletion field, it is called at interrupt time when the PPC Toolbox function completes execution.sWARNINGCompletion routines execute at the interrupt level and must preserve all registers other than A0, A1, and D0–D2. (Note that MPW C and MPW Pascal do this automatically.) Your completion routine must not make any calls to the Memory Manager directly or indirectly, and it can’t depend on the validity of handles to unlocked blocks. The PPC Toolbox preserves the application global register A5.sYou can write completion routines in C, Pascal, or assembly language. A completion routine declared in Pascal has this format:PROCEDURE MyCompletionRoutine (pb: PPCParamBlockPtr);The pb parameter points to the PPC parameter block passed to the PPC Toolbox function.You may call another PPC Toolbox function from within a completion routine, but the function called must be executed asynchronously. It is recommended that you allocate parameter blocks of data type PPCParamBlockRec so that you may reuse the pb parameter to call another PPC Toolbox function from within a completion routine. For example, you should call either the PPCAccept function or the PPCReject function asynchronously from within a PPCInform completion routine to accept or reject the session request.If your application is executing PPC Toolbox functions asynchronously, you may want to define your own record type to hold all data associated with a session. You can attach the data to the end of the parameter block. Here’s an example:TYPE     SessRecHndl = ^SessRecPtr;    SessRecPtr = ^SessRec;    SessRec =     RECORD        pb:                            PPCParamBlockRec;         {must be first }                                                            { item in record}        thePPCPortRec                :            PPCPortRec;        theLocationNameRec:                             LocationNameRec;        theUserName:                             Str32;    END;The additional data elements in your record can be accessed during execution of a completion routine by coercing the pb parameter to a pointer to your record type.Specifying Port Names and Location NamesBefore initiating a session, you must open a port to communicate with other programs. A port name and location name identify each port. An application can open as many ports as it requires as long as each port name is unique within a particular computer. You specify both the port name and the location name in the PPC parameter block.Figure 11-10 illustrates a single Macintosh computer with two applications, and their corresponding port names and location names.To open a port, you need to specify a port name. A port name consists of a name string, a type string, and a script code for localization. For example, you can designate “make memo” as the application’s name string, “word processor” as its type string, and “smRoman” as its script code. A port name is defined by a PPC port record. The PPC port record contains a script code, name string, port kind selector, and type string. The script code is an integer script identifier used for localization. The name string consists of a 32-byte character string that designates the application name. You should keep both the script code and the name string in a resource. The port kind selector is an integer that selects the kind of type string. You should make it consistent internationally. The type string can be either a 32-byte character string or a 4-character creator and a 4-character file type. See the chapter “Finder Interface” of Inside Macintosh: Macintosh Toolbox Essentials for information on creators and file types. See Inside Macintosh: Text for information on script codes and localization.Figure 11-10    Two Macintosh applications and their corresponding portsThe PPCPortRec data type defines the PPC port record.TYPE PPCPortRec =     RECORD        nameScript:                        ScriptCode;                        {script identifier}        name:                        Str32;                        {port name in program }                                                         { linking dialog box}        portKindSelector:                        PPCPortKinds;                        {general category of }                                                        { application}        CASE PPCPortKinds OF                                ppcByString:                        (portTypeStr: Str32);                                ppcByCreatorAndType:                                                         (portCreator: OSType;                                                        portType: OSType);    END;The location name identifies the location of the computer on the network. The PPC Toolbox provides the location name when the user starts up the computer. The location name is specified in the standard Name-Binding Protocol (NBP) form, <object string>:PPCToolBox @<AppleTalk zone>. The object string is the name provided in the Sharing Setup control panel in the Control Panels folder. By default, the type string is “PPCToolBox”. The AppleTalk zone is the zone to which the particular Macintosh computer belongs. For example, “Jane Doe’s Macintosh:PPCToolBox@twilight” specifies the object string, type string, and AppleTalk zone for a particular computer.The LocationNameRec data type defines the location name record. The locationKindSelector field can be set to ppcNoLocation, ppcNBPLocation, or ppcNBPTypeLocation.TYPE LocationNameRec =     RECORD        locationKindSelector: PPCLocationKind;                                                        {which variant}        CASE PPCLocationKind OF            {ppcNoLocation: storage not used by this value}            ppcNBPLocation:                                                                                 (nbpEntity: EntityName); {NBP name entity}            ppcNBPTypeLocation:                                                                (nbpType: Str32);                        {just the NBP type }                                                        { string for the }                                                        { PPCOpen function}    END;The ppcNoLocation constant is used when the location received from or passed to a PPC Toolbox function is the location of the local machine.The ppcNBPLocation constant is used when a full NBP entity name is received from or passed to a PPC Toolbox function.NoteYou should assign an NBP value directly—do not pack it using nbpSetEntity.uThe ppcNBPTypeLocation constant is used only by the PPCOpen function when an alias location name is needed.The NBP type to be used for the alias location name is passed in the location name record’s nbpType field. Alias location names allow you to filter the NBP objects (Macintosh computers) displayed by the program linking dialog box (shown in Figure 11-12 on page 11-22) using the PPCBrowser function. See “Browsing for Ports Using the Program Linking Dialog Box” beginning on page 11-22 for information on the PPCBrowser function.An alias location name could be used to advertise a service (such as a dictionary service) that is available to any application located on the network. For example, “Joe Smith’s Macintosh: dictionary@ozone” specifies the object string, type string, and AppleTalk zone for a particular dictionary service.To search for all dictionary services available within a zone, you use the PPCBrowser function and a filter. Figure 11-11 illustrates a Macintosh dictionary service application, its corresponding port name, and its alias location name.Figure 11-11    The PPC Toolbox and a dictionary service applicationOpening a PortTo open a port and associate a name with it, use the PPCOpen function. Listing 11-2 illustrates how you use the PPCOpen function to open a port. In this listing, the name is “Inside Macintosh” and the port type string is “Example”. The location name is <object string>:PPC Example@<AppleTalk zone>.Listing 11-2    Opening a PPC portFUNCTION MyPPCOpen(VAR thePortRefNum: PPCPortRefNum;                         VAR nbpRegisteredFlag: Boolean): OSErr;VAR    thePPCOpenPBRec:                                 PPCOpenPBRec;    thePPCPortRec:                                 PPCPortRec;    theLocationNameRec:                                 LocationNameRec;BEGIN    WITH thePPCPortRec DO    BEGIN        {nameScript and name should be resources to allow }        { easy localization}        nameScript := smRoman;                                {Roman script}        name := 'Inside Macintosh';        {the port type should always be hard-coded to allow the }        { application to find ports of a particular type even }        { after the name is localized}        portKindSelector := ppcByString;        portTypeStr := 'Example';    END;    WITH theLocationNameRec DO    BEGIN        locationKindSelector := ppcNBPTypeLocation;        nbpType := 'PPC Example';    END;    WITH thePPCOpenPBRec DO    BEGIN        serviceType := ppcServiceRealTime;        resFlag := 0;                                            {must be 0 for 7.0}        portName := @thePPCPortRec;        locationName := @theLocationNameRec;        networkVisible := TRUE;                                            {make this a visible }                                                    { entity on the network}    END;    MyPPCOpen := PPCOpen(@thePPCOpenPBRec, FALSE);    {synchronous}    thePortRefNum := thePPCOpenPBRec.portRefNum;    nbpRegisteredFlag := thePPCOpenPBRec.nbpRegistered;END;The PPCOpen function opens a port with the port name and location name specified in the name and location fields of the parameter block. When the PPCOpen function completes execution, the portRefNum field returns the port reference number. You can use the port reference number in the PPCInform, PPCStart, StartSecureSession, and PPCClose functions to refer to the port you have opened.Browsing for Ports Using the Program Linking Dialog BoxBefore initiating a session, you can use either the PPCBrowser function or the IPCListPorts function to locate a port to communicate with.Use the PPCBrowser function to display the program linking dialog box (shown in Figure 11-12) on the user’s screen.NoteBecause this function displays a dialog box on the user’s screen, you must not call the PPCBrowser function from an application that is running in the background.uFigure 11-12    The program linking dialog boxIn the program linking dialog box, the user selects the computer, zone, and application. The zone list is not displayed if there is no network connection. Figure 11-13 shows the dialog box without the zone list.Figure 11-13    The program linking dialog box without a zone listAs shortcuts for the user, the program linking dialog box supports standard keyboard equivalents. Pressing Command-period or the Esc (Escape) key selects Cancel—pressing Enter or Return selects the OK button.Each list is sorted in alphabetical order. As in the Chooser, the current list is indicated by a thick outline around its border. The program linking dialog box supports keyboard navigation and use of the arrow keys to select items from the current list. Pressing Tab or clicking the rectangle of another list switches the current list. Pressing Shift-Tab reverses the order in which the lists are selected. In addition, double-clicking an application name in the Programs list of the program linking dialog box is equivalent to clicking the OK button.The PPCBrowser function allows users to browse for PPC ports.err := PPCBrowser (prompt, applListLabel, defaultSpecified,                          theLocation, thePortInfo, portFilter,                          theLocNBPType);If the defaultSpecified parameter is TRUE, the PPCBrowser function tries to select the PPC port specified by the parameters theLocation and thePortInfo when the program linking dialog box first appears. If the default cannot be found, the PPCBrowser function selects the first PPC port in the list.An application can open multiple ports as long as each port name is unique within a particular computer. Unique ports can have duplicate name fields but different types. For example, you can designate “make memo” as the application’s name string and “word processor” as its type string. You can also designate a separate port as “make memo” (the application’s name string) and “text only” (its type string).In such a case, the PPCBrowser function does a secondary sort based on the port type. Ports with a type selector of ppcByCreatorAndType are displayed before ppcByString ports, and types are sorted alphabetically within each type selector.The PPCBrowser function uses the IPCListPorts function to obtain the list of existing ports on a particular computer within a particular zone. The portFilter parameter of the PPCBrowser function allows you to filter the list of PPC ports before it displays them in the program linking dialog box. If you set the portFilter parameter to NIL, the PPCBrowser function displays the names of all the existing PPC ports returned by the IPCListPorts function. If you do not set the portFilter parameter to NIL, you must set it to a pointer to a port filter function that you create.Listing 11-3 illustrates how you use a sample port filter function. In this listing, the MyBrowserPortFilter function returns TRUE for ports with the port type string “Example”.Listing 11-3    Using a port filter functionFUNCTION MyBrowserPortFilter(theLocationNameRec: LocationNameRec;                                      thePortInfoRec: PortInfoRec)                                      : Boolean;BEGIN    IF thePortInfoRec.name.portKindSelector = ppcByString THEN        IF thePortInfoRec.name.portTypeStr = 'Example' THEN            MyBrowserPortFilter := TRUE        ELSE             MyBrowserPortFilter := FALSE    ELSE         MyBrowserPortFilter := FALSE;END;The PPCBrowser function calls your filter function once for each port on the selected computer. Your function should return TRUE for each port you want to display in the program linking dialog box, and FALSE for each port that you do not want to display. Do not modify the data in the filter function parameters theLocationNameRec and thePortInfoRec. The PPCBrowser function returns the selected port name in the parameter thePortInfo. The IPCListPorts function returns the port names in the area of memory pointed to by the bufferPtr field of the IPCListPorts parameter block. Both functions specify each port name in a port information record.TYPE PortInfoRec =    RECORD        filler1:                    SignedByte;                        {space holder}        authRequired:                    Boolean;                        {authentication required}        name:                    PPCPortRec;                        {port name}    END;If the authRequired field returns TRUE, the port requires authentication before a session can begin. You should use the StartSecureSession function to initiate a session with this port. If this field returns FALSE, you can use either the PPCStart function or the StartSecureSession function to initiate a session. See “Initiating a PPC Session” beginning on page 11-29 for detailed information. The name field of the port information record specifies an available port name.Listing 11-4 illustrates how you use the PPCBrowser function to display the program linking dialog box in order to obtain the location and name of a port chosen by the user. In this listing, the PPCBrowser function builds lists of zones (shown in the AppleTalk Zones list of the program linking dialog box), objects (shown in the Macintoshes list), and ports (shown in the Programs list). In this example, the PPCBrowser function next tries to default to object “Moof™” in the “Twilight” zone. If it matches the object and zone, it also tries to default to the port “Inside Macintosh” with the port type “Example”.Note that the data in the records LocationNameRec and PortInfoRec is used to match the names in the program linking dialog box. The data has nothing to do with the NBP type used by NBPLookup or the filtered PPC ports that show up in the program linking dialog box. The NBPLookup function uses the NBP type supplied in theLocNBPType. The PPC port names are filtered using the MyBrowserPortFilter function shown in Listing 11-3 on page 11-24.Listing 11-4    Browsing through dictionary service portsFUNCTION MyPPCBrowser(VAR theLocationNameRec: LocationNameRec;                             VAR thePortInfoRec: PortInfoRec): OSErr;VAR    prompt:                             Str255;    applListLabel:                             Str255;    defaultSpecified:                             Boolean;    theLocNBPType:                             Str32;BEGIN    prompt := 'Choose an example to link to:';    applListLabel := 'Examples';    defaultSpecified := TRUE;    WITH theLocationNameRec DO    BEGIN        locationKindSelector := ppcNBPLocation;        WITH nbpEntity DO        BEGIN            objStr := 'Moof™';            {typeStr is ignored}            zoneStr := 'Twilight';        END;    END;    WITH thePortInfoRec.name DO    BEGIN        {nameScript and name should be resources to allow easy }        { localization}        nameScript := smRoman;                                {Roman script}        name := 'Inside Macintosh';        {the port type should always be hard-coded to allow the }        { application to find ports of a particular type even }        { after the name is localized}        portKindSelector := ppcByString;        portTypeStr := 'Example';    END;    {when building the list of objects (Macintoshes), }    { show only those with the NBP type "PPC Example"}    theLocNBPType := 'PPC Example';                                            {match this NBP type}    MyPPCBrowser := PPCBrowser(prompt, applListLabel,                                         defaultSpecified,                                        theLocationNameRec,                                        thePortInfoRec,                                        @MyBrowserPortFilter,                                        theLocNBPType);END;Obtaining a List of Available PortsTo generate a list of ports without displaying dialog boxes, you can use the IPCListPorts function. The IPCListPorts function allows you to obtain a list of ports on a particular computer within a particular zone. To obtain a list of ports, several steps are required. First, use the GetZoneList function to obtain a list of zones. Next, you must use the PLookupName function to obtain a list of computers with ports. After establishing the zone and the computer, you can use the IPCListPorts function to obtain the list of available ports. See Inside Macintosh: Networking for information on the GetZoneList and PLookupName functions.Listing 11-5 illustrates how you use the IPCListPorts function to obtain a list of ports on a particular computer. This function returns a list of port information records in the buffer pointed to by the parameter thePortInfoBufferPtr. The actual number of port information records is returned in the parameter theActualCount.Listing 11-5    Using the IPCListPorts function to obtain a list of portsFUNCTION MyIPCListPorts             (theStartIndex: Integer;              theRequestCount: Integer; VAR theActualCount: Integer;              theObjStr: Str32; theZoneStr: Str32;              thePortInfoBufferPtr: PortInfoArrayPtr): OSErr;VAR    theIPCListPortsPBRec:                                     IPCListPortsPBRec;    thePPCPortRec:                                     PPCPortRec;    theLocationNameRec:                                    LocationNameRec;BEGIN    {list all PPC ports at the specified location}    WITH thePPCPortRec DO    BEGIN        nameScript := smRoman;        name := '=';                            {match all names}        portKindSelector := ppcByString;        portTypeStr := '=';                            {match all types}     END;    WITH theLocationNameRec DO    BEGIN        locationKindSelector := ppcNBPLocation;        WITH nbpEntity DO        BEGIN            {set NBP object from the list returned by NBPLookup}            objStr := theObjStr;            {set NBP type, in this example to "PPC Example"; if you }            { don't supply your own NBP type, use "PPCToolBox"}            typeStr := 'PPC Example';            {set NBP zone from the list returned by GetZoneList}            zoneStr := theZoneStr;        END;    END;    WITH theIPCListPortsPBRec DO    BEGIN        startIndex := theStartIndex;        requestCount := theRequestCount;        portName := @thePPCPortRec;        locationName := @theLocationNameRec;        bufferPtr := thePortInfoBufferPtr;    END;    MyIPCListPorts := IPCListPorts(@theIPCListPortsPBRec, FALSE);    theActualCount := theIPCListPortsPBRec.actualCount;END;The IPCListPorts function returns information about ports that are on the computer specified in the locationName field of the list ports parameter block. If you set the locationName field to NIL or if you set the locationKindSelector field in the location name record to ppcNoLocation, the IPCListPorts function returns only the port names for the local computer.The bufferPtr field points to an area of memory that contains the requested port names. You are responsible for allocating enough memory to hold the requested port names. The buffer length must be equal tosizeof(PortInfoRec) * requestCountPreparing for a SessionTo communicate, you can open a port for your application and make it available to receive session requests, to initiate sessions, or both. Applications that are able to receive session requests can choose to accept or reject incoming session requests. Before an application can accept and establish a session with another application, the PPC Toolbox authenticates the initiating user (unless guest access is enabled or the applications are located on the same computer). Once a session begins, the two applications can exchange data with each other. Initiating a PPC SessionOnce you have established the name and the location of the port that you want to communicate with, you can initiate a session. You can use either the StartSecureSession function or the PPCStart function to initiate a session. The StartSecureSession function displays several dialog boxes to identify each user who requests a session. You may prefer to use the PPCStart function for low-level code such as that used for drivers, which typically do not provide a user interface. You may also prefer to use PPCStart when the application you are initiating a session with does not require authentication. The IPCListPorts and PPCBrowser functions return information about whether a particular port requires authentication.NoteDo not call the StartSecureSession function from an application that is running in the background, because the function displays several dialog boxes on the user’s screen.uThe StartSecureSession function provides authentication services to identify each user who requests a session. This function combines the processes of prompting for user name and password and initiating a session into one synchronous procedure call. If authentication fails, the PPC Toolbox rejects the incoming session request.err := StartSecureSession (pb, userName, useDefault, allowGuest,                                     guestSelected, prompt);Set the useDefault parameter to TRUE if you want the StartSecureSession function to use the default user identity (described later in this section). If the default user identity cannot be authenticated, the StartSecureSession function displays a dialog box to allow a user to log on. Figure 11-14 shows the user identity dialog box.Figure 11-14    The user identity dialog boxThe prompt parameter of the StartSecureSession function allows you to specify a line of text that the dialog box can display. The allowGuest parameter specifies whether to enable the Guest radio button. If a port requires authentication, you should set this parameter to FALSE.The userName parameter specifies the name of the user who is attempting to initiate a session. If the user name is not specified, the user identity dialog box appears on the user’s screen with the owner name provided from the Sharing Setup control panel. If the user enters an invalid password, the StartSecureSession function displays the dialog box shown in Figure 11-15.Figure 11-15    The incorrect password dialog boxAfter the user clicks OK, the user identity dialog box reappears in the foreground so that the user can enter the password again.If the user’s name is invalid, the StartSecureSession function displays the dialog box shown in Figure 11-16.Figure 11-16    The invalid user name dialog boxAfter the user clicks OK, the user identity dialog box reappears so that the user can enter a new user name.The StartSecureSession function remains in this loop until a secure session is initiated or the user clicks Cancel in the user identity dialog box. If a secure session is initiated, StartSecureSession returns the user reference number in the corresponding field in the PPCStart parameter block. The user reference number represents the user name and password. A user reference number of 0 indicates that a session has been initiated with guest access. See “Setting Up Authenticated Sessions” beginning on page 11-6 for more information.Before your application quits, you need to invalidate all user reference numbers obtained with the StartSecureSession function except for the default user reference number and the guest reference number (0). See “Invalidating Users” on page 11-44 for detailed information.Listing 11-6 illustrates how to use the StartSecureSession function to establish an authenticated session. This listing shows only one session, although your application may conduct multiple sessions at one time.Listing 11-6    Using the StartSecureSession function to establish a sessionFUNCTION MyStartSecureSession(thePortInfoPtr: PortInfoPtr;                                         theLocationNamePtr: LocationNamePtr;                                         thePortRefNum: PPCPortRefNum;                                         VAR theSessRefNum: PPCSessRefNum;                                         VAR theUserRefNum: LongInt;                                         VAR theRejectInfo: LongInt;                                         VAR userName: Str32;                                         VAR guestSelected: Boolean): OSErr;VAR    thePPCStartPBRec: PPCStartPBRec;    useDefault:                         Boolean;    allowGuest:                         Boolean;    err:                         OSErr;BEGIN    WITH thePPCStartPBRec DO    BEGIN        ioCompletion := NIL;        portRefNum := thePortRefNum;                                            {from the PPCOpen function}        serviceType := ppcServiceRealTime;        resFlag := 0;        portName := @thePortInfoPtr^.name;                                                 {from the PPCBrowser}        locationName := theLocationNamePtr;     {from the PPCBrowser}        userData := 0;                        {application-specific data that the }                                { PPCInform function sees}    END;    {try to connect with default user identity}    useDefault := TRUE;    {highlight the Guest button appropriately}    allowGuest := NOT thePortInfoPtr^.authRequired;    err := StartSecureSession(@thePPCStartPBRec, userName,                                       useDefault, allowGuest,                                      guestSelected, stringPtr(NIL)^);    IF err = noErr THEN    BEGIN        theSessRefNum := thePPCStartPBRec.sessRefNum;        theUserRefNum := thePPCStartPBRec.userRefNum;    END    ELSE        IF err = userRejectErr THEN            {return rejectInfo from the PPCReject function}            theRejectInfo := thePPCStartPBRec.rejectInfo;    MyStartSecureSession := err;END;For low-level code such as that used for drivers (which typically do not provide a user interface), you can use the PPCStart function instead of the StartSecureSession function to initiate a session. You can also use the IPCListPorts function (instead of displaying the program linking dialog box) to obtain a list of ports.If the authRequired field of the port information record contains FALSE, the port allows guest access. If the authRequired field of the port information record contains TRUE, use the PPCStart function and the user reference number obtained previously from the StartSecureSession function to reestablish an authenticated session.You can also attempt to log on as the default user using the GetDefaultUser function to obtain the default user reference number and the default user name. The default user name is established after the owner starts up the computer.err := GetDefaultUser (userRef, userName);The userRef parameter is a reference number that represents the user name and password of the default user. The userName parameter contains the owner name that is specified in the Sharing Setup control panel.The GetDefaultUser function returns an error when the default user identity does not exist (no name is specified in the Sharing Setup control panel) or the user is not currently logged on.Listing 11-7 illustrates how you use the PPCStart function to initiate a session. The PPCStart function uses the port information record and the location name record to attempt to open a session with the selected PPC port.Listing 11-7    Initiating a session using the PPCStart functionFUNCTION MyPPCStart(thePortInfoPtr: PortInfoPtr;                             theLocationNamePtr: LocationNamePtr;                             thePortRefNum: PPCPortRefNum;                             VAR theSessRefNum: PPCSessRefNum;                             VAR theUserRefNum: LongInt;                             VAR theRejectInfo: LongInt): OSErr;VAR    thePPCStartPBRec: PPCStartPBRec;    userName:                         Str32;    err:                         OSErr;BEGIN    WITH thePPCStartPBRec DO    BEGIN        ioCompletion := NIL;         portRefNum := thePortRefNum;                                            {from the PPCOpen function}        serviceType := ppcServiceRealTime;        resFlag := 0;        portName := @thePortInfoPtr^.name;                                                 {destination port}        locationName := theLocationNamePtr;                                                 {destination location}        userData := 0;                        {application-specific data for PPCInform}    END;    err := GetDefaultUser(thePPCStartPBRec.userRefNum, userName);    IF err <> noErr THEN        thePPCStartPBRec.userRefNum := 0;    IF thePortInfoPtr^.authRequired AND         (thePPCStartPBRec.userRefNum = 0) THEN        {port selected doesn't allow guests & you don't have a }        { default user ref number so you can't log on to this port}        err := authFailErr    ELSE        {attempt to log on}        err := PPCStart(@thePPCStartPBRec, FALSE);    IF err = noErr THEN    BEGIN        theSessRefNum := thePPCStartPBRec.sessRefNum;        theUserRefNum := thePPCStartPBRec.userRefNum;    END    ELSE        IF err = userRejectErr THEN            {return rejectInfo from the PPCReject function}            theRejectInfo := thePPCStartPBRec.rejectInfo;    MyPPCStart := err;END;The port to which you wish to connect must have an outstanding PPCInform function to successfully start a session. You cannot initiate a session with a port that is not able to receive session requests. If the port is open, has an outstanding PPCInform function posted, and accepts your session request, the PPCStart function returns a noErr result code and a valid session reference number. This session reference number is used to identify the session during the exchange of data.Receiving Session RequestsYour application can open as many ports as it requires as long as each port name is unique within a particular computer. A single port can support a number of communication sessions. To allow a port to receive session requests, use the PPCInform function. (Note that you must open a port to obtain a port reference number before calling the PPCInform function.) A port may have any number of outstanding PPCInform requests.Listing 11-8 illustrates how you use the PPCInform function to allow a port to receive session requests. In this listing, the parameter thePPCParamBlockPtr points to a PPC parameter block record allocated by the application. The portRefNum, autoAccept, portName, locationName, userName, and ioCompletion parameters of the PPC parameter block record must be supplied. If you want to automatically accept all incoming session requests, you can set the autoAccept field in the PPCInform parameter block. Listing 11-8    Using the PPCInform function to enable a port to receive sessionsFUNCTION MyPPCInform(thePPCParamBlockPtr: PPCParamBlockPtr;                             thePPCPortPtr: PPCPortPtr;                            theLocationNamePtr: LocationNamePtr;                             theUserNamePtr: stringPtr;                             thePortRefNum: PPCPortRefNum): OSErr;BEGIN    WITH thePPCParamBlockPtr^.informParam DO    BEGIN        ioCompletion := @MyInformCompProc;        portRefNum := thePortRefNum;                                        {from the PPCOpen function}        autoAccept := FALSE;                                        {the completion routine }                                                { handles accepting or }                                                { rejecting requests}        portName := thePPCPortPtr;        locationName := theLocationNamePtr;        userName := theUserNamePtr;    END;    MyPPCInform := PPCInform(PPCInformPBPtr(thePPCParamBlockPtr),                                        TRUE);            {asynchronous}END;A PPC parameter block record is used instead of a PPCInform parameter block record so that the same parameter block can be reused to make other PPC Toolbox calls from the PPCInform completion routine. The parameter block and the records it points to cannot be deallocated until all calls that use the parameter block and records have completed.You should make the call to PPCInform asynchronously. For each function that you use asynchronously, you should provide a completion routine. The completion routine gets called at interrupt time when the PPCInform function completes.Listing 11-9 illustrates a completion routine for a PPCInform function. You can use the data passed into your PPCInform completion routine (user name, user data, port name, and location name) to determine whether to accept or reject the session request.Listing 11-9    Completion routine for a PPCInform functionPROCEDURE MyInformCompProc(pb: PPCParamBlockPtr);BEGIN    IF pb^.informParam.ioResult = noErr THEN    BEGIN        {decide if this session should be accepted or rejected by }        { looking at data supplied by the session requester}        IF pb^.informParam.userData <> -1 THEN            DoPPCAccept(pb)        ELSE            DoPPCReject(pb);    END    ELSE        {use a global to tell the application that }        { PPCParamBlockRec and the records it points to }        { can be deallocated}        gPBInUse := FALSE;END;When the PPCInform function completes, the MyInformCompProc procedure determines whether to accept or reject the incoming session request. It does this by calling PPCAccept or PPCReject, as described in the next section.Accepting or Rejecting Session RequestsUse the PPCAccept function or the PPCReject function to accept or reject an incoming session request.sWARNINGIf the PPCInform function (with the autoAccept parameter set to FALSE) returns a noErr result code, you must call either the PPCAccept function or the PPCReject function. The computer trying to initiate a session (using the StartSecureSession function or the PPCStart function) waits (hangs) until the session attempt is either accepted or rejected, or until an error occurs.sListing 11-10 illustrates how you use the PPCAccept function to accept a session request. This listing reuses the parameter block used in the PPCInform function, so the sessRefNum field already contains the session reference number needed by the PPCAccept function.Listing 11-10    Accepting a session request using the PPCAccept functionPROCEDURE DoPPCAccept(pb: PPCParamBlockPtr);VAR    err:        OSErr;BEGIN        {accept the session}    pb^.acceptParam.ioCompletion := @MyAcceptCompProc;    {the sessRefNum field is set by the PPCInform function}    err := PPCAccept(@pb^.acceptParam, TRUE);                                                        {asynchronous}END;For each function that you use asynchronously, you should provide a completion routine. Listing 11-11 illustrates a completion routine for a PPCAccept function. This procedure gets called at interrupt time when the PPCAccept function completes. If there are no errors, it sets the global variable gSessionOpen to TRUE. The global variable gPBInUse is set to FALSE to inform the application that the parameter block and the records it points to are no longer in use.You can use the session reference number in subsequent PPCWrite, PPCRead, and PPCEnd functions once a session is accepted.Listing 11-11    Completion routine for a PPCAccept functionPROCEDURE MyAcceptCompProc(pb: PPCParamBlockPtr);BEGIN    IF pb^.acceptParam.ioResult = noErr THEN        {accept completed so the session is completely open}        gSessionOpen := TRUE;    {use a global to tell the application that PPCParamBlockRec }    { and the records it points to can be deallocated}    gPBInUse := FALSE;END;Use the PPCReject function to reject an incoming session request. Listing 11-12 illustrates how you use the PPCReject function to reject a session request. This listing reuses the parameter block used in the PPCInform function, so the sessRefNum field already contains the session reference number needed by the PPCReject function.Listing 11-12    Rejecting a session request using the PPCReject functionPROCEDURE DoPPCReject(pb: PPCParamBlockPtr);VAR    err:        OSErr;BEGIN {reject the session}    WITH pb^.rejectParam DO    BEGIN        ioCompletion := @MyRejectCompProc;        {the sessRefNum field is set by the PPCInform function}        rejectInfo := -1;    END;    err := PPCReject(@pb^.rejectParam, TRUE);                                                        {asynchronous}END;Listing 11-13 illustrates a completion routine for a PPCReject function. This procedure is called at interrupt time when the PPCReject function completes. In this example, the global variable gPBInUse is set to FALSE to inform the application that the parameter block and the records it points to are no longer in use.Listing 11-13    Completion routine for a PPCReject functionPROCEDURE MyRejectCompProc(pb: PPCParamBlockPtr);BEGIN    {use a global to tell the application that PPCParamBlockRec }    { and the records it points to can be deallocated}    gPBInUse := FALSE;END;Exchanging Data During a PPC SessionAfter a session begins, each application can send data to and receive data from the other using a sequence of message blocks. The PPC Toolbox treats each message block as a byte stream and does not interpret the contents of the message block. The size of a message block can be between 0 and (232–1) bytes. The PPC Toolbox treats the buffer size as an unsigned long integer.The PPC Toolbox delivers the message blocks in the same sequence as they are sent and without duplicates. In Figure 11-17, an application transmits message blocks during a session.Figure 11-17    Transmitting message blocksFor each message block, you specify a block creator, block type, and user data. The first PPCWrite function that you use to create a new message block sets the attributes for the block. The PPCRead function returns the block creator, block type, and user data attributes for the current message block when the call completes.Although the PPC Toolbox does not interpret these attributes, they can give the receiving application information about how to process the contents of the message block. For example, a database application may specify, in the block creator field, a counter to indicate the block number (block number 20 of 30 total blocks). This application could also specify a code, such as 'DREC', in the block type field to indicate that the information it contains is a database record. In addition, this application could specify, in the user data field, the length of the message block.Reading Data From an ApplicationAn application can both read from and write data to another application during a session. Use the PPCRead function during a session to read incoming blocks of data from another application.Once a session is initiated, you should have a PPCRead function pending. You can issue a PPCRead function from inside a completion routine. This provides you with immediate notification if an error condition arises or the session closes. The blockCreator, blockType, and userData fields are returned for the block you are reading. (These fields are set by the PPCWrite function.) To determine whether there is additional data to be read, check the more field. The value FALSE indicates the end of a message block.Listing 11-14 illustrates how you use the PPCRead function to read data during a session.Listing 11-14    Using the PPCRead function to read data during a sessionFUNCTION MyPPCRead(thePPCReadPBPtr: PPCReadPBPtr;                             theSessRefNum: PPCSessRefNum;                             theBufferLength: Size;                             theBufferPtr: Ptr): OSErr;BEGIN    WITH thePPCReadPBPtr^ DO    BEGIN        ioCompletion := NIL;        sessRefNum := theSessRefNum;                                        {from PPCStart or PPCInform}        bufferLength := theBufferLength;        bufferPtr := theBufferPtr;    END;    MyPPCRead := PPCRead(thePPCReadPBPtr, TRUE);                                                            {asynchronous}END;You should make any calls to PPCRead asynchronously. You can provide a completion routine that will be called when the PPCRead function has completed, or you can poll the ioResult field of the PPC parameter block to determine whether the PPCRead function has completed. A PPCRead completion routine can issue another asynchronous PPC Toolbox call or set global variables. If another PPC Toolbox call is made from a completion routine, then the PPCRead function must use a record of data type PPCParamBlockRec instead of type PPCReadPBRec.Listing 11-15 illustrates a function that can be used to poll the ioResult field of a record of data type PPCReadPBRec. The function returns TRUE when the PPCRead function associated with PPCReadPBRec has completed.Listing 11-15    Polling the ioResult field to determine if a PPCRead function has completedFUNCTION MyReadComplete(thePPCReadPBPtr: PPCReadPBPtr;                                 VAR err: OSErr): Boolean;BEGIN    err := thePPCReadPBPtr^.ioResult;    MyReadComplete := err <> 1;END;Sending Data to an ApplicationUse the PPCWrite function to send a message block during a session specified by the session reference number.You should call the PPCWrite function asynchronously. You can provide a completion routine that will be called when the PPCWrite function has completed, or you can poll the ioResult field of the PPC parameter block to determine whether the PPCWrite function has completed. A PPCWrite completion routine can issue another PPC Toolbox call or set global variables. If another PPC Toolbox call is made from a completion routine, then the PPCWrite function must use a record of data type PPCParamBlockRec instead of type PPCWritePBRec. Note that message blocks are sent in the order in which they are written.Listing 11-16 illustrates how you use the PPCWrite function to write data during a session.Listing 11-16    Using the PPCWrite function to write data during a sessionFUNCTION MyPPCWrite(thePPCWritePBPtr: PPCWritePBPtr;                          theSessRefNum: PPCSessRefNum;                          theBufferLength: Size;                          theBufferPtr: Ptr): OSErr;BEGIN    WITH thePPCWritePBPtr^ DO    BEGIN        ioCompletion := NIL;        sessRefNum := theSessRefNum;                                        {from PPCStart or PPCInform}        bufferLength := theBufferLength;        bufferPtr := theBufferPtr;        more := FALSE;                                {no more data to read}        userData := 0;                                {application-specific data}        blockCreator := '????';                                {application-specific data}        blockType := '????';                                {application-specific data}    END;    MyPPCWrite := PPCWrite(thePPCWritePBPtr, TRUE); {asynchronous}END;The first PPCWrite function that you use to create a new message block sets the block creator, block type, and user data attributes for the block. These attributes are returned to the application when it reads from the message block. Set the more field to FALSE to indicate the end of the message block or set this field to TRUE if you want to append additional data to a message block.Listing 11-17 illustrates a function that can be used to poll the ioResult field of a record of data type PPCWritePBRec. The function returns TRUE when the PPCWrite function associated with PPCWritePBRec has completed.Listing 11-17    Polling the ioResult field to determine if a PPCWrite function has completedFUNCTION MyWriteComplete(thePPCWritePBPtr: PPCWritePBPtr;                                 VAR err: OSErr): Boolean;BEGIN    err := thePPCWritePBPtr^.ioResult;    MyWriteComplete := err <> 1;END;Ending a Session and Closing a PortAfter data is written and read in, use the PPCEnd function to end the session (identified by the session reference number). You may receive an error if you use the PPCEnd function to end a session that has already been terminated.Listing 11-18 illustrates how you use the PPCEnd function to end a session.Listing 11-18    Ending a PPC session using the PPCEnd functionFUNCTION MyPPCEnd(theSessRefNum: PPCSessRefNum): OSErr;VAR    thePPCEndPBRec: PPCEndPBRec;BEGIN    thePPCEndPBRec.sessRefNum := theSessRefNum;    MyPPCEnd := PPCEnd(@thePPCEndPBRec, FALSE);                                                                {synchronous}END;The PPCEnd function causes all calls to the PPCRead and PPCWrite functions to complete (with a sessClosedErr result code) and invalidates the session reference number. The PPCEnd function also releases any PPC Toolbox resources so that they can be reused.Use the PPCClose function to close the port specified by the port reference number. When you close a port, all sessions associated with a port are ended. Any active asynchronous calls associated with a session then call their completion routines (if they have one).Listing 11-19 illustrates how you use the PPCClose function to close a port.Listing 11-19    Closing a PPC port using the PPCClose functionFUNCTION MyPPCClose(thePortRefNum: PPCPortRefNum): OSErr;VAR    theClosePBRec: PPCClosePBRec;BEGIN    theClosePBRec.portRefNum := thePortRefNum;                                                                 {from PPCOpen}    MyPPCClose := PPCClose(@theClosePBRec, FALSE);                                                                {synchronous}END;In this example, the call to PPCClose is made synchronously.Invalidating UsersIt is your responsibility to invalidate all user reference numbers obtained with the StartSecureSession function before your application quits. However, while your application remains open, you may want to keep track of a user reference number to start a session with a port, end it, and then later start another session with the same port.Use the DeleteUserIdentity function to invalidate the user reference number for a particular user.err := DeleteUserIdentity (userRef);The DeleteUserIdentity function removes a user by invalidating the specified user reference number. Note that you cannot invalidate the guest reference number (0) and, in most cases, you should not dispose of the default user reference number.Listing 11-20 illustrates how you use the DeleteUserIdentity function to invalidate a user reference number obtained from a StartSecureSession function. The sample code does not invalidate the user reference number if it is either the default user reference number or the guest reference number (0).Listing 11-20    Using the DeleteUserIdentity function to invalidate a user identityFUNCTION MyDeleteNewUserRefNum(newUserRef: LongInt): OSErr;VAR    err:                     OSErr;    defUserRef:                     LongInt;    defUserName:                     Str32;BEGIN    IF newUserRef <> 0 THEN    BEGIN        {user reference number passed was not the guest}        err := GetDefaultUser(defUserRef, defUserName);        IF err = noErr THEN        BEGIN            {there is a default user}            IF newUserRef <> defUserRef THEN                {new user ref number isn't the default user ref num, }                { so ok to delete}                err := DeleteUserIdentity(newUserRef);        END        ELSE            {there is no default, so delete new user ref num}                        err := DeleteUserIdentity(newUserRef);        MyDeleteNewUserRefNum := err;    END    ELSE {user reference number passed was the guest}        MyDeleteNewUserRefNum := noErr;END;PPC Toolbox ReferenceThis section describes the data structures and routines that are specific to the PPC Toolbox. The section “PPC Toolbox Routines” beginning on page 11-50 describes PPC Toolbox routines. “Application-Defined Routines” beginning on page 11-77 describes completion routines and port filter functions.Data StructuresThis section describes the PPC parameter block, PPC port record, location name record, and port information record. The PPC Toolbox Parameter BlockPPC Toolbox functions require a pointer to a PPC parameter block. You must fill out any fields of the parameter block that the specific PPC Toolbox function requires. TYPE     PPCParamBlockRec =     RECORD        CASE Integer OF        0: (openParam:                            PPCOpenPBRec);                            {PPCOpen params}        1: (informParam:                            PPCInformPBRec);                            {PPCInform params}        2: (startParam:                            PPCStartPBRec);                            {PPCStart params}        3: (acceptParam:                            PPCAcceptPBRec);                            {PPCAccept params}        4: (rejectParam:                            PPCRejectPBRec);                            {PPCReject params}        5: (writeParam:                            PPCWritePBRec);                            {PPCWrite params}        6: (readParam:                            PPCReadPBRec);                            {PPCRead params}        7: (endParam:                            PPCEndPBRec);                            {PPCEnd params}        8: (closeParam:                            PPCClosePBRec);                            {PPCClose params}        9: (listPortsParam:                            IPCListPortsPBRec);                            {IPCListPorts }                                                                { params}    END;Figure 11-18 on the next page shows the PPC Toolbox parameter blocks. Note that the reserved fields are not included in the illustration. The qLink, csCode, intUse, intUsePtr, and reserved fields are used internally by the PPC Toolbox. Your application should not rely on the PPC Toolbox to preserve these fields across calls.Your application transfers ownership of the PPC Toolbox parameter block (and any buffers or records pointed to by the PPC Toolbox parameter block) to the PPC Toolbox until a PPC function is complete. Once the function completes, ownership of the parameter block (and any buffers or records it points to) is transferred back to your application. If a PPC Toolbox function is executed asynchronously, your program cannot alter memory that might be used by the PPC Toolbox until that function completes.Figure 11-18    The PPC Toolbox parameter blocksA PPC Toolbox function that is executed asynchronously must specify NIL or the address of a completion routine in the ioCompletion field of the PPC parameter block. The ioResult field should be used to determine the actual result code when an asynchronously executed PPC Toolbox function completes. If you specify a completion routine in the ioCompletion field, it is called at interrupt time when the PPC Toolbox function completes execution. See page 11-78 for the routine declaration for a completion routine.The PPC Port RecordA PPC port name is defined by a PPC port record. The PPCPortRec data type defines the PPC port record.TYPE PPCPortRec =     RECORD        nameScript:                        ScriptCode;                        {script identifier}        name:                        Str32;                        {port name in program }                                                         { linking dialog box}        portKindSelector:                        PPCPortKinds;                        {general category of }                                                        { application}        CASE PPCPortKinds OF                                    ppcByString:                        (portTypeStr: Str32);                                ppcByCreatorAndType:                                                         (portCreator: OSType;                                                        portType: OSType);    END;Field descriptionsnameScript    An integer script code. name    A string that designates the application name. portKindSelectorAn  integer that selects the kind of type string (either ppcByString or ppcByCreatorAndType).portTypeStr    If the portKindSelector field specifies ppcByString, the portTypeStr field contains a 32-byte character string.portCreator    If the portKindSelector field specifies ppcByCreatorAndType, the portCreator field contains a 4-character creator code.portType    If the portKindSelector field specifies ppcByCreatorAndType, the portType field contains a 4-character type code.To open a port, you need to specify a port name. As previously described, a port name consists of a script code, a name string, and a type string. For example, you can designate “smRoman” as the script code, “make memo” as the application’s name string, and “word processor” as its type string. The Location Name RecordA location name identifies the location of a computer on the network. A location name is specified in the standard Name-Binding Protocol (NBP) form, <object string>:PPCToolBox @<AppleTalk zone>. The object string is the name provided in the Sharing Setup control panel in the Control Panels folder. By default, the type string is “PPCToolBox”. The AppleTalk zone is the zone to which the particular Macintosh computer belongs. For example, “Jane Doe’s Macintosh:PPCToolBox@twilight” specifies the object string, type string, and AppleTalk zone for a particular computer.The LocationNameRec data type defines the location name record. The locationKindSelector field can be set to ppcNoLocation, ppcNBPLocation, or ppcNBPTypeLocation.TYPE LocationNameRec =     RECORD        locationKindSelector: PPCLocationKind;                                                        {which variant}        CASE PPCLocationKind OF            {ppcNoLocation: storage not used by this value}            ppcNBPLocation:                                                                                 (nbpEntity: EntityName); {NBP name entity}            ppcNBPTypeLocation:                                                                (nbpType: Str32);                        {just the NBP type }                                                        { string for the }                                                        { PPCOpen function}    END;Field descriptionslocationKindSelectorAn  integer that determines how the location is specified. You can use either of the constants ppcNBPLocation or ppcNBPTypeLocation. (The PPC Toolbox uses the constant ppcNoLocation when the location received from or passed to a PPC Toolbox function is the location of the local machine.)nbpEntity    If the locationKindSelector field specifies ppcNBPLocation, the nbpEntity field specifies a full NBP entity name.nbpType    If the locationKindSelector field specifies ppcNBPTypeLocation, the nbpType field specifies an alias location name. This location kind is used only by the PPCOpen function when an alias location name is needed.NoteYou should assign an NBP value directly—do not pack it using nbpSetEntity.uThe Port Information RecordA port information record identifies whether a particular port requires authentication and specifies the port’s port name. Both the PPCBrowser and IPCListPorts functions return information about ports using port information records. In addition, if you provide a port filter function, the PPC Toolbox provides information to your function about the current port in a port information record. The PortInfoRec data type defines a port information record.TYPE PortInfoRec =    RECORD        filler1:                    SignedByte;                        {space holder}        authRequired:                    Boolean;                        {authentication required}        name:                    PPCPortRec;                        {port name}    END;Field descriptionsfiller1    Reserved.authRequired    Specifies whether the port requires authentication. This field is TRUE if the port requires authentication before a session can begin. Otherwise, this field is FALSE.name    Specifies an available port name.For information on the PPCBrowser and IPCListPorts functions, see page 11-52 and page 11-54, respectively. For information on port filter functions, see page 11-78.PPC Toolbox RoutinesThis section describes the routines forn    initializing the PPC Toolboxn    displaying the program linking dialog boxn    listing available portsn    opening and closing a portn    starting and ending a sessionn    accepting and rejecting a sessionn    reading and writing datan    obtaining the default user reference number and namen    invalidating a user reference numberResult codes appear after each function where applicable.Initializing the PPC ToolboxYou use the PPCInit function to initialize the PPC Toolbox.PPCInitUse the PPCInit function to initialize the PPC Toolbox.FUNCTION PPCInit: OSErr;DESCRIPTIONAfter initialization, most PPC Toolbox routines can execute either synchronously or asynchronously.Note that a noGlobalsErr result code indicates that the PPC Toolbox is not loaded properly.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the PPCInit function areTrap macro    Selector    _PPCBrowser    $0000    The registers on entry and exit for this routine areRegisters on entry        D0    Selector code    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    noGlobalsErr    –904    System unable to allocate memory, critical error    Using the Program Linking Dialog BoxYou can use either the PPCBrowser function or the IPCListPorts function to locate a port to communicate with. Use the PPCBrowser function to display the program linking dialog box. For the description of IPCListPorts, see page 11-54.PPCBrowserUse the PPCBrowser function to display the program linking dialog box, which allows a user to select a port to communicate with.FUNCTION PPCBrowser (prompt: Str255; applListLabel: Str255;                             defaultSpecified: Boolean;                             VAR theLocation: LocationNameRec;                             VAR thePortInfo: PortInfoRec;                             portFilter: PPCFilterProcPtr;                             theLocNBPType: Str32): OSErr; prompt    A line of text that the PPCBrowser function displays as a prompt in the program linking dialog box. If you specify NIL or an empty string is passed, the default prompt “Choose a program to link to:” is used.applListLabelThe title of the list of PPC ports. If you specify NIL or an empty string is passed, the default title “Programs” is used.defaultSpecifiedA value that determines which port is initially selected in the program linking dialog box. If you specify TRUE, you must provide information in the parameters theLocation and thePortInfo. In this case, the PPCBrowser function tries to select the PPC port specified by the parameters theLocation and thePortInfo when the program linking dialog box first appears. If you specify FALSE, the PPCBrowser function selects the first port in the list and you can leave the location name record and the port information record (in the parameters theLocation and thePortInfo) uninitialized.theLocationThe port location. For information on this data structure, see “The Location Name Record” on page 11-49.thePortInfoThe port name. For information on this data structure, see “The Port Information Record” on page 11-50.portFilterDetermines how the list of PPC ports is filtered. If this parameter is NIL, the names of all existing PPC ports are displayed. If this parameter isn’t NIL, it must be a pointer to a port filter function.theLocNBPTypeThe NBP type passed to NBPLookup to generate the list of computers. If you specify NIL or an empty string is passed, the default, “PPCToolBox”, is used.DESCRIPTIONThe PPCBrowser function builds the list of ports and then displays the program linking dialog box.If you set the defaultSpecified parameter to TRUE, the PPCBrowser function tries to select the PPC port specified by the parameters theLocation and thePortInfo when the program linking dialog box first appears. The locationKindSelector field in the location name record must be set to the ppcNoLocation constant (which specifies the local computer) or the ppcNBPLocation constant (which specifies the NBP object and NBP zone). The ppcNBPTypeLocation constant is not supported for matching. When matching the location, only the object string and the zone string of the entity name are used—the type string is ignored. When matching the port, the entire PPC port record (script, name, and port type) is used in the port information record. The authRequired field of the port information record is ignored.The parameter theLocNBPType of the PPCBrowser function specifies the NBP type passed to NBPLookup to generate the list of computers. If you specify NIL or an empty string is passed, the default, “PPCToolBox”, is used. Note that the current computer is always included in the list of computers (even if a location with the specified type does not exist for it). If the parameter theLocNBPType contains either of the NBP wildcard characters (= or ≈), the PPCBrowser function returns a paramErr result code.If the PPCBrowser function returns noErr, the parameters theLocation and thePortInfo specify the port chosen by the user. If the PPCBrowser function returns a userCanceledErr result code, the user clicked the Cancel button, and no port was selected. If the function returns a memFullErr result code, there was not enough memory to load the PPCBrowser package, and the dialog box did not appear. NoteYou must not call the PPCBrowser function from an application that is running in the background, since this function displays a dialog box on the user’s screen.uRESULT CODESnoErr    0    No error    paramErr    –50    Illegal parameter    memFullErr    –108    Not enough memory to load PPCBrowser package    userCanceledErr    –128    User decided not to conduct a session    SEE ALSOFor an example of the use of the PPCBrowser function, see Listing 11-4 on page 11-26. For an example of the program linking dialog box, see Figure 11-12 on page 11-22. For information on port filter functions, see page 11-78.Obtaining a List of PortsUse the IPCListPorts function to generate a list of existing ports without displaying a dialog box. The IPCListPortsPBRec data type defines the parameter block used by the IPCListPorts function.IPCListPortsUse the IPCListPorts function to generate a list of existing ports without displaying a dialog box.FUNCTION IPCListPorts (pb: IPCListPortsPBPtr;                               async: Boolean): OSErr; pb    A pointer to an IPCListPorts parameter block.async    A value that specifies whether the function is to be executed asynchronously (TRUE) or synchronously (FALSE).Parameter blockÆ    ioCompletion    PPCCompProcPtr    Address of a completion routine    ¨    ioResult    OSErr    Result code    Æ    startIndex    Integer    Index to the port entry list    Æ    requestCount    Integer    Number of port names requested    ¨    actualCount    Integer    Number of port names returned    Æ    portName    PPCPortPtr    Pointer to a PPCPortRec    Æ    locationName    LocationNamePtr    Pointer to a LocationNameRec    Æ    bufferPtr    PortInfoArrayPtr    Pointer to an array of PortInfoRec    DESCRIPTIONIf your application calls the IPCListPorts function asynchronously, you must specify in the ioCompletion field either the address of a completion routine or NIL. If you set ioCompletion to NIL, you should poll the ioResult field of the PPC parameter block (from your application’s main event loop) to determine whether the PPC Toolbox has completed the requested operation. A value in the ioResult field other than 1 indicates that the call is complete. Note that it is unsafe to poll the ioResult field at interrupt time since the PPC Toolbox may be in the process of completing a call. See “PPC Toolbox Calling Conventions” beginning on page 11-14 for detailed information.If you call the IPCListPorts function asynchronously, you must not change any of the fields in the parameter block until the call completes. The port name, location name, and buffer pointed to by IPCListPortsPBRec are owned by the PPC Toolbox until the call completes. These objects must not be deallocated or moved in memory while the call is in progress.The startIndex field specifies the index to the list of ports on the remote machine from which the PPC Toolbox begins to get the list. In most cases, you’ll want to start at the beginning, so set the startIndex field to 0. The requestCount field specifies the maximum number of port information records that can fit into your buffer.The actualCount field returns the actual number of entries returned. Your program can use the IPCListPorts function repeatedly to obtain the entire list of ports. Ports that are not visible to the network are not included in the ports listing on a remote machine. (If you specify FALSE for the networkVisible field in the PPCOpen function, the port is not included in the listing of available ports across a network.)The portName field must contain a pointer to a PPC port record that specifies which PPC ports to list. You can specify particular values in the PPC port record or you can use an equal sign (=) in the name or the portTypeStr fields as a wildcard to match all port names or port types.The locationName field should contain a pointer to a location name record that designates the computer that contains the PPC ports you want returned. If the locationKindSelector field in the location name record is ppcNoLocation or if the locationName pointer is NIL, then the location is the local machine. If the locationKindSelector field in the location name record is ppcNBPLocation, then the location is a remote machine designated by the location name record’s nbpEntity field.The IPCListPorts function returns an array (list) of port information records in the area of memory pointed to by bufferPtr. Make sure that the buffer pointed to by the bufferPtr field is at least sizeof(PortInfoRec) * requestCount.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the IPCListPorts function areTrap macro    Selector    _PPC    $000A    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a parameter block    D0    Selector code    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    notInitErr    –900    PPC Toolbox has not been initialized yet    nameTypeErr    –902    Invalid or inappropriate locationKindSelector in location name    noGlobalsErr    –904    System unable to allocate memory, critical error    localOnlyErr    –905    Network activity is currently disabled    sessTableErr    –907    PPC Toolbox is unable to create a session    noResponseErr    –915    Unable to contact application    badPortNameErr    –919    PPC port record is invalid    networkErr    –925    An error has occurred in the network    badLocNameErr    –931    Location name is invalid    SEE ALSOFor an example of the use of the IPCListPorts function, see Listing 11-5 on page 11-28. Opening and Closing a PortYou open a port using the PPCOpen function and close a port using the PPCClose function.PPCOpenYou open a port using the PPCOpen function.FUNCTION PPCOpen (pb: PPCOpenPBPtr; async: Boolean): OSErr;pb    A pointer to a PPCOpen parameter block.async    A value that specifies whether the function is to be executed asynchronously (TRUE) or synchronously (FALSE).Parameter blockÆ    ioCompletion    PPCCompProcPtr    Address of a completion routine    ¨    ioResult    OSErr    Result code    ¨    portRefNum    PPCPortRefNum    Port reference number of port opened    Æ    serviceType    PPCServiceType    Service type requested—must be ppcServiceRealTime    Æ    resFlag    SignedByte    Reserved field—must be 0    Æ    portName    PPCPortPtr    Pointer to a PPCPortRec    Æ    locationName    LocationNamePtr    Pointer to a LocationNameRec    Æ    networkVisible    Boolean    Make this port network visible    ¨    nbpRegistered    Boolean    Port location was registered on the network    DESCRIPTIONIf your application calls the PPCOpen function asynchronously, you must specify in the ioCompletion field either the address of a completion routine or NIL. If you set ioCompletion to NIL, you should poll the ioResult field of the PPC parameter block (from your application’s main event loop) to determine whether the PPC Toolbox has completed the requested operation. A value in the ioResult field other than 1 indicates that the call is complete. Note that it is unsafe to poll the ioResult field at interrupt time since the PPC Toolbox may be in the process of completing a call. See “PPC Toolbox Calling Conventions” beginning on page 11-14 for detailed information.If you call the PPCOpen function asynchronously, you must not change any of the fields in the parameter block until the call completes. The port name and location name pointed to by the PPCOpen parameter block record are owned by the PPC Toolbox until the call completes. These objects must not be deallocated or moved in memory while the call is in progress.The portRefNum field returns the PPC port identifier. Use this port reference number to initiate a session for this particular port. Set the serviceType field to indicate that this port accepts sessions in real time. For System 7, this field must always be set to the ppcServiceRealTime constant. You must set the resFlag field to 0.The portName field must contain a pointer to a PPC port record that specifies the name of the PPC port to be opened.The locationName field should contain a pointer to a location name record that designates the location of the PPC port to be opened. If the locationName pointer is NIL, then the default name PPC Toolbox is used. If a location name record is used, then the locationKindSelector field in the location name record must be ppcNBPTypeLocation, and an alias location name specified by the location name record’s nbpType field is used.The networkVisible field indicates whether the port should be made visible (for browsing as well as incoming network requests). If you specify FALSE, this port is not visible in the listing of available ports across a network (although it is still included within the local machine’s listing of available ports).The nbpRegistered field returns TRUE if the location name specified was registered on the network.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the PPCOpen function areTrap macro    Selector    _PPC    $0001    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a parameter block    D0    Selector (1)    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    notInitErr    –900    PPC Toolbox has not been initialized yet    nameTypeErr    –902    Invalid or inappropriate locationKindSelector in location name    noPortErr    –903    Unable to open port or bad port reference number    noGlobalsErr    –904    System unable to allocate memory, critical error    badReqErr    –909    Bad parameter or invalid state for this operation    portNameExistsErr    –910    Another port is already open with this name    badPortNameErr    –919    PPC port record is invalid    badServiceMethodErr    –930    Service method is other than ppcServiceRealTime    badLocNameErr    –931    Location name is invalid    nbpDuplicateName    –1027    Location name represents a duplicate on this computer    SEE ALSOFor an example of the use of the PPCOpen function, see Listing 11-2 on page 11-21. PPCCloseYou use the PPCClose function to close the port specified by the port reference number.FUNCTION PPCClose (pb: PPCClosePBPtr; async: Boolean): OSErr; pb    A pointer to a PPCClose parameter block.async    A value that specifies whether the function is to be executed asynchronously (TRUE) or synchronously (FALSE).Parameter blockÆ    ioCompletion    PPCCompProcPtr    Address of a completion routine    ¨    ioResult    OSErr    Result code    Æ    portRefNum    PPCPortRefNum    Port reference number of port to close    DESCRIPTIONIf your application calls this function asynchronously, you must specify in the ioCompletion field either the address of a completion routine or NIL. If you set ioCompletion to NIL, you should poll the ioResult field of the PPC parameter block (from your application’s main event loop) to determine whether the PPC Toolbox has completed the requested operation. A value in the ioResult field other than 1 indicates that the call is complete. Note that it is unsafe to poll the ioResult field at interrupt time since the PPC Toolbox may be in the process of completing a call. See “PPC Toolbox Calling Conventions” beginning on page 11-14 for detailed information.The portRefNum field specifies the PPC port identifier of the port to close. The port reference number must be a valid port reference number returned from a previous call to the PPCOpen function.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the PPCClose function areTrap macro    Selector    _PPC    $0009    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a parameter block    D0    Selector code    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    notInitErr    –900    PPC Toolbox has not been initialized yet    noPortErr    –903    Bad port reference number    noGlobalsErr    –904    System unable to allocate memory, critical error    SEE ALSOFor an example of the use of the PPCClose function, see Listing 11-19 on page 11-44. Starting and Ending a SessionYou use the PPCStart or StartSecureSession function to initiate a session with another port, and you use the PPCEnd function to end a session.PPCStartThe PPCStart function initiates a session with the destination port specified in the name and location fields.FUNCTION PPCStart (pb: PPCStartPBPtr; async: Boolean): OSErr;pb    A pointer to a PPCStart parameter block.async    A value that specifies whether the function is to be executed asynchronously (TRUE) or synchronously (FALSE).Parameter blockÆ    ioCompletion    PPCCompProcPtr    Address of a completion routine    ¨    ioResult    OSErr    Result code    Æ    portRefNum    PPCPortRefNum    Port reference number of this session    ¨    sessRefNum    PPCSessRefNum    Session reference number of this session    Æ    serviceType    PPCServiceType    Service type requested—must be ppcServiceRealTime    Æ    resFlag    SignedByte    Reserved field—must be 0    Æ    portName    PPCPortPtr    Pointer to a PPCPortRec    Æ    locationName    LocationNamePtr    Pointer to a LocationNameRec    ¨    rejectInfo    LongInt    Value from PPCReject if session was rejected    Æ    userData    LongInt    Application-specific data    Æ    userRefNum    LongInt    User reference number    DESCRIPTIONIf your application calls the PPCStart function asynchronously, you must specify in the ioCompletion field either the address of a completion routine or NIL. If you set ioCompletion to NIL, you should poll the ioResult field of the PPC parameter block (from your application’s main event loop) to determine whether the PPC Toolbox has completed the requested operation. A value in the ioResult field other than 1 indicates that the call is complete. Note that it is unsafe to poll the ioResult field at interrupt time, since the PPC Toolbox may be in the process of completing a call. See “PPC Toolbox Calling Conventions” beginning on page 11-14 for detailed information.If you call the PPCStart function asynchronously, you must not change any of the fields in the parameter block until the call completes. The port name and location name pointed to by the PPCStart parameter block record are owned by the PPC Toolbox until the call completes. These objects must not be deallocated or moved in memory while the call is in progress.You specify the PPC port identifier in the portRefNum field. The port reference number is a reference number for the port through which you are requesting a session. The value you specify must correspond to the port reference number returned from the PPCOpen function.The sessRefNum field returns a session identifier. This number, which is provided by the PPC Toolbox, is used while data is being exchanged to identify a particular session. You must set the serviceType field to indicate that the session is to be connected in real time. For System 7, this field must always be set to the ppcServiceRealTime constant. You must set the resFlag field to 0.The portName field must contain a pointer to a PPC port record. The locationName field should contain a pointer to a location name record or NIL. The PPC port record and the location name record specify the name and location of the PPC port to initiate a session with, and they are usually obtained from the PPCBrowser function. If the locationKindSelector field in the location name record is ppcNoLocation or if the locationName pointer is NIL, then the location is the local machine. If the locationKindSelector field in the location name record is ppcNBPLocation, then the location is a remote machine designated by the location name record’s nbpEntity field.If the ioResult field of the PPC parameter block returns a userRejectErr result code, the rejectInfo field contains the same value as the rejectInfo field in the PPCReject parameter block. The rejectInfo field is defined by your application.The initiating port can specify any information in the userData field. The PPCInform function reports this data to the responding port upon its completion.The userRefNum field specifies an authenticated user. The authentication mechanism of the PPC Toolbox identifies each user through an assigned name and a password. A user reference number of 0 indicates that you want to specify a guest. ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the PPCStart function areTrap macro    Selector    _PPC    $0002    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a parameter block    D0    Selector code    Registers on exit        D0    Result code    RESULT CODES    noErr    0    No error    notInitErr    –900    PPC Toolbox has not been initialized yet    nameTypeErr    –902    locationKindSelector is not ppcNBPLocation or ppcNoLocation    noPortErr    –903    Bad port reference number    noGlobalsErr    –904    System unable to allocate memory, critical error    localOnlyErr    –905    Network activity is currently disabled    destPortErr    –906    Port does not exist at destination    sessTableErr    –907    PPC Toolbox is unable to create a session    noUserNameErr    –911    User name unknown on destination machine    userRejectErr    –912    Destination rejected the session request    noResponseErr    –915    Unable to contact application    portClosedErr    –916    The port was closed    badPortNameErr    –919    PPC port record is invalid    networkErr    –925    An error has occurred in the network    noInformErr    –926    PPCStart failed because target application did not have an inform pending    authFailErr    –927    User’s password is wrong    noUserRecErr    –928    Invalid user reference number    badServiceMethodErr    –930    Service method is other than ppcServiceRealTime    guestNotAllowedErr    –932    Destination port requires authentication    SEE ALSOFor an example of the use of the PPCStart function, see Listing 11-7 on page 11-34. StartSecureSessionThe StartSecureSession function prompts for user name and password and calls PPCStart—all in one synchronous procedure call. Use the StartSecureSession function whenever a port destination requires authentication.FUNCTION StartSecureSession (pb: PPCStartPBPtr;                                       VAR userName: Str32;                                       useDefault: Boolean;                                       allowGuest: Boolean;                                       VAR guestSelected: Boolean;                                       prompt: Str255): OSErr;pb    A pointer to a PPCStart parameter block.userName    A pointer to a 32-byte character string to be displayed as the user’s name.useDefaultA Boolean value that indicates whether you want the StartSecureSession function to use the default user identity (and possibly prevent the user identity dialog box from appearing). If so, specify TRUE; otherwise, specify FALSE.allowGuestA Boolean value that determines whether the Guest radio button in the user identity dialog box is active (TRUE) or inactive (FALSE).guestSelectedReturns TRUE if the user has logged on as a guest.prompt    A line of text that the dialog box displays in place of the default prompt. Specify NIL or an empty string to use the default prompt.DESCRIPTIONYour program fills out a parameter block just as though it were calling the PPCStart function. You specify all input fields in the parameter block except for the userRefNum field. The userRefNum field is returned when the StartSecureSession function successfully completes.The userName parameter is a pointer to a 32-byte character string to be displayed as the user’s name. If the Pascal string length is 0, the default user name is used. The default user name is the name specified in the Sharing Setup control panel. The default user name is returned in the userName buffer.Set the useDefault parameter to TRUE if you want the StartSecureSession function to use the default user identity (and possibly prevent the user identity dialog box from appearing). The allowGuest parameter specifies whether the Guest radio button in the user identity dialog box is active. You usually set it to the inverse of the authRequired field in the port information record. For example, if authRequired is TRUE, then allowGuest should be set to FALSE.The guestSelected parameter returns TRUE if the user has logged on as a guest. The prompt parameter of the StartSecureSession function allows you to specify a line of text that the dialog box can display. Specify NIL or an empty string for the prompt parameter to enable the PPC Toolbox to use the default prompt. The PPC Toolbox uses the default string “Link to <port name> on <object string> as:”. The port name is obtained from the name string of the port name, and the object string is obtained from the object string of the location name. NoteDo not call the StartSecureSession function from an application that is running in the background, because the function displays several dialog boxes on the user’s screen.u ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the StartSecureSession function areTrap macro    Selector    _PPC    $000E    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a StartSecureParams record    D0    Selector code    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    userCanceledErr    –128    User decided not to conduct a session    notInitErr    –900    PPC Toolbox has not been initialized yet    nameTypeErr    –902    locationKindSelector is not ppcNBPLocation or ppcNoLocation    noPortErr    –903    Bad port reference number    noGlobalsErr    –904    System unable to allocate memory, critical error    localOnlyErr    –905    Network activity is currently disabled    destPortErr    –906    Port does not exist at destination    sessTableErr    –907    PPC Toolbox is unable to create a session    noResponseErr    –915    Unable to contact application    portClosedErr    –916    The port was closed    badPortNameErr    –919    PPC port record is invalid    noUserRefErr    –924    Unable to create a new user reference number    networkErr    –925    An error has occurred in the network    noInformErr    –926    PPCStart failed because target application did not have an inform pending    badServiceMethodErr    –930    Service method is other than ppcServiceRealTime    guestNotAllowedErr    –932    Destination port requires authentication    SEE ALSOFor an example of the use of the StartSecureSession function, see “Initiating a PPC Session” beginning on page 11-29. PPCEndUse the PPCEnd function to end a session. This function completes all outstanding asynchronous calls associated with the session reference number.FUNCTION PPCEnd (pb: PPCEndPBPtr; async: Boolean): OSErr; pb    A pointer to a PPCEnd parameter block.async    A value that specifies whether the function is to be executed asynchronously (TRUE) or synchronously (FALSE).Parameter blockÆ    ioCompletion    PPCCompProcPtr    Address of a completion routine    ¨    ioResult    OSErr    Result code    Æ    sessRefNum    PPCSessRefNum    Session reference number of session to end    DESCRIPTIONIf your application calls the PPCEnd function asynchronously, you must specify in the ioCompletion field either the address of a completion routine or NIL. If you set ioCompletion to NIL, you should poll the ioResult field of the PPC parameter block (from your application’s main event loop) to determine whether the PPC Toolbox has completed the requested operation. A value in the ioResult field other than 1 indicates that the call is complete. Note that it is unsafe to poll the ioResult field at interrupt time since the PPC Toolbox may be in the process of completing a call. See “PPC Toolbox Calling Conventions” beginning on page 11-14 for detailed information.You provide a session identifier in the sessRefNum field to identify the session that you are terminating. The PPCStart, StartSecureSession, or PPCInform function returns the session reference number.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the PPCEnd function areTrap macro    Selector    _PPC    $0008    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a parameter block    D0    Selector code    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    notInitErr    –900    PPC Toolbox has not been initialized yet    noGlobalsErr    –904    System unable to allocate memory, critical error    noSessionErr    –908    Invalid session reference number    SEE ALSOFor an example of the use of the PPCEnd function, see Listing 11-18 on page 11-43. Receiving, Accepting, and Rejecting a SessionYou use the PPCInform function to receive session requests. After the PPCInform function completes (with the autoAccept field set to FALSE), you must accept or reject the session request using the PPCAccept or PPCReject function.PPCInformAs long as a port has been opened, you can call the PPCInform function at any time. You can have any number of outstanding PPCInform functions.FUNCTION PPCInform (pb: PPCInformPBPtr; async: Boolean): OSErr;pb    A pointer to a PPCInform parameter block.async    A value that specifies whether the function is to be executed asynchronously (TRUE) or synchronously (FALSE). You should execute the PPCInform function asynchronously. Parameter blockÆ    ioCompletion    PPCCompProcPtr    Address of a completion routine    ¨    ioResult    OSErr    Result code    Æ    portRefNum    PPCPortRefNum    Port reference number of this session    ¨    sessRefNum    PPCSessRefNum    Session reference number of this session    ¨    serviceType    PPCServiceType    Service type of this session    Æ    autoAccept    Boolean    If TRUE, session is accepted automatically    Æ    portName    PPCPortPtr    Pointer to PPCPortRec, may be NIL    Æ    locationName    LocationNamePtr    Pointer to LocationNameRec, may be NIL        userName    StringPtr    Pointer to Str32, may be NIL    ¨    userData    LongInt    Application-specific data    ¨    requestType    PPCSessionOrigin    Network or local request    DESCRIPTIONIf your application calls the PPCInform function asynchronously, you must specify in the ioCompletion field either the address of a completion routine or NIL. If you set ioCompletion to NIL, you should poll the ioResult field of the PPC parameter block (from your application’s main event loop) to determine whether the PPC Toolbox has completed the requested operation. A value in the ioResult field other than 1 indicates that the call is complete. Note that it is unsafe to poll the ioResult field at interrupt time since the PPC Toolbox may be in the process of completing a call. See “PPC Toolbox Calling Conventions” beginning on page 11-14 for detailed information.If you call the PPCInform function asynchronously, you must not change any of the fields in the parameter block until the call completes. The port name, location name, user name, and buffer pointed to by the record of type PPCInformPBRec are owned by the PPC Toolbox until the call completes. These objects must not be deallocated or moved in memory while the call is in progress. You provide the PPC port identifier in the portRefNum field. A PPCOpen function returns the port identifier. The sessRefNum field returns a session identifier.The serviceType field indicates the service type. For system software version 7.0, this field always returns the ppcServiceRealTime constant.If you set the autoAccept field to TRUE, session requests are automatically accepted as they are received. When the PPCInform function completes execution with a noErr result code and you set the autoAccept field to FALSE, you need to accept or reject the session.sWARNINGIf the PPCInform function (with the autoAccept parameter set to FALSE) returns a noErr result code, you must call either the PPCAccept function or the PPCReject function. The computer trying to initiate a session using the StartSecureSession function or the PPCStart function waits (hangs) until the session attempt is either accepted or rejected, or until an error occurs.sThe portName field must contain NIL or a pointer to a PPC port record. If the portName field contains NIL, then the name of the PPC port that initiated the session is not returned. If the portName field points to a PPC port record, then the PPC port record is filled with the name of the PPC port that initiated the session when the PPCInform function completes.The locationName field must contain NIL or a pointer to a location name record. If the locationName field contains NIL, then the location of the PPC port that initiated the session is not returned. If the locationName field points to a location name record, then the location name record is filled with the location of the PPC port that initiated the session when the PPCInform function completes. If the locationKindSelector field of the location name record returned is ppcNoLocation, then the location is the local machine. If the locationKindSelector field of the location name record returned is ppcNBPLocation, then the location is a remote machine designated by the location name record’s nbpEntity field.The userName field must contain NIL or a pointer to a 32-byte character string. If the userName field contains NIL, then the user name string is not returned. If the userName field points to a 32-byte character string, then the 32-byte character string is filled with the name of the user making the session request (if authenticated) when the PPCInform function completes.When the PPCInform function completes, the userData field contains the user data provided by the application making the session request. This field is transparent to the PPC Toolbox. The application can send any data in this field.When the PPCInform function completes, the requestType field contains either ppcRemoteOrigin or ppcLocalOrigin, depending on whether the session request is initiated by a computer across the network or by a port on the same computer.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the PPCInform function areTrap macro    Selector    _PPC    $0003    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a parameter block    D0    Selector code    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    notInitErr    –900    PPC Toolbox has not been initialized yet    noPortErr    –903    Unable to open port or bad port reference number    noGlobalsErr    –904    System unable to allocate memory, critical error    portClosedErr    –916    The port was closed    SEE ALSOFor an example of the use of the PPCInform function, see Listing 11-8 on page 11-36. PPCAcceptUse the PPCAccept function to indicate that an application is willing to accept an incoming session request after a PPCInform function completes.FUNCTION PPCAccept (pb: PPCAcceptPBPtr; async: Boolean): OSErr;pb    A pointer to a PPCAccept parameter block.async    A value that specifies whether the function is to be executed asynchronously (TRUE) or synchronously (FALSE).Parameter blockÆ    ioCompletion    PPCCompProcPtr    Address of a completion routine    ¨    ioResult    OSErr    Result code    Æ    sessRefNum    PPCSessRefNum    Session reference number of session to accept    DESCRIPTIONIf your application calls the PPCAccept function asynchronously, you must specify in the ioCompletion field either the address of a completion routine or NIL. If you set ioCompletion to NIL, you should poll the ioResult field of the PPC parameter block (from your application’s main event loop) to determine whether the PPC Toolbox has completed the requested operation. A value in the ioResult field other than 1 indicates that the call is complete. Note that it is unsafe to poll the ioResult field at interrupt time since the PPC Toolbox may be in the process of completing a call. See “PPC Toolbox Calling Conventions” beginning on page 11-14 for detailed information.The sessRefNum field specifies a session identifier. Use the session reference number returned from the completed PPCInform parameter block to accept the session request.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the PPCAccept function areTrap macro    Selector    _PPC    $0004    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a parameter block    D0    Selector code    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    notInitErr    –900    PPC Toolbox has not been initialized yet    noGlobalsErr    –904    System unable to allocate memory, critical error    noSessionErr    –908    Invalid session reference number    badReqErr    –909    Bad parameter or invalid state for this operation    SEE ALSOFor an example of the use of the PPCAccept function, see “Accepting or Rejecting Session Requests” beginning on page 11-37. PPCRejectUse the PPCReject function to reject a session request after a PPCInform function completes.FUNCTION PPCReject (pb: PPCRejectPBPtr; async: Boolean): OSErr;pb    A pointer to a PPCReject parameter block.async    A value that specifies whether the function is to be executed asynchronously (TRUE) or synchronously (FALSE).Parameter blockÆ    ioCompletion    PPCCompProcPtr    Address of a completion routine    ¨    ioResult    OSErr    Result code    Æ    sessRefNum    PPCSessRefNum    Session reference number of session to reject    Æ    rejectInfo    LongInt    Value to return if session is rejected    DESCRIPTIONIf your application calls the PPCReject function asynchronously, you must specify in the ioCompletion field either the address of a completion routine or NIL. If you set ioCompletion to NIL, you should poll the ioResult field of the PPC parameter block (from your application’s main event loop) to determine whether the PPC Toolbox has completed the requested operation. A value in the ioResult field other than 1 indicates that the call is complete. Note that it is unsafe to poll the ioResult field at interrupt time since the PPC Toolbox may be in the process of completing a call. See “PPC Toolbox Calling Conventions” beginning on page 11-14 for detailed information.The sessRefNum field specifies a session to be rejected. This must be a valid session reference number returned from a previous PPCInform function. The rejectInfo field is an optional field. The application receiving a session request may specify any data in this field. The initiating application receives this information in the PPCStart parameter block.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the PPCReject function areTrap macro    Selector    _PPC    $0005    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a parameter block    D0    Selector code    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    notInitErr    –900    PPC Toolbox has not been initialized yet    noGlobalsErr    –904    System unable to allocate memory, critical error    noSessionErr    –908    Invalid session reference number    badReqErr    –909    Bad parameter or invalid state for this operation    SEE ALSOFor an example of the use of the PPCReject function, see page 11-39. Reading and Writing DataThe PPCRead function reads incoming data from an application, and the PPCWrite function writes data to an application during a session.PPCReadUse the PPCRead function to read message blocks during a session.FUNCTION PPCRead (pb: PPCReadPBPtr; async: Boolean): OSErr;pb    A pointer to a PPCRead parameter block.async    A value that specifies whether the function is to be executed asynchronously (TRUE) or synchronously (FALSE). You should execute the PPCRead function asynchronously. Parameter blockÆ    ioCompletion    PPCCompProcPtr    Address of a completion routine    ¨    ioResult    OSErr    Result code    Æ    sessRefNum    PPCSessRefNum    Session reference number    Æ    bufferLength    Size    Length of data buffer    ¨    actualLength    Size    Actual length of data read    Æ    bufferPtr    Ptr    Pointer to data buffer    ¨    more    Boolean    TRUE if more data in this block to be read    ¨    userData    LongInt    Application-specific data    ¨    blockCreator    OSType    Creator of block read    ¨    blockType    OSType    Type of block read    DESCRIPTIONIf your application calls the PPCRead function asynchronously, you must specify in the ioCompletion field either the address of a completion routine or NIL. If you set ioCompletion to NIL, you should poll the ioResult field of the PPC parameter block (from your application’s main event loop) to determine whether the PPC Toolbox has completed the requested operation. A value in the ioResult field other than 1 indicates that the call is complete. Note that it is unsafe to poll the ioResult field at interrupt time since the PPC Toolbox may be in the process of completing a call. See “PPC Toolbox Calling Conventions” beginning on page 11-14 for detailed information.If you call the PPCRead function asynchronously, you must not change any of the fields in the parameter block until the call completes. The buffer pointed to by the record of data type PPCReadPBRec is owned by the PPC Toolbox until the call completes. These objects must not be deallocated or moved in memory while the call is in progress. The sessRefNum field specifies a session to read data from. This must be a valid session reference number returned from a previous PPCStart, StartSecureSession, or PPCInform function. The bufferLength and bufferPtr fields specify the length and location of a buffer the message block will be read into. Your application must allocate the storage for the buffer. The actualLength field returns the actual size of the data read into your data buffer.The more field returns TRUE if the provided buffer cannot hold the remainder of the message block. Your application may read a message block in several pieces. It is not necessary to have a buffer large enough to read in the entire message block, so a message block can span multiple calls to the PPCRead function.Upon completion of the PPCRead function, the userData, blockCreator, and blockType fields contain information regarding the contents of the message block. You specify these fields using the PPCWrite function. ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the PPCRead function areTrap macro    Selector    _PPC    $0007    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a parameter block    D0    Selector code    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    notInitErr    –900    PPC Toolbox has not been initialized yet    noGlobalsErr    –904    System unable to allocate memory, critical error    noSessionErr    –908    Invalid session reference number    badReqErr    –909    Bad parameter or invalid state for this operation    sessClosedErr    –917    The session has closed    SEE ALSOFor an example of the use of the PPCRead function in conjunction with the PPCWrite function, see “Exchanging Data During a PPC Session” beginning on page 11-39.PPCWriteUse the PPCWrite function to write message blocks during a session.FUNCTION PPCWrite (pb: PPCWritePBPtr; async: Boolean): OSErr;pb    A pointer to a PPCWrite parameter block.async    A value that specifies whether the function is to be executed asynchronously (TRUE) or synchronously (FALSE). You should execute the PPCWrite function asynchronously. Parameter blockÆ    ioCompletion    PPCCompProcPtr    Address of a completion routine    ¨    ioResult    OSErr    Result code    Æ    sessRefNum    PPCSessRefNum    Session reference number    Æ    bufferLength    Size    Length of data buffer    ¨    actualLength    Size    Actual length of data written    Æ    bufferPtr    Ptr    Pointer to data buffer    Æ    more    Boolean    TRUE if more data in this block to be written    Æ    userData    LongInt    Application-specific data    Æ    blockCreator    OSType    Creator of block written    Æ    blockType    OSType    Type of block written    DESCRIPTIONIf your application calls the PPCWrite function asynchronously, you must specify in the ioCompletion field either the address of a completion routine or NIL. If you set ioCompletion to NIL, you should poll the ioResult field of the PPC parameter block (from your application’s main event loop) to determine whether the PPC Toolbox has completed the requested operation. A value in the ioResult field other than 1 indicates that the call is complete. Note that it is unsafe to poll the ioResult field at interrupt time since the PPC Toolbox may be in the process of completing a call. See “PPC Toolbox Calling Conventions” beginning on page 11-14.If you call the PPCWrite function asynchronously, you must not change any of the fields in the parameter block until the call completes. The buffer pointed to by the record of data type PPCWritePBRec is owned by the PPC Toolbox until the call completes. These objects must not be deallocated or moved in memory while the call is in progress.The sessRefNum field specifies a session identifier. This must be a valid session reference number returned from a previous PPCStart, StartSecureSession, or PPCInform function. The bufferLength and bufferPtr fields specify the length and location of a buffer the message block is sent to. If the PPCWrite function returns a noErr result code, the actualLength field returns the actual size of the message block that was written.Set the more field to TRUE to indicate that you will be using the PPCWrite function again to append data to this message block. Set the more field to FALSE to indicate that this is the end of the data in this message block.The initiating port can specify any information in the userData field. The PPCRead function reports this data to the responding port upon its completion.Set the userData, blockCreator, and blockType fields for each message block that you create. These fields can give the receiving application information about how to process the contents of the message block. They are ignored when you append information to a message block.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the PPCWrite function areTrap macro    Selector    _PPC    $0006    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a parameter block    D0    Selector code    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    notInitErr    –900    PPC Toolbox has not been initialized yet    noGlobalsErr    –904    System unable to allocate memory, critical error    noSessionErr    –908    Invalid session reference number    badReqErr    –909    Bad parameter or invalid state for this operation    sessClosedErr    –917    The session has closed    SEE ALSOFor an example of the use of the PPCWrite function in conjunction with the PPCRead function, see “Exchanging Data During a PPC Session” beginning on page 11-39.Locating a Default User and Invalidating a UserYou use the GetDefaultUser function to obtain a user reference number and the name of the default user. To invalidate a particular user name and corresponding password, use the DeleteUserIdentity function.GetDefaultUserThe GetDefaultUser function returns the user reference number and the name of the default user.FUNCTION GetDefaultUser (VAR userRef: LongInt;                                 VAR userName: Str32): OSErr;userRef    If the GetDefaultUser function completes with no errors, then the userRef parameter returns the user reference number that represents the user name and password of the default user.userName    The name of the default user.DESCRIPTIONThe default user is specified in the Sharing Setup control panel. This function is useful if your application uses the PPCStart function to initiate a session with an application that does not support guest access. If the GetDefaultUser function completes with no errors, then the userRef parameter returns the user reference number that represents the user name and password of the default user. The userName parameter must contain NIL or a 32-byte character string. If the userName parameter contains NIL, then the user name string is not returned. If the userName parameter is a 32-byte character string, the 32-byte character string contains the user name that is specified in the Sharing Setup control panel when the GetDefaultUser function completes (with no errors). sWARNINGIf you are using Pascal, you cannot pass NIL for the userName parameter. For example, you cannot pass StringPtr(NIL)^ because Pascal performs range checking of string bounds.sASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the GetDefaultUser function areTrap macro    Selector    _PPC    $000D    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a GetDefaultUserParams record    D0    Selector code    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    noDefaultUserErr    –922    User has not specified owner name in Sharing Setup control panel    notLoggedInErr    –923    Default user reference number does not yet exist    SEE ALSOFor an example of the use of the GetDefaultUser function, see Listing 11-20 on page 11-45.DeleteUserIdentityTo invalidate a particular user name and corresponding password, use the DeleteUserIdentity function.FUNCTION DeleteUserIdentity (userRef: LongInt): OSErr;userRef    The reference number representing the user and password to be deleted.DESCRIPTIONThe DeleteUserIdentity function deletes the user name and password corresponding to the user reference number.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DeleteUserIdentity function areTrap macro    Selector    _PPC    $000C    The registers on entry and exit for this routine areRegisters on entry        A0    Pointer to a DeleteUserParams record    D0    Selector code    Registers on exit        D0    Result code    RESULT CODESnoErr    0    No error    noUserRecErr    –928    Invalid user reference number    SEE ALSOFor an example of the use of the DeleteUserIdentity function, see “Invalidating Users” on page 11-44.Application-Defined RoutinesThis section describes the routine syntax for completion routines and port filter functions.Completion Routines for PPC Toolbox RoutinesYour application can provide a pointer to a completion routine in the ioCompletion field of a PPC parameter block. You can provide completion routines only for PPC Toolbox routines that you execute asynchronously.MyCompletionRoutineYou can provide a completion routine for a PPC Toolbox routine that you execute asynchronously.PROCEDURE MyCompletionRoutine (pb: PPCParamBlockPtr);pb    A pointer to the PPC parameter block passed to the PPC Toolbox function.DESCRIPTIONIf you specify a completion routine in the ioCompletion field of a PPC parameter block, it is called at interrupt time when the PPC Toolbox routine completes execution. The PPC Toolbox passes to your completion routine a pointer to the same PPC parameter block that your application passed to the PPC Toolbox routine.sWARNINGCompletion routines execute at the interrupt level and must preserve all registers other than A0, A1, and D0–D2. (Note that MPW C and MPW Pascal do this automatically.) Your completion routine must not make any calls to the Memory Manager, directly or indirectly, and it can’t depend on the validity of handles to unlocked blocks. The PPC Toolbox preserves the application global register A5.sSEE ALSOFor examples of completion routines, see Listing 11-9 on page 11-37, Listing 11-11 on page 11-38, and Listing 11-13 on page 11-39.Port Filter FunctionsThis section describes the port filter function that can be used by the PPCBrowser function.MyPortFilterYou can provide a pointer to a port filter function in the portFilter parameter of the PPCBrowser function.You can use a port filter function to refine the list of PPC ports that the PPCBrowser function displays in the program linking dialog box. FUNCTION MyPortFilter (locationName: LocationNamePtr;                               thePortInfo: PortInfoPtr): Boolean; locationNameA pointer to a location name record. This record specifies the location of the PPC port currently under consideration for display in the program linking dialog box.thePortInfoA pointer to a port information record. This record specifies the port information for the PPC port currently under consideration for display in the program linking dialog box.DESCRIPTIONThe PPCBrowser function calls your port filter function once for each port before it adds that port to the dialog list. Your port filter function should return TRUE for each port that should be displayed in the program linking dialog box, and FALSE for each port that shouldn’t be displayed.SEE ALSOFor an example of a port filter function, see Listing 11-3 on page 11-24. For a description of the location name record, see page 11-49. For a description of the port information record, see page 11-50.Summary of the PPC ToolboxPascal SummaryConstantsCONST            {gestalt selectors}    gestaltPPCToolboxAttr                                    = 'ppc ';                {PPC Toolbox attributes}    gestaltPPCToolboxPresent                                    = $0000;                {PPC Toolbox is present}    gestaltPPCSupportsRealTime                                    = $1000;                {real time only in system }                                                        { software version 7.0}    gestaltPPCSupportsOutGoing                                    = $0002;                {support of outgoing }                                                        { sessions across a network}    gestaltPPCSupportsIncoming                                    = $0001;                {user enabled program }                                                        { linking in Sharing Setup }                                                        { control panel}    {service type)    ppcServiceRealTime                                    = 1;                {real time only in System 7}    {look-up type}    ppcNoLocation                                    = 0;                {there is no PPCLocName}    ppcNBPLocation                                    = 1;                {use AppleTalk NBP}    ppcNBPTypeLocation                                    = 2;                {use just the NBP type, fill }                                                        { in the rest with default}    {port type}    ppcByCreatorAndType                                    = 1;                 {port type is specified as }                                                        { standard creator and type}    ppcByString                                    = 2;                 {port type is in Pascal }                                                         { string format}    {session request type returned in the PPCInform function}    ppcLocalOrigin                                     = 1;                {session initiated on }                                                        { local computer}     ppcRemoteOrigin                                    = 2;                {session initiated on }                                                        { remote computer}Data TypesTYPE     PPCServiceType                                 = SignedByte;                        {service type}    PPCLocationKind                                 = Integer;                        {look-up type}    PPCPortKinds                                = Integer;                        {port type}    PPCSessionOrigin                                = SignedByte;                        {local or remote}    PPCPortRefNum                                = Integer;                        {port reference number}    PPCSessRefNum                                = LongInt;                        {session reference number}    LocationNamePtr                     = ^LocationNameRec;    LocationNameRec                     =     RECORD        locationKindSelector: PPCLocationKind;                                                    {which variant}        CASE PPCLocationKind OF                                                     {ppcNoLocation: storage not }                                                            { used by this value}            ppcNBPLocation:                                                {NBP name entity}                                     (nbpEntity: EntityName);            ppcNBPTypeLocation:(nbpType: Str32);                                                {just the NBP type string }                                                            { for the PPCOpen function}    END;    PortInfoPtr = ^PortInfoRec;    PortInfoRec =    RECORD        filler1:                            SignedByte;                        {space holder}        authRequired:                            Boolean;                        {authentication required}        name:                            PPCPortRec;                        {port name}    END;    PPCPortPtr = ^PPCPortRec;    PPCPortRec =     RECORD        nameScript:                            ScriptCode;                        {script identifier}        name:                            Str32;                        {port name shown in program }                                                            { linking dialog box}            portKindSelector:                        PPCPortKinds;                        {general category of }                                                            { application}            CASE PPCPortKinds OF                ppcByString:                    (portTypeStr: Str32);                            {32 characters}                ppcByCreatorAndType:                                             {4-character creator and type}                                    (portCreator: OSType; portType: OSType);    END;        PPCParamBlockPtr = ^PPCParamBlockRec;        PPCParamBlockRec =         RECORD            CASE Integer OF            0: (openParam:                            PPCOpenPBRec);                            {PPCOPen params}            1: (informParam:                            PPCInformPBRec);                            {PPCInform params}            2: (startParam:                            PPCStartPBRec);                            {PPCStart params}            3: (acceptParam:                            PPCAcceptPBRec);                            {PPCAccept params}            4: (rejectParam:                            PPCRejectPBRec);                            {PPCReject params}            5: (writeParam:                            PPCWritePBRec);                            {PPCWrite params}            6: (readParam:                            PPCReadPBRec);                            {PPCRead params}            7: (endParam:                            PPCEndPBRec);                            {PPCEnd params}            8: (closeParam:                            PPCClosePBRec);                            {PPCClose params}            9: (listPortsParam:                            IPCListPortsPBRec);                            {IPCListPorts params}        END;        PortInfoArrayPtr = ^PortInfoArray;        PortInfoArray    = ARRAY[0..0] OF PortInfoRec;        PPCOpenPBPtr = ^PPCOpenPBRec;        PPCOpenPBRec =         RECORD            qLink:                     Ptr;                            {private}            csCode:                     Integer;                            {private}            intUse:                    Integer;                            {private}            intUsePtr:                    Ptr;                            {private}            ioCompletion:                    PPCCompProcPtr;                            {address of a }                                                            { completion routine}            ioResult:                     OSErr;                            {completion of operation}            reserved:                     ARRAY[1..5] OF LongInt;                                                            {private}            portRefNum:                        PPCPortRefNum;                        {PPC port identifier}            filler1:                        LongInt;                        {space holder}            serviceType:                        PPCServiceType;                        {real time only}            resFlag:                        SignedByte;                        {reserved field}            portName    :                    PPCPortPtr;                        {name of port to be opened}            locationName:                        LocationNamePtr;                        {location of port to be }                                                            { opened}            networkVisible:                        Boolean;                        {port is visible for }                                                            { browsing}            nbpRegistered:                        Boolean    ;                    {location name registered }                                                            { on network}        END;        PPCInformPBPtr = ^PPCInformPBRec;        PPCInformPBRec =         RECORD            qLink:                         Ptr;                        {private}            csCode:                         Integer;                        {private}            intUse:                        Integer;                        {private}            intUsePtr:                        Ptr;                        {private}            ioCompletion:                         PPCCompProcPtr;                        {address of a completion }                                                            { routine}            ioResult:                         OSErr;                        {completion of operation}             reserved:                         ARRAY[1..5] OF LongInt;                                                            {private}            portRefNum:                        PPCPortRefNum;                        {port identifier}            sessRefNum:                        PPCSessRefNum;                        {session identifier}            serviceType:                        PPCServiceType;                        {real time only}            autoAccept:                        Boolean;                        {automatic session }                                                            { acceptance}            portName:                        PPCPortPtr;                        {name of port that }                                                            { initiated a session}            locationName:                        LocationNamePtr;                        {location of port that }                                                            { initiated a session}            userName:                        StringPtr;                        {name of user that }                                                             { initiated a session}            userData:                        LongInt;                        {application-defined}            requestType:                        PPCSessionOrigin;                        {local or remote}        END;        PPCStartPBPtr = ^PPCStartPBRec;        PPCStartPBRec =         RECORD            qLink:                         Ptr;                        {private}            csCode:                         Integer;                        {private}            intUse:                        Integer;                        {private}            intUsePtr:                        Ptr;                        {private}            ioCompletion:                         PPCCompProcPtr;                        {address of a completion }                                                            { routine}            ioResult:                         OSErr;                        {completion of operation}            reserved:                         ARRAY[1..5] OF LongInt;                                                            {private}            portRefNum:                        PPCPortRefNum;                        {identifier for requested }                                                            { port}            sessRefNum:                        PPCSessRefNum;                        {session identifier}            serviceType:                        PPCServiceType;                        {real time only}            resFlag:                        SignedByte;                        {reserved field}            portName:                        PPCPortPtr;                        {name of port to be opened}            locationName:                        LocationNamePtr;                        {location of port to be }                                                            { opened}            rejectInfo:                        LongInt;                        {rejection of session}            userData:                        LongInt;                        {application-specific}            userRefNum:                        LongInt;                        {specifies an authenticated }                                                            { user}        END;        PPCAcceptPBPtr = ^PPCAcceptPBRec;        PPCAcceptPBRec =         RECORD            qLink:                         Ptr;                        {private}            csCode:                         Integer;                        {private}            intUse:                        Integer;                        {private}            intUsePtr:                        Ptr;                        {private}            ioCompletion:                         PPCCompProcPtr;                        {address of a completion }                                                            { routine}            ioResult:                         OSErr;                        {completion of operation}            reserved:                         ARRAY[1..5] OF LongInt;                                                            {private}            filler1:                        Integer;                        {space holder}            sessRefNum:                        PPCSessRefNum;                        {session identifier}        END;        PPCRejectPBPtr = ^PPCRejectPBRec;        PPCRejectPBRec =         RECORD            qLink:                         Ptr;                        {private}            csCode:                         Integer;                        {private}            intUse:                        Integer;                        {private}            intUsePtr:                        Ptr;                        {private}            ioCompletion:                         PPCCompProcPtr;                        {address of a completion }                                                            { routine}            ioResult:                         OSErr;                        {completion of operation}            reserved:                         ARRAY[1..5] OF LongInt;                                                            {private}            filler1:                        Integer;                        {space holder}            sessRefNum:                        PPCSessRefNum;                        {session identifier}            filler2:                        Integer;                        {space holder}            filler3:                        LongInt;                        {space holder}            filler4:                        LongInt;                        {space holder}            rejectInfo:                        LongInt;                        {rejection of session}        END;        PPCWritePBPtr = ^PPCWritePBRec;        PPCWritePBRec =         RECORD            qLink:                         Ptr;                        {private}            csCode:                         Integer;                        {private}            intUse:                        Integer;                        {private}            intUsePtr:                        Ptr;                        {private}            ioCompletion:                         PPCCompProcPtr;                        {address of a completion }                                                            { routine}            ioResult:                         OSErr;                        {completion of operation}            reserved:                         ARRAY[1..5] OF LongInt;                                                            {private}            filler1:                        Integer;                        {space holder}            sessRefNum:                        PPCSessRefNum;                        {session identifier}            bufferLength:                        Size;                        {length of buffer to be }                                                            { written}            actualLength:                        Size;                        {actual size of data written}            bufferPtr:                        Ptr;                        {location of buffer to be }                                                            { written}            more:                        Boolean;                        {additional data to be }                                                            { written}            filler2:                        SignedByte;                        {space holder}            userData:                        LongInt;                        {application-specific}            blockCreator:                        OSType;                        {creator of block to be }                                                            { written}            blockType:                        OSType;                        {type of block to be written}        END;        PPCReadPBPtr = ^PPCReadPBRec;        PPCReadPBRec =         RECORD            qLink:                         Ptr;                        {private}            csCode:                         Integer;                        {private}            intUse:                        Integer;                        {private}            intUsePtr:                        Ptr;                        {private}            ioCompletion:                         PPCCompProcPtr;                        {address of a completion }                                                             { routine}            ioResult:                         OSErr;                        {completion of operation}            reserved:                         ARRAY[1..5] OF LongInt;                                                            {private}            filler1:                        Integer;                        {space holder}            sessRefNum:                        PPCSessRefNum;                        {session identifier}            bufferLength:                        Size;                        {length of buffer to be read}            actualLength:                        Size;                        {actual size of the data }                                                            { read}            bufferPtr:                        Ptr;                        {location of buffer to be }                                                            { read}            more:                        Boolean;                        {additional data to be read}            filler2:                        SignedByte;                        {space holder}            userData:                        LongInt;                        {application-specific}            blockCreator:                        OSType;                        {creator of block to be read}            blockType:                        OSType;                        {type of block to be read}        END;                PPCEndPBPtr = ^PPCEndPBRec;        PPCEndPBRec =         RECORD            qLink:                         Ptr;                        {private}            csCode:                         Integer;                        {private}            intUse:                        Integer;                        {private}            intUsePtr:                        Ptr;                        {private}            ioCompletion:                         PPCCompProcPtr;                        {address of a completion }                                                            { routine}            ioResult:                         OSErr;                        {completion of operation}            reserved:                         ARRAY[1..5] OF LongInt;                                                            {private}            filler1:                        Integer;                        {space holder}            sessRefNum:                        PPCSessRefNum;                        {identifier of session to }                                                            { be terminated}        END;                PPCClosePBPtr = ^PPCClosePBRec;        PPCClosePBRec =         RECORD            qLink:                         Ptr;                        {private}            csCode:                         Integer;                        {private}            intUse:                        Integer;                        {private}            intUsePtr:                        Ptr;                        {private}            ioCompletion:                         PPCCompProcPtr;                        {address of a completion }                                                             { routine}            ioResult:                         OSErr;                        {completion of operation}            reserved:                         ARRAY[1..5] OF LongInt;                                                            {private}            portRefNum:                        PPCPortRefNum;                        {identifier of port to }                                                             { be closed}        END;                IPCListPortsPBPtr = ^IPCListPortsPBRec;        IPCListPortsPBRec =        RECORD            qLink:                         Ptr;                        {private}            csCode:                         Integer;                        {private}            intUse:                        Integer;                        {private}            intUsePtr:                        Ptr;                        {private}            ioCompletion:                         PPCCompProcPtr;                        {address of a completion }                                                            { routine}            ioResult:                         OSErr;                        {completion of operation}            reserved:                        ARRAY[1..5] OF LongInt;                                                            {private}            filler1:                        Integer;                        {space holder}            startIndex:                        Integer;                         {index to the port entry }                                                             { list}            requestCount:                        Integer;                        {number of entries to }                                                            { be returned}            actualCount:                        Integer;                        {actual number of port names}            portName:                        PPCPortPtr;                         {list of port names}             locationName:                        LocationNamePtr;                        {location of port names}            bufferPtr:                        PortInfoArrayPtr;                         {pointer to a buffer}        END;PPC Toolbox RoutinesInitializing the PPC ToolboxFUNCTION PPCInit: OSErr;Using the Program Linking Dialog BoxFUNCTION PPCBrowser    (prompt: Str255; applListLabel: Str255; defaultSpecified: Boolean; VAR theLocation: LocationNameRec; VAR thePortInfo: PortInfoRec; portFilter: PPCFilterProcPtr; theLocNBPType: Str32): OSErr;Obtaining a List of PortsFUNCTION IPCListPorts    (pb: IPCListPortsPBPtr; async: Boolean): OSErr; Opening and Closing a PortFUNCTION PPCOpen    (pb: PPCOpenPBPtr; async: Boolean): OSErr;FUNCTION PPCClose    (pb: PPCClosePBPtr; async: Boolean): OSErr; Starting and Ending a SessionFUNCTION PPCStart    (pb: PPCStartPBPtr; async: Boolean): OSErr;FUNCTION StartSecureSession    (pb: PPCStartPBPtr; VAR userName: Str32; useDefault: Boolean; allowGuest: Boolean; VAR guestSelected: Boolean; prompt: Str255): OSErr;FUNCTION PPCEnd    (pb: PPCEndPBPtr; async: Boolean): OSErr; Receiving, Accepting, and Rejecting a SessionFUNCTION PPCInform    (pb: PPCInformPBPtr; async: Boolean): OSErr; FUNCTION PPCAccept    (pb: PPCAcceptPBPtr; async: Boolean): OSErr;FUNCTION PPCReject    (pb: PPCRejectPBPtr; async: Boolean): OSErr;Reading and Writing DataFUNCTION PPCRead    (pb: PPCReadPBPtr; async: Boolean): OSErr;FUNCTION PPCWrite    (pb: PPCWritePBPtr; async: Boolean): OSErr;Locating a Default User and Invalidating a UserFUNCTION GetDefaultUser    (VAR userRef: LongInt; VAR userName: Str32) : OSErr; FUNCTION DeleteUserIdentity    (userRef: LongInt): OSErr; Application-Defined RoutinesPROCEDURE MyCompletionRoutine(pb: PPCParamBlockPtr);FUNCTION MyPortFilter    (locationName: LocationNameRec; thePortInfo: PortInfoRec): Boolean;C SummaryConstantsCONST        enum {    /*gestalt selectors*/    #define gestaltPPCToolboxAttr                                     'ppc '                /*PPC Toolbox attributes*/    gestaltPPCToolboxPresent                                    = $0000,                /*PPC Toolbox is present*/    gestaltPPCSupportsRealTime                                    = $1000,                /*real time only in system */                                                        /* software version 7.0*/    gestaltPPCSupportsOutGoing                                    = $0002,                /*support of outgoing */                                                        /* sessions across a network*/    gestaltPPCSupportsIncoming                                    = $0001                /*user enabled program */                                                        /* linking in Sharing Setup */                                                        /* control panel*/};enum {    /*service type*/    ppcServiceRealTime                                    = 1                /*real time only in System 7*/};enum {    /*look-up type*/    ppcNoLocation                                    = 0,                /*there is no PPCLocName*/    ppcNBPLocation                                    = 1,                /*use AppleTalk NBP*/    ppcNBPTypeLocation                                    = 2                /*use just the NBP type, fill */                                                        /* in the rest with default*/};enum {    /*port type*/    ppcByCreatorAndType                                    = 1,                 /*port type is specified as */                                                        /* standard Mac creator and type*/    ppcByString                                    = 2                 /*port type is in Pascal */                                                         /* string format*/};enum {    /*session request type returned in the PPCInform function*/    ppcLocalOrigin                                     = 1,                /*session initiated on */                                                        /* local computer*/     ppcRemoteOrigin                                    = 2                /*session initiated on */                                                        /* remote computer*/};Data Typestypedef unsigned char PPCServiceType;                                                             /*service type*/typedef short PPCLocationKind;                                                             /*look-up type*/typedef short PPCPortKinds;                                                             /*port type*/typedef unsigned char PPCSessionOrigin;                                                            /*local or remote*/typedef short PPCPortRefNum;                                                            /*port reference number*/typedef long PPCSessRefNum;                                                            /*session reference number*/struct PPCPortRec {    ScriptCode nameScript;                                                        /*script identifier*/    Str32 name;                                                        /*port name shown in program */                                                            /* linking dialog box*/    PPCPortKinds portKindSelector;                                                        /*general category of */                                                            /* application*/    union        Str32 portTypeStr;                                                    /*32 characters*/        struct            OSType creator;                                                /*4-character creator and */            OSType type;                                                /* type*/            } port;        } u;};typedef struct PPCPortRec PPCPortRec;typedef PPCPortRec *PPCPortPtr;struct LocationNameRec {    PPCLocationKind locationKindSelector;                                                        /*which variant*/    union {                                                            EntityName                 nbpEntity;                                    /*NBP name entity*/        Str32                 nbpType;                                    /*just the NBP type string */                                                            /* for the PPCOpen function*/        } u;};typedef struct LocationNameRec LocationNameRec;typedef LocationNameRec *LocationNamePtr;struct PortInfoRec {    unsigned char                     filler1;                                    /*space holder*/    Boolean                     authRequired;                                    /*authentication required*/    PPCPortRec                     name;                                    /*port name*/};typedef struct PortInfoRec PortInfoRec;typedef PortInfoRec *PortInfoPtr;typedef PortInfoRec *PortInfoArrayPtr;typedef pascal Boolean (*PPCFilterProcPtr) (LocationNamePtr, PortInfoPtr);/*procedures you need to write*//*ex: void MyCompletionRoutine(PPCParamBlkPtr pb)*//*ex: pascal Boolean MyPortFilter(LocationNamePtr, PortInfoPtr)*/typedef ProcPtr PPCCompProcPtr;#define PPCHeader \    Ptr                        qLink;                                /*private*/    unsigned short                        csCode;                                /*private*/    unsigned short                        intUse;                                /*private*/    Ptr                        intUsePtr;                                /*private*/    PPCCompProcPtr                        ioCompletion;                                /*address of a */                                                            /* completion routine*/    OSErr                        ioResult;                                /*completion of operation*/    unsigned long                        Reserved[5];                                /*private*/struct PPCOpenPBRec {    PPCHeader    PPCPortRefNum                     portRefNum;                                    /*PPC port identifier*/    long                     filler1;                                    /*space holder*/    PPCServiceType     serviceType;                                                    /*real time only*/    unsigned char                     resFlag;                                    /*reserved field*/    PPCPortPtr                     portName;                                    /*name of port to be opened*/    LocationNamePtr locationName;                                                        /*location of port to be */                                                            /* opened*/    Boolean                     networkVisible;                                    /*port is visible for */                                                            /* browsing*/    Boolean                     nbpRegistered;                                    /*location name registered */                                                            /* on network*/};typedef struct PPCOpenPBRec PPCOpenPBRec;typedef PPCOpenPBRec *PPCOpenPBPtr;struct PPCInformPBRec {    PPCHeader    PPCPortRefNum                         portRefNum;                                /*port identifier*/    PPCSessRefNum                         sessRefNum;                                /*session identifier*/    PPCServiceType                         serviceType;                                /*real time only*/    Boolean                         autoAccept;                                /*automatic session acceptance*/    PPCPortPtr                         portName;                                /*name of port that */                                                            /* initiated a session*/    LocationNamePtr                         locationName;                                /*location of port that */                                                            /* initiated a session*/    StringPtr                         userName;                                /*name of user that */                                                             /* initiated a session*/    unsigned long                         userData;                                /*application-defined*/    PPCSessionOrigin                         requestType;                                /*local or remote*/};typdef struct PPCInformPBRec PPCInformPBPtr;struct PPCStartPBRec {    PPCHeader    PPCPortRefNum                         portRefNum;                            /*identifier for requested */                                                        /* port*/    PPCSessRefNum                         sessRefNum;                            /*session identifier*/    PPCServiceType                         serviceType;                            /*real time only*/    unsigned char                        resFlag;                            /*reserved field*/    PPCPortPtr                         portName;                            /*name of port to be opened*/    LocationNamePtr                         locationName;                            /*location of port to be opened*/    unsigned long                         rejectInfo;                            /*rejection of session*/    unsigned long                         userData;                            /*application-specific*/    unsigned long                         userRefNum;                            /*specifies an authenticated user*/};typedef struct PPCStartPBRec PPCStartPBRec;typedef PPCStartPBRec *PPCStartPBPtr;struct PPCAcceptPBRec {        PPCHeader        short                     filler1;                            /*space holder*/        PPCSessRefNum                     sessRefNum;                            /*session identifier*/};typedef struct PPCAcceptPBRec PPCAcceptPBRec;typedef PPCAcceptPBRec *PPCAcceptPBPtr;struct PPCRejectPBRec {        PPCHeader        short                     filler1;                            /*space holder*/        PPCSessRefNum                     sessRefNum;                            /*session identifier*/        short                     filler2;                            /*space holder*/        long                     filler3;                            /*space holder*/        long                     filler4;                            /*space holder*/        unsigned long                     rejectInfo;                            /*rejection of session*/};typedef struct PPCRejectPBRec PPCRejectPBRec;typedef PPCRejectPBRec *PPCRejectPBPtr;struct PPCWritePBRec {    PPCHeader    short                     filler1;                                /*space holder*/    PPCSessRefNum                     sessRefNum;                                /*session identifier*/    Size                     bufferLength;                                /*length of buffer to be written*/    Size                     actualLength;                                /*actual size of data written*/    Ptr                     bufferPtr;                                /*location of buffer to be */                                                        /* written*/    Boolean                     more;                                /*additional data to be written*/    unsigned char                     filler2;                                /*space holder*/    unsigned long                     userData;                                /*application-specific*/    OSType                     blockCreator;                                /*creator of block to be written*/    OSType                     blockType;                                /*type of block to be written*/};typedef struct PPCWritePBRec PPCWritePBRec;typedef PPCWritePBRec *PPCWritePBPtr;struct PPCReadPBRec {    PPCHeader    short                     filler1;                                /*space holder*/    PPCSessRefNum                     sessRefNum;                                /*session identifier*/    Size                     bufferLength;                                /*length of buffer to be read*/    Size                     actualLength;                                /*actual size of the data read*/    Ptr                     bufferPtr;                                /*location of buffer to be read*/    Boolean                     more;                                /*additional data to be read*/    unsigned char                     filler2;                                /*space holder*/    unsigned long                     userData;                                /*application-specific*/    OSType                     blockCreator;                                /*creator of block to be read*/    OSType                     blockType;                                /*type of block to be read*/};typedef struct PPCReadPBRec PPCReadPBRec;typdef PPCReadPBRec *PPCReadPBPtr;struct PPCEndPBRec {    PPCHeader    short                     filler1;                                /*space holder*/    PPCSessRefNum                     sessRefNum;                                /*identifier of session to */                                                        /* be terminated*/};typedef struct PPCEndPBRec PPCEndPBRec;typedef PPCEndPBRec *PPCEndPBPtr;struct PPCClosePBRec {    PPCHeader    PPCPortRefNum                     portRefNum;                                /*identifier of port to */                                                         /* be closed*/};typedef struct PPCClosePBRec PPCClosePBRec;typedef PPCClosePBRec *PPCClosePBPtr;struct IPCListPortsPBRec {    PPCHeader    short                         filler1;                            /*space holder*/    unsigned short                         startIndex;                             /*index to the port entry list*/     unsigned short                         requestCount;                            /*number of entries to */                                                        /* be returned*/    unsigned short                         actualCount;                            /*actual number of port names*/    PPCPortPtr                         portName;                             /*list of port names*/     LocationNamePtr                         locationName;                            /*location of port names*/    PortInfoArrayPtr                         bufferPtr;                            /*pointer to a buffer*/};typedef struct IPCListPortsPBRec IPCListPortsPBRec;typedef IPCListPortsPBRec *IPCListPortsPBPtr;union PPCParamBlockRec {    PPCOpenPBRec                         openParam;                            /*PPCOpen params*/    PPCInformPBRec                         informParam;                            /*PPCInform params*/    PPCStartPBRec                         startParam;                            /*PPCStart params*/    PPCAcceptPBRec                         acceptParam;                            /*PPCAccept params*/    PPCRejectPBRec                         rejectParam;                            /*PPCReject params*/    PPCWritePBRec                         writeParam;                            /*PPCWrite params*/    PPCReadPBRec                         readParam;                            /*PPCRead params*/    PPCEndPBRec                         endParam;                            /*PPCEnd params*/    PPCClosePBRec                         closeParam;                            /*PPCClose params*/    IPCListPortsPBRec                     listPortsParam;                                 /*IPCListPorts params*/};typdef union PPCParamBlockRec PPCParamBlockRec;typdef PPCParamBlockRec *PPCParamBlockPtr;PPC Toolbox RoutinesInitializing the PPC Toolboxpascal OSErr PPCInit    (void);Using the Program Linking Dialog Boxpascal OSErr PPCBrowser    (ConstStr255Param prompt, ConstStr255Param applListLabel, Boolean defaultSpecified, LocationNameRec *theLocation, PortInfoRec *thePortInfo, PPCFilterProcPtr portFilter, ConstStr32Param theLocNBPType);Obtaining a List of Portspascal OSErr IPCListPorts    (IPCListPortsPBPtr pb, Boolean async); Opening and Closing a Portpascal OSErr PPCOpen    (PPCOpenPBPtr pb, Boolean async);pascal OSErr PPCClose    (PPCClosePBPtr pb, Boolean async); Starting and Ending a Sessionpascal OSErr PPCStart    (PPCStartPBPtr pb, Boolean async);pascal OSErr StartSecureSession(PPCStartPBPtr pb, Str32 userName, Boolean useDefault, Boolean allowGuest, Boolean *guestSelected, ConstStr255Param prompt);pascal OSErr PPCEnd    (PPCEndPBPtr pb, Boolean async); Receiving, Accepting, and Rejecting a Sessionpascal OSErr PPCInform    (PPCInformPBPtr pb, Boolean async); pascal OSErr PPCAccept    (PPCAcceptPBPtr pb, Boolean async);pascal OSErr PPCReject    (PPCRejectPBPtr pb, Boolean async);Reading and Writing Datapascal OSErr PPCRead    (PPCReadPBPtr pb, Boolean async);pascal OSErr PPCWrite    (PPCWritePBPtr pb, Boolean async);Locating a Default User and Invalidating a Userpascal OSErr GetDefaultUser    (unsigned long *userRef, Str32 userName); pascal OSErr DeleteUserIdentity(unsigned long userRef); Application-Defined Routinesvoid MyCompletionRoutine    (PPCParamBlockPtr pb);pascal Boolean MyPortFilter    (LocationNameRec locationName, PortInfoRec thePortInfo);Assembly-Language SummaryTrap MacrosTrap Macros Requiring Routine Selectors_Pack9Selector    Routine    $0D00    PPCBrowser    _PPCSelector    Routine    $0000    PPCInit    $0001    PPCOpen    $0002    PPCStart    $0003    PPCInform    $0004    PPCAccept    $0005    PPCReject    $0006    PPCWrite    $0007    PPCRead    $0008    PPCEnd    $0009    PPCClose    $000A    IPCListPorts    $000C    DeleteUserIdentity    $000D    GetDefaultUser    $000E    StartSecureSession    Result CodesnoErr    0    No error    paramErr    –50    Illegal parameter    memFullErr    –108    Not enough memory to load PPCBrowser package    userCanceledErr    –128    User decided not to conduct a session    notInitErr    –900    PPC Toolbox has not been initialized yet    nameTypeErr    –902    Invalid or inappropriate locationKindSelector in location name    noPortErr    –903    Unable to open port or bad port reference number    noGlobalsErr    –904    System unable to allocate memory, critical error    localOnlyErr    –905    Network activity is currently disabled    destPortErr    –906    Port does not exist at destination    sessTableErr    –907    PPC Toolbox is unable to create a session    noSessionErr    –908    Invalid session reference number    badReqErr    –909    Bad parameter or invalid state for this operation    portNameExistsErr    –910    Another port is already open with this name    noUserNameErr    –911    User name unknown on destination machine    userRejectErr    –912    Destination rejected the session request    noResponseErr    –915    Unable to contact application    portClosedErr    –916    The port was closed    sessClosedErr    –917    The session has closed    badPortNameErr    –919    PPC port record is invalid    noDefaultUserErr    –922    User has not specified owner name in Sharing Setup control panel    notLoggedInErr    –923    Default user reference number does not yet exist    noUserRefErr    –924    Unable to create a new user reference number    networkErr    –925    An error has occurred in the network    noInformErr    –926    PPCStart failed because target application did not have an inform pending    authFailErr    –927    User’s password is wrong    noUserRecErr    –928    Invalid user reference number    badServiceMethodErr    –930    Service method is other than ppcServiceRealTime    badLocNameErr    –931    Location name is invalid    guestNotAllowedErr    –932    Destination port requires authentication    nbpDuplicate    –1027    Location name represents a duplicate on this computer    Listing 12-0Table 11-0Data Access ManagerContentsAbout the Data Access Manager12-5The High-Level Interface12-7Sending a Query Through the High-Level Interface12-8Retrieving Data Through the High-Level Interface12-9The Low-Level Interface12-9Sending a Query Through the Low-Level Interface12-10Retrieving Data Through the Low-Level Interface12-11Comparison of the High-Level and Low-Level Interfaces12-11Using the Data Access Manager12-12Executing Routines Asynchronously12-12General Guidelines for the User Interface12-13Keep the User in Control12-13Provide Feedback to the User12-13Using the High-Level Interface12-14Writing a Status Routine for High-Level Functions12-22Using the Low-Level Interface12-28Getting Information About Sessions in Progress12-35Processing Query Results12-36Getting Query Results12-36Converting Query Results to Text12-42Creating a Query Document12-46User Interface Guidelines for Query Documents12-46Contents of a Query Document12-48Query Records and Query Resources12-51Writing a Query Definition Function12-51Data Access Manager Reference12-54Data Structures12-54The Asynchronous Parameter Block12-55The Query Record12-56The Results Record12-58Data Access Manager Routines12-59Initializing the Data Access Manager12-60High-Level Interface: Handling Query Documents12-61High-Level Interface: Handling Query Results12-65Low-Level Interface: Controlling the Session12-68Low-Level Interface: Sending and Executing Queries12-76Low-Level Interface: Retrieving Results12-82Installing and Removing Result Handlers12-86Application-Defined Routines12-89Resources12-90The Query Resource12-90The Query String Resource12-91The Query Definition Function Resource12-92Summary of the Data Access Manager12-93Pascal Summary12-93Constants12-93Data Types12-94Data Access Manager Routines12-96Application-Defined Routines12-98C Summary12-98Constants12-98Data Types12-100Data Access Manager Routines12-101Application-Defined Routines12-103Assembly-Language Summary12-103Trap Macros12-103Result Codes12-104Data Access ManagerThis chapter describes how your application can use the Data Access Manager to gain access to data in another application. It also tells you how to provide templates to be used for data transactions.The Data Access Manager is available in System 7 and later versions. Use the Gestalt Manager to determine whether the Data Access Manager is present. To determine whether the Data Access Manager is available, use the Gestalt function with the gestaltDBAccessMgrAttr environmental selector. If the Data Access Manager is not available, the Gestalt function returns an error. For more information on the Gestalt Manager, see Inside Macintosh: Operating System Utilities.The Data Access Manager allows your application to communicate with a database or other data source even if you do not know anything about databases in general or the specific data source with which the users of your software will be communicating. All your application needs are a few high-level Data Access Manager functions and access to a file called a query document. The query document, provided by another application, contains commands and data in the format appropriate for the database or other data source. The string of commands and data sent to the data source are referred to as a query. Note that a query does not necessarily extract data from a data source; it might only send data or commands to a database or other application.The Data Access Manager makes it easy for your application to communicate with data sources. You need only add a menu item that opens a query document, using a few standard Data Access Manager functions to implement the menu selection. Users of your application can then access a database or other data source whenever they have the appropriate query documents. A user of a word-processing program might use this feature, for example, to obtain access to archived material, dictionaries in a variety of languages, or a database of famous quotations. A user of a spreadsheet program might use a query document to obtain tax records, actuarial tables, or other data. A user of an art or computer-aided design program might download archived illustrations or designs. And for the user of a database application for the Macintosh computer, the Data Access Manager can provide the resources and power of a mainframe database.The Data Access Manager also provides a low-level interface for use by applications that are capable of creating their own queries and that therefore do not have to use query documents. If your application uses only the high-level interface and relies on query documents created by other programs, then all the routines you need to know are described in this chapter. However, if you want to create a query document or an application that uses the low-level interface, then you must also be familiar with the command language used by the data server. You need the information in this chapter if you want your application to access data in other applications or if you want to write a query document.NoteThe Data Access Manager makes it easy for your application to communicate with a database running on a remote computer, and this chapter generally assumes that you are using it for that purpose. However, there is no reason why the database could not be local—that is, running on the same computer as your application. To implement such a system, you would have to have a database that runs on a Macintosh computer and that has a command-language interface, plus a database extension that can use that command language. In most cases, it would be much simpler to run the database as a separate application and use the Clipboard to transfer data into and out of the database.u Note also that the program containing the data need not be a database. With the appropriate database extension, your application could read data from a spreadsheet, for example, or any other program that stores data.Apple Computer, Inc. provides a database extension that uses Data Access Language (DAL). A database extension provides an interface between the Data Access Manager and the database or other program that contains the data. If you want to write an application that uses the low-level interface to communicate with a Data Access Language server, or if you want to create a query document that uses Data Access Language, you must be familiar with that language. Data Access Language Programmer’s Reference, available from APDA, fully describes this language.About the Data Access ManagerThe Data Access Manager constitutes a standard interface that allows Macintosh applications to communicate with any number of databases or other data sources through a variety of data servers. As used in this chapter, a data server is the application that acts as an interface between the database extension on the Macintosh computer and the data source, which can be on the Macintosh computer or on a remote host computer. A data server can be a database server program, such as a Data Access Language server, which can provide an interface to a variety of different databases, or it can be the data source itself, such as a Macintosh application.The Data Access Manager has two application interfaces: the high-level interface and the low-level interface. If the proper database extension and query documents are available in the user’s system, you can use the high-level interface to communicate with a data source without having any knowledge of the command language that the data server uses. Even if you use the low-level interface, your application can isolate the user from any specific knowledge of the data source or the data server’s command language.This section presents an overview and description of the Data Access Manager, including diagrams and conceptual descriptions of the components and processes involved in using the high-level and low-level interfaces. Next, “Using the Data Access Manager” beginning on page 12-12 includes descriptions, flowcharts, and program fragments that provide a step-by-step guide to the use of the high-level and low-level interfaces. “Creating a Query Document” beginning on page 12-46 describes the contents and function of a query document. You do not have to read this section unless you are writing an application that creates query documents, although if you are using the high-level interface you might be interested to know just how a query document works. Figure 12-1 illustrates connections between Macintosh applications and a database on a remote computer. The arrows in Figure 12-1 show the flow of information, not the paths of commands or control signals. See Figure 12-2 on page 12-8 and Figure 12-3 on page 12-10 for the sequences involved in sending and retrieving data.Figure 12-1    A connection with a databaseThe High-Level InterfaceAs Figure 12-1 on page 12-6 shows, a database-naive application—that is, one that cannot prepare a query for a specific data server—uses the Data Access Manager’s high-level routines to communicate with a data server. Because the application cannot prepare a query, it must use a query document to provide one. A query document can contain code, called a query definition function, that prompts the user for information and modifies the query before the Data Access Manager sends it to the data server. The exact format of a query definition function is described in “Writing a Query Definition Function” on page 12-51.NoteThe term query refers to any string of commands (and associated data) that can be executed by a data server. A query can send data to a data source, retrieve data from a data source, or reorganize the data in a data source. The Data Access Manager does not interpret or execute the query; it only implements the interface (sometimes called the application program interface, or API) that allows you to send the query to the data server.u When you want to use the high-level routines to execute a query on a data server, you first select a query document or allow the user to select one. You use high-level routines to n    get the query from the query document n    execute the query definition function to modify the queryn    send the query to the data servern    retrieve the results from any query that asks for information from the data sourcen    convert to text the results returned by a queryFor example, suppose a company that makes rubber ducks has a database on a minicomputer that contains a mailing list of all its customers. The database has a Data Access Language interface, and the company’s marketing manager has a Macintosh computer with an application that uses high-level Data Access Manager routines to communicate with the remote database server. As Figure 12-2 illustrates, the marketing manager must also have a query document, created by another application, that she can use to get an address from the mailing list on the remote minicomputer. The query document can be as complex or as simple as its creator cares to make it; in this example, the query document is designed specifically to obtain addresses from the rubber duck mailing list. The marketing manager might have several other query documents available as well: one to extract a mailing list for a specific zip code, one to list all of the customers who have made a purchase within the last year, and so on.Notice that once the query document has sent the query to the data server, the Data Access Manager handles the data retrieval. Although query documents and high-level Data Access Manager routines make it very easy for you to request data from a data source, there is no way for a query document to verify that data sent to a data source has been successfully received. For that reason, it is recommended that you use the low-level interface to send data to a data source or update data in a data source.Figure 12-2    Using high-level Data Access Manager routinesSending a Query Through the High-Level InterfaceTo obtain a list of addresses from the mailing list, the marketing manager chooses the Open Query menu command from the File menu in her application. From the list of query documents displayed, she chooses one named Rubber Duck Address List. The application calls the Data Access Manager function DBGetNewQuery, specifying the resource ID of the query ('qrsc') resource in the Rubber Duck Address List query document. The DBGetNewQuery function creates a query record and a partial query from the information in the query resource. The partial query specifies the type of data (character strings) and the columns from which the data items should come (the name and address columns). The partial query lacks some specific data (the rows that should be searched) that is needed to complete the search criteria. Next, the application calls the DBStartQuery function, which in turn calls the query definition function in the query document. The query definition function displays a dialog box that asks for the purchase dates to search. When the marketing manager types in the requested information and clicks OK, the query definition function adds the data to the partial query in memory. The query is now ready to be executed. Next, the DBStartQuery function sends the query to the Data Access Language database extension, and the database extension sends the query over a communications network to the remote Data Access Language server. Finally, the DBStartQuery function commands the Data Access Language server to execute the query. Retrieving Data Through the High-Level InterfaceWhen the application is ready to retrieve the data that it requested from the database, the application calls the DBGetQueryResults function. This function determines when the data is available, retrieves it from the data server, and places the data in a record in memory. The application can then call the DBResultsToText function, which uses routines called result handlers to convert each data item to a character string. The DBResultsToText function passes to the application a handle to the converted data. The application then displays the list of customers for the marketing manager.Data items and result handlers are described in “Processing Query Results” beginning on page 12-36.The Low-Level InterfaceA database-aware application communicates through the low-level interface of the Data Access Manager. You can use the low-level interface ton    initiate communication with the data server, sending the user name, password, and other information to the data servern    send a query to the data servern    execute the query that you have sent to the data servern    halt execution of the queryn    return status and errors from the data servern    send data to the data sourcen    retrieve data from the data sourceFor example, suppose once again that a company that makes rubber ducks has a mailing list of all of its customers in a database on a minicomputer, and the database has a Data Access Language interface. This time, suppose the Macintosh application the marketing manager is using calls low-level Data Access Manager routines to communicate with the remote database server. Figure 12-3 illustrates the use of the low-level interface. Notice that if you use the high-level interface (Figure 12-2), the query document and the Data Access Manager prepare the query, send the query, retrieve the query results, and translate the data for you. If you use the low-level interface, however, you must perform these functions yourself.Figure 12-3    Using low-level Data Access Manager routinesSending a Query Through the Low-Level InterfaceTo update the mailing list with a new address for customer Marvin M., the marketing manager enters the new address into her application. The application prepares a Data Access Language statement (a query) that specifies the type of data (a character string), the column into which the data item should go (the address column), the row to be modified (the Marvin M. row), plus the actual data the application wishes to send (Marvin M.’s address). The application then passes this query to the Data Access Manager using the low-level interface. (The application can send the query in several pieces or all at once.) The Data Access Manager sends the query to the Data Access Language database extension in the Macintosh computer, and the database extension sends the query to the remote Data Access Language server. Retrieving Data Through the Low-Level InterfaceOnce the query begins executing, the application can periodically check with the data server to determine whether the data is ready (Figure 12-3). When the data is available, the application must retrieve it one data item at a time. An application that uses the low-level interface must determine the data type of each data item, convert the data into a format that is meaningful to the user, and store the data in memory allocated by the application. Data types are described in “Getting Query Results” beginning on page 12-36.Note that neither the Data Access Manager nor the DAL database extension reads, modifies, or acts on the query that an application sends to the data server. The data server does execute the query, causing the data source to accept new data or prepare data for the application. To use the low-level interface to communicate with a data server, your application must be capable of preparing a query that can be executed by the data server.Comparison of the High-Level and Low-Level InterfacesAn application that uses the low-level interface to send a query to the data server must prepare the query, initiate communication with the data server, send the query to the data server, and execute the query. If it requested data to be returned, the application must determine when the data is ready, and retrieve the data one item at a time. Each step in this process requires calling one or more low-level routines. The high-level interface between the Data Access Manager and the application, in contrast, consists of only a few routines, each of which might call several low-level routines to accomplish its tasks. For example, a single high-level function can call the query definition function, initiate communication with the data server, send the query to the data server, and execute the query. Because the high-level interface is very easy to use and requires no specific knowledge of the data source or database server, you can add high-level data access to your application very easily. Then, whenever someone provides a query document for use with a specific data server, the user can take advantage of the data access capability included in your application. However, because there is no way for a query document to verify that data sent to a data source has been successfully received, it is recommended that you use the low-level interface to send data to a data source or update data in a data source.Although in concept the low-level routines and high-level routines serve separate purposes, there is nothing to prevent you from using calls to both in a single application. For example, you might use low-level routines to send a query to a data server and high-level routines to read the results and convert them to text.Using the Data Access ManagerThere are at least three different ways in which you can use the Data Access Manager to communicate with a data source. You cann    use low-level interface routines to send queries and retrieve data from the data source. In this case, your application must be capable of preparing a query in a language appropriate for the data server.n    use high-level interface routines to send queries and retrieve data from the data source. In this case, you must have one or more query documents provided by another application.n    create your own query documents and use high-level interface routines to send queries and retrieve data from the data source. In this case, your application must be capable of preparing a query, but it can use the same query repeatedly once it has been prepared. This section describes how to use the high-level and low-level interfaces to the Data Access Manager to send queries to a data server. This section also describes how to call Data Access Manager functions asynchronously, how to determine the status of the high-level functions at various points in their execution (and cancel execution if you so desire), how to obtain information about Data Access Manager sessions that are in progress, and how to retrieve query results and convert them to text. Executing Routines AsynchronouslyAll of the Data Access Manager low-level routines and some of the high-level routines can execute asynchronously—that is, the routine returns control to your application before the routine has completed execution. Your application must call the Event Manager’s WaitNextEvent function periodically to allow an asynchronous routine to complete execution. NoteThe database extension is responsible for implementing asynchronous execution of Data Access Manager routines. For example, if you call the DBSend function to send a query to a data server, and the database extension calls a device driver, the database extension can return control to your application as soon as the device driver has placed its routine in the driver input/output (I/O) queue. If you attempt to execute a routine asynchronously and the database extension that the user has selected does not support asynchronous execution, the routine returns a result code of rcDBAsyncNotSupp and terminates execution.u All Data Access Manager routines that can execute asynchronously take as a parameter a pointer to a parameter block known as the asynchronous parameter block. If the value of this pointer is NIL, the function is executed synchronously—that is, the routine does not return control to your application until execution is complete. General Guidelines for the User InterfaceWhen you use the Data Access Manager to provide data access, you should keep two important principles in mind: keep the user in control, and provide feedback to the user. Keep the User in ControlWhen designing a data access feature or application, keep in mind that the user should have as much access to the Macintosh computer’s abilities as possible. Design your application so that most of the data access process happens in the background. Call the Data Access Manager asynchronously whenever the database extension you are using supports asynchronous calls. Because data retrieval queries can take minutes or even hours to complete, they should always run in the background.After issuing a query, return control of the computer to users so that they may work on other tasks or switch to other applications while the query runs. Whenever a background task requires the user’s attention, follow the suggestions in Macintosh Human Interface Guidelines regarding user notification. A background task should never take control from the user by posting an alert box in front of the active application’s windows. Any message that you post should identify the query that requires attention. For example, an alert box might display the message “The query Get Employee Information was canceled because the connection was unexpectedly broken.”If your application allows more than one simultaneous connection to data sources or allows more than one query document to run, provide a modeless window that lists the open connections and queries, displays the status of each, and allows the user to cancel them if necessary. Allow the user to limit the amount of disk space that must remain free after any transaction. For example, a user may wish to specify that 1 MB of space always be free. Cancel any transaction that would exceed the user’s limit and notify the user. Provide Feedback to the UserKeep the user informed about status, progress, and error conditions, and allow the user to cancel an interaction whenever possible. Inform the user before the application becomes modal and the computer becomes unavailable. Use the spinning beach ball cursor or the animated wristwatch cursor to indicate a process that takes several seconds to complete. Use a dialog box to indicate any process that lasts longer than a few seconds. For example, connecting to a remote database could take a couple of minutes. In this case include a Cancel button in the dialog box so that the user can cancel the operation. When possible, display a progress indicator to show how long a process lasts. Warn the user before doing anything potentially dangerous or irreversible, such as deleting all of a user’s data files to replace them with data retrieved from a data source.When a data retrieval query terminates prematurely, make the retrieved data available to the user but warn the user that it is incomplete. The user can then evaluate the partial data before deciding whether to run the query again. Using the High-Level InterfaceUse the high-level interface to the Data Access Manager if you want to use a query document to do the work of communicating with a data source. You can use the high-level interface to open a query document, execute the query definition function in the query document, establish communication (initiate a session) with a data server, send the query to the data server, execute the query, retrieve any data requested by the query, and convert the retrieved data to text. Although two or three high-level routines accomplish most of these tasks, you may need to call a few low-level routines as well to control a session with a data server. Applications that implement this type of data access must provide user control and feedback as described in “General Guidelines for the User Interface” on page 12-13. In addition, you should include an Open Query command in the File menu. The Open Query command is equivalent to the Open (file) command in meaning. When the user chooses this command, display an open file dialog box filtered to show only query documents (file type 'qery'). The user can then select the desired query document. The query document contains the query to be sent to the data source. Depending on the type of query, the data source could receive information, send back information, report the status of the data source, or perform some other task. Figure 12-4 is a flowchart of a typical session using the high-level interface. As Figure 12-4 illustrates, you must follow this procedure to use the high-level interface:    1.    Call the InitDBPack function to initialize the Data Access Manager.    2.    Select the query document that you want to use and determine the resource ID of the 'qrsc' resource in that query document. You can use any method you like to select the query document. One possibility is to use the StandardGetFile procedure to let the user select the query document. A query document should contain only one 'qrsc' resource; you can then use the Resource Manager to determine the resource ID of the 'qrsc' resource in the document that the user selected. For further information, see the description of the StandardGetFile procedure in the chapter “Standard File Package” in Inside Macintosh: Files and the chapter “Resource Manager” in Inside Macintosh: More Macintosh Toolbox.    3.    Call the DBGetNewQuery function. The DBGetNewQuery function creates in memory a data structure called a query record from the 'qrsc' resource that you specify.     4.    Call the DBStartQuery function specifying the handle to the query record that you created with the DBGetNewQuery function (step 3). You should also provide the DBStartQuery function with a handle to your status routine. A status routine is a routine that you provide to update windows, check the results of the low-level calls made by the DBStartQuery and DBGetQueryResults functions, and cancel execution of these functions when you consider it appropriate to do so. Figure 12-4    A flowchart of a session using the high-level interfaceThe DBStartQuery function calls the query definition function (if any) referred to by the query record. The query definition function can prompt the user for information and modify the query record. After the query definition function has completed execution, the DBStartQuery function calls your status routine so that you can update your windows if necessary. The DBStartQuery function then checks whether communication has been established with the data server. If not, it calls your status routine so that you can display a status dialog box and then calls the DBInit function to establish communication (initiate a session) with the data server. The DBStartQuery function obtains the values it needs for the DBInit function parameters from the query record. When the DBInit function completes execution, the DBStartQuery function calls your status routine again. The DBInit function returns an identification number, called a session ID. This session ID is unique; no other current session, for any database extension, has the same session ID. You must specify the session ID any time you want to send data to or retrieve data from this session. If you prefer, you can use the DBInit function to establish communication before you call the DBStartQuery function. In that case, you must specify the session ID as an input parameter to the DBStartQuery function. See “Using the Low-Level Interface” beginning on page 12-28 for more information on using the DBInit function. Once communication has been established, the DBStartQuery function calls the DBSend function to send the data server the query specified by the query record. When the DBSend function has completed execution, the DBStartQuery function calls your status routine. Finally, the DBStartQuery function uses the DBExec function to execute the query. The DBStartQuery function calls your status routine after the DBExec function has completed execution (that is, the query has started executing and the DBExec function has returned control to the DBStartQuery function) and again just before the DBStartQuery function completes execution.     5.    If you requested data and want to know when the data is available, but do not want to retrieve the data immediately, you can call the DBState function. This function tells you when the data server has finished executing the query, but it does not retrieve the data. If you requested data and want to retrieve it as soon as it is available, you do not have to call the DBState function; go to step 6 instead.If you did not request data, you can use the DBState function to determine the status of the query. When the data server has finished executing the query, skip to step 8.    6.    Call the DBGetQueryResults function. If the query has not finished executing, this function returns the rcDBExec result code. If the query has finished executing, the DBGetQueryResults function calls the DBGetItem function repeatedly until the data server has returned all of the data available. The DBGetQueryResults function puts the returned data into a record that contains handles to arrays that contain the data, the type of data in each column, and the length of each data item. The Data Access Manager allocates the memory for this data in the application heap.The DBGetQueryResults function calls your status routine after it retrieves each data item. You can use this opportunity to display the data item for the user and to give the user the opportunity to cancel execution of the function. The DBGetQueryResults function also calls your status routine just before completing execution, so that you can dispose of any memory allocated by the status routine, remove any dialog box that you displayed, and update your windows if necessary.To convert the returned data to text, go to the next step. If you do not want to convert the returned data to text, skip to step 9.    7.    Call the DBResultsToText function. This function calls a result handler function for each data type. The result handler converts the data to text, places it in a buffer, and returns a handle to the buffer. Some result handlers are provided with the Data Access Manager; you can provide as many with your application as you wish. Result handlers are discussed in “Converting Query Results to Text” beginning on page 12-42.    8.    If you are finished using the query record, call the DBDisposeQuery function to dispose of the query record and free all the memory associated with the query record. If you want to reuse the same query, return to step 5. You should close the query document when you are finished using it.If you want to use a new query document, return to step 3.    9.    When you are finished using the data source, you must use the DBEnd function to terminate the session. You must call the DBEnd function after the DBInit function has returned a nonzero session ID, even if it also returned an error.Listing 12-1 illustrates the use of the high-level interface. This code initiates a session with a remote database, lets the user select a query document to execute, opens the selected file, finds a 'qsrc' resource, and creates a query record. Next, it executes the query, checks the status of the remote database server, retrieves the data when it’s available, and converts this data to text. When the query has finished executing, the code disposes of the query record, ends the session, and closes the user-selected query document. In general, there’s no reason why there can’t be multiple sessions open at once. You can identify each session by its session ID. Listing 12-1 shows just one session.Listing 12-1 assumes that you are using a database extension that supports asynchronous execution of Data Access Manager routines. This listing shows just one possible approach to sending a query and retrieving data asynchronously. Listing 12-1    Using the high-level interfacePROCEDURE MyHiLevel(VAR rr: ResultsRecord; myTextHdl: Handle;                        VAR thisSession: LongInt; VAR sessErr: OSErr);TYPE    {define a record to include space for the current value in }    { A5 so a completion routine can find it}    CRRec = RECORD        QPB: DBAsyncParamBlockRec;                                            {the parameter block}        appsA5: LongInt;                                            {append A5 to the }                                                    { parameter block}    END;    CRRecPtr = ^CRRec;VAR    StartPB, GetQRPB:                                                            CRRec;    SFR:                                                            StandardFileReply;    packErr, startQErr, getQErr, disposeQErr:                                                            OSErr;    getnewQErr, gStartQErr, gGetQRErr:                                                            OSErr;    endErr, fsopenErr, fscloseErr, resultsErr:                                                            OSErr;    gStart, gQueryResults:                                                            Boolean;    qrscHandle:                                                            Handle;    rsrcID:                                                            Integer;    rsrcType:                                                            ResType;    rsrcName:                                                            Str255;    myQHandle:                                                            QueryHandle;    savedResFile:                                                            Integer;    typeList:                                                            SFTypeList;    fsRefNum:                                                            Integer;FUNCTION GetQPB: CRRecPtr;    INLINE $2E88;                                        {MOVE.L  A0,(SP)}BEGIN    gStart := FALSE;    gQueryResults := FALSE;    sessErr := noErr;                                        {assume everything went fine}    packErr := InitDBPack;                                        {initialize the Data Access Mgr}    {display a dialog box to let the user pick a query document}    typeList[0] := 'qery';    StandardGetFile(NIL, 1, typeList, SFR);    IF SFR.sfGood = TRUE THEN        fsopenErr := FSpOpenRF(SFR.sfFile, fsCurPerm, fsRefNum);    IF (fsopenErr <> noErr) OR (SFR.sfGood = FALSE) THEN    BEGIN        sessErr := fsopenErrOrUserCanceled;        EXIT(MyHiLevel);    END;    savedResFile := CurResFile;                                        {save current resource file}    UseResFile(fsRefNum);                                        {get query info from here}    {a query document should have only one 'qrsc' resource}    qrscHandle := Get1IndResource('qrsc', 1);    IF ResError <> noErr THEN    BEGIN        sessErr := ResError;        EXIT(MyHiLevel);    END;    {get the resource ID of the 'qrsc' resource}    GetResInfo(qrscHandle, rsrcID, rsrcType, rsrcName);    {create a query record using the resource ID}    getnewQErr := DBGetNewQuery(rsrcID, myQHandle);    IF getnewQErr <> noErr THEN    BEGIN        sessErr := getnewQErr;        endErr := DBEnd(thisSession, NIL);        EXIT(MyHiLevel);    END;    StartPB.QPB.completionProc := @MyStartCompRoutine;    StartPB.appsA5 := SetCurrentA5;                                                {save this for the }                                                    { completion routine}    {MyStartStatus is a status routine that handles messages sent }    { by the DBStartQuery function when it calls a low-level         }    { function}    startQErr := DBStartQuery(thisSession, myQHandle,                                        @MyStartStatus, @StartPB);    IF startQErr <> noErr THEN    BEGIN        sessErr := startQErr;        IF thisSession <> 0 THEN             endErr := DBEnd(thisSession, NIL);        EXIT(MyHiLevel);    END;    WHILE NOT gStart DO                            {while waiting for gStart to go TRUE, }    BEGIN                            { MyGoDoSomething calls WaitNextEvent }        MyGoDoSomething;                        { to give other routines a chance to run}    END;            {while}    {the DBStartQuery call has completed}    IF gStartQErr <> noErr THEN    BEGIN        sessErr := gStartQErr;        IF thisSession <> 0 THEN             endErr := DBEnd(thisSession, NIL);        EXIT(MyHiLevel);    END;    GetQRPB.QPB.completionProc := @MyGetQRCompRoutine;    GetQRPB.appsA5 := SetCurrentA5;                                                    {save this for the }                                                        { completion routine}    {MyGetQRStatus is a status routine that handles messages sent }    { by the DBGetQueryResults function when it calls a low-level }    { function.}    getQErr := DBGetQueryResults(thisSession, rr, kDBWaitForever,                                            @MyGetQRStatus, @GetQRPB);    IF getQErr <> noErr THEN    BEGIN        sessErr := getQErr;        endErr := DBEnd(thisSession, NIL);        EXIT(MyHiLevel);    END;    WHILE NOT gQueryResults DO    BEGIN        MyGoDoSomething;    END; {while}    {The DBGetQueryResults call has completed. Assuming the call }    { completed successfully, you may want to convert the }    { retrieved data to text, return memory you have borrowed, }    { and end the session.}    IF gGetQRErr <> noErr THEN    BEGIN        sessErr := gGetQRErr;        endErr := DBEnd(thisSession, NIL);        EXIT(MyHiLevel);    END;    {the data has been retrieved; convert it to text}    resultsErr := DBResultsToText(rr, myTextHdl);    {The current query is finished.  You can elect to execute }    { the next 'qrsc' resource of the file, or select another }    { query document.  This example just returns to the caller.}    disposeQErr := DBDisposeQuery(myQHandle);    UseResFile(savedResFile);                {restore current resource file}    fscloseErr := FSClose(fsRefNum);                                            {close the query document}    IF fscloseErr <> noErr THEN         DoError(fscloseErr);    endErr := DBEnd(thisSession, NIL);    IF endErr <> noErr THEN         DoError(endErr);    END;Listing 12-2 shows the completion routines MyStartCompRoutine and MyGetQRCompRoutine used in Listing 12-1.Listing 12-2    Two completion routinesPROCEDURE MyStartCompRoutine(aCRRecPtr: CRRecPtr);VAR    curA5:            LongInt;BEGIN    aCRRecPtr := GetQPB;                                                {get the param block}    curA5 := SetA5(aCRRecPtr^.appsA5);                                                {set A5 to the app's A5}    gStart := TRUE;                                                {query has been started}    gStartQErr := aCRRecPtr^.QPB.result;                                                {send back result code}    {do whatever else you want to do}    curA5 := SetA5(curA5);                        {restore original A5}END;  {MyStartCompRoutine}PROCEDURE MyGetQRCompRoutine(aCRRecPtr: CRRecPtr);VAR    curA5:            LongInt;BEGIN    aCRRecPtr := GetQPB;                                                {get the param block}    curA5 := SetA5(aCRRecPtr^.appsA5);                                                {set A5 to the app's A5}    gQueryResults := TRUE;                        {query results are complete}    gGetQRErr := aCRRecPtr^.QPB.result;                                                {send back the result code}    {do whatever else you want to do}    curA5 := SetA5(curA5);                                                {restore original A5}END;      {MyGetQRCompRoutine}The next section provides information about status routines.Writing a Status Routine for High-Level FunctionsBoth of the two main high-level functions, DBStartQuery and DBGetQueryResults, call low-level functions repeatedly. After each time they call a low-level function, these high-level functions call a routine that you provide, called a status routine. Your status routine can check the result code returned by the low-level function and can cancel execution of the high-level function before it calls the next low-level function. Your status routine can also update your application’s windows after the DBStartQuery function has displayed a dialog box.You provide a pointer to your status routine in the statusProc parameter to the DBStartQuery and DBGetQueryResults functions. Here is a function declaration for a status routine:FUNCTION MyStatusFunc (message: Integer; result: OSErr;                               dataLen: Integer; dataPlaces: Integer;                               dataFlags: Integer; dataType: DBType;                               dataPtr: Ptr): Boolean;Your status routine should return a value of TRUE if you want to continue execution of the DBStartQuery or DBGetQueryResults function, or a value of FALSE if you want to cancel execution of the function. In the latter case, the high-level function returns the userCanceledErr result code.NoteIf you call the DBStartQuery or DBGetQueryResults function asynchronously, you cannot depend on the A5 register containing a pointer to your application’s global variables when the Data Access Manager calls your status routine.uThe message parameter tells your status routine the current status of the high-level function that called it. The possible values for the message parameter depend on which function called your routine. The value of the result parameter depends on the value of the message parameter, as summarized in the following list: Message    Result    kDBUpdateWind    0    kDBAboutToInit    0    kDBInitComplete    Result of DBInit    kDBSendComplete    Result of DBSend    kDBExecComplete    Result of DBExec    kDBStartQueryComplete    Result of DBStartQuery    kDBGetItemComplete    Result of DBGetItem    kDBGetQueryResultsComplete    Result of DBGetQueryResults    The dataLen, dataPlaces, dataFlags, dataType, and dataPtr parameters are returned only by the DBGetQueryResults function, and only when the message parameter equals kDBGetItemComplete. When the DBGetQueryResults function calls your status routine with this message, the dataLen, dataPlaces, and dataType parameters contain the length, decimal places, and type of the data item retrieved, respectively, and the dataPtr parameter contains a pointer to the data item. The least significant bit of the dataFlags parameter is set to 1 if the data item is in the last column of the row. The third bit of the dataFlags parameter is set to 1 if the data item is NULL. You can use this information, for example, to check whether the data meets some criteria of interest to the user, or to display each data item as the DBGetItem function receives it. You can use the constants kDBLastColFlag and kDBNullFlag to test for these flag bits.The DBGetQueryResults function returns a results record, which contains a handle to the retrieved data. The address in the dataPtr parameter points inside the array specified by this handle. Because the dataPtr parameter is not a pointer to a block of memory allocated by the Memory Manager, but just a pointer to a location inside such a block, you cannot use this pointer in any Memory Manager routines (such as the GetPtrSize function). Note also that you cannot rely on this pointer remaining valid after you return control to the DBGetQueryResults function. The DBStartQuery function can send to your status routine the following constants in the message parameter:CONST        {DBStartQuery status messages}        kDBUpdateWind                                 = 0;            {update windows}        kDBAboutToInit                                = 1;            {about to call DBInit}        kDBInitComplete                                = 2;            {DBInit has completed}        kDBSendComplete                                = 3;            {DBSend has completed}        kDBExecComplete                                = 4;            {DBExec has completed}        kDBStartQueryComplete                                = 5;            {DBStartQuery is about to }                                                    { complete} DBStartQuery message constant    Meaning(continued)    kDBUpdateWind    The DBStartQuery function has just called a query definition function. Your status routine should process any update events that your application has received for its windows.    kDBAboutToInit    The DBStartQuery function is about to call the DBInit function to initiate a session with a data server. Because initiating the session might involve establishing communication over a network, and because in some circumstances the execution of a query can tie up the user’s computer for some length of time, you might want to display a dialog box giving the user the option of canceling execution at this time.         continued    kDBInitComplete    The DBInit function has completed execution. When the DBStartQuery function calls your status routine with this message, the result parameter contains the result code returned by the DBInit function. If the DBInit function returns the noErr result code, the DBStartQuery function calls the DBSend function next. If the DBInit function returns any other result code, you can display a dialog box informing the user of the problem before returning control to the DBStartQuery function. The DBStartQuery function then returns an error code and stops execution.    kDBSendComplete    The DBSend function has completed execution. When the DBStartQuery function calls your status routine with this message, the result parameter contains the result code returned by the DBSend function. If the DBSend function returns the noErr result code, the DBStartQuery function calls the DBExec function next. If the DBSend function returns any other result code, you can display a dialog box informing the user of the problem before returning control to the DBStartQuery function. The DBStartQuery function then returns an error code and stops execution.    kDBExecComplete    The DBExec function has completed execution. When the DBStartQuery function calls your status routine with this message, the result parameter contains the result code returned by the DBExec function. If the DBExec function returns the noErr result code, the DBStartQuery function returns control to your application next. If the DBExec function returns any other result code, you can display a dialog box informing the user of the problem before returning control to the DBStartQuery function. The DBStartQuery function then returns an error code and stops execution.    kDBStartQueryComplete    The DBStartQuery function has completed execution and is about to return control to your application. The function result is in the result parameter passed to your status routine. Your status routine can use this opportunity to perform any final tasks, such as disposing of memory that it allocated or removing from the screen any dialog box that it displayed.    The DBGetQueryResults function can send to your status routine the following constants in the message parameter:CONST        {DBGetQueryResults status messages}        kDBGetItemComplete                                     = 6;        {DBGetItem has completed}        kDBGetQueryResultsComplete     = 7;                                        {DBGetQueryResults has }                                                    { completed} DBGetQueryResults message constant    Meaning    kDBGetItemComplete    The DBGetItem function has completed execution. When the DBGetQueryResults function calls your status routine with this message, the result parameter contains the result code returned by the DBGetItem function. The DBGetQueryResults function also returns values for the dataLen, dataPlaces, dataType, dataFlags, anddataPtr parameters, as discussed earlier in this section.For each data item that it retrieves, the DBGetQueryResults function calls the DBGetItem function twice: once to obtain information about the next data item and once to retrieve the data item. The DBGetQueryResults function calls your status routine only after calling the DBGetItem function to retrieve a data item.If your status routine returns a function result of FALSE in response to the kDBGetItemComplete message, the results record returned by the DBGetQueryResults function to your application contains data through the last full row retrieved.Data types and results records are described in “Getting Query Results” beginning on page 12-36.    kDBGetQueryResultsComplete    The DBGetQueryResults function has completed execution and is about to return control to your application. The function result is in the result parameter passed to your status routine. Your status routine can use this opportunity to perform any final tasks, such as disposing of memory that it allocated or removing from the screen any dialog box that it displayed.    Listing 12-3 shows a status routine for the DBStartQuery function. This routine updates the application’s windows in response to the kDBUpdateWind message, displays a dialog box giving the user the option of canceling before the data access is initiated, and checks the results of calls to the DBInit, DBSend, and DBExec functions. If one of these functions returns an error, the status routine displays a dialog box describing the error.Listing 12-3    A sample status routineFUNCTION MyStartStatus(message: Integer; result: OSErr;                                 dataLen: Integer; dataPlaces: Integer;                                dataFlags: Integer; dataType: DBType;                                 dataPtr: Ptr): Boolean;VAR    myString:                Str255;    continue:                Boolean;BEGIN    continue := TRUE;                        {assume user wants to continue with query}    CASE message OF    kDBUpdateWind:                        {a qdef function has just been called; }        BEGIN                    { handle activate and update events}            MyDoActivate;                    {find and handle activate events}            MyDoUpdate;                    {find and handle update events}        END;  {kDBUpdateWind}    kDBAboutToInit:                        {about to initiate a session}        BEGIN        {MyDisplayDialog displays a dialog box. The value }                { returned in the continue variable indicates }                { whether DBStartQuery should continue.}            myString := 'The Data Access Manager is about to open a                             session.  This could take a while.  Do you                            want to continue?';            MyDisplayDialog(@myString, continue);        END;  {kDBAboutToInit}    kDBInitComplete:                        {the DBInit function has completed execution}        BEGIN            IF result <> noErr THEN                                {if there's an error, }            BEGIN                                { let the user know what it is}                CASE result OF                rcDBError:                BEGIN                    myString := 'The Data Access Manager was unable to                                    open the session.  Please check your                                    connections and try again later.';                    MyDisplayString(@myString);                END;        {rcDBError}                rcDBBadDDev:                BEGIN                    myString := 'The Data Access Manager cannot find                                    the database extension file it needs to                                    open a session.  Check with your system                                    administrator for a copy of the file.';                    MyDisplayString(@myString);                END    ;    {rcDBBadDDev}                OTHERWISE                BEGIN                    myString := 'The Data Access Manager was unable to                                    open the session.  The error code                                     returned was';                    MyDisplayError(@myString, result);                END; {of otherwise}            END;  {of CASE result}            END; {of result <> noErr}        END; {kDBInitComplete}    kDBSendComplete:                        {the DBSend function has completed execution}         BEGIN            {if there's an error, let the user know what it is}            IF result <> noErr THEN            BEGIN                IF result = rcDBError THEN                BEGIN                    myString := 'An error occurred while the Data                                     Access Manager was trying to send the                                     query. Please try again later.';                    MyDisplayString(@myString);                END                ELSE                BEGIN                    myString := 'An error occurred while the Data                                     Access Manager was trying to send the                                     query. The error code returned was';                    MyDisplayError(@myString, result);                END;            END;        {of result <> noErr}        END;  {kDBSendComplete}    kDBExecComplete:                        {the DBExec function has completed execution}        BEGIN            IF result <> noErr THEN                                {if there's an error, }            BEGIN                                { let the user know what it is}                IF result = rcDBError THEN                BEGIN                    myString := 'The Data Access Manager was unable to                                execute the query. There may be a problem                                with the query document or the database.                                Check with your system administrator.';                    MyDisplayString(@myString);                END                ELSE                BEGIN                    myString := 'An error occurred while the Data                                Access Manager was trying to execute the                                query.  The error code returned was';                    MyDisplayError(@myString, result);                END;            END;        {of result <> noErr}        END;  {kDBExecComplete}    kDBStartQueryComplete:                            {the DBStartQuery function is about }        BEGIN                        { to return control to your application}            {clean up memory and any dialog boxes left on the screen}            MyCleanUpWindows;        END;  {kDBStartQueryComplete}    END; {CASE message}    MyStartStatus := continue;END;Using the Low-Level InterfaceYou can use the low-level interface to establish communication (initiate a session) with a data server, send a query to the data server, execute the query, and retrieve any data requested by the query. You call one or more low-level routines to accomplish each of these tasks. Applications that implement this type of data access must provide user control and feedback, as described in “General Guidelines for the User Interface” on page 12-13. When the data source is ready to return data, you can retrieve it all and then display it to the user, or you can display the data as it arrives. If the data arrives slowly, it’s best to display it one record at a time as it arrives. This way the user can preview the data, decide if it’s the desired information, and cancel the query if not. Figure 12-5 is a flowchart of a typical session using the low-level interface. As Figure 12-5 illustrates, you must follow this procedure to use the low-level interface:    1.    Call the InitDBPack function to initialize the Data Access Manager.    2.    Call the DBInit function to establish communication with the data server. The DBInit function returns an identification number, called a session ID. This session ID is unique; no other current session, for any database extension, has the same session ID. Figure 12-5    A flowchart of a session using the low-level interfaceYou must specify the session ID any time you want to send data to or retrieve data from this session.The DBInit function requires as input parameters the name of the database extension and character strings for the host system, user name, password, and connection string. All of these parameters depend on the user and the user’s computer system, including the specific database extension, host computer, data server, and database management software in use. You will not know the user name and password when you are writing an application, and you might not know the values of any of these parameters. Therefore, you must display a dialog box that prompts the user for the necessary information. Depending on the database extension you are using, the DBInit function might return a session ID of zero if it fails to initiate a session, or it might return a nonzero session ID and a result code other than noErr. In the latter case, you can pass the session ID to the DBGetErr function to determine the cause of the error. If the DBInit function returns a nonzero session ID and a result code other than noErr, you must call the DBEnd function before making another attempt to open the session.    3.    Prepare a query, and send it to the data server by calling the DBSend and DBSendItem functions one or more times. An application that uses the low-level interface must be capable of creating a query for the data server in the language and format required by that data server.The DBSend function sends a query or a portion of a query to the data server. The data server appends this portion of the query to any portion you sent previously. Because the Data Access Manager and data server do not modify the string you send in any way, they do not insert any delimiter between fragments of queries that you send to the data server. If you want a blank or a semicolon to be included between query fragments, or if you want to use return characters to divide the query into lines of text, you must include them in the character string that you send with the DBSend function. The data string that you send with the DBSend function can be any length up to 64 KB. The DBSendItem function sends a single data item to the data server. Use the DBSendItem function to send data items to the data source in the same format as they are retrieved from the data source by the DBGetItem function. You must specify the data type as an input parameter and, for any data type that does not have an implied length, you must specify the length as well. The database extension or the data server (depending on how the system is implemented) converts the data item to a character string and appends it to the query, just as a query program fragment is appended to the query by the DBSend function. You can call the DBSend and DBSendItem functions as many times as you wish to send your query to the data server.Listing 12-4 sends the Data Access Language query fragment “print 451+222;” to the Data Access Language server.Listing 12-4    Sending a query fragmentFUNCTION MySendFragment(sessID: LongInt): OSErr;VAR    value1:                                        LongInt;    value2:                                        LongInt;    text1, text2, text3:                                        Str15;    text1Ptr, text2Ptr, text3Ptr:                                        Ptr;    rc:            OSErr;BEGIN    text1 := 'print ';    value1 := 451;    text2 := '+';    value2 := 222;    text3 := ';';    MySetTextPtrs(text1, text1Ptr, text2, text2Ptr,                         text3, text3Ptr);    rc := DBSend (sessID, text1Ptr, LENGTH(text1), NIL);    IF rc = noErr THEN        rc := DBSendItem (sessID, typeInteger, 0, 0, 0,                                 Ptr(ORD(@value1)), NIL);    IF rc = noErr THEN        rc := DBSend (sessID, text2Ptr, LENGTH(text2), NIL);    IF rc = noErr THEN        rc := DBSendItem (sessID, typeInteger, 0, 0, 0,                                 Ptr(ORD(@value2)), NIL);    IF rc = noErr THEN        rc := DBSend (sessID, text3Ptr, LENGTH(text3), NIL);    MySendFragment := rc;END;    4.    Use the DBExec function to initiate execution of the query. Depending on the way the system you are using is implemented, the DBExec function might return control to your application as soon as the query has begun execution.     5.    Use the DBState function to determine the status of the data source. The DBState function tells you when the data server has finished executing the query you just sent. If you have requested data, the data server stores the data you requested but does not send it to your application until you request it explicitly. The DBState function tells you when the data is available; if data is available, go to step 6. If you wish to send another query, return to step 3. If you are finished using the data source, skip to step 7.    6.    Call the DBGetItem function repeatedly to retrieve the data. The DBGetItem function retrieves the next data item from the data server. You can also use this function to obtain information about the next data item without retrieving the data. When you use the DBGetItem function to retrieve a data item, you must specify the location and size of the buffer into which the function is to place that item. If you know beforehand what kind of data to expect, you can allocate a buffer of the exact size you need. If you do not know what type of data to expect, you can first call the DBGetItem function with a NIL pointer to the data buffer. The DBGetItem function then returns information about the next data item without actually retrieving it. You can then allocate the appropriate buffer and call DBGetItem again. Alternatively, to avoid calling DBGetItem twice for each data item, you can allocate a buffer that you expect to be of sufficient size for any data item and call the DBGetItem function. If the buffer is not large enough for the data item, the DBGetItem function returns the rcDBError result code, but still returns information about the data item. You can then allocate the necessary buffer, call the DBUnGetItem function to go back one data item, and call the DBGetItem function again to retrieve the data item a second time.The DBGetItem function includes a timeout parameter that you can use to specify the maximum amount of time that the database extension should wait to receive results from the data server before canceling the command. If the database extension you are using does not support asynchronous execution of routines, you can use the timeout parameter to return control to your application while a query is executing. To use the timeout parameter in this way, call the DBGetItem function periodically, specifying a brief period of time for the timeout parameter. Your application can then retrieve the next data item as soon as execution of the query is complete without having to call the DBState function to determine when data is available. The DBGetItem function ignores the timeout parameter if you make an asynchronous call to this function.    7.    When you are finished using the data source, you must use the DBEnd function to terminate the session. You must call the DBEnd function after the DBInit function has returned a nonzero session ID, even if it also returned an error.The procedure in Listing 12-5 uses the low-level interface to send a Data Access Language routine to the Data Access Language server on a remote computer and then retrieves the results. The procedure initiates a session with a remote database and calls the MySendFragment routine (Listing 12-4) to send a query. Next, it executes the query, checks the status of the remote database server, and retrieves the data when it’s available. This example retrieves only one data item. To retrieve more than one data item, put the data-retrieval code in a loop.Listing 12-5 assumes that the database extension does not support asynchronous execution of Data Access Manager routines. For an example of asynchronous execution of routines, see Listing 12-1 beginning on page 12-18.Listing 12-5    Using the low-level interfacePROCEDURE MyLoLevel(VAR thisSession: LongInt; VAR sessErr: OSErr);VAR    theDDevName:                                                Str63;    theHost, theUser:                                                Str255;    thePasswd, theConnStr:                                                Str255;    packErr, initErr, sendErr, execErr:                                                OSErr;    stateErr, getErr, endErr:                                                OSErr;    myTimeout:                                                LongInt;    myType:                                                DBType;    len, places, flags:                                                Integer;    myBuffer:                                                Ptr;    myDataInfo:                                                Boolean;    myDataReturned:                                                Boolean;BEGIN    sessErr := noErr;                                {assume everything went fine}    packErr := InitDBPack;                                {init the Data Access Mgr}    {Set up values for theDDevName, theHost, theUser, thePasswd, }    { and theConnStr. You can display a dialog box prompting }    { the user to supply some of these parameters.}    theDDevName := 'DAL';    theHost := 'The Host System Name';    theUser := 'Joe User';    thePasswd := 'secret';    theConnStr := 'extra stuff as needed';    initErr := DBInit(thisSession, theDDevName, theHost, theUser,                            thePasswd, theConnStr, NIL);    IF initErr <> noErr THEN    BEGIN        sessErr := initErr;        IF thisSession <> 0 THEN endErr := DBEnd(thisSession, NIL);        EXIT(MyLoLevel);    END;    {send a query or query fragment to the remote data server}    sendErr := MySendFragment(thisSession);    {If there's an error, then probably something went wrong with }    { DBSend or DBSendItem.  Don't forget to end the session.}    IF sendErr <> noErr THEN    BEGIN        sessErr := sendErr;        endErr := DBEnd(thisSession, NIL);        EXIT(MyLoLevel);    END;    {The query has been sent.  This example assumes that }    { the query will return data.}     execErr := DBExec(thisSession, NIL);    IF execErr = noErr THEN    BEGIN        stateErr := rcDBExec;        WHILE (stateErr = rcDBExec) DO        BEGIN                        {while waiting for stateErr <> rcDBExec, }            MyGoDoSomething; { let other apps run}            stateErr := DBState(thisSession, NIL);        END;        {DBState returned a result code other than rcDBExec. }        { If it's rcDBValue, there are results to retrieve. }        { Otherwise, it's probably an error.}        IF stateErr = rcDBValue THEN        BEGIN            {call DBGetItem once to get info on the data item and }            { call DBGetItem a second time to get the data item}            myTimeout := 2*60;                            {2*60 ticks = 2 seconds}            myType := DBType(typeAnyType);            myDataInfo := FALSE;            WHILE NOT myDataInfo DO            BEGIN                getErr := DBGetItem(thisSession, myTimeout, myType,                                             len, places, flags, NIL, NIL);                {If you timed out, then give up control.  When }                { control returns, continue getting the info.}                IF getErr = rcDBBreak THEN MyGoDoSomething                ELSE IF (getErr = noErr) OR (getErr = rcDBValue) THEN                     myDataInfo := TRUE                ELSE                BEGIN                    sessErr := getErr;                    endErr := DBEnd(thisSession, NIL);                    EXIT(MyLoLevel);                END;            END; {while}            {At this point, you may want to examine the info }            { about the data item before calling DBGetItem a }            { second time to actually retrieve it.}            {MyGimmeSpace returns a pointer to where you want }            { the data item to go.}            myBuffer := MyGimmeSpace(len);            myDataReturned := FALSE;            WHILE NOT myDataReturned DO            BEGIN                getErr := DBGetItem(thisSession, myTimeout, myType,                                              len, places, flags, myBuffer,                                            NIL);                {If you timed out, then give up control.  When }                { control returns, continue getting the data.}                IF getErr = rcDBBreak THEN MyGoDoSomething                ELSE IF (getErr = noErr) OR                        (getErr = rcDBValue) THEN myDataReturned := TRUE                ELSE                BEGIN                    sessErr := getErr;                    endErr := DBEnd(thisSession, NIL);                    EXIT(MyLoLevel);                END;            END; {while}        END        ELSE sessErr := stateErr;    END    ELSE sessErr := execErr;    endErr := DBEnd(thisSession, NIL);END;Note that, even if you are using the low-level interface to send queries to the data server, you might want to use the high-level functions to retrieve data and convert it to text.Getting Information About Sessions in ProgressIf your application is only one of several on a single Macintosh computer connected to data servers, you can use the DBGetConnInfo and DBGetSessionNum functions to obtain information about the sessions in progress. If you know the session ID (which is returned by the DBInit function when you open a session), you can use the DBGetConnInfo function to determine the database extension being used, the name of the host system on which the session is running, the user name and connection string used to initiate the session, the time at which the session started, and the status of the session. The status of the session specifies whether the data server is executing a query or waiting for another query fragment, whether there is output data available, and whether execution of a query ended in an error.If you do not know the session ID, or if you want to get information about all open sessions, you can specify a database extension and a session number when you call the DBGetConnInfo function. Although there can be only one active session with a given session ID, session numbers are unique only for a specific database extension. Because the database extension assigns session numbers sequentially, starting with 1, you can call the DBGetConnInfo function repeatedly for a given database extension, incrementing the session number each time, to obtain information about all sessions open for that database extension. Your application need not have initiated the session to obtain information about it in this fashion.The DBGetSessionNum function returns the session number when you specify the session ID. You can use this function to determine the session numbers for the sessions opened by your own application. You might want this information, for example, so you can distinguish your own sessions from those opened by other applications when you use the DBGetConnInfo function to get information about all open sessions. Processing Query ResultsYou can use the low-level function DBGetItem to retrieve a single data item returned by a query, or you can use the high-level function DBGetQueryResults to retrieve all of the query results at once. If you use the DBGetQueryResults function, you can then use the DBResultsToText function to convert the results to ASCII text. The DBResultsToText function calls routines called result handlers, which are installed in memory by applications or by system extensions (files containing 'INIT' resources). This section discusses the use of the DBGetItem and DBGetQueryResults functions and describes how to write and install a result handler.Getting Query ResultsThe DBGetItem function retrieves a single data item that was returned by a data source in response to a query. When you call the DBGetItem function, you specify the data type to be retrieved. If you do not know what data type to expect, you can specify the typeAnyType constant for the dataType parameter, and the data server returns the next data item regardless of data type. It also returns information about the data item, including data type and length. If you do not know the length of the next data item, you can specify NIL for the buffer parameter in the DBGetItem function, and the data server returns the data type, length, and number of decimal places without retrieving the data item. The next time you call the DBGetItem function with a nonzero value for the buffer parameter, the function retrieves the data item. If you want to skip a data item, specify the typeDiscard constant for the dataType parameter. Then the next time you call the DBGetItem function, it retrieves the following data item.You should use the DBGetItem function if you want complete control over the retrieval of each item of data. If you want the Data Access Manager to retrieve the data for you, use the DBGetQueryResults function instead.Table 12-1 shows the data types recognized by the Data Access Manager. You use a constant to specify each data type, as follows:CONST        {data types}        typeAnyType                    =  0;                {can be any data type}         typeNone                    = 'none';                {no more data expected}        typeBoolea            n        = 'bool';                {Boolean}        typeSMInt                    = 'shor';                {short integer}        typeInteger                    = 'long';                {integer}        typeSMFloat                    = 'sing';                {short floating point}        typeFloat                    = 'doub';                {floating point}        typeDate                    = 'date';                {date}        typeTime                    = 'time';                {time}        typeTimeStamp                    = 'tims';                {date and time}        typeChar                    = 'TEXT';                {character}        typeDecimal                    = 'deci';                {decimal number}        typeMoney                    = 'mone';                {money value}        typeVChar                    = 'vcha';                {variable character}        typeVBin                    = 'vbin';                {variable binary}        typeLChar                    = 'lcha';                {long character}        typeLBin                    = 'lbin';                {long binary}        typeDiscard                    = 'disc';                {discard next data item}        typeUnknown                    = 'unkn';                {result handler for unknown }                                            { data type}        typeColBreak                    = 'colb';                {result handler for column break}        typeRowBreak                    = 'rowb';                {result handler for end of line}The writer of a database extension can define other data types to support specific data sources or data servers.Each data type has a standard definition, shown in Table 12-1. For example, if the DBGetItem function returns the typeInteger constant for the dataType parameter, you know that the data item represents an integer value and that a 4-byte buffer is necessary to hold it. Similarly, if you are using the DBSendItem function to send to the data server a data item that you identify as typeFloat, the data server expects to receive an 8-byte floating-point value. Notice that some of these data types are defined to have a specific length (referred to as an implied length), and some do not. The len parameter of the DBSendItem and DBGetItem functions indicates the length of an individual data item. The DBGetQueryResults function returns a handle to an array of lengths, decimal places, and flags in the colInfo field of the results record. The typeAnyType, typeColBreak, and typeRowBreak constants do not refer to specific data types, and therefore the length specification is not applicable for these constants.Table 12-1    Data types defined by the Data Access Manager (continued)Constant    Length    Definition    typeAnyType    NA    Any data type (used as an input parameter to the DBGetItem function only; never returned by the function).    typeNone    0    Empty.    typeBoolean    1 byte    TRUE (1) or FALSE (0).    typeSMInt    2 bytes    Signed integer value.    typeInteger    4 bytes    Signed long integer value.    typeSMFloat    4 bytes    Signed floating-point value.    typeFloat    8 bytes    Signed floating-point value.    typeDate    4 bytes    Date; a long integer value consisting of a year (most significant 16 bits), month (8 bits), and day (least significant 8 bits).    typeTime    4 bytes    Time; a long integer value consisting of an hour (0–23; most significant 8 bits), minute (8 bits), second (8 bits), and hundredths of a second (least significant 8 bits).    typeTimeStamp    8 bytes    Date and time. A long integer date value followed by a long integer time value.    typeChar    Any    Fixed-length character string, not NULL terminated. The length of the string is defined by the specific data source.    typeDecimal    Any    Packed decimal string. A contiguous string of 4-bit nibbles, each of which contains a decimal number, except for the low nibble of the highest-addressed byte (that is, the last nibble in the string), which contains a sign. The value of the sign nibble can be 10, 12, 14, or 15 for a positive number or 11 or 13 for a negative number; 12 is recommended for a positive number and 13 is recommended for a negative number. The most significant digit is the high-order nibble of the lowest-addressed byte (that is, the first nibble to appear in the string).The total number of nibbles (including the sign nibble) must be even; therefore, the high nibble of the highest-addressed byte of a number with an even number of digits must be 0.For example, the number +123 is represented as $123C.The number –1234 is represented as $01234D.The length of a packed decimal string is defined as the number of bytes, including any extra leading 0 and the sign nibble. A packed decimal string can have from 0 to 31 digits, not including the sign nibble.In addition to the length of a packed decimal string, each data item has an associated value that indicates the number of digits that follow the decimal place. The places parameter in the DBGetItem and DBSendItem functions indicates the number of decimal places in an individual data item. The DBGetQueryResults function returns the number of decimal places.    typeMoney    Any    Same as typeDecimal, but always has two decimal places.     typeVChar    Any    Variable-length character string, NULL terminated.            continued    typeVBin    Any    Not defined. Reserved for future use.    typeLChar    Any    Not defined. Reserved for future use.    typeLBin    Any    Not defined. Reserved for future use.    typeDiscard    NA    Do not retrieve the next data item (used as an input parameter to the DBGetItem function only; never returned by the function).    typeUnknown    NA    A dummy data type for the result handler that processes any data type for which no other result handler is available (used as an input parameter to the DBInstallResultHandler, DBRemoveResultHandler, and DBGetResultHandler functions only; never returned by the DBGetItem function).    typeColBreak    NA    A dummy data type for the result handler that the DBGetQueryResults function calls after each item that is not the last item in a row (used as an input parameter to the DBInstallResultHandler, DBRemoveResultHandler, and DBGetResultHandler functions only; never returned by the DBGetItem function).    typeRowBreak    NA    A dummy data type for the result handler that the DBGetQueryResults function calls at the end of each row (used as an input parameter to the DBInstallResultHandler, DBRemoveResultHandler, and DBGetResultHandler functions only; never returned by the DBGetItem function).    The DBGetQueryResults function retrieves all of the data that was returned by a data source in response to a query, unless insufficient memory is available to hold the data, in which case it retrieves as many complete rows of data as possible. The DBGetQueryResults function stores the data in a structure called a results record. You must allocate the results record data structure and pass this record to the DBGetQueryResults function. The Data Access Manager allocates the handles inside the results record. When your application is finished using the results record, you must deallocate both the results record and the handles inside the results record.The results record is defined by the ResultsRecord data type.TYPE ResultsRecord =     RECORD        numRows:                Integer;                        {number of rows retrieved}        numCols:                Integer;                        {number of columns per row}        colTypes:                ColTypesHandle;                        {type of data in each column}        colData:                Handle;                        {array of data items}        colInfo:                ColInfoHandle;                        {info about each data item}    END;The numRows field in the results record indicates the total number of rows retrieved. If the DBGetQueryResults function returns a result code other than rcDBValue, then not all of the data actually returned by the data source was retrieved. This could happen, for instance, if the user’s computer does not have sufficient memory space to hold all the data. In this case, your application can make more space available (by writing the data in the data record to disk, for example) and then call the DBGetQueryResults function again to complete retrieval of the data.NoteThe DBGetQueryResults function retrieves whole rows only; if it runs out of space in the middle of a row, it stores the partial row in a private buffer so that the data in the results record ends with the last complete row. Because the last partial row is no longer available from the data server, you cannot start to retrieve data with the DBGetQueryResults function and then switch to the DBGetItem function to complete the data retrieval.u The numCols field indicates the number of columns in each row of data.The colTypes field is a handle to an array of data types, specifying the type of data in each column. The number of elements in the array is equal to the value in the numCols field. Table 12-1 beginning on page 12-38 shows the standard data types. The colData field is a handle to the data retrieved by the DBGetQueryResults function.The colInfo field is a handle to an array of records of type DBColInfoRecord, each of which specifies the length, places, and flags for a data item. There are as many records in the array as there are data items retrieved by the DBGetQueryResults function. Here is the DBColInfoRecord type definition:TYPE DBColInfoRecord =     RECORD        len:                Integer;                    {length of data item}        places:                Integer;                    {places for decimal and }                                            { money data items}        flags:                Integer;                    {flags for data item}    END;The len field indicates the length of the data item. The DBGetQueryResults function returns a value in this field only for those data types that do not have implied lengths; see Table 12-1 beginning on page 12-38. The places field indicates the number of decimal places in data items of types typeMoney and typeDecimal. For all other data types, the places field returns 0. The least significant bit of the flags field is set to 1 if the data item is in the last column of the row. The third bit of the flags field is 1 if the data item is NULL. You can use the constants kDBLastColFlag and kDBNullFlag to test for these flag bits. Converting Query Results to TextThe DBResultsToText function provided by the high-level interface converts the data retrieved by the DBGetQueryResults function into strings of ASCII text. This function makes it easier for you to display retrieved data for the user. For the DBResultsToText function to convert data of a specific type to text, either the application or the system software must have a routine called a result handler. With System 7, Apple Computer, Inc., provides system result handlers for the data types listed here. (These data types are described in Table 12-1 beginning on page 12-38.) Data type    Constant    Data type    Constant    Boolean    typeBoolean    Time    typeTime    Short integer    typeSMInt    Date and time    typeTimeStamp    Integer    typeInteger    Character    typeChar    Short floating point    typeSMFloat    Decimal number    typeDecimal    Floating point    typeFloat    Money value    typeMoney    Date    typeDate    Variable character    typeVChar    NoteApple’s system result handler for the variable character (typeVChar) data type strips trailing spaces from the character string.u In addition to the result handlers for these standard data types, Apple provides the following three system result handlers, which correspond to no specific data type: Data type    Constant    Unknown     typeUnknown    Column break    typeColBreak    End of line    typeRowBreak    The typeUnknown result handler processes any data type for which no other result handler is available. The DBResultsToText function calls the typeColBreak result handler after each item that is not the last item in a row. This result handler does not correspond to any data type, but adds a delimiter character to separate columns of text. The default typeColBreak result handler inserts a tab character. Similarly, the DBResultsToText function calls the typeRowBreak result handler at the end of each row of data to add a character that separates the rows of text. The default typeRowBreak result handler inserts a return character. Your application can install your own typeColBreak and typeRowBreak result handlers to insert whatever characters you wish—or to insert no character at all, if you prefer.You can install result handlers for any data types you know about. When you call the DBInstallResultHandler function, you can specify whether the result handler you are installing is a system result handler. A system result handler is available to all applications that use the system. All other result handlers (called application result handlers) are associated with a particular application. The DBResultsToText function always uses a result handler for the current application in preference to a system result handler for the same data type. When you install a system result handler for the same data type as an already installed system result handler, the new result handler replaces the old one. Similarly, when you install an application result handler for the same data type as a result handler already installed for the same application, the new result handler replaces the old one for that application. Result handlers are stored in memory. The Data Access Manager installs its system result handlers the first time the Macintosh Operating System loads the Data Access Manager into memory. You must reinstall your own application result handlers each time your application starts up. You can also install your own system result handlers each time your application starts up, or you can provide a system extension (that is, a file with an 'INIT' resource) that installs system result handlers each time the user starts up the system.Here is a function declaration for a result handler function:FUNCTION MyResultHandler (dataType: DBType;                                   theLen, thePlaces, theFlags: Integer;                                   theData: Ptr; theText: Handle): OSErr;The dataType parameter specifies the data type of the data item that the DBResultsToText function is passing to the result handler. Table 12-1 beginning on page 12-38 describes the standard data types. The parameters theLen and thePlaces specify the length and number of decimal places of the data item that the DBResultsToText function wants the result handler to convert to text. The parameter theFlags is the value returned for the flags parameter by the DBGetItem function. If the least significant bit of this parameter is set to 1, the data item is in the last column of the row. If the third bit of this parameter is set to 1, the data item is NULL. You can use the constants kDBLastColFlag and kDBNullFlag to test for these flag bits.The parameter theData is a pointer to the data that the result handler is to convert to text.The parameter theText is a handle to the buffer that is to hold the text version of the data. The result handler should use the Memory Manager’s SetHandleSize function to increase the size of the buffer as necessary to hold the new text, and append the new text to the end of the text already in the buffer. The SetHandleSize function is described in the chapter “Memory Manager” in Inside Macintosh: Memory.If the result handler successfully converts the data to text, it should return a result code of 0 (noErr). You can use the DBInstallResultHandler function to install a result handler and the DBRemoveResultHandler function to remove an application result handler. You can install and replace system result handlers, but you cannot remove them. The following line of code installs an application result handler. The first parameter (typeInteger) specifies the data type that this result handler processes. The second parameter (MyTypeIntegerHandler) is a pointer to the result handler routine. The last parameter (FALSE) is a Boolean value specifying that this routine is not a system result handler.err := DBInstallResultHandler                             (typeInteger,@MyTypeIntegerHandler,FALSE);Listing 12-6 shows a result handler that converts the integer data type to text.Listing 12-6    A result handlerFUNCTION MyTypeIntegerHandler(datatype: DBType; theLen: Integer;                                        theData: Ptr;                                         theText: Handle): OSErr;VAR            theInt:                    LongInt;    theTextLen:                    LongInt;    temp:                    Str255;    atemp1:                    Ptr;    atemp2:                    LongInt;    atemp3:                    LongInt;BEGIN    BlockMove(theData, @theInt, sizeof(theInt));    NumToString(theInt, temp);                                                        {convert to text}    theTextLen := GetHandleSize(theText);                                                        {get current size }                                                            { of theText}                                                            {size text handle}    SetHandleSize(theText, theTextLen + LongInt(LENGTH(temp)));    IF (MemError <> noErr) THEN         MyTypeIntegerHandler := MemError    ELSE    BEGIN        atemp1 := Ptr(ORD(@temp));        atemp2 := LongInt(theText^) + theTextLen;        atemp3 := LongInt(LENGTH(temp));        {use BlockMove to append text}        BlockMove(P2CStr(atemp1), Ptr(atemp2), atemp3);        MyTypeIntegerHandler := MemError;    END;END;Creating a Query DocumentA query document is a file of type 'qery' that contains a 'qrsc' resource and one or more 'wstr' resources, and may contain a 'qdef' resource plus other resources. Query documents make it possible for you to write applications that can communicate with data servers without requiring familiarity with the command language used by the data server. Because a query document is most useful if it can be used by many different applications, no query document should depend on the presence of a particular application in order to function.An application can call the DBGetNewQuery function to convert a 'qrsc' resource into a query record in memory. A query record specifies connection information and also contains a handle to an array of queries; each query can be either a complete query or a template for a query. If the 'wstr' resource is a template, it contains the commands and data necessary to create a query, without any information that the user must add just before the query is sent. The 'qdef' resource contains a query definition function, which can modify the query record and, if necessary, fill in the query template to create a complete query. The DBStartQuery function sends the query pointed to by a query record to a data server. The following sections describe the contents of a query document, describe query records, and define the 'qrsc', 'wstr', and 'qdef' resources.User Interface Guidelines for Query DocumentsAll query documents should behave in fundamentally the same way. They should be self-explanatory and should never execute a query without an explicit command from the user. When your application opens a query document, the query document should display a dialog box with enough information about the query so that the user can decide if it’s the right query. The dialog box should describe the purpose of the query, what kind of data it transfers and in which direction, the type of data source it accesses, and any warnings or instructions. The dialog box can describe how the user interprets the data, such as the name of each field in a record. Figure 12-6 shows an example of a query document dialog box.Figure 12-6    A query document dialog boxThis dialog box should allow the user to cancel the request for data. In addition, it may be useful to allow the user to set parameters with text boxes, checkboxes, or radio buttons. For example, a query to a database of financial information could provide a list of these options: a trial balance, profit-and-loss statements, or net worth reports. Save the last set of user-specified parameters with the query document. This way the user can review the parameters used to generate the data or use the same parameters the next time. Once a query starts running, it must be able to complete its task without user intervention. If a query must run modally (that is, it must run to completion before returning control to the user), display a dialog box that shows the query’s progress and be sure to return control to the user as soon as possible. The philosophy of this process is similar to that of receiving electronic mail—that is, inform the user when the information arrives, but let the user decide when to read it. Whenever possible, query documents should check that data is compatible before transmitting it to a data source. Establish a connection with a data source only after you have checked the data.Contents of a Query DocumentThe query document must containn    one 'qrsc' resource, as defined in the next section, “Query Records and Query Resources”n    one 'STR#' resource that contains the name of the database extension to be used, plus any host, user name, password, and connection string needed for the DBInit function n    one or more 'wstr' resources containing queries—that is, strings of commands and data that the DBSend function sends to the data server and that the DBExec function executesA 'wstr' resource consists of a 2-byte length field followed by a character string. (The w in 'wstr' refers to the length word as opposed to the length byte used in an 'STR ' resource.) Each 'wstr' resource contains one query (or one query template, to be modified by the query definition function before it is sent to the data server). The 'qrsc' resource includes an array that lists the resource ID numbers of all of the 'wstr' resources in the query document and an index into the array that specifies which one of the 'wstr' resources should be sent to the data server.In addition, the query document may containn    a 'qdef' resource that contains a query definition functionn    any resources needed by the query definition function, such as 'DLOG' and 'DITL' resources (which support dialog boxes)n    resources to support an icon (to replace the default icon that the Finder uses for files of type 'qery'); see the chapter “Finder Interface” in Inside Macintosh: Macintosh Toolbox Essentials for more information on icon resources and for guidelines on designing iconsFigure 12-7 illustrates the relationship between the resources in a query document and the query record. Figure 12-7    The relationship between resources in a query document and the query recordThe query document in Figure 12-7 contains a 'qrsc' resource that specifies the resource ID of a 'qdef' resource, the resource IDs of three 'wstr' resources, and the resource ID of an 'STR#' resource. It also specifies which of the three 'wstr' resources represents the current query.The DBGetNewQuery function creates the query record and partial queries from this information. Your application can use the DBStartQuery function to send a query to a data server. The DBStartQuery function calls the query definition function referred to by the query record (if any). The query definition function can prompt the user for information and modify the query as needed. Figure 12-8 illustrates a query record that contains a handle to an array of queries, a handle to a query definition function, and an index that identifies the current query. The query definition function displays a dialog box and modifies the current query according to the user’s input. Once the query definition function modifies the current query and returns, the DBStartQuery function sends the query to the data server.Figure 12-8    The relationship between a query definition function and queriesQuery Records and Query ResourcesThe DBGetNewQuery function converts the 'qrsc' resource in the query document into a query record in memory. The query definition function can then modify the query record before the application sends the query to the data server. See “The Query Record” beginning on page 12-56 for a description of the query record. See “The Query Resource” beginning on page 12-90 for the format of a 'qrsc' resource. The next section provides information about query definition functions.Writing a Query Definition FunctionBefore the DBStartQuery function sends a query to a data server, it calls the query definition function specified by the queryProc field in the query record. The purpose of the query definition function is to modify the query and the query record before the query is sent to the data server. The query definition function can use dialog boxes to request information from the user. Because a query document is most useful if it can be used by many different applications, no query definition function should depend on the presence of a particular application.If you want to include a query definition function, you must make it the first piece of code in a resource of type 'qdef' in the query document. Here is a function declaration for a query definition function. FUNCTION MyQDef (VAR sessID: LongInt; query: QueryHandle): OSErr;If the application has already initiated a session with the data server, the DBStartQuery function passes the session ID for that session in the sessID parameter to the query definition function. If the query definition function receives a 0 in this parameter, then the Data Access Manager has not initiated a session. In this case, the query definition function can return a 0 in the sessID parameter, or it can call the DBInit function to initiate a session and then return the session ID in this parameter. If the query definition function returns a 0 in the sessID parameter, the DBStartQuery function calls the DBInit function and then calls the DBSend function to send a query to the data server. If the query definition function returns a session ID in this parameter, the DBStartQuery function calls the DBSend function immediately.The query parameter to the query definition function specifies a handle to the query record. The query definition function can modify any of the fields in the query record, including the currQuery field that specifies which query is to be sent to the data server. In addition, the query definition function can modify an existing query or create a new query, adding the handle to the new query to the query list. Note that, because a query in memory consists only of a 2-byte length value followed by a character string, the query definition function has to know the exact contents and structure of a query in order to modify it.The query definition function must return the noErr result code as the function result if the function executed successfully. If it returns any other value, the DBStartQuery function does not call the DBSend function. The query definition function can return any result code, including noErr, userCanceledErr, or rcDBError.When the DBStartQuery function calls the query definition function, the current resource file is the file that contains the 'qrsc' resource from which the Data Access Manager created the query record. When the query definition function returns control to the Data Access Manager, the current resource file must be unchanged. See the chapter “Resource Manager” in Inside Macintosh: More Macintosh Toolbox for more information on the current resource file.The query definition function can allocate memory and use the dataHandle field in the query record to store a handle to it. The query definition function must free any memory it allocates before terminating.Listing 12-7 shows a query definition function that uses a dialog box to prompt the user for a user name and password and then modifies the query record accordingly.Listing 12-7    A query definition functionFUNCTION MyQDef(VAR sessID: LongInt; query: QueryHandle): OSErr;CONST    myNameItem                         =     7;    myPassWordItem                         =     8;VAR    myNumRes:                        Integer;    myResList:                        ResListHandle;    myResLPtr:                        ResListPtr;    myIndex:                        Integer;    myDialog:                        DialogPtr;    myDlogID:                        Integer;    itemType:                        Integer;    itemHName:                        Handle;    itemHPasswd:                        Handle;    itemBox:                        Rect;    mySTR:                        ARRAY[1..2] OF Str255;    itemHit:                        Integer;    myQErr:                        OsErr;BEGIN    {If sessID = 0 no session has been initiated. Your qdef may }    { optionally initiate a session, or it can let DBStartQuery }    { take care of this.  In this example, the qdef doesn't }    { check the sessID parameter.}    HLock(Handle(query));    myNumRes := query^^.numRes;    myResList := query^^.resList;    HLock(Handle(myResList));    myResLPtr := myResList^;    myIndex := 0;    {look for a 'DLOG' resource}    WHILE (myIndex < myNumRes) AND            (myResLPtr^[myIndex].theType <> 'DLOG') DO    BEGIN        myIndex := myIndex + 1;    END;    IF (myIndex < myNumRes) THEN                                        {found the 'DLOG' resource}        myDlogID := myResLPtr^[myIndex].id    ELSE    BEGIN        {The 'DLOG' wasn't found; exit with no error.  This }        { is probably OK; it just means that the query }        { and the query record don't get modified.}        MyQDEF := noErr;        HUnlock(Handle(query));        HUnlock(Handle(myResList));        EXIT(MyQDef);    END;    {found the 'DLOG' and its ID; now display the dialog box}    myDialog := GetNewDialog(myDlogID, Ptr(NIL), WindowPtr(-1));    SetPort(GrafPtr(myDialog));    REPEAT        ModalDialog(@MyEventFilter, itemHit);    UNTIL ((itemHit = kOK) OR (itemHit = kCancel));    IF itemHit = kOK THEN    BEGIN        {The user clicked the OK button. Update the user }        { and password fields of the query record.}        GetDialogItem(myDialog, myNameItem, itemType, itemHName,                          itemBox);        GetDialogItemText(itemHName, mySTR[1]);        GetDialogItem(myDialog, myPassWordItem, itemType,                         itemHPasswd, itemBox);        GetDialogItemText(itemHPasswd, mySTR[2]);        {Now you can change the query record or the query itself. }        { What you change is entirely up to you. In this example, }        { the qdef changes only the user and password fields }        { of the query record.}        query^^.user := mySTR[1];        query^^.password := mySTR[2];        MyQDef := noErr;    END    ELSE         MyQDef := userCanceledErr;    HUnlock(Handle(query));    HUnlock(Handle(myResList));    DisposDialog(myDialog);END;Data Access Manager ReferenceThis section describes the data structures, routines, and resources that are specific to the Data Access Manager. The “Data Structures” section shows the data structures for the asynchronous parameter block, the results record, the query record, and the data item record. The “Data Access Manager Routines” section beginning on page 12-59 describes routines for using the high-level and low-level interfaces, including initializing the Data Access Manager, handling query documents and results, controlling sessions, sending and executing queries, retrieving results, and installing and removing result handlers. The “Resources” section beginning on page 12-90 describes the query resource, the query string resource, and the query definition function resource.Data StructuresThis section describes the data structures that you use to provide information to the Data Access Manager or that the Data Access Manager uses to provide information to your application.You provide a pointer to an asynchronous parameter block as a parameter to the DBStartQuery, DBGetQueryResults, DBInit, DBEnd, DBGetSessionNum, DBKill, DBSend, DBSendItem, DBExec, DBState, DBGetErr, DBBreak, DBGetItem, and DBUnGetItem functions.The query record specifies connection information and contains a handle to an array of one or more complete queries or query templates. The DBGetNewQuery function returns a handle to a query record, and you provide a handle to a query record as a parameter to the DBStartQuery and DBDisposeQuery functions.You use the results record to store the data that was returned by a data source in response to a query. The results record is a parameter to the DBGetQueryResults and DBResultsToText functions.The Asynchronous Parameter BlockEach Data Access Manager routine that can be called asynchronously (that is, that can return control to your application before it has completed execution) takes as a parameter a pointer to a parameter block known as the asynchronous parameter block. If you specify NIL for this parameter, the routine does not return control to your application until it has completed execution. NoteThe asynchronous parameter block is passed on to the database extension, which is responsible for implementing the asynchronous routine. If the database extension does not support asynchronous routines, the Data Access Manager returns the rcDBAsyncNotSupp result code and terminates execution of the routine.uThe DBAsyncParamBlockRec data type defines the asynchronous parameter block.TYPE     DBAsyncParamBlockRec =     RECORD        completionProc:                        ProcPtr;            {pointer to completion routine}        result:                        OSErr;            {result of call}        userRef:                        LongInt;            {reserved for use by application}        ddevRef:                        LongInt;            {reserved for use by database }                                            { extension}        reserved:                        LongInt;            {reserved for use by Data }                                            { Access Manager}    END;    DBAsyncParmBlkPtr = ^DBAsyncParamBlockRec;Field descriptionscompletionProcPoints to a completion routine that the database extension calls when it has completed executing the asynchronous function. Before calling the completion routine, the Data Access Manager places a pointer to the asynchronous parameter block in the A0 register. If you do not want to use a completion routine, set this parameter to NIL.result     Returns the result code for the called routine. The database extension sets this field to 1 while the routine is executing and places the result code in it when the routine completes. Your application can poll this field to determine when an asynchronous routine has completed execution. userRef    Reserved for the application’s use. Because the Data Access Manager passes a pointer to the parameter block to the completion routine, you can use this field to pass information to the completion routine.ddevRef    Reserved for use by the database extension.reserved    Reserved for use by the Data Access Manager.The Query RecordThe DBGetNewQuery function converts a 'qrsc' resource in a query document into a query record in memory and returns a handle to the query record. The query record specifies connection information and also contains a handle to an array of queries; each query can be either a complete query or a template for a query. The DBGetNewQuery function creates the queries from the 'wstr' resources stored in the query document. The QueryRecord data type defines a query record.TYPE QueryRecord =     RECORD        version:                Integer;                        {query record format version}        id:                Integer;                        {resource ID of 'qrsc'}        queryProc:                Handle;                        {handle to qdef}        ddevName:                Str63;                        {name of database extension}        host:                Str255;                        {name of host computer}        user:                Str255;                        {name of user}        password:                Str255;                        {user's password}        connStr:                Str255;                        {connection string}        currQuery:                Integer;                        {index of current query}        numQueries:                Integer;                        {number of queries in list}        queryList:                QueryListHandle;                        {handle to array of }                                                { handles to text}        numRes:                Integer;                        {number of resources in list}        resList:                ResListHandle;                        {handle to array of resource }                                                { list elements}        dataHandle:                Handle;                        {handle to memory for qdef}        refCon:                LongInt;                        {reserved for use by app}    END;QueryPtr                 = ^QueryRecord;                                {pointer to query record}QueryHandle     = ^QueryPtr;                                            {handle to query record}Field descriptionsversion    The version number of the query record format. For the Data Access Manager released with System 7, the version number is 0.id    The resource ID of the 'qrsc' resource from which the Data Access Manager created this query record.queryProc    A handle to the query definition function that the DBStartQuery function calls. This handle is NIL if there is no query definition function—that is, if the DBStartQuery function should send the query specified by this query record to the data server without modifications.ddevName    The database extension name used as a parameter to the DBInit function. host    The name of the host computer system used as a parameter to the DBInit function. user    The name of the user, used as a parameter to the DBInit function.password    The user’s password, used as a parameter to the DBInit function. connStr    The connection string used as a parameter to the DBInit function. currQuery    An index value from 1 through numQueries, indicating which element in the array of query handles represents the current query. The current query is the one actually sent to the data server. If the query document contains more than one 'wstr' resource, the query definition function can prompt the user to select a new current query and modify this field in the query record appropriately. numQueries    The number of queries referred to by the queryList field.queryList    A handle to an array of handles. Each handle in this array refers to a query. Each query is created from a 'wstr' resource in the query document and is stored in memory as a 2-byte length field followed by ASCII text. (The length does not include the 2 bytes of the length field.) The query definition function can create a new query. To add a new handle to the array of handles, use the Memory Manager’s SetHandleSize function to increase the size of the array. Don’t forget to change the value of the numQueries field as well.numRes    The number of resources referred to by the resList field.resList    A handle to an array of records of type ResListElem. Each record in the array contains the type and ID of a resource that is needed by the query definition function.                     TYPE ResListElem =                         RECORD                            theType:            ResType;                {resource type}                            id:            Integer;                {resource ID}                        END;dataHandle    A handle to memory for use by the query definition function. When the Data Access Manager first creates the query record, it sets this field to NIL. The query definition function can allocate memory and place a handle to it in this field. The query definition function should dispose of any memory it allocates before it returns control to the Data Access Manager.refCon    The query record’s reference value. The application can use this field for any purpose.The Results RecordThe results record describes the data that was returned by a data source in response to a query. To get the results of a query, allocate a results record and pass this record to the DBGetQueryResults function. The Data Access Manager allocates the handles inside the results record. When your application is finished using the results record, you must deallocate both the results record and the handles inside the results record.The results record is defined by the ResultsRecord data type.TYPE ResultsRecord =     RECORD        numRows:                Integer;                        {number of rows retrieved}        numCols:                Integer;                        {number of columns per row}        colTypes:                ColTypesHandle;                        {type of data in each column}        colData:                Handle;                        {array of data items}        colInfo:                ColInfoHandle;                        {info about each data item}    END;Field descriptionsnumRows    The total number of rows retrieved. If the DBGetQueryResults function returns a result code other than rcDBValue, then not all of the data actually returned by the data source was retrieved. This could happen, for instance, if the user’s computer does not have sufficient memory space to hold all the data. In this case, your application can make more space available (by writing the data in the data record to disk, for example) and then call the DBGetQueryResults function again to complete retrieval of the data.NoteThe DBGetQueryResults function retrieves whole rows only; if it runs out of space in the middle of a row, it stores the partial row in a private buffer so that the data in the results record ends with the last complete row. Because the last partial row is no longer available from the data server, you cannot start to retrieve data with the DBGetQueryResults function and then switch to the DBGetItem function to complete the data retrieval.u numCols    The number of columns in each row of data.colTypes    A handle to an array of data types, specifying the type of data in each column. The number of elements in the array is equal to the value in the numCols field. Table 12-1 beginning on page 12-38 shows the standard data types. colData    A handle to the data retrieved by the DBGetQueryResults function.colInfo     A handle to an array of records of type DBColInfoRecord, each of which specifies the length, places, and flags for a data item. There are as many records in the array as there are data items retrieved by the DBGetQueryResults function. Here is the DBColInfoRecord type definition:                    TYPE DBColInfoRecord =                         RECORD                            len:            Integer;                {length of data item}                            places:            Integer;                {places for decimal }                                                        { and money data items}                            flags:            Integer;                {flags for data item}                        END;    The len field indicates the length of the data item. The DBGetQueryResults function returns a value in this field only for those data types that do not have implied lengths; see Table 12-1 on page 12-38 for a list of these data types.     The places field indicates the number of decimal places in data items of types typeMoney and typeDecimal. For all other data types, the places field returns 0.     The least significant bit of the flags field is set to 1 if the data item is in the last column of the row. The third bit of the flags field is 1 if the data item is NULL. You can use the constants kDBLastColFlag and kDBNullFlag to test for these flag bits. Data Access Manager RoutinesThe Data Access Manager has high-level routines, low-level routines, and routines that manipulate result handlers. This section describes all of the Data Access Manager routines.All of the low-level routines and some of the high-level routines accept a pointer to an asynchronous parameter block as a parameter. For these routines, see “The Asynchronous Parameter Block” beginning on page 12-55 for a description of the fields in the parameter block.If you specify a nonzero value for the pointer to the asynchronous parameter block, the database extension executes the function asynchronously—that is, it returns control to the Data Access Manager before the routine has completed execution, and the Data Access Manager returns control to your application. If you specify NIL for this parameter, the database extension does not return control to your application until the routine has finished execution. Your application must call the Event Manager’s WaitNextEvent function periodically to allow an asynchronous routine to complete execution. The WaitNextEvent function is described in the chapter “Event Manager” in Inside Macintosh: Macintosh Toolbox Essentials.You can tell when an asynchronous routine has completed execution and check the result code by looking at values in the asynchronous parameter block. You can use the DBKill function to cancel an asynchronous routine.NoteA noErr result code returned by a routine that has been called asynchronously indicates only that the routine began execution successfully. You must check the result field of the asynchronous parameter block for the final result of the routine.uAssembly-Language NoteYou can invoke each of the Data Access Manager routines with a macro that has the same name as the routine, but preceded with an underscore; for example, the macro for the DBInit function is named _DBInit. Each of these macros places a routine selector in the D0 register and calls the trap _Pack13. The routine selectors are listed in each routine description and in “Assembly-Language Summary” beginning on page 12-103.uInitializing the Data Access ManagerYou must initialize the Data Access Manager before you can use it.InitDBPackUse the InitDBPack function to initialize the Data Access Manager. FUNCTION InitDBPack: OSErr;DESCRIPTIONThe InitDBPack function initializes the Data Access Manager. You must call the InitDBPack function before you call any other Data Access Manager routines. If the Data Access Manager has already been initialized, the InitDBPack function returns the noErr result code but does nothing else.The interface routine that implements the InitDBPack function includes a version number for the Data Access Manager. If the Data Access Manager is a different version from that specified by the interface routine, then the InitDBPack function returns the rcDBWrongVersion result code.SPECIAL CONSIDERATIONSThe InitDBPack function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the InitDBPack function areTrap macro    Selector    _InitDBPack    $0100    RESULT CODESnoErr    0    No error    rcDBWrongVersion    –812    Wrong version number    High-Level Interface: Handling Query DocumentsThe high-level interface to the Data Access Manager allows applications to manipulate query documents and to get the results of the query provided by a query document. The use and contents of query documents are discussed in “Creating a Query Document” beginning on page 12-46. The routines described in this section create query records, dispose of query records, and use query documents to establish communication with and send queries to a data server. For a general discussion of the high-level interface, see “The High-Level Interface” beginning on page 12-7 . For instructions on using the high-level interface, refer to “Using the High-Level Interface” beginning on page 12-14.DBGetNewQueryYou can use the DBGetNewQuery function to create a query record.FUNCTION DBGetNewQuery (queryID: Integer;                                 VAR query: QueryHandle): OSErr;queryID    The resource ID of a 'qrsc' resource. query    Returns a handle to the query record. DESCRIPTIONThe DBGetNewQuery function creates a query record from the specified 'qrsc' resource. The resource file that contains the 'qrsc' resource must remain open until after the DBStartQuery function has completed execution. If you do not already know the resource ID of the 'qrsc' resource (for example, if you call the StandardGetFile procedure to let the user select the query document), you can use Resource Manager routines to determine the resource ID. SPECIAL CONSIDERATIONSThe DBGetNewQuery function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBGetNewQuery function areTrap macro    Selector    _DBGetNewQuery    $030F    RESULT CODESnoErr    0    No error    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOSee Listing 12-1 beginning on page 12-18 for an example of the use of the DBGetNewQuery function. For a description of the query record, see page 12-56. For a description of the 'qrsc' resource, see “The Query Resource” beginning on page 12-90. The StandardGetFile procedure is described in the chapter “Standard File Package” in Inside Macintosh: Files, and Resource Manager routines are described in the chapter “Resource Manager” in Inside Macintosh: More Macintosh Toolbox. DBDisposeQueryWhen you are finished using a query record, call DBDisposeQuery to dispose of the query record.FUNCTION DBDisposeQuery (query: QueryHandle): OSErr;query    A handle to the query record to dispose.DESCRIPTIONThe DBDisposeQuery function disposes of a query record and frees all the memory that the Data Access Manager allocated when it created the query record.SPECIAL CONSIDERATIONSThe DBDisposeQuery function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBDisposeQuery function areTrap macro    Selector    _DBDisposeQuery    $0210    RESULT CODESnoErr    0    No error    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOSee Listing 12-1 beginning on page 12-18 for an example of the use of the DBDisposeQuery function in the high-level interface. For a description of the query record, see page 12-56.DBStartQueryUse the DBStartQuery function to initiate the process of sending a query to a data server.FUNCTION DBStartQuery (VAR sessID: LongInt; query: QueryHandle;                              statusProc: ProcPtr;                               asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    A session ID that identifies a session with the data server. If you specify 0 for this parameter, then the DBStartQuery function initiates a session and returns the session ID in the sessID parameter.query    A handle to a query record. statusProcA pointer to a status routine that your application can use to update its windows after the query definition function has completed execution. (The DBStartQuery function does not attempt to update your application’s windows.) The DBStartQuery function also calls your status routine before it initiates a session with a data server, after it calls the DBInit function, after it calls the DBSend function, and after it calls the DBExec function. Status routines are discussed in “Writing a Status Routine for High-Level Functions” beginning on page 12-22.asyncPB    A pointer to an asynchronous parameter block. When specified, the DBStartQuery function calls the DBInit, DBSend, and DBExec functions asynchronously. As soon as the DBInit function has started execution, it returns control to your application. Your application must then call the Event Manager’s WaitNextEvent function periodically to allow these asynchronous routines to run, and it must check the result field of the asynchronous parameter block to determine when each routine has completed execution.DESCRIPTIONThe DBStartQuery function performs the following tasks, in the order specified:    1.    It calls the query definition function (if any) pointed to by the query record. The query definition function modifies the query record and the query, usually by asking the user for input. The query definition function can display a dialog box that gives the user the option of canceling the query; if the user does cancel the query, the DBStartQuery function returns the userCanceledErr result code.    2.    If you specify a nonzero value for the statusProc parameter, the DBStartQuery function calls your status routine with the kDBUpdateWind constant in the message parameter so that your application can update its windows.    3.    If you specify a nonzero value for the statusProc parameter, the DBStartQuery function calls your status routine with the kDBAboutToInit constant in the message parameter so that your application can display a dialog box informing the user that a session is about to be initiated with a data server, and giving the user the option of canceling execution of the function.    4.    If the sessID parameter is 0, the DBStartQuery function calls the DBInit function to initiate a session, and returns a session ID.     5.    If you specify a nonzero value for the statusProc parameter and the DBStartQuery function calls the DBInit function, the DBStartQuery function calls your status routine with the kDBInitComplete constant in the message parameter and the result of the DBInit function in the function result.    6.    The DBStartQuery function calls the DBSend function to send the query to the data server.    7.    If you specify a nonzero value for the statusProc parameter, the DBStartQuery function calls your status routine with the kDBSendComplete constant in the message parameter and the result of the DBSend function in the result parameter.    8.    The DBStartQuery function calls the DBExec function to execute the query.    9.    If you specify a nonzero value for the statusProc parameter, the DBStartQuery function calls your status routine with the kDBExecComplete constant in the message parameter and the result of the DBExec function in the result parameter.    10.    If you specify a nonzero value for the statusProc parameter, the DBStartQuery function calls your status routine with the kDBStartQueryComplete constant in the message parameter and the result of the DBStartQuery function in the result parameter.SPECIAL CONSIDERATIONSThe DBStartQuery function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBStartQuery function areTrap macro    Selector    _DBStartQuery    $0811    RESULT CODESnoErr    0    No error    userCanceledErr    –128    User canceled the query     rcDBError    –802    Error initiating session, sending text, or executing query    rcDBBadSessID    –806    Session ID is invalid    rcDBBadDDev    –808    Couldn’t find the specified database extension, or error occurred in opening database extension    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOSee “Using the High-Level Interface” beginning on page 12-14 for a general description of how the DBStartQuery function works in conjunction with other Data Access Manager routines. See Listing 12-1 beginning on page 12-18 for an example of the use of the DBStartQuery function. For a description of the query record, see page 12-56. For information on how to write a query definition function or status routine, see “Writing a Query Definition Function” beginning on page 12-51 and “Writing a Status Routine for High-Level Functions” beginning on page 12-22, respectively. Descriptions of the DBInit, DBSend, and DBExec functions begin on page 12-68, page 12-76, and page 12-78, respectively. High-Level Interface: Handling Query ResultsThe high-level interface to the Data Access Manager allows applications to manipulate query documents and to get the results of the query provided by a query document. The high-level routines in this section retrieve query results and convert them to text. DBGetQueryResultsYou can use the DBGetQueryResults function to retrieve the results of a query. FUNCTION DBGetQueryResults (sessID: LongInt;                                      VAR results: ResultsRecord;                                      timeout: LongInt; statusProc: ProcPtr;                                      asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    The session ID of the session from which you wish to retrieve results.results    The results record, which contains handles to the retrieved data. timeout     The value that the DBGetQueryResults function uses for the timeout parameter each time it calls the DBGetItem function. The timeout parameter specifies the maximum amount of time that the database extension should wait to receive results from the data server before canceling the DBGetItem function. Specify the timeout parameter in sixtieths of a second. To disable the timeout feature, set the timeout parameter to the kDBWaitForever constant. Some database extensions ignore the timeout parameter when you specify a nonzero value for the asyncPB parameter.statusProcA pointer to a status routine that you provide. The DBGetQueryResults function calls your status routine after it calls the DBGetItem function to retrieve a data item. When it calls the status routine, the DBGetQueryResults function provides the result of the DBGetItem function, the data type, the data length, the number of decimal places, the flags associated with the data item, and a pointer to the data item. asyncPB    A pointer to an asynchronous parameter block. If specified, the DBGetQueryResults function calls the DBGetItem function asynchronously for each data item. As soon as the DBGetItem function has started execution, it returns control to your application. Your application must then call the Event Manager’s WaitNextEvent function periodically to allow this asynchronous routine to run, and it must check the result field of the asynchronous parameter block to determine when the routine has completed execution.DESCRIPTIONThe DBGetQueryResults function retrieves the results returned by a query and places them in memory. If there is sufficient memory available, this function retrieves all of the results at once. If the DBGetQueryResults function runs out of memory, it places as much data as possible in memory, up to the last whole row. You can then make more memory available and call the DBGetQueryResults function again to retrieve more data. You must allocate the results record and pass this record to the DBGetQueryResults function. The Data Access Manager allocates the handles inside the results record. When your application is finished using the results record, you must deallocate both the results record and the handles inside the results record.The DBGetQueryResults function can be used to retrieve the results of any query, not only queries sent and executed by the DBStartQuery function.SPECIAL CONSIDERATIONSThe DBGetQueryResults function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBGetQueryResults function areTrap macro    Selector    _DBGetQueryResults    $0A12    RESULT CODESnoErr    0    No error    userCanceledErr    –128    Function canceled by status routine    rcDBValue    –801    Data available     rcDBError    –802    Query execution ended in an error    rcDBBreak    –804    Function timed out    rcDBExec    –805    Query currently executing     rcDBBadSessID    –806    Session ID is invalid    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOSee Listing 12-1 beginning on page 12-18 for an example of the use of the DBGetQueryResults function. See page 12-55 for a description of the asynchronous parameter block. Descriptions of the DBStartQuery and DBGetItem functions begin on page 12-63 and page 12-83, respectively. For more information on results records, see “The Results Record” beginning on page 12-58 and “Getting Query Results” beginning on page 12-36. For more information on status routines, see “Writing a Status Routine for High-Level Functions” beginning on page 12-22. DBResultsToTextAfter retrieving a results record from DBGetQueryResults, you can use the DBResultsToText function to convert the returned data to text. FUNCTION DBResultsToText (results: ResultsRecord;                                   VAR theText: Handle): OSErr;results    The results record returned by the DBGetQueryResults function. theText    The DBResultsToText function returns a handle to the converted text in this parameter. This handle is allocated by the Data Access Manager.DESCRIPTIONThe DBResultsToText function calls result handlers to convert to text the data retrieved by the DBGetQueryResults function. SPECIAL CONSIDERATIONSThe DBResultsToText function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBResultsToText function areTrap macro    Selector    _DBResultsToText    $0413    RESULT CODESnoErr    0    No error    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOSee Listing 12-1 begining on page 12-18 for an example of the use of the DBResultsToText function. See “Converting Query Results to Text” beginning on page 12-42 for a discussion of result handlers. Low-Level Interface: Controlling the SessionThe low-level interface to the Data Access Manager allows applications to open and close sessions with a data server, send and execute queries, retrieve query results, and obtain information about any current session. DBInitUse the DBInit function to initiate a session with a data server. FUNCTION DBInit (VAR sessID: LongInt; ddevName: Str63;                       host: Str255; user: Str255; password: Str255;                      connStr: Str255;                       asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    The DBInit function returns the session ID in this parameter. This session ID is unique; no other current session, for any database extension, has the same session ID. You must specify the session ID any time you want to send data to or retrieve data from this session. Depending on the database extension you are using, the DBInit function might return a session ID of 0 if it fails to initiate a session, or it might return a nonzero session ID and a result code other than noErr. In the latter case, you can pass the session ID to the DBGetErr function to determine the cause of the error.ddevName    A string of no more than 63 characters that specifies the name of the database extension. The name of the database extension is contained in the database extension file in a resource of type 'STR ' with a resource ID of 128. For the Data Access Language database extension provided by Apple, for example, this string is “DAL”.host    The name of the host system on which the data server is located. This name depends on the manner in which the database extension initiates communication with the data server and how the system administrator has set up the computer system.user    The name of the user.password    The password associated with the user name.connStr    A string that is passed to the data server, which might pass it on to the database management software on the host computer. This string is necessary in some systems to complete log-on procedures.asyncPB    A pointer to an asynchronous parameter block. If you do not want to call the function asynchronously, set this parameter to NIL.DESCRIPTIONYou must initiate a session before you call any Data Access Manager function that requires a session ID as an input parameter. If the DBInit function returns a nonzero session ID, you must call the DBEnd function to terminate the session, even if the DBInit function also returns a result code other than noErr.Because the high-level function DBStartQuery can call the DBInit function, you do not have to call the DBInit function if you have called the DBStartQuery function.SPECIAL CONSIDERATIONSThe DBInit function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBInit function areTrap macro    Selector    _DBInit    $0E02    RESULT CODESnoErr    0    No error    rcDBError    –802    Error initiating session    rcDBBadDDev    –808    Couldn’t find the specified database extension, or error occurred in opening database extension    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a description of the asynchronous parameter block, see page 12-55. See Listing 12-5 beginning on page 12-33 for an example of the use of the DBInit function. See page 12-63 for a description of the DBStartQuery function. The DBEnd function is described next.DBEndYou must call the DBEnd function to terminate a session.FUNCTION DBEnd (sessID: LongInt;                      asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    The session ID that was returned by the DBInit function.asyncPB    A pointer to an asynchronous parameter block. If you do not want to call the function asynchronously, set this parameter to NIL.DESCRIPTIONThe DBEnd function terminates a session with a data server and terminates the network connection between the application and the host computer. SPECIAL CONSIDERATIONSThe DBEnd function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBEnd function areTrap macro    Selector    _DBEnd    $0403    RESULT CODESnoErr    0    No error    rcDBError    –802    Error ending session    rcDBBadSessID    –806    Session ID is invalid    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a description of the asynchronous parameter block, see page 12-55. DBGetConnInfoThe DBGetConnInfo function returns information about the specified session, including n    the version of the database extensionn    the name of the host system on which the session is runningn    the user namen    the connection string that was used to initiate communicationn    the name of the networkn    the time at which the session started, in ticks (sixtieths of a second)n    the status of the sessionFUNCTION DBGetConnInfo (sessID: LongInt; sessNum: Integer;                                 VAR returnedID: LongInt;                                VAR version: LongInt;                                 VAR ddevName: Str63;                                 VAR host: Str255; VAR user: Str255;                                VAR network: Str255; VAR connStr: Str255;                                 VAR start: LongInt; VAR state: OSErr;                                 asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    The session ID that was returned by the DBInit function. If you include a nonzero value for the sessID parameter when you call the DBGetConnInfo function, the function returns the name of the database extension in the ddevName parameter. If you use 0 for the sessID parameter and specify the database extension and session number instead (in the ddevName and sessNum parameters), the function returns the session ID in the returnedID parameter.sessNum    The session number of the session about which you want information. If you specify a nonzero session number, you must also provide the database extension in the ddevName parameter.returnedIDReturns the session ID if you specify the session number and the database extension.version    Returns the version number of the database extension that is currently in use.ddevName    A string of no more than 63 characters that specifies the name of the database extension. If you specify 0 for the session ID, you must include the name of the database extension as well as a session number. If you specify a valid session ID, then the DBGetConnInfo function returns the name of the database extension in the ddevName parameter. The name of the database extension is contained in the database extension file in a resource of type 'STR ' with a resource ID of 128. For the Data Access Language database extension provided by Apple, for example, this string is “DAL”.host    Returns the host string used to initiate communication with the data server.user    Returns the user string used to initiate communication with the data server.network    Returns the name of the network through which the database extension is communicating with the data server. This parameter is an empty string if you are not communicating through a network.connStr    Returns the connection string used to initiate communication with the data server.start    Returns the time, in ticks (sixtieths of a second), at which this session was initiated.state    Returns one of the following values to provide information about the status of the session:            CONST        noErr                =    0;            {no error--ready for more }                                                { text}                    rcDBValue                = –801;            {output data available}                    rcDBError                = –802;            {execution ended in an }                                                { error}                    rcDBExec                = –805;            {busy--currently executing }                                                { query}asynchPB    A pointer to an asynchronous parameter block. If you do not want to call the function asynchronously, set this parameter to NIL.DESCRIPTIONYou can use the DBGetConnInfo function to get information about a particular session, or you can call the function repeatedly, incrementing the session number each time, to get information about all of the sessions associated with a particular database extension.The sessID parameter is the session ID that was returned by the DBInit function. The sessNum parameter is the session number of the session about which you want information. You can specify either the session ID or the session number when you call the DBGetConnInfo function. If you specify the sessID parameter, use 0 for the sessNum parameter. If you specify the sessNum parameter, then use 0 for the sessID parameter. If you specify the sessNum parameter, you must specify a value for the ddevName parameter as well. If you specify the session number and the database extension, then the DBGetConnInfo function returns the session ID in the returnedID parameter.SPECIAL CONSIDERATIONSThe DBGetConnInfo function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBGetConnInfo function areTrap macro    Selector    _DBGetConnInfo    $1704    RESULT CODESnoErr    0    No error    rcDBBadSessID    –806    Session ID is invalid or database extension name is invalid    rcDBBadSessNum    –807    Invalid session number    rcDBBadDDev    –808    Couldn’t find the specified database extension, or error occurred in opening database extension    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a description of the asynchronous parameter block, see page 12-55. For more information on the use of the DBGetConnInfo function, see “Getting Information About Sessions in Progress” on page 12-35. DBGetSessionNumThe DBGetSessionNum function returns a session number when you specify the session ID.FUNCTION DBGetSessionNum (sessID: LongInt; VAR sessNum: Integer;                                   asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    The session ID that was returned by the DBInit function.sessNum    Returns the session number of the session you specify with the sessID parameter. The session number is unique for a particular database extension, but the same session number might be in use for different database extensions at the same time.asyncPB    A pointer to an asynchronous parameter block. If you do not want to call the function asynchronously, set this parameter to NIL.DESCRIPTIONYou can use the DBGetSessionNum function to determine the session numbers for the sessions opened by your own application. You might want this information, for example, so you can distinguish your own sessions from those opened by other applications when you use the DBGetConnInfo function to get information about all open sessions.SPECIAL CONSIDERATIONSThe DBGetSessionNum function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBGetSessionNum function areTrap macro    Selector    _DBGetSessionNum    $0605    RESULT CODESnoErr    0    No error    rcDBBadSessID    –806    Session ID is invalid    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOA description of the asynchronous parameter block structure begins on page 12-55. The DBInit function description begins on page 12-68. A description of the DBGetConnInfo function begins on page 12-71. DBKillUse the DBKill function to cancel the execution of an asynchronous routine.FUNCTION DBKill (asyncPB: DBAsyncParmBlkPtr): OSErr;asyncPB    A pointer to an asynchronous parameter block.DESCRIPTIONThe DBKill function cancels the execution of the asynchronous call specified by the asyncPB parameter.SPECIAL CONSIDERATIONSThe DBKill function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBKill function areTrap macro    Selector    _DBKill    $020E    RESULT CODESnoErr    0    No error    rcDBError    –802    Error canceling routine    rcDBBadAsynchPB    –810    Invalid parameter block specified    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a description of the asynchronous parameter block, see page 12-55. Low-Level Interface: Sending and Executing QueriesThe functions in this section send queries or portions of queries to the data server, execute queries that have been sent, return information about queries that have been sent, and halt execution of queries that are executing. DBSendYou can use the DBSend function to send a query or a portion of a query to a data server. FUNCTION DBSend (sessID: LongInt; text: Ptr; len: Integer;                       asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    The session ID that was returned by the DBInit function.text    A pointer to the query or query fragment that you want to send to the data server. The query or query fragment must be a character string. len    The length of the character string. If the len parameter has a value of –1, then the character string is assumed to be NULL terminated (that is, the string ends with a NULL byte); otherwise, the len parameter specifies the number of bytes in the string.asyncPB    A pointer to an asynchronous parameter block. If you do not want to call the function asynchronously, set this parameter to NIL.DESCRIPTIONThe DBSend function sends a query or a portion of a query to the data server. The data server appends this portion of the query to any portion you sent previously. Because the Data Access Manager does not modify the string you send in any way, it does not insert any delimiter between fragments of queries that you send to the data server. If you want a blank or a semicolon to be included between query fragments, or if you want to use return characters to divide the query into lines of text, you must include them in the character string that you send with this function. The data server does not execute the query until you call the DBExec function.SPECIAL CONSIDERATIONSThe DBSend function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBSend function areTrap macro    Selector    _DBSend    $0706    RESULT CODESnoErr    0    No error    rcDBError    –802    Error trying to send text    rcDBBadSessID    –806    Session ID is invalid    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a description of the asynchronous parameter block, see page 12-55. See Listing 12-4 beginning on page 12-31 for an example of the use of the DBSend function in sending a query fragment. See page 12-78 for a description of the DBExec function.DBSendItemYou can use the DBSendItem function to send to the data server the data that you wish to include in a query. FUNCTION DBSendItem (sessID: LongInt; dataType: DBType;                             len: Integer; places: Integer;                             flags: Integer; buffer: Ptr;                             asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    The session ID that was returned by the DBInit function.dataType    The data type for the data item that you are sending to the data server.len    The length of the data item that you are sending to the data server. The database extension and data server ignore the len parameter if the data type has an implied length. places    The number of decimal places for the data item that you are sending to the data server. The database extension and data server ignore the places parameter for all values of the dataType parameter except typeDecimal and typeMoney.flags    Set the flags parameter to 0. There are no flags currently defined for the DBSendItem function. buffer    A pointer to the memory location of the data item that you want to send. When you use the DBSendItem function to send an item of data to a data server, the database extension and data server format the data according to the data type, length, and decimal places you specify, convert it to a character string, and append the data to the query. asyncPB    A pointer to an asynchronous parameter block. If you do not want to call the function asynchronously, set this parameter to NIL.DESCRIPTIONThe DBSendItem function sends a single data item to the data server. The database extension or the data server (depending on how the system is implemented) converts the data item to a character string and appends it to the query, just as the DBSend function appends a query program fragment to the query. The query is not executed until you call the DBExec function.SPECIAL CONSIDERATIONSThe DBSendItem function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBSendItem function areTrap macro    Selector    _DBSendItem    $0B07    RESULT CODESnoErr    0    No error    rcDBError    –802    Error trying to send item    rcDBBadSessID    –806    Session ID is invalid    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a discussion of data types, see “Getting Query Results” beginning on page 12-36. For a description of the asynchronous parameter block, see page 12-55. See Listing 12-4 beginning on page 12-31 for an example of the use of the DBSendItem function in sending a query fragment. See page 12-76 for a description of the DBSend function. The DBExec function is described next. DBExecThe DBExec function initiates execution of a query that you have sent to a data server.FUNCTION DBExec (sessID: LongInt;                       asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    The session ID that was returned by the DBInit function.asyncPB    A pointer to an asynchronous parameter block. If you do not want to call the function asynchronously, set this parameter to NIL.DESCRIPTIONThe DBExec function initiates execution of a query that you have sent to a data server. You can use the DBState function to determine the status of a query after you have initiated execution.SPECIAL CONSIDERATIONSThe DBExec function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBExec function areTrap macro    Selector    _DBExec    $0408    RESULT CODESnoErr    0    No error    rcDBError    –802    Error trying to begin execution    rcDBBadSessID    –806    Session ID is invalid    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a description of the asynchronous parameter block, see page 12-55. See Listing 12-5 beginning on page 12-33 for an example of the use of the DBExec function. Descriptions of the DBSend and DBSendItem functions begin on page 12-76 and page 12-77, respectively. The DBState function is described next. DBStateYou can use the DBState function to determine whether the data server has successfully executed a query and whether it has data available for you to retrieve. FUNCTION DBState (sessID: LongInt;                         asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    The session ID that was returned by the DBInit function.asyncPB    A pointer to an asynchronous parameter block. If you do not want to call the function asynchronously, set this parameter to NIL.DESCRIPTIONThe DBState function returns a result code that indicates the status of the data server.SPECIAL CONSIDERATIONSThe DBState function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBState function areTrap macro    Selector    _DBState    $0409    RESULT CODESnoErr    0    No error    rcDBValue    –801    Output data available    rcDBError    –802    Error executing function    rcDBExec    –805    Query currently executing     rcDBBadSessID    –806    Session ID is invalid    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a description of the asynchronous parameter block, see page 12-55. DBGetErrThe DBGetErr function retrieves error codes and error messages from a data server. You can use this function to obtain information when a low-level function returns the result code rcDBError. FUNCTION DBGetErr (sessID: LongInt; VAR err1: LongInt;                         VAR err2: LongInt; VAR item1: Str255;                         VAR item2: Str255; VAR errorMsg: Str255;                         asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    The session ID that was returned by the DBInit function.err1     Returns the primary error code. err2    Returns the secondary error code. item1    Returns a string that describes the object of the error message.item2    Returns a string that describes the object of the error message.errorMsg    Returns the error message.asyncPB    A pointer to an asynchronous parameter block. If you do not want to call the function asynchronously, set this parameter to NIL.DESCRIPTIONIf the DBState function returns the rcDBError result code, indicating that execution of a query ended in an error, the error information retuned by DBGetErr can help you debug the query. The meaning of each error code and error message returned by this function depends on the data server with which you are communicating; see the documentation for that data server for more information.SPECIAL CONSIDERATIONSThe DBGetErr function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBGetErr function areTrap macro    Selector    _DBGetErr    $0E0A    RESULT CODESnoErr    0    No error    rcDBError    –802    Error retrieving error information    rcDBBadSessID    –806    Session ID is invalid    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a description of the asynchronous parameter block, see page 12-55. DBBreakYou can use the DBBreak function to cancel a query—for example, if you determine that it is taking too long to complete execution.FUNCTION DBBreak (sessID: LongInt; abort: Boolean;                         asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    The session ID that was returned by the DBInit function.abort    A Boolean value that indicates how DBBreak should cancel the query. Specify TRUE (nonzero) to cause the data server to halt any query that is executing and terminate the current session. Specify FALSE (0) to cause the data server to halt any query that is executing and reinitialize itself.asyncPB    A pointer to an asynchronous parameter block. If you do not want to call the function asynchronously, set this parameter to NIL.DESCRIPTIONThe DBBreak function can halt execution of a query and reinitialize the data server, or it can unconditionally terminate a session with a data server.SPECIAL CONSIDERATIONSThe DBBreak function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBBreak function areTrap macro    Selector    _DBBreak    $050B    RESULT CODESnoErr    0    No error    rcDBError    –802    Error executing function    rcDBBadSessID    –806    Session ID is invalid    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a description of the asynchronous parameter block, see page 12-55. Low-Level Interface: Retrieving ResultsThe functions in this section allow you to retrieve a data item from the data server, to obtain information about the next data item, and to retrieve the same data item more than once. DBGetItemAfter you have executed a query and the DBState function returns the rcDBValue result code, indicating that data is available, you can use the DBGetItem function to retrieve the next data item. You can also use this function to obtain information about the next data item without retrieving the data. FUNCTION DBGetItem (sessID: LongInt; timeout: LongInt;                           VAR dataType: DBType; VAR len: Integer;                          VAR places: Integer; VAR flags: Integer;                          buffer: Ptr; asyncPB: DBAsyncParmBlkPtr)                          : OSErr;sessID    The session ID that was returned by the DBInit function.timeout    The maximum amount of time that the database extension should wait to receive results from the data server before canceling the function. Specify the timeout parameter in ticks (sixtieths of a second). To disable the timeout feature, set the timeout parameter to the kDBWaitForever constant. If the timeout period expires, the DBGetItem function returns the rcDBBreak result code. The DBGetItem function ignores the timeout parameter if you call the function asynchronously.     One use for the timeout parameter is to call the DBGetItem function periodically with a short value set for this parameter in order to return control to your application while a query is executing. Your application can then retrieve the next data item as soon as execution of the query is complete without having to call the DBState function to determine when data is available.dataType    The data type that you expect the next data item to be. If the item is not of the expected data type, the database extension returns the rcDBBadType result code. If you want to retrieve the next data item regardless of type, set the dataType parameter to the typeAnyType constant. To skip the next data item, set the dataType parameter to the typeDiscard constant. The data server sets the dataType parameter to the actual type of the data item when it retrieves the data item or returns information about the data item.len    The length of the data buffer pointed to by the buffer parameter. If you use the DBGetItem function to obtain information only (by setting the buffer parameter to NIL), then the data server ignores the len parameter. The data server sets the len parameter to the actual length of the data item when it retrieves the data item or returns information about the data item.places    Returns the number of decimal places in data items of types typeMoney and typeDecimal. For all other data types, the data server returns 0 for the places parameter.flags    If the least significant bit of the flags parameter is set to 1, the data item is in the last column of the row. If the third bit of this parameter is set to 1, the data item is NULL. You can use the constants kDBLastColFlag and kDBNullFlag to test for these flag bits.buffer    A pointer to the location where you want the retrieved data item to be stored. You must ensure that the location you specify contains enough space for the data item that will be returned. To determine the data type, length, and number of decimal places of the next data item without retrieving it, specify NIL for the buffer parameter. asyncPB    A pointer to an asynchronous parameter block. If you do not want to call the function asynchronously, set this parameter to NIL.DESCRIPTIONThe DBGetItem function retrieves the next data item from the data server. You can repeat the DBGetItem function as many times as is necessary to retrieve all of the data returned by the data source in response to a query.SPECIAL CONSIDERATIONSThe DBGetItem function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBGetItem function areTrap macro    Selector    _DBGetItem    $100C    RESULT CODESnoErr    0    No error    rcDBNull    –800    The data item was NULL    rcDBValue    –801    Data available was successfully retrieved    rcDBError    –802    Error executing function    rcDBBadType    –803    Next data item not of requested data type    rcDBBreak    –804    Function timed out    rcDBBadSessID    –806    Session ID is invalid    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a discussion of data types, see “Getting Query Results” beginning on page 12-36. To retrieve all of a query’s data items at once, use the high-level function DBGetQueryResults; a description of that function begins on page 12-65. For a description of the asynchronous parameter block, see page 12-55. See Listing 12-5 beginning on page 12-33 for an example that illustrates the use of the DBGetItem function. DBUnGetItemThe DBUnGetItem function reverses the effect of the last call to the DBGetItem function, in the sense that the next time you call the DBGetItem function it retrieves the same item a second time.FUNCTION DBUnGetItem (sessID: LongInt;                              asyncPB: DBAsyncParmBlkPtr): OSErr;sessID    The session ID that was returned by the DBInit function.asyncPB    A pointer to an asynchronous parameter block. If you do not want to call the function asynchronously, set this parameter to NIL.DESCRIPTIONThe DBUnGetItem function does not remove the just-retrieved data item from the input buffer. This function can reverse the effect of only one call to the DBGetItem function; you cannot use it to step back through several previously retrieved data items. SPECIAL CONSIDERATIONSThe DBUnGetItem function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBUnGetItem function areTrap macro    Selector    _DBUnGetItem    $040D    RESULT CODESnoErr    0    No error    rcDBError    –802    Error executing function    rcDBBadSessID    –806    Session ID is invalid    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a description of the asynchronous parameter block, see page 12-55. See page 12-83 for a description of the DBGetItem function.Installing and Removing Result HandlersThe functions in this section install, remove, and return pointers to result handlers. DBInstallResultHandlerThe DBInstallResultHandler function installs a result handler for the data type specified by the dataType parameter. The result handler is then used by the DBResultsToText function to convert data of the specified type into a character string.FUNCTION DBInstallResultHandler (dataType: DBType;                                             theHandler: ProcPtr;                                             isSysHandler: Boolean): OSErr;dataType    The type of result handler to install.theHandlerA pointer to a result handler.isSysHandlerA Boolean value that specifies whether the result handler is an application result handler—to be used only when the DBResultsToText function is called by the application that installed the result handler—or a system result handler—to be used by every application running on the system. If the isSysHandler parameter is TRUE, the result handler is a system result handler.DESCRIPTIONWhen you install an application result handler, it replaces any result handler with the same name previously installed by that application. Similarly, when you install a system result handler, it replaces any existing system result handler with the same name. Before you temporarily replace an existing result handler, use the DBGetResultHandler function to obtain a pointer to the present handler, and save the present result handler in your application’s private storage. Then you can reinstall the original result handler when you are finished using the temporary one.Because an application result handler is used in preference to a system result handler if both are available, you can temporarily replace a system result handler for purposes of your application by installing an application result handler for the same data type. You can then use the DBRemoveResultHandler function to remove the application result handler and return to using the system result handler whenever you wish.SPECIAL CONSIDERATIONSThe DBInstallResultHandler function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBInstallResultHandler function areTrap macro    Selector    _DBInstallResultHandler    $0514    RESULT CODESnoErr    0    No error    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOSee page 12-67 for a description of the DBResultsToText function. For information on application and system result handlers, see “Converting Query Results to Text” beginning on page 12-42; that section also lists the data types for which Apple provides system result handlers. Listing 12-6 on page 12-45 shows a sample result handler. The DBRemoveResultHandler function is described on page 12-89, and the DBGetResultHandler function is described next. DBGetResultHandlerThe DBGetResultHandler function returns a pointer to a result handler for a specified data type.FUNCTION DBGetResultHandler (dataType: DBType;                                       VAR theHandler: ProcPtr;                                       getSysHandler: Boolean): OSErr;dataType    The data type for which to install a result handler.theHandlerReturns a pointer to the result handler.getSysHandlerIf you set the getSysHandler parameter to FALSE (0), the function returns a pointer to the current application result handler for the specified data type, or it returns NIL if there is no application result handler for that data type. If you set the getSysHandler parameter to TRUE (nonzero), the function returns a pointer to the current system result handler for the specified data type, or it returns NIL if there is no system result handler for that data type.DESCRIPTIONYou can use the DBGetResultHandler function to obtain a pointer to a result handler so that you can use it to convert to text an individual data item retrieved by the DBGetItem function. The DBGetQueryResults function automatically converts to text all of the data pointed to by the results record.SPECIAL CONSIDERATIONSThe DBGetResultHandler function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBGetResultHandler function areTrap macro    Selector    _DBGetResultHandler    $0516    RESULT CODESnoErr    0    No error    rcDBNoHandler    –811    There is no handler for this data type installed for the current application    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOThe DBGetQueryResults function is described on page 12-65, and the DBGetItem function is described on page 12-83. See “Converting Query Results to Text” beginning on page 12-42 for a list of the data types for which Apple provides system result handlers. Listing 12-6 on page 12-45 shows a sample result handler. DBRemoveResultHandlerYou can use the DBRemoveResultHandler function to remove an application result handler.FUNCTION DBRemoveResultHandler (dataType: DBType): OSErr;dataType    The type of result handler to remove.DESCRIPTIONThe DBRemoveResultHandler function removes from memory the specified application result handler. This function cannot remove a system result handler. SPECIAL CONSIDERATIONSThe DBRemoveResultHandler function may move or purge memory. You should not call this routine from within an interrupt, such as in a completion routine or a VBL task.ASSEMBLY-LANGUAGE INFORMATIONThe trap macro and routine selector for the DBRemoveResultHandler function areTrap macro    Selector    _DBRemoveResultHandler    $0215    RESULT CODESnoErr    0    No error    rcDBNoHandler    –811    There is no handler for this data type installed for the current application    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    SEE ALSOFor a discussion of result handlers, see “Converting Query Results to Text” beginning on page 12-42. Application-Defined RoutinesYou can provide status functions, result handler functions, and query defintion functions for use with the Data Access Manager. For information on status functions, see “Writing a Status Routine for High-Level Functions” beginning on page 12-22. See “Processing Query Results” beginning on page 12-36 for information on result handlers. See “Writing a Query Definition Function” beginning on page 12-51 for information on query definition functions.ResourcesThis section describes the query resource, the query string resource, and the query definition function resource. You use the query resource to provide information that the Data Access Manager uses to create a query record in memory. You use the query string resource to define individual queries. You use the query definition function to modify a query and the query record before the query is sent to the data server.The Query ResourceEach query document should contain a single 'qrsc' resource. Figure 12-9 shows the format of the 'qrsc' resource.Figure 12-9    Structure of a compiled query ('qrsc') resourceA 'qrsc' resource contains these elements:n    The version number of the 'qrsc' format. For the Data Access Manager released with System 7, the version number is 0.n    The resource ID of the 'qdef' resource containing the query definition function that the Data Access Manager is to call when it opens this 'qrsc' resource. Use an ID of 0 if there is no query definition function for this resource—that is, if the Data Access Manager should send the query in this resource to the data server without modifications.n    The resource ID of an 'STR#' resource that contains five Pascal strings corresponding to some of the parameters used by the DBInit function. If the query definition function is going to prompt the user for the values of these parameters before entering them in the query record, they should be zero-length strings in the 'STR#' resource.n    An index value indicating which element in the array of 'wstr' IDs represents the current query. The current query is the one actually sent to the data server.n    The number of 'wstr' resources in the query document.n    An array of resource IDs of the 'wstr' resources in the query document. (The array elements are numbered starting with 1.) If the query document contains more than one 'wstr' resource, the query definition function can prompt the user to select the query to use and modify the current query field in the query record appropriately.n    The number of other resources in this query document.n    An array listing the resource types and IDs of all the resources in the query document other than the standard resources included in all query documents. The resources listed in this final array are those used by the query definition function. This list should include resources embedded in other resources, such as a 'PICT' resource that is included in a 'DITL' resource. The Query String ResourceA query document must contain one or more query string resources of type 'wstr'. These 'wstr' resources contain individual queries—that is, strings of commands and data that the DBSend function sends to the data server and that the DBExec function executes.A 'wstr' resource consists of a 2-byte length field followed by a character string. (The w in 'wstr' refers to the length word as opposed to the length byte used in an 'STR ' resource.) Each 'wstr' resource contains one query (or one query template, to be modified by the query definition function before it is sent to the data server). Figure 12-10 shows the structure of the 'wstr' resource.Figure 12-10    Structure of a compiled query string ('wstr') resourceThe 'qrsc' resource includes an array that lists the resource ID numbers of all of the 'wstr' resources in the query document and an index into the array that specifies which one of the 'wstr' resources should be sent to the data server.The Query Definition Function ResourceA query document may contain a query definition function, which can modify the query record and, if necessary, fill in the query template to create a complete query.If you want to include a query definition function, you must make it the first piece of code in a resource of type 'qdef' in the query document.Note that, because a query in memory consists only of a 2-byte length value followed by a character string, the query definition function has to know the exact contents and structure of a query in order to modify it. For a sample query definition function that uses a dialog box to prompt the user for a user name and password, see Listing 12-7 on page 12-52.Summary of the Data Access ManagerPascal SummaryConstantsCONST                gestaltDBAccessMgrAttr                                    = 'dbac';                {Gestalt selector for }                                                            { Data Access Manager}        {Gestalt selector response}        gestaltDBAccessMgrPresent                                    = 0;                {TRUE if Data Access Manager }                                                            { is present}        {DBStartQuery status messages}        kDBUpdateWind                                    = 0;                {update windows}        kDBAboutToInit                                    = 1;                {about to call DBInit}        kDBInitComplete                                     = 2;                {DBInit has completed}        kDBSendComplete                                     = 3;                {DBSend has completed}        kDBExecComplete                                     = 4;                {DBExec has completed}        kDBStartQueryComplete                                    = 5;                {DBStartQuery is about }                                                              { to complete}        {DBGetQueryResults status messages}        kDBGetItemComplete                                     = 6;                {DBGetItem has completed}        kDBGetQueryResultsComplete                                    = 7;                {DBGetQueryResults has }                                                            { completed data types}        {data type codes}        typeNone                                    = 'none';                {no more data expected}        typeDate                                    = 'date';                {date}        typeTime                                    = 'time';                {time}        typeTimeStamp                                    = 'tims';                {date and time}        typeDecimal                                    = 'deci';                {decimal number}        typeMoney                                    = 'mone';                {money value}        typeVChar                                    = 'vcha';                {variable character}        typeVBin                                    = 'vbin';                {variable binary}        typeLChar                                    = 'lcha';                {long character}        typeLBin                                    = 'lbin';                {long binary}        typeDiscard                                    = 'disc';                {discard next data item}        typeBoolean                                     = 'bool';                {Boolean}        typeChar                                     = 'TEXT';                {character}        typeSMInt                                     = 'shor';                {short integer}        typeInteger                                     = 'long';                {integer}        typeSMFloat                                     = 'sing';                {short floating point}        typeFloat                                     = 'doub';                {floating point}        {dummy data types for DBResultsToText}        typeUnknown                                    = 'unkn';                {result handler for unknown }                                                            { data type}        typeColBreak                                    = 'colb';                {result handler for column }                                                            { break}        typeRowBreak                                    = 'rowb';                {result handler for end of }                                                            { line}        {any data type in DBGetItem}        typeAnyType                                    = 0;                {any data type}        {infinite timeout value for DBGetItem}        kDBWaitForever                                    = -1;                {infinite timeout value for }                                                            { DBGetItem}        {flags for DBGetItem}        kDBLastColFlag                                     = $0001;                {data item is last column }                                                            { of the row}        kDBNullFlag                                     = $0004;                {data item is NULL}Data TypesTYPE DBType =                             OSType;                                {data type}    DBAsyncParamBlockRec =                                                         {asynchronous parameter block}    RECORD        completionProc:                        ProcPtr;                            {pointer to completion routine}        result:                        OSErr;                            {result of call}        userRef:                        LongInt;                            {reserved for use by }                                                            { application}        ddevRef:                        LongInt;                            {reserved for use by database }                                                            { extension}        reserved:                        LongInt;                            {reserved for use by }                                                            { Data Access Mgr}    END;    DBAsyncParmBlkPtr = ^DBAsyncParamBlockRec;    ResListElem =                                                         {resource list in QueryRecord}    RECORD        theType:                        ResType;                            {resource type}        id:                        Integer;                            {resource ID}    END;    ResListArray                     = ARRAY[0..255] OF ResListElem;    ResListPtr                     = ^ResListArray;    ResListHandle                     = ^ResListPtr;    QueryRecord =     RECORD        version:                    Integer;                        {query record format version}        id:                    Integer;                        {resource ID of 'qrsc'}        queryProc:                    Handle;                        {handle to query def proc}        ddevName:                    Str63;                        {name of database extension}        host:                    Str255;                        {name of host computer}        user:                    Str255;                        {name of user}        password:                    Str255;                        {user's password}        connStr:                    Str255;                        {connection string}        currQuery:                    Integer;                        {index of current query}        numQueries:                    Integer;                        {number of queries in list}        queryList:                    QueryListHandle;                        {handle to array of handles to text}        numRes:                    Integer;                        {number of resources in list}        resList:                    ResListHandle;                        {handle to array of resource list }                                                     { elements}        dataHandle:                    Handle;                        {handle to memory for query def proc}        refCon:                    LongInt;                        {reserved for use by application}    END;    QueryPtr                 = ^QueryRecord;                                {pointer to query record}    QueryHandle     = ^QueryPtr;                                            {handle to query record}    {query list in QueryRecord}    QueryArray                         = ARRAY[0..255] OF Handle;    QueryListPtr                         = ^QueryArray;    QueryListHandle                         = ^QueryListPtr;    {column types array in ResultsRecord}    ColTypesArray                     = ARRAY[0..255] OF DBType;    ColTypesPtr                     = ^ColTypesArray;    ColTypesHandle             = ^ColTypesPtr;    DBColInfoRecord =                                                 {column info in ResultsRecord}    RECORD        len:                Integer;                            {length of data item}        places:                Integer;                            {places for decimal and money }                                                    { data items}        flags:                Integer        ;                    {flags for data item}    END;    ColInfoArray                     = ARRAY[0..255] OF DBColInfoRecord;    ColInfoPtr                     = ^ColInfoArray;    ColInfoHandle                     = ^ColInfoPtr;    {structure of results returned by DBGetResults}    ResultsRecord =     RECORD        numRows:                    Integer;                        {number of rows retrieved}        numCols:                    Integer;                        {number of columns per row}        colTypes:                    ColTypesHandle;                        {type of data in each column}        colData:                    Handle;                        {array of data items}        colInfo:                    ColInfoHandle;                        {DBColInfoRecord array--info about }                                                    { each data item}    END;Data Access Manager RoutinesInitializing the Data Access ManagerFUNCTION InitDBPack:    OSErr;High-Level Interface: Handling Query DocumentsFUNCTION DBGetNewQuery    (queryID: Integer; VAR query: QueryHandle): OSErr;FUNCTION DBDisposeQuery    (query: QueryHandle): OSErr;FUNCTION DBStartQuery    (VAR sessID: LongInt; query: QueryHandle; statusProc: ProcPtr; asyncPB: DBAsyncParmBlkPtr): OSErr;High-Level Interface: Handling Query ResultsFUNCTION DBGetQueryResults    (sessID: LongInt; VAR results: ResultsRecord; timeout: LongInt; statusProc: ProcPtr; asyncPB: DBAsyncParmBlkPtr): OSErr;FUNCTION DBResultsToText    (results: ResultsRecord; VAR theText: Handle): OSErr;Low-Level Interface: Controlling the SessionFUNCTION DBInit    (VAR sessID: LongInt; ddevName: Str63; host: Str255; user: Str255; password: Str255; connStr: Str255; asyncPB: DBAsyncParmBlkPtr): OSErr;FUNCTION DBEnd    (sessID: LongInt; asyncPB: DBAsyncParmBlkPtr): OSErr;FUNCTION DBGetConnInfo    (sessID: LongInt; sessNum: Integer; VAR returnedID: LongInt; VAR version: LongInt; VAR ddevName: Str63; VAR host: Str255; VAR user: Str255; VAR network: Str255; VAR connStr: Str255; VAR start: LongInt; VAR state: OSErr; asyncPB: DBAsyncParmBlkPtr): OSErr;FUNCTION DBGetSessionNum    (sessID: LongInt; VAR sessNum: Integer; asyncPB: DBAsyncParmBlkPtr): OSErr;FUNCTION DBKill    (asyncPB: DBAsyncParmBlkPtr): OSErr;Low-Level Interface: Sending and Executing QueriesFUNCTION DBSend    (sessID: LongInt; text: Ptr; len: Integer; asyncPB: DBAsyncParmBlkPtr): OSErr;FUNCTION DBSendItem    (sessID: LongInt; dataType: DBType; len: Integer; places: Integer; flags: Integer; buffer: Ptr; asyncPB: DBAsyncParmBlkPtr): OSErr;FUNCTION DBExec    (sessID: LongInt; asyncPB: DBAsyncParmBlkPtr): OSErr;FUNCTION DBState    (sessID: LongInt; asyncPB: DBAsyncParmBlkPtr): OSErr;FUNCTION DBGetErr    (sessID: LongInt; VAR err1: LongInt; VAR err2: LongInt; VAR item1: Str255; VAR item2: Str255; VAR errorMsg: Str255; asyncPB: DBAsyncParmBlkPtr): OSErr;FUNCTION DBBreak    (sessID: LongInt; abort: Boolean; asyncPB: DBAsyncParmBlkPtr): OSErr;Low-Level Interface: Retrieving ResultsFUNCTION DBGetItem    (sessID: LongInt; timeout: LongInt; VAR dataType: DBType;VAR len: Integer; VAR places: Integer; VAR flags: Integer; buffer: Ptr;asyncPB: DBAsyncParmBlkPtr): OSErr;FUNCTION DBUnGetItem    (sessID: LongInt;asyncPB: DBAsyncParmBlkPtr): OSErr;Installing and Removing Result HandlersFUNCTION DBInstallResultHandler(dataType: DBType; theHandler: ProcPtr;isSysHandler: Boolean): OSErr;FUNCTION DBGetResultHandler    (dataType: DBType; VAR theHandler: ProcPtr;getSysHandler: Boolean): OSErr;FUNCTION DBRemoveResultHandler(dataType: DBType): OSErr;Application-Defined RoutinesFUNCTION MyStatusFunc    (message: Integer; result: OSErr; dataLen: Integer; dataPlaces: Integer; dataFlags: Integer; dataType: DBType; dataPtr: Ptr): Boolean;FUNCTION MyResultHandler    (dataType: DBType; theLen: Integer; thePlaces: Integer; theFlags: Integer; theData: Ptr; theText: Handle): OSErr;FUNCTION MyQDef    (VAR sessID: LongInt; query: QueryHandle): OSErr;C SummaryConstantsenum {    #define gestaltDBAccessMgrAttr                                            'dbac'            /*Gestalt selector for */                                                            /* Data Access Manager*/    /*Gestalt selector response*/    gestaltDBAccessMgrPresent                                        = 0                /*TRUE if Data Access Manager */                                                            /* is present*/};enum {                                                            /*DBStartQuery status messages*/    kDBUpdateWind                                        = 0,                /*update windows*/    kDBAboutToInit                                        = 1,                /*about to call DBInit*/    kDBInitComplete                                         = 2,                /*DBInit has completed*/    kDBSendComplete                                         = 3,                /*DBSend has completed*/    kDBExecComplete                                         = 4,                /*DBExec has completed*/    kDBStartQueryComplete                                        = 5                /*DBStartQuery is about */                                                            /* to complete*/};enum {    /*DBGetQueryResults status messages*/    kDBGetItemComplete                                         = 6,            /*DBGetItem has completed*/    kDBGetQueryResultsComplete                                        = 7,            /*DBGetQueryResults has */                                                        /* completed data types*/    /*data type codes*/    #define typeNone                                         'none'            /*no more data expected*/    #define typeDate                                         'date'            /*date*/    #define typeTime                                         'time'            /*time*/    #define typeTimeStamp                                         'tims'            /*date and time*/    #define typeDecimal                                         'deci'            /*decimal number*/    #define typeMoney                                         'mone'            /*money value*/    #define typeVChar                                         'vcha'            /*variable character*/    #define typeVBin                                         'vbin'            /*variable binary*/    #define typeLChar                                         'lcha'            /*long character*/    #define typeLBin                                         'lbin'            /*long binary*/    #define typeDiscard                                         'disc'            /*discard next data item*/    /*dummy data types for DBResultsToText*/    #define typeUnknown                                         'unkn'            /*result handler for unknown */                                                        /* data type*/    #define typeColBreak                                         'colb'            /*result handler for */                                                        /* column break*/    #define typeRowBreak                                         'rowb'            /*result handler for */                                                        /* end of line*/    /*any data type in DBGetItem*/    #define typeAnyType                                     (DBType)0                /*any data type*/    /*infinite timeout value for DBGetItem*/    kDBWaitForever                                        = -1    ,        /*infinite timeout value for */                                                        /* DBGetItem*/    /*flags for DBGetItem*/    kDBLastColFlag                                         = 0x0001,            /*data item is last column */                                                        /* of the row*/    kDBNullFlag                                         = 0x0004            /*data item is NULL*/};enum {    /*more data type codes*/    typeBoolean                                     = 'bool',                /*Boolean*/    typeChar                                     = 'TEXT',                /*character*/    typeSMInt                                     = 'shor',                /*short integer*/    typeInteger                                     = 'long',                /*integer*/    typeSMFloat                                     = 'sing',                /*short floating point*/    typeFloat                                     = 'doub'                /*floating point*/};Data Typestypedef OSType DBType;                                                /*data type*/struct DBAsyncParamBlockRec {                                                /*asynchronous parameter block*/    ProcPtr             completionProc;                                /*pointer to completion routine*/    OSErr             result;                                /*result of call*/    long             userRef;                                /*reserved for use by application*/    long             ddevRef;                                /*reserved for use by database */                                                /* extension*/    long             reserved;                                /*reserved for use by */                                                /* Data Access Manager*/};typedef struct DBAsyncParamBlockRec DBAsyncParamBlockRec;typedef DBAsyncParamBlockRec *DBAsyncParmBlkPtr;struct ResListElem {                                                /*resource list in QueryRecord*/    ResType             theType;                                /*resource type*/    short             id;                                /*resource ID*/};typedef struct ResListElem ResListElem;typedef ResListElem *ResLisPtr, **ResListHandle;typedef Handle **QueryListHandle;struct QueryRecord {                                                /*query record*/    short                         version;                    /*query record format version*/    short                         id;                    /*resource ID of 'qrsc'*/    Handle                         queryProc;                    /*handle to query def proc*/    Str63                         ddevName;                    /*name of database extension*/    Str255                         host;                    /*name of host computer*/    Str255                         user;                    /*name of user*/    Str255                         password;                    /*user's password*/    Str255                         connStr;                    /*connection string*/    short                         currQuery;                    /*index of current query*/    short                         numQueries;                    /*number of queries in list*/    QueryListHandle                         queryList;                    /*handle to array of handles to text*/    short                         numRes;                    /*number of resources in list*/    ResListHandle                         resList;                    /*handle to array of resource list */                                                /* elements*/    Handle                         dataHandle;                    /*handle to memory for query def proc*/    long                         refCon;                    /*reserved for use by application*/};typedef struct QueryRecord QueryRecord;typedef QueryRecord *QueryPtr, **QueryHandle;/*column types array in ResultsRecord*/typedef Handle ColTypesHandle;struct DBColInfoRecord {                                                /*column info in ResultsRecord*/    short len;                                            /*length of data item*/    short places;                                            /*places for decimal and money */                                                /* data items*/    short flags;                                            /*flags for data item*/};typedef struct DBColInfoRecord DBColInfoRecord;typedef Handle ColInfoHandle;struct ResultsRecord {                                                /*results returned by DBGetResults*/    short                     numRows;                        /*number of rows retrieved*/    short                     numCols;                        /*number of columns per row*/    ColTypesHandle     colTypes;                                        /*type of data in each column*/    Handle                     colData;                        /*array of data items*/    ColInfoHandle                     colInfo;                        /*DBColInfoRecord array--info about */                                                /* each data item*/};typedef struct ResultsRecord ResultsRecord;Data Access Manager RoutinesInitializing the Data Access Managerpascal OSErr InitDBPack                                     (void);High-Level Interface: Handling Query Documentspascal OSErr DBGetNewQuery    (short queryID, QueryHandle *query);pascal OSErr DBDisposeQuery    (QueryHandle query);pascal OSErr DBStartQuery    (long *sessID, QueryHandle query, ProcPtr statusProc, DBAsyncParmBlkPtr asyncPB);High-Level Interface: Handling Query Resultspascal OSErr DBGetQueryResults(long sessID, ResultsRecord *results, long timeout, ProcPtr statusProc, DBAsyncParmBlkPtr asyncPB);pascal OSErr DBResultsToText(ResultsRecord *results, Handle *theText);Low-Level Interface: Controlling the Sessionpascal OSErr DBInit    (long *sessID, ConstStr63Param ddevName, ConstStr255Param host, ConstStr255Param user, ConstStr255Param passwd, ConstStr255Param connStr, DBAsyncParmBlkPtr asyncPB);pascal OSErr DBEnd    (long sessID, DBAsyncParmBlkPtr asyncPB);pascal OSErr DBGetConnInfo    (long sessID, short sessNum, long *returnedID, long *version, Str63 ddevName, Str255 host, Str255 user, Str255 network, Str255 connStr, long *start, OSErr *state, DBAsyncParmBlkPtr asyncPB);pascal OSErr DBGetSessionNum(long sessID, short *sessNum, DBAsyncParmBlkPtr asyncPB);pascal OSErr DBKill    (DBAsyncParmBlkPtr asyncPB);Low-Level Interface: Sending and Executing Queriespascal OSErr DBSend    (long sessID, char *text, short len, DBAsyncParmBlkPtr asyncPB);pascal OSErr DBSendItem    (long sessID, DBType dataType, short len, short places, short flags, void *buffer, DBAsyncParmBlkPtr asyncPB);pascal OSErr DBExec    (long sessID, DBAsyncParmBlkPtr asyncPB);pascal OSErr DBState    (long sessID, DBAsyncParmBlkPtr asyncPB);pascal OSErr DBGetErr    (long sessID, long *err1, long *err2, Str255 item1, Str255 item2, Str255 errorMsg, DBAsyncParmBlkPtr asyncPB);pascal OSErr DBBreak    (long sessID, Boolean abort, DBAsyncParmBlkPtr asyncPB);Low-Level Interface: Retrieving Resultspascal OSErr DBGetItem    (long sessID, long timeout, DBType *dataType, short *len, short *places, short *flags, void *buffer, DBAsyncParmBlkPtr asyncPB);pascal OSErr DBUnGetItem    (long sessID, DBAsyncParmBlkPtr asyncPB);Installing and Removing Result Handlerspascal OSErr DBInstallResultHandler(DBType dataType, ProcPtr theHandler, Boolean isSysHandler);pascal OSErr DBGetResultHandler(DBType dataType, ProcPtr *theHandler, Boolean getSysHandler);pascal OSErr DBRemoveResultHandler(DBType dataType);Application-Defined Routinespascal Boolean MyStatusFunc    (short message, OSErr result, short dataLen, short dataPlaces, short dataFlags, DBType dataType, Ptr dataPtr);pascal OSErr  MyResultHandler(DBType dataType, short theLen, short thePlaces, short theFlags, Ptr theData, Handle theText);pascal OSErr MyQDef    (long *sessID, QueryHandle query);Assembly-Language SummaryTrap MacrosTrap Macros Requiring Routine Selectors_Pack13Selector    Routine    $0100    InitDBPack    $020E    DBKill    $0210    DBDisposeQuery    $0215    DBRemoveResultHandler    $030F    DBGetNewQuery    $0403    DBEnd    $0408    DBExec    $0409    DBState    $040D    DBUnGetItem    $0413    DBResultsToText    $050B    DBBreak    $0514    DBInstallResultHandler    $0516    DBGetResultHandler    $0605    DBGetSessionNum    $0706    DBSend    $0811    DBStartQuery    $0A12    DBGetQueryResults    $0B07    DBSendItem    $0E02    DBInit    $0E0A    DBGetErr    $100C    DBGetItem    $1704    DBGetConnInfo    Result CodesnoErr    0    No error    userCanceledErr    –128    User canceled the query     rcDBNull    –800    The data item was NULL    rcDBValue    –801    Data available or successfully retrieved    rcDBError    –802    Error executing function    rcDBBadType    –803    Next data item not of requested data type    rcDBBreak    –804    Function timed out    rcDBExec    –805    Query currently executing     rcDBBadSessID    –806    Session ID is invalid    rcDBBadSessNum    –807    Invalid session number    rcDBBadDDev    –808    Couldn’t find the specified database extension, or error occurred in opening database extension    rcDBAsyncNotSupp    –809    The database extension does not support asynchronous calls    rcDBBadAsynchPB    –810    Invalid parameter block specified    rcDBNoHandler    –811    There is no handler for this data type installed for the current application    rcDBWrongVersion    –812    Wrong version number    rcDBPackNotInited    –813    The InitDBPack function has not yet been called    Glossaryabstract superclassA superclass listed in the Apple Event Registry: Standard Suites, such as cObject or cOpenableObject, that is used only in definitions of object classes and not for real Apple event objects. See also object class.active functionA function called by a scripting component periodically during script compilation and execution. You must provide an alternative active function for the use of scripting components if you want your application to get time during script compilation and execution for tasks such as spinning the cursor or checking for system-level errors.additional parameterA keyword-specified descriptor record that a server application uses in addition to the data specified in the direct parameter. For example, an Apple event for arithmetic operations may include additional parameters that specify operands in an equation. Additional parameters may be required, or they may be optional.address descriptor recordA descriptor record of data type AEAddressDesc that contains the address of the target or source of an Apple event.AEIMPSee Apple Event Interprocess Messaging Protocol.AE recordA descriptor record of data type AERecord that usually contains a list of parameters for an Apple event. See also Apple event parameter. Apple eventA high-level event that adheres to the Apple Event Interprocess Messaging Protocol. An Apple event consists of attributes (including the event class and event ID, which identify the event and its task) and, usually, parameters (which contain data used by the target application for the event). See also Apple event attribute, Apple event parameter.Apple event arrayAn array in a descriptor list. The data for an Apple event array is specified by an array data record, which is defined by the data type AEArrayData.Apple event attributeA keyword-specified descriptor record that identifies the event class, event ID, target application, or some other characteristic of an Apple event. Taken together, the attributes of an Apple event identify the event and denote the task to be performed on the data specified in the Apple event’s parameters. Unlike Apple event parameters (which contain data used only by the target application of the Apple event), Apple event attributes contain information that can be used by both the Apple Event Manager and the target application. See also Apple event parameter.Apple event dispatch tableA table in either the application heap or the system heap that the Apple Event Manager uses to map Apple events to the appropriate Apple event handlers.Apple event handlerAn application-defined function that extracts pertinent data from an Apple event, performs the action requested by the Apple event, and returns a result. Apple Event Interprocess Messaging Protocol (AEIMP)A standard defined by Apple Computer, Inc., for communication and data sharing among applications. High-level events that adhere to this protocol are called Apple events. See also Apple event.Apple Event ManagerThe collection of routines that allows client applications to send Apple events to server applications for the purpose of requesting services or information.Apple event objectA distinct item in a target application or any of its documents that can be specified by an object specifier record in an Apple event sent by a source application. Apple event objects can be anything that an application can locate on the basis of such a description, including items that a user can differentiate and manipulate while using an application, such as words, paragraphs, shapes, windows, or style formats. See also object specifier record.Apple event object classSee object class.Apple event parameterA keyword-specified descriptor record containing data that the target application for an Apple event uses. Unlike Apple event attributes (which contain information that can be used by both the Apple Event Manager and the target application), Apple event parameters contain data used only by the target application of the Apple event. See also Apple event attribute, direct parameter, optional parameter, required parameter.Apple event recordA descriptor record of data type AppleEvent that contains a list of keyword-specified descriptor records. These descriptor records describe—at least—the attributes necessary for an Apple event; they may also describe parameters for the Apple event. Apple Event Manager functions are used to add parameters to an Apple event record.Apple event user terminology resourcesTwo resources with identical formats used by server applications to specify the Apple events and corresponding user terminology that the applications support. The 'aeut' resource, which is provided by scripting components, contains terminology information for all the standard suites of Apple events defined in the Apple Event Registry: Standard Suites. An 'aete' resource must be provided by every scriptable application; it describes which of the standard suites listed in the 'aeut' resource the application supports and provides additional terminology information for extensions to the standard suites and custom Apple events supported by the application. See also scripting component.AppleScript componentThe scripting component that implements the AppleScript scripting language. See also scripting component.AppleScript scripting languageThe standard user scripting language defined by Apple Computer, Inc. The AppleScript scripting language is implemented by the AppleScript scripting component. See also dialect.application result handlerA result handler that is associated with a particular application. Compare with system result handler.asynchronous parameter blockIn the Data Access Manager, the parameter block that allows a routine to return control to your application before the routine has completed execution.authenticationThe process of establishing the identity of a user. The authentication mechanism of the PPC Toolbox identifies each user through an assigned name and password.boundary objectsThe elements, specified in a range descriptor record, that identify the beginning and end of the range. See also range descriptor record.client applicationAn application that uses Apple events to request a service (for example, printing a list of files, checking the spelling of a list of words, or performing a numeric calculation) from another application (called a server application). These applications can reside on the same local computer or on remote computers connected to a network.coercion handlerA routine that coerces data from one descriptor type to another.coercion handler dispatch tableA table in either the application heap or the system heap that the Apple Event Manager uses to map desired coercions to the appropriate coercion handler. See also coercion handler.comparison descriptor recordA coerced AE record of type typeCompDescriptor that specifies an Apple event object and either another Apple event object or data for the Apple Event Manager to compare to the first object.compiled scriptCompiled code that a client application can decompile into source data or execute using the standard scripting component routines.compiled script fileA script file with the file type 'scpt' that contains script data as a resource of type 'scpt'. Before executing the script in a compiled script file, a user must first open the script from the Finder or from an application such as Script Editor.component-specific storage descriptor recordA descriptor record returned by OSAStore. The descriptor type for a component-specific storage descriptor record is the scripting component subtype value for the scripting component that created the script data.containerAn Apple event object that contains another Apple event object. A container is specified in an object specifier record by a keyword-specified descriptor record with the keyword keyAEContainer. The keyword-specified descriptor record is usually another object specifier record. It can also be a null descriptor record, or it can be used much like a variable when the Apple Event Manager determines a range or performs a series of tests. The objects a container contains can be either elements or properties. See also Apple event object, element, object specifier record, property.container hierarchyThe chain of containers that determine the location of one or more Apple event objects. See also container.core Apple eventAn Apple event defined as part of the Core suite of Apple events in the Apple Event Registry: Standard Suites. create functionA function called by a scripting component whenever it creates an Apple event during script execution. You must provide an alternative create function if you want to gain control over the creation and addressing of Apple events. If you don’t provide an alternative create function, scripting components call the standard Apple Event Manager function AECreateAppleEvent with default parameters.custom Apple eventAn Apple event you define for use by your own applications. Instead of creating custom Apple events, you should try to use the standard Apple events and extend their definitions as necessary for your application. If you think you need to define custom Apple events, you should check with the Apple Event Registrar to find out whether Apple events that already exist or are under development can be adapted to the needs of your application.database extensionThe interface between the Data Access Manager and a data server.data serverAn application that acts as an interface between a database extension on a Macintosh computer and a data source, which can be on the Macintosh computer or on a remote host computer. A data server can be a database server program that can provide an interface to a variety of different databases, or it can be the data source itself, such as a Macintosh application.default containerThe outermost container in an application’s container hierarchy; usually the application itself. See also container hierarchy.default scripting componentThe scripting component used by the generic scripting component when an application passes kOSANullScript rather than a valid script ID to OSACompile or OSAStartRecording.descriptor listA descriptor record of data type AEDescList whose data handle refers to a list of descriptor records.descriptor recordA data structure of type AEDesc that consists of a handle to data and a descriptor type that identifies the type of the data referred to by the handle. Descriptor records are the fundamental data structures from which Apple events are constructed.descriptor typeAn identifier for the type of data referred to by the handle in a descriptor record.dialectA version of a scripting language that resembles a specific human language or programming language; for example, the AppleScript scripting language provides dialects that resemble English, Japanese, and other languages. See also AppleScript scripting language.direct parameterThe parameter in an Apple event that contains the data or object specifier record to be used by the server application. For example, a list of documents to be opened is specified in the direct parameter of the Open Documents event. See also Apple event parameter.editionThe data written to an edition container by a publisher. A publisher writes data to an edition whenever a user saves a document that contains a publisher, and subscribers in other documents may read the data from the edition whenever it is updated. See also publisher, subscriber.edition containerA file that holds edition data, represented on the desktop by an edition icon. An edition container obtains its data from a publisher within a document. See also edition, publisher.Edition ManagerThe collection of routines that allows applications to automate copy and paste operations between applications, so that data can be shared dynamically.elementAn Apple event object contained by another Apple event object specified as the element’s container. An Apple event object can contain many elements of the same element class, whereas an Apple event object can have only one of each of its properties. See also Apple event object, container, element classes, property.element classesIn the Apple Event Registry: Standard Suites, a list of the object classes for the elements that an Apple event object of a given object class can contain. See also Apple event object, object class.error callback functionAn object callback function that gives the Apple Event Manager an address. The Apple Event Manager writes to this address the descriptor record it is currently working with if an error occurs during the resolution of an object specifier record. See also object callback function.event classAn attribute that identifies a group of related Apple events. The event class appears in the message field of the Apple event’s event record. The event class and the event ID identify the action an Apple event performs. See also Apple event attribute, event ID.event IDAn attribute that identifies a particular Apple event within a group of related Apple events. The event ID appears in the where field of the Apple event’s event record. The event ID and the event class identify the action an Apple event performs. See also Apple event attribute, event class.Event ManagerThe collection of routines that an application can use to receive information about actions performed by the user, to receive notice of changes in the processing status of the application, and to communicate with other applications.extensionAn object class that duplicates all the characteristics of an object class of the same name and adds some of its own. Like a word in a dictionary, a single object class ID can have several related definitions. factoringUsing Apple events to separate the code that controls an application’s user interface from the code that responds to the user’s manipulation of the interface. In a fully factored application, any significant user actions generate Apple events that a scripting component can record as statements in a compiled script. See also recordable application.functional-area Apple eventA standard Apple event supported by applications with related features; for example, an Apple event related to text manipulation for word-processing applications, or an Apple event related to graphics manipulation for drawing applications. Functional-area Apple events are defined by Apple Computer, Inc., in consultation with interested developers and are published in the Apple Event Registry: Standard Suites.generic script IDSpecial script IDs used by the generic scripting component to keep track of script IDs provided by multiple scripting components. The generic scripting component translates generic scripting IDs into the corresponding component-specific script IDs and vice versa when necessary.generic scripting componentA special scripting component that establishes connections dynamically with the appropriate scripting component for each script that a client application attempts to manipulate or execute. The generic scripting component also provides routines that you can use to determine which scripting component created a particular script, get an instance of a specific scripting component, and perform other useful tasks when you are using multiple scripting components. See also scripting component.generic storage descriptor recordA descriptor record of type kOSAGenericStorage that can be used by the generic scripting component or any other scripting component to store script data. The script data in a generic storage descriptor record is followed by a trailer that contains the subtype for the scripting component that created the script data.implied lengthThe definition of a specific length for a data type. An example of this is the Data Access Manager’s typeInteger data type, which has a defined length of 4 bytes.insertion location descriptor recordA record of type typeInsertionLoc that consists of two keyword-specified descriptor records. The first is an object specifier record, and the data for the second is a constant that specifies the insertion location in relation to the Apple event object described by the object specifier record.interapplication communication (IAC) architectureA standard and extensible mechanism for communication among Macintosh applications, including the Edition Manager, the Open Scripting Architecture, the Apple Event Manager, the Event Manager, and the PPC Toolbox.key dataThe data in an object specifier record that distinguishes one or more Apple event objects from other Apple event objects of the same object class in the same container. Key data is specified by a keyword-specified descriptor record with the keyword keyAEKeyData. The Apple Event Manager interprets key data according to the key form specified in the same object specifier record.key formThe form taken by the key data in an object specifier record. The key form is specified by a keyword-specified descriptor record with the keyword keyAEKeyForm. The keyword-specified descriptor record contains a constant that determines how the Apple Event Manager and a target application use the key data to locate specific Apple event objects. For example, the key form constant formName indicates that the key data consists of a name, which should be compared to the names of Apple event objects in the container specified by the object specifier record.keywordA four-character code that uniquely identifies a descriptor record inside another descriptor record. In Apple Event Manager functions, constants are typically used to represent the four-character codes.keyword-specified descriptor recordA record of data type AEKeyDesc that consists of a keyword and a descriptor record. Keyword-specified descriptor records are used to describe the attributes and parameters of an Apple event.location nameAn identifier for the network location of the computer on which a port resides. The PPC Toolbox provides the location name. It contains an object string, a type string, and a zone. An application can specify an alias for its location name by modifying its type string. See also port.logical descriptor recordA coerced AE record of type typeLogicalDescriptor that specifies a logical expression—that is, an expression that the Apple Event Manager evaluates to either TRUE or FALSE. The logical expression is constructed from a logical operator (one of the Boolean operators AND, OR, or NOT) and a list of logical terms to which the operator is applied. Each logical term in the list can be either another logical descriptor record or a comparison descriptor record. mark-adjusting functionA marking callback function that unmarks objects previously marked by a call to an application’s marking function. mark countThe number of times the Apple Event Manager has called the marking function for the current mark token. Applications that support marking callback functions should associate the mark count with each Apple event object they mark. marking callback functionsObject callback functions that allow your application to use its own marking scheme rather than tokens when identifying large groups of Apple event objects. See also mark-adjusting function, mark token function, object callback function, and object-marking function.mark token A token returned by a mark token function. A mark token identifies the way an application marks Apple event objects during the current sessions while resolving a single test. A mark token does not identify a specific Apple event object; rather, it allows an application that supports marking callback functions to associate a group of objects with a marked set.mark token functionA marking callback function that returns a mark token.message blockA byte stream that an open application uses to send data to and receive data from another open application (which can be located on the same computer or across a network). The PPC Toolbox delivers message blocks to an application in the same sequence in which they were sent.Name-Binding Protocol (NBP)An AppleTalk protocol that maintains a table containing the internet address and name of each entity in the node that is visible to other entities on the internet (that is, each entity that has registered a name with NBP).null descriptor recordA descriptor record whose descriptor type is typeNull and whose data handle is NIL.object accessor dispatch tableA table in either the application heap or the system heap that the Apple Event Manager uses to map descriptions of objects in an object specifier record to object accessor functions that can locate those objects.object accessor functionAn application- defined function that locates an Apple event object of a specified object class in a container identified by a token of a specified descriptor type.object callback functionAn application- defined function used by the Apple Event Manager to resolve object specifier records. See also error callback function,  marking callback functions, object-comparison function, object-counting function, and token disposal function.object classA category for Apple event objects that share specific characteristics listed in an object class definition in the Apple Event Registry: Standard Suites. Among these characteristics are properties, element classes, and Apple events that can specify objects of that class. An object class is specified in an object specifier record by a keyword-specified descriptor record with the keyword keyAEDesiredClass whose data handle refers to either a constant or an object class ID.object class IDA four-character code, which can also be represented by a constant, that identifies an object class for an Apple event object. The object class ID for a primitive object class is the same as the four-character value of its descriptor type.object class inheritance hierarchyThe hierarchy of subclasses and superclasses that determines which properties, elements, and Apple events object classes inherit from other object classes.object-comparison functionAn object callback function that compares an element to either another element or to a descriptor record and returns either TRUE or FALSE. object-counting functionAn object callback function that counts the number of elements of a specified class in a specified container, so that the Apple Event Manager can determine how many elements it must examine to find the element or elements that pass a test. object-marking functionAn object callback function called repeatedly by the Apple Event Manager to mark specific Apple event objects. See also marking callback functions.object specifier recordA description of one or more Apple event objects based on the Apple Event Manager and the classification system defined in the Apple Event Registry: Standard Suites. An object specifier record consists of a descriptor record of descriptor type typeObjectSpecifier that comprises four keyword-specified descriptor records: the object class ID, the container for the Apple event object (which is usually another Apple event object, specified by another object specifier record), the key form, and the key data. Open Application eventAn Apple event that asks an application to perform the tasks—such as displaying untitled windows—associated with opening itself; one of the four required Apple events.Open Documents eventAn Apple event that asks an application to open one or more documents specified in a list; one of the four required Apple events.Open Scripting Architecture (OSA)A mechanism based on the Apple Event Manager and the Apple Event Registry: Standard Suites that allows users to control multiple applications by means of scripts. The scripts can be written in any scripting language that supports the OSA.optional parameterA supplemental parameter in an Apple event used to specify data that the server application can use in addition to the data specified in the direct parameter. Source applications list the keywords for parameters that they consider optional in the attribute identified by the keyOptionalKeywordAttr keyword. Target applications use this attribute to identify any parameters that they are required to understand. If a parameter’s keyword is not listed in this attribute, the target application must understand that parameter to handle the event successfully. See also Apple event attribute, Apple event parameter.port(1) A portal through which an open application can exchange information with another open application using the PPC Toolbox. A port is designated by a port name and a location name. An application can open as many ports as it requires so long as each port name is unique within a particular computer. (2) A connection between the CPU and main memory or a device (such as a terminal) for transferring data. (3) A socket on the back panel of a computer where you plug in a cable for connection to a network or a peripheral device.port nameA unique identifier for a particular application within a computer. The port name contains a name string, a type string, and a script code. An application can specify any number of port names for a single port so long as each name is unique. See also port.primitive object classAn object class defined in the Apple Event Registry: Standard Suites for Apple event objects that contain a single value; for example, the cBoolean, cLongInteger, and cAlias object classes are all primitive object classes. An Apple event object that belongs to a primitive object class has no properties and contains only one element—the value of the data.Print Documents eventAn Apple event that requests that an application print a list of documents; one of the four required Apple events.Program-to-Program Communications (PPC) ToolboxThe collection of routines that allows applications to exchange blocks of data with other applications by reading and writing low-level message blocks. propertyAn Apple event object that defines some characteristic of another Apple event object, such as its font or point size, that can be uniquely identified by a constant. The definition of each object class in the Apple Event Registry: Standard Suites lists the constants and class IDs for properties of Apple event objects belonging to that object class. For example, the constants pName and pBounds identify the name and boundary properties of Apple event objects that belong to the object class cWindow. The pName property of a specific window is defined by an Apple event object of object class cProperty, such as the word “MyWindow,” which defines the name of the window. An Apple event object can contain only one of each of its properties, whereas it can contain many elements of the same element class. See also Apple event object, container, element classes.property IDA four-character code, which can also be represented by a constant, that identifies a property.publishTo make data available to other documents and applications through a publisher. When a user creates or edits the data in the publisher and then saves it, the current version of the data is stored in an edition. See also edition, publisher, subscriber.publisherA portion of a document that makes its data available to other documents or applications. A publisher stores its data in an edition whenever a user creates or edits the data in the publisher and then saves it. See also edition, section, subscriber.queryA string of commands and data sent to a database or other data source. A query does not necessarily extract data from a data source; it might only send data or commands to a database or other application.query definition functionA function contained in a query document that prompts the user for information and modifies the query before the Data Access Manager sends it to the data server.query documentA file of file type 'qery' containing commands and data in a format appropriate for a database or other data source. An application uses high-level Data Access Manager routines to open a query document.query recordA data structure in memory containing information provided by a 'qrsc' resource. The query record includes a pointer to a query.Quit Application eventAn Apple event that requests that an application perform the tasks—such as releasing memory, asking the user to save documents, and so on—associated with quitting; one of the four required Apple events. The Finder sends this event to an application immediately after sending it a Print Documents event or if the user chooses Restart or Shut Down from the Finder’s Special menu.range descriptor recordA coerced AE record of type typeRangeDescriptor that identifies two Apple event objects marking the beginning and end of a range of elements. See also boundary objects.recordable applicationAn application that uses Apple events to report user actions to the Apple Event Manager for recording purposes. When a user turns on recording (for example, by pressing the Record button in the Script Editor application), a scripting component translates the Apple events generated by the user’s subsequent actions into statements in a scripting language and records them in a compiled script. See also scriptable application.recordable eventAny Apple event that any recordable application sends to itself while recording is turned on for the local computer, with the exception of events that are sent with the kAEDontRecord flag set in the sendMode parameter of the AESend function.recording processAny process (for example, a script editor) that can turn Apple event recording on and off and receive and record recordable Apple events.required Apple eventOne of the four Apple events in the Required suite that the Finder sends to applications: Open Documents, Open Application, Print Documents, or Quit Application. required parameterAn Apple event parameter that must be included in an Apple event. For example, a list of documents to open is a required parameter for the Open Documents event. Direct parameters are often required, and other additional parameters may be required. Optional parameters are never required.resolveTo locate the Apple event object described by an object specifier record.result handlerA routine that the Data Access Manager calls to convert a data item to a character string.results recordA structure that the Data Access Manager uses to store the data retrieved by the DBGetQueryResults function. This data is returned by a data source in response to a query.resume dispatch functionAn application-defined function called by OSADoEvent or OSAExecuteEvent to dispatch an Apple event directly to an application’s default handler for that event.scriptAny collection of data that, when executed by the appropriate program, causes a corresponding action or series of actions. When a scripting component that supports the OSA executes a script, it sends Apple events as necessary to trigger actions in server applications.scriptable applicationAn application that can respond as a server application to Apple events sent to it by scripting components. To be scriptable, an application must respond to the appropriate standard Apple events, and it must provide an 'aete' resource that describes the nature of that support. See also Apple event user terminology resources.script applicationA script file with the file type 'APPL' that contains the script data as a resource of type 'scpt'. If a script application has the creator signature 'aplt', a user can double-click its icon to trigger the script. If a script application has the creator signature 'dplt', a user can drag the icon for another file or a folder over the script application’s icon to trigger its script. By default, when a user triggers the script in a script application, a splash screen appears that allows the user either to quit or to run the script. Users can also save a script application in a form that bypasses the splash screen, running the script immediately after the user double-clicks its icon.script application componentA component registered with the Component Manager at system startup. When a user opens a script application, the script application component loads the script and passes the resulting script ID to the appropriate scripting component for execution.script commentA description, in a script editor window, of what the script displayed in that window does.script contextA form of script that maintains context information for the execution of other scripts. A script context can also be used to handle Apple events. Like a compiled script, a script context can be decompiled as source data. In the AppleScript scripting language, a script context is called a script object.script dataA compiled script, script value, script context, or any other representation of a script in memory used internally by a scripting component. See also compiled script, script context, script value.script editorAn application that allows users to record, edit, save, and execute scripts; for example, the Script Editor application provided with AppleScript.script fileA file in which a script is stored. A script file can be a compiled script file, a script application file, or a script text file.script IDA data structure of type OSAID—that is, a long integer—used by scripting components to keep track of script data.scriptingWriting and executing scripts to control the behavior of multiple applications.scripting componentA component that responds appropriately to calls made to the standard scripting component routines. Most scripting components implement scripting languages; for example, the AppleScript component implements the AppleScript scripting language.script objectAppleScript term for script context. See also script context.script text fileUncompiled statements in a scripting language saved by a script editor as a text file. A user must open a script text file in a script editor and successfully compile it before it will execute. See also script editor.script valueAn integer, a string, a Boolean value, a constant, a 'PICT', or any other fixed data that a scripting component returns or uses in the course of executing a script.sectionA document or portion of a document that shares its contents with other documents. The Edition Manager supports two types of sections: publishers and subscribers. A publisher makes its data available to share and a subscriber subscribes to available data. See also publisher, subscriber.send functionA function called by a scripting component whenever it sends an Apple event during script execution. You can provide an alternative send function if you want your application to perform some action instead of or in addition to sending Apple events. If you don’t provide an alternative send function, scripting components call the standard Apple Event Manager function AESend with default parameters.server applicationAn application that responds to Apple events requesting a service or information sent by client applications or scripting components (for example, by printing a list of files, checking the spelling of a list of words, or performing a numeric calculation). Apple event servers and clients can reside on the same local computer or on remote computers connected to a network.session(1) A logical (as opposed to physical) connection between two entities (such as a Macintosh program and a database server) that facilitates the transmission of information between the two entities. (2) In the PPC Toolbox, an exchange of information between one open application with a port and another open application with a port. Sessions can occur between applications that are located on the same computer or across a network. An application has the option to accept or reject a session request. Authentication of the requesting user may be required before a session can commence. See also authentication, message block, port.session IDA number that uniquely identifies a session.source applicationThe application that sends a particular Apple event to another application or to itself. Typically, an Apple event client sends an Apple event requesting a service from an Apple event server; in this case, the client is the source application for the Apple event. The Apple event server may return a different Apple event as a reply; in this case, the server is the source for the reply Apple event.source dataStatements in a scripting language that constitute an uncompiled script.special handler dispatch tableA table in either the application heap or the system heap that the Apple Event Manager uses to keep track of various specialized handlers.status routineAn application-defined routine that can update windows, check the results of the low-level calls made by the Data Access Manager’s DBStartQuery and DBGetQueryResults functions, and cancel execution of these functions when appropriate to do so.subclassAn object class that inherits properties, element classes, and Apple events from another object class—its superclass. A subclass can also include properties, element classes, or Apple events that are not inherited from its superclass. Every object class, with the exception of cObject, is a subclass of another object class. See also object class, superclass.subscribeTo obtain data that a publisher makes available in an edition. A user subscribes to a publisher by choosing Subscribe To from the Edit menu and selecting the desired edition. See also edition, publish.subscriberA portion of a document that automatically obtains current data from other documents and applications. A subscriber reads data from an edition. See also edition, section.suiteIn the Apple Event Registry: Standard Suites, a group of definitions for Apple events, object classes, primitive object classes, descriptor types, and constants that are all used for a set of related activities. For example, the Text suite includes definitions of Apple events, object classes, and so on that are used for text processing.superclassThe object class from which a subclass inherits properties, elements, and Apple events. See also object class, subclass.system Apple event dispatch tableSee Apple event dispatch table.system coercion dispatch tableSee coercion handler dispatch table.system object accessor dispatch tableSee object accessor dispatch table.system result handlerA result handler that is available to all applications that use the system. Compare with application result handler.target addressAn application signature, a process serial number, a session ID, a target ID record, or some other application-defined type that identifies the target of an Apple event.target applicationThe application addressed to receive an Apple event. Typically, an Apple event client sends an Apple event requesting a service from a server application; in this case, the server is the target application of the Apple event. The server application may return a different Apple event as a reply; in this case, the client is the target of the reply Apple event.tokenA descriptor record returned by an object accessor function that identifies a requested Apple event object in a specified container.token disposal functionAn object callback function that disposes of a token.transactionA sequence of Apple events sent back and forth between the client and server applications, beginning with the client’s initial request for a service. All Apple events that are part of one transaction must have the same transaction ID.whose descriptor record A coerced AE record of descriptor type typeWhoseDescriptor. The Apple Event Manager creates whose descriptor records when it resolves object specifier records that specify formTest.whose range descriptor recordA coerced AE record of type typeWhoseRange. Under certain conditions, the Apple Event Manager coerces a range descriptor record to a whose range descriptor record when it resolves object specifier records that specify formTest.IndexSymbols'****' (wildcard) descriptor type4-10, 4-58, 4-63, 6-26'----' keyword3-15Aactive functionsroutines for manipulating10-45 to 10-46supplying alternative10-23additional parameters for Apple events3-9address descriptor recordsadding to an Apple event5-11 to 5-13defined3-14for direct dispatching5-13addresses in Apple events5-10 to 5-13'addr' keyword3-15AEAddressDesc data type3-14, 5-11 to 5-13AEArrayData data type4-60, 5-57AEArrayDataPointer data type4-61AEArrayType data type4-60AECallObjectAccessor function6-82 to 6-83AECoerceDesc function4-95 to 4-96AECoercePtr function4-94 to 4-95AECountItems function4-31, 4-74AECreateAppleEvent function5-4, 5-25 to 5-26AECreateAppleEventProcPtr data type10-24AECreateDesc function5-6, 5-11, 5-26 to 5-27AECreateList function5-28 to 5-29AECreateProcPtr function10-95 to 10-96AEDeleteItem function4-92AEDeleteKeyDesc function4-93AEDeleteParam function4-93AEDesc data type3-12, 4-56AEDescList data type3-17AEDisposeDesc function4-39 to 4-40, 4-94AEDisposeToken function6-41, 6-46, 6-54, 6-87 to 6-88AEDuplicateDesc function5-27 to 5-28AEEventClass data type4-59, 4-62AEEventID data type4-59, 4-62AEEventSource data type4-29AEGetArray function4-77 to 4-78AEGetAttributeDesc function4-73AEGetAttributePtr function4-28 to 4-31, 4-71 to 4-72AEGetCoercionHandler function4-98AEGetEventHandler function4-64 to 4-65AEGetInteractionAllowed function4-82AEGetKeyDesc function4-80 to 4-81AEGetKeyPtr function4-79 to 4-80AEGetNthDesc function4-32, 4-76 to 4-77AEGetNthPtr function4-32 to 4-33, 4-75 to 4-76AEGetObjectAccessor function6-81 to 6-82AEGetParamDesc function4-27 to 4-28, 4-31, 4-69 to 4-70AEGetParamPtr function4-27, 4-68 to 4-69AEGetSpecialHandler function4-101 to 4-102AEGetTheCurrentEvent function4-89AEIMP (Apple Event Interprocess Messaging Protocol)1-3AEInstallCoercionHandler function4-96 to 4-97AEInstallEventHandler function4-8 to 4-9, 4-62 to 4-64AEInstallObjectAccessor function6-22 to 6-27, 6-78 to 6-79AEInstallSpecialHandler function4-100 to 4-101AEInteractAllowed data type4-48, 4-82AEInteractWithUser function4-50, 4-83 to 4-84AEKeyDesc data type3-16AEKeyword data type3-15 to 3-16AEManagerInfo function4-104AEObjectInit function6-77AEProcessAppleEvent function4-66 to 4-68AEPutArray function5-31AEPutAttributeDesc function5-36 to 5-37AEPutAttributePtr function5-35 to 5-36AEPutDesc function5-30AEPutKeyDesc function5-33AEPutKeyPtr function5-32AEPutParamDesc function5-6, 5-34AEPutParamPtr function5-5, 5-33 to 5-34AEPutPtr function5-29 to 5-30AERecord data type3-17 to 3-18AE recordsadding data to5-32adding keyword-specified descriptor records to5-32 to 5-33creating5-28 to 5-29defined3-17 to 3-18deleting keyword-specified descriptor records from4-93getting data out of4-25 to 4-33, 4-78 to 4-80AE records (continued)getting descriptor records out of4-80 to 4-81getting sizes and descriptor types of keyword-specified descriptor records in4-90 to 4-91and other Apple Event Manager data structures3-18AERemoveCoercionHandler function4-99AERemoveEventHandler function4-65 to 4-66AERemoveObjectAccessor function6-84 to 6-85AERemoveSpecialHandler function4-102 to 4-103AEResetTimer function4-84 to 4-85AEResolve function6-4 to 6-8, 6-28 to 6-47, 6-85 to 6-87AEResumeTheCurrentEvent function4-86 to 4-88AESend function5-13 to 5-20, 5-37 to 5-41AESendPriority data type5-38AESendProcPtr data type10-25, 10-96AESetInteractionAllowed function4-81 to 4-82AESetObjectCallbacks function6-46, 6-79 to 6-80AESetTheCurrentEvent function4-88AESizeOfAttribute function4-91 to 4-92AESizeOfKeyDesc function4-90 to 4-91AESizeOfNthItem function4-90AESizeOfParam function4-91AESuspendTheCurrentEvent function4-85 to 4-86'aete' resourcesand AppleScript7-17 to 7-20creating8-13 to 8-23defined7-15 to 7-16dynamic loading of7-20recordable applications and1-18 to 1-19role of1-16 to 1-19, 7-17 to 7-20scriptable applications and1-16 to 1-17structure of8-8 to 8-13, 8-26 to 8-44supporting new suites8-23supporting standard suites with extensions8-16 to 8-23supporting standard suites without extensions8-14 to 8-16supporting subsets of suites8-23'aeut' resourcesadditional parameters array8-34 to 8-36and AppleScript7-17 to 7-20comparison operators array8-42 to 8-43defined7-15 to 7-16elements array8-40 to 8-41enumerations array8-43 to 8-44events array8-29 to 8-33header data8-27object classes array8-36 to 8-37properties array8-38 to 8-40resource type declaration8-9 to 8-13role of7-17 to 7-20structure of8-8 to 8-13, 8-26 to 8-44suites array8-27 to 8-29'aevt' descriptor type4-57'aevt' event class3-8alert boxesfor multiple publishers in a document2-58for new publishers2-19for PPC session termination11-7alias records, for publishers and subscribers2-16, 2-20'alis' descriptor type4-58'alis' format type2-25'alis' resource type2-19'aplt' creator signature7-7'appa' descriptor type4-58Apple event attributesadding to Apple events5-35 to 5-37defined3-7event classes3-8, 3-15event IDs3-8, 3-15event sources3-15getting data out of4-28 to 4-31, 4-71 to 4-72getting descriptor records out of4-73getting descriptor types of4-91 to 4-92getting sizes of4-91 to 4-92interaction level3-15, 4-45keywords for3-15missed keyword3-15, 4-30, 4-34 to 4-35optional keyword4-34, 5-7 to 5-10original source3-15return ID3-15setting with the AECreateAppleEvent function5-3 to 5-4target address3-15, 5-10 to 5-13timeout3-15, 5-21transaction ID3-15Apple event data structuresarrays4-60 to 4-61disposing of4-39 to 4-40summarized4-56 to 4-61AppleEvent data type3-18 to 3-19Apple event dispatch tablesdefined3-22getting entries from4-64 to 4-65installing entries in4-7 to 4-11, 4-62 to 4-64removing entries from4-65 to 4-66system4-7Apple event handlersadding to dispatch tables4-7 to 4-9, 4-62 to 4-64called from the AEProcessAppleEvent function4-66 to 4-67defined3-5getting from dispatch tables4-64 to 4-65introduced1-12removing from dispatch tables4-65 to 4-66tasks performed by3-23 to 3-27writing4-33 to 4-35Apple Event Interprocess Messaging Protocol (AEIMP)1-3Apple Event Manager3-3 to 6-116, 9-3 to 9-37application-defined functions for resolving object specifier records6-94 to 6-103getting information about4-103 to 4-104Object Support Library and6-3routines in4-61 to 4-104, 5-25 to 5-41, 6-77 to 6-94testing for availability4-4use of Notification Manager4-51user interaction with server application4-45 to 4-55, 4-81 to 4-84Apple event object classes. See object classes, Apple eventApple event objectsApple Event Registry: Standard Suites and1-11classification of3-39 to 3-46container hierarchy for3-45 to 3-46defined3-6described in Apple event parameters3-10, 3-12elements of3-42 to 3-46finding3-46 to 3-47hierarchy within an application3-33object accessor functions that find6-29 to 6-37object classes and1-11object specifier records and3-32 to 3-34properties of3-42 to 3-46tokens for6-4 to 6-7, 6-39 to 6-41, 6-47Apple event parametersadding5-5 to 5-7, 5-33 to 5-34additional3-9AppleScript and8-3 to 8-7checking for missing required4-34 to 4-35defined3-8deleting4-93direct3-9, 3-15error number4-36 to 4-37error string4-37 to 4-39getting data out of4-26 to 4-28, 4-68 to 4-71getting descriptor records out of4-27 to 4-28, 4-69 to 4-70getting descriptor types of4-91getting sizes of4-91optional3-9, 3-15, 5-7 to 5-10required3-9Apple event recordsdefined3-18disposing of4-39 to 4-40getting data out of4-25 to 4-33, 4-79 to 4-80getting descriptor records out of4-80 to 4-81and other Apple Event Manager data structures3-18Apple Event Registry: Standard Suites1-10 to 1-12Apple events. See also Apple event attributes; Apple event parametersaccepting3-20 to 3-22, 4-5 to 4-7addresses for5-10 to 5-13AppleScript and8-3 to 8-7attributes and parameters for3-7 to 3-12client applications using3-4 to 3-5Create Publisher4-22 to 4-25creating5-3 to 5-13data structures in3-12 to 3-19defined3-3determining current4-89direct dispatching5-13dispatching4-9 to 4-11, 4-66 to 4-68from Edition Manager2-13 to 2-14Get AETE8-23 to 8-26Get Data. See Get Data eventhandling1-12, 4-4 to 4-44and high-level events4-5 to 4-7introduced1-9Move. See Move eventOpen Application. See Open Application eventOpen Documents. See Open Documents eventPrint Documents. See Print Documents eventprocessing3-20 to 3-27, 4-67 to 4-68, 4-84 to 4-89Quit Application. See Quit Application eventReceive Recordable Event9-36Recorded Text10-27recording9-3 to 9-37Recording Off9-4Recording On9-4reply. See reply Apple eventsreplying to4-36 to 4-39, 5-24requesting more time to respond to4-84 to 4-85requesting services through3-28 to 3-32required1-10, 4-11 to 4-20Reset Timer4-85responding to1-9 to 1-13, 3-20 to 3-27, 4-5 to 4-7resuming handling of4-86 to 4-88Section Cancel2-13Section Read2-13Section Scroll2-13, 4-21Section Write2-13, 4-21sending1-9 to 1-13, 5-13 to 5-20sending to the current process5-13server applications using3-5Set Data. See Set Data eventstandard suites of1-10Start Recording9-36Stop Recording9-37suspending handling of4-85 to 4-86Apple event terminology extension resources. See 'aete' resourcesApple event user terminology resources. See 'aeut' resourcesAppleScript componentdefined7-4error numbers for OSAScriptError10-40routines for10-80 to 10-84AppleScript scripting languageApple events and8-3 to 8-7defined7-4dialects, defined7-17dialects, routines for manipulating10-67 to 10-71scriptable applications and8-3 to 8-7supporting1-13 to 1-22'APPL' file type7-7application-defined routinesMyActiveProc10-23, 10-95MyAdjustMarks6-53 to 6-54, 6-103MyAECreateProc10-24 to 10-25MyAESendProc10-25 to 10-26, 10-96MyCoerceDesc4-107MyCoercePtr4-106MyCompareObjects6-97 to 6-99MyCompletionRoutine11-78MyCountObjects6-96 to 6-97MyDisposeToken6-99MyEventHandler4-105 to 4-106MyExpDlgHook2-98MyExpModalFilter2-98MyGetErrorDesc6-100MyGetMarkToken6-53 to 6-54, 6-101 to 6-102MyIdleFunction5-42MyIO2-104MyMark6-102MyObjectAccessor6-95 to 6-96MyOpener2-102MyPortFilter11-78 to 11-79MyQDef12-51MyReplyFilter5-42 to 5-43MyResultHandler12-43MyResumeDispatch10-97MyStatusFunc12-22arrays, data types for4-60 to 4-61ASGetSourceStyleNames function10-84ASGetSourceStyles function10-82 to 10-83ASInit function10-80 to 10-82ASSetSourceStyles function10-83AssociateSection function2-20, 2-50, 2-79'****' (wildcard) descriptor type4-10, 4-58, 4-63, 6-26asynchronous parameter block record12-55 to 12-56authenticating sessions11-7, 11-10, 11-30B'bool' descriptor type4-57borders for publishers and subscribers2-9 to 2-10, 2-50 to 2-57in bitmapped graphics2-57in object-oriented graphics2-56 to 2-57in spreadsheets2-55 to 2-56in word processors2-54 to 2-55boundary objectsspecified in range descriptor records6-20specified in whose range descriptor records6-44CCallEditionOpenerProc function2-64, 2-103 to 2-104CallFormatIOProc function2-68, 2-104ccntTokenRecord data type6-21client applications, for Apple eventsdefined3-4 to 3-5introduced1-9and scripting components7-10setting user interaction preferences4-46 to 4-47CloseEdition function2-28, 2-88 to 2-89'CODE' resources, in script application files10-14coercion handlers for descriptor types4-41 to 4-44, 4-96 to 4-99comparison descriptor recordscomparison operators for6-51creating6-67 to 6-69, 6-89 to 6-90defined6-16'comp' descriptor type4-57compiled script files7-7compiled scriptsdefined7-23modifying and recompiling10-17 to 10-19compiling, scripting component routines for10-47 to 10-51completion routinesin PPC Toolbox11-16 to 11-17, 11-46 to 11-78for PPCAccept function11-38 to 11-39for PPCInform function11-36 to 11-37for PPCRead function11-41for PPCReject function11-39for PPCWrite function11-42complex object specifier records, creating6-64 to 6-75component description records, scripting component flags for10-5component instances, and scripting component routines10-4Component Manager, and scripting components10-3 to 10-7component-specific storage descriptor records10-12container hierarchydefined3-45described in object specifier records6-10for formTest6-17 to 6-19specifying6-61 to 6-63containersdefault6-10described in object specifier records3-35, 6-10specifying6-61 to 6-63specifying for a range of objects6-20Control Panels folder11-6'core' event class3-8Core suite of Apple events1-11, 3-41cProperty as object class ID3-42, 6-13, 6-27CreateCompDescriptor function6-68 to 6-69, 6-89 to 6-90CreateEditionContainerFile function2-32 to 2-34, 2-79 to 2-80Create Element event handler9-11create functionsroutines for manipulating10-55 to 10-57supplying alternative10-24CreateLogicalDescriptor function6-69 to 6-70, 6-91 to 6-92CreateObjSpecifier function6-55 to 6-75, 6-93 to 6-94CreateOffsetDescriptor function6-72, 6-88 to 6-89Create Publisher command (Edit menu)2-10Create Publisher event4-22 to 4-25CreateRangeDescriptor function6-73, 6-92 to 6-93DDAL (Data Access Language)12-4Data Access Language (DAL)12-4Data Access Manager12-3 to 12-104. See also sessions, data accessasynchronous calls12-12asynchronous parameter block record12-55 to 12-56canceling a function call12-75connection with a database, illustrated12-6data structures in12-54 to 12-59data types12-36 to 12-43disk-space limit12-13high-level interfacecompared to low-level12-11examples of12-7, 12-18 to 12-21retrieving data12-9routines12-61 to 12-68sending a query12-8 to 12-9status routines12-22 to 12-28using12-14 to 12-28high-level routines12-7 to 12-9flowchart12-8sequence of use12-14 to 12-17uses12-7initializing12-60 to 12-61local database and12-4low-level interface12-9 to 12-11compared to high-level12-11examples of12-9 to 12-11retrieving data12-11sending a query12-11using12-28 to 12-35low-level routines12-68 to 12-86flowchart12-29sequence of use12-28 to 12-35uses12-9queriesconverting results to text12-42 to 12-45, 12-67 to 12-68defined12-7executing12-78 to 12-79halting execution12-81 to 12-82processing results12-36 to 12-46retrieving results12-42sending12-30 to 12-31, 12-76 to 12-77starting12-63 to 12-65query definition function resources12-92query definition functions12-51 to 12-54query documentscontents12-48 to 12-51dialog boxes12-46 to 12-47query records12-56 to 12-57creating12-61defined12-46disposing of12-62 to 12-63query resources12-90 to 12-91query string resources12-91resources in12-90 to 12-92result handlers12-42 to 12-45, 12-86 to 12-89application12-43function declaration12-43installing12-84 to 12-85provided by Apple Computer12-42 to 12-43system12-43results records12-40 to 12-42routines in12-59 to 12-89status routines12-22 to 12-28sample12-26 to 12-28and status messages12-22 to 12-25suggested uses12-3testing for availability12-3user interface guidelines12-13for providing feedback12-13for query documents12-46 to 12-47database access. See Data Access Managerdatabase command strings. See queriesdatabase extensionsasynchronous execution and12-12defined12-4database queries. See queriesdatabases. See Data Access Managerdata serversdefined12-5status12-79DBAsyncParamBlockRec data type12-55DBBreak function12-81 to 12-82DBColInfoRecord data type12-42, 12-59DBDisposeQuery function12-62 to 12-63DBEnd function12-70 to 12-71DBExec function12-31, 12-78 to 12-79DBGetConnInfo function12-71 to 12-73DBGetErr function12-80 to 12-81DBGetItem function12-83 to 12-85DBGetNewQuery function12-61 to 12-62DBGetQueryResults function12-22 to 12-28, 12-65 to 12-67DBGetResultHandler function12-87 to 12-88DBGetSessionNum function12-74 to 12-75DBInit function12-68 to 12-70DBInstallResultHandler function12-86 to 12-87DBKill function12-75DBRemoveResultHandler function12-89DBResultsToText function12-67 to 12-68DBSend function12-76 to 12-77DBSendItem function12-77 to 12-78DBStartQuery function12-22 to 12-28, 12-63 to 12-65DBState function12-79 to 12-80DBUnGetItem function12-85 to 12-86ddev. See database extensionsdefault container6-5, 6-10default scripting componentdefined10-3getting and setting10-86 to 10-87DeleteEditionContainerFile function2-49, 2-81DeleteUserIdentity function11-44 to 11-45, 11-76 to 11-77descriptor listsadding array data to5-31adding descriptor records to5-30adding items to5-29 to 5-30counting descriptor records in4-74creating5-28 to 5-29defined3-17deleting descriptor records from4-92disposing of4-39 to 4-40getting data out of4-31 to 4-33, 4-75 to 4-76getting descriptor records out of4-76 to 4-77getting descriptor types of descriptor records in4-90getting sizes of descriptor records in4-90and other Apple Event Manager data structures3-18descriptor records. See also keyword-specified descriptor recordsadding as attributes5-36 to 5-37adding as parameters5-34adding to descriptor lists5-30coercing data in4-95 to 4-96counting in descriptor lists4-74creating5-26defined3-12 to 3-14deleting from descriptor lists4-92disposing of4-39 to 4-40, 6-58duplicating5-27 to 5-28getting data out of, in descriptor list4-75 to 4-76getting descriptor types of, in descriptor lists4-90getting from attributes4-73getting from descriptor lists4-76getting from keyword-specified descriptor records4-80getting from parameters4-26 to 4-28, 4-69 to 4-70getting sizes of, in descriptor lists4-90and other Apple Event Manager data structures3-12, 3-18descriptor typesin AE records4-90 to 4-91in Apple events4-89 to 4-92coercing4-41 to 4-44, 4-95 to 4-96defined3-13 to 3-14in descriptor lists4-90used by Apple Event Manager4-57 to 4-58DescType data type3-13dialects, of AppleScript scripting languagedefined7-17routines for manipulating10-67 to 10-71dialog boxescustomizing, for publishers and subscribers2-60 to 2-62to enable guest access11-9for incorrect passwords11-31for invalid user names11-31for program linking11-22 to 11-23, 11-32for publisher creation2-5, 2-29, 2-31for publisher options2-43for query documents12-46 to 12-47for subscriber creation2-6, 2-37for subscriber options2-44, 2-45for user identification11-30for users and groups11-8dialog hook functions, expandable2-97, 2-98direct dispatching, of Apple events5-13direct parameters for Apple events3-9, 3-15disks, free space limit for data access12-13dispatch tablesfor Apple event handlers4-7 to 4-9, 4-61 to 4-66for coercion handlers4-41 to 4-42dispatch tables (continued)for object accessor functions6-21 to 6-27for special handlers4-99 to 4-103'doub' descriptor type4-57'dplt' creator signature7-7, 10-14Eedition containers. See also editionsalias record reference to2-16, 2-22closing2-28creating2-32 to 2-34defined2-4deleting2-49opener functions2-63 to 2-67, 2-102 to 2-104opener verbs2-64 to 2-66opening2-26, 2-27, 2-68to read data2-41to write data2-35 to 2-36preview of2-37reading from2-27 to 2-28relocating2-60writing to2-27 to 2-28EditionContainerSpec data type2-39EditionHasFormat function2-41, 2-84 to 2-85Edition Manager2-3 to 2-122. See also editions; publishers; subscribersApple events sent by3-8, 4-20 to 4-21installing entries in Apple event dispatch table4-9introduced1-6 to 1-9routines in2-73 to 2-105and Translation Manager2-28, 2-41, 2-85, 2-86edition opener functions2-63, 2-102 to 2-104EditionOpenerParamBlock data type2-64, 2-103editions. See also edition containersdefined2-4formats for2-24 to 2-26preview of2-6Edit menuCreate Publisher command2-10Edition Manager commands in2-10Publisher/Subscriber Options command2-10, 2-43 to 2-44Show/Hide Borders command2-10Stop All Editions command2-10Subscribe To command2-10elements of Apple event objects3-42 to 3-46'enum' descriptor type4-58'erng' descriptor type10-39'errn' keyword3-15error callback function6-100error numbersreturned by AppleScript for OSAScriptError10-40returned by scripting components for OSAScriptError10-39 to 10-40errors in script compilation or execution, obtaining information about10-37 to 10-40'errs' keyword3-15'esrc' keyword3-15'evcl' keyword3-15event classes3-8event IDs3-8 to 3-9EventRecord data type2-13event records2-13, 3-8events, high-level. See high-level events'evid' keyword3-15expandable dialog hook functions2-97, 2-98expandable modal-dialog filter functions2-97, 2-98'exte' descriptor type4-57extensions of object classes3-41Ffactoring, for Apple event recording7-21, 9-6 to 9-13sending events without executing them9-12 to 9-13window movement9-12'fals' descriptor type4-58File menuNew command9-9 to 9-11Open Query command12-14Quit command4-14, 4-20, 9-6 to 9-9file types'APPL'7-7, 10-14'edtp'2-32'edts'2-32'edtt'2-32'osas'10-14'qery'12-46'scpt'7-7, 10-14Finder events3-8FindNextComponent function10-5'fmts' format type2-25formAbsolutePosition key formintroduced6-12key data for6-14specifying6-63FormatIOParamBlock data type2-69format I/O verbs2-69 to 2-70format marks2-27FormatsAvailable data type2-26format types2-24 to 2-26'form' keyword6-8formName key formintroduced3-36, 6-12key data for6-14specifying6-62 to 6-63formPropertyID key formintroduced3-36, 6-12key data for6-13specifying6-63formRange key formintroduced3-36, 6-12key data for6-20 to 6-21specifying6-72 to 6-75formRelativePosition key formintroduced3-36, 6-12key data for6-15specifying6-64formTest key formand formWhose6-42introduced3-36, 6-12key data for6-15 to 6-19specifying6-64 to 6-72formUniqueID key formintroduced3-36, 6-12key data for6-14formWhose key form6-12, 6-42 to 6-45'from' keywordas the keyAEContainer keyword6-8as the keyOriginalAddressAttr keyword3-15, 9-37'fss ' descriptor type4-58functional-area suites of Apple events1-11Ggeneric script IDs10-85generic scripting component10-84 to 10-92component-specific routines and10-87 to 10-92default scripting component, getting and setting10-86 to 10-87defined7-22and generic script IDs10-85name of component, obtaining10-47opening a connection to10-4and OSALoad function10-15generic storage descriptor recordsdefined10-12routines for manipulating trailer10-92 to 10-94Get AETE eventhandling8-23 to 8-26introduced7-20Get Data eventresolving object specifier record in6-5 to 6-7sample object accessor functions6-29 to 6-34sent by AppleScript component7-10GetDefaultUser function11-33, 11-75 to 11-76GetEditionFormatMark function2-27, 2-82 to 2-83GetEditionInfo function2-49, 2-98 to 2-99GetEditionOpenerProc function2-63, 2-102GetLastEditionContainerUsed function2-39, 2-90 to 2-91GetStandardFormats function2-101GoToPublisherSection function2-49 to 2-50, 2-100Hhandlers for Apple events. See Apple event handlershigh-level events. See also Apple eventshandling when accepting Apple events4-5 to 4-7processing while waiting for reply Apple event5-24I, Jidle functions5-21 to 5-23InitDBPack function12-60 to 12-61InitEditionPack function2-12, 2-74insertion location descriptor records8-5'inte' keyword3-15interapplication communication (IAC)1-3 to 1-22invalidating users11-44I/O functions2-68, 2-104 to 2-105IPCListPorts functiondescription11-54 to 11-55use of by PPCBrowser function11-25 to 11-27IPCListPortsPBRec data type11-46isHighLevelEventAware flag4-5IsRegisteredSection function2-14, 2-78KkAEAlwaysInteract flag4-46 to 4-47kAEAnswer event ID4-36kAECanInteract flag4-46 to 4-47kAECanSwitchLayer flag4-47kAECoreSuite event class3-8kAEDontExecute flag5-40, 9-12kAEDontRecord flag5-40, 9-3kAEInteractWithAll flag4-48kAEInteractWithLocal flag4-48kAEInteractWithSelf flag4-48kAENeverInteract flag4-46 to 4-47kAENoReply flag5-14 to 5-15kAEOpenDocuments event ID3-9kAEPrintDocuments event ID3-9kAEQueueReply flag4-37, 5-14 to 5-15kAEQuitApplication event ID3-9kAEWaitReply flag4-36, 5-14 to 5-15kCoreEventClass event class3-8keyAddressAttr keyword3-15keyAECompOperator keyword6-16keyAEContainer keyword3-34, 6-8, 6-55keyAEDesiredClass keyword3-34, 6-8, 6-55keyAEEditionFileLoc keyword4-22keyAEIndex keyword6-42keyAEKeyData keyword3-34, 6-8keyAEKeyForm keyword3-34, 6-8keyAELogicalOperator constant6-17keyAELogicalTerms constant6-17keyAEObject keyword8-5keyAEObject1 keyword6-16keyAEObject2 keyword6-16keyAEPosition keyword8-5keyAERangeStart constant6-20keyAERangeStop constant6-20keyAETest keyword6-42key data, in object specifier records6-12 to 6-21defined3-36for formAbsolutePosition6-14for formNameID6-14for formPropertyID6-13for formRange6-20for formRelativePosition6-15for formTest6-15 to 6-19for formUniqueID6-14for formWhose6-42specifying6-57 to 6-75keyDirectObject keyword3-15keyErrorNumber keyword3-15, 4-36 to 4-37keyErrorString keyword3-15, 4-37keyEventClassAttr keyword3-15keyEventIDAttr keyword3-9, 3-15keyEventSourceAttr keyword3-15, 4-29key form, in object specifier recordsdefined3-36introduced6-11 to 6-12specifying6-57keyInteractLevelAttr keyword3-15, 4-45keyMissedKeywordAttr keyword3-15, 4-30, 4-34 to 4-35, 5-10keyOptionalKeywordAttr keyword3-15, 4-34, 5-7 to 5-10keyOriginalAddressAttr keyword3-15keyOSASourceEnd keyword10-39keyOSASourceStart keyword10-39keyReturnIDAttr keyword3-15keyTimeoutAttr keyword3-15, 5-21keyTransactionIDAttr keyword3-15'keyw' descriptor type4-58keywords for Apple events3-15keyword-specified descriptor records. See also descriptor recordsadding to AE records5-32 to 5-33defined3-15 to 3-16deleting from AE records4-92 to 4-93disposing of4-39 to 4-40getting data out of4-79 to 4-80getting descriptor records out of4-80 to 4-81getting descriptor types of4-90 to 4-91getting sizes of4-90 to 4-92kHighLevelEvent message class4-5kOSAComponentType component type10-4kOSAGenericScriptingComponentSubtype component subtype10-4, 10-14kOSAScriptIsModified script information selector10-42kOSAScriptResourceType resource10-14kOSASupportsAECoercion flag10-52kOSASupportsAESending flag10-5, 10-56kOSASupportsCoercion flag10-5kOSASupportsCompiling flag10-5, 10-47kOSASupportsDialects flag10-5, 10-67kOSASupportsGetSource flag10-5, 10-51kOSASupportsRecording flag10-5, 10-59kOSASupportsTinkering flag10-5, 10-72kOSASupportsWindowEditing flag10-5Llinking programs. See program linking'list' descriptor type4-57localAndRemoteHLEvents flag4-5LocationNameRec data type11-19, 11-49logical descriptor recordscreating6-69 to 6-70, 6-91 to 6-92defined6-17'long' descriptor type4-57M'magn' descriptor type4-57mark-adjusting function6-54marking callback functions6-53 to 6-54mark token function6-53menu commandsCreate Publisher (Edit menu)2-10New (File menu)9-9 to 9-12Open Query (file menu) 12-14Publisher/Subscriber Options (Edit menu)2-10, 2-43 to 2-44Quit (File menu)4-14, 4-20, 9-6 to 9-9Show/Hide Borders (Edit menu)2-10Stop All Editions (Edit menu)2-10Subscribe To (Edit menu)2-10message blocksdefined11-5reading data using11-40 to 11-41writing data using11-42 to 11-43'miss' keyword3-15, 5-10modal-dialog filter functions, expandable2-97, 2-98'modi' script information selector10-42Move event, handled by script context7-25 to 7-28NNewPublisherDialog function2-29, 2-31, 2-93 to 2-94NewPublisherExpDialog function2-60 to 2-61, 2-96 to 2-98NewPublisherReply data type2-30 to 2-31new publisher reply records2-30, 2-80, 2-93 to 2-94NewSection function2-18, 2-75NewSubscriberDialog function2-37 to 2-39, 2-91 to 2-92NewSubscriberExpDialog function2-60, 2-96 to 2-98NewSubscriberReply data type2-38new subscriber reply records2-38 to 2-39, 2-91Notification Manager, used by Apple Event Manager4-50null descriptor recordsas default reply Apple event3-26, 4-36used to specify default container6-10'null' descriptor type4-58, 6-10, 9-17O'oapp' event ID3-9object accessor dispatch tablesdefined6-5getting entries from6-81 to 6-82installing entries in6-21 to 6-27, 6-78 to 6-79removing entries from6-84 to 6-85system6-22object accessor functionsadding to dispatch tables6-21 to 6-27, 6-78 to 6-79calling6-82 to 6-83defined6-4examples of6-29 to 6-38getting from dispatch tables6-81 to 6-82for properties6-37 to 6-38removing from dispatch tables6-84 to 6-85whose descriptor records and6-44 to 6-45writing6-28 to 6-45object callback functionsdefined6-4error callback function6-100mark-adjusting function6-54marking callback functions6-53 to 6-54mark token function6-53object comparison function6-50 to 6-52object-counting function6-48 to 6-49object-marking function6-54special handler dispatch tables and4-100specifying6-79 to 6-80token disposal function6-41writing6-45 to 6-75object classes, Apple eventApple event objects and1-11and classification of Apple event objects3-39 to 3-41defined3-6object class IDsin object specifier records3-35, 6-9for properties of Apple event objects3-42, 6-13object class inheritance hierarchy3-40 to 3-41object comparison function6-50 to 6-52object-counting function6-48 to 6-49object-marking function6-54object specifier recordsapplication-defined functions for resolving6-94 to 6-103complex6-64 to 6-75creating6-55 to 6-75, 6-88 to 6-94defined3-32 to 3-39descriptor types used in6-76keywords for3-34, 6-8resolving3-33, 6-4 to 6-8, 6-85 to 6-87simple, creating6-57 to 6-60specifying a property6-63specifying a range6-72 to 6-75specifying a relative position6-64specifying a test6-64 to 6-72specifying the container hierarchy6-61 to 6-63Object Support Librarydisabling4-103initializing6-77linking6-3'odoc' event ID3-9offset descriptor records6-72, 6-88 to 6-89Open Application eventdefined4-13event ID for3-9handling4-14 to 4-15OpenComponent function10-4OpenDefaultComponent function10-4Open Documents eventdefined4-13event ID for3-9handling4-15 to 4-17illustration of responding to3-27OpenEdition function2-26, 2-41, 2-83opener verbs2-64 to 2-66OpenNewEdition function2-26, 2-35, 2-86 to 2-87Open Query command (File menu)12-14. See also Data Access ManagerOpen Scripting Architecture (OSA)defined1-13and scripting components7-4optional parameters for Apple eventsdefined3-9and keyOptionalKeywordAttr attribute4-34specifying5-7 to 5-10'optk' keyword3-15, 5-7 to 5-10OSAActiveProcPtr data type10-23OSAAddStorageType function10-93 to 10-94OSAAvailableDialectCodeList function10-68 to 10-69OSAAvailableDialects function10-70 to 10-71OSACoerceFromDesc function10-52 to 10-54OSACoerceToDesc function10-54 to 10-55OSACompileExecute function10-10, 10-63 to 10-64OSACompile function10-7 to 10-9, 10-48 to 10-50'osa ' component type10-4OSACopyID function10-50OSADisplay function10-35 to 10-36OSADispose function10-41OSADoEvent function10-19 to 10-23, 10-76 to 10-78OSADoScript function10-10, 10-65 to 10-66OSAExactScriptingComponent function10-18OSAExecuteEvent function10-19 to 10-21, 10-74 to 10-76OSAExecute function10-7 to 10-9, 10-14 to 10-17, 10-33 to 10-35OSAGenericToRealID function10-90 to 10-91OSAGetActiveProc function10-46OSAGetCreateProc function10-56OSAGetCurrentDialect function10-68OSAGetDefaultScriptingComponent function10-86OSAGetDialectInfo function10-69 to 10-70OSAGetResumeDispatchProc function10-73 to 10-74OSAGetScriptInfo function10-43 to 10-44OSAGetScriptingComponentFromStored function10-88 to 10-89OSAGetScriptingComponent function10-89 to 10-90OSAGetSendProc function10-57OSAGetSource function10-17 to 10-18, 10-51 to 10-52OSAGetStorageType function10-93OSAID data type7-23, 10-29OSALoadExecute function10-61 to 10-63OSALoad function10-14 to 10-17, 10-32 to 10-33OSAMakeContext function10-79OSARealToGenericID function10-91 to 10-92OSARemoveStorageType function10-94OSAScriptError function10-10 to 10-11, 10-37 to 10-40OSAScriptingComponentName function10-47OSASetActiveProc function10-45OSASetCreateProc function10-56OSASetCurrentDialect function10-67OSASetDefaultScriptingComponent function10-87OSASetDefaultTarget function10-58 to 10-59OSASetResumeDispatchProc function10-72OSASetScriptInfo function10-41 to 10-42OSASetSendProc function10-57OSAStartRecording function10-59 to 10-60OSAStopRecording function10-60 to 10-61OSAStore function10-30 to 10-31P'pdoc' event ID3-9port filter function11-24 to 11-25PortInfoRec data type11-25port locations11-4port names11-4PPCAccept function11-38, 11-66, 11-68 to 11-69PPCAcceptPBRec data type11-46PPCBrowser function11-52 to 11-53use to locate a port11-22 to 11-27use with Apple events5-11, 5-12PPCClose function11-43 to 11-44, 11-58 to 11-59PPCClosePBRec data type11-46PPCEnd function11-43, 11-64 to 11-65PPCEndPBRec data type11-46PPCInform function11-35 to 11-37, 11-66 to 11-68PPCInformPBRec data type11-46PPCInit function11-11, 11-51PPCOpen function11-20 to 11-22, 11-56 to 11-57PPCOpenPBRec data type11-46PPCParamBlockRec data type11-15, 11-46PPC parameter blocks11-15, 11-17, 11-46 to 11-48PPCPortRec data type11-18 to 11-19, 11-48PPC portsclosing11-43 to 11-44defined11-4listing available11-22 to 11-27opening11-17 to 11-22specifying locations11-4, 11-19, 11-49specifying names11-4, 11-17PPCRead function11-40 to 11-41, 11-71 to 11-73PPCReadPBRec data type11-46PPCReject function11-39, 11-66, 11-70PPCRejectPBRec data type11-46PPC sessionsaccepting11-37 to 11-39defined11-5ending11-43exchanging message blocks during11-39 to 11-40initiating11-29 to 11-35receiving requests for11-35 to 11-37rejecting11-37 to 11-39PPCStart function11-29, 11-33 to 11-35, 11-59 to 11-62PPCStartPBRec data type11-46PPCWrite function11-42 to 11-43, 11-73 to 11-75PPCWritePBRec data type11-46primitive object classes3-41Print Documents eventdefined4-13event ID for3-9handling4-17 to 4-19program linkingdefined11-5dialog box11-22 to 11-27to server applications for Apple events4-5Program-to-Program Communications (PPC) Toolbox11-3 to 11-97calling conventions11-14 to 11-17data structures in11-46 to 11-48routines in11-50 to 11-77testing for availability11-11'prop' descriptor type4-58properties of Apple event objectsdefined3-42 to 3-46object accessor functions that find6-37 to 6-38object class ID for3-42, 6-13specifying in an object specifier record6-63'prvw' format type2-25'psn ' descriptor type3-14, 4-58Publisher Options command (Edit menu)2-10, 2-43publishersborders2-9 to 2-10, 2-50 to 2-54canceling2-48 to 2-49creating2-29 to 2-32defined2-4locating2-49 to 2-50multiple2-18, 2-58 to 2-59, 2-73options for2-43 to 2-50update modes2-47 to 2-48Publisher/Subscriber Options command (Edit menu)2-10publishing data. See Edition Manager; publishersQ'qdef' resource type12-90, 12-92'qery' file type12-46'qrsc' resource type12-90 to 12-91queriesconverting results to text12-42 to 12-45, 12-67 to 12-68defined12-7executing12-78 to 12-79halting execution12-81 to 12-82processing results12-36 to 12-46retrieving results12-42sending12-30 to 12-31, 12-76 to 12-77starting12-63 to 12-65query definition function resources12-92query definition functions12-51 to 12-54query documents12-46 to 12-54contents12-48 to 12-51dialog boxes12-46 to 12-47QueryRecord data type12-56query records12-56 to 12-57creating12-61defined12-46disposing of12-62 to 12-63query resources12-90 to 12-91query string resources12-91Quit Application eventdefined4-13event ID for3-9handling4-19 to 4-20Quit command (File menu)4-14, 4-20'quit' event ID3-9Rrange descriptor recordscreating6-92 to 6-93key data for6-20ReadEdition function2-27, 2-85 to 2-86Receive Recordable Event event9-36'reco' descriptor type4-57recordable applications1-18 to 1-19, 7-20 to 7-22, 9-3 to 9-5'aete' resources and1-18 to 1-19defined7-5direct dispatching and5-13factoring9-6 to 9-13guidelines for what to record9-14 to 9-35introduced1-15Recorded Text event10-27Recording Off event9-4Recording On event9-4recording scripts, routines for10-59 to 10-61reference constantsfor Apple event handlers4-8, 4-34for object accessor function6-24RegisterSection function2-22, 2-76 to 2-77relative position, specifying in an object specifier record6-64reply Apple events4-36 to 4-39disposing of4-39 to 4-40filter functions while waiting for5-24timeouts for4-84 to 4-85, 5-20 to 5-21required Apple events4-11 to 4-20required parameters for Apple events3-9, 4-34 to 4-35Required suite of Apple events1-10Reset Timer event4-85ResListElem record12-57resourcesalias2-19Apple event terminology. See 'aete' resources; 'aeut' resourcesquery12-90 to 12-91query definition function12-92query string12-91script7-7, 10-14scripting size8-45 to 8-46section2-19size4-5, 10-14resource types'aete'. See 'aete' resources'aeut'. See 'aeut' resources'alis'2-19'qdef'12-90, 12-92'qrsc'12-90 to 12-91'scpt'7-7, 10-14'scsz'8-45 to 8-46'sect'2-19'SIZE'4-5, 10-14'wstr'12-48, 12-91result handlers12-42 to 12-46, 12-86 to 12-89application12-43function declaration12-43installing12-86 to 12-87provided by Apple Computer12-42 to 12-43system12-43ResultsRecord data type12-41, 12-58results records12-40 to 12-42resume dispatch functionsdefined7-27example of use10-21'rtid' keyword3-15Ssample routinesDoEvent4-5DoHighLevelEvent4-6DoNewPublisher2-33 to 2-34DoNewSubscriber2-40DoOptionsDialog2-46 to 2-47DoPPCAccept11-38DoPPCReject11-39DoReadEdition2-42 to 2-43DoSectionRead2-15DoWriteEdition2-21, 2-34, 2-36, 2-46, 2-47MyAcceptCompProc11-38MyBrowserPortFilter11-24MyCompareObjects6-52MyConnectToScripting10-6MyCountObjects6-49MyCreateComparisonDescRec6-68MyCreateDocContainer6-61MyCreateFormNameObjSpecifier6-67MyCreateLogicalDescRec6-70MyCreateObjSpecRec6-70MyCreateOptionalKeyword5-9MyCreateRangeDescriptor6-74MyCreateTableContainer6-62MyDeleteNewUserRefNum11-45MyDoDragWindow9-13MyDoMenuNew9-9MyDoMenuQuit9-6MyDoNewScript10-9MyEditGenericScript10-18MyFindDocumentObjectAccessor6-30MyFindParaObjectAccessor6-32MyFindPropertyOfWindowObjectAccessor6-38MyFindWindowObjectAccessor6-35MyFindWordObjectAccessor6-34MyGeneralAppleEventHandler10-21MyGetAETE8-25MyGetQRCompRoutine12-21MyGetScriptErrorInfo10-11MyGetSectionHandleFromEvent2-15MyGetTargetAddress5-12MyGotRequiredParams4-35MyHandleCreateElement9-11MyHandleCreatePublisherEvent4-23MyHandleOApp4-15MyHandleODoc4-15MyHandlePDoc4-18MyHandleQuit4-19, 9-8MyHandler4-38MyHandleSectionReadEvent2-14MyHiLevel12-18MyIdleFunction5-23MyInformCompProc11-37MyIPCListPorts11-28MyLoadAndExecute10-16MyLoLevel12-33MyMultHandler4-39MyOpenExistingDocument2-23sample routines (continued)MyPPCBrowser11-26MyPPCClose11-44MyPPCEnd11-43MyPPCInform11-36MyPPCInit11-12MyPPCOpen11-21MyPPCRead11-41MyPPCStart11-34MyPPCWrite11-42MyQDef12-52MyReadComplete11-41MyRejectCompProc11-39MyRequestRowFromTarget6-59MySaveDocument2-21MySendAECreateElement9-10MySendAEQuit9-7MySendFragment12-31MySendMultiplyEvent5-17MySetTargetAddresses5-11MyStartCompRoutine12-21MyStartSecureSession11-32MyStartStatus12-26MyTypeIntegerHandler12-45MyWriteComplete11-43'scpt' component subtype10-4, 10-14'scpt' file type7-7'scpt' resource type7-7, 10-14scriptable applications'aete' resources and1-16 to 1-17, 8-13 to 8-23AppleScript and8-3 to 8-7defined7-4introduced1-15requirements for1-16 to 1-17, 7-14 to 7-20, 8-13 to 8-23script applicationscreator signature for10-14defined7-7script comments7-6, 10-14script contextsdefined7-23handling Apple events with7-25 to 7-28, 10-19 to 10-23introduced7-12routines for handling Apple events with10-71 to 10-79used for global contexts10-8script datacoercing a descriptor record to10-52 to 10-54coercing to a descriptor record10-54 to 10-55defined7-23disposing of10-41executing10-14 to 10-17, 10-33 to 10-35generic scripting component and trailer for10-15getting handle to10-30 to 10-31getting information about10-43 to 10-44loading and executing10-14 to 10-17resource and file types for10-13saving10-12 to 10-14, 10-30 to 10-31saving and loading, routines for10-30 to 10-33setting and getting information about10-41 to 10-44storage formats for10-12 to 10-13updating10-50Script Editor applicationand applications that execute scripts1-21scriptable applications and1-14 to 1-15script window for7-6script editorsand Apple event recording9-35 to 9-37defined7-6script error information selectors10-37 to 10-38script files7-7script IDsdefined7-23and generic script IDs10-85script information selectors10-43 to 10-44scripting components7-3 to 7-28, 10-3 to 10-125and Apple event recording9-35 to 9-37application-defined functions for10-94 to 10-98connecting with via Component Manager10-3 to 10-7defined7-4error numbers for OSAScriptError10-39 to 10-40flags for component description records10-5and generic scripting component7-22, 10-15introduced1-13optional routines for10-46 to 10-79required routines for10-30 to 10-46routines used by10-84 to 10-94and scriptable applications7-8 to 7-11using to manipulate and execute scripts7-11 to 7-14, 7-22 to 7-28writing10-27ScriptingComponentSelector data type10-85scripting languagesAppleScript. See AppleScript scripting languageand object specifier records3-33supporting1-13 to 1-22scriptsdefined7-4executing in one step, routines for10-61 to 10-66introduced1-13manipulating and executing1-19 to 1-22, 7-22 to 7-28multithreaded execution of10-4recording, Recorded Text event and10-27recording, routines for10-59 to 10-61script text files7-8script valuescoercing to readable text10-35 to 10-36coercion of, routines for10-52 to 10-55defined7-23'scsz' resource8-45 to 8-46'sect' descriptor type4-58Section Cancel event2-13SectionEventMsgClass event class4-21SectionOptionsDialog function2-43, 2-94 to 2-95SectionOptionsExpDialog function2-60 to 2-61, 2-96 to 2-98SectionOptionsReply data type2-45 to 2-46Section Read event2-13, 4-21preventing initial2-75SectionReadMsgID event ID4-21SectionRecord data type2-17 to 2-18, 2-72 to 2-73section records for publishers and subscribers2-15 to 2-24Section Scroll event2-13, 4-21SectionScrollMsgID event ID4-21sections. See also publishers; subscribers2-15 to 2-28canceling2-48 to 2-49defined2-4reading and writing2-24registering2-13 to 2-14renaming documents that contain2-50Section Write event2-13, 4-21SectionWriteMsgID event ID4-21'sect' resource type2-19'seld' keyword6-8Select event9-16 to 9-35send functionsroutines for manipulating10-55 to 10-57supplying alternative10-25 to 10-26sendMode flags for AESend5-39server applications, for Apple eventsdefined3-4 to 3-5introduced1-9setting user interaction preferences4-48user interaction with4-45 to 4-55session ID, data accessdefined12-16getting12-28session numbers, data accessgetting12-36, 12-74 to 12-75use of12-36sessions, data accesscontrolling12-68 to 12-75examples12-18, 12-33getting information about12-36, 12-71 to 12-73initiating12-16, 12-28, 12-68 to 12-70terminating12-17, 12-32, 12-70 to 12-71, 12-81 to 12-82sessions, PPC. See PPC sessionsSet Data eventhandling1-12recording9-27 to 9-30sent by AppleScript component7-10sent during script execution1-17SetEditionFormatMark function2-27, 2-82SetEditionOpenerProc function2-63, 2-102Sharing Setup control panel11-6'shor' descriptor type4-57Show/Hide Borders command (Edit menu)2-10'sign' descriptor type3-14, 4-58simple object specifier records, creating6-57 to 6-60'sing' descriptor type4-57'SIZE' resourceuse by Apple events4-5use in script application files10-14source applications, for Apple events3-4 to 3-5source data, for scriptsAppleScript routines for styles10-82 to 10-84compiling10-48 to 10-50compiling and executing10-7 to 10-11defined7-23obtaining from script data10-51 to 10-52'srce' keyword10-39'srcs' keyword10-39'ssid' descriptor type3-14, 4-58Start Recording event9-36StartSecureSession function11-30 to 11-31, 11-62 to 11-65status routines, Data Access Manager12-22 to 12-28for DBGetQueryResults function12-22 to 12-28for DBStartQuery function12-22 to 12-28defined12-14function declaration12-22sample12-26 to 12-28and status messages12-22 to 12-25Stop All Editions command (Edit menu)2-10Stop Recording event9-37subclasses, in object class definitions3-40Subscriber Options command (Edit menu)2-43 to 2-45subscribersborders2-9 to 2-10, 2-50, 2-54canceling2-48creating2-37 to 2-39defined2-4modifying the contents of2-59to non-edition files2-62 to 2-70options for2-43 to 2-50update modes2-48Subscribe To command (Edit menu)2-10subscribing. See Edition Manager; subscriberssuperclasses, in object class definitions3-40system Apple event dispatch table4-7system coercion dispatch table4-41system object accessor dispatch table6-22T'targ' descriptor type3-14, 4-58target addresses of Apple events5-10 to 5-13target applications, for Apple events3-4 to 3-5terminology in applications, recommended2-4terminology resources, Apple event8-3 to 8-46and AppleScript7-17 to 7-20defined7-15structure of8-8 to 8-13, 8-26 to 8-44'TEXT' descriptor type4-57timeouts for interacting with the user4-50timeouts for reply Apple events4-84 to 4-85, 5-20 to 5-21'timo' keyword3-15token disposal functionscalled by Apple Event Manager6-41, 6-46defined6-7marking callback functions and6-54tokens, for Apple event objectsdefined6-4defining descriptor types for6-39 to 6-41object accessor functions and6-28 to 6-29ranges of text and6-40'tran' keyword3-15'true' descriptor type4-57typeAbsoluteOrdinal descriptor type6-14, 6-76typeAEList descriptor type4-57typeAERecord descriptor type4-57typeAlias descriptor type4-58typeAppleEvent descriptor type4-57typeApplSignature descriptor type3-14, 4-58, 5-10typeAppParameters descriptor type4-58typeBoolean descriptor type4-57typeChar descriptor type4-57typeCompDescriptor descriptor type6-16typeComp descriptor type4-57typeCurrentContainer descriptor type6-20, 6-76'type' descriptor type4-58typeEnumerated descriptor type4-58, 6-76typeExtended descriptor type4-57typeFalse descriptor type4-58typeFSS descriptor type4-58typeKeyword descriptor type4-58typeLogicalDescriptor descriptor type6-17typeLongFloat descriptor type4-57typeLongInteger descriptor type4-57typeMagnitude descriptor type4-57typeNull descriptor type4-58, 6-10, 9-17typeObjectBeingExamined descriptor type6-16, 6-68, 6-76typeObjectSpecifier descriptor type4-22, 6-55 to 6-75, 6-76typeOSAErrorRange descriptor type10-39typeOSAGenericStorage descriptor type10-12, 10-14typeProcessSerialNumber descriptor type3-14, 4-58, 5-10, 5-13typeProperty descriptor type4-58typeRangeDescriptor descriptor type6-20typeSectionH descriptor type4-58typeSessionID descriptor type3-14, 4-58, 5-10typeShortFloat descriptor type4-57typeShortInteger descriptor type4-57typeTargetID descriptor type3-14, 4-58, 5-10typeTrue descriptor type4-57typeType descriptor type4-58typeWhoseDescriptor descriptor type6-42 to 6-45typeWhoseRange descriptor type6-44typeWildCard descriptor type4-10, 4-58, 4-63, 6-26 to 6-27U, VUnRegisterSection function2-22, 2-48, 2-77 to 2-78user interactionrequesting4-49 to 4-56, 4-81 to 4-84setting preferences for client application4-45 to 4-47setting preferences for server application4-48Users & Groups control panel11-7WWaitNextEvent function, use by the Apple Event Manager5-15'want' keyword6-8whose descriptor records6-42 to 6-45whose range descriptor records6-44WriteEdition function2-27, 2-88'wstr' resource type12-48, 12-91X, Y, ZXCMDs, as a script10-13This Apple manual was written, edited, and composed on a desktop publishing system using Apple Macintosh computers and FrameMaker software. Proof pages were created on an Apple LaserWriter IINTX printer. Final page negatives were output directly from text files on an Optrotech SPrint 220 imagesetter. Line art was created using Adobe™ Illustrator and Adobe Photoshop. PostScript™, the page-description language for the LaserWriter, was developed by Adobe Systems Incorporated.Text type is Palatino® and display type is Helvetica®. Bullets are ITC Zapf Dingbats®. Some elements, such as program listings, are set in Apple Courier.LEAD WRITERSharon EversonWRITERSSean Cotter, Paul Black, Laine RapinDEVELOPMENTAL EDITORSAntonio Padial, Anne SzablaINDEX SPECIALISTSanborn HodgkinsILLUSTRATORSBruce Lee, Ruth Anderson, Barbara Carey, Lisa HymelCOVER DESIGNERBarb SmythPRODUCTION EDITORTeresa LujanFORMATTERJudith RadinPROJECT MANAGERPatricia EastmanSpecial thanks to William Cook, Tony Francis, Warren Harris, Eric House, Ed Lai, Donald Olson, Beverly ZegarskiAcknowledgments to Jens Alfke, Gary Bond, Kevin Calhoun, Julie Callahan, Dave Curbow, Donn Denman, Laili Di Silvestro, Sue Dumont, Wendy Krafft, Bennet Marks, Cassandra Markham Nelson, and the entire AppleScript and Inside Macintosh teams.@@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4í∫◊,Palatino

.
°dONLNdˇˇ(ô∫    Addison-WÑ@°dONLNdˇˇ)4esley Publishing Company    °dONLNdˇˇ(´∫Reading, MassachusettsÀ†°dONLNdˇˇ)hMenlo Park, California쇰dONLNdˇˇ)dNew ˆ∞°dONLNdˇˇ)
Y#°dONLNdˇˇ)ork°dONLNdˇˇ(∑∫Don Mills, Ontarioc °dONLNdˇˇ)T
W膰dONLNdˇˇ)okingham, England@°dONLNdˇˇ)XAmsterÜ°dONLNdˇˇ)damwp°dONLNdˇˇ)Bonn°dONLNdˇˇ(√∫SydneyH °dONLNdˇˇ)'Singapor°dONLNdˇˇ)$
ee∞°dONLNdˇˇ)
T°dONLNdˇˇ)okyoÏP°dONLNdˇˇ)Madrid–°dONLNdˇˇ)(San Juan°dONLNdˇˇ(œ∫Parisl¿°dONLNdˇˇ)Seoulk`°dONLNdˇˇ)MilanËÄ°dONLNdˇˇ) Mexico City °dONLNdˇˇ):
T»Ä°dONLNdˇˇ)aipei
(0∫
4Ÿ∫˘

{∂èÕ4zµ{∂ê{∂èÕ08x|˛˛
ˇ
ˇ?ˇ¯?ÔÔ«‡á‡É¿
¿
Äê{∂èÕ
08||«‡É¿¿
ÄÄ

ˇ·ˇ‚7^3 ðdONLNdí∫´
‘*tINSIDE MACINT∫ °dONLNdí
‘´(§
‘OSH

˙H
 4˚H
  
H


ˇ·ˇ‚7^ˇˇ≥>ˇ◊°dONLNd
H
.
Ú(
&HInterapplication Communicationˇ&Z@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄ú˙
¯4^*¿∫,Palatino
.
°dONLNdZ*f1+*c
°dONLNd\6er)Apple Computer>Ä°dONLNd\reÇ)<, Inc.°dONLNdg*pE(n*© 1993, .Ä°dONLNdgFpÇ)Apple ComputerÌ°dONLNd-gÅpë);, Inc.°dONLNd4p*yP(w*All rights r˝Ä°dONLNd@pPyo)&    eserved. °dONLNdJ{*Ñ•(Ç*#No part of this publication may be °dONLNdmÑ*ç-*    
rÑÄ°dONLNdnÑ-ç8)epr-°dONLNdqÑ9çd)oduced, storËÄ°dONLNd}ÑdçÄ)+    ed in a r°°dONLNdÜÑÅçù)    etrieval °dONLNdèç*ñ≤(î*'system, or transmitted, in any form or °dONLNd∂ñ*üû*     by any means, mechanical, electréÄ°dONLNd÷ñûü∞)tonic, °dONLNd‹ü*®b(¶*photocopying, rÔÄ°dONLNdÎüb®p)8ecor¥°dONLNdÔüq®µ)ding, or otherwise, °dONLNd
®*±™(Ø*$without prior written permission of °dONLNd
'±*∫f*    Apple Computer>Ä°dONLNd
5±f∫´)<, Inc. Printed in the °dONLNd
K∫*√d(¡*United States of iÄ°dONLNd
\∫d√Ñ):America.°dONLNd
e≈*Œf(Ã*No licenses, exprúÄ°dONLNd
v≈fŒ¢)<ess or implied, arX°dONLNd
à≈£Œ®)=e °dONLNd
äŒ*◊](’*granted with r`Ä°dONLNd
òŒ]◊£)3espect to any of the °dONLNd
≠◊*‡•(fi*#technology described in this book. °dONLNd
–‡*ÈE*    Apple rÑÄ°dONLNd
◊‡EÈó)etains all intellectual pr°dONLNd
Ò‡òȱ)Soperty °dONLNd
¯È*ÚØ(*&rights associated with the technology °dONLNdÚ*˚®*    %described in this book. This book is °dONLNdC˚*
ì*    intended to assist application °dONLNdb
*
π*    (developers to develop applications only °dONLNdä
*
6*    for eÄ°dONLNdé
6
ú)Apple Macintosh computers.°dONLNd©
*
#f(
!*Apple Computer>Ä°dONLNd∑
f
#v)<, Inc.°dONLNdæ
#*
,^(
**20525 Mariani >Ä°dONLNdÃ
#^
,d)4
AªÄ°dONLNdÕ
#c
,x)venue°dONLNd”
,*
5^(
3*Cupertino, CA6Ä°dONLNd‡
,^
5t)4 95014°dONLNdÁ
5*
>W(
<*408-996-1010°dONLNdÙ
B*
KQ*Apple, the MÄ°dONLNdˇ
BQ
K|)'Apple logo, Ö°dONLNd
B|
Kó)+APDA, °dONLNd
K*
TT(
R*AppleLink, ÜÄ°dONLNd
KT
Tn)*AppleT±Ä°dONLNd"
Kn
Tò)alk, LaserW&°dONLNd-
Kò
Tß)*riter•Ä°dONLNd2
K¶
T™), °dONLNd4
T*
]g(
[*Macintosh, MPWJ°dONLNdB
Tg
]ô)=, and SANE arŒÄ°dONLNdO
Tô
]û)2e °dONLNdQ
]*
f](
d*trademarks of …Ä°dONLNd_
]]
fô)3Apple Computerà°dONLNdm
]ô
f≠)<, Inc., °dONLNdu
f*
o-(
m*
rÑÄ°dONLNdv
f-
oD)egister˙°dONLNd}
fD
o•)ed in the United States and °dONLNdô
o*
xa(
v*other countries.°dONLNd™
z*
Éo*AppleScript, Finder‡Ä°dONLNdΩ
zo
Éù)E, Moof, New ⁄°dONLNd…
zù
É¢).
Yt°dONLNd 
z¢
ɱ)ork, °dONLNdœ
É*
åS(
ä*    QuickDraw;°dONLNdÿ
ÉS
åq)), QuickT"Ä°dONLNd‡
Éq
å≥)ime, and System 7 °dONLNdÚ
å*
ï1(
ì*arÑÄ°dONLNdÙ
å1
ïj)e trademarks of £°dONLNd
åj
ï¶)9Apple ComputeraÄ°dONLNd
å¶
ï∂)<, Inc.°dONLNd
ó*
†g(
û*Adobe IllustratorÄ°dONLNd*
óg
†k)=, “°dONLNd,
ój
†≠)Adobe Photoshop, °dONLNd=
†*
©f(
ß*and PostScript arÍÄ°dONLNdN
†f
©ü)<e trademarks of     °dONLNd^
††
©π):Adobe °dONLNdd
©*
≤Æ(
∞*#Systems Incorporated, which may be °dONLNdá
≤*
ª-*    
rÑÄ°dONLNdà
≤-
ªD)egister˙°dONLNdè
≤D
ªü)ed in certain jurisdictions.°dONLNd¨
Ω*
Δ™(
ƒ*$America Online is a service mark of °dONLNd–
Δ*
œ¢*    Quantum Computer Services, Inc.°dONLNd
—*
⁄k*CompuServe is a rÉÄ°dONLNd

—k
⁄Ç)Aegister˘°dONLNd
—Ç
⁄≥)ed trademark °dONLNd
⁄*
„r(
·*of CompuServe, Inc.°dONLNd)
Â*
Ój*FrameMaker is a røÄ°dONLNd:
Âj
ÓÅ)@egister5°dONLNdA
ÂÇ
Ó≥)ed trademark °dONLNdN
Ó*
˜P(
ı*
of Frame T4°dONLNdX
ÓP
˜§)&echnology Corporation.°dONLNdo
˘*Ö(*Helvetica, Palatino, and THÄ°dONLNdâ
˘Öû)[imes arÍ°dONLNdê
˘û£)e °dONLNdí*-(    *
rÑÄ°dONLNdì-D)egister˙°dONLNdöD§)ed trademarks of Linotype °dONLNd¥*M(*Company°°dONLNdªLN)"
.°dONLNdΩ*M(*HyperCarÄ°dONLNd≈NÄ)$d and HyperTôÄ°dONLNd—í)1alk are°dONLNd◊ìò)e °dONLNdŸ*(-(&*
rÑÄ°dONLNd⁄-(D)egister˙°dONLNd·D(ô)ed trademarks of Claris °dONLNd˘(*1W(/*Corporation.°dONLNd3*<†*#Internet is a trademark of Digital °dONLNd)<*EÄ*    Equipment Corporation.°dONLNd@G*P*ITC Zapf Dingbats is a r]Ä°dONLNdXGPñ)Uegister”°dONLNd_GñP†)ed °dONLNdbP*Yé(W*trademark of International TΔ°dONLNd~PéY´)dypeface °dONLNdÜY*bW(`*Corporation.°dONLNdìf*o:*Optr9Ä°dONLNdóf;o∞)!otech is a trademark of Orbotech °dONLNd∏o*xW(v*Corporation.°dONLNd≈|*Öπ*'Simultaneously published in the United °dONLNdÏÖ*ém*    States and Canada.4^…¿
Y
°dONLNdˇ]…eÒ(c…    LIMITED W°dONLNd]Òe
=)(ARRANTY ON MEDIAöp°dONLNd]
=e
Q)L AND °dONLNdf…nˇ(l…REPLACEMENT°dONLNd)s…{÷*ALL_0°dONLNd,s◊{
)
 IMPLIED WYê°dONLNd6s
{
M))ARRANTIES ON THIS °dONLNdH|…Ñ
<(Ç…MANUAL, INCLUDING IMPLIED °dONLNdbÖ…ç–*    
Wfl°dONLNdcÖœç
2)ARRANTIES OF MERCHANTd°dONLNdxÖ
2ç
P)cABILITY °dONLNdÄé…ñ
(î…AND FITNESS FOR AÊ∞°dONLNdëé
ñ
)H Ph¿°dONLNdìé
ñ
!)ARÜP°dONLNdïé
!ñ
C)
TICULAR °dONLNdùó…ü
?(ù…PURPOSE, ARE LIMITED IN DURA¶ °dONLNdπó
?ü
S)vTION °dONLNd憅®
(¶…TO NINETY (90) DAiÄ°dONLNdœ†
®
I)BYS FROM THE DAÀ†°dONLNd›†
H®
R)=TE °dONLNd‡©…±

(Ø…OF THE ORIGINAL∞°dONLNdÔ©
±
)B RET30°dONLNdÛ©
±
&)AILÖ °dONLNdˆ©
&±
Q)
 PURCHASE °dONLNd≤…∫
(∏…OF THIS PRODUCTæ`°dONLNd≤
∫
)B
.°dONLNdø…«
B(≈…$Even though Apple has reviewed this °dONLNd5»…–
-*    manual, APPLE MAKES NO Wa@°dONLNdM»
-–
R)dARRANTY °dONLNdU—…Ÿˇ(◊…OR REPRESENT{¿°dONLNda—ˇŸ
)6
AI °dONLNdb—
Ÿ
W)TION, EITHER EXPRESS °dONLNdw⁄…‚
O(‡…!OR IMPLIED, WITH RESPECT TO THIS °dONLNdò„…Î
*    MANUAL, ITS QUALITYf∞°dONLNd´„
Î
H)S
, ACCURACYõÄ°dONLNdµ„
HÎ
K),, °dONLNd∑Ï…ÙÙ(Ú…MERCHANT°dONLNdøÏÙÙ
)+ABILITY≠p°dONLNdΔÏ
Ù
U), OR FITNESS FOR A[†°dONLNdÿÏ
VÙ
W)F
 °dONLNdŸı…˝Õ(˚…
PB°dONLNd⁄ıÕ˝◊)AR_†°dONLNd‹ı◊˝
/)
TICULAR PURPOSE. AS AÑê°dONLNdÒı
/˝
H)X RESUL‡°dONLNd˜ı
H˝
L)
T†°dONLNd¯ı
L˝
O), °dONLNd˙˛…
˝(
…THIS MANUAL°dONLNd    ˛˛

N)5 IS SOLD “AS IS,” AND °dONLNd    
…

X(
…!YOU, THE PURCHASER, ARE ASSUMING °dONLNd    <
…

Q*    "THE ENTIRE RISK AS TO ITS QUALITY °dONLNd    ^
…
!
*    AND ACCURACY0°dONLNd    j


!
)<
.°dONLNd    l
&…
.
(
,…IN NO EVENT WILLùp°dONLNd    |
&

.
M)D APPLE BE LIABLE °dONLNd    ç
/…
7ı(
5…
FOR DIRECTˇ@°dONLNd    ó
/Ù
7
)+
, INDIRECT °dONLNd    °
/

7
A)(, SPECIAL, °dONLNd    ¨
8…
@Ì(
>…INCIDENTÃÄ°dONLNd    ¥
8Ì
@
F)$AL, OR CONSEQUENTIALK°dONLNd    »
8
G
@
H)Z
 °dONLNd    …
A…
I
(
G…DAMAGES RESUL)–°dONLNd    ÷
A

I
F)?TING FROM ANY °dONLNd    ‰
J…
R
D(
P…DEFECT OR INACCURACY IN THIS °dONLNd


S…
[
X*    +MANUAL, even if advised of the possibility °dONLNd
,
\…
dˇ*    of such damages.°dONLNd
=
i…
q‡*THE We†°dONLNd
B
i‡
q
O)ARRANTY AND REMEDIES SET °dONLNd
[
r…
z◊(
x…FOR°dONLNd
^
r◊
z
V)TH ABOVE ARE EXCLUSIVE AND IN °dONLNd
|
{…
ÉÙ(
Å…LIEU OF ALLQ°dONLNd
á
{ı
É
,), OTHERS, ORAL¸†°dONLNd
î
{
,
É
:)7 OR °dONLNd
ò
Ñ…
å
J(
ä… WRITTEN, EXPRESS OR IMPLIED. No °dONLNd
∏
ç…
ïÚ*    Apple dealerÜ0°dONLNd
ƒ
çÚ
ï
:)), agent, or employee is °dONLNd
‹
ñ…
û
+(
ú…authorized to make any modifi°dONLNd
˘
ñ
+
û
A)bcation, °dONLNd

ü…
ß
C(
•…'extension, or addition to this warrantyÛ`°dONLNd(
ü
B
ß
C)y
.°dONLNd*
¨…
¥
N(
≤…*Some states do not allow the exclusion or °dONLNdT
µ…
Ω
U*    .limitation of implied warranties or liability °dONLNdÇ
æ…
Δ
U*    ,for incidental or consequential damages, so °dONLNdÆ
«…
œ
O*    *the above limitation or exclusion may not °dONLNdÿ
–…
ÿ
C*    &apply to you. This warranty gives you °dONLNd˛
Ÿ…
·›*    specifi¿°dONLNd
Ÿfi
·
T)&c legal rights, and you may also have °dONLNd+
‚…
Í
O(
Ë…,other rights which vary from state to state.4^
h
™
¯4
∫
h¿
¯


∫
h
«
¯4
∫
h
«
¯ 
ª
h
ª
¯

ˇ·ˇ‚7^,    Helvetica°dONLNdˇˇ(
Ã
hISBN 0-201-62200-9°dONLNdˇˇ*    1 2 3 4 5 6 7 8 9-MU-9796959493°dONLNdˇˇ*    First Printing, June 1993ˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
Ñ`(‡iii4^H¿ˇˇ¬òˇ◊°dONLNd\∫u
(n∫Contents
°dONLNd    ü∫´“*:FigurR¿°dONLNdü“´Ê)es, Tè °dONLNdü´
6)ables, and Listings|@°dONLNd(ü
K´
U)fxv

…H–4 H– ÀHÀ

ˇ·ˇ‚7^,    Helvetica°dONLNd+ΩH»m(≈HPreface°dONLNd3∫∫…‚)rAbout ∑@°dONLNd9∫‚…
 )(    This Book
Û@°dONLNdDº
4»
G)Rxxiii°dONLNdK–∫‹ı(Ÿ∫Format of a T¿°dONLNdX–ı‹
6);ypical ChapterM °dONLNdh–
J‹
\)Uxxiv°dONLNdm›∫È
E(Ê∫Conventions Used in This BookÄ°dONLNdå›
ZÈ
i)†xxv°dONLNdê̓ˆ˛(ÛƒSpecial Fonts°‡°dONLNdüÍ
ˆ
!)Nxxv°dONLNd£˜ƒ
 (
ƒ
T∫¿°dONLNd§˜…

)ypes of Notes)`°dONLNd≥˜


))Qxxv°dONLNd∑
ƒ

V(
ƒAssembly-Language Information?Ä°dONLNd÷

k

})ßxxvi°dONLNd€
∫

$(
∫The Development Envirц°dONLNd

$

E)jonment|‡°dONLNd¯

Z

l)6xxvi


MH
T4
NH
T 
OH
O

ˇ·ˇ‚7^°dONLNd˝
AH
Lx(
IH    Chapter 1°dONLNd

>∫
M
⁄)r.Introduction to Interapplication Communication
@°dONLNd
7
@
Ô
L
¸(
I
Ô1-1°dONLNd
<
T∫
`
Ñ(
]∫*Overview of Interapplication Communications†°dONLNd
h
T
ô
`
¶)fl1-3°dONLNd
l
a∫
mˆ(
j∫Sharing Data m‡°dONLNd
y
aˆ
m
)<Among ¿°dONLNd

a

m
R)$Applicationsª‡°dONLNd
ç
a
f
m
s)L1-6°dONLNd
ë
n∫
z
7(
w∫Sending and Responding to h@°dONLNd
´
n
7
z
r)}Apple EventsB °dONLNd
π
n
á
z
î)P1-9°dONLNd
Ω
{ƒ
áÊ(
уStandar¥@°dONLNd
ƒ
{Ê
áÓ)"d Ò†°dONLNd
Δ
{Ó
á
))Apple EventsÀÄ°dONLNd
‘
{
>
á
P)P1-10°dONLNd
Ÿ
àƒ
î(
ëƒ    Handling `°dONLNd
‚
àÒ
î
,)-Apple EventsÎ@°dONLNd

à
@
î
R)O1-12°dONLNd
ı
ï∫
°Ó(
û∫Supporting ‡ °dONLNd
ïÓ
°
∞)4)AppleScript and Other Scripting Languages˜†°dONLNd+
ï
ƒ
°
÷)÷1-13°dONLNd0
¢ƒ
ÆÚ(
´ƒScriptable ™¿°dONLNd;
¢Ú
Æ
*).Applicationse‡°dONLNdI
¢
?
Æ
Q)M1-16°dONLNdN
؃
ª›(
∏ƒRecor¢`°dONLNdS
Ø›
ª˜)dable `°dONLNdY
د
ª
0)Applications‘Ä°dONLNdg
Ø
D
ª
V)L1-18°dONLNdl
ºƒ
»
¢(
≈ƒ0Applications That Manipulate and Execute Scriptsß@°dONLNdû
º
∂
»
»)Ú1-19°dONLNd£
…∫
’
5(
“∫Exchanging Message Blocksw°dONLNdæ
…
J
’
\)ê1-22

H4H H

ˇ·ˇ‚7^°dONLNd√
˘Hx(
H    Chapter 2°dONLNdÕ
ˆ∫
)rEdition Manager
i°dONLNdfi
¯
4
A)z2-1°dONLNd„∫ (∫Intr∑@°dONLNdÁ ˇ)oduction to È`°dONLNdÛˇ
¢)5%Publishers, Subscribers, and Editionsm`°dONLNd
∑
ƒ)∏2-4°dONLNd∫%
3("∫About the Edition Manager¿°dONLNd9
H%
Z)é2-12°dONLNd>&∫2
1(/∫Using the Edition ManagerN°dONLNdY&
F2
X)å2-12°dONLNd^3ƒ?Ú(<ƒ
Receiving *†°dONLNdh3Ú?
9).Apple Events Frÿ†°dONLNdw3
9?
§)Gom the Edition Manager£°dONLNdè3
π?
À)Ä2-13°dONLNdî@ƒLœ(IƒCr\°dONLNdñ@œL
8)eating the Section Recor‡°dONLNdÆ@
9L
U)jd and Δ`°dONLNd¥@
TL
Ü)Alias Recor=¿°dONLNdø@
áL
ç)3
dYÄ°dONLNd¬@
°L
≥)2-15°dONLNd«MƒY
u(Vƒ%Saving a Document Containing Sections’Ä°dONLNdÓM
âY
õ)≈2-19°dONLNdÛZƒf
µ(cƒ2Opening and Closing a Document Containing SectionsP`°dONLNd'Z
 f
‹(c
 2-22°dONLNd,gƒs
(pƒReading and Wå°dONLNd9g
s
J)Driting a Section›Ä°dONLNdKg
^s
p)V2-24°dONLNdPtŒÄ
-(}ŒFormats in an Editiong@°dONLNdgt
BÄ
T)t2-24°dONLNdlÅŒç
%(äŒOpening an Edition§¿°dONLNdÄÅ
9ç
K)k2-26°dONLNdÖéŒö
(óŒFormat MarksA†°dONLNdìé
!ö
3)S2-27°dONLNdòõŒß
(§ŒReading and Wå°dONLNd•õ
ß
d)Driting Edition DataÉ`°dONLNd∫õ
yß
ã)g2-27°dONLNdø®Œ¥
 (±ŒClosing an Edition›†°dONLNd”®
4¥
F)f2-28ˇ8@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*ˇ
¯,Palatino

.
(·*iv4^*¿
¯°dONLNd\¶h±(e¶Cr\°dONLNd\±h
)eating a Publisher䠡dONLNd\
h
&)c2-29°dONLNdi∞uª(r∞Cr\°dONLNdiªu
8)eating the Edition Container∂°dONLNd;i
Lu
^)ë2-32°dONLNd@v∞Ç
M(∞!Opening an Edition Container to W5Ä°dONLNdav
MÇ
s)ù    rite Dataú °dONLNdlv
áÇ
ô):2-35°dONLNdqɶè±(å¶Cr\°dONLNdsɱè
)eating a SubscriberKÄ°dONLNdàÉ
è
+)h2-37°dONLNdçê∞ú
q(ô∞)Opening an Edition Container to Read Data‡°dONLNd∏ê
Üú
ò)÷2-41°dONLNdΩù∞©
c(¶∞%Choosing Which Edition Format to Read?°dONLNd‰ù
x©
ä)»2-41°dONLNdÈ™¶∂
W(≥¶&Using Publisher and Subscriber Options@°dONLNd
™
l∂
~)Δ2-43°dONLNd
∑∞√
ò(¿∞1Publishing a New Edition While Saving or Manuallyq¿°dONLNd
I∑
≠√
ø)˝2-47°dONLNd
Nƒ∞–
"(Õ∞Subscribing to an Edition c†°dONLNd
hƒ
"–
ö)rAutomatically or ManuallyŒÄ°dONLNd
Ƀ
Æ–
¿)å2-48°dONLNd
à—∞›
(⁄∞Canceling Sections Wo °dONLNd
ú—
›
X)_ithin Documents=Ä°dONLNd
≠—
m›
)^2-48°dONLNd
≤fi∞Í
(Á∞Locating a Publisher Thrw†°dONLNd
 fi
Í
l)mough a SubscriberÔ`°dONLNd
›fi
ÄÍ
í)c2-49°dONLNd
‚ζ˜
f(Ù¶'Renaming a Document Containing SectionsÄ°dONLNdÎ
{˜
ç)’2-50°dONLNd¯¶

Y(

¶'Displaying Publisher and Subscriber Bor6‡°dONLNd7¯
Z

m)¥dersK‡°dONLNd=¯
Å

ì)'2-50°dONLNdB
∞
∂(
∞
Tµ¿°dONLNdC
µ
‘)ext Bor¿†°dONLNdJ
‘
Á)ders’†°dONLNdP
˚

)'2-54°dONLNdU
∞
ø(
∞Spr܇°dONLNdX
ø
˜)eadsheet Bor&Ä°dONLNdd
¯

)9ders;Ä°dONLNdj



1)'2-55°dONLNdo
∞
+
3(
(∞Object-Oriented Graphics Bor◊ °dONLNdã

3
+
F)ÉdersÏ °dONLNdë

Z
+
l)'2-56°dONLNdñ
,∞
8
(
5∞Bitmapped Graphics Bor◊@°dONLNd¨
,

8
0)mdersÏ@°dONLNd≤
,
D
8
V)'2-57°dONLNd∑
9∞
E
^(
B∞&Duplicating Publishers and Subscribers»@°dONLNdfl
9
r
E
Ñ)¬2-58°dONLNd‰
F¶
R
(
O¶Modifying a Subscriber5`°dONLNd¸
F
"
R
4)|2-59°dONLNd

S¶
_
(
\¶Relocating an Edition≥‡°dONLNd
S

_
+)s2-60°dONLNd
`¶
l
(
i¶Customizing Dialog BoxesÎ`°dONLNd7
`
/
l
A)â2-60°dONLNd<
mú
y
,(
vú Subscribing to Non-Edition Files¿¿°dONLNd^
m
@
y
R)§2-62°dONLNdc
z¶
ÜÔ(
ɶGetting the CurrkİdONLNds
zÔ
Ü
C)Ient Edition Opener†°dONLNdá
z
X
Ü
j)i2-63°dONLNdå
á¶
ì
(
ê¶Setting an Edition Openero °dONLNdß
á
-
ì
?)á2-63°dONLNd¨
î¶
†
(
ù¶Calling an Edition Opener»¿°dONLNd«
î
.
†
@)à2-64°dONLNdÃ
°¶
≠
+(
™¶Opening and Closing Editionsx@°dONLNdÍ
°
@
≠
R)ö2-68°dONLNdÔ
ƶ
∫
P(
∑¶&Listing Files That Can Be Subscribed TƆ°dONLNd
Æ
O
∫
T)©
o$ °dONLNd
Æ
i
∫
{)2-68°dONLNd
ª¶
«÷(
Ħ
Reading Fr0`°dONLNd'
ª◊
«
)1om and W©†°dONLNd/
ª

«
>)-riting to Files.@°dONLNd@
ª
S
«
e)O2-68°dONLNdE
Ȧ
‘
-(
—¶Calling a Format I/O FunctionQ`°dONLNdd
»
B
‘
T)ú2-68°dONLNdi
’ú
·
(
fiúEdition Manager Refer˝†°dONLNd~
’

·
)dence“Ä°dONLNdÑ
’
(
·
:)(2-71°dONLNdâ
‚¶
Ó…(
ζData Str``°dONLNdë
‚ 
Ó·)$ucturÊ@°dONLNdñ
‚·
ÓÍ)esχ°dONLNdö
‚˛
Ó
)2-71°dONLNdü
Ô∞
˚
.(
¯∞The Edition Container RecorÖ‡°dONLNd∫
Ô
.
˚
4)~
d°†°dONLNdΩ
Ô
H
˚
Z)2-71°dONLNd¬
¸∞˛(∞The Section RecorI`°dONLNd”
¸ˇ
)O
de °dONLNd÷
¸

+)2-72°dONLNd€    ¶
(¶Edition Manager Routines–‡°dONLNdı    
.
@)à2-73°dONLNd˙∞"
=(∞ Initializing the Edition Manager]Ä°dONLNd
R"
d)¢2-74°dONLNd!#∞/ª(,∞Cr\°dONLNd##ª/
H) eating and Registering a Section¸‡°dONLNdE#
\/
n)°2-74°dONLNdJ0∞<ª(9∞Cr\°dONLNdL0ª<
p)(eating and Deleting an Edition Container[@°dONLNdv0
Ö<
ó) 2-79°dONLNd{=∞I
J(F∞!Setting and Getting a Format Mark
 °dONLNdû=
_I
q)Ø2-81°dONLNd£J∞V
(S∞Reading in Edition Data' °dONLNdºJ
/V
A)2-83°dONLNd¡W∞c∫(`∞
W¬†°dONLNd¬Wπc
)    riting out Edition Data˘°dONLNd€W
1c
C)x2-86°dONLNd‡d∞p
(m∞Closing an Edition ˇ@°dONLNdÛd
p
Z)TAfter Reading or W °dONLNdd
[p
s)WritingÜ@°dONLNdd
áp
ô),2-88°dONLNdq∞}
(z∞Displaying Dialog Boxesx@°dONLNd+q
1}
C)Å2-90°dONLNd0~∞ä
M(á∞#Locating a Publisher and Edition Frì@°dONLNdS~
Mä
ì)ùom a Subscriberw`°dONLNdd~
®ä
∫)[2-98°dONLNdiã∞ó
%(î∞Edition Container Formatsr`°dONLNdÑã
:ó
Q)ä2-101°dONLNdäò∞§Ù(°∞Reading and Wå°dONLNdóòÙ§
])Driting Non-Edition Files”‡°dONLNd±ò
q§
à)}2-102°dONLNd∑•¶±(ƶApplication-Defi†°dONLNd«•±
*)Jned RoutinesI¿°dONLNd’•
?±
V)O2-105ˇx@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
‡(‡
v4^H¿°dONLNd\∫h
N(e∫Summary of the Edition Manager∫‡°dONLNd \
bh
y)®2-106°dONLNd&iƒu
(rƒPascal Summary‡°dONLNd6i
"u
9)^2-106°dONLNd<vŒÇ˙(Œ    ConstantsÆ°dONLNdGv
Ç
%)@2-106°dONLNdMÉŒèÎ(åŒData T:`°dONLNdSÉÎèˇ)ypes“@°dONLNdYÉ
è
*)(2-108°dONLNd_êŒú
B(ôŒEdition Manager Routines–‡°dONLNdyê
Vú
c)à2-1ò °dONLNd|ê
cú
h)
1Ä°dONLNd}ê
hú
m)
1°dONLNdùŒ©
(¶ŒApplication-Defi†°dONLNdèù
©
R)Jned RoutinesI¿°dONLNdùù
g©
t)O2-1°dONLNd†ù
t©
~)13°dONLNd£™ƒ∂˘(≥ƒ    C SummaryᆰdONLNdÆ™
∂
)I2-1N‡°dONLNd±™
∂
$)14°dONLNd¥∑Œ√˙(¿Œ    ConstantsÆ°dONLNdø∑
√
)@2-1u@°dONLNd¬∑
√
%)14°dONLNd≈ƒŒ–Î(ÕŒData T:`°dONLNdÀƒÎ–ˇ)ypes“@°dONLNd—ƒ
–
 )(2-1ôÄ°dONLNd‘ƒ
 –
*)16°dONLNd◊—Œ›
B(⁄ŒEdition Manager Routines–‡°dONLNdÒ—
V›
c)à2-1ò °dONLNdÙ—
c›
m)19°dONLNd˜fiŒÍ
(ÁŒApplication-Defi†°dONLNd
fi
Í
R)Jned RoutinesI¿°dONLNd
fi
gÍ
~)O2-122°dONLNd
΃˜˛(ÙƒResult Codesï`°dONLNd
)Î
˜
))N2-122


'H
.4
(H
. 
)H
)

ˇ·ˇ‚7^,    Helvetica°dONLNd
/
H
&x(
#H    Chapter 3°dONLNd
9
∫
'
)rIntroduction to P@°dONLNd
I


'
h)\Apple Events
 °dONLNd
W

|
&
â)f3-1°dONLNd
\
.∫
:ÿ(
7∫About ØÄ°dONLNd
b
.ÿ
:
)Apple Eventsâ`°dONLNd
p
.
(
:
5)P3-3°dONLNd
t
;ƒ
G
(
DƒApple Events and ˆ°dONLNd
Ö
;

G
o)QApple Event Objectsy°dONLNd
ö
;
Ñ
G
ë)o3-6°dONLNd
û
Hƒ
T˛(
QƒApple Event >Ä°dONLNd
™
H˛
T
r):Attributes and Parametersˇ‡°dONLNd
≈
H
Ü
T
ì)à3-7°dONLNd
…
UŒ
a
(
^ŒApple Event >Ä°dONLNd
’
U

a
4):
Attributes=@°dONLNd
·
U
I
a
V)A3-8°dONLNd
Â
bŒ
n
9(
kŒApple Event Parametersr`°dONLNd
˝
b
N
n
[)Ä3-9°dONLNd

oŒ
{Ì(
xŒInterpru†°dONLNd
oÌ
{
)eting Ï °dONLNd
o

{
?)Apple Event ™†°dONLNd
o
?
{
≥):Attributes and Parametersl°dONLNd5
o
»
{
⁄)â3-10°dONLNd:
|ƒ
àÁ(
ÖƒData Str``°dONLNdB
|Ë
àˇ)$ucturÊ@°dONLNdG
|ˇ
à
)es W‡@°dONLNdK
|

à
+)ithin ∑¿°dONLNdQ
|
+
à
f)Apple Events놰dONLNd_
|
{
à
ç)P3-12°dONLNdd
âŒ
ï
(
íŒDescriptor Recorfi °dONLNdt
â

ï
")Jds6‡°dONLNdx
â
7
ï
I)3-12°dONLNd}
ñŒ
¢Ò(
üŒKeywor¨`°dONLNdÉ
ñÒ
¢
)#d-Specifi凰dONLNdå
ñ

¢
o)'ed Descriptor RecorP`°dONLNdü
ñ
p
¢
z)Xds© °dONLNd£
ñ
é
¢
†)3-15°dONLNd®
£Œ
Ø
(
¨ŒDescriptor Lists|@°dONLNd∫
£
(
Ø
:)Z3-16°dONLNdø
∞∫
º˝(
π∫Responding to ;¿°dONLNdÕ
∞˝
º
8)CApple Events†°dONLNd€
∞
M
º
_)P3-20°dONLNd‡
Ωƒ
…
(
ΔƒAccepting and Pr:Ä°dONLNd
Ω

…
8)M    ocessing Œ`°dONLNd˘
Ω
8
…
s)'Apple Events®@°dONLNd
Ω
à
…
ö)P3-20°dONLNd
 ƒ
÷‚(
”ƒAbout ØÄ°dONLNd
 ‚
÷
E)Apple Event HandlersÏÄ°dONLNd(
 
Y
÷
k)w3-23°dONLNd-
◊Œ
„
R(
‡ŒExtracting and Checking Data[‡°dONLNdK
◊
g
„
y)ô3-23°dONLNdP
‰Œ


(
ÌŒInteracting Wù`°dONLNd]
‰



=)<ith the User7`°dONLNdk
‰
R

d)H3-25°dONLNdp
Ҍ
˝
D(
˙ŒPerforming the Requested d°dONLNdâ
Ò
D
˝
 )vAction and Returning a ResultÆ¿°dONLNd®
Ò
fi
˝
)ö3-25°dONLNd≠
˛∫
≈(∫Cr\°dONLNdØ
˛≈

)eating and Sending ˇ°dONLNd¬
˛


#)W
AΔ@°dONLNd√
˛
$

X)pple Eventsÿ‡°dONLNd–
˛
l

~)H3-28°dONLNd’ƒœ(ƒCr\°dONLNd◊œ˙)
eating an #‡°dONLNd·˙
M)+Apple Event Recorc °dONLNdÚ
M
S)S
d~‡°dONLNdı
g
y)3-29°dONLNd˙ƒ$Ë(!ƒAdding È@°dONLNd
Ë$
")$Apple Event ß¿°dONLNd
"$
ñ):Attributes and Parametersi °dONLNd(
´$
Ω)â3-29°dONLNd-%ƒ1¯(.ƒSending an 2`°dONLNd8%¯1
ú)4"Apple Event and Handling the Reply˙¿°dONLNd\%
∞1
¬)∏3-30°dONLNda2∫>ƒ(;∫
Wï°dONLNdb2√>Ï)    orking W»Ä°dONLNdj2Ï>
6))ith Object Specifil°dONLNd|2
7>
[)Ker Recor †°dONLNdÑ2
[>
e)$ds#`°dONLNdà2
z>
å)3-32°dONLNdç?ƒKÀ(Hƒ
D=@°dONLNdé?ÃKË)ata Str``°dONLNdï?ËKˇ)ucturÊ@°dONLNdö?ˇK
)es W‡@°dONLNdû?
K
t)ithin an Object Specifi釰dONLNdµ?
uK
ô)aer RecorÌÄ°dONLNdΩ?
ôK
ü)$
d    @°dONLNd¿?
¥K
Δ)3-34°dONLNd≈LƒX˜(UƒThe Classifi*@°dONLNd—L¯X
 )4
cation of w °dONLNd€L
 X
z)(Apple Event ObjectsÄ°dONLNdL
èX
°)o3-39°dONLNdıYŒe
(bŒObject Classes∂Ä°dONLNdY
!e
3)S3-39°dONLNd
fŒr◊(oŒPrN†°dONLNdfÿr
:)
operties and Elements] °dONLNd#f
Nr
`)v3-42°dONLNd(sƒÈ(|ƒFinding O °dONLNd0sÈ
C)%Apple Event ObjectsflÄ°dONLNdEs
W
i)n3-46°dONLNdJÄ∫åË(â∫
About the ‡°dONLNdTÄÈå
J)/Apple Event Managerª¿°dONLNdiÄ
^å
p)u3-48°dONLNdnçƒô¯(ñƒSupporting ‡ °dONLNdyç¯ô
h)4Apple Events as a Server ˜ °dONLNdíç
hô
ú)pApplicationu@°dONLNdüç
±ô
√)I3-48°dONLNd§öƒ¶¯(£ƒSupporting ‡ °dONLNdØö¯¶
f)4Apple Events as a Client ]¿°dONLNd»ö
g¶
õ)oApplication€‡°dONLNd’ö
ض
¡)H3-49°dONLNd⁄߃≥¯(∞ƒSupporting ‡ °dONLNdÂ߯≥
R)4Apple Event ObjectspÄ°dONLNd˙ß
g≥
y)o3-49°dONLNdˇ¥ƒ¿¯(ΩƒSupporting ‡ °dONLNd
¥¯¿
K)4Apple Event Recor`°dONLNd¥
L¿
`)TdingÑ°dONLNd!¥
t¿
Ü)(3-50ˇb@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*ˇ
¯,Palatino

.
(·*vi4^*¿
¯

k*r
¯4l*r
¯ m*m
¯

ˇ·ˇ‚7^,    Helvetica°dONLNd_*jZ(g*    Chapter 4°dONLNd
\úk˙)rResponding to ‡ °dONLNd\˘k
K)]Apple Events
Y‡°dONLNd&^
`j
m)g4-1°dONLNd+rú~»({ú    Handling `°dONLNd4r…~
)-Apple EventsÎ@°dONLNdBr
~
%)O4-4°dONLNdF¶ã‚(à¶Accepting an Ò¿°dONLNdS‚ã
)<Apple Event醰dONLNd`
.ã
;)L4-5°dONLNddå¶ò
(ï¶Installing Entries in the í¿°dONLNd~å
ò
y)iApple Event Dispatch TŒ °dONLNdîå
xò
é)iablesD¿°dONLNdõå
£ò
∞)+4-7°dONLNdüô∞•≥(¢∞
IfiÄ°dONLNd†ô≥•
;) nstalling Entries for the Requir∏†°dONLNd¿ô
;•
H)àed ø†°dONLNd√ô
H•
É)Apple EventsôÄ°dONLNd—ô
ò•
•)P4-8°dONLNd’¶∞≤
(Ø∞Installing Entries for 7†°dONLNd϶
≤
…)](Apple Events Sent by the Edition ManagerΔ@°dONLNd
¶
›≤
Í)–4-9°dONLNd
≥∞ø»(º∞How øÄ°dONLNd
≥»ø
D)Apple Event Dispatching W#°dONLNd
7≥
Dø
W)|orksW@°dONLNd
=≥
kø
x)'4-9°dONLNd
A¿¶Ã

(…¶Handling the Requirí`°dONLNd
T¿

Ã
)[ed ô`°dONLNd
W¿
Ã
I)Apple Eventss@°dONLNd
e¿
^Ã
k)P4-1:Ä°dONLNd
h¿
kÃ
p)
1°dONLNd
jÕ∞ŸÕ(÷∞RequirE@°dONLNd
pÕŒŸ€)ed L@°dONLNd
sÕ€Ÿ
)Apple Events& °dONLNd
ÅÕ
+Ÿ
8)P4-1Ì`°dONLNd
ÑÕ
7Ÿ
<)
1°dONLNd
Ü⁄∞Ê
(„∞Handling the Open g¿°dONLNd
ò⁄
Ê
X)XApplication Event@°dONLNd
´⁄
mÊ
)e4-14°dONLNd
∞Á∞Û
V(∞!Handling the Open Documents Event~°dONLNd
”Á
kÛ
})ª4-15°dONLNd
ÿÙ∞

T(˝∞"Handling the Print Documents Event˝`°dONLNd
¸Ù
h

z)∏4-17°dONLNd


∞

(

∞Handling the Quit ¸Ä°dONLNd




S)SApplication Eventö°dONLNd&


h

z)e4-19°dONLNd+
¶
“(
¶    Handling `°dONLNd4
”

è)-(Apple Events Sent by the Edition Manager†°dONLNd^

£

µ)–4-20°dONLNdc
∞
'
-(
$∞The Section Read, Section Wh@°dONLNd~

-
'
Ñ)}rite, and Section Scrú†°dONLNdì

Ñ
'
Ø)W
oll Events?@°dONLNdü

ƒ
'
÷)@4-21°dONLNd§
(∞
4¯(
1∞Handling the Cr© °dONLNd≥
(¯
4
R)Heate Publisher EventQ‡°dONLNd…
(
g
4
y)o4-22°dONLNdŒ
5¶
AŸ(
>¶Getting Dat8°dONLNdŸ
5⁄
A
)4
a Out of a¶¿°dONLNd„
5

A
)+n ô¿°dONLNdÂ
5

A
D)Apple Event6†°dONLNdÚ
5
Y
A
k)L4-25°dONLNd˜
B∞
N
(
K∞Getting Data Out of an ô¿°dONLNd
B

N
~)gApple Event ParameterO °dONLNd%
B
ì
N
•)|4-26°dONLNd*
O∞
[
(
X∞Getting Data Out of an ô¿°dONLNdA
O

[
?)g    Attribute[Ä°dONLNdL
O
T
[
f)=4-28°dONLNdQ
\∞
h
S(
e∞%Getting Data Out of a Descriptor ListÊ°dONLNdx
\
g
h
y)∑4-31°dONLNd}
i¶
u∞(
r¶
W¬†°dONLNd~
iØ
u…)    riting JÄ°dONLNdÖ
i 
u
-)Apple Event HandlersáÄ°dONLNdõ
i
A
u
S)w4-33°dONLNd†
v¶
ÇÈ(
¶Replying to an e°dONLNdØ
vÈ
Ç
 )CApple Event
‡°dONLNdº
v
5
Ç
G)L4-36°dONLNd¡
ɶ
è‡(
å¶Disposing of À °dONLNdŒ
ɇ
è
>):Apple Event Data Str»`°dONLNd‚
É
>
è
U)^ucturN@°dONLNdÁ
É
V
è
_)esT‡°dONLNdÎ
É
s
è
Ö)4-39°dONLNd
ê¶
ú∞(
ô¶
W¬†°dONLNdÒ
êØ
ú
)    riting and Installing Coerz°dONLNd
ê

ú
])pcion Handlersπ†°dONLNd
ê
q
ú
É)R4-41°dONLNd
ùú
©ÿ(
¶úInteracting Wù`°dONLNd,
ùÿ
©
)<ith the User7`°dONLNd:
ù
 
©
2)H4-45°dONLNd?
™¶
∂Ù(
≥¶Setting the Client  °dONLNdR
™ı
∂
Ü)O!Application’s User Interaction PrΩ°dONLNds
™
Ü
∂
ñ)ëeferi °dONLNdw
™
ó
∂
Ø)ences{°dONLNd~
™
√
∂
’),4-46°dONLNdÉ
∑¶
√ˆ(
¿¶Setting the Server ¥Ä°dONLNdñ
∑ˆ
√
á)P!Application’s User Interaction PrV`°dONLNd∑
∑
à
√
ò)íeferÄ°dONLNdª
∑
ô
√
±)ences`°dONLNd¬
∑
≈
√
◊),4-48°dONLNd«
Ħ
–
!(
Õ¶Requesting User Interaction˙†°dONLNd‰
ƒ
5
–
G)è4-49°dONLNdÈ
—ú
›≥(
⁄úRefer⁄ °dONLNdÓ
—≥
›
)ence to Responding to "†°dONLNd
—

›
S)eApple Events¸Ä°dONLNd
—
g
›
y)O4-56°dONLNd
ަ
Í…(
Á¶Data Str``°dONLNd
fi 
Í·)$ucturÊ@°dONLNd$
fi·
Í
#)es Used by the l@°dONLNd3
fi
$
Í
Ö)CApple Event Manager °dONLNdH
fi
ö
Í
¨)v4-56°dONLNdM
Î∞
˜˙(
Ù∞Descriptor Recorfi °dONLNd]
Î˙
˜
b)Jds and Related Data Str °dONLNdt
Î
c
˜
z)iucturí°dONLNdy
Î
z
˜
É)esò†°dONLNd}
Î
ó
˜
©)4-56°dONLNdÇ
¯∞Í(
∞Apple Event >Ä°dONLNdé
¯Í
$):Array Data T¥Ä°dONLNdö
¯
#
7)9ypesL`°dONLNd†
¯
L
^))4-60°dONLNd•¶
"(¶Routines for Responding to % °dONLNd¿
"
])|Apple Eventsˇ°dONLNdŒ
q
É)O4-61°dONLNd”∞ª(∞Cr\°dONLNd’ª
,)eating and Managing the ;†°dONLNdÌ
,
ñ)qApple Event Dispatch Tw°dONLNd
ï
´)iables̆°dONLNd

ø
—)*4-61°dONLNd∞+Ë((∞Dispatching S@°dONLNdË+
#)8Apple Events- °dONLNd)
8+
J)P4-66°dONLNd.,∞8
A(5∞ Getting Data or Descriptor Recor˛@°dONLNdN,
A8
G)ë
d°dONLNdO,
H8
m)    s Out of g`°dONLNdX,
m8
t)%
A.†°dONLNdY,
u8
Ô)pple Event Parameters and °dONLNds9∫EÊ(B∫
Attributes~¿°dONLNd9˚E
)A4-68°dONLNdÑF∞R
X(O∞&Counting the Items in Descriptor Lists °dONLNd¨F
mR
)Ω4-74°dONLNd±S∞_¯(\∞Getting Items Frà°dONLNd¡S¯_
N)Hom Descriptor ListsM¿°dONLNd÷S
c_
u)k4-74°dONLNd€`∞l˛(i∞Getting Data and % °dONLNdÏ`ˇl
")OKeyworQÄ°dONLNdÚ`
"l
H)#d-Specifi2°dONLNd˚`
Il
V)'ed ó`°dONLNd˛`
Vl
†)Descriptor RecorıÄ°dONLNd`
†l
¶)J
d@°dONLNd`
ßl
Ã)    s Out of ^†°dONLNd`
Ãl
”)%
A%‡°dONLNd`
‘l
‹)E °dONLNdm∫y”(v∫Recor¢`°dONLNd m”y›)ds˚ °dONLNd$mÒy
)4-78°dONLNd)z∞Ü
+(É∞Requesting User Interaction˙†°dONLNdFz
?Ü
Q)è4-81°dONLNdKá∞ì˜(ê∞Requesting MorYÄ°dONLNdYá˜ì
)Ge T7@°dONLNd\á
ì
W)ime to Respond to Ë°dONLNdná
Vì
ë)RApple Events¡‡°dONLNd|á
¶ì
∏)P4-84°dONLNdÅî∞†
)(ù∞Suspending and Resuming Ì°dONLNdôî
)†
ç)yApple Event Handlingy†°dONLNdØî
¢†
¥)y4-85°dONLNd¥°∞≠
G(™∞"Getting the Sizes and Descriptor T( °dONLNd÷°
G≠
≥)óypes of Descriptor RecorÁÄ°dONLNdÓ°
≥≠
Ω)lds@@°dONLNdÚ°
“≠
‰)4-89°dONLNd˜Æ∞∫
"(∑∞Deleting Descriptor Recor"@°dONLNdÆ
#∫
-)sds{°dONLNdÆ
A∫
S)4-92ˇ‡@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
I (‡
vii4^H¿°dONLNd\Œh
ä(eŒ(Deallocating Memory for Descriptor Recorχ°dONLNd(\
äh
î)ºdsE†°dONLNd,\
©h
ª)4-93°dONLNd1iŒu„(rŒCoerõ °dONLNd5i„u
/)cing Descriptor TJ¿°dONLNdFi
/u
C)Lypes⠡dONLNdLi
Wu
i)(4-94°dONLNdQvŒÇŸ(ŒCr\°dONLNdSvŸÇ
_)eating and Managing the Coerµ °dONLNdov
_Ç
À)Ücion Handler Dispatch TV@°dONLNdÜv
ÀÇ
·)lablesÇ°dONLNdçv
ıÇ)*4-96°dONLNdíÉŒèŸ(åŒCr\°dONLNdîÉŸè
√)2eating and Managing the Special Handler Dispatch TË °dONLNdΔÉ

ÿ)Èables^¿°dONLNdÕÉ
Ìè
ˇ)+4-99°dONLNd“êŒú
)(ôŒGetting Information ãÄ°dONLNdÊê
)ú
W)[
About the `°dONLNdê
Xú
π)/Apple Event Manager«@°dONLNd
ê
Õú
‰)u4-103°dONLNd
ùƒ©
(¶ƒApplication-Defi†°dONLNd
ù
©
H)Jned RoutinesI¿°dONLNd
)ù
]©
t)O4-104°dONLNd
/™∫∂
6(≥∫Summary of Responding to u¿°dONLNd
H™
6∂
q)|Apple EventsO†°dONLNd
V™
Ü∂
ù)P4-108°dONLNd
\∑ƒ√
(¿ƒPascal Summary‡°dONLNd
l∑
"√
9)^4-108°dONLNd
rƒŒ–˙(ÕŒ    ConstantsÆ°dONLNd
}ƒ
–
%)@4-108°dONLNd
É—Œ›Î(⁄ŒData T:`°dONLNd
â—Λˇ)ypes“@°dONLNd
è—
›
 )(4-1ôÄ°dONLNd
í—
 ›
*)12°dONLNd
ïfiŒÍı(ÁŒRoutines≠`°dONLNd
ùfiıÍ
I)' for Responding to % °dONLNd
∞fi
JÍ
Ö)UApple Eventsˇ°dONLNd
æfi
ôÍ
¶)O4-1Δ@°dONLNd
¡fi
¶Í
∞)14°dONLNd
ƒÎŒ˜
(ÙŒApplication-Defi†°dONLNd
‘Î
˜
R)Jned RoutinesI¿°dONLNd
‚Î
g˜
t)O4-1°dONLNd
ÂÎ
t˜
~)18°dONLNd
˯ƒ
˘(

ƒ    C SummaryᆰdONLNd
Û¯


)I4-1N‡°dONLNd
ˆ¯


$)18°dONLNd
˘
Œ
˙(
Œ    ConstantsÆ°dONLNd



)@4-1u@°dONLNd



%)18°dONLNd

Œ
’(
Œ
D=@°dONLNd
÷
Î)ata T:`°dONLNd
Î
ˇ)ypes“@°dONLNd



*)(4-123°dONLNd
Œ
+ı(
(ŒRoutines≠`°dONLNd$
ı
+
I)' for Responding to % °dONLNd7

J
+
Ö)UApple Eventsˇ°dONLNdE

ô
+
∞)O4-124°dONLNdK
,Œ
8
(
5ŒApplication-Defi†°dONLNd[
,

8
R)Jned RoutinesI¿°dONLNdi
,
g
8
~)O4-128°dONLNdo
9ƒ
E
L(
BƒAssembly-Language Summary~†°dONLNdä
9
a
E
x)ù4-128°dONLNdê
FŒ
R‘(
OŒ
T∫¿°dONLNdë
F”
R˚)rap Macr⁄°dONLNdô
F˚
R
)(osåÄ°dONLNdù
F

R
0)4-128°dONLNd£
Sƒ
_˛(
\ƒResult Codesï`°dONLNd±
S

_
))N4-130


èH
ñ4
êH
ñ 
ëH
ë

ˇ·ˇ‚7^,    Helvetica°dONLNd∑
ÉH
éx(
ãH    Chapter 5°dONLNd¡
Ä∫
è
E)rCreating and Sending ˇ‡°dONLNd÷
Ä
D
è
ñ)äApple Events
y†°dONLNd‰
Ç
´
é
∏)g5-1°dONLNdÈ
ñ∫
¢≈(
ü∫Cr\°dONLNdÎ
ñ≈
¢)
eating an #‡°dONLNdı
ñ
¢
')+Apple Event¿¿°dONLNd
ñ
;
¢
H)K5-3°dONLNd
£ƒ
Ø
5(
¨ƒAdding Parameters to an »°dONLNd
£
5
Ø
l)qApple Eventd‡°dONLNd+
£
Å
Ø
é)L5-5°dONLNd/
∞ƒ
º
o(
πƒ&Specifying Optional Parameters for an ÃÄ°dONLNdU
∞
o
º
¶)´Apple Eventi`°dONLNdb
∞
ª
º
»)L5-7°dONLNdf
Ωƒ
…
(
ΔƒSpecifying a TE¿°dONLNdt
Ω

…

)>ar
¿°dONLNdv
Ω

…
)    get «Ä°dONLNdz
Ω

…
1)Addrã@°dONLNd~
Ω
2
…
?)essŒ‡°dONLNdÉ
Ω
S
…
e)!5-10°dONLNdà
 Œ
÷Ÿ(
”ŒCr\°dONLNdä
 Ÿ
÷
)
eating an #‡°dONLNdî
 

÷
)+AddrÁ†°dONLNdò
 

÷
u)ess Descriptor Recor    `°dONLNd¨
 
v
÷
|)[
d% °dONLNdØ
 
ê
÷
ù)5-1Ï`°dONLNd≤
 
ú
÷
°)
1°dONLNd¥
◊Œ
„Â(
‡ŒAddrC¿°dONLNd∏
◊Ê
„
)
essing an C@°dONLNd¬
◊

„
h)+Apple Event for Dir¿°dONLNd’
◊
i
„
≠)Xect Dispatching¥†°dONLNdÊ
◊
¡
„
”)X5-13°dONLNdÎ
‰∫
Ó(
Ì∫Sending an 2`°dONLNdˆ
‰Ó

%)4Apple Eventœ@°dONLNd
‰
9

K)K5-13°dONLNd
Òƒ
˝Û(
˙ƒ    Dealing W+Ä°dONLNd
ÒÛ
˝
)/ith T;¿°dONLNd
Ò

˝
*)imeoutsΩ¿°dONLNd
Ò
>
˝
P)75-20°dONLNd$
˛ƒ
Œ(ƒ
W¬†°dONLNd%
˛Õ

0)    riting an Idle Function°dONLNd>
˛
D

V)w5-21°dONLNdCƒŒ(ƒ
W¬†°dONLNdDÕÁ)    riting ®‡°dONLNdKË
)    a Reply F)@°dONLNdT

G)*ilter Functio¿°dONLNda
G
L)5
n¬ °dONLNdd
a
s)5-24°dONLNdi∫$—(!∫Refer⁄ °dONLNdn—$˝)
ence to CrB‡°dONLNdx˛$
V)-eating and Sending ‡°dONLNdã
U$
ê)WApple Eventsø¿°dONLNdô
•$
∑)P5-24°dONLNdû%ƒ1
(.ƒRoutines for CrE`°dONLNd≠%
1
`)Deating and Sending Ë`°dONLNd¿%
_1
ö)WApple Events¬@°dONLNdŒ%
Ø1
¡)P5-25°dONLNd”2Œ>Ÿ(;ŒCr\°dONLNd’2Ÿ>ˆ)eating “Ä°dONLNd‹2ˆ>
1)Apple Events¨`°dONLNdÍ2
F>
X)P5-25°dONLNdÔ?ŒKŸ(HŒCr\°dONLNdÒ?ŸK
ã)'eating and Duplicating Descriptor Recor‡°dONLNd?
åK
ñ)≥dsg†°dONLNd?
™K
º)5-26°dONLNd!LŒXŸ(UŒCr\°dONLNd#LŸX
R)eating Descriptor Lists and ª‡°dONLNd?L
RX
{)yAE RecorA@°dONLNdGL
|X
Ü)*dsö°dONLNdKL
öX
¨)5-28°dONLNdPYŒe
^(bŒ Adding Items to Descriptor Listsw@°dONLNdrY
se
Ö)•5-29°dONLNdwfŒr
h(oŒ Adding Data and Descriptor RecoríÄ°dONLNdóf
hr
Ä)öds to D¿°dONLNdùf
Är
©)AE Recor  °dONLNd•f
©r
≥))ds"‡°dONLNd©f
»r
⁄)5-32°dONLNdÆsŒ
:(|ŒAdding Parameters and ´‡°dONLNdƒs
:
t)lAttributes to  °dONLNd“s
u
∞);Apple Eventsfi°dONLNd‡s
ƒ
÷)O5-33°dONLNdÂÄŒåÙ(âŒSending ·°dONLNdÌÄÙå
/)&Apple Events∫‡°dONLNd˚Ä
Då
V)P5-37°dONLNdçƒô
(ñƒApplication-Defi†°dONLNdç
ô
)JneĆ°dONLNdç
ô
H)
d RoutinesI¿°dONLNdç
]ô
o)D5-41ˇ0@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*ˇ
¯,Palatino

.
(·*viii4^*¿
¯°dONLNd\úh‡(eúSummary of Crñ°dONLNd\‡h
8)Deating and Sending 9°dONLNd \
8h
s)XApple Events‡°dONLNd.\
àh
ö)P5-44°dONLNd3i¶uÔ(r¶Pascal Summary‡°dONLNdCi
u
)^5-44°dONLNdHv∞Ç‹(∞    ConstantsÆ°dONLNdSvÇ
)@5-44°dONLNdXÉ∞èÕ(å∞Data T:`°dONLNd^ÉÕè·)ypes“@°dONLNddÉıè
)(5-48°dONLNdiê∞ú◊(ô∞Routines≠`°dONLNdqê◊úÛ)' for CrE`°dONLNdxêÙú
L)eating and Sending Ë`°dONLNdãê
Kú
Ü)WApple Events¬@°dONLNdôê
õú
≠)P5-50°dONLNdûù∞©˙(¶∞Application-Defi†°dONLNdÆù˙©
4)Jned RoutinesI¿°dONLNdºù
I©
[)O5-51°dONLNd¡™¶∂€(≥¶    C SummaryᆰdONLNdÙÔ∂

)I5-51°dONLNd—∑∞√◊(¿∞Constantq°dONLNdŸ∑ÿ√‹)(
sÆ°dONLNd‹∑√
)5-51°dONLNd·ƒ∞–Õ(Õ∞Data T:`°dONLNdÁƒÕ–·)ypes“@°dONLNd̃ı–
)(5-56°dONLNdÚ—∞›◊(⁄∞Routines≠`°dONLNd˙—◊›Û)' for CrE`°dONLNd

—Ù›
L)eating and Sending Ë`°dONLNd
—
K›
Ü)WApple Events¬@°dONLNd
"—
õ›
≠)P5-57°dONLNd
'fi∞Í˙(Á∞Application-Defi†°dONLNd
7fi˙Í
4)Jned RoutinesI¿°dONLNd
Efi
IÍ
[)O5-59°dONLNd
Jζ˜
.(Ù¶Assembly-Language Summary~†°dONLNd
eÎ
C˜
U)ù5-59°dONLNd
j¯∞
∂(

∞
T∫¿°dONLNd
k¯µ
›)rap Macr⁄°dONLNd
s¯›
Ê)(osåÄ°dONLNd
w¯˚

)5-59°dONLNd
|
¶
‡(
¶Result Codesï`°dONLNd
ä
Ù

)N5-60


A*
H
¯4
B*
H
¯ 
C*
C
¯

ˇ·ˇ‚7^,    Helvetica°dONLNd
è
5*
@Z(
=*    Chapter 6°dONLNd
ô
2ú
A
á)r$Resolving and Creating Object Specifi6†°dONLNd
æ
2
à
A
Ã)Ï
er Records
®Ä°dONLNd
 
4
‡
@
Ì)X6-1°dONLNd
œ
Hú
T
(
QúResolving Object Specifi)°dONLNd
Á
H

T
+)ker RecorᆰdONLNd
Ô
H
+
T
5)$ds‡`°dONLNd
Û
H
I
T
V)6-4°dONLNd
˜
Uú
aÊ(
^úDescriptor Recorfi °dONLNd
UÊ
a
S)Jds Used in Object Specifiņ°dONLNd 
U
T
a
x)ner Recor‡@°dONLNd(
U
x
a
Ç)$ds9°dONLNd,
U
ó
a
§)6-8°dONLNd0
b¶
n‹(
k¶Object Class؇°dONLNd>
b
n˝)J6-9°dONLNdB
o¶
{“(
x¶    Containerñ@°dONLNdM
oÊ
{Û)@6-9°dONLNdQ
|¶
à—(
Ö¶Key Formf °dONLNd[
|Ê
àÛ)@6-1-`°dONLNd^
|Û
à¯)
1°dONLNd`
â¶
ïœ(
í¶Key DataöÄ°dONLNdj
â„
ïı)=6-12°dONLNdo
ñ∞
¢¸(
ü∞Key Data for a Pr• °dONLNdÄ
ñ¸
¢
&)L    operty IDF@°dONLNdã
ñ
;
¢
M)?6-13°dONLNdê
£∞
Ø
8(
¨∞Key Data for an Object’s NameO °dONLNdØ
£
M
Ø
_)ù6-14°dONLNd¥
∞¶
º
(
π¶Key Data for a Unique Iü‡°dONLNdÀ
∞

º
)i
D] °dONLNdŒ
∞
+
º
=)6-14°dONLNd”
Ω∞
…Í(
Δ∞Key Data for ¯ °dONLNd‡
ΩÍ
…
8):Absolute Positionã °dONLNdÛ
Ω
M
…
_)c6-14°dONLNd¯
 ∞
÷
5(
”∞Key Data for Relative PositionÁ@°dONLNd
 
I
÷
[)ô6-15°dONLNd
װ
„¯(
‡∞Key Data for a T@°dONLNd-
◊¯
„
)HestU@°dONLNd2
◊

„
*) 6-15°dONLNd7
‰∞

(
Ì∞Key Data for a RangeƆ°dONLNdM
‰
"

4)r6-20°dONLNdR
Òú
˝
$(
˙ú!Installing Entries in the Object I@°dONLNds
Ò
$
˝
})àAccessor Dispatch T;@°dONLNdÜ
Ò
}
˝
ì)Yables±‡°dONLNdç
Ò
ß
˝
π)*6-21°dONLNdí
˛¶
(¶Installing Object !°dONLNd§
˛Ò

v)KAccessor Functions That Find 5¿°dONLNd¡
˛
v

–)ÖApple Event ObjectsΔ °dONLNd÷
˛
‰

ˆ)n6-23°dONLNd€¶(¶Installing Object !°dONLNdÌÒ
Ä)KAccessor Functions That Find Prb¿°dONLNd
Ä
£)èoperties»°dONLNd
∑
…)76-27°dONLNdú$¶(!ú
W¬†°dONLNd•$fi)    riting Object 
°dONLNd*fl$
4):Accessor Functions[°dONLNd>
H$
Z)i6-28°dONLNdC%¶1∞(.¶
W¬†°dONLNdD%Ø1Ë)    riting Object 
°dONLNdR%È1
n):Accessor Functions That Find ¿°dONLNdo%
n1
ã)ÖApple @°dONLNdu%
å1
®)Event 2†°dONLNd{%
®1
»)Objects¶ °dONLNdÑ%
‹1
Ó)46-29°dONLNdâ2¶>∞(;¶
W¬†°dONLNdä2Ø>Ë)    riting Object 
°dONLNdò2È>
x):Accessor Functions That Find PrB¿°dONLNd∑2
x>
õ)èoperties®°dONLNd¡2
Ø>
¡)76-37°dONLNdΔ?¶K∏(H¶Defi†°dONLNd ?πK’)ning T„†°dONLNd–?‘KÌ)okens¿@°dONLNd◊?
K
).6-39°dONLNd‹L¶X˘(U¶Handling Whose Ts°dONLNdÏL˘X
    )Sests˘°dONLNdÚL
X
/)$6-41°dONLNd˜Yúe¶(bú
W¬†°dONLNd¯Y•e
3)     riting Object Callback Functions‘†°dONLNdY
Ge
Y)¢6-45°dONLNdf¶r∞(o¶
W¬†°dONLNd fØr
J)    "riting an Object-Counting Function>`°dONLNdDf
_r
q)∞6-48°dONLNdIs¶∞(|¶
W¬†°dONLNdJsØ
W)    $riting an Object-Comparison Function†°dONLNdps
l
~)Ω6-50°dONLNduĶå∞(â¶
W¬†°dONLNdvÄØå
G)    !riting Marking Callback Functionsfi°dONLNdôÄ
[å
m)¨6-53°dONLNdûçúôß(ñúCr\°dONLNd†çßô
)eating Object SpecifiX@°dONLNdµç

ô
%)Zer Recor∂‡°dONLNdΩç
%ô
/)$ds†°dONLNd¡ç
Dô
V)6-55°dONLNdΔö¶¶±(£¶Cr\°dONLNd»ö±¶
3)eating a Simple Object SpecifiÄ°dONLNdÊö
4¶
X)Éer Recorg °dONLNdÓö
X¶
^)$
dLJ°dONLNdÒö
r¶
Ñ)6-57°dONLNdˆß∞≥
<(∞∞Specifying the Container Hierar>†°dONLNdß
=≥
L)çchy`°dONLNdß
a≥
s)$6-61ˇ™@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
, (‡ix4^H¿°dONLNd\Œh
(eŒSpecifying a Prfi†°dONLNd\
h
-)Boperty‰°dONLNd\
Ah
S)16-63°dONLNdiŒu
Q(rŒSpecifying a Relative Position†¿°dONLNd<i
eu
w)ó6-64°dONLNdAvƒÇœ(ƒCr\°dONLNdCvœÇ
[)eating a Complex Object SpecifiïÄ°dONLNdbv
[Ç
)åer RecorÙ °dONLNdjv
Ç
Ö)$
d‡°dONLNdmv
öÇ
¨)6-64°dONLNdrÉŒè
(åŒSpecifying a TE¿°dONLNdÄÉ
è
)>esté¿°dONLNdÖÉ
,è
>) 6-64°dONLNdäêŒú
"(ôŒSpecifying a RangeË °dONLNdûê
6ú
H)h6-72°dONLNd£ù∫©—(¶∫Refer⁄ °dONLNd®ù—©
?)ence to Resolving and Cr1†°dONLNd¿ù
@©
ô)oeating Object Specifi-‡°dONLNd’ù
ö©
æ)Zer RecoråÄ°dONLNd›ù
æ©
»)$dsÂ@°dONLNd·ù
‹©
Ó)6-75°dONLNdÊ™ƒ∂Á(≥ƒData Str``°dONLNdÓ™Ë∂ˇ)$ucturÊ@°dONLNdÛ™ˇ∂
k)es Used in Object Specifi7†°dONLNd
™
l∂
ê)mer Recorñ@°dONLNd
™
ê∂
ö)$dsÔ°dONLNd
™
Æ∂
¿)6-75°dONLNd
∑ƒ√
I(¿ƒRoutines for Resolving and Cr4 °dONLNd
:∑
J√
£)Üeating Object Specifi0`°dONLNd
O∑
§√
»)Zer Recorè°dONLNd
W∑
»√
“)$dsÁ¿°dONLNd
[∑
Ê√
¯)6-77°dONLNd
`ƒŒ–
w(ÕŒ'Initializing the Object Support LibraryÊ@°dONLNd
âƒ
ã–
ù)Ω6-77°dONLNd
é—Œ›
(⁄ŒSetting Object / °dONLNd
ù—
›
Ï)@0Accessor Functions and Object Callback Functions¢°dONLNd
œ—›)Ú6-77°dONLNd
‘fiŒÍ
{(ÁŒ&Getting, Calling, and Removing Object fiÄ°dONLNd
˙fi
{Í
–)≠Accessor Functions8Ä°dONLNdfi
ÂÍ
˜)j6-81°dONLNdÎŒ˜
8(ÙŒResolving Object Specifi)°dONLNd+Î
9˜
])ker RecorᆰdONLNd3Î
]˜
g)$ds‡`°dONLNd7Î
{˜
ç)6-85°dONLNd<¯Œ

F(

ŒDeallocating Memory for TƒÄ°dONLNdU¯
E

^)wokens° °dONLNd\¯
s

Ö).6-87°dONLNda
Œ
Ÿ(
ŒCr\°dONLNdc
Ÿ

2)eating Object SpecifiX@°dONLNdx

3

W)Zer Recor∂‡°dONLNdÄ

W

a)$ds†°dONLNdÑ

v

à)6-88°dONLNdâ
ƒ

(
ƒApplication-Defi†°dONLNdô



)JneĆ°dONLNdõ



9)d Routiq¿°dONLNd¢

:

H)!nesI¿°dONLNdß

]

o)#6-94°dONLNd¨
Œ
+Ï(
(ŒObject ÿ °dONLNd≥
Ï
+
A)Accessor Functions2 °dONLNd«

V
+
h)j6-94°dONLNdÃ
,Œ
8
A(
5ŒObject Callback Functions´¿°dONLNdÁ
,
U
8
g)á6-96°dONLNdÏ
9∫
E
@(
B∫Summary of Resolving and CrÑ¿°dONLNd
9
@
E
ô)Üeating Object SpecifiÅ°dONLNd
9
ö
E
æ)Zer Recorfl†°dONLNd$
9
æ
E
»)$ds8`°dONLNd(
9
›
E
Ù)6-104°dONLNd.
Fƒ
R
(
OƒPascal Summary‡°dONLNd>
F
"
R
9)^6-104°dONLNdD
SŒ
_˙(
\Œ    ConstantsÆ°dONLNdO
S

_
%)@6-104°dONLNdU
`Œ
lÎ(
iŒData T:`°dONLNd[
`Î
lˇ)ypes“@°dONLNda
`

l
*)(6-106°dONLNdg
mŒ
yı(
vŒRoutines≠`°dONLNdo
mı
y
S)' for Resolving and Cr4 °dONLNdÑ
m
T
y
≠)_eating Object Specifi0`°dONLNdô
m
Æ
y
“)Zer Recorè°dONLNd°
m
“
y
‹)$dsÁ¿°dONLNd•
m

y)6-106°dONLNd´
zŒ
Ü’(
Ɍ
AG@°dONLNd¨
z÷
Ü
)pplication-Defi†°dONLNdª
z

Ü
N)Bned Routine¿°dONLNdΔ
z
O
Ü
S)7
sI¿°dONLNd…
z
g
Ü
~)6-108°dONLNdœ
áƒ
ìÛ(
êƒC Summar¯Ä°dONLNd◊
áÛ
ì¯)/
yᆰdONLNd⁄
á

ì
$)6-109°dONLNd‡
îŒ
†ı(
ùŒConstantq°dONLNdË
îˆ
†˙)(
sÆ°dONLNdÎ
î

†
%)6-109°dONLNdÒ
°Œ
≠Î(
™ŒData T:`°dONLNd˜
°Î
≠ˇ)ypes“@°dONLNd˝
°

≠
 )(6-1ôÄ°dONLNd
°
 
≠
%)
1‡°dONLNd

°
%
≠
*)
1°dONLNd
ƌ
∫ı(
∑ŒRoutines≠`°dONLNd
Æı
∫
S)' for Resolving and Cr4 °dONLNd 
Æ
T
∫
≠)_eating Object Specifi0`°dONLNd5
Æ
Æ
∫
“)Zer Recorè°dONLNd=
Æ
“
∫
‹)$dsÁ¿°dONLNdA
Æ

∫
˝)6-1Ø°dONLNdD
Æ
˝
∫)12°dONLNdG
ªŒ
«’(
ƒŒ
AG@°dONLNdH
ª÷
«
)pplication-Defi†°dONLNdW
ª

«
N)Bned Routine¿°dONLNdb
ª
O
«
S)7
sI¿°dONLNde
ª
g
«
t)6-1°dONLNdh
ª
t
«
~)14°dONLNdk
»ƒ
‘
L(
—ƒAssembly-Language Summary~†°dONLNdÜ
»
a
‘
n)ù6-1E‡°dONLNdâ
»
n
‘
x)15°dONLNdå
’Œ
·‘(
fiŒ
T∫¿°dONLNdç
’”
·˚)rap Macr⁄°dONLNdï
’˚
·
)(osåÄ°dONLNdô
’

·
&)6-1S¿°dONLNdú
’
&
·
0)15°dONLNdü
‚ƒ
Ó˛(
΃Result Codesï`°dONLNd≠
‚

Ó
)N6-1\†°dONLNd∞
‚

Ó
))15

H%4H%  H 

ˇ·ˇ‚7^,    Helvetica°dONLNd≥Hx(H    Chapter 7°dONLNdΩ∫
M)rIntroduction to Scripting
ᇰdONLNdÿ
a
n)ß7-1°dONLNd›%∫1
o(.∫&About Scripts and Scripting Componentsc¿°dONLNd%
Ñ1
ë) 7-4°dONLNd    2ƒ>
F(;ƒScript Editors and Script Filesz°dONLNd*2
[>
h)ó7-6°dONLNd.?ƒK
k(Hƒ$Scripting Components and Scriptable Ù °dONLNdR?
kK
ü)ßApplicationr@°dONLNd]?
†K
§)5
sØ@°dONLNd`?
∏K
≈)7-8°dONLNddLƒX
=(UƒScripting Components and k°dONLNd}L
=X
“)y!Applications That Execute ScriptsxÄ°dONLNd†L
ÊX
Û)©7-1?¿°dONLNd£L
ÛX
¯)
1°dONLNd•Y∫efi(b∫Making †°dONLNd¨YfleÂ)%
Y‡ °dONLNd≠Y‰eı)our q°dONLNd±Yˆe
Y)Application Scriptablex@°dONLNd…Y
me
)w7-14°dONLNdŒfƒr‚(oƒAbout ØÄ°dONLNd‘f‚r
")Apple Event T °dONLNd·f
"r
v)@erminology Resour¥°dONLNdÚf
vr
É)Tces*‡°dONLNd˜f
òr
™)"7-15°dONLNd¸sŒÊ(|ŒHow øÄ°dONLNdsÊ
;)AppleScript Uses TM °dONLNds
;
•)Uerminology Information:@°dONLNd*s
∫
Ã)7-17°dONLNd/ÄŒå
1(âŒDynamic Loading of T?`°dONLNdCÄ
1å
õ)cerminology Information,Ä°dONLNd[Ä
∞å
¬)7-20°dONLNd`ç∫ôfi(ñ∫Making †°dONLNdgçflôÂ)%
Y‡ °dONLNdhç‰ôı)our q°dONLNdlçˆô
F)Application RecorëÄ°dONLNd}ç
Fô
Y)Pdabl@°dONLNdÅç
Zô
^)
eʇ°dONLNdÑç
rô
Ñ)7-20°dONLNdâö∫¶
Y(£∫"Manipulating and Executing Scripts∂ °dONLNd≠ö
m¶
)≥7-22°dONLNd≤߃≥À(∞ƒ
Có°dONLNd≥ßÀ≥¯)
ompiling, ¸@°dONLNdΩ߯≥
)-Saving, + °dONLNd≈ß
≥
´)$Modifying, and Executing Script °dONLNd‰ß
¨≥
∞)ê
sP °dONLNdÁß
ij
÷)7-24°dONLNdÏ¥ƒ¿˛(ΩƒUsing a ScripZ@°dONLNd˘¥ˇ¿
-);t Context t≥‡°dONLNd¥
-¿
e).o Handle an ‡°dONLNd¥
f¿
ù)9Apple Event©¿°dONLNd¥
±¿
√)K7-25ˇ¢@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*ˇ
¯,Palatino

.
(·*
x4^*¿
¯

k*r
¯4l*r
¯ m*m
¯

ˇ·ˇ‚7^,    Helvetica°dONLNd_*jZ(g*    Chapter 8°dONLNd
\úkÎ)rApple Event ù†°dONLNd\ÎkÛ)O
Tù†°dONLNd\Úk
})erminology Resources
ÿ¿°dONLNd-^
ëj
û)ü8-1°dONLNd2rú~Æ({úDefi†°dONLNd6rØ~À)ning T„†°dONLNd<r ~
@)erminology for Use by the 懰dONLNdVr
@~
¨)vAppleScript Component¿°dONLNdmr
¡~
Œ)Å8-3°dONLNdqúã®(àúStr‡¿°dONLNdt®ãø)ucturf†°dONLNdy¿ã“)e of õ@°dONLNd~“ã
)Apple Event Ṫ°dONLNdã
ã
e)?erminology Resourü¿°dONLNdú
fã
s)Uces†°dONLNd°
àã
ï)"8-8°dONLNd•åúòß(ïúCr\°dONLNdßåßò“)
eating an #‡°dONLNd±å“ò
)+Apple Event TvÄ°dONLNdæå
ò
ì)?erminology Extension Resour6`°dONLNdŸå
îò
ù)Écep@°dONLNd›å
±ò
√)8-13°dONLNd‚ô¶•˝(¢¶Supporting Standarr¿°dONLNdÙô˝•
,)W
d Suites Wz °dONLNd˛ô
,•
y)/ithout ExtensionsÄ@°dONLNd
ô
ç•
ü)a8-14°dONLNd
¶¶≤
(ضExtending the Standar°dONLNd
+¶
    ≤
,)cd Suites,°dONLNd
5¶
@≤
R)78-16°dONLNd
:≥¶ø
$(º¶Supporting Subsets of Suites‘†°dONLNd
X≥
8ø
J)í8-23°dONLNd
]¿¶Ã
(…¶Supporting New Suites¶@°dONLNd
t¿
!Ã
3){8-23°dONLNd
yÕúŸÎ(÷úHandling the Get õ‡°dONLNd
äÕΟ
!)O
AETE Event⁄¿°dONLNd
ñÕ
5Ÿ
G)J8-23°dONLNd
õ⁄úÊ≥(„úRefer⁄ °dONLNd
†⁄≥ÊÃ)ence tq`°dONLNd
¶⁄ÕÊ‘)o Ä°dONLNd
®⁄’Ê‹)
Aœ¿°dONLNd
©⁄‹Ê
)    pple Evenc°dONLNd
≤⁄
    Ê
)-t T[ °dONLNd
µ⁄
Ê
h)erminology Resour°dONLNd
Δ⁄
iÊ
v)Ucesɇ°dONLNd
À⁄
äÊ
ú)!8-26°dONLNd
–Á¶Û˝(¶Header Data for an °†°dONLNd
„Á˝Û
=)WApple Event TÙ@°dONLNd
Á
<Û
ê)?erminology Resour¶ °dONLNd
Á
ëÛ
ö)Uce‡°dONLNdÁ
ÆÛ
¿)8-27°dONLNd
Ù¶
∑(˝¶SuitÒ†°dONLNdÙ∑
Ú)e Data for an ȇ°dONLNdÙÚ

&);
Apple EvenD`°dONLNd&Ù
'

2)5t T<Ä°dONLNd)Ù
2

Ü)erminology ResourÓ`°dONLNd:Ù
Ü

è)Tce(@°dONLNd>Ù
§

∂)8-27°dONLNdC

∞
∂(

∞
Eõ¿°dONLNdD

∂
Δ)ven›°dONLNdG

Δ
‡)t Dataü°dONLNdO

ı

)/8-29°dONLNdT
∞
·(
∞Object Clasr‡°dONLNd_
‚
˝)2s Data/Ä°dONLNdg



$)08-36°dONLNdl
∞
'
)(
$∞Comparison Operator DataÖ‡°dONLNdÜ

=
'
O)ç8-42°dONLNdã
(∞
4‰(
1∞
Enumeratio§¿°dONLNdï
(‰
4
L)4n and Enumerator Data‡°dONLNd¨
(
a
4
s)}8-43°dONLNd±
5¶
A
(
>¶The Scripting Size Resourº °dONLNd 
5

A
 )qceˆ°dONLNdŒ
5
4
A
F)8-45


q*
x
¯4
r*
x
¯ 
s*
s
¯

ˇ·ˇ‚7^°dONLNd”
e*
pZ(
m*    Chapter 9°dONLNd›
bú
qfl)r
Recording h °dONLNdÁ
bfl
q
1)CApple Events
·‡°dONLNdı
d
E
p
R)f9-1°dONLNd˙
xú
Ñ”(
ÅúAbout Recor0@°dONLNd
x‘
ÑÓ)8dable ß@°dONLNd
xÓ
Ñ
")Application%`°dONLNd
x
#
Ñ
')5
sb`°dONLNd
x
;
Ñ
H)9-3°dONLNd
Öú
ë»(
éú
Factoring ≈ °dONLNd'
Ö»
ëŒ),
YÖ†°dONLNd(
֌
ëfl)our Ä°dONLNd,
Ö‡
ë
?)Application for Recors°dONLNdA
Ö
?
ë
S)_ding◊†°dONLNdG
Ö
g
ë
t)(9-6°dONLNdK
í¶
û´(
õ¶
F °dONLNdL
í¨
û
ñ)-actoring the Quit Command and the New Command[ °dONLNd{
í
™
û
∑)˛9-6°dONLNd
ü¶
´Ã(
®¶Sending ·°dONLNdá
üÃ
´
)&Apple Events WÆ@°dONLNdï
ü

´
y)Hithout Executing Them    ¿°dONLNd¨
ü
é
´
†)z9-12°dONLNd±
¨ú
∏€(
µúWhat to Recorn°dONLNdæ
¨€
∏·)?
dâ¿°dONLNd¡
¨ı
∏
)9-14°dONLNdΔ
π¶
Ŭ(
¦
R.°dONLNd«
π≠
≈ø)ecor¢`°dONLNdÀ
πø
≈Ì)
ding User i °dONLNd’
πÌ
≈
).ActionsO@°dONLNdfi
π
#
≈
5)69-15°dONLNd„
Δ¶
“ø(
œ¶Recor¢`°dONLNdË
Δø
“
!)ding the Selection of TÄ¿°dONLNdˇ
Δ
!
“
Q)bext Objects®‡°dONLNd
Δ
e
“
w)D9-18°dONLNd
Ӧ
flø(
‹¶Recor¢`°dONLNd
”ø
fl
)ding Insertion PointsZ°dONLNd-
”
0
fl
B)q9-23°dONLNd2
‡¶
Ïø(
ȶRecor¢`°dONLNd7
‡ø
Ï‹)ding T¡¿°dONLNd=
‡€
ÏÙ)ypingõ‡°dONLNdD
‡
    
Ï
).9-27°dONLNdI
̶
˘ø(
ˆ¶Recor¢`°dONLNdN
Ìø
˘
b)%ding the Selection of Nontext ObjectsK@°dONLNdu
Ì
w
˘
â)∏9-30°dONLNdz
˙¶˙(¶Identifying Objectsfl`°dONLNdè
˙

 )h9-32°dONLNdî¶
A(¶!Moving the Selection During Recorˆ¿°dONLNdµ
A
O)õdinÃ@°dONLNd∏
P
U)
g[`°dONLNdª
j
|)9-34°dONLNd¿¶ ø(¶Recor¢`°dONLNd≈ø 
)ding Interactions W«¿°dONLNdÿ
 
^)With Dialog Boxes°dONLNdÍ
s 
Ö)]9-35°dONLNdÔ!ú-¥(*úHow øÄ°dONLNdÛ!¥-
)Apple Event Recor˛¿°dONLNd!
-
')Sding W¯`°dONLNd
!
'-
:) orks,†°dONLNd!
O-
a)(9-35

]*d
¯4^*d
¯ _*_
¯

ˇ·ˇ‚7^°dONLNdQ*\`(Y*
Chapter 10°dONLNd Nú]
%)rScripting Components
0Ä°dONLNd6P
:\
L)û10-1°dONLNd<dúp
C(mú#Connecting to a Scripting ComponentÀÄ°dONLNdad
Wp
i)ª10-3°dONLNdfqú}
A(zú"Using Scripting Component Routines¿°dONLNdäq
V}
h)∫10-7°dONLNdè~¶ä
.(á¶Compiling and Executing Sour˚`°dONLNd´~
.ä
N)àce Data¥‡°dONLNd¥~
cä
u)510-7°dONLNdπã¶ó˜(î¶Saving Script Data~°dONLNdÕã
ó
#)f10-12°dONLNd”ò∞§
;(°∞Storage Formats for Script Dataò¿°dONLNdÙò
O§
f)ü10-12°dONLNd˙•∞±œ(Æ∞Resourv@°dONLNd•œ±
)ce and File TÅÄ°dONLNd•
±
])7ypes for Script Data$Ä°dONLNd#•
r±
â)l10-13ˇ÷@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
, (‡xi4^H¿°dONLNd\ƒh
^(eƒ!Loading and Executing Script DataB¿°dONLNd#\
sh
ä)Ø10-14°dONLNd)iƒu
ì(rƒ+Modifying and Recompiling a Compiled Script=@°dONLNdVi
®u
ø)‰10-17°dONLNd\vƒÇ
e(ƒ$Using a Script Context to Handle an ‡°dONLNdÄv
fÇ
ù)¢Apple Event©¿°dONLNdçv
±Ç
»)K10-19°dONLNdìɃè…(åƒ
Sø¿°dONLNdîÉ…è
r)#upplying a Resume Dispatch Functionó °dONLNdπÉ
áè
û)æ10-21°dONLNdøêƒú

(ôƒSupplying an ˛Ä°dONLNdÃê

ú
5)=Alternative :`°dONLNdÿê
6ú
|)5Active Function÷°dONLNdÈê
êú
ß)Z10-23°dONLNdÔùƒ©Ù(¶ƒ
Supplying ≠ °dONLNd˘ùÙ©
3)0Alternative Cr#`°dONLNd
ù
4©
ü)@eate and Send Functions„ °dONLNd
 ù
≥©
 )10-24°dONLNd
&™Œ∂
(≥ŒAlternative Crˆ@°dONLNd
4™
∂
L)?eate Functions“`°dONLNd
D™
a∂
x)T10-24°dONLNd
J∑Œ√
F(¿ŒAlternative Send Functions@°dONLNd
f∑
[√
r)ç10-25°dONLNd
lƒƒ–›(ÕƒRecor¢`°dONLNd
qƒ›–
)ding ScriptsìÄ°dONLNd
ƒ
&–
=)I10-26°dONLNd
Ö—∫›ƒ(⁄∫
W¬†°dONLNd
Ü—√›
D)    riting a Scripting ComponentH °dONLNd
§—
Y›
p)ñ10-27°dONLNd
™fi∫Í
7(Á∫Scripting Components Refer∂`°dONLNd
ƒfi
7Í
J)}enceã@°dONLNd
 fi
_Í
v)(10-28°dONLNd
–΃˜Á(ÙƒData Str``°dONLNd
ÿ΢ˇ)$ucturÊ@°dONLNd
›Îˇ˜
)esχ°dONLNd
·Î
˜
3)10-29°dONLNd
Á¯ƒ
·(

ƒRequirE@°dONLNd
̯‚

x)ed Scripting Component Routinesw@°dONLNd¯
å

£)™10-30°dONLNd
Œ

Z(
ŒSaving and Loading Script Dataa°dONLNd4

o

Ü)°10-30°dONLNd:
Œ

h(
Œ"Executing and Disposing of Scripts3¿°dONLNd^

}

î)Ø10-33°dONLNdd
Œ
+
w(
(Œ&Setting and Getting Script Information}Ä°dONLNdå

å
+
£)æ10-41°dONLNdí
,Œ
8
(
5ŒManipulating the ™‡°dONLNd£
,

8
c)OActive FunctionFÄ°dONLNd¥
,
x
8
è)[10-45°dONLNd∫
9ƒ
E
v(
Bƒ%Optional Scripting Component Routines†°dONLNd·
9
ã
E
¢)«10-46°dONLNdÁ
FŒ
R
(
OŒCompiling Scriptsà¿°dONLNd˙
F
2
R
I)d10-47°dONLNd
SŒ
_
(
\ŒGetting Sourπ¿°dONLNd
S

_
&)8ce Datas@°dONLNd
S
;
_
R)510-51°dONLNd
`Œ
l„(
iŒCoerõ °dONLNd
`„
l
)cing Script Vp‡°dONLNd,
`

l
1)8aluesg°dONLNd3
`
F
l
])+10-52°dONLNd9
mŒ
y
((
vŒManipulating the CrÂ@°dONLNdL
m
(
y
ì)Zeate and Send Functions•°dONLNde
m
®
y
ø)Ä10-55°dONLNdk
zŒ
ÜÁ(
ÉŒRecor¢`°dONLNdp
zÁ
Ü
)ding ScriptsìÄ°dONLNd~
z
0
Ü
G)I10-59°dONLNdÑ
áŒ
ì
P(
êŒExecuting Scripts in One Step†°dONLNd£
á
e
ì
|)ó10-61°dONLNd©
îŒ
†◊(
ùŒ
Mı@°dONLNd™
î◊
†
/)    anipulating DialectsÛ °dONLNd¿
î
D
†
[)m10-67°dONLNdΔ
°Œ
≠
_(
™Œ Using Script Contexts to Handle xÄ°dONLNdÊ
°
_
≠
ö)ëApple EventsR`°dONLNdÙ
°
Ø
≠
Δ)P10-71°dONLNd˙
ƃ
∫
Z(
∑ƒAppleScript Component RoutinesÅ@°dONLNd
Æ
n
∫
Ö)™10-80°dONLNd 
ªŒ
«
(
ƒŒInitializing ˛@°dONLNd-
ª

«
5)2AppleScriptK@°dONLNd:
ª
J
«
a)J10-80°dONLNd@
»Œ
‘
f(
—Œ#Getting and Setting Styles for Sour: °dONLNdc
»
g
‘
á)ôce DataÛ†°dONLNdl
»
õ
‘
≤)410-82°dONLNdr
’ƒ
·
m(
fiƒ#Generic Scripting Component Routine‡†°dONLNdï
’
m
·
q)©
s†°dONLNdò
’
Ü
·
ù)10-84°dONLNdû
‚Œ
Ó
π(
ÎŒ3Getting and Setting the Default Scripting Component¿°dONLNd”
‚
Œ
Ó
Â(
Î
Œ10-86°dONLNdŸ
Ԍ
˚
@(
¯ŒUsing Component-Specifiò¿°dONLNd
Ô
@
˚
n)r
c Routines∂`°dONLNd¸
Ô
Ç
˚
ô)B10-87°dONLNd
¸ƒ
x(ƒ%Routines Used by Scripting Componentsä°dONLNd)
¸
å
£)»10-92°dONLNd/    Œ
(ŒManipulating Tʆ°dONLNd=    

“)D,railers for Generic Storage Descriptor RecorQ`°dONLNdi    
”
›)¡ds™ °dONLNdm    
Ò)10-92°dONLNdsƒ"
(ƒApplication-Defi†°dONLNdÉ
"
)JneĆ°dONLNdÖ
"
H)
d RoutinesI¿°dONLNdë
]"
t)D10-94°dONLNdó#∫/ø(,∫
Sø¿°dONLNdò#ø/
V)ummary of Scripting Components@°dONLNd∏#
k/
Ç)¨10-99°dONLNdæ0ƒ<
(9ƒPascal Summary‡°dONLNdŒ0
"<
9)^10-99°dONLNd‘=ŒI˙(FŒ    ConstantsÆ°dONLNdfl=
I
%)@10-99°dONLNdÂJŒVÎ(SŒData T:`°dONLNdÎJÎV˚)ypeï@°dONLNdÓJ˚Vˇ)
s“@°dONLNdÒJ
V
/)10-105°dONLNd¯WŒcÎ(`ŒRequirE@°dONLNd˛WÏc
Ç)ed Scripting Component Routinesw@°dONLNdW
ñc
≤)™10-106°dONLNd&dŒp
Ä(mŒ%Optional Scripting Component Routines†°dONLNdMd
ïp
±)«10-107°dONLNdTqŒ}
d(zŒAppleScript Component RoutinesÅ@°dONLNdtq
x}
ä)™10-1HÄ°dONLNdxq
ä}
î)10°dONLNd{~Œä
w(áŒ#Generic Scripting Component Routine‡†°dONLNdû~
wä
{)©
s†°dONLNd°~
êä
¢)10-1‰‡°dONLNd•~
°ä
´)10°dONLNd®ãŒó
}(îŒ$Routines Used by Scripting ComponentM°dONLNdÃã
~ó
Ç)∞
sä°dONLNdœã
ñó
®)10-1Q@°dONLNd”ã
®ó
≠)
1ƒ†°dONLNd‘ã
¨ó
±)
1°dONLNd÷òŒ§’(°Œ
AG@°dONLNd◊ò÷§
)pplication-Defi†°dONLNdÊò
§
")BneĆ°dONLNdËò
#§
R)
d RoutinesI¿°dONLNdÙò
g§
y)D10-1°dONLNd¯ò
y§
~)
1Ñ`°dONLNd˘ò
}§
Ç)
1ˇT@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*ˇ
¯,Palatino

.
(·*xii4^*¿
¯°dONLNd\¶h€(e¶    C SummaryᆰdONLNd\Ôh

)I10-1N‡°dONLNd\

h
)12°dONLNdi∞u‹(r∞    ConstantsÆ°dONLNdiu
)@10-1u@°dONLNd!i
u
)12°dONLNd$v∞Ç∑(∞
D=@°dONLNd%v∏ÇÕ)ata T:`°dONLNd*vÕÇ›)ypeï@°dONLNd-v›Ç·)
s“@°dONLNd0vıÇ
)10-1ôÄ°dONLNd4v
Ç
)18°dONLNd7É∞èÕ(å∞RequirE@°dONLNd=ÉŒè
d)ed Scripting Component Routinesw@°dONLNd^É
xè
ä)™10-1>Ä°dONLNdbÉ
äè
î)19°dONLNdeê∞ú
b(ô∞%Optional Scripting Component Routines†°dONLNdåê
wú
ì)«10-120°dONLNdìù∞©
F(¶∞AppleScript Component RoutinesÅ@°dONLNd≥ù
Z©
v)™10-123°dONLNd∫™∞∂
Y(≥∞#Generic Scripting Component Routine‡†°dONLNd›™
Y∂
])©
s†°dONLNd‡™
r∂
é)10-123°dONLNdÁ∑∞√
_(¿∞$Routines Used by Scripting ComponentM°dONLNd
∑
`√
d)∞
sä°dONLNd
∑
x√
î)10-124°dONLNd
İз(Ͱ
AG@°dONLNd
ƒ∏–˙)pplication-Defi†°dONLNd
%ƒ˙–
)BneĆ°dONLNd
'ƒ
–
4)
d RoutinesI¿°dONLNd
3ƒ
I–
e)D10-124°dONLNd
:—¶›‡(⁄¶Result Codesï`°dONLNd
H—Ù›
)N10-125


*

¯4
*

¯ 
*

¯

ˇ·ˇ‚7^,    Helvetica°dONLNd
O

*
Z(
    *    Chapter 1˛p°dONLNd
X

Y
_)/
1°dONLNd
Z˛ú

å)C"Program-to-Program Communications ë`°dONLNd
|˛
å

î)
Të`°dONLNd
}˛
ì

º)oolbox
Œ@°dONLNd
Ö

–

’)=
1A†°dONLNd
Ü

’

‚)1-1°dONLNd
ã
ú
 Ê(
úAbout the PPC TK@°dONLNd
ö
Ê
 
)JoolboxD`°dONLNd
¢


 
)2
1∑¿°dONLNd
£


 
))1-4°dONLNd
ß
!¶
-
D(
*¶#Ports, Sessions, and Message BlocksÄ°dONLNd
Ã
!
Y
-
^)≥
1à‡°dONLNd
Õ
!
]
-
j)1-4°dONLNd
—
.¶
:◊(
7¶Setting Up ¬°dONLNd
‹
.◊
:
=)1Authenticated SessionsqÄ°dONLNd
Ù
.
R
:
W){
1‰‡°dONLNd
ı
.
V
:
c)1-6°dONLNd
˘
;ú
G‰(
DúUsing the PPC TäÄ°dONLNd
;‰
G

)HoolboxɆ°dONLNd
;

G
)2
1˜°dONLNd
;

G
,)1-10°dONLNd
H¶
T¡(
Q¶PPC T`°dONLNd
H¡
T
<)oolbox Calling Conventions◊Ä°dONLNd7
H
P
T
U)è
1J‡°dONLNd8
H
U
T
g)1-14°dONLNd=
U¶
a
i(
^¶(Specifying Port Names and Location Names˜`°dONLNdg
U
}
a
Ç)◊
1j¿°dONLNdh
U
Ç
a
î)1-17°dONLNdm
b∞
nÛ(
k∞Opening a Portˆ°dONLNd}
b

n
)W
1i`°dONLNd~
b

n
)1-20°dONLNdÉ
o∞
{∫(
x∞Br`¿°dONLNdÖ
o∫
{
<)
owsing for Ports Using the PrŸ`°dONLNd¢
o
<
{
±)Çogram Linking Dialog Box†°dONLNdº
o
Δ
{
À)ä
1í°dONLNdΩ
o
 
{
‹)1-22°dONLNd¬
|∞
à
(
Ö∞Obtaining a List of °dONLNd÷
|

à
)U
AÛ@°dONLNd◊
|

à
G)vailable Ports°dONLNdÁ
|
\
à
a)Q
1à`°dONLNdË
|
`
à
r)1-27°dONLNdÌ
â¶
ïØ(
í¶PrN†°dONLNdÔ
â∞
ï
)
eparing for a SessionDÄ°dONLNd
â
 
ï
%)p
1∑‡°dONLNd
â
$
ï
6)1-29°dONLNd
ñ∞
¢
(
ü∞Initiating a PPC Session´ °dONLNd&
ñ
-
¢
2)}
1Ä°dONLNd'
ñ
2
¢
D)1-29°dONLNd,
£∞
Ø
((
¨∞Receiving Session RequestsYÄ°dONLNdH
£
=
Ø
B)ç
1Ç°dONLNdI
£
A
Ø
S)1-35°dONLNdN
∞∞
º
a(
π∞'Accepting or Rejecting Session Requests ‡°dONLNdw
∞
u
º
z)≈
1>@°dONLNdx
∞
z
º
å)1-37°dONLNd}
Ω¶
…
T(
Δ¶$Exchanging Data During a PPC Session¿°dONLNd£
Ω
i
…
n)√
1 °dONLNd§
Ω
m
…
)1-39°dONLNd©
 ∞
÷¯(
”∞Reading Data Fr∞°dONLNd∏
 ¯
÷
)Hom an lÄ°dONLNdæ
 

÷
J)Application͆°dONLNdÀ
 
^
÷
c)H
1^°dONLNdÃ
 
c
÷
u)1-40°dONLNd—
װ
„
(
‡∞Sending Data to an ȇ°dONLNd‰
◊

„
:)VApplicationh°dONLNdÒ
◊
O
„
T)I
1€`°dONLNdÚ
◊
S
„
e)1-42°dONLNd˜
‰¶

E(
̶#Ending a Session and Closing a Port `°dONLNd
‰
Z

_)¥
1ì¿°dONLNd
‰
^

p)1-43°dONLNd"
Ò¶
˝˜(
˙¶Invalidating UsersK`°dONLNd6
Ò

˝
)f
1æ¿°dONLNd7
Ò

˝
")1-44°dONLNd<
˛ú
∑(úPPC T`°dONLNdA
˛∑
Ô)oolbox Refer3@°dONLNdM
˛Ô

)8ence °dONLNdS
˛


)(
1{Ä°dONLNdT
˛


-)1-46°dONLNdY¶…(¶Data Str``°dONLNda ·)$ucturÊ@°dONLNdf·Í)esχ°dONLNdj˛
)
1`@°dONLNdk

)1-46°dONLNdp∞$fl(!∞    The PPC Tõ¿°dONLNdyfi$
A).oolbox Parameter Bloc@°dONLNdé
B$
G)d
k¶`°dONLNdë
[$
`)
1¿°dONLNdí
`$
r)1-46°dONLNdó%∞1∂(.∞
T†¿°dONLNdò%∂1
)he PPC Port RecorºÄ°dONLNd©%
1
)Q
dÿ@°dONLNd¨%
!1
&)
1K†°dONLNd≠%
&1
8)1-48°dONLNd≤2∞>
"(;∞The Location Name Recor=¿°dONLNd…2
#>
))s
dYÄ°dONLNdÃ2
=>
B)
1Ç°dONLNdÕ2
A>
S)1-49°dONLNd“?∞K
)(H∞The Port Information Recor√¿°dONLNdÏ?
)K
/)y
dflÄ°dONLNdÔ?
CK
H)
1R‡°dONLNd?
HK
Z)1-50°dONLNdıL¶X¨(U¶
P↰dONLNdˆL¨X¡)PC T`°dONLNd˙L¡X
)oolbox RoutinesÄ°dONLNdL
X
")\
1y‡°dONLNdL
!X
3)1-50°dONLNdY∞e
(b∞Initializing the PPC Tö°dONLNd'Y
e
+)^oolboxì °dONLNd/Y
@e
E)2
1Ä°dONLNd0Y
Ee
W)1-51°dONLNd5f∞rÁ(o∞Using the Pry °dONLNdAfÁr
\)7ogram Linking Dialog Boxæ`°dONLNd[f
pr
u)â
11¿°dONLNd\f
ur
á)1-51°dONLNdas∞
(|∞Obtaining a List of PortsfÄ°dONLNd|s
0
5)Ä
1Ÿ‡°dONLNd}s
4
F)1-54°dONLNdÇÄ∞å
+(â∞Opening and Closing a Port›‡°dONLNdûÄ
?å
D)è
1Q@°dONLNdüÄ
Då
V)1-56°dONLNd§ç∞ô
3(ñ∞Starting and Ending a SessionqÄ°dONLNd√ç
Hô
M)ò
1‰‡°dONLNdƒç
Lô
^)1-59°dONLNd…ö∞¶‡(£∞Receiving, ™†°dONLNd‘ö‡¶
x)0"Accepting, and Rejecting a Session\†°dONLNd¯ö
ç¶
í)≠
1–°dONLNd˘ö
ë¶
£)1-66°dONLNd˛ß∞≥Ù(∞∞Reading and Wå°dONLNdßÙ≥
#)Driting Dataq‡°dONLNdß
8≥
=)D
1Â@°dONLNdß
<≥
N)1-71°dONLNd¥∞¿
É(Ω∞/Locating a Default User and Invalidating a UserU`°dONLNdO¥
ò¿
ù)Ë
1»¿°dONLNdP¥
ú¿
Æ)1-75ˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
Ñ`(‡xiii4^H¿°dONLNd\ƒh
(eƒApplication-Defi†°dONLNd\
h
H)Jned RoutinesI¿°dONLNd\
]h
b)O
1Ω °dONLNd\
ah
s)1-77°dONLNd$iŒu
Y(rŒCompletion Routines for PPC TO†°dONLNdAi
Yu
†)ãoolbox Routinesˆ °dONLNdRi
¥u
π)[
1iÄ°dONLNdSi
πu
À)1-77°dONLNdXvŒÇ
((ŒPort Filter Functions °dONLNdov
=Ç
B)o
1åÄ°dONLNdpv
AÇ
S)1-78°dONLNduÉ∫èø(å∫
Sø¿°dONLNdvÉøè
)ummary of the PPC T˜`°dONLNdâÉ
è
;)_oolboxÄ°dONLNdëÉ
Pè
U)2
1c‡°dONLNdíÉ
Uè
g)1-80°dONLNdóêƒú
(ôƒPascal Summary‡°dONLNdßê
"ú
')^
1É@°dONLNd®ê
&ú
8)1-80°dONLNd≠ùŒ©˙(¶Œ    ConstantsÆ°dONLNd∏ù
©
)@
1!`°dONLNdπù
©
%)1-80°dONLNd晌∂Î(≥ŒData T:`°dONLNdƒ™Î∂ˇ)ypes“@°dONLNd ™
∂
)(
1E†°dONLNdÀ™
∂
*)1-81°dONLNd–∑Œ√È(¿ŒPPC T`°dONLNd’∑È√
0)oolbox RoutinesÄ°dONLNdÊ∑
E√
J)\
1y‡°dONLNdÁ∑
I√
[)1-87°dONLNdσŒ–
(ÕŒApplication-Defi†°dONLNd¸ƒ
–
R)Jned RoutinesI¿°dONLNd

ƒ
g–
l)O
1Ω °dONLNd
ƒ
k–
})1-88°dONLNd
—ƒ›˘(⁄ƒ    C SummaryᆰdONLNd
—
›
)I
1˚°dONLNd
—
›
#)1-89°dONLNd
!fiŒÍ˙(ÁŒ    ConstantsÆ°dONLNd
,fi
Í
)@
1!`°dONLNd
-fi
Í
%)1-89°dONLNd
2ÎŒ˜’(ÙŒ
D=@°dONLNd
3Î÷˜Î)ata T:`°dONLNd
8ÎΘˇ)ypes“@°dONLNd
>Î
˜
)(
1E†°dONLNd
?Î
˜
*)1-90°dONLNd
D¯Œ
È(

ŒPPC T`°dONLNd
I¯È

0)oolbox RoutinesÄ°dONLNd
Z¯
E

J)\
1y‡°dONLNd
[¯
I

[)1-95°dONLNd
`
Œ

(
ŒApplication-Defi†°dONLNd
p



R)Jned RoutinesI¿°dONLNd
~

g

l)O
1Ω °dONLNd


k

})1-96°dONLNd
Ñ
ƒ

L(
ƒAssembly-Language Summary~†°dONLNd
ü

a

f)ù
1Ú°dONLNd
†

e

w)1-96°dONLNd
•
Œ
+‘(
(Œ
T∫¿°dONLNd
¶
”
+˚)rap Macr⁄°dONLNd
Æ
˚
+
)(osåÄ°dONLNd
≤


+
)
1ˇ‡°dONLNd
≥


+
/)1-96°dONLNd
∏
,ƒ
8˛(
5ƒResult Codesï`°dONLNd
Δ
,

8
)N
1¿°dONLNd
«
,

8
))1-97


hH
o4
iH
o 
jH
j

ˇ·ˇ‚7^,    Helvetica°dONLNd
Ã
\H
g~(
dH
Chapter 12°dONLNd
◊
Y∫
h€)rData .¿°dONLNd
‹
Y€
h
C)!Access Manager
lÄ°dONLNd
Ï
[
W
g
i)|12-1°dONLNd
Ú
o∫
{
(
x∫About the Data åÄ°dONLNd

o

{
G)FAccess Manager⇰dONLNd
o
\
{
n)\12-5°dONLNd
|ƒ
à
2(
ÖƒThe High-Level Interface#¿°dONLNd0
|
G
à
Y)É12-7°dONLNd5
âŒ
ï
*(
íŒSending a Query Thr$‡°dONLNdH
â
+
ï
∞)]ough the High-Level InterfaceG`°dONLNdg
â
ƒ
ï
÷)ô12-8°dONLNdl
ñŒ
¢
&(
üŒRetrieving Data ThrÑÄ°dONLNd
ñ
&
¢
´)Xough the High-Level Interfaceß°dONLNdû
ñ
ø
¢
—)ô12-9°dONLNd£
£ƒ
Ø
/(
¨ƒThe Low-Level Interfaceq¿°dONLNdº
£
D
Ø
V)Ä12-9°dONLNd¡
∞Œ
º
*(
πŒSending a Query Thr$‡°dONLNd‘
∞
+
º
≠)]ough the Low-Level Interfaceï`°dONLNdÚ
∞
¡
º
ÿ)ñ12-10°dONLNd¯
ΩŒ
…
&(
ΔŒRetrieving Data ThrÑÄ°dONLNd
Ω
&
…
®)Xough the Low-Level Interfaceı°dONLNd)
Ω
º
…
Œ)ñ12-1º@°dONLNd-
Ω
Œ
…
”)
1°dONLNd/
 ƒ
÷
Ω(
”ƒ5Comparison of the High-Level and Low-Level Interfacest °dONLNdf
 
“
÷
‰(
”
“12-1;`°dONLNdj
 
‰
÷
È)
1°dONLNdl
׺
„˛(
‡∫Using the Data À¿°dONLNd{
◊˛
„
E)DAccess Manager… °dONLNdã
◊
Z
„
q)\12-12°dONLNdë
‰ƒ

(
̃Executing Routines _†°dONLNd§
‰


A)XAsynchrÀ°dONLNd´
‰
A

d)%onouslyC°dONLNd¥
‰
y

ê)812-12°dONLNd∫
Òƒ
˝
y(
˙ƒ)General Guidelines for the User Interface†°dONLNdÂ
Ò
é
˝
•) 12-13°dONLNdÎ
˛Œ

3(ŒKeep the User in Contr`°dONLNd

˛
4

<)folr@°dONLNd
˛
P

g)12-13°dONLNdŒ◊(ŒPrN†°dONLNdÿ
P)
ovide Feedback to the UserS°dONLNd)
d
{)å12-13°dONLNd/ƒ$
L(!ƒUsing the High-Level InterfaceÄ°dONLNdO
a$
x)ù12-14°dONLNdU%ƒ1Œ(.ƒ
W¬†°dONLNdV%Õ1
°)    0riting a Status Routine for High-Level Functionsê °dONLNdà%
∂1
Õ)È12-22°dONLNdé2ƒ>
I(;ƒUsing the Low-Level Interface`Ä°dONLNd≠2
^>
u)ö12-28°dONLNd≥?ƒK
(HƒGetting Information ãÄ°dONLNd«?
K
z)[About Sessions in Prë`°dONLNd€?
zK
à)[ogr[°dONLNdfi?
âK
ñ)essû†°dONLNd„?
™K
¡)!12-35°dONLNdÈLƒXÕ(UƒPrN†°dONLNdÎLŒX
4)
ocessing Query Results¿°dONLNdL
IX
`){12-36°dONLNd    YŒe
0(bŒGetting Query Results
@°dONLNd Y
Ee
\)w12-36°dONLNd&fŒr
U(oŒConverting Query Results to T °dONLNdCf
Ur
b)áext?¿°dONLNdHf
vr
ç)!12-42°dONLNdNs∫≈(|∫Cr\°dONLNdPs≈
7)eating a Query Document∫¿°dONLNdis
K
b)Ü12-46°dONLNdoăå
ó(âƒ-User Interface Guidelines for Query Documents`°dONLNdûÄ
¨å
√)Ë12-46°dONLNd§çƒô
N(ñƒContents of a Query Document燰dONLNd¬ç
bô
y)û12-48°dONLNd»öƒ¶˚(£ƒQuery RecorP¿°dONLNd”ö¸¶
Z)8ds and Query Resour;@°dONLNdÊö
Z¶
g)^ces≤ °dONLNdÎö
{¶
í)!12-51°dONLNdÒ߃≥Œ(∞ƒ
W¬†°dONLNdÚßÕ≥
 )    riting a Query Defij‡°dONLNdß
!≥
d)Tnition Function_¿°dONLNdß
y≥
ê)X12-51ˇÓ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*ˇ
¯,Palatino

.
(·*xiv4^*¿
¯°dONLNd\úh≥(eúData °@°dONLNd\≥h
)Access Manager Referx¿°dONLNd\
h
()benceM†°dONLNd\
=h
T)(12-54°dONLNd%i¶u…(r¶Data Str``°dONLNd-i u·)$ucturÊ@°dONLNd2i·uÂ)
e؇°dONLNd3iÊuÍ)
sχ°dONLNd6i˛u
)12-54°dONLNd<v∞Ç√(∞The ]`°dONLNd@v√ÇË)Asynchr»¿°dONLNdGvËDz)%onouå@°dONLNdKvˇÇ
N)s Parameter Block⁄¿°dONLNd^v
bÇ
y)c12-55°dONLNddÉ∞è˚(å∞The Query RecoråÄ°dONLNdsÉ˚è

)K
d®@°dONLNdvÉ
è
,)12-56°dONLNd|ê∞úˇ(ô∞The Results Recorņ°dONLNdçêˇú
)O
dù`°dONLNdêê
ú
0)12-58°dONLNdñù¶©Ω(¶¶Data °@°dONLNdõùΩ©
)Access Manager RÆ°dONLNd´ù
©
.)QoutinesL°dONLNd¥ù
C©
Z)512-59°dONLNd∫™∞∂

(≥∞Initializing the Data €@°dONLNd–™

∂
Q)ZAccess Managerÿ†°dONLNd‡™
f∂
})\12-60°dONLNdÊ∑∞√
(¿∞High-Level Interface: H9`°dONLNd˝∑
√
é)iandling Query Documents†°dONLNd
∑
£√
∫)ä12-61°dONLNd
ƒ∞–
(Õ∞High-Level Interface: H9`°dONLNd
3ƒ
–
|)iandling Query Results©†°dONLNd
Jƒ
ê–
ß)w12-65°dONLNd
P—∞›
(⁄∞Low-Level Interfacl`°dONLNd
b—
›
')Te: Contrõ@°dONLNd
j—
'›
t)#olling the Session∫`°dONLNd
~—
à›
ü)a12-68°dONLNd
Ñfi∞Í
(Á∞Low-Level Interface: Su¿°dONLNd
öfi
Í
ô)cending and Executing QueriesÅ`°dONLNd
∏fi
≠Í
ƒ)ö12-76°dONLNd
æÎ∞˜
(Ù∞Low-Level Interface: R‰°dONLNd
‘Î
˜
^)detrieving Results'@°dONLNd
ÁÎ
s˜
ä)_12-82°dONLNd
̯∞

g(

∞'Installing and Removing Result Handlersχ°dONLNd¯
{

í)À12-86°dONLNd
¶
(
¶Application-Defi†°dONLNd,


*)Jned RoutinesI¿°dONLNd:

?

V)O12-89°dONLNd@
¶
≈(
¶Resourv@°dONLNdF
≈
“)cesÌ °dONLNdK
Ê
˝)!12-90°dONLNdQ
∞
+

(
(∞The Query Resour``°dONLNda



+
)Q
c–†°dONLNdb


+
    )
eö@°dONLNde


+
5)12-90°dONLNdk
,∞
8
(
5∞The Query String Resourû°dONLNdÇ
,

8
')nce◊‡°dONLNdÜ
,
;
8
R)12-91°dONLNdå
9∞
E∂(
B∞
T†¿°dONLNdç
9∂
EÙ)he Query Defi˝¿°dONLNdö
9Ù
E
)>nition © °dONLNd°
9

E
:)    Function r†°dONLNd™
9
;
E
Z)*Resourh‡°dONLNd∞
9
Z
E
^)
cŸ °dONLNd±
9
^
E
b)
e¢¿°dONLNd¥
9
w
E
é)12-92°dONLNd∫
Fú
R˝(
OúSummary of the Data 8†°dONLNdŒ
F˝
R
A)aAccess ManageC`°dONLNd€
F
A
R
D)D
r6°dONLNdfi
F
Y
R
p)12-93°dONLNd‰
S¶
_Ô(
\¶Pascal Summary‡°dONLNdÙ
S

_
)^12-93°dONLNd˙
`∞
l‹(
i∞    ConstantsÆ°dONLNd
`
l
)@12-93°dONLNd
m∞
yÕ(
v∞Data T:`°dONLNd
mÕ
y·)ypes“@°dONLNd
mı
y
)(12-94°dONLNd
z∞
Ü«(
É∞Data °@°dONLNd"
z«
Ü
)Access Manager †°dONLNd1
z

Ü
9)KRoutinesL°dONLNd;
z
M
Ü
d);12-96°dONLNdA
á∞
ì˙(
ê∞Application-Defi†°dONLNdQ
á˙
ì
4)Jned RoutinesI¿°dONLNd_
á
I
ì
`)O12-98°dONLNde
î¶
†€(
ù¶    C SummaryᆰdONLNdp
îÔ
†
)I12-98°dONLNdv
°∞
≠‹(
™∞    ConstantsÆ°dONLNdÅ
°
≠
)@12-98°dONLNdá
Æ∞
∫Õ(
∑∞Data T:`°dONLNdç
ÆÕ
∫·)ypes“@°dONLNdì
Æı
∫
)(12-100°dONLNdö
ª∞
««(
ƒ∞Data °@°dONLNdü
ª«
«
)Access Manager †°dONLNdÆ
ª

«
9)KRoutinesL°dONLNd∏
ª
M
«
i);12-101°dONLNdø
»∞
‘˙(
—∞Application-Defi†°dONLNdœ
»˙
‘
4)Jned RoutinesI¿°dONLNd›
»
I
‘
e)O12-103°dONLNd‰
’¶
·
.(
fi¶Assembly-Language Summary~†°dONLNdˇ
’
C
·
_)ù12-103°dONLNd
‚∞
Ó∂(
Î∞
T∫¿°dONLNd
‚µ
Ó›)rap Macr⁄°dONLNd
‚›
ÓÊ)(osåÄ°dONLNd
‚˚
Ó
)12-103°dONLNd
Ô¶
˚‡(
¯¶Result Codesï`°dONLNd(
ÔÙ
˚
)N12-104

+*2
¯4,*2
¯ -*-
¯

ˇ·ˇ‚7^,    Helvetica°dONLNd/ú+”('úGlossary
∏Ä°dONLNd9Á*˝)KGL-1

a*h
¯4b*h
¯ c*c
¯

ˇ·ˇ‚7^°dONLNd?Rúaæ(]úIndex
º‡°dONLNdFT“`Ê)6IN-1ˇ–@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
‡(‡xv4^H¿ˇˇ—Úˇ◊°dONLNd[∫o‰(j∫Figur{z°dONLNd[‰o
)*es, T5°dONLNd
[
o
ñ)"ables, and Listings

®HÆ4©HÆ ™∫™

ˇ·ˇ‚7^,    Helvetica
°dONLNdúH®j(•HPreface°dONLNd&ù∫®Ÿ)rAbout °dONLNd,ù⁄®

)     This Book    °dONLNd7ù
®
+)Cxxiii

”HŸ4‘HŸ ’∫’

ˇ·ˇ‚7^
°dONLNd>«H”s(–H    Chapter 1°dONLNdH»∫”
ú)r.Introduction to Interapplication Communication    Y °dONLNdx»
Ø”
º)ı1-1
°dONLNd}‹∫Á‰(‰∫
Figure 1-1°dONLNdà‹
Á
Ô)N7Principal methods of communication between applications䇰dONLNd¡‹
Á)˘1-5
°dONLNd≈Ë∫Û‰(∫
Figure 1-2°dONLNd–Ë
Û
»)N0Sharing data with the aid of the Edition Manager燰dONLNd
Ë
⁄Û
Á)“1-7
°dONLNd
Ù∫ˇ‰(¸∫
Figure 1-3°dONLNd
Ù
ˇ
)N
A0°dONLNd
Ù
ˇ
5)
 publisherÖ °dONLNd
Ù
4ˇ
ß)&, an edition, and a subscriber–°dONLNd
<Ù
∫ˇ
«)Ü1-8
°dONLNd
@
∫
‰(
∫
Figure 1-4°dONLNd
K



∫)N,Sharing dynamic data with other applications    `°dONLNd
y

Õ

⁄)≈1-8
°dONLNd
}
∫
‰(
∫
Figure 1-5°dONLNd
à



v)NSending and responding to  °dONLNd
¢

v

ı)n!Apple events with the aid of the p°dONLNd
√

ı
)Apple °dONLNd
…


!
E(

Event ManagerÑ°dONLNd
ÿ

W
!
i)O1-10
°dONLNd
›
"∫
-‰(
*∫
Figure 1-6°dONLNd
Ë
"

-
)N
A0°dONLNd
È
"

-
L) Set Data event‡°dONLNd
˙
"
^
-
p)P1-12
°dONLNd
ˇ
.∫
9‰(
6∫
Figure 1-7°dONLNd

.

9
∫)N+How a scripting component executes a script∞°dONLNd7
.
Õ
9
fl)≈1-14
°dONLNd<
:∫
E‰(
B∫
Figure 1-8°dONLNdG
:

E
)N
A0°dONLNdH
:

E
º), Set Data event sent during script execution–°dONLNdv
:
Œ
E
‡)¿1-17
°dONLNd{
F∫
Q‰(
N∫
Figure 1-9°dONLNdÜ
F

Q
≈)N0Recording user actions in a factored application
`°dONLNd∏
F
ÿ
Q
Í)–1-19
°dONLNdΩ
R∫
]Í(
Z∫Figure 1-10°dONLNd…
R

]
o)NControlling an application’[0°dONLNd‰
R
o
]
„)gs own behavior by executing °dONLNd
\

g
(
d
a °dONLNd
\

g
%)script‡°dONLNd

\
7
g
I)'1-20
°dONLNd
h∫
sÍ(
p∫Figure 1-11°dONLNd
h

s
Ó)N8Posting an invoice and updating a database by executing °dONLNdS
r

}
*
a °dONLNdU
r

}
%)script‡°dONLNd]
r
7
}
I)'1-21


°H
ß4
¢H
ß 
£∫
£

ˇ·ˇ‚7^
°dONLNdb
ïH
°s(
ûH    Chapter 2°dONLNdl
ñ∫
°

)rEdition Manager    ö¿°dONLNd}
ñ

°
))b2-1
°dONLNdÇ
™∫
µ‰(
≤∫
Figure 2-1°dONLNdç
™

µ
e)NThe default edition iconá °dONLNdß
™
w
µ
Ñ)o2-4
°dONLNd´
∂∫
¡‰(
æ∫
Figure 2-2°dONLNd∂
∂

¡
)N
A0°dONLNd∑
∂

¡
5)
 publisherÖ °dONLNd¡
∂
4
¡
ß)&, an edition, and a subscriber–°dONLNd·
∂
∫
¡
«)Ü2-5
°dONLNdÂ
º
Õ‰(
 ∫
Figure 2-3°dONLNd
¬

Õ
j)NThe publisher dialog boxÜ@°dONLNd

¬
|
Õ
â)t2-5
°dONLNd
κ
Ÿ‰(
÷∫
Figure 2-4°dONLNd
Œ

Ÿ
o)NThe subscriber dialog boxÑ–°dONLNd4
Œ
Å
Ÿ
é)y2-7
°dONLNd8
⁄∫
‰(
‚∫
Figure 2-5°dONLNdC
⁄

Â
)N
A0°dONLNdD
⁄

Â
≤)( document and its corresponding editions¿°dONLNdn
⁄
ƒ
Â
—)∂2-8
°dONLNdr
Ê∫
Ò‰(
Ó∫
Figure 2-6°dONLNd}
Ê

Ò
å)N Publisher and subscriber bordersÑ∞°dONLNdü
Ê
û
Ò
´)ñ2-9
°dONLNd£
Ú∫
˝‰(
˙∫
Figure 2-7°dONLNdÆ
Ú

˝
ª)N)Edition Manager commands in the Edit menu¿°dONLNdŸ
Ú
Œ
˝
‡)Δ2-10
°dONLNdfi
˛∫    ‰(∫
Figure 2-8°dONLNdÈ
˛
    
Ë)N3Edition Manager commands under the Publishing menu °dONLNd

/*
command†°dONLNd%
B
O):2-1VÄ°dONLNd(
N
S)
1
°dONLNd*∫‰(∫
Figure 2-9°dONLNd5

)N
A0°dONLNd6

˚); document with a publisher and subscriber and its resource °dONLNdq
)
(&
fork†°dONLNdw
))
;)!2-16
°dONLNd|*∫5Í(2∫Figure 2-10°dONLNdà*
5
v)NThe new publisher alert box0°dONLNd•*
â5
õ)Å2-19
°dONLNd™6∫AÍ(>∫Figure 2-11°dONLNd∂6
A
)N
A0°dONLNd∑6
A
Ä) sample publisher dialog box°dONLNd’6
íA
§)Ñ2-29
°dONLNd⁄B∫MÍ(J∫Figure 2-12°dONLNdÊB
M
)N
A0°dONLNdÁB
M
Ö) sample subscriber dialog boxê°dONLNdB
óM
©)â2-37
°dONLNdN∫YÍ(V∫Figure 2-13°dONLNdN
Y
Ó)N9The publisher options dialog box with update mode set to °dONLNdPX
c
*
On 
°dONLNdSX
c
+)SaveÉp°dONLNdYX
=c
O)&2-43
°dONLNd^d∫oÍ(l∫Figure 2-14°dONLNdjd
o
Ó)N9The publisher options dialog box with update mode set to °dONLNd£n
y
,*
ManuallyÄê°dONLNd≠n
>y
P)62-44
°dONLNd≤z∫ÖÍ(Ç∫Figure 2-15°dONLNdæz
Ö
Û)N:The subscriber options dialog box with update mode set to °dONLNd¯Ñ
è
=*
Automatically‡°dONLNdÑ
Pè
b)H2-44
°dONLNdê∫õÍ(ò∫Figure 2-16°dONLNdê
õ
Û)N:The subscriber options dialog box with update mode set to °dONLNdRö
•
,*
ManuallyÄê°dONLNd\ö
>•
P)62-45
°dONLNda¶∫±Í(Æ∫Figure 2-17°dONLNdm¶
±
÷)N-Edit menu with Show/Hide Borders menu commandÜ–°dONLNdú¶
˱
˙)‡2-51
°dONLNd°≤∫ΩÍ(∫∫Figure 2-18°dONLNd≠≤
Ω
N)NPublisher borders°dONLNd¿≤
aΩ
s)Y2-52ˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*ˇ
¯,Palatino

.
(·*xvi4^*¿
¯,    Helvetica    °dONLNd\úgÃ(dúFigure 2-19°dONLNd\Íg
6)NSubscriber bordersÅp°dONLNd \
Hg
Z)^2-53
°dONLNd%húsÃ(púFigure 2-20°dONLNd1hÍs)N
A0°dONLNd2hs
s)  publisher with contents removedá¿°dONLNdTh
Ös
ó)ï2-54
°dONLNdYtúÃ(|úFigure 2-21°dONLNdetÍ)N
A0°dONLNdft
≤)/ publisher border within a spreadsheet documentå–°dONLNdót
ƒ
÷)‘2-55
°dONLNdúÄúãÃ(àúFigure 2-22°dONLNd®ÄÍã)N
A0°dONLNd©Äã
Ç)% publisher border with resize handlesá`°dONLNd–Ä
îã
¶)§2-56
°dONLNd’åúóÃ(îúFigure 2-23°dONLNd·åÍó)N
A0°dONLNd‚åó
™)/ publisher and subscriber with clipped graphicsâ`°dONLNd
å
ºó
Œ)Ã2-57
°dONLNd
òú£Ã(†úFigure 2-24°dONLNd
$òÍ£
~)N&Creating multiple publishers alert boxÉ °dONLNd
Lò
ê£
¢)¶2-58
°dONLNd
Q§úØÃ(¨úFigure 2-25°dONLNd
]§ÍØ
w)N$Saving multiple publishers alert box°dONLNd
ɧ
äØ
ú)†2-58
°dONLNd
à∞úªÃ(∏úFigure 2-26.°dONLNd
î∞ͪ
M)NSubscribing directly to a ,
Courier°dONLNd
Æ∞
Mª
k)c'PICT'°dONLNd
¥∞
kª
r) fi°dONLNd
∑∞
rª
y)le°dONLNd
ª∞
ãª
ù)2-62
.
°dONLNd
¿»ú”»(–úListing 2-1°dONLNd
û͔
’)N<Accepting Section Read events and verifying if a section is °dONLNd“Í›
*

registeredć°dONLNd“
$›
6):2-14
°dONLNdfiúÈ»(ÊúListing 2-2°dONLNd%fiÍÈ
Ü)N%Saving a document containing sectionså0°dONLNdLfi
òÈ
™)Æ2-21
°dONLNdQÍúı»(ÚúListing 2-3°dONLNd]ÍÍı
å)N&Opening a document containing sections0°dONLNdÖÍ
üı
±)µ2-23
°dONLNdäˆú

»(˛úListing 2-4°dONLNdñˆÍ


:)NCreating a publisher °dONLNd¨ˆ
M


_)c2-33
°dONLNd±
ú
»(

úListing 2-5°dONLNdΩ
Í
Ú)N
W’ê°dONLNdæ
Ú

M)riting data to an edition‹@°dONLNdŸ

_

q)m2-36
°dONLNdfi
ú
»(
úListing 2-6°dONLNdÍ
Í

?)NCreating a subscriber
∞°dONLNd


R

d)h2-40
°dONLNd
ú
%»(
"úListing 2-7°dONLNd
Í
%
F)NReading in edition dataá¿°dONLNd+

X
%
j)n2-42
°dONLNd0
&ú
1»(
.úListing 2-8°dONLNd<
&Í
1
Y)NResponding to action codesâ°dONLNdX
&
k
1
})Å2-46
°dONLNd]
2ú
=»(
:úListing 2-9°dONLNdi
2Í
=
Ö)N&Using your own edition opener function    ∞°dONLNdë
2
ò
=
™)Æ2-67


a*
g
¯4
b*
g
¯ 
cú
c
¯

ˇ·ˇ‚7^
°dONLNdñ
U*
aU(
^*    Chapter 3°dONLNd†
Vú
a‰)rIntroduction to ©–°dONLNd∞
V‰
a
$)HApple Events    {P°dONLNdæ
V
7
a
D)S3-1
°dONLNd√
jú
uΔ(
rú
Figure 3-1°dONLNdŒ
jÍ
u
V)NAn Open Documents eventàp°dONLNdÁ
j
h
u
u)~3-4
°dONLNdÎ
vú
ÅΔ(
~ú
Figure 3-2°dONLNdˆ
vÍ
Å)N
A0°dONLNd˜
v
Å
/) Get Data event@°dONLNd
v
A
Å
N)Q3-7
°dONLNd
Çú
çΔ(
äú
Figure 3-3°dONLNd
ÇÍ
ç
fl)N;Major attributes and direct parameter of an Open Documents °dONLNdR
åÍ
ó
*
eventÇê°dONLNdY
å

ó
$)(3-10
°dONLNd^
òú
£Δ(
†ú
Figure 3-4°dONLNdi
òÍ
£
Œ)N9Major attributes and direct parameter of a Get Data eventâ°dONLNd§
ò
‡
£
Ì)ˆ3-1fl–°dONLNdß
ò
Ï
£
Ò)
1
°dONLNd©
§ú
ØΔ(
¨ú
Figure 3-5°dONLNd¥
§Í
Ø)N
A0°dONLNdµ
§
Ø
Ì)? descriptor record whose data handle refers to an unterminated °dONLNdÙ
ÆÍ
πˇ(
∂Ístring¿°dONLNd¸
Æ

π
$)(3-13
°dONLNd

∫ú
≈Δ(
¬ú
Figure 3-6°dONLNd
∫Í
≈)N
A0°dONLNd
∫
≈
Ÿ); descriptor record whose data handle refers to event class °dONLNdH
ƒÍ
œ˚(
ÃÍdataê°dONLNdN
ƒ

œ
 )$3-14
°dONLNdS
–ú
€Δ(
ÿú
Figure 3-7°dONLNd^
–Í
€)N
A0°dONLNd_
–
€
0) keyword-specifiÇ`°dONLNdo
–
0
€
Ò)@3ed descriptor record for the event class attribute °dONLNd¢
⁄Í
Â
(
‚Í
of an Open`°dONLNd¨
⁄

Â
)-
 ÖÄ°dONLNd≠
⁄

Â
_)Documents eventâê°dONLNdæ
⁄
q
Â
É)X3-16
°dONLNd√
Êú
ÒΔ(
Óú
Figure 3-8°dONLNdŒ
ÊÍ
Ò)N
A0°dONLNdœ
Ê
Ò
r)& descriptor list for a list of aliases°dONLNd˜
Ê
Ñ
Ò
ñ)î3-17
°dONLNd¸
Úú
˝Δ(
˙ú
Figure 3-9°dONLNd
ÚÍ
˝
Æ)N.Data structures within an Open Documents eventâ∞°dONLNd7
Ú
¿
˝
“)÷3-19
°dONLNd<
˛ú    Ã(úFigure 3-10°dONLNdH
˛Í    
æ)N0Accepting and processing an Open Documents event–°dONLNdz
˛
—    
„)Á3-21
°dONLNd
úÃ(úFigure 3-11°dONLNdã
͸)NThe ê°dONLNdè
¸
“)4Apple Event Manager calling the handler for an Open °dONLNd√Í
0(ÍDocuments eventÑ°dONLNd‘
B
T)X3-22
°dONLNdŸ ú+Ã((úFigure 3-12°dONLNd Í+
ë)N%Responding to an Open Documents event°dONLNd 
§+
∂)∫3-27
°dONLNd,ú7Ã(4úFigure 3-13°dONLNd,Í7
C)NData structures within Å0°dONLNd4,
C7
l)Y
a simple oÇ°dONLNd>,
l7
õ))bject specifiÑ °dONLNdK,
õ7
æ)/    er recordÉê°dONLNdV,
—7
„)63-37
°dONLNd[8úCÃ(@úFigure 3-14°dONLNdg8ÍC
+)NAn object specifi†°dONLNdx8
,C
†)Ber record in a Get Data event
P°dONLNdó8
≤C
ƒ)Ü3-38
°dONLNdúDúOÃ(LúFigure 3-15°dONLNd®DÍO
`)NSuperclasses and subclasses°dONLNd≈D
sO
Ö)â3-40
°dONLNd Pú[Ã(XúFigure 3-16°dONLNd÷PÍ[
—)N<The object class inheritance hierarchy for the object class .°dONLNdZÍe
*
cWindow°dONLNdZ
e
1)53-44
.
°dONLNd fúqÃ(núFigure 3-17.°dONLNd,fÍq˜)NAn 
p°dONLNd/f˜q
f)Apple event object of class 
p°dONLNdKf
fq
)ocWord
p°dONLNdPf
q
¿) contained in an LJ°dONLNdaf
øq
Ò)@Apple event °dONLNdmpÍ{
'(xÍobject of class °dONLNd}p
'{
Y)=
cParagraph°dONLNdâp
k{
})D3-46ˇ“@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
I (‡xvii4^H¿

hHn4iHn j∫j

ˇ·ˇ‚7^,    Helvetica°dONLNd\Hhs(eH    Chapter 4°dONLNd
]∫h
)rResponding to 䰡dONLNd]
h
C)IApple Events    ∂0°dONLNd&]
Vh
c)S4-1
°dONLNd+q∫|‰(y∫
Figure 4-1°dONLNd6q
|
)N
A0°dONLNd7q
|
Ê)6 document with a button that triggers a Get Data event–°dONLNdoq
¯|
)Í4-51
°dONLNdt}∫à‰(Ö∫
Figure 4-2°dONLNd}
à
)N
A0°dONLNdÄ}
à
Ì): server application displaying a dialog box that requests °dONLNd∫á
í
l(è
information from the userÅ°dONLNd’á
~í
ê)v4-52
°dONLNd⁄ì∫û‰(õ∫
Figure 4-3°dONLNdÂì
û
f)NHandling user interactio`°dONLNd˝ì
gû
l)_
n0°dONLNd
ì
~û
ê)4-53
°dONLNd
ü∫™‰(ß∫
Figure 4-4.°dONLNd
ü
™
è)N#Handling user interaction with the ,
Courier°dONLNd
3ü
è™
À)ákAEWaitReply°dONLNd
?ü
À™
“)< fl°dONLNd
Bü
“™
Ë)ag se°dONLNd
Gü
Ë™
Î)
t°dONLNd
Jü
˝™)4-54
.
°dONLNd
O´∫∂‰(≥∫
Figure 4-5.°dONLNd
Z´
∂
è)N#Handling user interaction with the °dONLNd
}´
è∂
–)ákAEQueueReply°dONLNd
ä´
–∂
◊)A fl°dONLNd
ç´
׶
„)ag °dONLNd
ê´
„∂
Ì)se°dONLNd
í´
Ì∂
)

t°dONLNd
ï´∂)4-55
.
°dONLNd
ö√∫Œ·(À∫    Table 4-1°dONLNd
§√
Œ
ì)N"Coercion handling provided by the 
¿°dONLNd
Δ√
ìŒ
È)ãApple Event Managerëp°dONLNd
€√
˚Œ)h4-43
°dONLNd
‡œ∫⁄·(◊∫    Table 4-2°dONLNd
͜
⁄
|)NDescriptor types used by the á`°dONLNdœ
|⁄)tApple Event Manager (excluding °dONLNd&Ÿ
‰
}(·
those used with object specifiᇰdONLNdDŸ
}‰
®)uer records)°dONLNdQŸ
ª‰
Õ)>4-57
°dONLNdVÒ∫¸Ê(˘∫Listing 4-1.°dONLNdbÒ
¸
)N
A
p°dONLNdcÒ
¸
)
 
p°dONLNddÒ
¸
3)DoEvent
p°dONLNdkÒ
3¸
^)#
 procedure
p°dONLNdwÒ
p¸
})=4-5
.
°dONLNd{˝∫
Ê(
∫Listing 4-2.°dONLNdá˝


)N
A
p°dONLNdà˝


)
 
p°dONLNdâ˝


`)DoHighLevelEvent
p°dONLNdô˝
`

æ)P procedure for handling LJ°dONLNd±˝
Ω
)]Apple events and .
°dONLNd¬



b(

other high-level events¿°dONLNd€

u

Ç)m4-6
°dONLNdfl
∫
Ê(
∫Listing 4-3°dONLNdÎ



É)N Adding entries for the required à°dONLNd

É

˝){Apple events to an application’i`°dONLNd*

˝
)zs °dONLNd,


(
q(
%
Apple event dispatch table
°dONLNdH

Ñ
(
ë)|4-8
°dONLNdL
)∫
4Ê(
1∫Listing 4-4°dONLNdX
)

4
Q)NAdding entries for P°dONLNdk
)
Q
4)I/Apple events sent by the Edition Manager to an °dONLNdö
3

>
5(
;
application’Y0°dONLNd¶
3
5
>
<)-s ⁄¿°dONLNd®
3
;
>
§)Apple event dispatch tabled¿°dONLNdƒ
3
∑
>
ƒ)|4-9
°dONLNd»
?∫
JÊ(
G∫Listing 4-5°dONLNd‘
?

J
)N
A0°dONLNd’
?

J
e) handler for the Open 
@°dONLNdÎ
?
e
J
©)WApplication eventè–°dONLNd˛
?
ª
J
Õ)V4-15
°dONLNd
K∫
VÊ(
S∫Listing 4-6°dONLNd
K

V
)N
A0°dONLNd
K

V
´)% handler for the Open Documents event凰dONLNd7
K
Ω
V
œ)Ø4-15
°dONLNd<
W∫
bÊ(
_∫Listing 4-7°dONLNdH
W

b
)N
A0°dONLNdI
W

b
®)& handler for the Print Documents event
°dONLNdq
W
∫
b
Ã)¨4-18
°dONLNdv
c∫
nÊ(
k∫Listing 4-8°dONLNdÇ
c

n
)N
A0°dONLNdÉ
c

n
`) handler for the Quit à°dONLNdô
c
_
n
£)QApplication event†°dONLNd¨
c
∂
n
»)W4-19
°dONLNd±
o∫
zÊ(
w∫Listing 4-9°dONLNdΩ
o

z
)N
A0°dONLNdæ
o

z
®)' handler for the Create Publisher eventä–°dONLNdÁ
o
∫
z
Ã)¨4-23
°dONLNdÏ
{∫
ÜÎ(
É∫Listing 4-10°dONLNd˘
{

Ü
õ)N'Extracting items from a descriptor list˛°dONLNd"
{
≠
Ü
ø)•4-33
°dONLNd'
á∫
íÎ(
è∫Listing 4-11.°dONLNd4
á

í
)N
A
p°dONLNd5
á

í
y) function that checks for a 
p°dONLNdQ
á
y
í
›)kkeyMissedKeywordAttr
p°dONLNde
á
›
í
fl)d
 .
°dONLNdf
ë

ú
((
ô
    attribute
†°dONLNdq
ë
;
ú
M)34-35
°dONLNdv
ù∫
®Î(
•∫Listing 4-12.°dONLNdÉ
ù

®
5)NAdding the °dONLNdé
ù
5
®
{)-keyErrorString°dONLNdú
ù
{
®
◊)F parameter to the reply 
p°dONLNd¥
ù
◊
®
)\Apple .
°dONLNd∫
ß

≤
(
Ø
eventÇê°dONLNd¡
ß
0
≤
B)(4-38
°dONLNdΔ
≥∫
æÎ(
ª∫Listing 4-13°dONLNd”
≥

æ
Ö)NAdding parameters to the reply á°dONLNdÚ
≥
Ö
æ
¥)}Apple event °dONLNdˇ
≥
«
æ
Ÿ)B4-39
°dONLNd
ø∫
 Î(
«∫Listing 4-14.°dONLNd
ø

 
0)N
Using the °dONLNd
ø
0
 
ä)(AEInteractWithUser°dONLNd-
ø
ä
 
≠)Z     function°dONLNd8
ø
ø
 
—)54-50


ÓH
Ù4
ÔH
Ù 
∫


ˇ·ˇ‚7^
.
°dONLNd=
‚H
Ós(
ÎH    Chapter 5°dONLNdG
„∫
Ó
')rCreating and Sending ]0°dONLNd\
„
'
Ó
g)mApple Events    .∞°dONLNdj
„
z
Ó
á)S5-1
°dONLNdo
˜∫Ê(
ˇ∫Listing 5-1°dONLNd{
˜

„)N7Creating the optional keyword for the Create Publisher °dONLNd≤


*
eventÇê°dONLNdπ

0
=)(5-9
°dONLNdΩ∫Ê(∫Listing 5-2°dONLNd…

m)NCreating a target address0°dONLNd‰
Ä
ç)x5-1[°dONLNdÁ
å
ë)
1
°dONLNdÈ∫$Ê(!∫Listing 5-3°dONLNdı
$
ç)N"Specifying a target address in an ä–°dONLNd
ç$
Ú)ÖApple event by using the .°dONLNd0#
.
:(+

PPCBrowser°dONLNd:#
:.
])2     function°dONLNdE#
o.
Å)55-12
.
°dONLNdJ/∫:Ê(7∫Listing 5-4°dONLNdV/
:
8)NSending an p°dONLNda/
8:
g)0Apple event冰dONLNdn/
y:
ã)A5-17
°dONLNds;∫FÊ(C∫Listing 5-5°dONLNd;
F
E)NAn idle function‡°dONLNdë;
XF
j)P5-23

jHp4kHp l∫l

ˇ·ˇ‚7^
°dONLNdñ^Hjs(gH    Chapter 6°dONLNd†_∫j
s)r$Resolving and Creating Object Specifi√·°dONLNd≈_
sj
®)π
er Records    è·°dONLNd—_
ªj
»)H6-1
°dONLNd÷s∫~‰({∫
Figure 6-1°dONLNd·s
~
r)NResolving an object specifi°dONLNd¸s
s~
’)ker record for a table in a °dONLNd}
à
/(Ö
document‡°dONLNd!}
Bà
O):6-6
°dONLNd%â∫î‰(ë∫
Figure 6-2°dONLNd0â
î
)N
NˇP°dONLNd1â
î
)esÄ °dONLNd3â
î
,)
ted oÇ–°dONLNd8â
,î
[)bject specifiÑ°dONLNdEâ
[î
Â)/$er records that specify a container °dONLNdiì
û
,(õ
    hierarchy°dONLNdtì
?û
Q)76-10
°dONLNdyü∫™‰(ß∫
Figure 6-3°dONLNdÑü
™
â)N!The container hierarchy for the fi °dONLNd¶ü
ä™)Ç rst row in a table that meets a °dONLNdΔ©
¥
(±
test
°dONLNdé
)¥
;)!6-18ˇ(@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*ˇ
¯,Palatino

.
(·*xviii4^*¿
¯,    Helvetica    °dONLNd\úgΔ(dú
Figure 6-4°dONLNd\Íg)N
A0°dONLNd\g
)& logical descriptor record that specifiÖ‡°dONLNd3\
g
°)è    es a testà–°dONLNd>\
≥g
≈)46-19
°dONLNdChúsΔ(pú
Figure 6-5°dONLNdNhÍs
á)N(Descriptor record for an application-defi`°dONLNdwh
às
›)ûned token that identifiã–°dONLNdéh
›s
)Ues a °dONLNdìrÍ}
(zÍdocument‡°dONLNdùr
$}
6):6-39
°dONLNd¢~úâΔ(Üú
Figure 6-6°dONLNd≠~Íâ
á)N(Descriptor record for an application-defi`°dONLNd÷~
àâ
›)ûned token that identifiã–°dONLNdÌ~
݉
È)Ues .°dONLNdàÍì˘(êÍthe ,
Courier°dONLNdÙà˘ì
)pbounds°dONLNd˚à
ì
p)# property of a window°dONLNd
à
Çì
î)f6-40
.
°dONLNd
îúüΔ(úú
Figure 6-7°dONLNd
"îÍü)N
A0°dONLNd
#îü
})$ container hierarchy created by the ã °dONLNd
Gî
|ü
’)åApple Event Manager ë°dONLNd
[î
’ü
Ù)Yusing a °dONLNd
cûÍ©
J(¶Íwhose descriptor recordŇ°dONLNd
|û
\©
n)r6-43
°dONLNd
Å∂ú¡√(æú    Table 6-1.°dONLNd
ã∂Í¡
})N$Standard descriptor types used with °dONLNd
Ø∂
}¡
π)ìkeyAEKeyData°dONLNd
Ω∂
À¡
›)N6-12
.
°dONLNd
¬¬úÕ√( ú    Table 6-2°dONLNd
ìÍÕ
))NKeyword-specifi–°dONLNd
€¬
*Õ
é)@ed descriptor records for .°dONLNd
ıÃÍ◊
D(‘ÍtypeCompDescriptor°dONLNd    Ã
V◊
h)l6-16
.
°dONLNdÿú„√(‡ú    Table 6-3°dONLNdÿÍ„
))NKeyword-specifi–°dONLNd'ÿ
*„
é)@ed descriptor records for .°dONLNdA‚ÍÌ
S(ÍÍtypeLogicalDescriptor°dONLNdX‚
eÌ
w){6-17
.
°dONLNd]Óú˘√(ˆú    Table 6-4°dONLNdgÓ͢
))NKeyword-specifi–°dONLNdvÓ
*˘
ı)@5ed descriptor records in a descriptor record of type .°dONLNd´¯Í

I(
ÍtypeRangeDescriptor°dONLNd¿¯
[

m)q6-20
.
°dONLNd≈
ú
√(
ú    Table 6-5°dONLNdœ
Í

))NKeyword-specifi–°dONLNdfi

*

é)@ed descriptor records for .°dONLNd¯
Í

I(
ÍtypeWhoseDescriptor°dONLNd

[

m)q6-42
.
°dONLNd
ú
%√(
"ú    Table 6-6ˇˇÄ.°dONLNd
Í
%
+)NKeyword-specifi°dONLNd+

+
%
é)Aed descriptor records for ˇ˛¿°dONLNdE

é
%
‘)ctypeWhoseRangeˇˇÄ°dONLNdU

Ê
%
¯)X6-44
.
°dONLNdZ
&ú
1√(
.ú    Table 6-7°dONLNdd
&Í
1˙)NNesÄ °dONLNdg
&˙
1
)ted oÇ–°dONLNdl
&

1
=)bject specifiÑ°dONLNdy
&
=
1
Õ)/%er records that describe a container °dONLNdû
0Í
;

(
8Íhierarchˇ°dONLNd¶
0


;
) 
y°dONLNd©
0
!
;
3)6-56
°dONLNdÆ
<ú
G√(
Dú    Table 6-8°dONLNd∏
<Í
G
 )NObject specifiÇ@°dONLNdΔ
<
 
G
g)6er record for the fiÉp°dONLNd⁄
<
g
G
‚)G!rst row that meets a test in the °dONLNd˚
FÍ
Q
Z(
NÍtable named “MyAddresses”–°dONLNd
F
m
Q
)É6-65
°dONLNd
Rú
]√(
Zú    Table 6-9°dONLNd%
RÍ
]
z)N%Logical descriptor record that specifiÖ°dONLNdK
R
z
]
ú)ê    es a testà°dONLNdV
R
Æ
]
¿)46-66
°dONLNd[
^ú
i»(
fú
Table 6-10°dONLNdf
^Í
i)N
A0°dONLNdg
^
i
O) range descriptor recordÑ`°dONLNdÅ
^
a
i
s)q6-73
°dONLNdÜ
jú
u»(
rú
Table 6-11°dONLNdë
jÍ
u
))NKeyword-specifi–°dONLNd†
j
*
u
é)@ed descriptor records for .°dONLNd∫
tÍ

I(
|ÍtypeObjectSpecifier°dONLNdœ
t
[

m)q6-76
.
°dONLNd‘
åú
ó»(
îúListing 6-1°dONLNd‡
åÍ
ó
ç)N+Installing object accessor functions that fi    ¿°dONLNd
å
é
ó
’)§nd elements of difÂ@°dONLNd
å
‘
ó
Ì)Fferent °dONLNd%
ñÍ
°
û(
ûÍ-classes for container tokens of the same type
°dONLNdT
ñ
±
°
√)«6-23
°dONLNdY
¢ú
≠»(
™úListing 6-2°dONLNde
¢Í
≠
ö)N.Installing one object accessor function that fiP°dONLNdî
¢
õ
≠
›)±nds elements of °dONLNd§
¨Í
∑Û(
¥Ídif◊0°dONLNdß
¨Û
∑
´)    /ferent classes for container tokens of one type„‡°dONLNdÿ
¨
Ω
∑
œ) 6-25
°dONLNd›
∏ú
√»(
¿úListing 6-3°dONLNdÈ
∏Í
√
ç)N+Installing object accessor functions that fi    ¿°dONLNd
∏
é
√
Û)§nd elements of the same °dONLNd-
¬Í
Õ
f(
 Í!class for container tokens of dif]@°dONLNdN
¬
f
Õ
ï)|ferent types`Ä°dONLNd\
¬
ß
Õ
π)A6-25
°dONLNda
Μ
Ÿ»(
÷úListing 6-4°dONLNdm
ŒÍ
Ÿ
fi)N@Installing object accessor functions that locate elements of difeÄ°dONLNd≠
Œ
fi
Ÿ
˜)Ùferent °dONLNd¥
ÿÍ
„
e(
‡Í classes in the default containerP°dONLNd÷
ÿ
x
„
ä)é6-26
°dONLNd€
‰ú
Ô»(
ÏúListing 6-5°dONLNdÁ
‰Í
Ô
ã)N)An object accessor function that locates P°dONLNd
‰
ã
Ô
Ê)°Apple event objects of .°dONLNd'
ÓÍ
˘
(
ˆÍobject class °dONLNd4
Ó

˘
J)3    cDocument°dONLNd?
Ó
\
˘
n)?6-30
.
°dONLNdD
˙ú»(úListing 6-6°dONLNdP
˙Í
ã)N)An object accessor function that locates P°dONLNdy
˙
ã
Ê)°Apple event objects of .°dONLNdêÍ
(Íobject class °dONLNdù

O)3
cParagraph°dONLNd©
a
s)D6-32
.
°dONLNdÆú»(úListing 6-7°dONLNd∫Í
ã)N)An object accessor function that locates P°dONLNd„
ã
Ê)°Apple event objects of .°dONLNd˙Í%
("Íobject class °dONLNd
%
6)3cWord°dONLNd
H%
Z)+6-34
.
°dONLNd&ú1»(.úListing 6-8°dONLNd&Í1
ã)N)An object accessor function that locates P°dONLNdH&
ã1
Ê)°Apple event objects of .°dONLNd_0Í;
(8Íobject class °dONLNdl0
;
@)3cWindow°dONLNdu0
R;
d)56-35
.
°dONLNdz<úG»(DúListing 6-9°dONLNdÜ<ÍG
Ü)N(An object accessor function that identifiã°dONLNdØ<
ÜG
ÿ)úes any property of a °dONLNdƒFÍQ
(NÍwindowÄ`°dONLNdÕF
#Q
5)96-38
°dONLNd“Rú]Õ(ZúListing 6-10°dONLNdflRÍ]
V)NAn object-counting function∞°dONLNd¸R
i]
{)6-49
°dONLNd    
^úiÕ(fúListing 6-11°dONLNd    ^Íi
¶)N-Object-comparison function that compares two @°dONLNd    ;^
¶i
ÿ)ºApple event °dONLNd    GhÍs
(pÍobjects
‡°dONLNd    Ph
s
+)/6-52
°dONLNd    UtúÕ(|úListing 6-12°dONLNd    btÍ
O)NCreating an object specifiÖÄ°dONLNd    |t
O
ç)eer record using .°dONLNd    å~Íâ
D(ÜÍCreateObjSpecifier°dONLNd    †~
Vâ
h)l6-58
.
°dONLNd    •äúïÕ(íúListing 6-13.°dONLNd    ≤äÍï
)NUsing °dONLNd    ∏ä
ï
])CreateObjSpecifier°dONLNd     ä
]ï
≤)Z in an application-defi°dONLNd    ·ä
≤ï
√)Uned .
°dONLNd    ÂîÍü
    (úÍfunction–°dONLNd    Ôî
ü
.)26-59
°dONLNd    Ù†ú´Õ(®úListing 6-14°dONLNd

†Í´
l)NSpecifying a document container    °dONLNd
"†
´
ë)ï6-61ˇ!x@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
, (‡    xix4^H¿,    Helvetica    °dONLNd\∫gÎ(d∫Listing 6-15°dONLNd\
g
v)NSpecifying a table container°dONLNd+\
âg
õ)Å6-62
°dONLNd0h∫sÎ(p∫Listing 6-16°dONLNd=h
s
m)NCreating an object specifiÖÄ°dONLNdWh
ms
⁄)eer record with the key form ,
Courier.°dONLNdsr
}
0(z
formName°dONLNd}r
B}
T):6-67
.
°dONLNdÇ~∫âÎ(Ü∫Listing 6-17°dONLNdè~
â
®)N'Creating a comparison descriptor record†°dONLNd∏~
ªâ
Õ)≥6-68
°dONLNdΩä∫ïÎ(í∫Listing 6-18°dONLNd ä
ï
ì)N$Creating a logical descriptor record@°dONLNdä
¶ï
∏)û6-70
°dONLNdıñ∫°Î(û∫Listing 6-19°dONLNd
ñ
°
å)N Creating a complex object specifiÖ@°dONLNd
#ñ
å°
Ø)Ñ    er recordÑ∞°dONLNd
.ñ
¬°
‘)66-70
°dONLNd
3¢∫≠Î(™∫Listing 6-20°dONLNd
@¢
≠
ë)N"Creating a range descriptor recordÉ–°dONLNd
d¢
£≠
µ)õ6-74

—H◊4“H◊ ”∫”

ˇ·ˇ‚7^
°dONLNd
i≈H—s(ŒH    Chapter 7°dONLNd
sΔ∫—
-)rIntroduction to Scripting    Ä°dONLNd
éΔ
@—
M)Ü7-1
°dONLNd
ì⁄∫‰(‚∫
Figure 7-1°dONLNd
û⁄
Â
)N
A0°dONLNd
ü⁄
Â
Z) script window in th°dONLNd
≥⁄
ZÂ
ö)Le Script Editor a@°dONLNd
ƒ⁄
öÂ
¿)@
pplication`°dONLNd
–⁄
“Â
fl)87-6
°dONLNd
‘Ê∫Ò‰(Ó∫
Figure 7-2°dONLNd
flÊ
Ò
%)NScript fi–°dONLNd
ËÊ
&Ò
‹).le icons in the Finder and corresponding user °dONLNd
˚
 (¯
actionŇ°dONLNd
 ˚
$)
s
‡°dONLNd
7˚
D)7-7
°dONLNd#¸∫
‰(
∫
Figure 7-3°dONLNd.¸


)N
HˇP°dONLNd/¸


+)ow the LJ°dONLNd6¸
+

Œ)'AppleScript component executes a scriptå`°dONLNd_¸
‡

Ì)µ7-9
°dONLNdc
∫
‰(
∫
Figure 7-4°dONLNdn



{)NHow an application uses the     p°dONLNdä

{
)s!AppleScript component to execute °dONLNd´



(

a °dONLNd≠



%)script‡°dONLNdµ

7

I)'7-13
°dONLNd∫
∫
)‰(
&∫
Figure 7-5.°dONLNd≈


)
5)NRole of the °dONLNd—

5
)
S)-'aete'°dONLNd◊

S
)
f) and °dONLNd‹

f
)
Ñ)'aeut'°dONLNd‚

Ñ
)
◊) resources when the 
p°dONLNdˆ

◊
))SAppleScript .
°dONLNd
(

3
≤(
0
(component compiles and executes a script↰dONLNd,
(
ƒ
3
÷)º7-18
°dONLNd1
4∫
?‰(
<∫
Figure 7-6.°dONLNd<
4

?
5)NRole of the °dONLNdH
4
5
?
S)-'aete'°dONLNdN
4
S
?
f) and °dONLNdS
4
f
?
Ñ)'aeut'°dONLNdY
4
Ñ
?
◊) resources when the 
p°dONLNdm
4
◊
?)SAppleScript .
°dONLNdy
>

I
∂(
F
)component records and decompiles a scriptá∞°dONLNd§
>
»
I
⁄)¿7-19
°dONLNd©
J∫
U‰(
R∫
Figure 7-7°dONLNd¥
J

U
)N
UˇP°dONLNdµ
J

U
≈)0sing a handler in a script context to handle an P°dONLNdÂ
J
Δ
U
fl)∏Apple °dONLNdÎ
T

_
(
\
eventÇê°dONLNdÚ
T
0
_
B)(7-26


ÉH
â4
ÑH
â 
Ö∫
Ö

ˇ·ˇ‚7^
°dONLNd˜
wH
És(
ÄH    Chapter 8°dONLNd

x∫
ɯ)rApple Event ≠∞°dONLNd
x¯
ɲ)>
T-∞°dONLNd
x˛
É
k)erminology Resources    ùP°dONLNd$
x
}
É
ä)8-1
°dONLNd)
å∫
ó‰(
î∫
Figure 8-1.°dONLNd4
å

ó
F)NStructure of an °dONLNdD
å
F
ó
d)>'aeut'°dONLNdJ
å
d
ó
p) or °dONLNdN
å
p
ó
é)'aete'°dONLNdT
å
é
ó
¥)     resource°dONLNd_
å
Δ
ó
ÿ)88-26
.
°dONLNdd
ò∫
£‰(
†∫
Figure 8-2.°dONLNdo
ò

£
ê)N#Structure of the header data in an °dONLNdí
ò
ê
£
ï)à
'°dONLNdì
ò
ï
£
Æ)aeut'°dONLNdò
ò
Æ
£
∞)
 °dONLNdô
ò
∞
£
∫)or°dONLNdõ
ò
∫
£
º)

 °dONLNdú
ò
º
£
⁄)'aete'°dONLNd¢
ò
⁄
£
‹)
 .
°dONLNd£
¢

≠
+(
™
resourceĆ°dONLNd≠
¢
=
≠
O)58-27
°dONLNd≤
Æ∫
π‰(
∂∫
Figure 8-3.°dONLNdΩ
Æ

π
r)NStructure of suite data in a°dONLNdŸ
Æ
r
π
w)j
n°dONLNd⁄
Æ
w
π
y)
 °dONLNd€
Æ
y
π
ó)'aeut'°dONLNd·
Æ
ó
π
ô)
 °dONLNd‚
Æ
ô
π
£)or °dONLNdÂ
Æ
£
π
¡)
'aete'°dONLNdÎ
Æ
¡
π
√)
 °dONLNdÏ
Æ
√
π
Á)resource°dONLNdˆ
Æ
˘
π)68-28
.
°dONLNd˚
∫∫
≈‰(
º
Figure 8-4.°dONLNd
∫

≈
|)NStructure of event data in an °dONLNd$
∫
|
≈
ö)t'aeut'°dONLNd*
∫
ö
≈
¶) or °dONLNd.
∫
¶
≈
ƒ)'aete'°dONLNd4
∫
ƒ
≈
Í)     resource°dONLNd?
∫
¸
≈)88-30
.
°dONLNdD
Δ∫
—‰(
κ
Figure 8-5.°dONLNdO
Δ

—
§)N(Structure of additional parameter data i°dONLNdw
Δ
§
—
∑)ún an °dONLNd|
Δ
∑
—
’)'aeut'°dONLNdÇ
Δ
’
—
◊)
 °dONLNdÉ
Δ
◊
—
·)or °dONLNdÜ
Δ
·
—
ˇ)
'aete'°dONLNdå
Δ
ˇ
—
)
 .
°dONLNdç
–

€
+(
ÿ
resourceĆ°dONLNdó
–
=
€
O)58-34
°dONLNdú
‹∫
Á‰(
‰∫
Figure 8-6.°dONLNdß
‹

Á
ä)N"Structure of object class data in °dONLNd…
‹
ä
Á
ñ)Çan °dONLNdÃ
‹
ñ
Á
¥)'aeut'°dONLNd“
‹
¥
Á
∂)
 °dONLNd”
‹
∂
Á
¿)or °dONLNd÷
‹
¿
Á
fi)
'aete'°dONLNd‹
‹
fi
Á
‡)
 .
°dONLNd›
Ê

Ò
%(
Ó
resourc–°dONLNd‰
Ê
&
Ò
+)
eĆ°dONLNdÁ
Ê
=
Ò
O)8-36
°dONLNdÏ
Ú∫
˝‰(
˙∫
Figure 8-7.°dONLNd˜
Ú

˝
á)N!Structure of property data in an °dONLNd
Ú
á
˝
•)'aeut'°dONLNd
Ú
•
˝
±) or °dONLNd"
Ú
±
˝
œ)'aete'°dONLNd(
Ú
œ
˝
—)
 .
°dONLNd)
¸

%(
resourc–°dONLNd0
¸
&
+)
eĆ°dONLNd3
¸
=
O)8-38
°dONLNd8∫‰(∫
Figure 8-8.°dONLNdC

ù)N&Structure of element class data in an °dONLNdi
ù
ª)ï'aeut'°dONLNdo
ª
«) or °dONLNds
«
Â)'aete'°dONLNdy
Â
Á)
 .
°dONLNdz

%(
resourc–°dONLNdÅ
&
+)
eĆ°dONLNdÑ
=
O)8-41
°dONLNdâ∫)‰(&∫
Figure 8-9.°dONLNdî
)
∂)N+Structure of comparison operator data in an°dONLNdø
∂)
∏)Æ
 °dONLNd¿
∏)
÷)'aeut'°dONLNdΔ
÷)
‚) or °dONLNd 
‚))'aete'°dONLNd–))
 .
°dONLNd—(
3
%(0
resourc–°dONLNdÿ(
&3
+)
eĆ°dONLNd€(
=3
O)8-42
°dONLNd‡4∫?Í(<∫Figure 8-10.°dONLNdÏ4
?
ó)N$Structure of enumeration data in an °dONLNd4
ó?
µ)è'aeut'°dONLNd4
µ?
¡) or °dONLNd4
¡?
fl)'aete'°dONLNd 4
fl?
·)
 .
°dONLNd!>
I
%(F
resourc–°dONLNd(>
&I
+)
eĆ°dONLNd+>
=I
O)8-43
°dONLNd0J∫UÍ(R∫Figure 8-11.°dONLNd<J
U
ì)N#Structure of enumerator data in an °dONLNd_J
ìU
±)ã'aeut'°dONLNdeJ
±U
Ω) or °dONLNdiJ
ΩU
€)'aete'°dONLNdoJ
€U
›)
 .
°dONLNdpT
_
%(\
resourc–°dONLNdwT
&_
+)
eĆ°dONLNdzT
=_
O)8-44
°dONLNdl∫w·(t∫    Table 8-1°dONLNdâl
w
3)NSyntax for –°dONLNdîl
3w
Ù)+0AppleScript arguments that correspond to direct °dONLNdƒv
Å
5(~

parameters@°dONLNd–v
HÅ
U)@8-5
°dONLNd‘Ç∫ç·(ä∫    Table 8-2°dONLNdfiÇ
ç
3)NSyntax for –°dONLNdÈÇ
3ç)+3AppleScript arguments that correspond to insertion °dONLNdå
ó
S(î
location descriptor P°dONLNd0å
Tó
q)Lrecords °dONLNd9å
Ñó
ë)08-6
°dONLNd=ò∫£·(†∫    Table 8-3.°dONLNdGò
£
I)NStructure of the °dONLNdXò
I£
g)A'aeut'°dONLNd^ò
g£
z) and °dONLNdcò
z£
ò)'aete'°dONLNdiò
ò£
√)
 resources°dONLNduò
’£
‚)=8-8ˇp@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*ˇ
¯,Palatino

.
(·*xx4^*¿
¯,    Helvetica    °dONLNd\úg»(dúListing 8-1.°dONLNd\Íg
r)N"Resource type declaration for the ,
Courier°dONLNd.\
rg
ê)à'aeut'°dONLNd4\
êg
∂)     resource°dONLNd?\
»g
’)88-9
.
°dONLNdChús»(púListing 8-2.°dONLNdOhÍs
+)NRez input for an °dONLNd`h
+s
I)A'aete'°dONLNdfh
Is
)+ resource for an application that supports .
°dONLNdërÍ}
ú(zÍ.the Required and Core suites in their entirety∞°dONLNd¡r
Ø}
¡)≈8-15
°dONLNdΔ~úâ»(ÜúListing 8-3.°dONLNd“~Íâ
+)NRez input for an °dONLNd„~
+â
I)A'aete'°dONLNdÈ~
Iâ
ƒ) resource that extends the defi°dONLNd
~
ĉ
Î){nitions of .
°dONLNd
àÍì
L(êÍthe Required, Core, and ‹‡°dONLNd
+à
Lì
Q)b
T\‡°dONLNd
,à
Qì
w)
ext suites_°dONLNd
8à
âì
õ)88-17
°dONLNd
=îúü»(úúListing 8-4°dONLNd
IîÍü)N
A0°dONLNd
Jîü
@) handler for the Get à¿°dONLNd
_î
?ü
o)O
AETE eventç°dONLNd
kî
Åü
ì)B8-25
°dONLNd
p†ú´»(®úListing 8-5.°dONLNd
|†Í´
r)N"Resource type declaration for the °dONLNd
û†
r´
ê)à'scsz'°dONLNd
§†
ê´
∂)     resource°dONLNd
؆
»´
⁄)88-45

œ*’
¯4–*’
¯ —ú—
¯

ˇ·ˇ‚7^
.
°dONLNd
¥√*œU(Ã*    Chapter 9°dONLNd
æƒúœ—)r
Recording P°dONLNd
»ƒ—œ
)5Apple Events    Ë–°dONLNd
÷ƒ
#œ
0)R9-1
°dONLNd
€ÿú„»(‡úListing 9-1°dONLNd
ÁÿÍ„)N
A0°dONLNd
Ëÿ„
fi)? function used by a factored application to send itself a Quit °dONLNd'‚ÍÌ
.(ÍÍApplication eventê°dONLNd:‚
AÌ
N)W9-7
°dONLNd>Óú˘»(ˆúListing 9-2°dONLNdJÓ͢)N
A0°dONLNdKÓ˘
Ã)9 routine used by a factored application to handle a Quit °dONLNdѯÍ

.(
ÍApplication eventê°dONLNdó¯
A

N)W9-8
°dONLNdõ
ú
»(
úListing 9-3°dONLNdß
Í
)N
A0°dONLNd®


‰)@ routine used by a factored application to send itself a Create °dONLNdË
Í

#(
ÍElement event°dONLNd˜

6

H)L9-10
°dONLNd¸
ú
%»(
"úListing 9-4°dONLNd
Í
%
≠)N0The Create Element event handler for a factored °dONLNd8
$Í
/
*
applicationÇ°dONLNdE
$
'
/
4)=9-1ÿ–°dONLNdH
$
3
/
8)
1
°dONLNdJ
0ú
;»(
8úListing 9-5°dONLNdV
0Í
;)N
A0°dONLNdW
0
;
“)9 routine used by a factored application to handle window °dONLNdê
:Í
E
(
BÍmovementÄ¿°dONLNdö
:
&
E
8)<9-13


i*
o
¯4
j*
o
¯ 
kú
k
¯

ˇ·ˇ‚7^
°dONLNdü
]*
i[(
f*
Chapter 10°dONLNd™
^ú
i
)rScripting Components    ∏‡°dONLNd¿
^

i
,)~10-1
°dONLNdΔ
rú
}Ã(
zúFigure 10-1°dONLNd“
rÍ
})N
A0°dONLNd”
r
}
v)" generic storage descriptor recordÖ‡°dONLNd˜
r
à
}
ü)ò10-12
°dONLNd˝
~ú
âÃ(
ÜúFigure 10-2°dONLNd    
~Í
â)N
A0°dONLNd

~
â
;) component-specifiÖ†°dONLNd
~
;
â
¶)Kc storage descriptor recordá°dONLNd9
~
∏
â
œ)}10-13
°dONLNd?
ñú
°Õ(
ûúListing 10-1°dONLNdL
ñÍ
°
π)N3Locating a scripting component that supports specifiçÄ°dONLNdÄ
ñ
π
°
‚)œc optional °dONLNdã
†Í
´

(
®ÍroutinesÅ`°dONLNdï
†

´
.)210-6
°dONLNdö
¨ú
∑Õ(
¥úListing 10-2°dONLNdß
¨Í
∑)N
A0°dONLNd®
¨
∑
Ø)/ routine that compiles and executes source dataê°dONLNdŸ
¨
¡
∑
”)—10-9
°dONLNdfi
∏ú
√Õ(
¿úListing 10-3.°dONLNdÎ
∏Í
√)N
A
p°dONLNdÏ
∏
√
E) procedure that uses 
p°dONLNd

∏
E
√
ã)UOSAScriptError
p°dONLNd
∏
ã
√
Ó)F to get information about .
°dONLNd)
¬Í
Õ
2(
 Ían execution error°dONLNd=
¬
E
Õ
W)[10-1Y¿°dONLNdA
¬
V
Õ
[)
1
°dONLNdC
Μ
ŸÕ(
÷úListing 10-4°dONLNdP
ŒÍ
Ÿ)N
A0°dONLNdQ
Œ
Ÿ
„)> routine that loads and executes script data previously saved °dONLNdè
ÿÍ
„
ç(
‡Í)using a generic storage descriptor record`°dONLNd∫
ÿ
†
„
∑)∂10-16
°dONLNd¿
‰ú
ÔÕ(
ÏúListing 10-5°dONLNdÕ
‰Í
Ô)N
A0°dONLNdŒ
‰
Ô
Δ)9 routine that displays a compiled script for editing and °dONLNd
ÓÍ
˘
(
ˆÍrecompiles `°dONLNd
Ó

˘
).it˛–°dONLNd
Ó
.
˘
E)10-18
°dONLNd
˙úÕ(úListing 10-6°dONLNd)
˙Í)N
A0°dONLNd*
˙
g) function that loads and modifiãP°dONLNdI
˙
g
ˆ)w&es script data, then saves it using a °dONLNdoÍ
n(Í!generic storage descriptor recordÉê°dONLNdí
Ä
ó)ñ10-19
°dONLNdòúÕ(úListing 10-7.°dONLNd•Í)N
A
p°dONLNd¶
)     general LJ°dONLNdØ

ö)!"Apple event handler that uses the LJ°dONLNd—
ö
Ã)â
OSADoEventLJ°dONLNd€
Ã
Œ)2
 .
°dONLNd‹Í%
    ("Ífunction–°dONLNdÊ
%
3)210-21

I*O
¯4J*O
¯ KúK
¯

ˇ·ˇ‚7^
°dONLNdÏ=*IU(F*    Chapter 1®¿°dONLNdı=UIZ)+
1°dONLNd˜>úI
X)G"Program-to-Program Communications 1–°dONLNd>
YI
_)Ω
T±–°dONLNd>
^I
~)oolbox    °dONLNd">
ëI
ñ)3
1rP°dONLNd#>
ïI
¢)1-1
°dONLNd(Rú]Ã(ZúFigure 11-1°dONLNd4RÍ])N
A0°dONLNd5R]
) PPC Z0°dONLNd:R
]
)
T⁄0°dONLNd;R
]
≠)'oolbox session between two applicationse∞°dONLNddR
¿]
≈)µ
1º°dONLNdeR
ƒ]
—)1-5
°dONLNdi^úiÃ(fúFigure 11-2°dONLNdu^Íi¸)NThe Å °dONLNdy^¸i
+)icon for the É–°dONLNdÜ^
+i
_)/Sharing Setuàp°dONLNdí^
_i
ö)4p control panel冰dONLNd£^
¨i
±)M
1„°dONLNd§^
∞i
Ω)1-6
°dONLNd®júuÃ(rúFigure 11-3°dONLNd¥jÍu
k)NThe Sharing Setup control panelâ°dONLNd’j
}u
Ç)ì
1‡P°dONLNd÷j
Åu
é)1-6
°dONLNd⁄vúÅÃ(~úFigure 11-4°dONLNdÊvÍÅ
n)N!The session termination alert box°dONLNd    v
ÅÅ
Ü)ó
1[P°dONLNd
v
ÖÅ
í)1-7
°dONLNdÇúçÃ(äúFigure 11-5°dONLNdÇÍç
m)NThe users and groups dialog boxâ–°dONLNd;Ç
ç
Ñ)ï
1‡0°dONLNd<Ç
Éç
ê)1-8
°dONLNd@éúôÃ(ñúFigure 11-6°dONLNdLéÍô
a)NThe user termination alert boxÄ°dONLNdlé
tô
y)ä
1Y‡°dONLNdmé
xô
Ö)1-8
°dONLNdqöú•Ã(¢úFigure 11-7°dONLNd}öÍ•
9)NThe guest dialog boáp°dONLNdêö
9•
=)O
xp°dONLNdìö
P•
U)
1]–°dONLNdîö
T•
a)1-9
°dONLNdò¶ú±Ã(ÆúFigure 11-8°dONLNd§¶Í±
)NThe PPC Y°dONLNd¨¶
±
)'
TŸ°dONLNd≠¶
±
å)oolbox authentication process‚p°dONLNdö
û±
£)â
18–°dONLNdÕ¶
£±
µ)1-10ˇ%@@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
, (‡    xxi4^H¿,    Helvetica    °dONLNd\∫gÍ(d∫Figure 11-9°dONLNd\
g
‰)N4Database and spreadsheet applications using the PPC °dONLNd@f
q
*

T°dONLNdAf
q
')oolboxÇê°dONLNdIf
9q
>),
1ÿ°dONLNdJf
=q
O)1-13
°dONLNdOr∫}Ô(z∫Figure 11-10°dONLNd\r
}
)N
TÄ–°dONLNd]r
}
Ì)7wo Macintosh applications and their corresponding ports–°dONLNdñr})Û
1b0°dONLNdór})1-18
°dONLNdú~∫âÔ(Ü∫Figure 11-11°dONLNd©~
â
/)NThe PPC Y°dONLNd±~
/â
4)'
TŸ°dONLNd≤~
3â
‹)+oolbox and a dictionary service application‚∞°dONLNdfl~
Óâ
Û)ª
19°dONLNd‡~
Ûâ)1-20
°dONLNdÂä∫ïÔ(í∫Figure 11-12°dONLNdÚä
ï
É)NThe program linking dialog boxÑ∞°dONLNd
ä
ïï
ö)ç
1€°dONLNd
ä
ôï
´)1-22
°dONLNd
ñ∫°Ô(û∫Figure 11-13°dONLNd
%ñ
°
Õ)N2The program linking dialog box without a zone listàÄ°dONLNd
Yñ
fl°
‰)◊
1fi‡°dONLNd
Zñ
„°
ı)1-23
°dONLNd
_¢∫≠Ô(™∫Figure 11-14°dONLNd
l¢
≠
)N
Tˇ`°dONLNd
m¢
≠
u)he user identity dialog box܆°dONLNd
ä¢
à≠
ç){
1›°dONLNd
ã¢
å≠
û)1-30
°dONLNd
êÆ∫πÔ(∂∫Figure 11-15°dONLNd
ùÆ
π
ë)N!The incorrect password dialog boxÖÄ°dONLNd
¿Æ
£π
®)õ
1€‡°dONLNd
¡Æ
ßπ
π)1-31
°dONLNd
Δ∫∫≈Ô(¬∫Figure 11-16°dONLNd
”∫
≈
å)N The invalid user name dialog boxÜ°dONLNd
ı∫
û≈
£)ñ
1›P°dONLNd
ˆ∫
¢≈
¥)1-31
°dONLNd
˚Δ∫—Ô(Œ∫Figure 11-17°dONLNdΔ
—
)N
T™p°dONLNd    Δ
—
|)ransmitting message blocks≠°dONLNd%Δ
é—
ì)Å
1p°dONLNd&Δ
ì—
•)1-40
°dONLNd+“∫›Ô(⁄∫Figure 11-18°dONLNd8“
›
/)NThe PPC Y°dONLNd@“
/›
4)'
TŸ°dONLNdA“
3›
ï)oolbox parameter blocks›°dONLNdZ“
ß›
¨)t
13`°dONLNd[“
¨›
æ)1-47
°dONLNd`Í∫ıÎ(Ú∫Listing 11-1.°dONLNdmÍ
ı
V)NInitializing the PPC V°dONLNdÇÍ
Vı
[)N
TWê°dONLNdÉÍ
Zı
û)oolbox using the ,
CourierWê°dONLNdîÍ
ûı
¡)DPPCInitWê°dONLNdõÍ
¡ı
‰)#     functionWê°dONLNd¶Í
ˆı
˚)5
1≠ °dONLNdßÍ
˙ı)1-12
.
°dONLNd¨ˆ∫

Î(˛∫Listing 11-2°dONLNdπˆ



X)NOpening a PPC port°dONLNdÕˆ
k


p)c
1\P°dONLNdŒˆ
o


Å)1-21
°dONLNd”
∫
Î(

∫Listing 11-3°dONLNd‡



?)NUsing a port fi
‡°dONLNdÔ

@

n)8lter functionÉ¿°dONLNd˛

Ä

Ö)@
1⁄ °dONLNdˇ

Ñ

ñ)1-24
°dONLNd
∫
Î(
∫Listing 11-4°dONLNd



¨)N)Browsing through dictionary service ports†°dONLNd<

ø

ƒ)∑
1[°dONLNd=

√

’)1-26
°dONLNdB
∫
%Î(
"∫Listing 11-5.°dONLNdO


%
0)N
Using the °dONLNdY

0
%
l)(IPCListPorts°dONLNde

l
%
Í)<# function to obtain a list of ports°dONLNdä

¸
%
)ê
1’ê°dONLNdã

%)1-28
.
°dONLNdê
&∫
1Î(
.∫Listing 11-6.°dONLNdù
&

1
0)N
Using the °dONLNdß
&
0
1
ä)(StartSecureSession°dONLNdπ
&
ä
1
Á)Z function to establish a .
°dONLNd“
0

;
&(
8
session
¿°dONLNd€
0
9
;
>)1
1X °dONLNd‹
0
=
;
O)1-32
°dONLNd·
<∫
GÎ(
D∫Listing 11-7.°dONLNdÓ
<

G
})NInitiating a session using the °dONLNd
<
}
G
•)uPPCStart°dONLNd
<
•
G
»)(     function°dONLNd 
<
⁄
G
fl)5
1’ê°dONLNd!
<
fi
G
)1-34
.
°dONLNd&
H∫
SÎ(
P∫Listing 11-8.°dONLNd3
H

S
0)N
Using the °dONLNd=
H
0
S
])(    PPCInform°dONLNdF
H
]
S
Ï)-& function to enable a port to receive .
°dONLNdl
R

]
+(
Z
sessionsÅ¿°dONLNdv
R
=
]
B)5
1ÿ °dONLNdw
R
A
]
S)1-36
°dONLNd|
^∫
iÎ(
f∫Listing 11-9.°dONLNdâ
^

i
i)NCompletion routine for a °dONLNd¢
^
i
i
ñ)a    PPCInform°dONLNd´
^
ñ
i
π)-     function°dONLNd∂
^
À
i
–)5
1’ê°dONLNd∑
^
œ
i
·)1-37
.
°dONLNdº
j∫
u(
r∫Listing 11-10.°dONLNd 
j

u
§)N&Accepting a session request using the °dONLNd
j
§
u
—)ú    PPCAccept°dONLNd˘
j
—
u
”)-
 .
°dONLNd˙
t


'(
|
function–°dONLNd
t
:

?)2
1Y0°dONLNd
t
>

P)1-38
°dONLNd

Ä∫
ã(
à∫Listing 11-11.°dONLNd
Ä

ã
i)NCompletion routine for a °dONLNd1
Ä
i
ã
ñ)a    PPCAccept°dONLNd:
Ä
ñ
ã
π)-     function°dONLNdE
Ä
À
ã
–)5
1’ê°dONLNdF
Ä
œ
ã
·)1-38
.
°dONLNdK
å∫
ó(
î∫Listing 11-12.°dONLNdY
å

ó
°)N&Rejecting a session request using the °dONLNd
å
°
ó
Œ)ô    PPCReject°dONLNdà
å
Œ
ó
–)-
 .
°dONLNdâ
ñ

°
'(
û
function–°dONLNdì
ñ
:
°
?)2
1Y0°dONLNdî
ñ
>
°
P)1-39
°dONLNdô
¢∫
≠(
™∫Listing 11-13.°dONLNdß
¢

≠
i)NCompletion routine for a °dONLNd¿
¢
i
≠
ñ)a    PPCReject°dONLNd…
¢
ñ
≠
π)-     function°dONLNd‘
¢
À
≠
–)5
1’ê°dONLNd’
¢
œ
≠
·)1-39
.
°dONLNd⁄
Æ∫
π(
∂∫Listing 11-14.°dONLNdË
Æ

π
0)N
Using the °dONLNdÚ
Æ
0
π
S)(PPCRead°dONLNd˘
Æ
S
π
Ï)#' function to read data during a session°dONLNd"
Æ
˛
π)´
1’ê°dONLNd#
Æ
π)1-41
.
°dONLNd(
∫∫
≈(
¬∫Listing 11-15.°dONLNd6
∫

≈
4)NPolling the °dONLNdB
∫
4
≈
\),ioResult°dONLNdJ
∫
\
≈
c)( fi°dONLNdM
∫
c
≈
≥)eld to determine if a °dONLNdc
∫
≥
≈
÷)PPPCRead°dONLNdj
∫
÷
≈)# function has .
°dONLNdx
ƒ

œ
1(
Ã
    completed0°dONLNdÉ
ƒ
D
œ
I)<
1Xê°dONLNdÑ
ƒ
H
œ
Z)1-41
°dONLNdâ
–∫
€(
ÿ∫Listing 11-16.°dONLNdó
–

€
0)N
Using the °dONLNd°
–
0
€
X)(PPCWrite°dONLNd©
–
X
€
“)(! function to write data during a .
°dONLNd 
⁄

Â
&(
‚
session
¿°dONLNd”
⁄
9
Â
>)1
1X °dONLNd‘
⁄
=
Â
O)1-42
°dONLNdŸ
Ê∫
Ò(
Ó∫Listing 11-17.°dONLNdÁ
Ê

Ò
)NPo°dONLNdÈ
Ê

Ò
4)
lling the °dONLNdÛ
Ê
4
Ò
\)!ioResult°dONLNd˚
Ê
\
Ò
c)( fi°dONLNd˛
Ê
c
Ò
≥)eld to determine if a °dONLNd
Ê
≥
Ò
€)PPPCWrite°dONLNd
Ê
€
Ò)( function has .
°dONLNd*


˚
1(
¯
    completed0°dONLNd5

D
˚
I)<
1Xê°dONLNd6

H
˚
Z)1-43
°dONLNd;
¸∫(∫Listing 11-18.°dONLNdI
¸

ä)NEnding a PPC session using the °dONLNdh
¸
ä
®)ÇPPCEnd°dONLNdn
¸
®
À)     function°dONLNdy
¸
›
‚)5
1’ê°dONLNdz
¸
·
Û)1-43
.
°dONLNd∫(∫Listing 11-19.°dONLNdç

|)NClosing a PPC port using the °dONLNd™
|
§)tPPCClose°dONLNd≤
§
«)(     function°dONLNdΩ
Ÿ
fi)5
1’ê°dONLNdæ
›
Ô)1-44
.
°dONLNd√∫(∫Listing 11-20.°dONLNd—

0)N
Using the °dONLNd€
0
ä)(DeleteUserIdentity°dONLNdÌ
ä
˝)Z function to invalidate a user .
°dONLNd
)
$(&
identity
P°dONLNd
7)
<)/
1W∞°dONLNd
;)
M)1-45

MHS4NHS O∫O

ˇ·ˇ‚7^
°dONLNdAHMy(JH
Chapter 12°dONLNd'B∫M‘)rData /°dONLNd,B‘M
%)Access Manager    –°dONLNd<B
8M
J)d12-1
°dONLNdBV∫aÍ(^∫Figure 12-1°dONLNdNV
a
)N
A0°dONLNdOV
a
}) connection with a databaseå`°dONLNdlV
èa
°)Å12-6
°dONLNdqb∫mÍ(j∫Figure 12-2°dONLNd}b
m
`)NUsing high-level Data –°dONLNdìb
`m
≈)XAccess Manager routinesàp°dONLNd¨b
◊m
È)w12-8
°dONLNd±n∫yÍ(v∫Figure 12-3°dONLNdΩn
y
\)NUsing low-level Data ÅÄ°dONLNd“n
\y
¡)TAccess Manager routines °dONLNdÎn
‘y
Î)x12-10
°dONLNdÒz∫ÖÍ(Ç∫Figure 12-4°dONLNd˝z
Ö
)N
A0°dONLNd˛z
Ö
) flP°dONLNd    
z
Ö
‹)3owchart of a session using the high-level interface°dONLNd    6z
ÓÖ)Ÿ12-15
°dONLNd    <Ü∫ëÍ(é∫Figure 12-5°dONLNd    HÜ
ë
)N
A0°dONLNd    IÜ
ë
) flP°dONLNd    LÜ
ë
ÿ)2owchart of a session using the low-level interface䆰dONLNd    ÄÜ
Íë
)’12-29
°dONLNd    Üí∫ùÍ(ö∫Figure 12-6°dONLNd    íí
ù
)N
A0°dONLNd    ìí
ù
|) query document dialog boxä0°dONLNd    Øí
éù
•)Ä12-47
°dONLNd    µû∫©Í(¶∫Figure 12-7°dONLNd    ¡û
©)N?The relationship between resources in a query document and the °dONLNd
®
≥
:*
query record
°dONLNd
®
M≥
d)E12-49ˇê@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*ˇ
¯,Palatino

.
(·*xxii4^*¿
¯,    Helvetica    °dONLNd\úgÃ(dúFigure 12-8°dONLNd\Íg
Ä)N$The relationship between a query defiäP°dONLNd1\
Äg
À)ñnition function and °dONLNdEfÍq
(nÍqueries
@°dONLNdNf
q
1)012-50
°dONLNdTrú}Ã(zúFigure 12-9.°dONLNd`rÍ}
e)NStructure of a compiled query (,
Courier°dONLNdr
e}
É){'qrsc'°dONLNdÖr
É}
¨)
) resource°dONLNdër
æ}
’);12-90
.
°dONLNdó~úâ—(ÜúFigure 12-10.°dONLNd§~Íâ
~)N&Structure of a compiled query string (°dONLNd ~
~â
ú)î'wstr'°dONLNd–~
úâ
≈)
) resource°dONLNd‹~
׉
Ó);12-91
.
°dONLNd‚ñú°»(ûú
Table 12-1°dONLNdÌñÍ°
&)NData types defiÑ∞°dONLNd¸ñ
&°
h)<ned by the Data ∞°dONLNd
ñ
h°
´)BAccess Manager–°dONLNd
ñ
Ω°
‘)U12-38
°dONLNd
"ÆúπÕ(∂úListing 12-1°dONLNd
/ÆÍπ
^)NUsing the high-level interfaceÑê°dONLNd
OÆ
pπ
á)Ü12-18
°dONLNd
U∫ú≈Õ(¬úListing 12-2°dONLNd
b∫Í≈Ô)N
TÄ–°dONLNd
c∫Ô≈
K)wo completion routinesÑ°dONLNd
{∫
]≈
t)n12-21
°dONLNd
ÅΔú—Õ(ŒúListing 12-3°dONLNd
éΔÍ—)N
A0°dONLNd
èΔ—
H) sample status routine@°dONLNd
ßΔ
Z—
q)j12-26
°dONLNd
≠“ú›Õ(⁄úListing 12-4°dONLNd
∫“Í›
Q)NSending a query fragmentP°dONLNd
‘“
d›
{)z12-31
°dONLNd
⁄fiúÈÕ(ÊúListing 12-5°dONLNd
ÁfiÍÈ
Z)NUsing the low-level interface@°dONLNdfi
mÈ
Ñ)É12-33
°dONLNdÍúıÕ(ÚúListing 12-6°dONLNdÍÍı)N
A0°dONLNdÍı
)) result handler@°dONLNd+Í
;ı
R)K12-45
°dONLNd1ˆú

Õ(˛úListing 12-7°dONLNd>ˆÍ

)N
A0°dONLNd?ˆ


)
 query defi0°dONLNdJˆ



Q)*nition functionâP°dONLNd[ˆ
c


z)I12-52ˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
Ñ`(·xxiii    3,Ã(#∫PREFN )3ACE 4^H¿

vHú4vHú óHó

ˇ·ˇ‚7^ˇˇ¬òˇ◊°dONLNd\∫u
i(n∫About This Book
°dONLNdú∫®Ë*7
This book,ô@°dONLNdúË®Í).
 @°dONLNdúή
∫)0Inside Macintosh: Interapplication CommunicationA °dONLNdMú
∫®
˙)œ, describes the °dONLNd]©∫µ
S(≤∫!interapplication communication ar‰¿°dONLNd~©
Sµ
y)ô    chitecturôÄ°dONLNdá©
zµ
´)'e, which pr¸†°dONLNdí©
´µ
Û)1ovides a standarT†°dONLNd¢©
Ùµ)Id and °dONLNd®∂∫¬
ü(ø∫.extensible mechanism for communication among M‰`°dONLNd÷∂
ü¬
¯)Âacintosh applicationÄ°dONLNdÍ∂
˘¬)Zs. °dONLNdÌ√∫œ
(Ã∫This book also deôÄ°dONLNd˛√
œ
z)Mscribes the system softwar[@°dONLNd
√
{œ
Ü)te ri‡°dONLNd
√
ܜ
˛)outines that you can use to °dONLNd
7–∫‹Ê(Ÿ∫implemen_Ä°dONLNd
?–Á‹
Î)-:t various forms of interapplication communication in your °dONLNd
y›∫ÈÓ(Ê∫application.°dONLNd
ÜÔ∫˚fl*    If you ar °dONLNd
èÔ‡˚
)&e new to prΩ¿°dONLNd
öÔ
˚
¡)1#ogramming on the Macintosh computer3‡°dONLNd
ΩÔ
¡˚
˙)∞, you should °dONLNd
 ¸∫
Ω(
∫
rE°dONLNd
À¸æ
«)ea†°dONLNd
Õ¸»
–)
d ™`°dONLNd
œ¸–
”)
I˛@°dONLNd
–¸”

D)nside Macintosh: Overview }‡°dONLNd
͸
E

q)rfor an intrÃ`°dONLNd
ı¸
q

˝), oduction to general concepts of °dONLNd
    ∫
Ù(
∫Macintosh pr,†°dONLNd!
    ı

-);ogramming; ¿°dONLNd,
    
.

¨)9Inside Macintosh: Macintosh Tg@°dONLNdI
    
´

Ô)}oolbox Essentials,@°dONLNdZ
    


)E for °dONLNd_
∫
"
≠(
∫3information on how to use menus, windows, and contrzÄ°dONLNdí

≠
")Ûols in your application`°dONLNd©

")d
;Ñ`°dONLNd™

")
 °dONLNd´
#∫
/Õ(
,∫and Ì °dONLNdØ
#Õ
/
o)%Macintosh Human Interface Guidelines |¿°dONLNd‘
#
p
/)£"for a complete discussion of user °dONLNdˆ
0∫
<
È(
9∫Einterface guidelines and principles that every Macintosh application °dONLNd;
=∫
Iÿ*should °dONLNdA
=Ÿ
I€)
 è °dONLNdB
=€
I˜)follow
¿°dONLNdH
=˜
I˘)
.°dONLNdJ
O∫
[
Â(
X∫AThis book describes how to implement publish and subscribe featurª °dONLNdã
O
Â
[(
X
Âes in your °dONLNdñ
\∫
h
‘(
e∫>application, how to communicate with other applications using 톰dONLNd‘
\
‘
h(
e
‘Apple events, °dONLNd‚
i∫
ufl(
r∫how to rö¿°dONLNdÍ
ifl
u
˜)%>espond to scripts, and how to exchange information with other °dONLNd(
v∫
Ç
9(
∫applications using the PPC T>@°dONLNdD
v
9
Ç)/oolbox. It also discusses how your application °dONLNds
É∫
è
(
å∫can use the Data N°dONLNdÑ
É

è
∂)K'Access Manager to access information fr˚†°dONLNd´
É
∂
è
˜)±om a database °dONLNdπ
ê∫
ú
=(
ô∫application or other data sour¡@°dONLNd◊
ê
=
ú
H)Éce.°dONLNd€
¢∫
Æ
H(
´∫!For an overview of all the featurs`°dONLNd¸
¢
H
Æ
])ées pr¡ °dONLNd

¢
]
Æ
Â)ovided by the interapplication °dONLNd 
Ø∫
ª

(
∏∫communication arıÄ°dONLNd0
Ø


ª
0)P    chitectur™@°dONLNd9
Ø
1
ª
)'e, see the chapter „‡°dONLNdL
Ø

ª
î)N“Intr °dONLNdQ
Ø
ï
ª)oduction to Interapplication °dONLNdn
º∫
»
(
≈∫Communication”W@°dONLNd|
º

»
?)M in this book.°dONLNdã
κ
⁄¿(
׺
Tµ¿°dONLNdå
ο
⁄–)o prr`°dONLNdê
Œ—
⁄
û).ovide support for publish and subscribe featur9 °dONLNdæ
Œ
ü
⁄)Œes in your application, °dONLNd÷
€∫
Á«(
‰∫seeP@°dONLNdŸ
€»
Á )
 –@°dONLNd⁄
€ 
Á˛)the chapter °dONLNdÊ
€˛
Á
R)4“Edition Manager”ìÄ°dONLNd˜
€
S
Á    )U* in this book. This chapter describes how °dONLNd!
Ë∫
Ù
j(
Ò∫(your application can allow users to shar‹¿°dONLNdI
Ë
j
Ù
Ì)∞e dynamic data among many °dONLNdc
ı∫
Ì(
˛∫
documents.°dONLNdn∫¿*
Tµ¿°dONLNdoø
ñ)/o communicate with other applications by using H°dONLNdû
ó
—)ÿApple eventsœ¿°dONLNd™
—
‹):, fi‹Ä°dONLNdÆ
‹
˙)rst see °dONLNd∂∫ Ω(∫
t¬`°dONLNd∑Ω «)he]`°dONLNdπ»  )
 ›`°dONLNd∫  Î)chapter¿°dONLNd¡Ï Ó)"
 ü¿°dONLNd¬Ó 
)“Intr◊°dONLNd«
 
8)oduction to ™¿°dONLNd”
8 
x)5Apple Events”ц°dONLNd‡
y 
≈)A for a general intr–Ä°dONLNdÛ
≈ 
Ó)L    oduction °dONLNd¸!∫-¬(*∫to7‡°dONLNd˛!√-≈)    
 YÄ°dONLNdˇ!≈-ˇ)Apple events·@°dONLNd!ˇ-
):. For information on how to ruÄ°dONLNd(!
Ä-
¬)Åespond to the rª °dONLNd7!
¬-
Ÿ)Bequir“`°dONLNd<!
Ÿ-
Ê)ed °dONLNd?.∫:◊(7∫Apple }Ä°dONLNdE.ÿ:
)
events, se`°dONLNdO.
:
>)+e the chapter w¿°dONLNd].
>:
Ü);“Responding to 3Ä°dONLNdl.
Ü:
…)HApple Events.”ç`°dONLNdz.
…:
—)C TC °dONLNd|.
—:
·)o crm‡°dONLNdÄ.
·:
ı)eate °dONLNdÖ;∫G (D∫andm °dONLNdà;ÀGÕ)
 Ì °dONLNdâ;ÕG‰)send Ä°dONLNdé;ÂG
h)Apple events, see the chapter ˙@°dONLNd¨;
hG
x)É“Cr÷@°dONLNdØ;
xG
–)eating and Sending y@°dONLNd¬;
–G)XApple Events.”°dONLNd—M∫Y¿(V∫
Y@Ä°dONLNd“M¿Y
Ø)8ou can choose to write your application so that it can ró °dONLNd
M
ØY
–)Ôecognizè`°dONLNdM
—Y)"e descriptions, °dONLNd!Z∫f≈(c∫in [`°dONLNd$Z≈f
¥)7Apple events, of objects in the application such as wor€‡°dONLNd[Z
¥f
˙)Ôds, paragraphs, °dONLNdkg∫s
(p∫shapes, or documents.ˆ@°dONLNdÄg
s
$)b T¨°dONLNdÇg
$s
ç)o do so, see the chapter ’@°dONLNdõg
çs
fi)i“Resolving and Cr†°dONLNd¨g
fls
¸)Reating °dONLNd≥t∫Ĉ(}∫Object Specifiß`°dONLNd¡tˆÄ
)<er Recor°dONLNd…t
Ä
,)%ds.”°dONLNdŒÜ∫í
,(è∫In addition to supporting ÷†°dONLNdËÜ
,í
à)rApple events, you caZ`°dONLNd¸Ü
âí
±)]n make yÁ†°dONLNd    Ü
±í
Ó)(our applicatioº`°dONLNd    Ü
Ôí
˜)>n °dONLNd    ì∫üæ(ú∫
sΩ°dONLNd    ìæüfl)criptablº¿°dONLNd    ì‡üÚ)"e—t»¿°dONLNd     ìÚü
B)hat is, capable of rº@°dONLNd    4ì
Bü
~)Pesponding to  °dONLNd    Aì
~ü
Ò)<Apple events sent to it by °dONLNd    \†∫¨ø(©∫
a°dONLNd    ]†ø¨¡)
 °dONLNd    ^†¬¨
)Lscripting component. By executing scripts, users of scriptable applications °dONLNd    ™≠∫π…(∂∫can¡†°dONLNd    ≠≠…πÀ)
 A†°dONLNd    Æ≠Ãπ¸)
automate r%†°dONLNd    ∏≠¸π
ˆ)0;epetitive tasks or conditional tasks that involve multiple ˇ"@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*˙
¯,Palatino

.
(·*xxiv    3,Ã(#úPREFN )3ACE 4^*¿
¯
°dONLNd\úh˙(eúapplications. For mor˘†°dONLNd\˙h

)^e C@°dONLNd\
h
%)general í°dONLNd\
%h
Y)#informationM`°dONLNd*\
Zh
ü)5 about scripting©†°dONLNd:\
üh
Ë)E, see the chapter °dONLNdLiúu±(rú“Intr∑@°dONLNdQi±u
)oduction to Scripting.”Å¿°dONLNdhi
u
])e See the chapter tÄ°dONLNdyi
^u
£)H“Apple Event T« °dONLNdái
¢u
◊)Derminology °dONLNdívúǪ(úResourv@°dONLNdòvªÇÕ)ces”Ì °dONLNdúvÕÇ
8) for information on the rÕ¿°dONLNdµv
8Ç
P)kesour°dONLNd∫v
QÇ
‘)ces your application needs to °dONLNdÿÉúè•(åúprG °dONLNd⁄ɶè÷)
ovide in or$‡°dONLNdÂÉ÷è
,)0der to be scriptable.°dONLNd˚ïú°¢(ûú
Y@Ä°dONLNd¸ï¢°
@)#ou can also make your application r@†°dONLNd
ï
@°
R)ûecorµ°dONLNd
#ï
R°
¬)dable, that is, capable of r@@°dONLNd
?ï
√°
’)qecor¥†°dONLNd
Cï
’°
Û)ding a °dONLNd
J¢úÆØ(´úuser=¿°dONLNd
N¢∞Æ
()’s actions for later playbackÄ°dONLNd
k¢
)Æ
Q)y    . For morä@°dONLNd
t¢
QÆ
è)(e information,@°dONLNd
Ç¢
êÆ
÷)? see the chapter °dONLNd
ìØúª∫(∏ú“Recor¢`°dONLNd
ôØ∫ª–)ding (†°dONLNd
ûØ—ª
)Apple Events.”°dONLNd
≠¡úÕ°( ú
F °dONLNd
Æ¡¢Õ
™);or information on how your application can execute a scriptö@°dONLNd
È¡
™Õ
ˆ( 
™ with the aid of a °dONLNd
¸Œú⁄˘(◊úscripting component,u¿°dONLNdŒ˙⁄
@)^ see the chapter e¿°dONLNd!Œ
A⁄
∞)G“Scripting Components.”°dONLNd9‡úÏ
>(Èú$Although you’ll usually want to use A`°dONLNd]‡
>Ï
€)¢!Apple events to communicate with °dONLNd~Ìú˘≥(ˆúother≈Ä°dONLNdÉÌ≥˘µ)
 EÄ°dONLNdÑÌ∂˘
g))applications, if you need low-level contr”@°dONLNd≠Ì
g˘
Ï)±ol of communication between °dONLNd…˙ú

%(
úapplications you can use the Pr˚°dONLNdË˙
%

[)âogram-to-PrÙÄ°dONLNdÛ˙
[

Â)6ogram Communications (PPC) °dONLNd
ú
¢(
ú
Tµ¿°dONLNd
°
Á)oolbox. For mor4†°dONLNd
Ë

m)Ge information, see the chapter ©†°dONLNd=

m

{)Ö“Prx@°dONLNd@

|

≤)ogram-to-Prq¿°dONLNdK

≤

—)6ogram °dONLNdQ
ú
 (
úCommunications TJ°dONLNda

 
)Toolbox.”°dONLNdj
&ú
2
"(
/úApplications can use the Data â °dONLNdà
&
"
2
”)Ü'Access Manager to access information fr6¿°dONLNdØ
&
‘
2
‰)≤om °dONLNd≤
3ú
?°(
<ú
a°dONLNd≥
3°
?£)
 °dONLNd¥
3§
?
P)'database application or other data sour≠†°dONLNd€
3
P
?
¬)¨ce. For example, a user in °dONLNdˆ
@ú
L¨(
IúSanë °dONLNd˘
@¨
LÆ)
  °dONLNd˙
@Ø
L
)Francisco might use a sprP¿°dONLNd
@

L
ã)peadsheet application to rÕ‡°dONLNd,
@
ã
L
«)lequest data fr˜¿°dONLNd:
@
«
L
fl)<om a °dONLNd?
Mú
Y
(
Vúcompany database in New Ñ`°dONLNdW
M

Y
)x
YD‡°dONLNdX
M

Y
O)ork. The spr|°dONLNdd
M
O
Y
œ)5eadsheet application can use °dONLNdÅ
Zú
f©(
cúthe]`°dONLNdÑ
Z™
f¨)
 ›`°dONLNdÖ
Z¨
f¿)Data›°dONLNdâ
Z¡
f√)
 ˛†°dONLNdä
Z√
f
)Access Manager to rx‡°dONLNdù
Z

f
i)Zequest the data fr °dONLNdØ
Z
j
f
 )Mom the database. The °dONLNdƒ
gú
s¬(
púdatabasel`°dONLNdÃ
g√
s≈)'
 Ï`°dONLNdÕ
g≈
s
)application in New ‡°dONLNd‡
g

s
#)X
Yfl`°dONLNd·
g
"
s
z)ork sends back the r0¿°dONLNdı
g
{
s
–)Yequested data, and °dONLNd
tú
Ä©(
}úthe]`°dONLNd
t™
Ĩ)
 ›`°dONLNd
t¨
Ä∫)spr·Ä°dONLNd
t∫
Ä
Ì)Geadsheet application can then use this data to generate a graph of the °dONLNdV
Åú
ç
i(
äú-information. For information on sending and r£†°dONLNdÉ
Å
i
ç
—)Õetrieving information fr†°dONLNdõ
Å
“
ç
Í)iom a °dONLNd†
éú
ö≈(
óú    data sour‹¿°dONLNd©
é≈
ö
))ce, see the chapter ܆°dONLNdΩ
é

ö
4)S“Data ߇°dONLNd√
é
4
ö
{)Access ManagerÁ‡°dONLNd—
é
{
ö
Ç)G.”°dONLNd‘
†ú
¨æ(
©úFor defiÈ`°dONLNd‹
†æ
¨
)"nitions of specifiâ@°dONLNdÓ
†

¨
)Ic  °dONLNd
†

¨
^)Apple events and 1†°dONLNd

†
^
¨
«)PApple event objects, seeŸ¿°dONLNd
†
«
¨
…)i
 Y¿°dONLNd
†
 
¨
⁄)the °dONLNd
≠ú
π≥(
∂úApplec°dONLNd#
≠¥
π∂)
 „°dONLNd$
≠∂
πÈ)Event Regist”@°dONLNd0
≠Í
π
8)4ry: Standard Suitesm¿°dONLNdC
≠
9
π
;)O
,Ì¿°dONLNdD
≠
;
π
n) available fr∑@°dONLNdQ
≠
o
π
)4om "`°dONLNdT
≠
Ä
π
ü)APDA.°dONLNdZ
øú
À
"(
»úFor information on handling fiv°dONLNdx
ø
#
À
Ä)áles in your applicatiodž°dONLNdé
ø
Ä
À
ç)]n a‘°dONLNdë
ø
ç
À
‚)nd a description of °dONLNd•
Ãú
ÿÈ(
’úaliases and alias r‘@°dONLNd∏
ÃÈ
ÿ˚)MecorH†°dONLNdº
ø
ÿ
)ds, see Ò†°dONLNdƒ
Ã

ÿ
x)Inside Macintosh: Files∏Ä°dONLNd€
Ã
y
ÿ
{)^
.°dONLNd›
fiú
͸(
ÁúFor information on pr¿†°dONLNdÚ
fi¸
Í
<)`ocesses and pr§‡°dONLNd
fi
<
Í
¨)@ocess serial numbers, see °dONLNd
Îú
˜¥(
ÙúInsideÒÄ°dONLNd 
Î¥
˜∂)
 qÄ°dONLNd!
Î∑
˜‰)
Macintosh:‚°dONLNd+
Ή
˜Ê)-
 b°dONLNd,
ÎÁ
˜)Pr3¿°dONLNd.
ÎÒ
˜
)
ocesses(°dONLNd5
Î

˜
)
.


˛*
¯4
ˇ*
¯

)*1
¯4**1
¯ +*+
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNd8*)ä($*Format of a T™∫°dONLNdEâ)Û)_ypical ChapterˇˇˇˇˇˇV˛($

0
°dONLNdU:úF
r(Cú1Almost all chapters in this book follow a standar’`°dONLNdÜ:
rF
Ü)÷d strœ °dONLNdã:
ÜF
ù)ucturU°dONLNdê:
ûF
Ù)e. For example, the °dONLNd§GúSø(Púchapter B`°dONLNd¨G¿S–)$“Cr`°dONLNdØG–S
()eating and Sending ¡`°dONLNd¬G
'S
g)WApple Events”õ@°dONLNdœG
hS
–)A contains these sections:,Zapf Dingbats°dONLNdÈ]úd°(cú
n
°dONLNdÎZ®f∏)“Cr\°dONLNdÓZ∏f„)
eating an #‡°dONLNd¯Z„f
)+Apple Event”¿¿°dONLNdZ
f
2)< and-‡°dONLNdZ
3f
5)
 ≠‡°dONLNd    Z
5f
n)“Sending an `@°dONLNdZ
nf
≠)9Apple Event.”} °dONLNd"Z
≠f
À)? These °dONLNd)f®rÀ(o®sections•Ä°dONLNd1fÀrÕ)#
 %Ä°dONLNd2fŒr
q)$describe how your application can cr.`°dONLNdVf
qr
∞)£eate and send Ä°dONLNddf
∞r
Ô)?Apple events. °dONLNdrr®~¯({®They describe the à¿°dONLNdÑr¯~
`)PApple Event Manager r|†°dONLNdôr
`~
ÿ)houtines that you can use to °dONLNdµ~®ä
*(á®accomplish these tasks, give rÁ °dONLNd”~
*ä
ø)Ç#elated user interface information, B¿°dONLNdˆ~
¿ä
”)ñand °dONLNd˙ä®ñ±(ì®prG °dONLNd¸ä≤ñ
)
ovide code sample¿‡°dONLNd    ä
ñ
)Rs a}‡°dONLNd    ä
ñ
)
nO@°dONLNd    ä
ñ
#)d aΰdONLNd    ä
#ñ
Ç)dditional information†@°dONLNd    )ä
Éñ
Ö)`
.°dONLNd    +üú¶°(•ú
n
°dONLNd    -ú®®ƒ)“Refer⁄ °dONLNd    3úƒ®)
ence to CrB‡°dONLNd    =úÒ®
I)-eating and Sending ‡°dONLNd    Pú
H®
ã)WApple Events.”?¿°dONLNd    ^ú
å®
é)D
 ø¿°dONLNd    _ú
é®
Œ)This section pr܇°dONLNd    nú
Ϩ
ˆ)A    ovides a °dONLNd    w®®¥÷(±®
complete r>‡°dONLNd    Å®◊¥Á)/eferΰdONLNd    Ö®Á¥
)ence to the v¿°dONLNd    ë®
¥
Å)2Apple Event Manager rj†°dONLNd    ¶®
Å¥
ù)houtine≠°dONLNd    ¨®
ù¥
©)s y˘ °dONLNd    Ø®
©¥
Â)ou can use to °dONLNd    Ω¥®¿∞(Ω®crµ@°dONLNd    ø¥∞¿Ô)eate and send ç`°dONLNd    Õ¥Ô¿
%)?Apple eventÿ °dONLNd    ÿ¥
%¿
+)6s.ï °dONLNd    ⁄¥
,¿
J) Each r∑Ä°dONLNd    ·¥
J¿
€)"outine description also follows a ˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
‡(·xxv    3,Ã(#∫PREFN )3ACE 4^H¿
°dONLNd\ΔhÁ(eΔstandar±Ä°dONLNd\Áh
:)!d format, which prπ °dONLNd\
:h
k)Sesents the r|Ä°dONLNd%\
lh
˝)2!outine declaration followed by a °dONLNdFhΔt
p(qΔ'description of every parameter of the r‚¿°dONLNdmh
pt
∞)™outine. Some rΩ°dONLNd{h
∞t)@outine descriptions °dONLNdètΔÄ(}ΔHalso give additional descriptive information, such as assembly-language °dONLNd◊ÄΔå
*information or rhÄ°dONLNdÁÄ
å
@)Gesult codes.,Zapf Dingbats°dONLNdÙï∫úø(õ∫
n
°dONLNdˆíΔû
)“Summary of Crñ°dONLNd
í
û
g)Ieating and Sending 9°dONLNd
í
gû
™)XApple Events.”퇰dONLNd
%í
™û
Ì)C This section pr⁄°dONLNd
5í
Ìû)Covides °dONLNd
<ûΔ™
≠(ßΔ7the Pascal and C interfaces for the constants, data str`†°dONLNd
sû
Æ™
≈)ËucturÊÄ°dONLNd
xû
≈™
÷)es, r≤ °dONLNd
}û
◊™)outines, and °dONLNd
ä™Δ∂…(≥Δ
rE°dONLNd
ã™ ∂
T) esult codes associated with the G†°dONLNd
´™
T∂
º)äApple Event Manager r;Ä°dONLNd
¿™
º∂
ˆ)houtines for cr¨ °dONLNd
Ϊ
ˆ∂):eating °dONLNd
’∂Δ¬ˇ(øΔand sending K`°dONLNd
·∂ˇ¬
á)9 Apple events. It also includes rè¿°dONLNd
∂
á¬
)àelevant assembly-language °dONLNd¬ΔŒ
&(ÀΔinterface information.

‘HÔ4’HÔ

ˇH
4
H
 

H



ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNd3ÏHˇ
+(˙HConventions Used in This BookˇˇˇˇˇˇV˛(˙
0
°dONLNdR
∫
ˇ(
∫Inside Macintoshb°dONLNdb



â)F uses various conventions to pr熰dONLNdÅ

â

Ê)âesent information. W¬°dONLNdï

Â

Ó)\or¸Ä°dONLNdó

Ó
)    ds that °dONLNdü
∫
)Ω(
&∫
rE°dONLNd†
æ
)’)equir\@°dONLNd•
’
)
)e special trw°dONLNd±


)
s)/eatment appear in specifiú¿°dONLNd 

s
)
Ù)o c fonts or font styles. Certain °dONLNdÍ
*∫
6
](
3∫&information, such as the contents of r˝¿°dONLNd
*
]
6)£*egisters, use special formats so that you °dONLNd:
7∫
C
(
@∫can scan them quicklyU`°dONLNdO
7

C
)a
.


hH
o4
iH
o 
j∫
jF

ˇ·ˇ‚7^,    Helveticaˇˇ‹.ˇ◊°dONLNdQ
Y∫
h
(
d∫Special Fontsˇˇˇˇˇˇ€r(
d
0
°dONLNd`
o∫
{

(
x∫All code listingsπ °dONLNdq
o


{
    )G, r~ °dONLNdt
o


{
@)    eserved worfi °dONLNd
o
@
{
‹)6$ds, and the names of actual data str’°dONLNd£
o
‹
{
Û)úucturZ‡°dONLNd®
o
Ù
{)es, .°dONLNd¨
|∫
à¡(
Ö∫
fi°dONLNdÆ
|¡
à
W)"elds, constants, parameters, and rR`°dONLNd–
|
W
à
É)ñ
outines ar$¿°dONLNd⁄
|
É
à
‹),e shown in Courier (,
Courier$¿°dONLNdÓ
|
‹
à)Ythis is °dONLNdˆ
â∫
ï‰(
í∫Courier°dONLNd˝
â‰
ïÎ)*)..
°dONLNd
õ∫
߃(
§∫
Wï°dONLNd

õ√
ßÃ)    orœÄ°dONLNd
õÃ
ß
)    ds that appear in 
¯†°dONLNd
õ

ß
@)Mboldfaceg°dONLNd
õ
A
ß
L)( ar¨°dONLNd 
õ
L
ß
“)e key terms or concepts and ar˘‡°dONLNd>
õ
“
ß
Í)Üe defi5†°dONLNdD
õ
Î
ß    )ned in °dONLNdK
®∫
¥Ò(
±∫the Glossaryº`°dONLNdW
®
¥Ú)6
.


ŸH
‡4
⁄H
‡ 
€∫
€F

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdY
 ∫
Ÿ¬(
’∫
T$é°dONLNdZ
 ¬
Ÿ
)ypes of Notesˇˇˇˇˇˇ€r(
’
0
°dONLNdi
‡∫
ό(
È∫Ther¿°dONLNdm
‡œ
Ïfl)e ar`°dONLNdq
‡fl
Ï
ï)+e several types of notes used in this book.


˙H4
˚H
    °dONLNdù
˘∫Õ(
∫Note

ˇ·ˇ‚7^
°dONLNd¢∫¡*
A∫†°dONLNd£¡
è)2 note like this contains information that is inter"°dONLNd’
ê
ˆ)œesting but possibly not °dONLNdÌ∫
Ô(∫Eessential to an understanding of the main text. (An example appears oÊ@°dONLNd2
Ô
˜(
Ôn °dONLNd4∫*—('∫page Z‡°dONLNd9“*‰)3-26Æ¿°dONLNd=‰*Ê)
..¿°dONLNd>Á*Í)
)dž°dONLNd@!Ô)ı)
u

7HE48HE
°dONLNdB8∫@Ÿ(>∫IMPORTÄ°dONLNdH8Ÿ@È)ANT

ˇ·ˇ‚7^
°dONLNdLC∫O¡(L∫
A∫†°dONLNdMC¡O
ø)> note like this contains information that is essential for an °dONLNdãO∫[
Æ(X∫5understanding of the main text. (An example appears oÎ@°dONLNd¿O
Æ[
∂)Ùn <†°dONLNd¬O
∑[
Œ)    page Ä°dONLNd«O
œ[
·)3-33k`°dONLNdÀO
·[
„)
.Î`°dONLNdÃO
„[
Ê)
)?@°dONLNdŒR
ÏZ
Û)    
s

hHv4iHv
°dONLNd–h¶rÆ(p¶
s
°dONLNd—i∫q√(o∫
WúÄ°dONLNd“i√qÓ)    ARNING

ˇ·ˇ‚7^
°dONLNdŸt∫ă(}∫
Wï°dONLNd⁄t√Ä
e)    'arnings like this indicate potential pr*‡°dONLNd
t
fÄ
Û)£oblems that you should be awar…@°dONLNdt
ÛÄ
˙)çe °dONLNd!Ä∫å
m(â∫)of as you design your application. Failur^†°dONLNdJÄ
må
¯)≥e to heed these warnings could °dONLNdiå∫òΩ(ï∫
rE°dONLNdjåæò
Á)Cesult in system crashes or loss of data. (An example appears on pagº@°dONLNd≠å
Áò
Ó(ï
Áe °dONLNdØò∫§—(°∫page Z‡°dONLNd¥ò“§‰)4-10Æ¿°dONLNd∏ò‰§Ê)
..¿°dONLNdπòÁ§Í)
)dž°dONLNdªõÔ£ˆ)
sˇ,@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*˙
¯,Palatino

.
(·*xxvi    3,Ã(#úPREFN )3ACE 4^*¿
¯

k*r
¯4l*r
¯ múm(

ˇ·ˇ‚7^,    Helveticaˇˇ‹.ˇ◊°dONLNd\úk
a(gúAssembly-Language Informationˇˇˇˇˇˇ€r(g

0
°dONLNdrú~Ë({úSome chapters pr`°dONLNd/rÈ~
◊)M4ovide additional assembly-language information. For °dONLNdcúãº(àúexampl0¿°dONLNdiΩãΔ)!e, ˙`°dONLNdlΔã
)    Inside Macintosh‹`°dONLNd|
ã
)F pr#Ä°dONLNd
ã
ü)ovides information about the rÓ`°dONLNdù
üã
Ó)Üegisters for specifi“@°dONLNd±
Ôã
ı)Pc °dONLNd≥åúòü(ïú
rE°dONLNd¥å†òË)outines like this:°dONLNd
;ıú

«(˛ú
In additio°dONLNd
Eı«

—)+n, ¡`°dONLNd
Hı“


)Inside Macintosh£`°dONLNd
Xı



$)F prÍÄ°dONLNd
[ı
$


≠)ovides information about the fi˝ °dONLNd
zı
≠


‘)â
elds of a °dONLNd
Ñ
ú

$(
úparameter block in this format:°dONLNd
Lú
Xº*JThe arrs`°dONLNd
Lº
XÃ) ow ø‡°dONLNd
LÃ
XŒ)
i®@°dONLNd
Lœ
X
í)-n the far left column indicates whether the fiɆ°dONLNdJ
L
ì
X
‘)ƒeld is an input °dONLNdZ
Yú
e…(
bú    parameterS†°dONLNdc
Y…
e
)-, output parameter±‡°dONLNdu
Y

e
D)R, or both. }@°dONLNdÄ
Y
E
e
K)*
Y=¿°dONLNdÅ
Y
K
e
Œ)ou must supply values for all °dONLNdü
fú
r¥(
oúinputÖ`°dONLNd§
f¥
r∂)
 `°dONLNd•
f∑
r
ã)-parameters and input/output parameters. The r.Ä°dONLNd“
f
ã
r
≠)‘outine rµ‡°dONLNd⁄
f
≠
r
Í)"eturns values °dONLNdË
sú
§(
|úin9¿°dONLNdÍ
s•
ß)    
 π¿°dONLNdÎ
sß

Ç).output parameters and input/output parameters.°dONLNd
Öú
ë
)(
éúThe second column shows the fi‡°dONLNd8
Ö
*
ë
q)éeld name as defi˝¿°dONLNdH
Ö
q
ë
Ÿ)Gned in the MPW Pascal °dONLNd^
íú
û (
õúinterface fiR‡°dONLNdj
íÀ
û¸)/les; the thir``°dONLNdw
í¸
û
“)11d column indicates the Pascal data type of that fií °dONLNd©
í
“
û
‰)÷eld. °dONLNdÆ
üú
´˚(
®úThe fourth column pr‘`°dONLNd¬
ü˚
´
º)_.ovides a brief description of the use of the fiD`°dONLNdÒ
ü
Ω
´
Ë)¬eld. For a °dONLNd¸
¨ú
∏
#(
µúcomplete description of each fiº†°dONLNd
¨
#
∏
Œ)á)eld, see the discussion that follows the °dONLNdD
πú
≈
º(
¬úBparameter block or the description of the parameter block in the rÄ°dONLNdÜ
π
Ω
≈
Õ(
¬
Ωefer¡†°dONLNdä
π
Õ
≈
„)ence °dONLNdè
Δú
“˙(
œúsection of the chapter@°dONLNd•
Δ˙
“¸)^
.


Ÿ*
Ù
¯4
⁄*
Ù
¯

*
¯4*
¯ *
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNd®
Ò*◊(
ˇ*The Development Envir§˙°dONLNdΩ
Ò◊
)≠onmentˇˇˇˇˇˇV˛(
ˇ

0
°dONLNd≈ú!Ú(úThe system softwar↰dONLNd◊Ú!˝)Ve rò@°dONLNd⁄˝!
å)!outines described in this book ar+‡°dONLNd˚
ç!
Ÿ)êe available using °dONLNd"ú.
¬(+úBPascal, C, or assembly-language interfaces. How you access these r+†°dONLNdO"
√.
Â(+
√outines °dONLNdW/ú;
6(8ú depends on the development envir‘¿°dONLNdw/
6;
v)öonment you arù¿°dONLNdÑ/
w;
·)Ae using. When showing °dONLNdö<úHfi(Eúsystem softwarM‡°dONLNd®<flHÍ)Ce r\Ä°dONLNd´<ÍH
Ë)<outines, this book uses the Pascal interface available with °dONLNdÁIúUÁ(Rúthe Macintosh PrëÄ°dONLNd˜IÁU
)Kogrammer™`°dONLNdˇI
U
))/’s WC†°dONLNdI
)U
r)orkshop (MPW).°dONLNd[úg
%(dú!All code listings in this book arr¿°dONLNd3[
%g
›)â,e shown in Pascal (except for listings that °dONLNd_hút«(qú
describe rɇ°dONLNdih«tfl)+esourà °dONLNdnhflt
)ces, which ar⁄`°dONLNd{h
t
“)9(e shown in Rez-input format). They show °dONLNd£uúÅ
(~úmethods of using various rU‡°dONLNdΩu
Å
˜)w4outines and illustrate techniques for accomplishing °dONLNdÒÇúéÂ(ãúparticular tasks. _°dONLNdÇÂé
‚)I9All code listings have been compiled and, in many cases, °dONLNd<èúõ‰(òútested. However}`°dONLNdKè‰õÈ)H, °dONLNdMèÈõ
4)Apple Computer«Ä°dONLNd[è
3õ
Ì)J-, Inc., does not intend for you to use these °dONLNdàúú®
3(•ú"code samples in your application. 醰dONLNd™ú
3®
9)ó
YO °dONLNd´ú
9®
^)ou can fi °dONLNd¥ú
_®
Û)&$nd the location of code listings in °dONLNdÿ©úµÕ(≤úthe list of fi†°dONLNdÊ©Œµ›)2gur^‡°dONLNdÈ©›µ
Ê)?es, tables, and listings. If you know the name of a particular 
    °dONLNd«•ú∞Í(≠úRegisters on entry
°dONLNd‹≥úø®*A0G@°dONLNdfl≥Ωøˆ)!Contents of rê@°dONLNdÏ≥ˆø
)9egister .†°dONLNdÙ≥
ø
J) A0 on entry
    °dONLNd
œú⁄‰(◊úRegisters on exit
°dONLNd
›úÈ®*D0=@°dONLNd
›ΩȈ)!Contents of rÜ@°dONLNd
&›ˆÈ
C)9egister D0 on exit,    Symbolˇˇr¿ˇ°dONLNd
§
ú
•(
ú
´,
Courier.^@°dONLNd
¶
∫
 Í)inAndOut[B°dONLNd
Ø


 
2)NInteger.
X§°dONLNd
∑

P
 
º)HInput/output parameterA§°dONLNd
Õ

º
 
æ)l
.°dONLNd
–
$ú
/•(
-ú
¨.^@°dONLNd
“
$∫
0‰)output1[B°dONLNd
⁄
$

0
)NPtr.
X§°dONLNd
fi
$
P
0
†)HOutput parameterD°dONLNd
Ó
$
†
0
¢)P
.°dONLNd
Ò
4ú
?•(
=ú
Æ.^@°dONLNd
Û
4∫
@fi)input1[B°dONLNd
˙
4

@
)NPtr.
X§°dONLNd
˛
4
P
@
ò)HInput parameter'ƒ°dONLNd
4
ò
@
ö)H
.ˇ∫@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,Palatino

.
I (·xxvii    3,Ã(#∫PREFN )3ACE 4^H¿
.°dONLNd\∫hæ(e∫
rR`°dONLNd
\æh
)outine (such as ,
CourierR`°dONLNd\
h
J)DMyHandleODocR`°dONLNd\
Jh
W)H or R`°dONLNd!\
Wh
ü)MyHandleQuitR`°dONLNd-\
üh)H) shown in a code listing, .
°dONLNdHi∫uÂ(r∫    you can fi⁄ °dONLNdRiÂu
[)+nd the page on which the r; °dONLNdli
\u)w)outine occurs by looking under the entry °dONLNdïv∫ÇÂ(∫    “sample rä °dONLNdûvÂÇ
z)+#outines” in the index of this book.°dONLNd¬à∫îœ(ë∫In orj`°dONLNd«àœî
ò).der to make the code listings in this book mor(†°dONLNdıà
ôî
§) e r7@°dONLNd¯à
§î)eadable, they show only °dONLNd
ï∫°Ë(û∫limited err6 °dONLNd
ïÈ°Ú)/orû@°dONLNd
ïÚ°Ù)    
 @°dONLNd
ïı°
!)
handling. ‡`°dONLNd
(ï
!°
'),
Y†‡°dONLNd
)ï
'°
Ì)+ou need to develop your own techniques for °dONLNd
T¢∫ÆÒ(´∫handling errq°dONLNd
`¢ÒÆ
)7ors. °dONLNd
f¥∫¿
â(Ω∫0This book occasionally illustrates concepts by rч°dONLNd
ñ¥
â¿
ô)œefer1°dONLNd
ö¥
ö¿)ence to sample applications °dONLNd
∂¡∫Õ÷( ∫called &`°dONLNd
Ω¡◊ÕÚ)SurfW- °dONLNd
¬¡ÚÕ
)riter5¿°dONLNd
«¡
Õ
), 5¿°dONLNd
…¡
Õ
')SurfDB·‡°dONLNd
œ¡
'Õ
<), andϡdONLNd
‘¡
=Õ
r) SurfCharter;≤†°dONLNd
·¡
sÕ
ó)6     these ar[†°dONLNd
Í¡
òÕ
◊)%e not actual pró¿°dONLNd
˘¡
◊Õ)?
oducts of °dONLNdŒ∫⁄
(◊∫Apple Computer(Ä°dONLNdŒ
⁄
)K, Inc.°dONLNd‡∫Ï◊(È∫APDAH¿°dONLNd‡◊Ï„) is ¿°dONLNd ‡„Ï
O)Apple’s worldwide sour¯ °dONLNd6‡
NÏ
å)kce for over thr¿°dONLNdE‡
çÏ
¥)?ee hundrº†°dONLNdM‡
¥Ï
˛)'ed development °dONLNd\Ì∫˘
(ˆ∫tools, technical rw¿°dONLNdnÌ
˘
)Hesour¿°dONLNdsÌ
˘
\)ces, training prµ†°dONLNdÉÌ
\˘
˚)B#oducts, and information for anyone °dONLNd¶˙∫
Œ(
∫inter
¿°dONLNd´˙œ

n)$ested in developing applications on M`°dONLNdœ˙
n

Ú)üApple platforms. Customers rj°dONLNdÎ˙
Ú
)Ñeceive °dONLNdÚ
∫
ı(
∫the quarterly f`°dONLNd
ˆ

)<APDA[@°dONLNd



) T€@°dONLNd



L)ools Catalog ~°dONLNd

M

ó)4featuring all curr @°dONLNd%

ò

€)Kent versions of Ù`°dONLNd5

⁄

˜)BApple °dONLNd;
∫
 
Ä(
∫+development tools and the most popular thirÈ¿°dONLNdf

Ä
 
˙)Δd-party development tools. °dONLNdÅ
!∫
-≈(
*∫Or ‡°dONLNdÉ
!Δ
-
)dering is easy; therü@°dONLNdó
!

-
))Se ar≠‡°dONLNdõ
!
)
-
˚).e no membership fees, and application forms arΔ‡°dONLNd…
!
˚
-)“e not °dONLNdœ
.∫
:Ω(
7∫
rE°dONLNd–
.æ
:’)equir\@°dONLNd’
.’
:
1)ed for most of our prF@°dONLNdÍ
.
1
:
S)\oducts. o‡°dONLNdÚ
.
S
:
p)"APDA8†°dONLNdˆ
.
p
:
{) ofT`°dONLNd˘
.
{
:
˛)fers convenient payment and °dONLNd
;∫
G
r(
D∫+shipping options, including site licensing.°dONLNdA
M∫
Y¿*
Tµ¿°dONLNdB
Mø
Y–)o or¿°dONLNdF
M–
YÎ)der pr‡°dONLNdL
MÏ
Y
')oducts or to rÒ‡°dONLNdZ
M
&
Y
Δ):#equest a complimentary copy of the Ç@°dONLNd}
M
«
Y
„)°APDAw °dONLNdÅ
M
„
Y
Î) T˜ °dONLNdÉ
M
Í
Y
¸)ools °dONLNdà
Z∫
fŸ(
c∫Catalogó`°dONLNdè
ZŸ
f˝)    , contact°dONLNdô
l∫
x◊(
u∫APDAH¿°dONLNdù
l◊
xŸ)
 °dONLNdü
y∫
Ö
(
Ç∫Apple Computer(Ä°dONLNd≠
y

Ö
)K, Inc. °dONLNdµ
Ü∫
í¿(
è∫
P?†°dONLNd∂
Üø
í).O. Box 319°dONLNd¬
ì∫
ü…(
ú∫Buf… °dONLNd≈
ì…
üÌ)falo, NYG†°dONLNdÕ
ìÓ
ü
 )% 14207-0319°dONLNd®#∫/‡(,∫    If you pr@°dONLNd±#·/ı)'ovid% °dONLNdµ#ı/
 )e commerã °dONLNdΩ#
 /
7)+cial pN@°dONLNd√#
8/
;)
r@°dONLNdƒ#
</
Û)+oducts and services, call 408-974-4897 for °dONLNdÔ0∫<
m(9∫'information on the developer support pr °dONLNd0
n<
¬)¥ograms available fr‹‡°dONLNd)0
¬<
“)Tom H°dONLNd,0
”<
)Apple.°dONLNd3B∫N
(K∫For information on ræÄ°dONLNdGB
N
g)Zegistering signaturòÄ°dONLNdZB
gN
{)Ses, fi´‡°dONLNd`B
{N
ù)le types∏ °dONLNdhB
ùN
ß)", a∏ °dONLNdkB
ßN
˘)
nd other technical °dONLNd~O∫[
(X∫information, contact°dONLNdìa∫m
!*Macintosh Developer T.@°dONLNd®a
!m
k)gechnical Support°dONLNdπn∫z
(w∫Apple Computer(Ä°dONLNd«n
z
)K, Inc.°dONLNdŒ{∫á˚(Ñ∫20525 Mariani +†°dONLNd‹{˚á
)A
A‡°dONLNd›{
á
Q)venue, M/S 75-3T°dONLNdÓà∫î˚(ë∫Cupertino, CA¿°dONLNd˚à˚î
-)A 95014-6299°dONLNdÿ
•∫
±¿(
Æ∫
Tµ¿°dONLNdŸ
•ø
±Á)elephone°dONLNd‚
•

±
ò)]800-282-2732 (United States)°dONLNdˇ
∞

º
*800-637-0029 (Canada)°dONLNd
ª

«
ó*716-871-6555 (International)°dONLNd3
˺
◊…(
‘∫Fax°dONLNd7
À

◊
O)b716-871-651õ °dONLNdB
À
O
◊
V)31 °dONLNdF
€∫
ÁÈ(
‰∫    AppleLink°dONLNdP
€

Á
9)bAPDA°dONLNdV
Î∫
˜
(
Ù∫America Online°dONLNde
Î

˜
9)bAPDA°dONLNdk
˚∫Û(∫
CompuServe°dONLNdv
˚

K)b
76666,2405°dONLNdÇ∫›(∫Internet°dONLNdã

õ)b[e-mail]ˇÆ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄*˙
¯,Palatino

.
(·*xxviii    3,Ã(#úPREFN )3ACE 4^*¿
¯
°dONLNd\úhØ(eúThe ]`°dONLNd\Øh
R)$Apple Event Registrar maintains the Ú@°dONLNd(\
Rh
Ó)£%Apple Event Registry: Standard Suites‡°dONLNdM\
Ôh
Ò)ù
 °dONLNdNiúu
õ(rú7and other information about the ongoing development of ¯°dONLNdÖi
õu
Ú)ˇApple event suites. °dONLNdôvúÇø(úFor mor¿°dONLNd†v¿Ç
)$e information about Û°dONLNd¥v
Ç
‘)Y*Apple event suites, including those under °dONLNdfiÉúè

(åúdevelopment, send electrM†°dONLNdˆÉ
è
Q)oonic mail to the »¿°dONLNd
É
Qè
ò)FAppleLink addr'`°dONLNd
É
ôè
“)Hess REGISTRdÄ°dONLNd
 É
“è
ÿ)9
YÙ@°dONLNd
!É
׏
Ÿ)
.ˇ≤@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,    Helvetica    .
(‡∫Contents,Palatino

, (‡    1-1    3,Ã(#∫CHAPTER ÿ)h
1
ˇˇˇˇˇˇˇˇ4^4|lòÄ2^A|rMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^A|r^A|r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
^6|@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^6|@^6|@˜˜˜˜˜˜˜˜˜˜˜˜˜˙ˇˇ
˙ˇ
˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜ˇˇˇˇˇˇ(JH
Figure 1-0*    Listing 1-0*    
T)able 1-0ˇˇ∫Ρ◊(qH
1°dONLNd[∫xÂ)rIntr9°dONLNd[Âx
q)+oduction to °dONLNdx∫ï
{(é∫Interapplication 

¥H
f
4¥H
f 
NH
N°dONLNd/
S∫
d˘*“Contents

ˇ·ˇ‚7^ˇˇ∫Ρ◊°dONLNd!ï∫≤
x(´∫Communication
°dONLNd8
u∫
Å
Ñ*”*Overview of Interapplication Communications†°dONLNdd
u
ô
Å
¶)fl1-3°dONLNdh
Ç∫
éˆ(
ã∫Sharing Data m‡°dONLNdu
Lj
é
)<Among ¿°dONLNd{
Ç

é
R)$Applicationsª‡°dONLNdâ
Ç
f
é
s)L1-6°dONLNdç
è∫
õ
7(
ò∫Sending and Responding to h@°dONLNdß
è
7
õ
r)}Apple EventsB °dONLNdµ
è
á
õ
î)P1-9°dONLNdπ
úƒ
®Ê(
•ƒStandar¥@°dONLNd¿
úÊ
®Ó)"d Ò†°dONLNd¬
úÓ
®
))Apple EventsÀÄ°dONLNd–
ú
>
®
P)P1-10°dONLNd’
©ƒ
µ(
≤ƒ    Handling `°dONLNdfi
©Ò
µ
,)-Apple EventsÎ@°dONLNdÏ
©
@
µ
R)O1-12°dONLNdÒ
∂∫
¬Ó(
ø∫Supporting ‡ °dONLNd¸
∂Ó
¬
∞)4)AppleScript and Other Scripting Languages˜†°dONLNd
'
∂
ƒ
¬
÷)÷1-13°dONLNd
,
√ƒ
œÚ(
ÃScriptable ™¿°dONLNd
7
√Ú
œ
*).Applicationse‡°dONLNd
E
√
?
œ
Q)M1-16°dONLNd
J
–ƒ
‹›(
ŸƒRecor¢`°dONLNd
O
–›
‹˜)dable `°dONLNd
U
–¯
‹
0)Applications‘Ä°dONLNd
c
–
D
‹
V)L1-18°dONLNd
h
›ƒ
È
¢(
ʃ0Applications That Manipulate and Execute Scriptsß@°dONLNd
ö
›
∂
È
»)Ú1-19°dONLNd
ü
Í∫
ˆ
5(
Û∫Exchanging Message Blocksw°dONLNd
∫
Í
J
ˆ
\)ê1-22ˇJ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4^*¿
¯ˇ?d@ˇˇˇˇˇ@

ˇ·ˇ‚7^,Palatino
&e.
3+ä"CHAPTER à)>
1
4⁄ä˙,    Helvetica    (‡ä*Overview of Interapplication Communication

, (‡    1-3
ˇˇˇˇˇˇˇˇ4^4|lòÄ2^A|sMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^A|s^A|s$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
^6|?MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^6|?^6|?˜˜˜˜˜˜˜˜˜˜˜˜˜˙ˇˇ
˙ˇ
˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜
4Å4
w?òÄ
Å6
w?MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""Å6
w?Å6
w?$˜
˙ˇ˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛
¸ˇ˛¸ˇ˝˚ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛
˙ˇ˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˛¸ˇˇ
ˇ˛ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˜˜˜˜
˙ˇ
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛˜˛˛ˇ˝
ˇˇˇ˛
ˇˇˇ˛    ˇˇˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
˙ˇ˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˝˛ˇ˛
˛ˇ˛ˇˇ    ˇ¸
ˇ    ˇ¸
ˇ
˛ˇ˛ˇˇ˜˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜    ˇˇ—ÚˇÆ°dONLNd8äC
;(@ä.Introduction to Interapplication Communicationˇˇˇˇˇˇ≠>(@
1
°dONLNd/\äh
¥(eäBThis chapter describes the interapplication communication (IAC) ar|`°dONLNdq\
¥h
⁄(e
¥    chitectur1 °dONLNdz\
€h
fl)'
e˙¿°dONLNd{\
flh
) for °dONLNdÄiäuÈ(räMacintosh computersd °dONLNdìiÍu
)`@, summarizes how your application can take advantage of it, and °dONLNd”väÇ…(ätells you wher\Ä°dONLNd·v…Ç
)?e in this book to fi_`°dONLNdıv
Ç
Ë)O-nd the information you need to perform specifie¿°dONLNd
#v
ËÇ)–c tasks.°dONLNd
,àäîù(ëäThe ]`°dONLNd
0àùî˛)Apple Event ManagerN‡°dONLNd
Cà˛î
F)a, Event ManagerB‡°dONLNd
Rà
Fî
h)H, and Pr~†°dONLNd
Zà
hî
û)"ogram-to-Prx °dONLNd
eà
ûî)6ogram Communications °dONLNd
zïä°¶(ûä(PPC) “°dONLNd
Äﶰ¨)
T¿°dONLNd
Å侮
ˇ)Moolbox underlie all the IAC tasks your application can perform. This chapter °dONLNd
Œ¢äÆô(´äintrA °dONLNd
“¢öÆÀ)oduces the œ`°dONLNd
ݢˮ
\)1Apple Event Manager and the Pró`°dONLNd
˚¢
]Æ
ì)íogram-to-PrꇰdONLNd¢
ìÆ)6ogram Communications °dONLNdØäªê(∏ä
Tµ¿°dONLNdØèª
j)/oolbox. For information about the Event ManageryÄ°dONLNdKØ
jª
)€, see …¿°dONLNdQØ
ª
˜)Inside Macintosh: Macintosh °dONLNdmºä»ê(≈ä
T°dONLNdnºè»”)oolbox EssentialsE°dONLNdº‘»÷)E
.≈°dONLNdĺ÷»˙) For defiÆ`°dONLNdâº˚»
X)%nitions of the standaro°dONLNdüº
Y»
a)^d ¨`°dONLNd°º
a»)&Apple events available for use by all °dONLNd«…ä’Â(“äapplications, see the !Ä°dONLNd›…Ê’
i)\Apple Event Registry: Standard †°dONLNd¸…
j’
Ö)ÑSuites.°dONLNd€äÁ∫(‰ä
The IAC ar=Ä°dONLNd€ªÁ·)1    chitecturÚ@°dONLNd€·Á
e)&e includes the Open Scripting à °dONLNd5€
fÁ
q)ÖAr`°dONLNd7€
rÁ
ò)    chitectur… °dONLNd@€
òÁ
∑)&e (OSAIÄ°dONLNdF€
∏Á
Ë)
). The OSA/`°dONLNdP€
ËÁ
)0 p±Ä°dONLNdR€
Á
Û)
rvÄ°dONLNdS€
ÙÁ)ovides °dONLNdZËäÙö(Òäa m‘°dONLNd]ËöÙª)echanis÷°dONLNdd˪م)!m tl`°dONLNdgË Ù
5)hat allows users to contr °dONLNdÄË
6Ù
Ú)l+ol multiple applications by means of script[ °dONLNd´Ë
ÚÙ)ºs, or °dONLNd±ıä

º(˛äsets of instrÁ °dONLNdæıº

È)2
uctions, wd °dONLNd»ıÍ


ö).*ritten in a variety of scripting languages˘¿°dONLNdÚı
ö


•)∞. EÄ°dONLNdıı
¶

)ach scripting language °dONLNd
ä
¥(
ä
has a corr+¿°dONLNd
µ
    )+Fesponding scripting component that is managed by the Component Manager:¿°dONLNd\
    
(
    . °dONLNd^
ä

õ(
ä=When a user executes a script, the scripting component sends [@°dONLNdõ

õ

(

õApple events to one or °dONLNd≤
ä
(ú(
%ämoréÄ°dONLNdµ
ú
(
ñ);e applications to perform the actions the script describes.°dONLNdÒ
.ä
:”(
7äThis chapter intrõ°dONLNd
.”
:
)Ioduces the OS£@°dONLNd
.

:
)?
A›‡°dONLNd
.

:
`) and describes h@°dONLNd 
.
a
:)H(ow to make your application scriptable, °dONLNdH
;ä
G…(
Däor capable of r¢Ä°dONLNdW
;…
G
)?esponding to ∞@°dONLNdd
;

G
‡)<2Apple events sent to it by a scripting component. °dONLNdó
Hä
T≠(
QäFor mor¿°dONLNdû
HÆ
T
í)$/e information about using the Component Manageró@°dONLNdÕ
H
ë
T
¶)„, see ÁÄ°dONLNd”
H
¶
T
)Inside Macintosh: °dONLNdÂ
Uä
aõ(
^äMorÄ°dONLNdË
Uú
aü)
e˙ °dONLNdÈ
Uü
a°)
 z °dONLNdÍ
U¢
aÃ)    Macintoshj†°dONLNdÛ
UÕ
aœ)+
 ͆°dONLNdÙ
Uœ
a’)
T͆°dONLNdı
U‘
a)oolbox.


hH
É4
iH
É


ìH
õ4
îH
õ 
ïH
ï

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNd˛
ÄH
ìU(
éH
OÜB°dONLNdˇ
ÄU
ì
í))verview of Interapplication CommunicationˇˇˇˇˇˇV˛(
é
1
°dONLNd*
§ä
∞ù(
≠äThe 
ª¿°dONLNd.
§ù
∞
Ñ)1interapplication communication (IAC) architectureˇÄ°dONLNd_
§
Ñ
∞
ê)Á prF†°dONLNdb
§
ë
∞
Ÿ)ovides a standarû†°dONLNdr
§
Ÿ
∞
ı)Hd and °dONLNdx
±ä
Ω
e(
∫ä-extensible mechanism for communication among o °dONLNd•
±
f
Ω
ñ)‹
Macintosh T†°dONLNdØ
±
ó
Ω
˘)1applications. The IAC °dONLNd≈
æä
 í(
«äarE°dONLNd«
æì
 π)        chitectur˘¿°dONLNd–
æπ
 
r)&+e makes it possible for your application to,Zapf Dingbats°dONLNd¸
‘ä
ۏ(
ڊ
n
°dONLNd˛
—ñ
›ü)prG °dONLNd
—†
›
2)
ovide automated copy and paste †°dONLNd
—
3
›
d)ìoperations } °dONLNd*
—
d
›)1#between your application and other °dONLNdM
ݖ
ÈÀ(
Êñapplications°dONLNdZ
Úä
˘è(
¯ä
n
°dONLNd\
Ôñ
˚
3)"be manipulated by means of scripts°dONLNdäè(
ä
n
°dONLNdÅ
ñƒ)
send and r%‡°dONLNdã
≈Û)/
espond to Í¿°dONLNdï
Ú
,)-Apple events°dONLNd¢äè(ä
n
°dONLNd§ñƒ)
send and r%‡°dONLNdÆ≈
q)/'espond to high-level events other than °dONLNd’
q
´)¨Apple events°dONLNd‚(ä/è(.ä
n
°dONLNd‰%ñ1ô)
rE°dONLNdÂ%ö1
w)1ead and write blocks of data between applications°dONLNd6äBù(?äThe ª¿°dONLNd6ùB¿)chapter ~ °dONLNd#6¡B
    )$“Event Manager/Ä°dONLNd16

B
)I” ió‡°dONLNd46
B
)
n È@°dONLNd66
B
ö)Inside Macintosh: Macintosh T;¿°dONLNdS6
öB
fi)~oolbox Essentials¿°dONLNdd6
flB)E describes °dONLNdoCäO
Y(Lä,how your application can use Event Manager rò‡°dONLNdõC
YO
∂)œoutines to send and rv°dONLNd∞C
∂O)]espond to high-level °dONLNd≈Pä\ı(Yäevents. High-level eventœ‡°dONLNd›Pı\
))ks need not añÄ°dONLNdÈP
*\
>)5dher@°dONLNdÌP
?\
Ä)e to any specifi‚`°dONLNd˝P
Ä\
ê)Ac prô¿°dONLNd    
P
ë\
Û)otocol, so their interpr†°dONLNd    P
Û\)betation °dONLNd    !]äi§(fäis defiÄ°dONLNd    (]•i
O)'ned by each application that sends or r€ °dONLNd    O]
Oi
ä)™eceives them.°dONLNd    ]oä{Ë(xäThe most important rΔ`°dONLNd    qoË{ˇ)^equir›†°dONLNd    voˇ{)=ement for high-level communication among all applications is °dONLNd    ≥|äà
!(Öä a common vocabulary of events. Tb‡°dONLNd    ”|
!à
2)óo prÄ°dONLNd    ◊|
3à
é)ovide such a standar@@°dONLNd    Î|
éà
ô)[d, ˝†°dONLNd    Ó|
òà
„)
Apple Computer¶ °dONLNd    ¸|
„à)K, Inc., has °dONLNd
âäïö(íädefir °dONLNd
âõïø)ned a pr°dONLNd
âøï
    )$otocol called the 
o@°dONLNd
&â

ï)K4Apple Event Interprocess Messaging Protocol (AEIMP).Ø¿°dONLNd
Zâï    )˝
 °dONLNd
[ñä¢
>(üä)High-level events that conform to this prX°dONLNd
Ññ
>¢
d)¥    otocol aròÄ°dONLNd
çñ
d¢
á)&    e called 
àÄ°dONLNd
ññ
à¢
ƒ)$Apple events  °dONLNd
¢ñ
Ģ
Δ)<
.J °dONLNd
£ñ
«¢
…)
 ˇò@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@l.Introduction to Interapplication Communication4⁄*˙
¯

(‡*1-4    )B*Overview of Interapplication Communication4^*¿
¯
°dONLNd\lh
(el%The vocabulary of publicly available •†°dONLNd%\
h
†)£!Apple events is published in the ø@°dONLNdF\
†h
‘)ëApple Event °dONLNdRilu÷(rlRegistry: Standard Suites,(`°dONLNdli◊u
)k
 which defil‡°dONLNdwi
u
K)1nes the standarS¿°dONLNdÜi
Ku
S)Cd ë °dONLNdài
Su
Í)!Apple events that developers and °dONLNd©vlÇ
T(l4Apple have worked out for use by all applications. T@°dONLNd›v
TÇ
t)Ëo ensur•‡°dONLNd‰v
tÇ
Ï) e that your application can °dONLNd
Élè
(ål%communicate at a high level with otheW¿°dONLNd
%É
è
 )©r a `°dONLNd
(É
 è
S)pplications >@°dONLNd
4É
Tè
ç)4that support (‡°dONLNd
AÉ
çè
œ)9Apple events n°dONLNd
OÉ
–è
Û)Cow and °dONLNd
Vêlúû(ôlin the futurĆ°dONLNd
bêûú
3)2!e, you should support the standarʇ°dONLNd
Éê
3ú
;)ïd $@°dONLNd
Öê
<ú
ï)    Apple events that ar« °dONLNd
ôê
ïú
±)Ye appr⁄°dONLNd
üê
±ú
‚)opriate for °dONLNd
´ùl©∫(¶lyour application. °dONLNd
æØlªu*Ef¬°dONLNd
¿Øuª≠)    fective IAC rÏ °dONLNd
ÕØ≠ªƒ)8equir`°dONLNd
үŻ
¯)Ges close cooperation among applications at several levels. In addition °dONLNdºl»
J(≈l3to the format for high-level events and the standar¢@°dONLNdLº
J»
ë)fid vocabulary of -‡°dONLNd\º
í»
—)HApple events, W@°dONLNdjº
—»
Ó)?Apple °dONLNdp…l’é(“lhas defiÄ°dONLNdx…è’ˇ)#ned several other standarˇ¿°dONLNdë…˛’
Û)o6ds your application can use to communicate with other °dONLNd«÷l‚
(fll#applications. These include standarf†°dONLNdÍ÷
‚
ñ)úd methods for dealing with shar{ °dONLNd    ÷
ñ‚
‰)éed dynamic data, °dONLNd„lÔ
(Ïl'scripts, and low-level message blocks. °dONLNdBıl

ú*
The IAC ar=Ä°dONLNdLıù

√)1    chitecturÚ@°dONLNdUı√


M)&e comprises the following partsó`°dONLNdtı
N


S)ã: ,Zapf Dingbats°dONLNdw
l
q(
l
n
°dONLNdy
x
ã)The 
ª¿°dONLNd}
ã
◊)Edition Manager®@°dONLNdå
ÿ

‡)M; allows applications to automate copy and paste operations °dONLNd«
x
 
B(
x.between applications, so that data can be sharê °dONLNdı

B
 
Ü) ed dynamically‚Ä°dONLNd

Ö
 
á)C
.°dONLNd
)l
0q(
/l
n
°dONLNd
&x
2ã)The 
ª¿°dONLNd
&ã
2
+)!Open Scripting Architecture (OSA)y¿°dONLNd,
&
,
2
8)° pr¿‡°dONLNd/
&
8
2
Ä)ovides a standar‡°dONLNd?
&
Å
2
Î)Id mechanism, based on °dONLNdU
2x
>à(
;xthe °dONLNdY
2à
>È)Apple Event ManagerpÄ°dONLNdl
2È
>
])a, that allows users to contrT†°dONLNdà
2
]
>
ı)t"ol multiple applications by means °dONLNd™
>x
J
^(
Gx7of scripts written in a variety of scripting languages.°dONLNd‚
Sl
Zq(
Yl
n
°dONLNd‰
Px
\ã)The 
ª¿°dONLNdË
Pã
\Ó)Apple Event Manager∑`°dONLNd˚
PÔ
\
É)d" allows applications to send and r„@°dONLNd
P
É
\
±)î
espond to ® °dONLNd'
P
±
\
Ó).Apple events.°dONLNd5
el
lq(
kl
n
°dONLNd7
bx
nã)The 
ª¿°dONLNd;
bã
n–)Event Manager‰¿°dONLNdH
b–
n
d)E" allows applications to send and r†°dONLNdj
b
e
n
·)ïespond to high-level events °dONLNdÜ
nx
z®(
wxother than L@°dONLNdë
n®
zÂ)0Apple events.°dONLNdü
Él
äq(
âl
n
°dONLNd°
Äx
åã)The 
ª¿°dONLNd•
Äã
å
^))Program-to-Program Communications (PPC) TÑ`°dONLNdŒ
Ä
^
å
})”oolbox°`°dONLNd‘
Ä
}
å
‚) allows applications to °dONLNdÏ
åx
ò
<(
ïx,exchange blocks of data with each other by rß°dONLNd
å
<
ò
Ê)ƒ%eading and writing low-level message °dONLNd=
òx
§è(
°xblockd‡°dONLNdB
òê
§¿)s. It also pr§¿°dONLNdO
ò¿
§
)0ovides a standar¸¿°dONLNd_
ò

§
‰)H3d user interface that allows a user working in one °dONLNdí
§x
∞
¨(
≠xFapplication to select another application with which to exchange data.°dONLNdŸ
µl
¡Ñ(
ælFigurR¿°dONLNdfi
µÑ
¡ò)e 1-1@°dONLNd„
µò
¡û) s≠@°dONLNdÂ
µü
¡Ù)hows the primary r›`°dONLNd˜
µÙ
¡
|)Uelationships among these partsπ°dONLNd
µ
}
¡
à)â. TŸ¿°dONLNd
µ
à
¡
÷)he managers and °dONLNd(
¬l
ξ(
Àlcomponents towarÒ°dONLNd8
¾
ŒÌ)Rd the top oô†°dONLNdC
¬Ó
Œ

)0f the fi◊†°dONLNdK
¬


Œ
)gur2‡°dONLNdN
¬

Œ
%)e rAÄ°dONLNdQ
¬
%
Œ
:)ely ox °dONLNdV
¬
:
Œ
˜))n the managers beneath them. The Edition °dONLNd
œl
€˝(
ÿl!Manager uses the services of the Å@°dONLNd†
œ˝
€
˜)ë5Apple Event Manager to support dynamic data sharing. °dONLNd’
‹l
Ë
Æ(
ÂlHScripting components manipulate and execute scripts with the aid of the t°dONLNd
‹
Æ
Ë
Ë(
Â
ÆApple Event °dONLNd)
Èl
ıì(
ÚlManagerT†°dONLNd0
Èì
ıû)'. Tu`°dONLNd3
Èû
ı´)he 2°dONLNd6
È´
ı
3)Apple Event Manager in turn rÌ °dONLNdS
È
3
ı
–)à#elies on the Event Manager to send ±°dONLNdv
È
–
ı
Ì)ùApple °dONLNd|
ˆl
‘(
ˇlQevents as high-level events, and the Event Manager uses the services of the PPC TÛ`°dONLNdÕ
ˆ
”
Û(
ˇ
”oolbox.lÄ°dONLNd‘
ˆ
Ù
ˆ)!
 °dONLNd÷lÑ(lFigurR¿°dONLNd€Ñò)e 1-1@°dONLNd‡ò„) also shows the fiç °dONLNdÚ‰
ó)L&ve principal means of communication pr€†°dONLNd    
ó
Î)≥ovided by the IAC °dONLNd    *l!t(larE°dONLNd    ,u!õ)        chitectur˘¿°dONLNd    5õ!
Ù)&Me. In addition to using the Edition Manager and scripting components to send °dONLNd    Ç"l.
Z(+l7Apple events on their behalf, applications can use the ® °dONLNd    π"
Z.
À)ÓApple Event Manager dir† °dONLNd    –"
À.
Ì)q    ectly to °dONLNd    Ÿ/l;É(8lsend ï`°dONLNd    fi/É;
)$Apple events to other applications. 0°dONLNd
/
 ;
ú)ùAll applications can use the 
@°dONLNd
/
ú;
÷)|Apple Event °dONLNd
+<lH•(ElManager to r釰dONLNd
7<•H‹)9espond apprCÄ°dONLNd
B<›H
)8opriately to s °dONLNd
O<
H
ó)5Apple events, whether they arÓ`°dONLNd
l<
óH
–)Öe sent by the °dONLNd
zIlUè(RlEdition ëÄ°dONLNd
ÇIèU∂)#Managerf °dONLNd
âI∂U
É)'0, a scripting component, or other applications. ü°dONLNd
πI
ÉU
œ)ÕApplications can °dONLNd
 VlbÄ(_lalso ö‡°dONLNd
œVÄbë)use (†°dONLNd
”Víbı)the Event Manager dirÄÄ°dONLNd
ËVıb
>)cectly to send or rM°dONLNd
˙V
?b
€)J$eceive high-level events other than °dONLNdcloâ(llApple }Ä°dONLNd$cäoÎ)events, and the PPC T≤@°dONLNd9cÍo
)`
oolbox dirÙÄ°dONLNdCc
o
`)-ectly to send or r¡°dONLNdUc
ao
æ)Jeceive blocks of data.ˇh@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@ä.Introduction to Interapplication Communication4⁄ä˙(‡ä*Overview of Interapplication Communication

, (‡    1-5
ˇˇˇˇˇˇˇˇ4^4|lòÄ2^A|rMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^A|r^A|r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
^6|@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^6|@^6|@˜˜˜˜˜˜˜˜˜˜˜˜˜˙ˇˇ
˙ˇ
˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜
4Å4
w?òÄ
Å6
w@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""Å6
w@Å6
w@$˜
˙ˇ˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛
¸ˇ˛¸ˇ˝˚ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛
˙ˇ˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˛¸ˇˇ
ˇ˛ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˜˜˜˜
˙ˇ
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛˜˛˛ˇ˝
ˇˇˇ˛
ˇˇˇ˛    ˇˇˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
˙ˇ˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˝˛ˇ˛
˛ˇ˛ˇˇ    ˇ¸
ˇ    ˇ¸
ˇ
˛ˇ˛ˇˇ˜˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHw4gHw"hH]

ˇ·ˇ‚7^    °dONLNd\äg¥(dä
Figure 1-1°dONLNd\Ãg
≥)B7Principal methods of communication between applications
°dONLNdD
•ä
±ê(
Æä
T†¿°dONLNdE
•ê
±£)he fi»Ä°dONLNdJ
•£
±
)ve forms of IAC shown in qÄ°dONLNdc
•

±
0)uFigurD@°dONLNdh
•
0
±
D)e 1-1·¿°dONLNdm
•
D
±
Œ) can be summarized as follows:,Zapf Dingbats°dONLNdå
ªä
(
¡ä
n
°dONLNdé
∏ñ
ƒÒ)Sharing dynamic data.Ä°dONLNd£
∏Ú
ƒ
Œ)\1 The Edition Manager allows users to copy data fr*@°dONLNd‘
∏
Œ
ƒ
Ò)‹om one °dONLNd€
Ė
–
ˇ(
ÕñOapplication’s document to another application’s document, updating information °dONLNd
*
–ñ
‹
‹*Hautomatically when the data in the original document changes. The verbs k@°dONLNd
r
–
›
‹
˙(
Ÿ
›publishÄ°dONLNd
y
–
˚
‹) and °dONLNd
~
‹ñ
˪(
Âñ    subscribe∏¿°dONLNd
á
ܻ
Ë
Ω)%: describe this form of dynamic data sharing, and the noun D‡°dONLNd
¡
‹
æ
Ë
Ÿ(
Â
æedition
@°dONLNd
»
‹
⁄
Ë) describes a °dONLNd
’
Ëñ
Ù

(
Òñcopy of the data to be sharÿ`°dONLNd

Ë


Ù
)ted. _`°dONLNd
Ù
Ë

Ù
)4Applications that support dynamic data sharing must °dONLNd(
Ùñ‰(
˝ñimplement the Cr[@°dONLNd8
Ù‰
k)Neate Publisher and Subscribe T/Ä°dONLNdV
Ù
k
˙)áo menu commands. The Edition °dONLNdsñ (    ñ
Manager prY °dONLNd} 
¨)45ovides the interface that allows applications to shar“†°dONLNd≤
¨
Ÿ)‚e editions.°dONLNdæñú(ñ
Y@Ä°dONLNdøú
∞)?ou can let users publish and subscribe on a local volume or acrvÄ°dONLNd˛
∞
˝(
∞oss a network. In °dONLNdñ'($ñXgeneral, users should be able to publish or subscribe to anything that they can copy or °dONLNdh'ñ3≤*paste. À °dONLNdo'≤3Û)“Sharing Data π°dONLNd}'Û3
)AAmong K‡°dONLNdÉ'
3
W)$Applications,”á°dONLNdë'
W3
§)@ which begins on ˜`°dONLNd¢'
§3
ª)Mpage “@°dONLNdß'
º3
…)1-6& °dONLNd™'
 3), describes how °dONLNd∫3ñ?
[(<ñ,you can use the publish and subscribe featurf‡°dONLNdÊ3
[?
Ω)≈es in your application.°dONLNd˛HäOè(Nä
n
°dONLNdEñQæ)
Scripting.ˆ °dONLNd
EæQË)( The OSA °dONLNdEÈQ
#)+ includes the C°dONLNd E
#Q
Ñ):Apple Event Manager4Ä°dONLNd3E
ÑQ
ô)a, the 3Ä°dONLNd9E
ôQ
Ê)Apple events defi-`°dONLNdJE
ÁQ)Nned by °dONLNdQQñ]¶(Zñthe ›`°dONLNdUQ¶]
E)&Apple Event Registry: Standard Suites,K °dONLNd{Q
F]
p)†
 and the rZ†°dONLNdÖQ
p]
–)*outines supported by 
I°dONLNdöQ
—]
¸)a
scripting °dONLNd§]ñi–(fñcomponents,âÄ°dONLNdØ]–i
¸):A which applications can use via the Component Manager to execute °dONLNdiñu
K(rñ+scripts. Script-editing applications such aˇ¿°dONLNdi
Ku
è)µs Script Editor (™Ä°dONLNd,i
êu
Ã)Enot shown in ¿°dONLNd9i
Õu
Â)=FigurÏÄ°dONLNd>i
‰u
¯)e 1-1ä°dONLNdCi
˘u
˛)) °dONLNdEuñŶ(~ñalloΔ@°dONLNdIu¶Å∂)w u§`°dONLNdLu∑Å
d)(sers to manipulate and execute scripts. °dONLNduÑñê
-(çñ"Each scripting language has a corr«Ä°dONLNdóÑ
-ê)ó/esponding scripting component that can execute °dONLNdΔêñú
Î(ôñMscripts written in that language. Scripting components typically implement a °dONLNdúñ®
D*'text-based scripting language based on ≈¿°dONLNd:ú
D®
œ)ÆApple events. For example, the 
úÄ°dONLNdYú
–®
)åAppleScript °dONLNde®ñ¥…(±ñ    componentô@°dONLNdn®…¥
)3 implements 
¯ °dONLNdz®
¥
<)9AppleScript,˝‡°dONLNdÜ®
<¥
p): the standar¿°dONLNdí®
q¥
Ù)5d user scripting language defiŸ`°dONLNd∞®
Ù¥)Éned by 

wH
é4vFwGò@@
˜@
˜wG∑>¡¡?Œˇ¿ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ0?¸ˇÄÄ˚ˇ¿@?˛ˇ¯˝ˇ‡ ˛ˇ‡ ¸ˇ‡ˆ0?¸ˇÄ
@˚ˇ¿†?˛ˇ¯˝ˇ‡P˛ˇ‡P¸ˇ‡ˆ0?¸ˇÄ ˚ˇ¿
?˛ˇ¯"˝ˇ‡à˛ˇ‡à¸ˇ‡ˆ0?¸ˇÄ˚ˇ¿?˛ˇ¯A˝ˇ‡
˛ˇ‡
¸ˇ‡ˆ0?¸ˇÄ˚ˇ¿?˛ˇ¯ÄÄ˝ˇ‡˛ˇ‡¸ˇ‡ˆ0?¸ˇÄ˚ˇ¿?˛ˇ¯
@˝ˇ‡
˛ˇ‡
¸ˇ‡ˆ0?¸ˇÄ ˚ˇ¿
?˛ˇ¯ ˝ˇ‡Ä˛ˇ‡Ä¸ˇ‡ˆ0?¸ˇÄ@
˚ˇ¿ Ä?˛ˇ¯˝ˇ‡@˛ˇ‡@¸ˇ‡ˆ0?¸ˇÄÄÄ˚ˇ¿@@?˛ˇ¯˝ˇ‡  ˛ˇ‡  ¸ˇ‡ˆ0?¸ˇÅ@˚ˇ¿Ä ?˛ˇ¯˝ˇ‡@˛ˇ‡@¸ˇ‡ˆ0?¸ˇÇ ˚ˇ¡?˛ˇ¯ ˝ˇ‡Ä˛ˇ‡Ä¸ˇ‡ˆ0?¸ˇÑ˚ˇ¬?˛ˇ¯@
˝ˇ·˛ˇ·¸ˇ‡ˆ0?¸ˇà˚ˇƒ?˛ˇ¯Äὡ‚˛ˇ‚¸ˇ‡ˆ0?¸ˇê˚ˇ»?˛ˇ˘˛G˝ˇ‰
˛ˇ‰
¸ˇ‡ˆ0?¸ˇ†Ç˚ˇ–¡?˛ˇ˙
¯'˝ˇË‡ü˛ˇË‡ü¸ˇ‡ˆ0?¸ˇ¿ A˚ˇ‡ ø˛ˇ¸˝ˇ_˛ˇ_¸ˇ‡ˆ/?¸ˇ†@ ˙ˇ– ˛ˇ˙˝ˇË?˛ˇË?¸ˇ‡ˆ0?¸ˇêò˚ˇ»Lø˛ˇ˘    Å˝ˇ‰&_˛ˇ‰&_¸ˇ‡ˆ0?¸ˇà‰
˚ˇƒr?˛ˇ¯Ä@ß˝ˇ‚9ü˛ˇ‚9ü¸ˇ‡ˆ,?¸ˇÑ?«˙ˇ¬ü„˝ˇ¯@s¸˝ˇ·
œÒ˝ˇ·
œÒ˚ˇ‡ˆ,?¸ˇÇ
˙ˇ¡å
˝ˇ¯ Ä?˝ˇ‡ÄF˝ˇ‡ÄF˚ˇ‡ˆ,?¸ˇÅÄ˙ˇ¿Ä@
˝ˇ¯?˝ˇ‡@ ˝ˇ‡@ ˚ˇ‡ˆ,?¸ˇÄÄ@˙ˇ¿@ 
˝ˇ¯?˝ˇ‡ ˝ˇ‡ ˚ˇ‡ˆ,?¸ˇÄ@0˙ˇ¿ 
˝ˇ¯?˝ˇ‡˝ˇ‡˚ˇ‡ˆ,?¸ˇÄ Û˙ˇ¿˘˝ˇ¯ˇ?˝ˇ‡¸˝ˇ‡¸˚ˇ‡ˆ+?¸ˇÄ
˙ˇ¿á˝ˇ¯
¸ˇ‡C˝ˇ‡C˚ˇ‡ˆ,?¸ˇÄ˙ˇ¿

˝ˇ¯Ä ?˝ˇ‡Ä˝ˇ‡Ä˚ˇ‡ˆ0?¸ˇÄ˚ˇ¿?˛ˇ¯@@˝ˇ‡

˛ˇ‡

¸ˇ‡ˆ0?¸ˇÄ˚ˇ¿
?˛ˇ¯ Ä˝ˇ‡Ç˛ˇ‡Ç¸ˇ‡ˆ0?¸ˇÄ
˚ˇ¿à?˛ˇ¯˝ˇ‡D˛ˇ‡D¸ˇ‡ˆ0?¸ˇĆ˚ˇ¿P?˛ˇ¯
˝ˇ‡(˛ˇ‡(¸ˇ‡ˆ0?¸ˇÄ@˚ˇ¿ ?˛ˇ¯˝ˇ‡˛ˇ‡¸ˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆò@@Ä
˜@Ä
˜∑G˜>?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆò@Ä¿
˜Ä¿
˜˜G
7>?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆò@¿

˜¿

˜
7G
w>?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆò@

@
˜

@
˜
wG
∑>?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆ?Œˇ‡ˆŒˇ‡ˆ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡
«`»
"    ê»
b»
R »
èë—@»
ÑÄ»
ƒ>»¡¡¡ò@
@
Ä
˜
@
Ä
˜
∑G
˜>¡¡%† p
 ˝
 @ ˝:HÂ$Äp8Ä 
 
¸
@ ˝@Â)%'¢»⁄Ÿ•"5ã¨áp∏2÷÷F»À¢lQwR-Ç“í2ËõpÁ)%)e "jÆ•ï5JÅPUjjÀIU%4j°UVÖÔRUIMÄÁ)%I-8'$LDŒ∫&RrPâJJZR&I$OBû‰âJdâíIpÁ)%f:  FùÈh$#.ñ†∫êêt⁄ˇjLTb®âèî∂ø⁄ìÁ)%N.p8DíFG%I· Dîî\ë*DHc√Gy
c$Jë‡Á˛˙˚ ÙÑ‚˛˙˚†ÙÑ‚˛˙˚@ÙÑ‚¡¡:p8

†Ä8˛HÅHÅ
– ˛
$¯6 (

ƒ¸@

@

˛Äb¸ ¯<8%‘û91Y€ë÷æ+-)#.â±
5µ£¥eË∂
€ŸËõÅ€ïñîëó$ÿÄZ⁄»Ÿ1tMÄ˙<8*T&¢RÖR©i*‘T^ı%Tî—öö‰‘™IZi"´%IM    Bi*/zí™*hÄ≠MYiR§¶Ä˙<8‹§$úóî¬JI“ò‰î¶Hô$ëíí¨ôíRJ$…híIBJrJS$LRHÅ)IKJÑ…$Ä˙<8P®IÜ¥    €õPV    <à˘Kk˝©0ç$$9=~⁄¶õEYÀ⁄ìÑõD|•µ˛tòGRõ∑ÌIÄ˙;7N–i<€ç="í#§ç(x¶2D© r%%-(îë$FíBmdëí<S"THê8ííãíEHâ˘Ù
˛
@ıĘ
 ÌÙ
˛
@ıĘ
 Ì
@Í
 Ì¡¡
"@0Ä ¿«ú
٠
 ˝A @
 †
Ÿ§_ŸrMáNHÉwQ»h!8+∏D†€¨°"¢¶àR†%®Rî8Bu@´–€    Eû$≈$áÖ¿?flÑ«
d∏ Ç&8%‹ê€ÁGÁIÅ…        a
µ†1HK- €E∫EDâûËÁN&‹Ÿ‰02r6Ó¿€Ù˙@
⁄Ù˙@
⁄Ù˙@
⁄¡¡¡¡¡¡¡¡¡¡¡¡¡¡
p8Õ

àÕ§Bk)¨åŒ;‘¢5w)P&îŒíô¬    %%sê$†Œ•-
HI⁄ I¨Œÿ»‡‰J1q‡iŒ
˛!˝@
˛!˝@
˛!˝@ ¡¡Ä@h ŒÄ
˛@  Œò@
Ä
¿
˜
Ä
¿
˜
˜G7>    ⁄&A@+‡Í—ÒXœ&J°
†TAI*¢†œ    "—¬¿îÇQtD†œCó1¯¬⁄EÂ@œB»ÁŒË®Ér:B@œ˙…˙…¡¡¡à@˛    ú∏¸Ä◊Äà    @˛    à

HÄ◊ëÀΔŒV±
uí
I÷\ñ‡Ÿ2ç√T©
—
ÊZ™K(à©Iÿ
    
"e»Úë"íÙëg    2H‡Ÿ    ã$Ì52#§FŸ¡ë˙ê Ÿó>Ft∂Ò…">Gr•<ëoQ¿Ÿˆ˛Ä”ˆ”Û–¡¡
ˇ Œ
R     ŒJRGıØ%ÇŒ≠(íÃ"RRŒ•)p§[¬îí
Œ≠JA6p‰ˆ§Œˆå9§_D§DLŒ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜7Gi>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜wG∑>
¡¡Õ3ıÕ@ˆ Œ ˆÕ@ˆÕ@ˆÕ@ˆ Œ ˆÕ@ˆ Œ ˆÕ@ˆÕ@ˆÕ@ˆ Œ ˆÕ@ˆ ˙Ę@˙˘ ˙ ˙ ˆ˙

@˜†˙˘P˙P˙@ˆ˙
 ¯

˙"˘à˙à˙@ˆ˙
¯
˙A˙

˚

˙@ˆ! ˚
¯
˙
ÄÄ˚
˚
˙ ˆ ˙
¯
˚
@˚

˚

˙@ˆ$ ˚
 ¯

˚ ˚ĸÄ˚ ˆ#˙
@
¯ ĸ˚@¸@˚@ˆ$˙ÄĢ@@¸˚  ¸  ˚@ˆ%˚
@˘Ä ¸˚@¸@˚@ˆ( ¸ ˙
¸ ˚ĸÄ˚ ˆ(˚˙¸@
¸
˝
˚@ˆ+ ¸˙¸ÄÄ˝˝˚ ˆ*˚˙˝
˛@˝
˝
˚@ˆ,˚ Ç˙¡˝
¯ ˝‡Ä˛‡Ä¸@ˆ-˚@ A˙  IJ˝@˛@¸@ˆ0 ¸ @ Ä˚ @˛˝ ˛ ¸ ˆ-˚ò˙LIJ
    Å˝&@˛&@¸@ˆ- ¸‰
˙r¸Ä@†˝9IJ9ĸ ˆ-˚?«Ä˚ü„¿˝@s¸x˝

œÒ‡˛

œÒ‡¸@ˆ+˚
Ä˚
å
¿˝ Ä8¸ÄF‡˝ÄF‡¸@ˆ*˚
ÄÄ˙Ä@
¿˝8¸@ ‡˝@ ‡¸@ˆ+ ˚Ä@Ä˙@ 
¿˝8¸ ‡˝ ‡¸ ˆ)˙@0Ä˙ 
¿˝8¸‡˝‡¸@ˆ+ ˚ ÛÄ˙˘¿˝ˇ8¸¸‡˝¸‡¸ ˆ)˙
Ä˙á¿˝
¯¸C‡˝C‡¸@ˆ(˙Ä˙

¿¸Ä 8¸ć˝ć¸@ˆ˙
¯
˙
@@˚


˚


˙@ˆ ˚
¯

˙
 Ä˙Ç˙Ç˙ ˆ˙

˜à˙˘D˙D˙@ˆ ˙†˜P˙
˘(˙(˙ ˆ˘@˜ ˙˘˙˙@ˆÕ@ˆÕ@ˆ Œ ˆ
ÊÈ@ˆ ˙¿˜0˙˘8˙8˙ ˆ˙

‡˜x˙
Ä˙l˙l˙@ˆ˙
0˜Ã˙
0¿˙Δ˙Δ˙@ˆ˙
ò¯

é˙
h‡˚

ã˚

ã˙@ˆ# ˚
¯
˙
‡˚
ĸ
Ä˚ ˆ!˙
¯
á˙
Ä˚ÉĸÉÄ˚@ˆ" ˚0?ˇˇ˛˚§˙
Ä˙¢˙¢˙ ˆ!˙?ˇˇ˛˚Ñ˚
¯Ä˙Ç˙Ç˙@ˆ$˙??ˇˇ˛¸
ƒ˚
HÄ˚
¬˚
¬˙@ˆ$˙)ê8¸
Ã˚
àÄ˚
 ˚
 ˙@ˆ) ˚!;ˇ<¸
DˇÄ
Ä˚
B˚
B˙ ˆ'˙1;ˇ~¸
    D@Ä
Ä˚
    B˚
    B˙@ˆò@@Ä
˜@Ä
˜∑G˜>
) ˚#0;˛Á¸

d@¿
*Ä˚

b˚

b˙ ˆ'˙!;˛√¸
DOˇ@
Ä˚
B˚
B˙@ˆ0˙%;˛√Ó¸D@@
HÄ@˝BPAB @ˆ0˙)ê;˛ÁÓ¸Ãg¸@
àĆ˝ @A  @ˆ3 ˚!;‡~.¸D @
ÄÆÈIJB◊q4¥B…K'  ˆ1˙1;Ï<.¸    D'ˇ@
ÄÈõ¿˛    BYOz¸    B+oó†@ˆ2 ˚#08.¸
d @
*Åö˝
bYICD
b&å  ˆ1˙!8?.¸D0@
ÅÈ¿˛BWI:<Bƒãì†@ˆ+˙%8sèÓ¸D7ˇ@
HÄÄ˝B
˝
B˙@ˆ+˙)ê8·œÓ¸à @
àÄÄ˝ ˝
 ˙@ˆ) ˚!9ˇ‡¸
D/¸@
Ä˚
B˚
B˙ ˆ'˙19ˇ‡¸
    D‡@
Ä˚
    B˚
    B˙@ˆ/ ˚#08¸
d`¿
*ÄIJ
b
˛

b˙ ˆ1˙!?ˇˇfi¸D    ¿Ä
Ä“›¯˛BKsBflÄ@ˆ1˙%?ˇˇ˛¸D¿Ä
HÅÎÚ‡˛BØ…¿B?7ß¿@ˆ1˙)ê?ˇˇ˛¸Ã    Ä
Ä
àÅò˛ 4I0  ö˛@ˆ/ ˚
!¯D˛
ÄËÚp˛B£»‡Bªù¿ ˆ'˙
1¯    Dˇ¸˛
Ä˚
    B˚
    B˛˛@ˆ& ˚
#0¯

d˚
*Ä˚

b˚

b˛8˛ ˆ&˙!
‚ê˚DIJ
Ä˚
B˚
B˙@ˆ)˙%
 ˚DIJ
HÄ˚
B˚B@˝@ˆ*˙)ê
Ûp¸Ã6˜˛
àÄ˚
 ˚ @˝@ˆ- ˚!
Ú¥»¸D
à ˛
Ä˚
B˚B3[IJ ˆ*˙1
¥»¸    Dƒ ˛
Ä˚
    B˚    BLÊ˝@ˆ- ˚#0
ÓìH¸
d<Ò˛
*Ä˚

b˚
bLQIJ ˆ&˙
!¯D@˛
Ä˚
B˚B3fl˝@ˆ#˙
%¯D@˛
HÄ˚
B˚
B˙@ˆ ˙
)ê¯
Ã˚
àÄ˚
 ˚
 ˙@ˆ" ˚
!¯
D˚
Ä˚
B˚
B˙ ˆ ˙
1¯
    |˚
Ä˚
    B˚
    B˙@ˆ! ˚#˜

@˚
*Ä˚

b˚

b˙ ˆ˙!˜
@˚
Ä˚
B˚
B˙@ˆ˙%˜
|@˚
HÄ˚
B˚
B˙@ˆ!˚
È¿¯
h˚
àÄ˚
 ˚
 ˙@ˆ" ˚
¿¿¯
0`˚
Ä˚
B˚
B˙ ˆ ˙
qį
¿˚
Ä˚
    B˚
    B˙@ˆ! ˚3˜
Ä˚
*Ä˚

b˚

b˙ ˆ˙˜˙
Ä˚
B˚
B˙@ˆ˙˜˙
HÄ˚
B˚
B˙@ˆÁ
àÄ˚
 ˚
 ˙@ˆ Ë
Ä˚
B˚
B˙ ˆÁ
Ä˚
    B˚
    B˙@ˆ  Û?˚ˇ˛
*Ä˚

b˚

b˙ ˆ#
ˆˇ‡ ˚˛
Ä˚
B˚
B˙@ˆ#
ˆ0 ˚˛
HÄ˚
B˚
B˙@ˆ#
ˆ0 ˚˛
àÄ˚
 ˚
 ˙@ˆ&
 ˆ    0 ‡˛
Ä˚
B˚
B˙ ˆ&
ˆ    0 
 ˛
Ä˚
    B˚
    B˙@ˆ&
 ˆ    0 Δfi~p˛
*Ä˚

b˚

b˙ ˆ&
ˆ    0 9ô9ê˛
Ä˚
B˚
B˙@ˆ,ÒD!¸    0 
ô9ê˛
HÄ˚
B˚
B˙@ˆ,Å3¸    0 Áûp˛
àÄ˚
 ˚
 ˙@ˆ. á\‹3g1ŸÄ0 ˛
Ä˚
B˚
B˙ ˆ.˘M2-Ù˙}0 ‡˛
Ä˚
    B˚
    B˙@ˆ+ âM2-î a0 ˚˛
*Ä˚

b˚

b˙ ˆ+˜D“)tπ›0 ˚˛
Ä˚
B˚
B˙@ˆ'
˘@0 ¸
IJ
HÄ˚
B˚
B˙@ˆ*
˙Ä0 ⁄qπù¿˛
àÄ˚
 ˚
 ˙@ˆ&
 ˆ    0 5Jg“IJ
Ä˚
B˚
B˙ ˆ&
ˆ    0 5JfIJ
Ä˚
    B˚
    B˙@ˆ&
 ˆ    0 ’q•“@˛
*Ä˚

b˚

b˙ ˆ&
ˆ0 @˛˛
Ä˚
B˚
B˙@ˆ&
ˆ0 @˛˛
HÄ˚
B˚
B˙@ˆ#
ˆ0 ˚˛
àÄ˚
 ˚
 ˙@ˆò@Ä¿
˜Ä¿
˜˜G
7>
#
 ˆ0?˚ˇ¯˛
Ä˚
B˚
B˙ ˆ#
ˆˇ˚ˇ¯˛
Ä˚
    B˚
    B˙@ˆ
 
ˆˇı
*Ä˚

b˚

b˙ ˆÁ
Ä˚
B˚
B˙@ˆ˜˙˙
HÄ˚
B˚
B˙@ˆ˜<˙
Ä˚
àÄ˚
 ˚
 ˙@ˆ! ¯f˙
¿˚
Ä˚
B˚
B˙ ˆ˜√˙
0`˚
Ä˚
    B˚
    B˙@ˆ# ˘
£Ä˚
b0˚
*Ä˚

b˚

b˙ ˆ!¯√Ä˚
pp˚
Ä˚
B˚
B˙@ˆ˜B˙
@˚
HÄ˚
B˚
B˙@ˆ˜J˙
¿˚
àÄ˚
 ˚
 ˙@ˆ" ¯B˚
¯@˚
Ä˚
B˚
B˙ ˆ!¯
‚˚
@˚
Ä˚
    B˚
    B˙@ˆ# ˘
"˚
*@˚
*Ä˚

b˚

b˙ ˆ!¯
"˚
@˚
Ä˚
B˚
B˙@ˆ!¯
b˚
H@˚
HÄ˚
B˚
B˙@ˆ!¯
™˚
à¿˚
àÄ˚
 ˚
 ˙@ˆ# ˘
"˚
@˚
Ä˚
B˚
B˙ ˆ!¯
"˚
@˚
Ä˚
    B˚
    B˙@ˆ# ˘
"˚
*@˚
*Ä˚

b˚

b˙ ˆ!¯
"˚
@˚
Ä˚
B˚
B˙@ˆ!¯
b˚
H@˚
HÄ˚
B˚
B˙@ˆ!¯
™˚
à¿˚
àÄ˚
 ˚
 ˙@ˆ# ˘
"˚
@˚
Ä˚
B˚
B˙ ˆ!¯
"˚
@˚
Ä˚
    B˚
    B˙@ˆ# ˘
"˚
*@˚
*Ä˚

b˚

b˙ ˆ!¯
"˚
@˚
Ä˚
B˚
B˙@ˆ!¯
b˚
H@˚
HÄ˚
B˚
B˙@ˆ!¯
æ˚
è¿˚
èÄ˚
 ˚
 ˙@ˆ! ˘
 ˚

˙

˙
B˚
B˙ ˆ¯
 ˚

˙

˙
    B˚
    B˙@ˆ! ˘
 ˚
(˙

(˙

b˚

b˙ ˆ¯
<8˚
˙
˙
B˚
B˙@ˆ¯
X˚
F˙
F˙
B˚
B˙@ˆ¯
∞˚

å˙
å˙
 ˚
 ˙@ˆ  ˘
`˙ÿ˙

ò˙
B˚
B˙ ˆ¯
¿˙p˘˙
    B˚
    B˙@ˆ ˘

Ä˙ ˘`˙

b˚

b˙ ˆfi
B˚
B˙@ˆfi
B˚
B˙@ˆfi
 ˚
 ˙@ˆ ˙Óˇ‡˚
B˚
B˙ ˆ˘Ó0˚
    B˚
    B˙@ˆ ˙Ó0˚

b˚

b˙ ˆ˘Ó0˚
B˚
B˙@ˆ˘Ó0˚
B˚
B˙@ˆ˘Ó0˚
 ˚
 ˙@ˆ ˙Ó0˚
B˚
B˙ ˆ˘Ó0˚
    B˚
    B˙@ˆ$ ˙˝Äx˘0˚

b˚

b˙ ˆ"˘˝Ä@0˘0˚
B˚
B˙@ˆ%˘˝    ÓòD≥ª6s9∞¸0˚
B˚
B˙@ˆ%˘˝    ôºz˙RflOÀ‡¸0˚
 ˚
 ˙@ˆ' ˙˝    "ô†CBRŸL  ¸0˚
B˚
B˙ ˆ%˘˝    "Óúz:JóKπ‡¸0˚
    B˚
    B˙@ˆ" ˙¸à˚˚0˚

b˚

b˙ ˆ ˘¸à˚p˚0˚
B˚
B˙@ˆ˘Ó0˚
B˚
B˙@ˆ˘Ó0˚
 ˚
 ˙@ˆ ˙Ó0˚
B˚
B˙ ˆ˘Ó0˚
    B˚
    B˙@ˆ ˙Ó0˚

b˚

b˙ ˆ˘Ó0˚
B˚
B˙@ˆò@¿

˜¿

˜
7G
w>
˘Óˇ˚
B˚
B˙@ˆ˘
Óˇ˚
 ˚
 ˙@ˆ fl
~˚
B˙ ˆfi
    @˚
    B˙@ˆ fl

@˚

b˙ ˆfi
8@˚
B˙@ˆfi
4x˚
B˙@ˆfi
∞˚
 ˙@ˆ fl
`˚
B˙ ˆfi
¿˚
    B˙@ˆ fl
Ä˚

b˙ ˆfi
˙
B˙@ˆ÷
B˙@ˆ÷
 ˙@ˆ ÌÓˇB˙ ˆÏÔ
Ä    B˙@ˆ ÌÔ
Ä
b˙ ˆÏÔ
ÄB˙@ˆÏÔ
ÄB˙@ˆÏÔ
Ä ˙@ˆ ÌÔ
ÄB˙ ˆÏÔ
Ä    B˙@ˆ ̸
‡@˘
Ä
b˙ ˆÏ¸
å¿˘
ÄB˙@ˆÏ¸
›Ã€åÌĸ
ÄB˙@ˆÏ¸
ÎÚã~_?˚
Ä ˙@ˆ ̸
ãfS1˚
ÄB˙ ˆÏ¸
ËÚJ^NÔ˚
Ä    B˙@ˆ ̈ ˚
Ä
b˙ ˆÏ˜

¿˚
ÄB˙@ˆÏÔ
ÄB˙@ˆÏÔ
Ä ˙@ˆ ÌÔ
ÄB˙ ˆÏÔ
Ä    B˙@ˆ ÌÔ
Ä
b˙ ˆÏÔ
ÄB˙@ˆÏÓˇÄB˙@ˆÏÓˇIJ˙@ˆ ◊
@˙ ˆ÷
    @˙@ˆ ◊
:@˙ ˆ÷
0x˙@ˆ÷
p˙@ˆ÷
‡˙@ˆ ◊
¿˙ ˆ÷
Ä˙@ˆ ◊
˘ ˆÕ@ˆÕ@ˆ‚Ôˇ¸@ˆ „@Ô ˆ‚@Ô@ˆ „@Ô ˆ‚@Ô@ˆ‚@Ô@ˆ‚@Ô@ˆ „@˚8c‡˙ ˆ‚@˚•êÄ˙@ˆ „@˚•åœ2@¸ ˆ‚@˚9ì,…ĸ@ˆ‚@˚!ì,…ĸ@ˆ‚@˚ ‡åœ2@¸@ˆ „@Ô ˆ‚@Ô@ˆò@

@
˜

@
˜
wG
∑>
 „@Ô ˆ‚@Ô@ˆ‚@Ô@ˆ‚@Ô@ˆ „@Ô ˆ‚@Ô@ˆ „@Ô ˆ‚Ôˇ˛@ˆ‚?Ôˇ˛@ˆÕ@ˆ Œ ˆÕ@ˆ Œ ˆÕ@ˆÕ@ˆÕ@ˆ Œ ˆÕ@ˆ Œ ˆŒÃ¿ˆŒU@ˆ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡
«`»
"    ê»
b»
R »
èë—@»
ÑÄ»
ƒ>»¡¡¡ò@
@
Ä
˜
@
Ä
˜
∑G
˜>
¡¡%† p
 ˝
 @ ˝:HÂ$Äp8Ä 
 
¸
@ ˝@Â)%'¢»⁄Ÿ•"5ã¨áp∏2÷÷F»À¢lQwR-Ç“í2ËõpÁ)%)e "jÆ•ï5JÅPUjjÀIU%4j°UVÖÔRUIMÄÁ)%I-8'$LDŒ∫&RrPâJJZR&I$OBû‰âJdâíIpÁ)%f:  FùÈh$#.ñ†∫êêt⁄ˇjLTb®âèî∂ø⁄ìÁ)%N.p8DíFG%I· Dîî\ë*DHc√Gy
c$Jë‡Á˛˙˚ ÙÑ‚˛˙˚†ÙÑ‚˛˙˚@ÙÑ‚¡¡:p8

†Ä8˛HÅHÅ
– ˛
$¯6 (

ƒ¸@

@

˛Äb¸ ¯<8%‘û91Y€ë÷æ+-)#.â±
5µ£¥eË∂
€ŸËõÅ€ïñîëó$ÿÄZ⁄»Ÿ1tMÄ˙<8*T&¢RÖR©i*‘T^ı%Tî—öö‰‘™IZi"´%IM    Bi*/zí™*hÄ≠MYiR§¶Ä˙<8‹§$úóî¬JI“ò‰î¶Hô$ëíí¨ôíRJ$…híIBJrJS$LRHÅ)IKJÑ…$Ä˙<8P®IÜ¥    €õPV    <à˘Kk˝©0ç$$9=~⁄¶õEYÀ⁄ìÑõD|•µ˛tòGRõ∑ÌIÄ˙;7N–i<€ç="í#§ç(x¶2D© r%%-(îë$FíBmdëí<S"THê8ííãíEHâ˘Ù
˛
@ıĘ
 ÌÙ
˛
@ıĘ
 Ì
@Í
 Ì¡¡
"@0Ä ¿«ú
٠
 ˝A @
 †
Ÿ§_ŸrMáNHÉwQ»h!8+∏D†€¨°"¢¶àR†%®Rî8Bu@´–€    Eû$≈$áÖ¿?flÑ«
d∏ Ç&8%‹ê€ÁGÁIÅ…        a
µ†1HK- €E∫EDâûËÁN&‹Ÿ‰02r6Ó¿€Ù˙@
⁄Ù˙@
⁄Ù˙@
⁄¡¡¡¡¡¡¡¡¡¡¡¡¡¡
p8Õ

àÕ§Bk)¨åŒ;‘¢5w)P&îŒíô¬    %%sê$†Œ•-
HI⁄ I¨Œÿ»‡‰J1q‡iŒ
˛!˝@
˛!˝@
˛!˝@ ¡¡Ä@h ŒÄ
˛@  Œò@
Ä
¿
˜
Ä
¿
˜
˜G7>
    ⁄&A@+‡Í—ÒXœ&J°
†TAI*¢†œ    "—¬¿îÇQtD†œCó1¯¬⁄EÂ@œB»ÁŒË®Ér:B@œ˙…˙…¡¡¡à@˛    ú∏¸Ä◊Äà    @˛    à

HÄ◊ëÀΔŒV±
uí
I÷\ñ‡Ÿ2ç√T©
—
ÊZ™K(à©Iÿ
    
"e»Úë"íÙëg    2H‡Ÿ    ã$Ì52#§FŸ¡ë˙ê Ÿó>Ft∂Ò…">Gr•<ëoQ¿Ÿˆ˛Ä”ˆ”Û–¡¡
ˇ Œ
R     ŒJRGıØ%ÇŒ≠(íÃ"RRŒ•)p§[¬îí
Œ≠JA6p‰ˆ§Œˆå9§_D§DLŒ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜7Gi>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜iG©>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜©GÈ>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜ÈG)>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜)Gi>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜iG©>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜©GÈ>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ÈG)>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜)G[>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜iG©>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜©GÈ>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜ÈG)>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜)Gi>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜iG©>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜©GÈ>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ÈG)>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜)G[>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@l.Introduction to Interapplication Communication4⁄*˙
¯

(‡*1-6    )BSharing Data ¿)7Among à0)Applications4^*¿
¯
°dONLNd\xh√(exApple Computer(Ä°dONLNd\√h
)K, Inc. When the ¥°dONLNd\
h
Ù)D5AppleScript component executes a script, it performs °dONLNdShxt
c(qx7the actions described in the script, including sending ó °dONLNdäh
ct
„)ÎApple events to applications °dONLNdßtxÄæ(}xwhen necessaryx@°dONLNdµtΩĬ)E. °dONLNd∏Éxè±(åx“Supporting ‡ °dONLNdƒÉ±è
z)9+AppleScript and Other Scripting Languages,”w†°dONLNdÔÉ
{è
»)  which begins on Ë°dONLNd
É
ȏ
fl)Mpage ¬‡°dONLNd
É
‡è
Ú)1-13¿°dONLNd
    É
Ûè
¯), °dONLNd
èxõfi(òxdescribes how the OSAÕ`°dONLNd
 èfiõ
î)f+ makes it possible for your application to ,Zapf Dingbats°dONLNd
L†x©}(ßx
n
°dONLNd
NûÑ™ç)prG °dONLNd
Pûé™
8)
$ovide human-language equivalents to ˇ‡°dONLNd
tû
7™
‘)©$Apple event codes so that scripting °dONLNd
ò™Ñ∂Â(≥Ñcomponents can send RÄ°dONLNd
¨™Ê∂
1)byour application ¿°dONLNd
Ω™
2∂
W)Lthe appr.`°dONLNd
≈™
W∂
x)%opriate Ɔ°dONLNd
Õ™
x∂
Æ)!Apple event˘`°dONLNd
ÿ™
Æ∂
∫)6s d“ °dONLNd
€™
ª∂
Ò)uring script °dONLNd
Ë∂ѬÆ(øÑ    execution°dONLNd
Ú«x–}(Œx
n
°dONLNd
Ù≈Ñ—»)allow users to rWÄ°dONLNd≈»—⁄)DecorÀ‡°dONLNd≈⁄—
)d their actionŇ°dONLNd≈
—
);s i'@°dONLNd≈
—
{)
n the form of a script°dONLNd0÷xfl}(›x
n
°dONLNd2‘ч
)manipulate and execute scripts°dONLNdQÈlq(Ôl
n
°dONLNdSÊxÚ±)Sending and r熰dONLNd`ʱÚ
)9esponding to Apple events.fl†°dONLNdzÊ
Ú
)l
 2°dONLNd{Ê
 Ú
&)
YÚÄ°dONLNd|Ê
%Ú
î)our application can send Ô†°dONLNdïÊ
îÚ
 )oApple event:`°dONLNd†Ê
ÀÚ
fi)7s dir¿Ä°dONLNd•Ê
fiÚ
ı)ectly °dONLNd´Úx˛‰(˚xto other applications to rÓ °dONLNd≈Ú‰˛
)lequest s^°dONLNdÕÚ
˛
d)$ervices or informatioq‡°dONLNd‚Ú
d˛
ç)\
n or to pr™`°dONLNdÏÚ
ç˛
fl))ovide information.O@°dONLNd˛Ú
‡˛
Ë)S T°dONLNdÚ
˲
Ô)o °dONLNd˛x

ù(
xsupport îÄ°dONLNd
˛ù


fi)%FAppleScript and most other scripting languages based on the OSA, your °dONLNdP

x
ı(
xapplication must be able to r °dONLNdm

ˆ

$)~
espond to fi°dONLNdw


#

b)-Apple events. e¿°dONLNdÖ


c

Â)@“Sending and Responding to °dONLNd†
x
"ª(
xApple Events,”Ÿ‡°dONLNdÆ
ª
"
)C which begins on J@°dONLNdø

    
"
 )Npage % °dONLNdƒ

!
"
.)1-9y°dONLNd«

.
"
È)*, describes how applications can send and °dONLNdÒ
"x
.{(
+x
rE°dONLNdÚ
"|
.™)
espond to     ‡°dONLNd¸
"™
.
:).!Apple events with the aid of the †°dONLNd
"
:
.
õ)êApple Event Manager °dONLNd0
"
õ
.
ù)a
.°dONLNd2
7l
>q(
=l
n
°dONLNd4
4x
@±)Sending and r熰dONLNdA
4±
@
C)9%esponding to other high-level events.x‡°dONLNdf
4
D
@
˜)ì' The Event Manager allows applications °dONLNdç
@x
L
&(
Ix(to support high-level events other than ˘†°dONLNdµ
@
&
L
Ã)Æ%Apple events. See the chapter “Event °dONLNd⁄
Lx
X≤(
UxManager” in À¿°dONLNdÊ
L≤
X
0):Inside Macintosh: Macintosh T@°dONLNd
L
0
X
t)~oolbox Essentials„@°dONLNd
L
t
X
ÿ)D for information about °dONLNd+
Xx
dΔ(
axhigh-level events.°dONLNd>
ml
tq(
sl
n
°dONLNd@
jx
vÈ)Exchanging message blocks.ᆰdONLNdZ
jÈ
v
)q
 The PPC T#`°dONLNdd
j

v
Û)11oolbox allows applications to exchange blocks of °dONLNdï
vx
ÇÊ(
xdata with each other by r›¿°dONLNdÆ
vÊ
Ç
˜)n<eading and writing low-level message blocks. This method of °dONLNdÍ
Çx
é
c(
ãx5communication is most useful for applications that ar:‡°dONLNd
Ç
d
é
⁄)Ïe closely integrated, specifi. °dONLNd<
Ç
€
é
Ú)wcally °dONLNdB
éx
öÏ(
óxdesigned to work togetherz°dONLNd[
éÏ
ö
Ò)t=, or dependent on each other for information. It can also be °dONLNdò
öx
¶
,(
£x*used in code that is not event-based. See —@°dONLNd¬
ö
,
¶
⁄)¥$“Exchanging Message Blocks” on page Í°dONLNdÊ
ö
⁄
¶
Ï)Æ1-22=‡°dONLNdÍ
ö
Ì
¶
Ô)
 °dONLNdÎ
¶x
≤
(
Øx$for a summary of the capabilities pr¸@°dONLNd
¶

≤
p)ùovided by the PPC TU†°dONLNd"
¶
p
≤
ê)[oolbox.°dONLNd*
∑l
√¡(
¿lAll forms of IAC ar∞ °dONLNd=
∑¡
√
)Ue based on the pr °dONLNdN
∑

√
Á)L1emise that applications cooperate with each otherÒ‡°dONLNd
∑
Ê
√
Î)Ÿ. °dONLNdÅ
ƒl
–
‹(
ÕlSBoth the application sending a high-level event or low-level message block and the °dONLNd‘
—l
›§*application r{‡°dONLNd·
—§
›˚)8eceiving it must agr∞@°dONLNdı
—˚
›
/)Wee on the prƇ°dONLNd

—
/
›
•)4otocol for communication. i@°dONLNd
—
¶
›
¨)w
Y)¿°dONLNd
—
¨
›
‰)ou can ensurå °dONLNd(
—
‰
›
Î)8e °dONLNd*
fil
Ít(
Álefo‡°dONLNd,
fit
Í
€)Nfective high-level communication between your application and other Macintosh °dONLNdz
Îl
˜
(
Ùl&applications by supporting the standar’@°dONLNd†
Î

˜
)´d †°dONLNd¢
Î
 
˜
m)    Apple events defiÄ°dONLNd≥
Î
n
˜
ú)Nned in the ⁄`°dONLNdæ
Î
ú
˜
–).Apple Event °dONLNd 
¯l÷(
lRegistry: Standard Suites.(`°dONLNd‰
¯◊Ÿ)k
 

*&
¯4*&
¯

6*>
¯47*>
¯ 8*8
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNdÁ#*6å(1*Sharing Data ¸™°dONLNdÙ#ã6Δ)aAmong nÜ°dONLNd˙#Δ6
");ApplicationsˇˇˇˇˇˇV˛(1

1
°dONLNd    GlS
|(Pl<All Macintosh applications can use the Scrap Manager to shar‡ °dONLNd    DG
|S
¿(P
|e static data by °dONLNd    UTl`í(]lallowingf °dONLNd    ]Tì`ï)'
 Ê °dONLNd    ^Tï`
Ò)Lthe user to copy and paste data between documents. Dynamic data sharing, or °dONLNd    ™alm
Ë(jlUautomated copy and paste operations between applications, extends this capability to °dONLNd    ˇnlz
¶*Edynamically changing data. The Edition Manager lets applications shar)¿°dONLNd
Dn
ßz
¯(w
ße dynamic data at °dONLNd
V{láè(Ñlthe userõ °dONLNd
^{êáù)$’s r‰`°dONLNd
b{ùáæ)equest. i†°dONLNd
j{øá≈)"
Y* °dONLNd
k{Ň
˜)Fou incorporate publish and subscribe capabilities in your application °dONLNd
±àlî
V(ël4much as you incorporate copy and paste capabilities.ˇj@@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@ä.Introduction to Interapplication Communication4⁄ä˙(‡äSharing Data ¿)7Among à0)Applications

, (‡    1-7
ˇˇˇˇˇˇˇˇ4^4|lòÄ2^A|rMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^A|r^A|r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
^6|@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^6|@^6|@˜˜˜˜˜˜˜˜˜˜˜˜˜˙ˇˇ
˙ˇ
˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜
4Å4
w?òÄ
Å6
w@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""Å6
w@Å6
w@$˜
˙ˇ˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛
¸ˇ˛¸ˇ˝˚ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛
˙ˇ˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˛¸ˇˇ
ˇ˛ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˜˜˜˜
˙ˇ
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛˜˛˛ˇ˝
ˇˇˇ˛
ˇˇˇ˛    ˇˇˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
˙ˇ˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˝˛ˇ˛
˛ˇ˛ˇˇ    ˇ¸
ˇ    ˇ¸
ˇ
˛ˇ˛ˇˇ˜˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähë(eä
A∫†°dONLNd
\ëh
)T user can publish data by selecting a portion of text, graphics, or other data in a °dONLNdUiäu

(rädocument and choosing Cr5†°dONLNdmi
u
J)xeate Publisher frW‡°dONLNd~i
Ju
Æ)Hom the Edit menu. In rL°dONLNdîi
Æu
Ì)desponse, your °dONLNd¢väÇ
Ü(ä:application saves the selected information in a separate fiÿ°dONLNd›v
ÜÇ
π)¸le. This stor€`°dONLNdÍv
πÇ)3ed information is °dONLNd¸Éäèç(åä
rE°dONLNd˝Ééè¢)eferr„¿°dONLNd
É¢è”)ed to as an 
è`°dONLNd
É‘è˜)2edition.—†°dONLNd
ɘè)#= The user can subscribe to an edition by choosing Subscribe Td@°dONLNd
SÉè(åo °dONLNd
Uêäúë(ôäfrò‡°dONLNd
Wêëú
 )om the Edit menu; when the useΔ†°dONLNd
uê
 ú
J)èr selects aaÄ°dONLNd
Äê
Kú
S)+ fiÓ@°dONLNd
Éê
Sú
·)"le that contains an edition, your °dONLNd
•ùä©
4(¶ä'application includes the information fr$`°dONLNd
Ãù
5©
•)´om the edition in the curr–¿°dONLNd
Êù
•©
˙)pent document. The °dONLNd
¯™ä∂
-(≥ä%information in an edition can be sharl °dONLNd™
-∂
ó)£ed by many documents.°dONLNd3ºä»¢(≈äFigurR¿°dONLNd8º¢»∂)e 1-2@°dONLNd=º∂»

) shows the princil†°dONLNdNº
»
)Lpal rú °dONLNdSº
»
 )&elationships among the Edition Manager„ °dONLNdyº
…»)≥, the publishing °dONLNdä…ä’
g(“ä3application, the subscribing application, and the fiΔ‡°dONLNdæ…
g’
·)›le that contains the edition. ‹°dONLNd‹…
·’)zIn addition °dONLNdË÷ä‚©(fläto the r⁄@°dONLNd÷©‚
2)!elationships illustrated in the fi1†°dONLNd÷
3‚
B)ägur凰dONLNd÷
B‚
T)e, thj@°dONLNd÷
U‚
¢)e Edition Managed¿°dONLNd*÷
£‚
Ø)Nr ufiÄ°dONLNd-÷
Ø‚
œ)ses the ° °dONLNd5÷
œ‚    ) Apple Event °dONLNdA„äÔ∑(Ïä    Manager t‘`°dONLNdJ„∑Ô
)-o communicate with aÁ‡°dONLNd^„
Ô
i)bpplications that arˆ‡°dONLNdq„
iÔ
”)Pe sharing dynamic data.


H
"4
H
""
H]

ˇ·ˇ‚7^
    °dONLNdâ
ä
¥(
ä
Figure 1-2°dONLNdî
Ã

å)B0Sharing data with the aid of the Edition Manager
°dONLNdΔ
·ä
Ìë(
Íä
A∫†°dONLNd«
·ë
Ìì)
 
:†°dONLNd»
·î
Ì¿)    publisher•@°dONLNd—
·¿
Ì
–),? is a portion of a document that is made available to other docé@°dONLNd
·
—
Ì
fl(
Í
—umi`°dONLNd
·
‡
Ì
Ù)ents °dONLNd
Óä
˙ó(
˜äthrX¿°dONLNd
Óó
˙·)ough an edition. Ë@°dONLNd+
Ó·
˙Ë)J
A"‡°dONLNd,
ÓÈ
˙Î)
 
¢‡°dONLNd-
ÓÎ
˙
)
subscriberb°dONLNd7
Ó

˙
¢)0 is a portion of a document thaz`°dONLNdV
Ó
¢
˙
´)át r
¿°dONLNdY
Ó
¨
˙
≈)
eads tÊÄ°dONLNd_
Ó
≈
˙    )he information °dONLNdn
˚äë(äfrò‡°dONLNdp
˚ë”)om an edition. °dONLNdÄä¢(äFigurR¿°dONLNdÖ¢∂)e 1-3@°dONLNdä∂
p)( shows a document containing a publisher- °dONLNd≤
q
É)ª, a fiπ‡°dONLNd∏
É) le containing an edition, and a °dONLNdÿä&
(#ä document containing a subscriberꆰdONLNd¯
&
_)ï. The bottom fi$Ä°dONLNd
`&
À)Ash in the Fishes of the W@°dONLNd 
À&)korld document °dONLNd.'ä3≈(0äis a publisher@°dONLNd<'≈3
);. The information fr§@°dONLNdP'
3)V7om this publisher is made available to other documents °dONLNdá4ä@ó(=äthrX¿°dONLNdä4ó@
+)#ough the Illustration edition. The  °dONLNd≠4
+@)î/Aquarium poster document contains a subscriber °dONLNd‹AäM˝(Jäthat gets its information frÍ@°dONLNd¯A˝M
)s=om the Illustration edition. Note that when a user selects a °dONLNd5NäZ
Ò(WäPpublisher or subscriber within a document, your application should display a bor4`°dONLNdÖN
ÚZ(W
Úder °dONLNdâ[ägú(däsurr{¿°dONLNdç[úg
:)#ounding the publisher or subscriberz†°dONLNd∞[
:g
<)û
.°dONLNd≤mäy
(väIn general, when a user modifiú¿°dONLNd–m
y)á7es the contents of a publisher and saves the document, °dONLNdzäÜ(ÉäTyour application should write the new data to the edition. The Edition Manager then °dONLNd[áäì∞*    uses the I¿°dONLNddá∞ì)&LApple Event Manager to inform all open applications with subscribers to the °dONLNd∞îä†    (ùäWedition that it has been updated. These applications can then automatically update the °dONLNd°ä≠
*subscribers in the documents.


!â
 4
 à
!âò@@
˜@
˜
!â
aÄ¡¡?·ˇ¸„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?Áˇ¿˛ˇ˛„?Áˇ¿˛ˇ˛„?ˇ‡˛Ìˇ¡¿ˇ˛„?ˇ·ˇˇÌˇ¬ ˇ˛„?ˇ·Ìˇƒˇ˛„?ˇ·Ìˇƒˇ˛„?ˇ·?ˇêÌˇƒ<ˇˇ˛„?ˇ·%êÌˇ¬¿ˇ˛„?ˇ·?ˇêÌˇ¡x0ˇ˛„?ˇ·%êÌˇ¿@ˇ˛„?ˇ·?ˇêÌˇ¿`2ˇ˛„?ˇ·&
–Ìˇ¿Å
ˇ˛„?ˇ·80Ìˇ¿Ç<ɡ˛„?ˇ·0@Ìˇ¡ jCˇ˛„?ˇ· 2Ìˇ¬@ï#ˇ˛„?ˇ·A
Ìˇ¬Å
#ˇ˛„?ˇ·Ç<èÌˇƒÉ#ˇ˛„?ˇ· jOÌˇƒÇ#ˇ˛„?ˇ‚@ï/Ìˇƒ!BCˇ˛„?ˇ‚Åö/Ìˇƒ"
!√ˇ˛„?ˇ‰Çï/ÌˇƒBˇ˛„?ˇ‰í/Ìˇ¬Bàˇ˛„?ˇ‰!OÌˇ¬DDˇ˛„?ˇ‰"œÌˇ¡¢ˇ˛„?ˇ‰BÌˇ¿ƒQˇ˛„?ˇ‚BÌˇ¿D®Éˇ˛„?ˇ‚DÌˇ¿$T√ˇ˛„?ˇ·Ìˇ¿+#ˇ˛„?ˇ‡ƒÌˇ¿
#ˇ˛„ò@@Ä
˜@Ä
˜
aâ
°Ä?ˇ‡DÌˇ¿#ˇ˛„?ˇ‡$Ìˇ¿cˇ˛„?ˇ‡Ìˇ¿
„ˇ˛„?ˇ‡
Ìˇ¿àˇ˛„?ˇ‡8Ìˇ¿pˇ˛„?ˇ‡¿Ìˇ¿˛ˇ˛„?ˇ‡˛Ìˇ¿˛ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„ò@Ä¿
˜Ä¿
˜
°â
·Ä?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„?·ˇ˛„·ˇ˛„¡¡¡¡¡¡¡¡¡¡¡¡    é8`3«
DêLÄ»
ƒÄàÄ»
§pãÄ»
    †à@»
#0î@»
à|¿cÄ»¡¡¡¡¡ ¿`@¡I
 #b@ç"fi Äpê@˛A    
 
Ç@Ñ (fiò@¿

˜¿

˜
·â!Ä$OF»˛YZ€¡Àäu]c¨Çß«YrMÖ1vWïÄ‚#R…  j¢lÇïI°5E*
Çjá)"¶ÖRö©*·#íY8'@L§LѶ$)ë"'âRÑOJE$Öîì)r·#Ãr  Ä&_Δõø<*Ÿc.v\€gIâßÊD·#úZpïDóÍ(4íBI [    ìünDâ=%N<·"˙
Ģ
¯‡"˙
Ģ¯‡˙¯¯‡¡¡8pp0 
¡˛Ë
 ˛
‡@‡@tà˝
@    ˜6  P Å˛@
1¸@@
@@ ÄÄ˝˜;7'®;:9
aZfl¨ÔäÀJHÀ¢l@MmhÌz-ÄvˆGD˙&« vÂe•$e…6 ∂≤6L]`˘;7*®MBR䢙j,4
5ΩIU%4@¶¶π5*íVÄöH™…RSBPöJãfi§™äö +SVZT©)†˘;7›HI<ó$ƒLK§
&9%)í&I$A$§´&D§îÄíâ2Z$íDêíúíî…í JRR“°2I ˘;7QPì¥'fiûP¨O">R⁄ˇjL#I    O_∂©Å&—Vrˆ§Δ°&—)mù&‘ÑɶÌ˚R`˘;7O†“t€öu$î'IJ)åë*DHâIKJ%$I§êõY$DÑA§èΔHï$$§¢‰ëR"@˘ı˛
ı ˜

Ïı˛
ı ˜

ÏÒ
Í

Ï¡¡$Äc@!Ä!úÿ  ˝$îÄ@Ä‚ ÿ$≤Ù[úêîäÁ:£ê–$8W8E@⁄    ,¬E$≠•@wH
•(pIÍ@´†⁄
EºII)Ä)    á…p@NÑL8%› ⁄gèmSí#)¡k@`H»ñ-@⁄EÙäHí=–ΔéMπ∞Á0dr6ÔÄ⁄ı˙ÄŸı˙ÄŸı˙ÄŸ¡¡¡¡¡¡¡¡¡¡¡¡¡¡

‡pÃ

 çD÷R<¨-òÕ;‘§jÓIPF®Õíôƒ    JJ”êD¿Õ•-:êìö âÿÕÿ»·ƒîb—‡…"Õ
!˝Ä…
!˝Ä…
!˝Ä…¡¡ÄÄ– ÕÄ
˛Ä@ Õ    ⁄,ÅÄ[¡’ëÚXŒ&UA@§Çí*• Œ    "„Ç;Å%¢tI ŒCÆ"
ÈÖ¥EÍ@Œò@

@
˜

@
˜!âaÄB—«›—I‰:D@Œ˚ »˚ »¡¡¡ê@˛?¿Ä—Äê    @˛ÄÄ—£÷ÕéW…∞ëe≈`“döΔî™–"≤ÑääÄ“
-
$•…‰ê%xìÄ“    9ñ)≠i0Gúï—≠$>Fy6Ûë ÂÈ    —˜
Ø
á¡¡

ˇ Õ
í ÕT íã˚.+"Õ∫Qî$TT"Õ•2·$≥ƒòî
"Õ≠TÇ6‡Ë¸®$Õˆòs$∑H®HXÕ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜aâ°Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜°â·Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜·âÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜
!â
aÄ
¡¡‡30„‡„ ·„‡„‡„‡„ ·„‡„ ·„‡„‡„`àÏ0Ä„     @ÄÏ"„    ûgÔÌ<}ºÒ¿„ ôlú§Ì2”2 @„ôcú§Ì#212 @„~núú̸Ô<…¿„˚Ë
@„ ¸8ÈÄ„‡„ 
@Í`„˛
Í@„ùYπ∏ÌÓfnn„>Sg⁄dÌôiˆô„ &SbZdÌ    ôhñô„ù]…§ÌÓgri„ Èà˝„Èà˝„‡„‡„ ·„‡„ ·„‡„‡„ˆ˙ˇ˛˙

¿˝„ 
ˇˇ¸˙˙
 ˝„
¸˙˙
˝„ 
¸˙˙
˝„
?ˇê¸˙˙<ˇ˛„
%ê¸˛˛˙¿„
?ˇê¸˛_Ä˙
x0„ 
%ê¸˛| ˘@„
?ˇê¸}—8˘`2„ 
&
–¸ˇ£˛˘Å
„
80¸ˇÁˇ˘Ç<Ä„#
0@˛˛ˇ¿¸
 j@„#
 2˛˛ˇ‡¸@ï „# 
A
˛Ä˛ˇ¯¸Å
 „%!
Ç<Ä
ˇˇ¿üˇˇ˜|ˇ˚ˇ¯ˇ˚É „%! 
 j@
""`<˘ˇˇˇˇ¯"#ÄÇ „%!@ï 
0ˇˇÔć8¿!B@„%Åö 
DD`˛ˇ«8¿Ô˝‡8DEÄ"
!¿„%!Çï 
àà¿ˇˇÛG8‡Ô˝8àãB„%! í 
ˇ˝Äˇ˛p<Ô˚88ˇˆBà„%!!@ˇ¸¯Ô˙8DD„% "¿ˇ˛¯Ô˙∏
¢„ B¸ˇ¯˝pÔ˚?∏¸ƒQ„ B˚ˇˇÄpÔÅÒ∏¸D®Ä„ D˚ˇ¯¿Ô±·∏¸$T¿„  
˚~~¸
¿‡xa∏¸+ „˛
ƒ˚<
?_¯?‡¸a∏¸
 „ò@@Ä
˜@Ä
˜
aâ
°Ä
  D˚ˇfl¯>·Œ∏¸ „˛
$˚?ˇÒ¯„á∏¸`„˛
˚_ˇˇÄÁˇ8¸
‡„˛

˚ü˜Áˇ8˚à˛„ 8˚Ò‡‡8˚p˛„˛
¿˚¡¿˛ˇ¯˜„ ˜J
IJˇ¯˜„ˆ˙˛ˇ¯˜„ˆ˙Ù„ˆ˙Ù„ ˜˙Ù„ˆ˙Ù„ ˜˘ˇÙ„ˆ˘ˇÙ„˝0È0˛„˝xÈx˛„ ˛ÃÈÃ˛„˛

ñÍ

ñ˛„ #˜
xƒˆ
#˛„˛
á˜
@àˆÉÄ„˝ƒ˜C‹ŒˆΔ˛„˝å˜|Õ)ˆä˛„ ˛Ñ˜DÕ)ˆÇ˛„˛
‘˜{ƒ…˜
“˛„ dÍ

b˛„˛
DÍ
B˛„˛
DÍ
F˛„˛
ÃÍ
 ˛„ DÍ
B˛„˛
TÍ
    R˛„ dÍ

b˛„˛
DÍ
B˛„˛
DÍ
F˛„˛
ÃÍ
 ˛„ DÍ
B˛„˛
TÍ
    R˛„ dÍ

b˛„˛
DÍ
B˛„˛
DÍ
F˛„˛
ÃÍ
 ˛„ DÍ
B˛„˛
TÍ
    R˛„ dÍ

b˛„˛
DÍ
B˛„˛
DÍ
F˛„˛
ÃÍ
 ˛„ DÍ
B˛„˛
TÍ
    R˛„ dÍ

b˛„˛
DÍ
B˛„˛
DÍ
F˛„˛
ÃÍ
 ˛„ DÍ
B˛„˛
TÍ
    R˛„ dÍ

b˛„˛
|Í
~˛„˛
@Í
@˛„˛
¿Í
¿˛„ @Í
@˛„˛
qpÍ
9x˛„ 2`Í
0˛„˛
¿Í
`˛„˛
ÄÍ
¿˛„˛È
IJ„ò@Ä¿
˜Ä¿
˜
°â
·Ä
 È
˝„

„ˇ
„
 ‰
Ä„
‰
Ä„
‰
Ä„
‰
Ä„
 ‰
Ä„
‰
Ä„
 ‰
Ä„
‰
Ä„
˜≈ÑÛ
Ä„
˜ ÃÛ
Ä„
 ˜spÕú«fˆ
Ä„
˜Â4»∑”ÈÙˆ
Ä„
 ˜%4»∂S)ш
Ä„
˜›H•“Átˆ
Ä„
Ò
ı
Ä„
Òı
Ä„
 ‰
Ä„
‰
Ä„
 ‰
Ä„
‰
Ä„
‰
Ä„

„ˇ
Ä„

 
„ˇ
Ä„‡„ ·„‡„‡„‡„ ·„‡„ ·„‡„‡„‡„‡32„·UT„¡¡¡¡¡¡¡¡¡¡¡¡    é8`3«
DêLÄ»
ƒÄàÄ»
§pãÄ»
    †à@»
#0î@»
à|¿cÄ»¡¡¡¡¡ ¿`@¡I
 #b@ç"fi Äpê@˛A    
 
Ç@Ñ (fiò@¿

˜¿

˜
·â!Ä
$OF»˛YZ€¡Àäu]c¨Çß«YrMÖ1vWïÄ‚#R…  j¢lÇïI°5E*
Çjá)"¶ÖRö©*·#íY8'@L§LѶ$)ë"'âRÑOJE$Öîì)r·#Ãr  Ä&_Δõø<*Ÿc.v\€gIâßÊD·#úZpïDóÍ(4íBI [    ìünDâ=%N<·"˙
Ģ
¯‡"˙
Ģ¯‡˙¯¯‡¡¡8pp0 
¡˛Ë
 ˛
‡@‡@tà˝
@    ˜6  P Å˛@
1¸@@
@@ ÄÄ˝˜;7'®;:9
aZfl¨ÔäÀJHÀ¢l@MmhÌz-ÄvˆGD˙&« vÂe•$e…6 ∂≤6L]`˘;7*®MBR䢙j,4
5ΩIU%4@¶¶π5*íVÄöH™…RSBPöJãfi§™äö +SVZT©)†˘;7›HI<ó$ƒLK§
&9%)í&I$A$§´&D§îÄíâ2Z$íDêíúíî…í JRR“°2I ˘;7QPì¥'fiûP¨O">R⁄ˇjL#I    O_∂©Å&—Vrˆ§Δ°&—)mù&‘ÑɶÌ˚R`˘;7O†“t€öu$î'IJ)åë*DHâIKJ%$I§êõY$DÑA§èΔHï$$§¢‰ëR"@˘ı˛
ı ˜

Ïı˛
ı ˜

ÏÒ
Í

Ï¡¡$Äc@!Ä!úÿ  ˝$îÄ@Ä‚ ÿ$≤Ù[úêîäÁ:£ê–$8W8E@⁄    ,¬E$≠•@wH
•(pIÍ@´†⁄
EºII)Ä)    á…p@NÑL8%› ⁄gèmSí#)¡k@`H»ñ-@⁄EÙäHí=–ΔéMπ∞Á0dr6ÔÄ⁄ı˙ÄŸı˙ÄŸı˙ÄŸ¡¡¡¡¡¡¡¡¡¡¡¡¡¡

‡pÃ

 çD÷R<¨-òÕ;‘§jÓIPF®Õíôƒ    JJ”êD¿Õ•-:êìö âÿÕÿ»·ƒîb—‡…"Õ
!˝Ä…
!˝Ä…
!˝Ä…¡¡ÄÄ– ÕÄ
˛Ä@ Õ    ⁄,ÅÄ[¡’ëÚXŒ&UA@§Çí*• Œ    "„Ç;Å%¢tI ŒCÆ"
ÈÖ¥EÍ@Œò@

@
˜

@
˜!âaÄ
B—«›—I‰:D@Œ˚ »˚ »¡¡¡ê@˛?¿Ä—Äê    @˛ÄÄ—£÷ÕéW…∞ëe≈`“döΔî™–"≤ÑääÄ“
-
$•…‰ê%xìÄ“    9ñ)≠i0Gúï—≠$>Fy6Ûë ÂÈ    —˜
Ø
á¡¡

ˇ Õ
í ÕT íã˚.+"Õ∫Qî$TT"Õ•2·$≥ƒòî
"Õ≠TÇ6‡Ë¸®$Õˆòs$∑H®HXÕ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜aâ°Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜°â·Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜·âÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜âSÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜SâìÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜ìâ”Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜”âÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜âSÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜SâìÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ìâ”Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜”âÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜âSÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜SâìÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜ìâ”Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜”âÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜âSÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜SâìÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ìâ”Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜”âÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇÉ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@l.Introduction to Interapplication Communication4⁄*˙
¯

(‡*1-8    )BSharing Data ¿)7Among à0)Applications4^*¿
¯

g*w
¯4g*w
¯"h*]

ˇ·ˇ‚7^
°dONLNd\lgñ(dl
Figure 1-3°dONLNd\Æg¥)B
A0°dONLNd\¥g€)
 publisherÖ °dONLNd\⁄g
M)&, an edition, and a subscriber
°dONLNd6
fl
r
f(
ol8For example, suppose the user changes the color of the fiÉ¿°dONLNdo
f
f
r
—)˙sh in the Fishes of the WqÄ°dONLNdà
f
—
r
Â)korld °dONLNdç
sl
Δ(
|ldocument shown in  °dONLNdü
s«
fl)[FigurÚ¿°dONLNd§
sfi
Ú)e 1-3ê@°dONLNd©
sÛ

ı):, then saves the document. This automatically changes the °dONLNd„
Äl
å
ï(
âlEIllustration edition, and the subscribing application can update the p‡°dONLNd
(
Ä
ï
å
„(
â
ïAquarium poster °dONLNd
8
çl
ô
4(
ñl-document if that’s what the user wants to do.°dONLNd
f
ül
´Ñ*FigurR¿°dONLNd
k
üÑ
´ò)e 1-4@°dONLNd
p
üò
´
) shows how a user might cr:‡°dONLNd
ä
ü

´
S)zeate a poster fr\†°dONLNd
ö
ü
S
´
Ó)A"om information contained in other °dONLNd
º
¨l
∏ú(
µl    documentsw°dONLNd
≈
¨ù
∏ü)1
.


⁄*
Î
¯4
€*
Î
¯"
€*]

ˇ·ˇ‚7^
    °dONLNd
«
–l
ۖ(
ÿl
Figure 1-4°dONLNd
“
–Æ
€
`)B,Sharing dynamic data with other applications

w*
N
¯4v)w*ò@@
˜@
˜w*∑!¡¡?Õˇˆ?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜ò@@Ä
˜@Ä
˜∑*˜!?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜ò@Ä¿
˜Ä¿
˜˜*
7!?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜ò@¿

˜¿

˜
7*
w!?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜?ÕˇÄ˜ÕˇÄ˜¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡

Ò«
é»    ˛àÇP»    ˛òÇ\»

ÇB»

#t<B»
!D§»
qÉ»¡¡¡¡¡
¯@#†@˛
í˛@(›˛
ê@!@˛
˛@›˛âËŸ¿§i'Y∞`é∫-Ä[(Ë”ù™+fi˛ Y"Ñ¡‹µ(j¿)°TíVÄ≠(Ql*-Tfi 
K'·
 ï¶GO@I#•$îÅ)HêÎK¬I‰fiò@

@
˜

@
˜
w*
∑! éD!'+a\Äzb-∂©ÅÛX.P‹jàfi ãCép≈≤NìÑRA˜$IRl°Àg$Lxfi˛
@˝
˝¸ ÷˛
@˝
˝¸ ÷˛
Ä˝
À¡¡9
éC
@@
¿ÄËê˝Ä‡@
ć@:H˝@Ģ6˛D

ä@ÄÄ@Ä1¸@@Ä@@@Ä˝¯;˛5ƒıgG!L+[‚uÄÌ ÀJHÀ—l@-mdlåπ&¿[ÎC¢˘« [„eRíeË∂ ^≤;F^ã`˙;˛5•U    ®JQTUMEÜÅ4ïΩITí¥@V¶¨¥ïQS@çD•eQ+BPçEäÔR™IZ )´VMJ§ï†˙<8
©    'í·dòââtÅ%9%)í%$§@•"bí@âÖ)."JDêâéíJeíR I*R…ë)% ˙<8

*a÷ÇD˚” ÇM¢>R⁄˝µL#©    MØÛ§¡…K:ÛTΔ°…î∑~⁄¶“DÉì◊Ì™`˙<8âÙNõsN§íÑÈ#I)åë)"HIIE…¢Dëíàç≠"$ÑAíác$îë$"T¢“âI@˙Û@ı ˆÑÌÛ@ı ˆÑÌ
ÈÑÌ¡¡
˛@ÄF0 Ä@¿⁄˛§@¸à $·@@⁄˛§èˆ^ãa”í
êa\ÁTr#
Á
»®€
%òH§ï¢®§£©
T•EHït€
H∑â)%!·p˚Ò0‚ô.Oâᪧ€l·—Ì™`r@
"BX"≠h B¡¢H€HæëICß∫ú·ë√I∑6<ÁéF›€Ù˙˛@€Ù˙˛@€Ù˙˛@€¡¡¡¡¡¡¡¡¡¡¡¡¡¡˛ 
¿
Õ˛ Äb
Õ˛    bîàÄZ GïÖ≥Œ˛    gzîÄ≠]…*’Œ˛    íS8Å)IZròŒ
•†GRsD;Œ;8íåZ<$@œ˛
 ˛ ˛
 ˛ ˛
 ˛ ¡¡‡pŒ
 Œ
;Eê!x:≤>Kœ
ƒ ®"®êRET§œ
$\pGp$†îNâ$œ(u¿D@=0∂àΩHœ»Z8˚∫) ‹áHàœ˙…˙…ò@
@
Ä
˜
@
Ä
˜
∑*
˜!¡¡¡
‡‡¿¯Ä“˛ê
 @PÄ“
z¡± ˘6R/Ï∏¨”
lìA¿“ïBöVPëQP”
E¢B$îπ<í¢œbP”
'2¬ E5¢&ÛÉ£Ú†”ï§á»œ&fir$¢›"° ”ı Œı Œ¡¡¡˛
 ¬?‡Ä
ÅÄœ˛
 B@ÄB@œ˛
a ÑQe≈`D@œ˛
bóJ"rÑääŃ@œ˛
î¶\$ñxìÄ$@œ
™êF‹ï$Äœ>”dñÈ    
ÀŒ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜
˜*7!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜7*i!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜w*∑!
¡¡Ã3ˆÕ
ˆ Œ
ˆÃĘÕ
ˆÃĘ Œ
ˆÕ
ˆ Œ
ˆÃĘÕ
ˆ
˘ˇ‡ÍÛˇ‡˛Ä˜
 ˘ ÍÛ0
ˆ
˘ ÍÛ8
ˆ
 ˘ ÍÛ,
ˆ
˘"ÍÛ&˛Ä˜
˛˝!ÍÛ#
ˆ
˛˝ ÍÛ#˛Ä˜
 ˛˝ ÍÛ!Ä
ˆ
˛4˝ ÍÛ ¿
ˆ Ô˝
?‡ÎÛ `
ˆ|q˛Ä`ÎÛ 0Ę˜˛`Î
ÙD`
ˆÄ˛`Î
Ùà†Ę  ˛
˛`Î˙
º˝ 
ˆ!õˇÒˆP`Î˙
w˛ 
ˆ! åü`Î˙b"p˛ 
ˆ"
˛Üx`Î˙8˛ 
ÄĘ$
˛
Ã`Î
˝
‡DD\˛ ¿
ˆ!
˙0`Î
˝?ˇËàÿü˛?ˇ¿Ä˜
 ¯`ν
ˇˇ¯˘øġ‡
ˆ
¯`ν˛ˇ˚‡˛`
ˆ
 ¯`ν˛ˇ#ˇˇ˛ `
ˆ
¯`ν˛ˇᡡ¸˝`Ę
¯`Î
˛˝ˇflˇˇ˛˝
`
ˆ
˙H`΢ˇÄ˛`Ę
 ˚Ü8`β˘ˇ‡˛
`
ˆ
˚Ûˇ`β
ˇ˚˚ˇ¯`
ˆ"
 ˚Ú/`β
¯Û˛ˇÔˇˇ¸ `
ˆ%
˛¿p¯`ν
~˛ˇÁ¡ˇ˛`Ę%
˛;ú@`Î
˛
«˛ˇ·¸¿`
ˆ&
˛9Ë>fi`Î
˛
˜Ô˛ˇ    ·¯ˇ‡`Ę$ Ä?¨øÄD`ν
~?˛ˇ¯¯pfl¯`
ˆ%
ÿˇÒ‡`Ρ·˛ˇÒ¸`7¸`
ˆ- 
«˛ˇ¿`˚?˙ˇ˛˙ˇ‡√øˇÁÒ˛xgˇ `
ˆ.˛ˇÛΔ`˚ ˙˙ˇ¸Éˇ¯ˇpˇÄ`Ę,Ô˝ˇ`˚ ˙˙ˇˇÄˇ˛‡‡`
ˆ.ˇ˝fiüˇ`˚ ˙˙ˇˇ¯˛¸p?`Ę, ˇ˛˛`˚ ˙˙˝ˇÊ~
‡v¯`
ˆ/ˇ˛fl¸`˚ ˛
˛˙
¸ˇ¿Ê
»<¯¯`
ˆ0 ¸7˚ˇ`˚ ˛æ˛˙
˝ˇø‡¿x˛| `
ˆ1¿#ˇˇ˛`˚ ˛¯@˙
˝ˇ‡03IJ~`Ę1
˛!è¯˛`˚ ˘ƒp˙
˛ˇ¸`˛bġˇ`
ˆ/
˛>ê˛`˚ ˇè¸˙
˛ˇ‹@˚ˇˇÄ`Ę,
 ˛˛`˚ ˇœ˛˙
˛ˇ¿˘Ô¿`
ˆ&
¯`˚ ?˛ˇÄ˙
˛ˇÄ˘?œ–`
ˆ%
 ¯`˚ ?˛ˇ¿˙
˛ˇÄ¯‡`
ˆ&
¯`˚ ?˛ˇ˙
˛ˇ¿¯¿`Ę(
¯`˚ ?ˇˇÓ¯
ˇ˜ˇ˝
˛ˇ‡¯1Ä`
ˆ*˘à`˚ yÛˇ˛˛
ˇ˛ˇ˝
˛ˇ‡¯Ä`Ę-
 ¯`¸
  ˛ˇfi˛?
¿p˛
Dzˇfi˚x`
ˆ.
¯`¸
0!˛ˇépÅfl˚¿p˛
¬˛ˇ¸`
ˆò@@Ä
˜@Ä
˜∑*˜!
1  ˙
c¸ˇ¯!ˇˇÊép?¡fl˚‡p˝ˇb˝˛ˇÄ
¿8 `
ˆ1
¯b¸!ˇ¸‡x·flˆppIJ2?˛ˇÄˇ‡
Ä``Ę2@˙
b¸DF!ˇ¯ ÒflÙ0pƒ˛DZ?p¸¿Éć`
ˆ5
˝

@˛b¸àã!ˇ‡˛ÒflÙ?p˝à䲡?√ˇÄ‡`Ę4
 ˝
¿˛b¸!ˇ˝·flˆpIJ¸
ˇÄáˇÄ`
ˆ5
˝
˛c¸!ˇˇ·fl„pë˛2
‡
ˇ‚?ˇ˛˛`
ˆ4  2.c¸ˇ¯ ˇˇ0
Åflc√p˝ˇb˝£ˇˆˇ¯ `
ˆ5
˛ˇ·ˇ˛`¸0 ¸¸=¯Å¿√p˛

¬¸ˇˇ˛ˇÄ‡`Ę6@ˇ˝ˇ¿`¸  x~ø~
¡¯√p˛
DzOˇˇ?ˇ¿`
ˆ4˛ˇ`˚ ˇø|
√úˇp˝
˛
à˝ˇ?˛`Ę1 ˛ˇ¯`˚ ˇ„
«ˇp˝˚ˇˇ˛dÅ˛
`
ˆ3˛ˇ˛`˚ 
?ˇˇ
œ˛p˝˝ˇˇ˛nüÄ`
ˆ2  
Áˇˇ˝ˇ`˚ ?Ô‡
œ˛p˝˝
"˝ˇ
Í˛ `
ˆ1>ˇflü¿`˚ ?„¿
¿p˝˚?ˇÔ˙¿˝`Ę3@ˇˇÛflè‡`˚ ˇÉÄ
˛ˇ˝
˛D_ˇ‡Ä:¿˝
`
ˆ3?ˇˇ„fi
`˚ î
˛ˇ˝
˝àøˇ .¿˝`Ę- ?ˇ¸Òï`˚ ˚
˛ˇ˝˚ˇÄ}Ä˝
`
ˆ*?ˇúã¸`˚ ˙˙¸ˇˇ˝`
ˆ*  ?ˇ
˛`˚ ˙˙¸ˇ¸˛˝ `
ˆ)?¸˝˛`˚ ˙˙¸‡
¸¸`Ę(@?˛˝`˚ ˙˙
¸t¯¸
`
ˆ&?ˇ‡
Ä`˚?˙ˇ˛˙
¯¸`Ę ?ˇ˛0`Θ‡¸
`
ˆÅáøp`Î

Û`
ˆ  /˜˛¿`Î
Û" `
ˆ
˛ˇ¸`ÎÒ`Ę@Oˇ¸~`˚ÄıÒ
`
ˆ 
˛èˇ˝‡`˚ÄıÒ`Ę 
 ˛˝¸˛`˚§˛ŒnˆÒ
`
ˆ 
˛¸x˛`˚•çÊôˆÒ
`
ˆ   ‡`˚§m&ôˆÒ
`
ˆ.
˛ ˛`˚ùƒ‚iˆ¡ŒÉ?¿Δĸ`Ę!@˙
`ÎÃ√1ÉÊ¿¿`
ˆ 
¯`Îx√1ÉÊ`¿`Ę
 ¯`Îx√1Éˆ¿`
ˆ
¯`ο0√1É¿÷¸`
ˆ!  ˙
`ÎxÉ?fi¿`
ˆ 
¯`Îx1ÉŒ`¿`Ę
¯D`ÎÃ1ÉŒ¿¿`
ˆ 
¯`ηé¯1ɇΔIJ`Ę
 ¯`ÎÒ
`
ˆ
¯`ÎÒ
`
ˆ
 ¯ˇ‡ÎÒ
`
ˆ
¯ˇ‡ÎÒ`ĘflÒ
`
ˆflÒ`Ę ‡˛‡˛¸
`
ˆ|DÊ˛`¯
`
ˆ  @åÊ˛|≥<ˆÃ˚Ä`
ˆ"D¸«flÁ˛fê≥FˆÃÿ`Ę!}ìÏ$åºÁ˛gò1≥ΔÃÿ`
ˆ"Ds$å†Á˛g¯31≥~ΔÃÿ`Ę! E“ÓÑúÁ˛gÄ?1≥fΔÃÿ`
ˆfl˛fò!≥fΔÃÿ`
ˆ ‡˛faüü>Δ|ÿ`
ˆfl˙

Ä˙`Ęí
‰˙

Ä˙
`
ˆí
‰Ò`Ę ™m8‰Ò
`
ˆ¨ôH‰Ò
`
ˆ lôH‰Ò
`
ˆDi8‰Ò`ĘflÒ
`
ˆflÒ`Ęò@Ä¿
˜Ä¿
˜˜*
7!
 ‡Ò
`
ˆflÒ
`
ˆ ‡¸˝¸
`
ˆfl¸˝¸`Ęfl˛

˛ ˛
`
ˆfl_xœÔ¿Y˝˝‡`Ę ‡ˇˇ¯Ôˇ¿]ˇˇ‡`
ˆfl@ÄÅ`
ˆ ‡¸˝¸
`
ˆflüª∏˜˜v~˛Ë`Ęflfiª¸◊o˙Ë`
ˆflÇ @@`Ę ‡¸˝¸
`
ˆfl˜¸˛ˇû_flÛ¿`
ˆ ‡ˆ˛¯˛flfl€˚‡`
ˆfl P@


A`Ęfl˛

˛ ˛
`
ˆflÛ{ÓfiO}Ç[…ÔÄ`Ę ‡˚˚˛ˇoÇ_ÌÔ`
ˆfl˛@

`
ˆ ‡¸˝¸
`
ˆflÎœx}`oØ<`ĘflÎÔl˝`غ`
ˆfl
@`Ę ‡¸˝¸
`
ˆflS›@Í{®}Ou`
ˆ ‡€˝@˚®oı`
ˆflH
     A `Ęfl¸˝¸
`
ˆflˇ~‡flˇ¿{ˇ¿`Ę ‡ˇ~‡ˇˇ¿ˇ¿`
ˆflà   Ä`
ˆ ‡¸˝¸
`
ˆflÓ¯]ˇkø‡`Ęfl˙¸ˇÄÔ`
ˆfl @

`Ę ‡¸˝¸
`
ˆfl¸˝¸
`
ˆ ‡¸˝¸
`
ˆfl¸˝¸`Ęfl¸˝¸
`
ˆfl¸˝¸`Ę ‡¸˝¸
`
ˆfl¸˝¸
`
ˆ ‡¸˝¸
`
ˆflÒ`ĘflÒ
`
ˆflÒ`Ę ‡Ò
`
ˆflÒ
`
ˆ ‡Ò
`
ˆflÒ`ĘflÒ
`
ˆflÒ`Ę ‡Ò
`
ˆflÒ
`
ˆ ‡Ò
`
ˆflÒˇ‡Ä˜fl
Òˇ
‡
ˆÃĘ Œ
ˆÕ
ˆ Œ
ˆfi
ÚĘò@¿

˜¿

˜
7*
w!
fi(¸˜
ˆfi(ÚmñÉòˇ`˜Ä˜ fl92˘ïBe迯
ˆfiE2ôïBdl@¯
ˆ flDÓyuCô«¿¯
ˆ› ÙĘ› ı
ˆÃĘ Œ
ˆÕ
ˆ Œ
ˆÃĘÕ
ˆÃĘ Œ
ˆÕ
ˆ Œ
ˆÃĘÕ
ˆÃĘÃ3ˆÕUˆ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡

Ò«
é»    ˛àÇP»    ˛òÇ\»

ÇB»

#t<B»
!D§»
qÉ»¡¡¡¡¡
¯@#†@˛
í˛@(›˛
ê@!@˛
˛@›˛âËŸ¿§i'Y∞`é∫-Ä[(Ë”ù™+fi˛ Y"Ñ¡‹µ(j¿)°TíVÄ≠(Ql*-Tfi 
K'·
 ï¶GO@I#•$îÅ)HêÎK¬I‰fiò@

@
˜

@
˜
w*
∑!
 éD!'+a\Äzb-∂©ÅÛX.P‹jàfi ãCép≈≤NìÑRA˜$IRl°Àg$Lxfi˛
@˝
˝¸ ÷˛
@˝
˝¸ ÷˛
Ä˝
À¡¡9
éC
@@
¿ÄËê˝Ä‡@
ć@:H˝@Ģ6˛D

ä@ÄÄ@Ä1¸@@Ä@@@Ä˝¯;˛5ƒıgG!L+[‚uÄÌ ÀJHÀ—l@-mdlåπ&¿[ÎC¢˘« [„eRíeË∂ ^≤;F^ã`˙;˛5•U    ®JQTUMEÜÅ4ïΩITí¥@V¶¨¥ïQS@çD•eQ+BPçEäÔR™IZ )´VMJ§ï†˙<8
©    'í·dòââtÅ%9%)í%$§@•"bí@âÖ)."JDêâéíJeíR I*R…ë)% ˙<8

*a÷ÇD˚” ÇM¢>R⁄˝µL#©    MØÛ§¡…K:ÛTΔ°…î∑~⁄¶“DÉì◊Ì™`˙<8âÙNõsN§íÑÈ#I)åë)"HIIE…¢Dëíàç≠"$ÑAíác$îë$"T¢“âI@˙Û@ı ˆÑÌÛ@ı ˆÑÌ
ÈÑÌ¡¡
˛@ÄF0 Ä@¿⁄˛§@¸à $·@@⁄˛§èˆ^ãa”í
êa\ÁTr#
Á
»®€
%òH§ï¢®§£©
T•EHït€
H∑â)%!·p˚Ò0‚ô.Oâᪧ€l·—Ì™`r@
"BX"≠h B¡¢H€HæëICß∫ú·ë√I∑6<ÁéF›€Ù˙˛@€Ù˙˛@€Ù˙˛@€¡¡¡¡¡¡¡¡¡¡¡¡¡¡˛ 
¿
Õ˛ Äb
Õ˛    bîàÄZ GïÖ≥Œ˛    gzîÄ≠]…*’Œ˛    íS8Å)IZròŒ
•†GRsD;Œ;8íåZ<$@œ˛
 ˛ ˛
 ˛ ˛
 ˛ ¡¡‡pŒ
 Œ
;Eê!x:≤>Kœ
ƒ ®"®êRET§œ
$\pGp$†îNâ$œ(u¿D@=0∂àΩHœ»Z8˚∫) ‹áHàœ˙…˙…ò@
@
Ä
˜
@
Ä
˜
∑*
˜!
¡¡¡
‡‡¿¯Ä“˛ê
 @PÄ“
z¡± ˘6R/Ï∏¨”
lìA¿“ïBöVPëQP”
E¢B$îπ<í¢œbP”
'2¬ E5¢&ÛÉ£Ú†”ï§á»œ&fir$¢›"° ”ı Œı Œ¡¡¡˛
 ¬?‡Ä
ÅÄœ˛
 B@ÄB@œ˛
a ÑQe≈`D@œ˛
bóJ"rÑääŃ@œ˛
î¶\$ñxìÄ$@œ
™êF‹ï$Äœ>”dñÈ    
ÀŒ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜
˜*7!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜7*i!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜i*©!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜©*È!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜È*)!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜)*i!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜i*©!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜©*È!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜È*)!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜)*[!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜i*©!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜©*È!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜È*)!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜)*i!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜i*©!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜©*È!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜È*)!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜)*[!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡


Íl¿
¯4
Èj
Íkò@@
˜@
˜
Ík*b¡¡?÷ˇ¸Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Óò@@Ä
˜@Ä
˜*kjb?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Óò@Ä¿
˜Ä¿
˜jk™b?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Óò@¿

˜¿

˜™kÍb?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó?÷ˇ˛Ó÷ˇ˛Ó¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡    ¯„Ä√«    DA
$«    LA(«    äA2«    ë∫:=«    
Ç"Q«    
∏á¡é«¡¡¡¡¡¡¡ ¸
É 
`
$D˛tàfi H
†˛ ˛
$D˛ Äfi"DÙY
,∑lÈÿµëá/)’uÇÂïÖ•$e»∂p‡"e,¢ÇµI5!YiZíäRPU&ÖF™fi§™âZć"â%ßĶJ%"JJR§îê¶DâÑÚî…Rp‡"
«D    Ø”L¬Œõ‰5ñˆ´eä≈ƒ)mö¶‡"
â≈√áJíI√jí•"§†“Iâ<ΔHï$‡‡ ˚ ˆ

€ ˚ ˆ

€
¿˚
¿ˆ

€ò@

@
˜

@
˜Ík*b¡¡¡¡9«#É  ‡@tà˝@    p ¿Ä
p $IJ @¯7"
≈ @@ ÄÄ˝  @
   @˝˜;7b∫É≥ß ¶)≠Ú:¿vÂe•$e…6 ∂≤6L]¿;{!—|ìcê;r≤©J2Ù[[Y#.I∞˘;7SJÑ‘*P™R¶•C@öJãfi§™äö +SVZT©+@M$R≤®©°(M%Ew™U$≠©´-%TT–˘;7èîÑ쓇≤îD…:@íúíî…í JRR“°2J@IDîóI"HINI%4âI)%))iHò§ê˘;7Ü    0ˆÅ"ıÈÍ
¡&—)mù&‘ÑɶÌ˚T¿ìh•ùy“cPìhèJ^ømSÍBA”k¸È0˘;7
≈⁄'[qߢIDtë§èΔHï$$§¢‰ëR$à“HF÷ë"B “Gä1îJHíRQrD®ë ˘Ù 
ıˆBÏÙ 
ıˆBÏÒ

ÈBÏ¡¡¡¡ˇ @1Ä`Ç
ŸR ˝J@ìÑ
ŸRã˚.E∞È…JBªÉ™9
†å+úD†€ìî$TJ—
T;áT™Rć!u ´–€§≥ƒòíê∏
ÇcÅLóÄA>&%‹ê€
6‡Ë¸’09 îÑ∞ÅV¥¿ÅK- €
§∑H®â!”›c'!§€É`Ûú2:6Ó¿€ı@˚@
⁄ı@˚@
⁄ı˘@
⁄¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡‡

¿Õ@1
ÄÕ1JH@-e#ä¿∂`Œ3ΩT@VÆÂ
†ŒI)∏@î§Æ9
ÕäR‡#©    ;"'`Œ
ùåúIF.#$àŒ˛@Ã˛@Ã˛…¡¡¡¡
8˛
†ÄŒà

ÄÄŒùƒ»à/É´G≈`œ‚…TT$™äÄœò@
@
Ä
˜
@
Ä
˜*kjbíZ8#∏í    E—Äœ
r‡" £iïŒ
‰Y}›‚»È    Œ˚»˚»¡¡¡¡¡    
 ˛ —H    ê 
˛  —ä=`Äf«+rÿ(ø≤Ú∞“∂I†‡cJTÖh    9BE%@“¢—!íR‰yH
K<II@“ìôa÷àònèjÄ“
 “CÁ<õx‰ëKtäDÄ“¡¡¡¡¡¡¡a‡@00Œ!    @@HHŒ0ÂB    Hø≤‰∞àŒ1K•YBEJ@8àŒJS.ã<Ií@àŒä’H#Œè‘ÄDêŒ
üiá2ãtäàÑ9`Œ˜Ã˜Ã¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜jk™b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜™k‹b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜
Ík*b
¡¡’30Ó’Ó ÷Ó’Ó’Ó’Ó ÷Ó’Ó ÷Ó’Ó’Ó’Ó ËÛˇÄÓÁÙ
¿Ó ËÙ
@ÓÁÙ
`ÓÁÙ
0ÓÁÙ
Ó ËÙ
Ó
˘ˇÄÚÙ
Ó
 ˘¿ÚÙ
Ó
˘¿ÚÙ
Ó
˘¿Ú˘
@˛

ÄÓ
˛

P˛¿Ú˘
å@˛
¿Ó
 ˛
˛¿Ú˘
ç¿˛
`Ó 
˛
ì˛¿Ú˙    π˛
0Ó
 
!Ä¿Ú˙"#˛
Ó
‡¿Ú˙

Ä
Ó"

ˇ¸¿Ú¸
ÄtDD‡
Ó"˛ˇ¸¿Ú¸>àà
Ó" ˝ˇ¿Ú˝ˇˇÄÕ¯
ˇˇÓ"˝ˇÄ¿Ú˝ˇˇÒfl˛˛ˇÓ"
 ˇˇÔ‡¿Ú˝?ˇˇÚ'ˇˇ˝Ó"
˜ˇˇ˜˜¿Ú˝˛ˇ¯ˇˇ¿˛Ó$
fioˇ˜≥¸¿Ú˛˛ˇ˛ˇˇ‡˛Ó#?ˇˇ¸˜Ò˛ˇ˚ˇÄı˛˙ˇ¯˛Ó!     ˇˇ¯ÛÄ?˛ˇÙ˛˙ˇ˛˛Ó"    ˇ˛hsÄˇè˛ˇÄı˛˘ˇÄÓ$ ˇé#¿ŒÄı˛Ôfl˚ˇ¿Ó'ˇ˛?ÓˇflÄı˛„˛ˇ?oˇÓ'¸˝Óˇ±Ĉ
˛
¸?˛ˇ?Á¸Ó'˛˝Œˇ†ÉĈ
˛?˛ˇá√˛Ó' ?ˇ¿0
Œˇ†˚øˆˇ
˛˛
˛˝ˇ«ÉΔˇÄÓ'?ˇ¸
`ˇ±˚±ˆ
˛

„˝ˇ«√Åˇ¿Ó( ?¸?ʼn¿¯¢ˆ"#à?¸˛ˇèÛ√øÓ'Ä√Ô¿˚†ı»ˇÄˇ¸?œ˚¿/¸Ó(o˚ˇ
¯ɧˆDEà
ˇˇˇ¯?«ãÄ'˛Ó(øˇˇÉ‡√®ˆàã˛ˇˇáġÓ( ˇˇèÄ„˚øˆˇ˛˛ˇ‡?∑‡¿
ˇÄÓ'ˇˇº8s˚Ĉ˝ˇ˛∞
0œ¿Ó' #˛¯Ĉ˝ˇ˛¡‡„‡Ó'˛¯Äı
˛ˇ¸Ä–ÛÓ'¯>Äı
˛ˇ7

úÛ¯Ó'    ‡˛ˇÄıˇˇ˛‡˛ˇ¸Ó 
 ˙˛ˇÄıˇˇ˛`˚ˇ˛Ó
˙ˇ˛ˇÄıˇˇ˛˘ˇÓ
 ˘¿Úˇˇ¸¯¸Ó
˘¿Úˇˇ¸˜˛Ó
˘ˇ¿Ú
˛ˇ˜ûÓ
˘ˇ¿Ú
˛ˇ˜LÓ Ëˇˇ˛@˚¿xÓÁ
˛ˇ¸¸¿pÓò@@Ä
˜@Ä
˜*kjb
 Ë
˝ˇ‡˝˛‡ÓÁˇÁˇfl˛@
ÄÓÌ
ˇÛ
ˇÄ`Ó@ ÌˇÄˆÄÓ  'ÛspÓ¸˛¯Ó ,g¥»Ó¿˛˛?¯xÓ #d¥»Ó˝"'ˇˇˇ‡ÓÓ#ìHÓ˝üˇ∞ˇ¿ÓÁ˝EˇˇÒˇ¯`?ÓÁ˝
àø˛ˇ¯ ¸Ó ˸˛ˇ¯`Ó˙?˙ˇ¸˜˝
˛ˇÒt˛Ó! ˚ ˙˜˝
"'˛ˇÒı˛Ó˙ ˙˜¸ˇˇèˇ◊˝Ó˙ ˙˜˝Eˇˇ÷˝Ó˙ ˙˜˝àˇ˚
÷˝Ó ˚ ˙˜¸
ˇ˝Ä
|˝Ó˙ ˙˜˝
ˇ¸¸˝Ó ˚ ˙˜¸'ˇ¯¯˝Ó˙ ˙˜¸w‡˝Ó!˙ q.8Úq#˜¸4Δ‡˝Ó ˙ pœ8‚q§ú˜˚à¿˝Ó ˚ @» íAd꘯¸Ó˙ y(<íy#˜¯¸Ó ˚ ˙˜ÚÓ˙ ˙˜ÚÓ˙ ˙˜ÚÓ˙ t˜ÚÓ ˚ &C5]t˛ˇ¿˙ÚÓ'˙ %√Uıj˛ˇ¿˙~p¸ů~0<‡Ó) ˚ %d≥tͲˇ¿˙``Δ
å`0fÓ'˙ ˛
¿˙`¿Δ
å`0√Ó'˙ ˛ÁÅ¿˙`¿Δ
å`∞¿Ó%˙ ˚Ô¡Ä˚~
ÄΔÅå~∞¿‡Ó' ˚ ˚ÿa¿˚`¿¸
¯`¿Ó%˙ ˚ÿa¿˚`¿¿
å`p√Ó' ˚ ˚ÿ|œ˚ˇ˚``¿
å`pfÓ%˙ ˚|≈»˚
àp¿¡å0<Ó˙ ˚}áÖÃ˙D»ÚÓ˙ ˚¡Ö»˙à»ÚÓ ˚ ˚·Ö»˚

àÚÓ˙ ˚q˝œ˚ˇ
˚ÚÓ ˚ ˚9˝¿˚
ÚÓ$˙ ˚?¸
¿˚ˇ`˛0˝Ó ˙ ˚?¸
¿˚
˛c`˘Ó$˙ ˚
¿˙˛cÁÄ˝ôÁ∂g‹Ó& ˚ ˚ˇˇ˚¿˙˛c4Äçö7∂ffÓ$˙ ˚˛ˇ¿˙˛c<¿ëçòˆ6ffÓ& ˚ ˚˛ˇ¿˙˛c?¡ôçõˆ6ffÓ ˙ ˙˜˛c<
˘çõ66ffÓ ˙ ˙˜˛c4¡çõ66ffÓ ˙?˙ˇ˛˜˛c7É¸˘ˆ3ÊfÓ ˚˙ˇ˛˜˙˙ÓÁ˙˙Ó ËÚÓÁÚÓÁÚÓÁÚÓ ˚
àÚÓ˙ÄÛÚÓ ˚πᔿÛÚÓ˙õ√ÏÄÛÚÓ˙öÄÛÚÓ˙â¡Ú@ÛÚÓò@Ä¿
˜Ä¿
˜jk™b
 ËÚÓÁÚÓ ˜?˙ˇ¸˚ÚÓˆ ˙˚¸@˝˝Ó ˆ ˙˚@˛
@˛

˛Ó ˆ ˙˚∫˜˜‡@_~ÎÔÔÓ" ˜ ˙˚ø˜˜‡@ˇ˛˛ˇÓ ˆ ˙˚ÄÇ@Ó" ˜ 
˚¸@˝˝Ó$ˆ 
˚º˝fl¿@øª∞˜˜@Ó$ˆ!˚π˛?˛˚ˆ˝fl‡@˛ª¯◊@Ó$ˆ 
˚@
 @@Ó" ˜!ˇy»?Ë˚¸@˝˝Ó$ˆ 
˚øΩ˜¿@˜¸˛ˇûÓ) ˜!ˇ˘ø»?˜ˇ˜ˇ˛ˇøˇ`@ˆ˛¯˛flflÓ'ˆ 

˛ˇ˛

Ç@ P@
Ó'ˆ!ˇyˇË>Ì˛ˇ˛@˛
@˛

˛Ó'ˆ 

¿p˛ø€fl@Û{Ó˛o|Ó) ˜!˛˘‡?ŸflÛ¿p˛øˇfi@˚˚˛ˇxÓ'ˆ 

fl˜‡p˛@@@Ó% ˜!ˇ°ˇà>˝flˆpp¸@˝˝Ó'ˆ! 

flÙ0pˇ^k¿@Î}y‡Ó'ˆ!!ˇÒÓ?·flÙ?wˇˇ˛ø_k`@ν}‡Ó'ˆ 

flˆtààã@˛@ @Ó% ˜!Ÿ/Òfl„t
à¸@˝˝Ó'ˆ 

flc√u˛»∫flÊ@S›@Í{®Ó) ˜! 

¿√v""#àæˇÊ@€˝@˚®Ó'ˆ! 

¡¯√t Ç @H
    Ó#ˆ 

√úˇwˇˇ˛¸@˝˝Ó'ˆ! 

«ˇp˜˚˚@ˇ~flÓÓ& ˜ ˚
œ˛pø˚˚@ˇ~ˇÓÓ#ˆ ˙¿`˛A
@à Ó" ˜ ˚
˛ˇ˛¸@˝˝Ó"ˆ ˙˛ˇ‡˛◊w@@Ó¯]flÓ$ˆ ˚
ˇ˝ˇ˛ˇ◊‡@˙¸ˇ_ÄÓ ˆ ˙˚
@ @Ó ˜ ˙˚¸@˝˝Óˆ?˙ˇ˛˚¸@˝˝Ó ˜˙ˇ˛˚¸@˝˝ÓÁ¸@˝˝ÓÁ¸@˝˝ÓÁ¸@˝˝Ó ˸@˝˝ÓÁ¸@˝˝Ó ˜ÄĈ¸@˝˝Óˆ!
¯¸@˝˝Óˆ4ÛÏqüÊ˘ÚÓˆ{!òJqÙ˘ÚÓ ˜C!òJMÑ˘ÚÓˆ<ëhq∏Ù˘ÚÓ Û@˜ÚÓÚ@˜ÚÓÁÚÓÁÚÓ ËÚÓÁÚÓ ËÚÓÁÚÓÁÒˇ
ÓÁÒˇ
Ó ÷Ó’Ó ÷Ó’Óò@¿

˜¿

˜™kÍb
Ê ÛÓÊP¸ ˜Ó ÁS…µ:c¸¿¯ÓÊtÀÂ5    ñ>įÓ Áå e5    ë∞įÓÊãπ‰ıgįÓÂÄıÓÂÄıÓ ÷Ó’Ó ÷Ó’Ó’Ó’Ó ÷Ó’Ó ÷Ó’Ó’Ó’ÃÓ÷32Ó¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡    ¯„Ä√«    DA
$«    LA(«    äA2«    ë∫:=«    
Ç"Q«    
∏á¡é«¡¡¡¡¡¡¡ ¸
É 
`
$D˛tàfi H
†˛ ˛
$D˛ Äfi"DÙY
,∑lÈÿµëá/)’uÇÂïÖ•$e»∂p‡"e,¢ÇµI5!YiZíäRPU&ÖF™fi§™âZć"â%ßĶJ%"JJR§îê¶DâÑÚî…Rp‡"
«D    Ø”L¬Œõ‰5ñˆ´eä≈ƒ)mö¶‡"
â≈√áJíI√jí•"§†“Iâ<ΔHï$‡‡ ˚ ˆ

€ ˚ ˆ

€
¿˚
¿ˆ

€ò@

@
˜

@
˜Ík*b
¡¡¡¡9«#É  ‡@tà˝@    p ¿Ä
p $IJ @¯7"
≈ @@ ÄÄ˝  @
   @˝˜;7b∫É≥ß ¶)≠Ú:¿vÂe•$e…6 ∂≤6L]¿;{!—|ìcê;r≤©J2Ù[[Y#.I∞˘;7SJÑ‘*P™R¶•C@öJãfi§™äö +SVZT©+@M$R≤®©°(M%Ew™U$≠©´-%TT–˘;7èîÑ쓇≤îD…:@íúíî…í JRR“°2J@IDîóI"HINI%4âI)%))iHò§ê˘;7Ü    0ˆÅ"ıÈÍ
¡&—)mù&‘ÑɶÌ˚T¿ìh•ùy“cPìhèJ^ømSÍBA”k¸È0˘;7
≈⁄'[qߢIDtë§èΔHï$$§¢‰ëR$à“HF÷ë"B “Gä1îJHíRQrD®ë ˘Ù 
ıˆBÏÙ 
ıˆBÏÒ

ÈBÏ¡¡¡¡ˇ @1Ä`Ç
ŸR ˝J@ìÑ
ŸRã˚.E∞È…JBªÉ™9
†å+úD†€ìî$TJ—
T;áT™Rć!u ´–€§≥ƒòíê∏
ÇcÅLóÄA>&%‹ê€
6‡Ë¸’09 îÑ∞ÅV¥¿ÅK- €
§∑H®â!”›c'!§€É`Ûú2:6Ó¿€ı@˚@
⁄ı@˚@
⁄ı˘@
⁄¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡‡

¿Õ@1
ÄÕ1JH@-e#ä¿∂`Œ3ΩT@VÆÂ
†ŒI)∏@î§Æ9
ÕäR‡#©    ;"'`Œ
ùåúIF.#$àŒ˛@Ã˛@Ã˛…¡¡¡¡
8˛
†ÄŒà

ÄÄŒùƒ»à/É´G≈`œ‚…TT$™äÄœò@
@
Ä
˜
@
Ä
˜*kjb
íZ8#∏í    E—Äœ
r‡" £iïŒ
‰Y}›‚»È    Œ˚»˚»¡¡¡¡¡    
 ˛ —H    ê 
˛  —ä=`Äf«+rÿ(ø≤Ú∞“∂I†‡cJTÖh    9BE%@“¢—!íR‰yH
K<II@“ìôa÷àònèjÄ“
 “CÁ<õx‰ëKtäDÄ“¡¡¡¡¡¡¡a‡@00Œ!    @@HHŒ0ÂB    Hø≤‰∞àŒ1K•YBEJ@8àŒJS.ã<Ií@àŒä’H#Œè‘ÄDêŒ
üiá2ãtäàÑ9`Œ˜Ã˜Ã¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜jk™b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜™k‹b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜‹kb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜k\b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜\kúb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜úk‹b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜‹kb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜k\b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜\kúb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜úkŒb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜‹kb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜k\b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜\kúb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜úk‹b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜‹kb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜k\b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜\kúb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜úkŒb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ<í@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@ä.Introduction to Interapplication Communication4⁄ä˙(‡äSending and Responding to ç¿)qApple Events

, (‡    1-9
ˇˇˇˇˇˇˇˇ4^4|lòÄ2^A|rMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^A|r^A|r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
^6|@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^6|@^6|@˜˜˜˜˜˜˜˜˜˜˜˜˜˙ˇˇ
˙ˇ
˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜
4Å4
w?òÄ
Å6
w@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""Å6
w@Å6
w@$˜
˙ˇ˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛
¸ˇ˛¸ˇ˝˚ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛
˙ˇ˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˛¸ˇˇ
ˇ˛ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˜˜˜˜
˙ˇ
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛˜˛˛ˇ˝
ˇˇˇ˛
ˇˇˇ˛    ˇˇˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
˙ˇ˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˝˛ˇ˛
˛ˇ˛ˇˇ    ˇ¸
ˇ    ˇ¸
ˇ
˛ˇ˛ˇˇ˜˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähê(eä
Y@Ä°dONLNd
\êh)Wour application should save the new information in the edition whenever the user edits °dONLNdXiäu
(räUthe publisher and saves the document that contains the publisher—unless the user has °dONLNd≠väÇ
™*Bindicated that the information should be saved in the edition on r– °dONLNdÔv
™Ç
‹(
™equest only•†°dONLNd˙v
‹Ç)2. When the °dONLNd
Éäè
§(åä?user saves new information in an edition, the Edition Manager r(°dONLNd
DÉ
•è
·(å
•eplaces the pr˜Ä°dONLNd
RÉ
·è)<evious °dONLNd
Yêäú±(ôä    contents.°dONLNd
c¢äÆû*Whe°dONLNd
f¢üƨ)n al`°dONLNd
i¢¨ÆÕ)n editio+¿°dONLNd
q¢ŒÆ
)"n is updated,Ô@°dONLNd
~¢
Æ
⁄)9/ the Edition Manager informs your application. ˛Ä°dONLNd
≠¢
ڮ
‡)”
Yø°dONLNd
Æ¢
‡Æ
Ò)our °dONLNd
≤Øäª
W(∏ä-application should then update any subscriber °dONLNd
߯
Xª
b)Œs (/°dONLNd
‚Ø
bª
˜)
#unless the user has indicated that °dONLNdºä»
+(≈ä#updates should be incorporated on r~`°dONLNd(º
+»
c)°equest only).°dONLNd6Œä⁄≈(◊äFor example, q†°dONLNdCŒΔ⁄Ì)<suppose ∂ °dONLNdKŒÌ⁄
)'a useC‡°dONLNdPŒ
⁄
)r o,°dONLNdSŒ
⁄
 )pen… °dONLNdVŒ
 ⁄
$)
s °dONLNdWŒ
%⁄
@) a woró†°dONLNd]Œ
@⁄
S)d-prŒ`°dONLNdaŒ
S⁄
)(ocessing document called My Stocks that °dONLNdâ€äÁÔ(‰äaccesses information fr°dONLNd†€ÔÁ
˘)e<om an edition called Stock Report. The Stock Report edition °dONLNd‹ËäÙ
0(Òä$might be updated twice a day by an oA`°dONLNdË
1Ù
9)ßnl˚ °dONLNdË
9Ù
t)ine database. åÄ°dONLNdË
uÙ)<"As the information in the edition °dONLNd2ıä


8(˛ä%changes, the My Stocks document can r °dONLNdWı
8


Î)Æ)eceive automatic updates with the latest °dONLNdÄ
ä
¡(
äinformation.°dONLNdç
ä
 ê*
Y@Ä°dONLNdé
ê
 
)Uou can implement publish and subscribe capabilities in your application by using the °dONLNd„
!ä
-ç(
*ä
rE°dONLNd‰
!é
-∫)
outines prÄ°dONLNdÓ
!ª
-
£)-2ovided by the Edition Manager and supporting the rÛ†°dONLNd 
!
¢
-
ø)Áelated Ô°dONLNd'
!
ø
-)Apple events. The °dONLNd9
.ä
:
E(
7ä)chapter “Edition Manager” in this book pr°†°dONLNdb
.
E
:)ª)ovides sample code that shows how to add °dONLNdã
;ä
GΩ(
Däthese featur°dONLNdó
;æ
G
.)4es to your application. Thı‡°dONLNd±
;
.
G
°)pe chapter “Responding to Ω†°dONLNd 
;
°
G
‰)sApple Events” Ä°dONLNdÿ
;
Â
G)Din this °dONLNd‡
Hä
T¢(
Qäbook 
¿°dONLNdÂ
H£
T©)
dÄ°dONLNdÊ
H©
T
))escribes how to support the rh†°dONLNd
H
)
T
F)Äelated d°dONLNd

H
F
T
Ö)Apple events. 


[H
v4
\H
v


ÜH
é4
áH
é 
àH
à

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNd
sH
Ü
(
ÅHSending and Responding to §°dONLNd4
s

Ü
u)ÃApple EventsˇˇˇˇˇˇV˛)˙
1
°dONLNdB
óä
£ö(
†äAn :@°dONLNdE
óö
£
â)7Apple event is a high-level event that conforms to the 
 °dONLNd|
ó
â
£
‚)ÔApple Event Interpr†°dONLNdè
ó
‚
£
˚)Yocess °dONLNdï
§ä
∞Δ(
≠äMessaging Pr_Ä°dONLNd°
§Δ
∞˘)<otocol. The 8`°dONLNd≠
§˘
∞
|)3Apple Event Manager uses thE¿°dONLNd»
§
|
∞
â)Ée E´ °dONLNdÀ
§
â
∞
Î)vent Manager to send °dONLNd‡
§
Ï
∞    )cApple °dONLNdÊ
±ä
Ω
Î(
∫äMevents between applications on the same computer or between applications on rE°dONLNd3
±
Ï
Ω    (
∫
Ïemote °dONLNd9
æä
 Ω(
«äcomputers. ~†°dONLNdD
ææ
 ¿)4
 ˛†°dONLNdE
æ¿
 ¬)
 °dONLNdG
–ä
‹ˇ(
ŸäApplications typically use ˆ†°dONLNdb
–ˇ
‹
K)uApple events to r˚@°dONLNds
–
K
‹
·)L"equest services and information frn@°dONLNdï
–
‚
‹
Ú)óom °dONLNdò
݊
È°(
Êäother≈Ä°dONLNdù
›°
È£)
 EÄ°dONLNdû
ݤ
È˝)applications or to pr†Ä°dONLNd≥
›˝
È
ó)Y#ovide services and information in r0°dONLNd÷
›
ò
È
‰)õesponse to such r‡°dONLNdÁ
›
‰
È    )L    equests. °dONLNd
Íä
ˆ
j(
Ûä2For example, any application can use the Get Data Ñ °dONLNd"
Í
j
ˆ
±)‡Apple event to rK¿°dONLNd2
Í
≤
ˆ
¸)Hequest that your °dONLNdC
˜äÒ(äapplication locate and rC °dONLNd[
˜Ú
≥)h/eturn a particular set of data, such as a table;`°dONLNdä
˜
¥
«)¬. If y¸‡°dONLNdê
˜
«)our application °dONLNd†ä
(äsupports the Get Data event, io†°dONLNdæ

e)Ñt should be able to r»‡°dONLNd”
e
–)Wecognize the event and rgÄ°dONLNdÎ
—
˘)lespond b⁄Ä°dONLNdÛ
˘
)(y °dONLNdıäƒ(älocating the r{¿°dONLNdƒ
):equested data and r§@°dONLNd

¯)W4eturning a copy of the data to the application that °dONLNdJä*ç('ä
rE°dONLNdKé*√)equested it. à°dONLNdX√*≈)5
 °dONLNdZ0ä<
Å(9ä4Communication between two applications that support 쇰dONLNdé0
Å<
Ù)˜Apple events is initiated b=@°dONLNd©0
ı<)ty a 
°dONLNd≠=äIé(Fä
c@°dONLNdÆ=éI€)lient application,©¿°dONLNd¿=‹I
%)N which sends an ü‡°dONLNd–=
%I
l)IApple event to rgÄ°dONLNd‡=
mI)H%equest a service or information. For °dONLNd    JäV
+(Sä%example, a client application might rÛ‡°dONLNd    *J
+V
’)°'equest services such as printing specifiê °dONLNd    RJ
÷V
‚)´c fiç °dONLNd    VJ
„V
Û)les, °dONLNd    [Wäc
)(`ä&checking the spelling of a list of wor«†°dONLNd    ÅW
)c
°)üds, or performing a numeri‡°dONLNd    õW
°c
¨)xc cQ`°dONLNd    ûW
≠c)alculation; or it might °dONLNd    ∂däpç(mä
rE°dONLNd    ∑dép
E)(equest information, such as one customer@`°dONLNd    fld
Fp
d)∏’s addr¡ °dONLNd    Êd
dp
Í)ess or a list of names and addrú°dONLNd
d
Íp)Ü    esses of °dONLNd
qä}
Z(zä0all customers living in Ohio. The application prH¿°dONLNd
>q
[}
—)—oviding the service or the r€ °dONLNd
Zq
—}
˚)v    equested °dONLNd
c~ääÏ(áäinformation is called a
 °dONLNd
z~Ìä
C)c server application.Ô‡°dONLNd
é~
Cä
Ú)V) The client and server applications can rç`°dONLNd
∑~
Ûä)∞eside °dONLNd
Ωãäó
#(îä"on the same local computer or on rΰdONLNd
flã
#ó
”)ô%emote computers connected to a networ«@°dONLNdã
‘ó
fi)±k. ˇMP@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@l.Introduction to Interapplication Communication4⁄*˙
¯

(‡*1-10    )BSending and Responding to ç¿)qApple Events4^*¿
¯
°dONLNd\lhÑ(elFigurR¿°dONLNd\Ñhò)e 1-5@°dONLNd
\òhÕ) shows the r*Ä°dONLNd\Œh
ê)6-elationships among a client application, the @°dONLNdC\
êh
Ò)¬Apple Event ManagerÛ¿°dONLNdV\
h
ı)`, °dONLNdXilu
S(rl6and a server application. The client application uses } °dONLNdéi
Su
ª)ÁApple Event Manager rq°dONLNd£i
ªu
È)houtines to °dONLNdÆvlÇt(lcrµ@°dONLNd∞vtÇ√)eate and send the Í¿°dONLNd¬v√Ç
â)O-Apple event, and the server application uses °dONLNdÔv
äÇ
Ó)«Apple Event Manager °dONLNd
Élèo(ål
rE°dONLNd
Épèº)outines to interpr˚¿°dONLNd
ɺè÷)Let the Ü¿°dONLNd
É◊è
')Apple event and rɆ°dONLNd
.É
'è
^)Pespond appr8@°dONLNd
9É
_è
Ü)8    opriatelyÚ†°dONLNd
BÉ
Öè
Ú)&. If the client application °dONLNd
^êlú|(ôlso rwÄ°dONLNd
bê|ú¸)equests, the server applicatioÜ°dONLNd
Äê¸ú
j)Än adds information to a rÑ °dONLNd
ôê
jú
)neply È°dONLNd
ûê
ú
≤)
Apple evenÒ`°dONLNd
®ê
≤ú
€)3t that the °dONLNd
≥ùl©‘(¶lApple Event Manager rs‡°dONLNd
»ù‘©
_)h"eturns to the client application. 

À*‹
¯4Ã*‹
¯"Ã*]

ˇ·ˇ‚7^
    °dONLNd
ΡlÃñ(…l
Figure 1-5°dONLNd
ˆ¡ÆÃ
)BSending and responding to  °dONLNd¡
Ã
õ)n!Apple events with the aid of the p°dONLNd1¡
õÃ
Ò)Apple Event Manager
°dONLNdF
õl
ßÇ(
§lIf an •`°dONLNdL
õÇ
ß
)!Apple event is one of the standar~@°dONLNdm
õ

ß
L)íd events defi`°dONLNdz
õ
M
ß
{)9ned in the ‰@°dONLNdÖ
õ
{
ß
◊).Apple Event Registry: °dONLNdõ
®l
¥®(
±lStandard SuiteS@°dONLNd©
®©
¥Ø)=s,∂‡°dONLNd´
®Ø
¥
=)" the client application can constr@@°dONLNdÕ
®
>
¥
Ô)è)uct the event and the server application °dONLNdˆ
µl
¡ú(
ælcan interpr¡ °dONLNd

µú
¡Δ)0et it accor‡°dONLNd
µ«
¡
)+ding to the standaræ@°dONLNd
µ

¡
3)Sd defiL °dONLNd%
µ
4
¡
ó)nition for that event. T冰dONLNd=
µ
ñ
¡
∂)bo ensur&@°dONLNdD
µ
∑
¡
È)!e that your °dONLNdP
¬l
ε(
Àlapplication can r=Ä°dONLNda
¶
Œ‰)J
espond to `°dONLNdk
¬‰
Œ
Ú).<Apple events sent by other applications, you should support °dONLNdß
œl
€ù(
ÿlthe standar‡°dONLNd≤
Ϟ
€¶)2d L@°dONLNd¥
Ϧ
€ˇ)Apple events that arÔ °dONLNd»
œˇ
€
)Ye appr°dONLNdŒ
œ

€
ò)opriate for your application.


*
¯4
*
¯ l
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdÏ
Úl
ß(
˝l    Standard )>°dONLNdı
Úß
˜);Apple Eventsˇˇˇˇˇˇ€r(
˝

1
°dONLNdlë(lThe currÍ¿°dONLNdëŒ)%ent edition of P‡°dONLNdœ
k)>%Apple Event Registry: Standard Suites>†°dONLNd?
l
)ù defi∞¿°dONLNdD

¬)nes the standaró†°dONLNdS
¬
 )Cd 
3`°dONLNdU
À
Ë)    suites W`°dONLNd\
Ë
Û)of °dONLNd_l “(lApple events, which arü °dONLNdu“ ‚)fe gr<‡°dONLNdy„ 

)    oups of rá°dONLNdÇ

 
c)'elated events that arÜ °dONLNdó
c 
Ô)Ye usually implemented together•`°dONLNdµ
Ô 
Ù)å. °dONLNd∑!l-(*lThe ]`°dONLNdª!-Ï)Apple Event Registrar m"°dONLNd“!Ì-
)naintain◊‡°dONLNdŸ!
-
)s t◊@°dONLNd‹!
-
")
he Ú@°dONLNdfl!
"-
æ)%Apple Event Registry: Standard Suites‡°dONLNd!
ø-
Ã)ù an1`°dONLNd!
Õ-
Ô)d other °dONLNd.l:n(7l
ih`°dONLNd.o:ø)nformation about Ç°dONLNd!.ø:œ)Pthe fl`°dONLNd%.œ:
>)ongoing development of ≈`°dONLNd<.
>:
ê)oApple event suites†°dONLNdN.
ë:
ñ)S. °dONLNdQ@lL†(IlThe standarÌ@°dONLNd\@†L
()4 d suites include the following: 
@°dONLNd|@
)L
+)â
 ,Zapf Dingbats°dONLNd~Vl]q(\l
n
°dONLNdÄSx_§)
The Requir;‡°dONLNdäS•_√)-ed suite°dONLNdíSƒ_
) consists of the four 5`°dONLNd®S
_
√)X&Apple events that the Finder sends to °dONLNdŒ_xk˜(hxapplications. These events arÖÄ°dONLNdÎ_˜k
)e Open i¿°dONLNdÚ_
k
`)"Application, Op≈‡°dONLNd
_
`k
ü)Gen Documentsy`°dONLNd_
†k
´)@, PÉ°dONLNd_
´k
ı)rint Documents, °dONLNd kxw°(tx    and Quit Ä°dONLNd)k¢w
8)*"Application. The Finder uses the rd`°dONLNdKk
8w
O)ñequir{†°dONLNdPk
Ow
)$ed events as part of the mechanisms °dONLNdtwxÉz(Äx
ih`°dONLNduw{Éé)n Syà†°dONLNdywéÉö)ste—†°dONLNd|wöɱ)m 7 a•†°dONLNdÅw≤É
«)?nd later versions for launching and terminating applications. T;@°dONLNd¿w
«É
Ù(Ä
«
o support °dONLNd Éxè°(åx    System 7,k‡°dONLNd”É¢è
B)*$ your application must support the r‡°dONLNd˜É
Cè
Z)°equir( °dONLNd¸É
Zè
g)ed / °dONLNdˇÉ
gè
Ë)Apple events as described in °dONLNdèxõÙ(òxthe chapter “Responding to [Ä°dONLNd7èÙõ
p)|Apple Events” in this book. ™°dONLNdSè
põ
r)|
 

€l
Ñ
¯4⁄j€kò@@
ˆ@
ˆ€k
a¡¡?Áˇ¯›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Óˇ˛˝ˇ¸›?Óˇ˛˝ˇ¸›?˛ˇ˛ˆˇ
˛˛ˇ¸›?˛ˇˇˇ¯ˆˇ
˛˛ˇ¸›?˛ˇĈˇ˛ ġ¸›?˛ˇĈˇ˛ @ˇ¸›?˛ˇüˇ»ˆˇ˛!Á¯ˇ¸›?˛ˇíàHˆˇ˛¯ˇ¸›?˛ˇüˇ»ˆˇ˛¿Äˇ¸›?˛ˇíàHˆˇ˛Ç`ˇ¸›?˛ˇüˇ»ˆˇ˛
êˇ¸›?˛ˇìˈˇ˛ˇ¸›?˛ˇúˆˇ˛
‰ˇ¸›?˛ˇò ˆˇ˛!Rˇ¸›?˛ˇêˆˇ˛"©ˇ¸›?˛ˇ†Äáˆˇ˛DQˇ¸›?˛ˇ¡Gˆˇ˛ Ñ)ˇ¸›?˛ˇÇ5'ˆˇ˛ à4ˇ¸›?˛ˇÒ Jóˆˇ˛!"ˇ¸›?˛ˇÒ@Õˆˇ˛!Qˇ¸›?˛ˇÚAJóˆˇ˛"hġ¸›?˛ˇÚÉ…ˆˇ˛‘@ˇ¸›?˛ˇÚÇ    'ˆˇ˛ ™ ˇ¸›?˛ˇÚÁˆˇ˛ ïˇ¸›?˛ˇÚ!¯ˆˇ˛ äàˇ¸›?˛ˇÒ!ˆˇ˛ ÖDˇ¸›?˛ˇÒ"ˆˇ˛
 Ƕˇ¸›?˛ˇLjˇ˛êAYˇ¸›?˛ˇbˆˇ˛P@πˇ¸›ò@@Ä
ˆ@Ä
ˆ
k
[a?˛ˇ"ˆˇ˛0 aˇ¸›?˛ˇˆˇ˛#ˇ¸›?˛ˇ    ˆˇ˛ ˇ¸›?˛ˇˆˇ˛@ˇ¸›?˛ˇˆˇ˛Äˇ¸›?˛ˇ
‡ˆˇ˛˝ˇ¸›?˛ˇ˛ˆˇ˛˝ˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›ò@Ä¿
ˆÄ¿
ˆ
[k
õa?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›?Áˇ¸›Áˇ¸›¡¡¡¡¡¡¡¡¡¡¡¡¡¡

Ò«»
àÇ    »
òÇ0»

ÇP»

#t—¯»
!f »
qòp»¡¡¡ò@¿

ˆ¿

ˆ
õk
€a¡¡0
¯
Ä
†˝–ÄÄ @H`ê@
¿|`Ô0ê@Ä
˝@Ä
˛ @H ê@Ä$†Ô40âËŸ≥≠ûgùDŸ÷œ9
Ö) ]-˜WXÎ ®·9÷@¬îê#•æ¬ÿæVÚ40 Y"Ñ

 ’&§)™    c™jìRÅéıP•V®RhMQIBêö†«z®8™‘Eid®Ú40
K'·\ôD§I2ù2L¢R$ÇD¶·…‰«
dHâ‚RDë¡"SpA<òIJe»Ú40éD—;iòzvTù¥Ã5IKÅ
â·
∂XÀÉ⁄≈!ó$•¿EQ<$OõŸÚ40ãCé-…8R[˘àñ‰ú"Ê2p‰yN$êírìb!$Ês8¯è(4Íí∏Ú#@˙D˛˛"@ˆ  ˙DÒ#@˙D˛˛"@ˆ† ˙DÒ#Ä˙8˛˛@ˆ@ ˙8Ò¡¡8
éC
@@
¿ÄËê˝Ä‡@
ć@:H˝@į6D

ä@ÄÄ@Ä1¸@@Ä@@@Ä˝˜;7ƒıgG!L+[‚uÄÌ ÀJHÀ—l@-mdlåπ&¿[ÎC¢˘« [„eRíeË∂ ^≤;F^ã`˘;7•U    ®JQTUMEÜÅ4ïΩITí¥@V¶¨¥ïQS@çD•eQ+BPçEäÔR™IZ )´VMJ§ï†˘;7
©    'í·dòââtÅ%9%)í%$§@•"bí@âÖ)."JDêâéíJeíR I*R…ë)% ˘;7

*a÷ÇD˚” ÇM¢>R⁄˝µL#©    MØÛ§¡…K:ÛTΔ°…î∑~⁄¶“DÉì◊Ì™`˘;7âÙNõsN§íÑÈ#I)åë)"HIIE…¢Dëíàç≠"$ÑAíác$îë$"T¢“âI@˘Ù@ı ˆÑÏÙ@ı ˆÑÏÒ
ÈÑÏ¡¡
˛@Ä`01Ä@¿Ÿ§@˝íêB@@Ÿ§èˆ^ãa”ííë\ÁTrÑ
Á
»®⁄
%òH§ï¢®é„©
T•    )Hït⁄
H∑â)%!·pE!0‚ô.    fiâᪧ⁄l·—Ì™`r@e"X"≠h    í¡¢H⁄HæëICß∫ò¡ë√I∑6ÁéF›⁄ı˙˛@⁄ı˙˛@⁄ı˙˛@⁄¡¡¡¡¡¡¡¡¡¡¡¡¡¡
 
¿
Ã
 Äb
ÃbîàÄZ GïÖ≥ÕgzîÄ≠]…*’ÕíS8Å)IZròÕ
•†GRsD;Õ;8íåZ<$@Œ ˛… ˛… ˛…¡¡‡pÕ
 Õò@

@
ˆ

@
ˆ
€ka
;Eê!x:≤>KŒ
ƒ ®"®êRET§Œ
$\pGp$†îNâ$Œ(u¿D@=0∂àΩHŒ»Z8˚∫) ‹áHàŒ˚»˚»¡¡¡
‡‡¿¯Ä—ê
 @PÄ—
z¡± ˘6R/Ï∏¨“
lìA¿“ïBöVPëQP“
E¢B$îπ<í¢œbP“
'2¬ E5¢&ÛÉ£Ú†“ï§á»œ&fir$¢›"° “ˆ Õˆ Õ¡¡¡ ¬?‡Ä
ÅÄŒ B@ÄB@Œa ÑQe≈`D@ŒbóJ"rÑääŃ@Œî¶\$ñxìÄ$@Œ
™êF‹ï$ÄŒ>”dñÈ    
ÀÕ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆk[a¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆ[kõa¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆõkÕa¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
ˆ@
ˆ€k
a
¡¡Ê30›Ê› ¬Ê›Ê›Ê› ¬Ê› ¬Ê›Ê›Ê› ˝
(Û

¿ÿ¸†
Ù
 ˝› ˝)ªÄı
Ü“ÿ⁄¸+ÂÛoã›¸™%Ù(相)‰Äı
«à› ¬Ê› ¬˚
P
Û
 ›˚
@Û@›˝ÓVg7ı‹ÍfÊp› ˛ôYÛLĘ
ÚöüiH€˝ôXìLĘ
2öâiH› ˛ÓWq4Ĉ¸Íw&H€¸àÚ
Ä˝›¸àÚ
Ä˝›Ê› ¬Ê› ¬Ê›Ê›
ϸ› ˝ˇˇ¯Ù◊¸ÄÙ
 Ä˝› ˝ÄÙ
 @ÿ¸üˇ»Ù!Á¯˛›¸íàHÙ¯˛›¸üˇ»Ù¿Ä› ˝íàHÙÇ`⁄¸üˇ»Ù
ê› ˝ìËÙ⁄¸úÙ
‰›¸ò Ù!R›¸êÙ"©› ˝†ÄÄıDQ⁄¸¡@ı Ñ)› ˝Ç5 ı à4⁄˝
 Jêı!"›˝
@Õı!Q›˝AJêı"hÄ› ˛É…ı‘@⁄˝Ç     ı ™ › ˛‡ı ï⁄˝!¯Ù äà›˝
!Û ÖD›˝
"Û
 Ƕ› ˝
ÇÚêAY⁄¸
bÚP@π›ò@@Ä
ˆ@Ä
ˆ
k
[a
 ˝
"Ú0 a⁄¸
Ú#›¸
    Ú ›¸
Ú
@˛› ˝
Ú
ÄŸ¸

‡Ì› ¬Ê›Ê›Ê› ¬Ê› ¬Ê›Ê›˚Ò@˛› ¸Ò‡Ÿ˚Ú

∞˛› ¸
3ÄÛ
Ÿ˚
`¿Û
˛›˚
Ù‡Û
˛›˚
ÄÛ
˛› ¸
ÄÛ
Ÿ˚
ÄÛ
˛› ˝˙ÄÛ
>Ÿ¸Ģ ˛
"˛›¸ĢÄ ˛
&˛›¸Ģ≥©˛
*˛› ˝Ģzi˛
"Ÿ¸    Ģ¬e˛
2˛› ˝
Ģª¶˛
"Ÿ¸į
˛
"˛›¸į
˛
&˛›¸ÄÛ
*˛› ˝Ģ ˛
"Ÿ     Ģ ˛
2˛› P
Ģw&˛
"ŸW:`ĢLØ˛
"˛›t¶Û˛ĢîˇˇÊ˛›å¶ÄĢ˜'˛
*˛› è:pįD˝
"Ÿ     įD˝
2˛›  
ÄÛ
"Ÿ¸Ĉ(Ä"˛›¸Ę!&˛›˝ ĢñÁKÄ*˛› igpĢ_íI"ŸıÙ†    ĢhíI2˛› Üц
ĢGëI"ŸttêĈ "˛›¸Ĉ &˛›¸ÄÛ
*˛› ˝Äı"Ÿ¸    Ĉ2˛› ˝
Ģè&éÄ"Ÿ¸Ģ”/«“Ä#¯˛›¸
¯
(6Ä%˝›¸
¯    ŒÁ„ŒÄ)˝› ˝
˜
!ÿ¸
˜
Ò‡˛› ˝
Ú
‚¿Ÿ¸
Ú
aIJ›¸

òÚ7˝›˚Ú˝›ò@Ä¿
ˆÄ¿
ˆ
[k
õa
 ¸`ÚÿÊ› ¬˝Ìˇ¸›˝@Ì›˝@Ì› ˛@Ì€˝@Ì› ˛@Ì€˝@Ì›˝@˝
Ä!¯›˝@˝Ä
3¯› ˛@˝
π”K;≥3ôÕĸ€˝@˝    •7áØ•-z~_˚› ˛@˝    e44%-JfQ˚€˝@˝    y”ᣧ©:]œ˚›˝@¸!˙@˚›˝@¸!˚
Ä˚› ˛@Ì€˝@Ì› ˛@Ì€˝@Ì›˝@Ì›˝@Ì› ˛@Ì€˝Ìˇ˛› ˛?Ìˇ˛€Ê›Ê›Ê› ¬Ê› ¬Ê›Ê›Ê› ¬Ê›Ê30›ÊÛ¡¡¡¡¡¡¡¡¡¡¡¡¡¡

Ò«»
àÇ    »
òÇ0»

ÇP»

#t—¯»
!f »
qòp»¡¡¡ò@¿

ˆ¿

ˆ
õk
€a
¡¡0
¯
Ä
†˝–ÄÄ @H`ê@
¿|`Ô0ê@Ä
˝@Ä
˛ @H ê@Ä$†Ô40âËŸ≥≠ûgùDŸ÷œ9
Ö) ]-˜WXÎ ®·9÷@¬îê#•æ¬ÿæVÚ40 Y"Ñ

 ’&§)™    c™jìRÅéıP•V®RhMQIBêö†«z®8™‘Eid®Ú40
K'·\ôD§I2ù2L¢R$ÇD¶·…‰«
dHâ‚RDë¡"SpA<òIJe»Ú40éD—;iòzvTù¥Ã5IKÅ
â·
∂XÀÉ⁄≈!ó$•¿EQ<$OõŸÚ40ãCé-…8R[˘àñ‰ú"Ê2p‰yN$êírìb!$Ês8¯è(4Íí∏Ú#@˙D˛˛"@ˆ  ˙DÒ#@˙D˛˛"@ˆ† ˙DÒ#Ä˙8˛˛@ˆ@ ˙8Ò¡¡8
éC
@@
¿ÄËê˝Ä‡@
ć@:H˝@į6D

ä@ÄÄ@Ä1¸@@Ä@@@Ä˝˜;7ƒıgG!L+[‚uÄÌ ÀJHÀ—l@-mdlåπ&¿[ÎC¢˘« [„eRíeË∂ ^≤;F^ã`˘;7•U    ®JQTUMEÜÅ4ïΩITí¥@V¶¨¥ïQS@çD•eQ+BPçEäÔR™IZ )´VMJ§ï†˘;7
©    'í·dòââtÅ%9%)í%$§@•"bí@âÖ)."JDêâéíJeíR I*R…ë)% ˘;7

*a÷ÇD˚” ÇM¢>R⁄˝µL#©    MØÛ§¡…K:ÛTΔ°…î∑~⁄¶“DÉì◊Ì™`˘;7âÙNõsN§íÑÈ#I)åë)"HIIE…¢Dëíàç≠"$ÑAíác$îë$"T¢“âI@˘Ù@ı ˆÑÏÙ@ı ˆÑÏÒ
ÈÑÏ¡¡
˛@Ä`01Ä@¿Ÿ§@˝íêB@@Ÿ§èˆ^ãa”ííë\ÁTrÑ
Á
»®⁄
%òH§ï¢®é„©
T•    )Hït⁄
H∑â)%!·pE!0‚ô.    fiâᪧ⁄l·—Ì™`r@e"X"≠h    í¡¢H⁄HæëICß∫ò¡ë√I∑6ÁéF›⁄ı˙˛@⁄ı˙˛@⁄ı˙˛@⁄¡¡¡¡¡¡¡¡¡¡¡¡¡¡
 
¿
Ã
 Äb
ÃbîàÄZ GïÖ≥ÕgzîÄ≠]…*’ÕíS8Å)IZròÕ
•†GRsD;Õ;8íåZ<$@Œ ˛… ˛… ˛…¡¡‡pÕ
 Õò@

@
ˆ

@
ˆ
€ka

;Eê!x:≤>KŒ
ƒ ®"®êRET§Œ
$\pGp$†îNâ$Œ(u¿D@=0∂àΩHŒ»Z8˚∫) ‹áHàŒ˚»˚»¡¡¡
‡‡¿¯Ä—ê
 @PÄ—
z¡± ˘6R/Ï∏¨“
lìA¿“ïBöVPëQP“
E¢B$îπ<í¢œbP“
'2¬ E5¢&ÛÉ£Ú†“ï§á»œ&fir$¢›"° “ˆ Õˆ Õ¡¡¡ ¬?‡Ä
ÅÄŒ B@ÄB@Œa ÑQe≈`D@ŒbóJ"rÑääŃ@Œî¶\$ñxìÄ$@Œ
™êF‹ï$ÄŒ>”dñÈ    
ÀÕ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆk[a
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆ[kõa
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆõkÕa
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
ˆ@
ˆÕka¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
ˆ@Ä
ˆkMa¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
ˆÄ¿
ˆMkça¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

ˆ¿

ˆçkÕa¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
ˆ

@
ˆÕka¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆkMa¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆMkça¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆçkøa¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
ˆ@
ˆÕka
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
ˆ@Ä
ˆkMa
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
ˆÄ¿
ˆMkça
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

ˆ¿

ˆçkÕa
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
ˆ

@
ˆÕka
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆkMa
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆMkça
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆçkøa
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇE@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@ä.Introduction to Interapplication Communication4⁄ä˙(‡äSending and Responding to ç¿)qApple Events

, (‡1-11
ˇˇˇˇˇˇˇˇ4^4|lòÄ2^A|rMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^A|r^A|r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
^6|@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^6|@^6|@˜˜˜˜˜˜˜˜˜˜˜˜˜˙ˇˇ
˙ˇ
˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜
4Å4
w?òÄ
Å6
w@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""Å6
w@Å6
w@$˜
˙ˇ˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛
¸ˇ˛¸ˇ˝˚ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛
˙ˇ˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˛¸ˇˇ
ˇ˛ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˜˜˜˜
˙ˇ
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛˜˛˛ˇ˝
ˇˇˇ˛
ˇˇˇ˛    ˇˇˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
˙ˇ˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˝˛ˇ˛
˛ˇ˛ˇˇ    ˇ¸
ˇ    ˇ¸
ˇ
˛ˇ˛ˇˇ˜˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,Zapf Dingbats°dONLNd_äfè(eä
n
°dONLNd\ñh∂)The Cor— °dONLNd    \∂hœ) e suite¶@°dONLNd\–h
+) consists of the basic $¿°dONLNd'\
,h
f)\Apple events¨Ä°dONLNd3\
fh):&, including Get Data, Set Data, Move, °dONLNdYhñt·(qñDelete, and Save,a†°dONLNdjh‚t
∞)L/ that nearly all applications use to communicat»`°dONLNdôh
∞t
∑)Œe.°dONLNdõh
∏t
∫)
 d`°dONLNdúh
∫t
¿)
Y$‡°dONLNdùh
¿t)ou should support °dONLNdØtñĶ(}ñthe °dONLNd≥t¶Ä
)Apple events in the Coro`°dONLNd t
Ä
‘)i.e suite that make sense for your application. °dONLNd˘âäêè(èä
n
°dONLNd˚Üñíù)
AY¿°dONLNd¸Üùí‘) functional-arù@°dONLNd

Ü‘íÚ)7ea suite‚†°dONLNd
ÜÚí
5) consists of a grô°dONLNd
#Ü
6í
U)Doup of Ç¿°dONLNd
*Ü
Uí
÷)Apple events that support a rÄ°dONLNd
GÜ
ג
Ò)ÇelatedÚ@°dONLNd
MÜ
Òí
Û)
 °dONLNd
NíñûŒ(õñfunctional arª†°dONLNd
[íŒû
)8ea. Functional-ar–°dONLNd
lí
û
z)Jea suites include the T! °dONLNd
Éí
zû
É)bex`°dONLNd
Öí
Ñû
î)
t su‡°dONLNd
âí
îû
)ite and the Database suite. °dONLNd
•ûñ™ú(ßñ
Y@Ä°dONLNd
¶ûú™
#)ou can decide which functionaÇ¿°dONLNd
√û
#™
.)ál-aø°dONLNd
Δû
.™
1)
rÑ°dONLNd
«û
2™
¢)ea suites to support accorà‡°dONLNd
·û
¢™
¸)pding to which featur£¿°dONLNd
ıû
¸™)Zes °dONLNd
¯™ñ∂Î(≥ñyour application pr¸`°dONLNd™Î∂
s)Uovides. For example, most worÓ‡°dONLNd(™
s∂
Ü)àd-pr%†°dONLNd,™
á∂)ocessing applications should °dONLNdI∂ñ¬—(øñsupport the TÜ°dONLNdV∂—¬
fl);=ext suite, and most database applications should support the °dONLNdì¬ñŒπ(ÀñDatabasD@°dONLNdö¬∫Œ¡)$e 燰dONLNdú¬¡ŒÀ)su“°dONLNdû¬ÀŒÿ)
ite.°dONLNd£”äflê(‹ä
Y@Ä°dONLNd§”êfl
 ) ou do not need to implement all $ °dONLNdƒ”
 fl
Å)êApple events at once. A`°dONLNd⁄”
Åfl
á)a
Y
‡°dONLNd€”
áfl)ou should begin by supporting °dONLNd˘‡äÏû(Èäthe r¢`°dONLNd˛‡ûϵ)equirπ†°dONLNd‡µÏ¬)ed ¿†°dONLNd‡¬Ï)IApple events, then add support for the events sent by the Edition Managerπ¿°dONLNdO‡Ï(È, °dONLNdQÌ䢮(ˆäthe corà °dONLNdXÌ®˘
-)e events, and the functional-ar6°dONLNdwÌ
.˘
^)Üea events a⇰dONLNdÇÌ
^˘
y)0s appr °dONLNdàÌ
z˘
∞)opriate for yπ‡°dONLNdïÌ
∞˘
¯)6our application. °dONLNdߡä
æ(
äIf necessaryg@°dONLNd≥ˇΩ

))3, you can extend the defioÄ°dONLNdÃˇ
)

Ü)lnitions of the standar0 °dONLNd‚ˇ
á

è)^d mÄ°dONLNd‰ˇ
è

œ)Apple events t∑†°dONLNdÚˇ
œ

È)@o suit °dONLNd˘
ä
é(
ä
sΩ°dONLNd˙
é
¶)pecifiÓ °dONLNd
¶
™)
c^`°dONLNd

´
≠)
 fi`°dONLNd
≠

:)"capabilities of your application. 쇰dONLNd$

;

A)é
YT`°dONLNd%

A

Ö)ou can also defi†°dONLNd5

Ü

„)Ene your own custom °dONLNdH
ä
%•(
"äApple˝Ä°dONLNdM
•
%ß)
 }Ä°dONLNdN
®
%Ú)events. Howeverî`°dONLNd]
Ú
%
‹)J6, only those applications that choose to support your °dONLNdì
&ä
2¨(
/äcustom ·‡°dONLNdö
&¨
2…)"Apple fl`°dONLNd†
& 
2
´)5events explicitly will be able to make use of them. I'‡°dONLNd’
&
¨
2
˜)‚f all applications °dONLNdË
3ä
?“(
<äcommunicated s#†°dONLNdˆ
3”
?„)Iolel3Ä°dONLNd˙
3„
?
')y by means of cø°dONLNd    
3
'
?
E)Dustom ∞†°dONLNd
3
E
?
{)Apple event˚`°dONLNd
3
{
?
§)6
s, every as†°dONLNd$
3
•
?)*pplication would have °dONLNd:
@ä
L
4(
Iä(to support all other applications’ custoË`°dONLNdb
@
4
L
D)™m e°dONLNde
@
E
L
ò)vents. Instead of crY‡°dONLNdy
@
ò
L
ÿ)Seating custom ꆰdONLNdá
@
ÿ
L
ı)@Apple °dONLNdç
Mä
Y¶(
Väevents
@°dONLNdì
Mß
YÃ)
, try to uç`°dONLNdù
MÃ
Y
    )%se the standar¢‡°dONLNd´
M
    
Y
)=d ‡@°dONLNd≠
M

Y
™)!Apple events and extend their defiΰdONLNdœ
M
™
Y
˚)ônitions as necessar—‡°dONLNd‚
M
¸
Y
)R
yE@°dONLNd„
M

Y)
.°dONLNdÂ
_ä
k
«(
häHApple events describe actions to be performed by the applications that r%Ä°dONLNd-
_
»
k(
h
»eceive them. In °dONLNd=
lä
x
c(
uä3addition to a vocabulary of actions, or “verbs,” efµ†°dONLNdp
l
c
x
Ú)Ÿfective communication between °dONLNdé
yä
ÖΔ(
Çäapplications r∏‡°dONLNdú
yΔ
Ö›)<equir– °dONLNd°
y›
Ö
$)es a method of rß¿°dONLNd±
y
$
Ö
L)G
eferring t`°dONLNdª
y
M
Ö
R))
oÙ‡°dONLNdº
y
R
Ö
T)
 t‡°dONLNdΩ
y
U
Ö
])
wÀ‡°dONLNdæ
y
]
Ö
–)indows, data (such as wor1 °dONLNd◊
y
—
Ö)tds or graphic °dONLNdÂ
Üä
íø(
èäelements), fiJ†°dONLNdÚ
Ü¿
í
Ò)6Fles, folders, volumes, zones, and other items on which actions can be °dONLNd8
ìä
ü (
úäperformed. Th•‡°dONLNdE
ì 
ü—)@e ë °dONLNdG
ì—
ü
;)Apple Event Manager p¬ °dONLNd\
ì
;
ü
>)j
rá °dONLNd]
ì
?
ü
’)"ovides a method for specifying strÄ°dONLNd
ì
÷
ü
Ì)óucturù`°dONLNdÑ
ì
Ì
ü
˙)ed °dONLNdá
†ä
¨(
©äUnames, or “noun phrases,” that applications can use to describe the objects on which °dONLNd‹
≠ä
πÿ*Apple events act. °dONLNdÔ
øä
Àù*The ª¿°dONLNdÛ
øù
À
9)%Apple Event Registry: Standard Suites©Ä°dONLNd
ø
:
À
u)ù includes defi◊Ä°dONLNd&
ø
u
À
•);nitions for 
˚‡°dONLNd2
ø
•
À
˝)0Apple event object °dONLNdE
Ãä
ÿ´(
’äclasses,‡°dONLNdM
è
ÿ’)"     which ar,@°dONLNdV
Ã’
ÿ
¯))Be simply names for objects that can be acted upon by each kind of °dONLNdò
Ÿä
Â≈(
‚äApple event. l`°dONLNd•
Ÿ≈
Â
<);Applications use these defiã`°dONLNd¿
Ÿ
<
Â
p)wnitions and ÇÄ°dONLNdÃ
Ÿ
p
Â
ÿ)4Apple Event Manager rv`°dONLNd·
Ÿ
ÿ
Â)houtines to °dONLNdÏ
Êä
Úí(
Ôäcrµ@°dONLNdÓ
Êí
Ú
[)-eate complex descriptions of almost any discrë@°dONLNd    
Ê
[
Ú
˝)…'ete item in another application or its °dONLNd    B
Ûä
ˇ
j(
¸ä1documents. For example, an application could use ë@°dONLNd    s
Û
j
ˇ
“)‡Apple Event Manager rÖ °dONLNd    à
Û
“
ˇ)houtines and °dONLNd    îä´(    ästandar±Ä°dONLNd    õ´¯)!d object class defi‚ °dONLNd    Ư
?)Mnitions to constrÄ°dONLNd    ø
@
≥)Huct a Get Data event that rÊ`°dONLNd    ⁄
≥)sequests “the most °dONLNd    Ïäç(ä
rE°dONLNd    Ìé
§)>ecent invoice to John Chapman in the Invoices database on the | °dONLNd
+
§
Ø(
§Ar`°dONLNd
-
∞)chives server in the °dONLNd
Bä&
c(#ä/Accounting zone” and send the event to the appr{Ä°dONLNd
q
c&
Δ)Ÿopriate application acrΔ@°dONLNd
à
Δ&)coss the network.°dONLNd
ô,ä8ö(5äAn 
ò†°dONLNd
ú,ö8)Apple event object¨‡°dONLNd
Æ,8
)V is any iteß °dONLNd
π,
8
„)*,m supported by an application, such as a worΔ†°dONLNd
Â,
„8
Ó)…d, °dONLNd
Ë9äE
í(Bä;paragraph, shape, or document, that can be described in an 6†°dONLNd#9
íE
–(B
íApple event. Ifl‡°dONLNd19
–E)>n the example °dONLNd?FäRÊ(Oäjust given, the specifiaÄ°dONLNdVFÁR
ç)]'ed invoice, the Invoices database, the 2@°dONLNd}F
çR
ò)¶AræÄ°dONLNdF
òR
—)chives server≥¿°dONLNdåF
—R
˘)9
, and the °dONLNdñSä_‡(\äAccounting zone ar÷Ä°dONLNd®S‡_
)V    e nested AÄ°dONLNd±S
_
Ô)'5Apple event objects. Nearly any item that a user can °dONLNdÊ`älñ(iädif™`°dONLNdÈ`ñl¢)fer凰dONLNdÏ`¢l
„)Fentiate and manipulate on a Macintosh computer can be described as an b†°dONLNd2`
„l(i
„Apple °dONLNd8mäy(väevent object of a specifi‘‡°dONLNdQmy
â)f$ed object class nested within other P¿°dONLNdum
äy)öApple event objects. When °dONLNdèzäÜ¡(Éähandling an ‚¿°dONLNdõz¡Ü)7MApple event that includes such a description, an application must locate the °dONLNdËáäì¶(êäspecifiÓ °dONLNdÔá¶ì≥)ed ı °dONLNdÚá≥ì
V)$Apple event object and perform the rm‡°dONLNdá
Wì
∑)§equested action on it. Ÿ†°dONLNd-á
∑ì
π)`
 ˇQ>@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@l.Introduction to Interapplication Communication4⁄*˙
¯

(‡*1-12    )BSending and Responding to ç¿)qApple Events4^*¿
¯
°dONLNd\lh¡(elMost of the standarB`°dONLNd\¬h )Vd ¿°dONLNd\ h
)Apple events defiy†°dONLNd&\
h
F)Nned in the GÄ°dONLNd1\
Gh
„)/%Apple Event Registry: Standard Suites5@°dONLNdV\
‰h
Ê)ù
 °dONLNdWiluo(rl
rE°dONLNdXipuá)equir\@°dONLNd]iáuÈ)e your application to rX°dONLNdtiÈu
.)becognize specifi°dONLNdÑi
/u
5)Fc ô‡°dONLNdÜi
5u
Û),Apple event object classes. Support for the °dONLNd≤vlÇç(lstandar±Ä°dONLNdπvçÇï)!d Ó‡°dONLNdªvïÇ

)Apple events, including `°dONLNd”v
Ç
)m7Apple event object classes, allows your application to °dONLNd

Élèo(ål
rE°dONLNd
Épè¢)espond to r-@°dONLNd
É¢è
D)2&equests for services or information frî@°dONLNd
<É
Dè
À)¢om any other application or prȇ°dONLNd
ZÉ
Àè
Á)áocess. 

¥*ª
¯4µ*ª
¯ ∂l∂
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd
b•l¥•(∞l    Handling ò~°dONLNd
k••¥ı)9Apple Eventsˇˇˇˇˇˇ€r(∞

1
°dONLNd
yªl«Ñ(ƒlFigurR¿°dONLNd
~ªÑ«ò)e 1-6@°dONLNd
ɪò«È) shows a common ~`°dONLNd
ìªÍ«
*)RApple event frb°dONLNd
°ª
*«
[)@
om the Cor⁄`°dONLNd
´ª
[«
‰)1!e suite, the Set Data event. The °dONLNd
ûl‘
Ê(—lYSurfDB application is the client; it sends a Set Data event to the SurfCharter applicatio@°dONLNd%»
Á‘
Ò(—
Án. °dONLNd(’l·†(filThis event r©¿°dONLNd4’†·
N)4&equests that SurfCharter use some new ¶†°dONLNdZ’
O·
f)Øsales R†°dONLNd`’
g·
m)
fi_`°dONLNdb’
m·
|)gur∫†°dONLNde’
|·
Ò)es generated by SurfDB to °dONLNd‚lÓ
’(ÎlMupdate the data for the chart named “Summary of Sales” in the document named À‡°dONLNdÂ
’Ó
fl(Î
’“S†°dONLNdŒ‚
‡Ó
Ï)aleΩ†°dONLNd—‚
ÏÓ
Ú)s °dONLNd”Ôl˚ï(¯l    Chart.” Tæ °dONLNd‹Ôï˚¢))he z¿°dONLNdflÔ¢˚
m)-Apple event contains information that identifiù‡°dONLNdÔ
m˚
Ë)Àes an action—setting data—°dONLNd'¸l
÷(
land a description of the ‡°dONLNd@¸◊

Ì)k=Apple event object on which to perform the action—“the chart °dONLNd}
    l

û(
l@named Summary of Sales in the document named Sales Report.” The ˇ¿°dONLNdΩ
    
û

Í(

ûApple event also °dONLNdŒ
l
"

(
l%includes the new data for the chart. ˘`°dONLNdÛ



"
)û
 


D*
U
¯4
E*
U
¯"
E*]

ˇ·ˇ‚7^
    °dONLNdı
:l
Eñ(
Bl
Figure 1-6°dONLNd
:Æ
E¥)B
A0°dONLNd

:¥
EÚ) Set Data event
°dONLNd5lAr(>l
Tµ¿°dONLNd5qA|)o rp@°dONLNd5}A¥)espond appr$‡°dONLNd!5µA‹)8    opriatelyfl@°dONLNd*5€A
f)&!, the SurfCharter application in î@°dONLNdK5
gA
)åFigurg°dONLNdP5
A
ì)e 1-6Ä°dONLNdU5
îA
 ) can use the °dONLNdbBlNá(KlApple˝Ä°dONLNdgBáNâ)
 }Ä°dONLNdhBäN
F)(Event Manager to determine what kind of \Ä°dONLNdêB
FN
Â)º#Apple event has been sent and pass °dONLNd≥Ol[y(Xlthe]`°dONLNd∂Oz[|)
 ›`°dONLNd∑O|[«)event to the appr     °dONLNd»O»[È)Lopriate â`°dONLNd–OÈ[
D)!Apple event handler˘‡°dONLNd„O
C[
H)Z. õÄ°dONLNdÂO
H[
X)An 
¥ °dONLNdËO
X[
µ)Apple event handlerê@°dONLNd˚O
∂[
œ)^ is an °dONLNd\lh±(elapplication-defi|‡°dONLNd\≤h
m)F,ned function that extracts pertinent data frΩ¿°dONLNd>\
mh
ã)ªom an z@°dONLNdD\
ãh
Ò)Apple event, performs °dONLNdZiluÄ(rlthe r¢`°dONLNd_iÄu·)equested action, and rŒ†°dONLNdui·u
)a
eturns a rß¿°dONLNdi
u
Î)*5esult. In this case, the Set Data event handler must °dONLNd¥vlÇï(l
locate an Õ °dONLNdævïÇ
>))&Apple event object—that is, the specifi/°dONLNdÂv
?Ç
ù)™ed chart in the specifiê@°dONLNd¸v
ùÇ
Ù)^ed document—and °dONLNdÉlèŸ(ålchange the data displaye+†°dONLNd$É⁄è
)n
d in the cŒ¿°dONLNd.É
è
&)(    hart as r◊ °dONLNd7É
&è
R)$
equested. 


T*
¯4
S(
T)ò@@
ˆ@
ˆ
T)
î¡¡?…ˇ¯˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚
?˛˝Œˇ¸˚?˛ˇˇŒˇ¸˚?˛
Œˇ¸˚?˛
ÊˇÄ¯Óˇ¸˚?˛ˇ˘ÊˇÄÓˇ¸˚?˛Q    ÊˇÄ ¿Óˇ¸˚?˛ˇ˘ÊˇÄA0Óˇ¸˚?˛Q    ÊˇÄĻӡ¸˚?˛ˇ˘ÊˇÅÓˇ¸˚?˛`ÊˇÇÚÓˇ¸˚?˛ÄÊˇÑÅ©Óˇ¸˚?˛¿ÊˇàTÌˇ¸˚?˛ Êˇà"(Ìˇ¸˚?˛ÊˇêBÌˇ¸˚?˛ »ÊˇêDÌˇ¸˚?˛B§ÊˇêÑ    Óˇ¸˚?˛ D    RÊˇêà Óˇ¸˚?˛ à¢Êˇë Óˇ¸˚?˛A)RÊˇâ@Óˇ¸˚?˛Ay"ÊˇâG¿Óˇ¸˚?˛BA$ÊˇÑO¿Óˇ¸˚?˛B ÅÊˇÉ¯¿Óˇ¸˚?˛D ˇÊˇÅì¯flÓˇ¸˚?˛$!ÊˇÄ~8ˇÓˇ¸˚?˛$AÊˇIJ8„Óˇ¸˚?˛AÊˇÄèx„Óˇ¸˚?˛AÊˇÄéΩ„Óˇ¸˚?˛AÊˇÄèz˜Óˇ¸˚?˛AÊˇÄéΩÎÓˇ¸˚?˛
 ÄÊˇÄflz˜Óˇ¸˚ò@@Ä
ˆ@Ä
ˆ
î)
‘?˛†ÄÊˇÄÆΩÎÓˇ¸˚?˛cÄÊˇÄflz˜Óˇ¸˚?˛<ÊˇÄÆΩÎÓˇ¸˚
?˛˝ÊˇÄflz˜Óˇ¸˚?·ˇÄ˚ÔæÓˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚ò@Ä¿
ˆÄ¿
ˆ
‘)?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚ò@¿

ˆ¿

ˆ)T?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚?…ˇ¸˚…ˇ¸˚¡¡¡¡¡¡¡¡¡¡¡

ÿ„åx»
ÑA    »
åA»


A »

ÚÒ »
Ç&@»
8áÿ@»¡¡¡¡¡
Ù
Å
Å¿@—ê
A @—ÑÙYÇ"‚Ö“fl—≈,¢Ñ    
À%E
Uj—
    %ßÓÑÄ^)âûL—«DàÑ”Oœ®û—    ≈√é√ääGî— ≈ ≈
¿≈¡¡9
éCÉ  ‡Ätê˝Ä    p 
Ä    
p :DIJ į7D
≈ @Ä ÄÄ˝  Ä
  @@˝˜;7ƒ∫É≥« ¶+;r:¿w≈e•$e—6 &∂¥våΩ¿;{#¢}cê;r≤“í2‰õ[Y&.â∞˘;7•JÑ‘JP™U-%C@öäãfi§™íö SS\öïI+@M$Ud©)°(M%EÔRUEM©´-*Tî–˘;7
îÑìí‡≤òII:@ìíî…$í íRUì"RJ@IDô-I"HINIJdâäI%))iPô$ê˘;7

    0÷Å"˚sj
¡'ë)mµ&§Ñá'Ø€T¿ìh´9{RcPìhèî∂øŒìÍBA”v˝©0˘;7â⁄'õqߧRDtë•ΔHï"$D§••í$à“HM¨í"B “Gäc$JâRQrH© ˘Ù 
ıˆÑÏÙ 
ıˆÑÏÒ

ÈÑÏ¡¡
˛ @Fc ¿Ÿî ¸à îÄ @Ÿîã˚.I∞È…
ê`Æ„™9îÖw
»î⁄
î$TT—
T§°’™Ráw®ïz⁄
(≥ƒò§ê∏˚ò·Ló)«ªí⁄<‡Ë¸È09 
"A,!V¥    )    a¢$⁄(∑H®ë!”›ú‡…¡§€õΔNF›ÿ⁄ı
˙˛ ⁄ı
˙˛ ⁄ı
˙˛ ⁄ò@

@
ˆ

@
ˆT)î¡¡¡¡¡¡¡¡¡¡¡¡¡¡
 
¿
Ã
 Ä1
Ãbîà@Me#ïɱČgzî@¶ÆÂ*“ÄŒíS8A$§ÆrîÕ
•†#I    ;D    5ÄŒ;âF.<" Œ ˛… ˛… ˛…¡¡‡pÕ
 Õ
;D» à|Z>+Œ
ƒ…T!T
à)%TTŒ
$Z8C∏êJ.àîŒ(r‡F [Hº®Œ»Y˘›nGHHŒ˚»˚»¡¡¡
‡‡¿Äw‡Ä
֐
 @"@)
÷
9aŸ ‹∂!"N≤@)"˙Àí‹ÿ
fQ°¿jï!Z!<ÀU@Ie) ÿ
B·"$LπR"DR^ÄR,·&Iÿ
#±b Dù¢¶B Dtà¿õ82?Rÿí‚G»Œñfi9$G»ÓTßà“-‚*"8ÿˆÄ“ˆĆ“Û¿–¡¡ ¡‡@
Ä¿Œ A
@@A Œa…B
H˛µ‰∞B Œbï•YÑJJA¬ Œî•.ãxRí@" Œ
©H&Œû‘Ç"@Œ>—á4ãËîàÅ…ÄŒ¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆî)‘¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆ‘)¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆ)F¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
ˆ@
ˆ
T)
î
¡¡»30˚»˚ ¬»˚»˚»˚ ¬»˚ ¬»˚»˚»˚  „‡‰(@Ê

Î˚ 
n‡ÂΔ“ÿÊ
˘@Â?ãÌ˚*â@Ê
çÌ˚
 y ÂÁàÌ˚ ¬»˚ ¬˛@ÂÌ˚˛Ä˙Ô Ì˚;ïôÕ¿˚ÛŒÊfspÓ˚ ¶V|” ˚{fl∑wÄı
Èñü4»Á ¶V$” ˚oüˇ˚Ù
)ñâ4»Ó˚ ªï‹M ˚3o|Ï{ÛÓÊwHÁ"˜3{flè«˚ÄÙ
ÄÎ˚"ˆcÔ
ÄÎ˚
Ûc◊˚ ¬»˚ ˘ıˇÿˇˇ˝ıfl˚
˝ı˘`Ë˚
˛
`ıàò˘p¯Ï˚ ˇ˘˛
pı˚ˇÿÂ!    Q    ˇÿıĸ ¿Ì˚#     ˇ˘˝">"z¸"8ĸA0Ê(    Q    ˝fl˝ĸÄ»Ì˚)    ˇ˘˝9fioˇÄ˛ĸ
Ì˚)    `˝àèÏÌ˚»˛àòĸÚÌ˚$     Ä˝go~¿˛˚ˇÿÅ©Ê'    ¿ˇÿ˝=Óyˇ¿˛˘pTÄÓ˚      pı"8˘`"(ÄÁ    `ı˜BÄÓ˚ »˛ı˜DÄÓ˚B§˛ıˇ¯˜Ñ    Ì˚  D    R˛ı
¿¯à Ê à¢˛ı
x¯ Ï˚ A)R˛ı
¯    @ÂAy"˛ı
¯    G¿Ì˚BA$˛ı
¯O¿Ì˚B Å˛ı
¯¯¿Ì˚ D ˇ˝ı
¯
ì¯flÊ$!¸ı
˜~8ˇÌ˚ $A¸ı
˜˛8„ÊA¸ı
˜èx„Ì˚A¸ıp¸éΩ„Ì˚A¸ıH¸èz˜Ì˚ A¸ıIùµfiŒ˝éΩÎÊ*
 Ä˝˛
IJ
˛KÚe+)˝flz˜Ì˚ò@@Ä
ˆ@Ä
ˆ
î)
‘
& †Ä˝˛2Ä
˛J%+)˝ÆΩÎÊ)˛
cÄ˝˛ Ê|Êh«˛q˘ÂΔ…˝flz˜Ì˚&˛<¸˛ üHüUÈ˛
˛
˚ÆΩÎÌ˚"¯˛"ôHôU    ˛
˛
˚flz˜Ì˚ ˘˛óDóTÁ˛
˜˚Ôæʯı

‰˚ ˘ı(
›¯ıg+ù0Â˚#]‡˛˝¿Äí:SxÂ˚*ì˛à˝" Ä íFS@˛
¿ Ï˚( ó”˛bthm#q屿bGù8˛ †
Ê,îì‡˛jT˘$†~˚¯˝
ì∏8€ÏÓ˚' îì˛äjTò§¢2¿¿¸s%Ò¯Á(tù‡˛qÍTx√!ŒªÄ˘3•1àÓ˚¯˚ĸ
˘
œ$¯Ó˚¯¸
˚
˛‰˚ ˘ıd∑8›¯Ñ˝º2Ú¸ê‰˚% ˘
˛¢ ÉDêˆˇ
‡˙ˇ˛Ù'¯3úÕ-‹iúÉç∏r<àˆ
 ˙˚˚)¯I%3*Ω(˚Ç_¸ˆ     æÊ»øÔ˚˚)¯I%1*°("öäS¸ˆà    †¢ÊeúÃÕ¸Ø˚˚' ˘1ŒÍù$y¯rO¸ˆ     ¢‰eî建ØÙ&¯ı@¸¸¸     ¢ÊeúûøØ˚˚$ ˘ı¸"¶¸"     ¢Êeúû¸/Ù%¯ıgL‹¸Ñ¸ æ‡˝
?Ô˚˚"¯ıîfl(¸ƒ¸
 ˙˚˚ ¯ıî—¸àå¸à
†˘ˇ˚˚! ˘ıgN‰¸Ñ¸
 ˚

3Ù#¯ı@¸î¸
 ˚

{˚˚! ˘ıĸ"¶¸"
 ˚

œÙ$¯ı
¸¸Ñ¸     @ 
œ˚˚$¯ı
¸¸ƒ¸     %ÄÄ 
{˚˚$¯ı
¸¸àå¸à    †!ãÜÕ,¿
˚˚" ˘ı
¸¸Ñ¸     %^âüΩ¿
ˇÙ$¯ı
¸¸î¸     NÜôØÄ
˚˚ ˘ı
¸¸"¶¸"
 ˚

Ù!¯ı
¸¸Ñ¸
 ˚

˚˚$¯ı
¸¸ƒ¸  ˛

˚˚#¯ıˇ¯˚¸àå¸à    † 


˚˚" ˘ı
¿¸¸Ñ¸     :ù∂ßd
Ù$¯ı
x¸¸î¸     &ìJ©:Ó
˚˚" ˘ı
¸¸"¶¸"     96gw
Ù#¯ı
¸¸Ñ¸ 
˝

˚˚#¯ı
¸¸ƒ¸ ˝

˚˚#¯ıp˛¸àå¸à
†˚

˚˚! ˘ıH¸Ñ¸
 ˚

Ù#¯ıIªÄ¸î¸
 ˚

˚˚! ˘ıK◊ä@¸"¶¸"
 ˚

Ù,¯3Δ9òΔpJTä@¸Ñ¸
 ˚

˚˚,¯ÃÄ)Bd
)ÄqÀÖĸƒ¸
 ˚

˚˚*¯ÃÄ)rd
!‡¸¸àå¸à
†˚

˚˚) ˘
LÄΔ
dΔ¯˝¸Ñ¸
 ˚

Ù*¯ÃÄ    )Jd
(길î¸
 ˚

˚˚( ˘3Δ1òœ`¸¸"¶¸"
 ˚

Ù#¯ı ¸Ñ¸
 ˚

˚˚#¯ıvp¸ƒ¸
 ˚

˚˚$¯ıœ ˝à
èè¸à
†˚

˚˚" ˘ı8 ˝
¸
 ˚

Ù$¯ıÁ˝

ñ¸
 ˚

˚˚ ˘ı
¸¸"Ó¸"
 ˚

Ù$¯ı
¸¸x¸ p˛
˚˚%¯ı
¸¸0¸
 ÑÎLËf
~¸˚!¯ı
¸ˆà
†d÷¶®î
¸˚ò@Ä¿
ˆÄ¿
ˆ
‘)
 ˘Ùˇ¸ˆ ÷™òî

Ĉ!¯ıˇ¯˚ˆ „÷¶êd
Ä˝˚ ˆ"
 ˝
¿ˆ‰ˆ
 ˝ 
@˝˚‰

˘ˇ¯ ˚
@˝˚‰
â˘à† 
@˝˚ Â

˘ §`
@ˆ‰

˘ ÍÄ
@˝˚ Â
#˘" n@
@@˘‰

˘ ‰‡
@
@˚‰

˘ ˚
@
ÁL˚‰
â˘à†˚
@îfi˚ Â

˘ ˚
@î–˘‰
8˛ ˚
@ÁN˚ Â#"$" ˚
@ѯ"‰
n%ü ˛ í
@Ñ˚!‰
Ù'œÄ ¯≠
@˝˚!‰â"Ñ&LÄà¢fœ

@˝˚" Â
r9«Ä#ôª¡$Å@˘‰

˘?ˇÑô1›¡
@,Ó˚ Â
#˘""ƒ
ô#≥@
æ

˘ df`Ó‡
@–î˚!‰

˝Ä¿$DtD˜`
@éí˚!‰
â˛Ä¿®à‰hÃ
@˝˚ Â
Y‹Ê„ÿ ƒˇ˚∞
@ˆ!‰
=}(üîfiÄ?ˇÑ¿ˇ
@˝˚! Â#!°(ôî–Ä"#@b0
@
¯"‰
$óìŒÄ"@»†
@

˚‰

˘ @ƒ`
@…õÄ˚‰
â˘à†aà‡
@+Â˚ Â

˘ 3"@
@*!˘‰

˘ 
Û¬«
@…‹Ä˚ Â
#˘" 
Lé#Ö$
@¯‰

˘ 
Ãáéf
@˚‰

˘ LůÅ
@˝˚‰
â˘à†
≥Ê
ˇ@˝˚ Â

˘ ˚
{¿ˆ‰

˘ ˚
KÄ˝˚ Â
#˘ˇ˛" ˚
œÄˆ‰
˘ˇ¸ ˚
oÄ˝˚‰ˆ
 ˚
;Ä˝˚‰ˆà
†˚
3¸¸˚ ˆ
 ˘ˇÙ‰ˆ
 ˚

˚˚ ˆ"
 ˚

Ù‰ˆ
 ˚

W˚˚‰ˆ
 ˚

w˚˚‰ˆà
†˚

G˚˚ ˆ
 ˚

Ù‰ˆ
 ˘ˇ˚˚ ˆ"
 ˘ˇÙ‰ˆ Ú˚‰ˆ Ú˚‰ˆà†Ú˚ ˆ Ήˆ Ú˚ ˆˇ‡Î»˚»˚»˚ ¬»˚ ¬»˚ò@¿

ˆ¿

ˆ)T
»˚»˚ ¬»˚ ¬»Ã˚…UT˚¡¡¡¡¡¡¡¡¡¡¡

ÿ„åx»
ÑA    »
åA»


A »

ÚÒ »
Ç&@»
8áÿ@»¡¡¡¡¡
Ù
Å
Å¿@—ê
A @—ÑÙYÇ"‚Ö“fl—≈,¢Ñ    
À%E
Uj—
    %ßÓÑÄ^)âûL—«DàÑ”Oœ®û—    ≈√é√ääGî— ≈ ≈
¿≈¡¡9
éCÉ  ‡Ätê˝Ä    p 
Ä    
p :DIJ į7D
≈ @Ä ÄÄ˝  Ä
  @@˝˜;7ƒ∫É≥« ¶+;r:¿w≈e•$e—6 &∂¥våΩ¿;{#¢}cê;r≤“í2‰õ[Y&.â∞˘;7•JÑ‘JP™U-%C@öäãfi§™íö SS\öïI+@M$Ud©)°(M%EÔRUEM©´-*Tî–˘;7
îÑìí‡≤òII:@ìíî…$í íRUì"RJ@IDô-I"HINIJdâäI%))iPô$ê˘;7

    0÷Å"˚sj
¡'ë)mµ&§Ñá'Ø€T¿ìh´9{RcPìhèî∂øŒìÍBA”v˝©0˘;7â⁄'õqߧRDtë•ΔHï"$D§••í$à“HM¨í"B “Gäc$JâRQrH© ˘Ù 
ıˆÑÏÙ 
ıˆÑÏÒ

ÈÑÏ¡¡
˛ @Fc ¿Ÿî ¸à îÄ @Ÿîã˚.I∞È…
ê`Æ„™9îÖw
»î⁄
î$TT—
T§°’™Ráw®ïz⁄
(≥ƒò§ê∏˚ò·Ló)«ªí⁄<‡Ë¸È09 
"A,!V¥    )    a¢$⁄(∑H®ë!”›ú‡…¡§€õΔNF›ÿ⁄ı
˙˛ ⁄ı
˙˛ ⁄ı
˙˛ ⁄ò@

@
ˆ

@
ˆT)î
¡¡¡¡¡¡¡¡¡¡¡¡¡¡
 
¿
Ã
 Ä1
Ãbîà@Me#ïɱČgzî@¶ÆÂ*“ÄŒíS8A$§ÆrîÕ
•†#I    ;D    5ÄŒ;âF.<" Œ ˛… ˛… ˛…¡¡‡pÕ
 Õ
;D» à|Z>+Œ
ƒ…T!T
à)%TTŒ
$Z8C∏êJ.àîŒ(r‡F [Hº®Œ»Y˘›nGHHŒ˚»˚»¡¡¡
‡‡¿Äw‡Ä
֐
 @"@)
÷
9aŸ ‹∂!"N≤@)"˙Àí‹ÿ
fQ°¿jï!Z!<ÀU@Ie) ÿ
B·"$LπR"DR^ÄR,·&Iÿ
#±b Dù¢¶B Dtà¿õ82?Rÿí‚G»Œñfi9$G»ÓTßà“-‚*"8ÿˆÄ“ˆĆ“Û¿–¡¡ ¡‡@
Ä¿Œ A
@@A Œa…B
H˛µ‰∞B Œbï•YÑJJA¬ Œî•.ãxRí@" Œ
©H&Œû‘Ç"@Œ>—á4ãËîàÅ…ÄŒ¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆî)‘
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆ‘)
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆ)F
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
ˆ@
ˆF)Ü¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
ˆ@Ä
ˆÜ)Δ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
ˆÄ¿
ˆΔ)¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

ˆ¿

ˆ)F¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
ˆ

@
ˆF)Ü¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆÜ)Δ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆΔ)¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆ)8¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
ˆ@
ˆF)Ü
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
ˆ@Ä
ˆÜ)Δ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
ˆÄ¿
ˆΔ)
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

ˆ¿

ˆ)F
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
ˆ

@
ˆF)Ü
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆÜ)Δ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆΔ)
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆ)8
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ@N@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@ä.Introduction to Interapplication Communication4⁄ä˙(‡äSupporting P).)AppleScript and Other Scripting Languages

, (‡1-13
ˇˇˇˇˇˇˇˇ4^4|lòÄ2^A|rMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^A|r^A|r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
^6|@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^6|@^6|@˜˜˜˜˜˜˜˜˜˜˜˜˜˙ˇˇ
˙ˇ
˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜
4Å4
w?òÄ
Å6
w@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""Å6
w@Å6
w@$˜
˙ˇ˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛
¸ˇ˛¸ˇ˝˚ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛
˙ˇ˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˛¸ˇˇ
ˇ˛ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˜˜˜˜
˙ˇ
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛˜˛˛ˇ˝
ˇˇˇ˛
ˇˇˇ˛    ˇˇˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
˙ˇ˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˝˛ˇ˛
˛ˇ˛ˇˇ    ˇ¸
ˇ    ˇ¸
ˇ
˛ˇ˛ˇˇ˜˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähù(eäThe ]`°dONLNd\ùh
)Apple Event Manager prS`°dONLNd\
h
.)novides r懰dONLNd"\
.h
˘)#1outines that a server application can use in its °dONLNdSiäu
3(rä&Apple event handlers to take apart an h°dONLNdyi
3u
Ò)©*Apple event and examine its contents. The °dONLNd£väÇ
(äSurfCharter application in ◊†°dONLNdæv
Ç
)vFigur™`°dONLNd√v
Ç
,)e 1-6G‡°dONLNd»v
-Ç
_) can interpr    °dONLNd‘v
`Ç
Â)3 et the contents of the Set Data °dONLNdÙv
ÂÇ)ÖApple °dONLNd˙Éäèº(åäevent accorh@°dONLNd
ɺèˇ)2ding to the defi‘@°dONLNd
ɡè
q)Cnition of that event in the Ä°dONLNd
1É
rè)s%Apple Event Registry: Standard SuitesÒ@°dONLNd
VÉè)ú. °dONLNd
Xêäú
0(ôä%The Set Data event handler uses both ¥¿°dONLNd
}ê
0ú
ò)¶Apple Event Manager r®†°dONLNd
íê
òú)houtines and the SurfCharter °dONLNd
Æùä©fl(¶äapplication’s own rû°dONLNd
¡ùfl©
ï)U*outines to locate the chart and make the rø†°dONLNd
Îù
ï©
·)∂equested change.°dONLNd
¸Øäªù(∏äThe ]`°dONLNdØùª
)Apple Event Manager also prn@°dONLNdØ
ª
B)Çovides rŸ¿°dONLNd#Ø
Bª
˝)#-outines that a client application can use to °dONLNdPºä»•(≈äconstrï °dONLNdVº•»Ì)uct and send an ¢¿°dONLNdfºÌ»
Q)HApple event. Howeverz °dONLNdzº
Q»
±)d, the most important r‚ °dONLNdêº
±»
»)`equir˘`°dONLNdïº
»»
ı)
ement for °dONLNdü…ä’
X(“ä1applications that support IAC is the ability to rãÄ°dONLNd–…
X’
Ü)Œ
espond to P`°dONLNd⁄…
Ü’
¿).Apple eventsÿ °dONLNdÊ…
¿’
˝):, because this °dONLNdı÷ä‚›(fläability is essential f}@°dONLNd÷fi‚
9)Tor an application tha
`°dONLNd ÷
:‚
o)\t users can c≥°dONLNd-÷
o‚
Å)5ontr
@°dONLNd1÷
Ç‚
á)
ov¿°dONLNd2÷
á‚
ô)l thr∑‡°dONLNd7÷
ô‚
∂)ough sR°dONLNd=÷
∑‚
“)cripts.û¿°dONLNdD÷
“‚
˝)
 The next °dONLNdN„äÔ
#(Ïä"section describes how you can use ˇ°dONLNdp„
#Ô)ô6Apple events to support scripting in your application.°dONLNdßıä

÷(˛äThe chapter “Intrµ`°dONLNd∏ı÷


)Loduction to â °dONLNdƒı



é)5Apple Events” in this book pr¿°dONLNd·ı
è


Ì)Ñovides an overview oì`°dONLNdıı
Ì


Ú)^f ‡°dONLNd˜ı
Û


˙)
A– °dONLNd¯ı
˙

)pple °dONLNd˝
ä
¢(
äeventÕ@°dONLNd
¢
≠)s aä@°dONLNd
Æ
≥)
n[†°dONLNd
¥
Ì)d describes hD†°dONLNd
Ó

E):ow you can use the k@°dONLNd&

E

Á)W!Apple Event Manager to implement Ä°dONLNdG

Á
)¢Apple °dONLNdM
ä

Ö(
ä8events in your application. The chapters “Responding to  °dONLNdÖ

Ö

 )˚Apple Events,”  °dONLNdî

À

–)F
“ °dONLNdï

–

€)Cr¶°dONLNdó

€
)eating and °dONLNd¢
ä
(∞(
%äSending ·°dONLNd™
∞
(
G)& Apple Events,” “Resolving and CrÖ†°dONLNd 

H
(
°)òeating Object SpecifiŇ°dONLNdfl

¢
(
Δ)Zer Recor‡Ä°dONLNdÁ

Δ
(
Ì)$    ds,” and °dONLNd
)ä
5®(
2ä“Recor¢`°dONLNdˆ
)®
5æ)ding (†°dONLNd˚
)ø
5
)Apple Events” prI†°dONLNd
)

5
±)M%ovide detailed information about the °dONLNd0
)
±
5
Î)•Apple Event °dONLNd<
6ä
B±(
?äManagerT†°dONLNdC
6±
B∂)'. T†°dONLNdE
6∂
B∏)
 


IH
d4
JH
d


tH
|4
uH
| 
vH
v

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNdH
aH
tù(
oHSupporting ’f°dONLNdS
aù
t
Ÿ)U)AppleScript and Other Scripting LanguagesˇˇˇˇˇˇV˛(
o
1
°dONLNd~
Öä
ëë(
éä
A∫†°dONLNd
Öë
ëì)
 
:†°dONLNdÄ
Öî
ë≠)script¬@°dONLNdÜ
Ö≠
ë
®): is any collection of data that, when executed by the apprÄ°dONLNd¿
Ö
©
ë
‘)¸
opriate pr©@°dONLNd 
Ö
‘
ë)+ogram, causes °dONLNdÿ
íä
û£(
õäa corrù`°dONLNdfi
í£
û
…)Cesponding action or series of actions. For example, some database, °dONLNd!
üä
´
(
®ätelecommunications, and pag©‡°dONLNd<
ü

´
)Çe-lØ¿°dONLNd?
ü

´
€),ayout applications allow users to automate rË@°dONLNdk
ü
€
´)ƒepetitive or °dONLNdx
¨ä
∏
f(
µä3conditional tasks by means of scripts written in prI@°dONLNd´
¨
g
∏
)›#oprietary scripting languages. The °dONLNdŒ
πä
Ŭ(
¬äHyperTT†°dONLNd‘
π¨
≈π)"alkà °dONLNd◊
∑π
¿æ(
æπ
®
Δ °dONLNdÿ
πø
≈
q+) scripting language allows users to contrÄ°dONLNd

π
r
≈
Ó)≥ol the behavior of HyperCar´`°dONLNd
π
Ó
≈
Ù)|
d« °dONLNd
∑
Ù
¿
˘(
æ
Ù
®
¡ °dONLNd
π
˙
≈
¸+
 °dONLNd
Δä
“¿(
œästacks. MacrÊ@°dONLNd+
Δ¿
“—)6o pr¢‡°dONLNd/
Δ“
“
Û)Aograms can automate tasks at the level of mouse clicks and keystr8†°dONLNdp
Δ
Ù
“
(
œ
Ùokes.√‡°dONLNdu
Δ

“)
 C‡°dONLNdv
Δ
“)
 √‡°dONLNdw
Δ
“)
 °dONLNdy
ÿä
‰‚(
·äThe Open Scripting Ó¿°dONLNdå
ÿ‚
‰Ì)XAr{°dONLNdé
ÿÓ
‰
)    chitectur/¿°dONLNdó
ÿ

‰
D)'
e (OSA) prK °dONLNd°
ÿ
D
‰
å)/ovides a standar£ °dONLNd±
ÿ
å
‰
¸)Hd mechanism that allows °dONLNd…
Âä
Ò≈(
Óäusers to contr3¿°dONLNd◊
ÂΔ
Ò
Û)<Hol multiple applications with scripts written in a variety of scripting °dONLNd
Úä
˛
S(
˚ä-languages. Each scripting language has a corr≠@°dONLNdL
Ú
S
˛    )…&esponding scripting component. When a °dONLNdr
ˇä
(äXscripting component executes a script, it performs the actions described in the script, °dONLNd ä‹*including sending ‹`°dONLNd‹‹
ê)R)Apple events to applications if necessary
°dONLNd    
ê
ï)¥. °dONLNd    ä*≤('äThe OSA°dONLNd    ≤*
:)( comprises the following parts:,Zapf Dingbats°dONLNd    /4ä;è(:ä
n
°dONLNd    11ñ=©)The ]`°dONLNd    51©=
t),Apple Event Manager allows applications to rW@°dONLNd    a1
t=
¢)À
espond to  °dONLNd    k1
¢=
).Apple events sent by °dONLNd    Ä=ñI
(Fñscripting components (see V‡°dONLNd    ö=
I
)vthe ¥@°dONLNd    û=
I
%)pr{`°dONLNd    †=
&I
i)
evious section, ı¿°dONLNd    ∞=
iI
Î)C“Sending and Responding to fi°dONLNd    À=
ÎI)ÇApple °dONLNd    —IñU∏(RñEvents”\`°dONLNd    ÿIπUæ)#).°dONLNd    €^äeè(dä
n
°dONLNd    ›[ñg©)The ª¿°dONLNd    ·[©g
E)%Apple Event Registry: Standard Suites©Ä°dONLNd
[
Fg
Y)ù defi†°dONLNd
[
Zg
ù)nes the standarÄ°dONLNd
[
ùg
‰)Cd vocabulary of °dONLNd
*gñs±(pñApple˝Ä°dONLNd
/g±s≥)
 }Ä°dONLNd
0g¥s”)events.°dONLNd
8|äÉè(Çä
n
°dONLNd
:yñÖ )The standarÌ@°dONLNd
Ey Ö
Q)4d scripting component data str∫‡°dONLNd
cy
RÖ
i)àuctur@¿°dONLNd
hy
jÖ
{)es, r`°dONLNd
my
|Ö
∏)outines, and rΩ‡°dONLNd
{y
∏Ö
–)<esour °dONLNd
Äy
—Ö
¸)
ces allow °dONLNd
äÖñë
á(éñ7applications to interact with any scripting component. °dONLNd
¬öä°è(†ä
n
°dONLNd
ƒóñ£©)The ]`°dONLNd
»ó©£
\)%AppleScript component implements the h`°dONLNd
Ìó
\£
Ê)≥AppleScript scripting languages¿°dONLNdó
Ê£
Ë)ä
.ˇQÿ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@l.Introduction to Interapplication Communication4⁄*˙
¯

(‡*1-14    )BSupporting P).)AppleScript and Other Scripting Languages4^*¿
¯
°dONLNd\lh(elThe 
ª¿°dONLNd\hÓ)AppleScript component,Z¿°dONLNd\Ôh
V)p which implements the 
È`°dONLNd0\
Vh
Á)gAppleScript scripting language, °dONLNdO\
Ëh
Ù)í is °dONLNdSiluı(rlthe implementation of the OSȦ°dONLNdpiıu

)â pr5°dONLNdsi
u
1)
ovided by Ú†°dONLNd}i
0u
{).Apple Computerõ °dONLNdãi
{u
fl)K, Inc. Users can view a °dONLNd£vlÇ≈(lscript written in the ◊@°dONLNdπv≈Ç
ä)Y-AppleScript scripting language in several difò@°dONLNdÊv
ãÇ
ó)Δferz¿°dONLNdÈv
óÇ
ß)ent 
ÿ °dONLNdÌv
ßÇ
Ã)    dialects,P°dONLNdˆv
ÕÇ
€)& or °dONLNd˙ÉlèØ(ålversions of the T °dONLNd

ÉØè
))CAppleScript language that r°dONLNd
%É
)è
k)zesemble specifi±°dONLNd
4É
lè
–)Cc human languages or °dONLNd
Iêlúu(ôlprG °dONLNd
Kêvú€)
ogramming languages.°dONLNd
`¢lÆÑ(´lFigurR¿°dONLNd
e¢ÑÆò)e 1-7@°dONLNd
j¢òÆÕ) shows the r*Ä°dONLNd
v¢ŒÆ
„)6?elationships among some of these parts. The client application °dONLNd
µØlªt(∏lin9¿°dONLNd
∑Øuªw)    
 π¿°dONLNd
∏Øwªè)FiguråÄ°dONLNd
ΩØ誣)e 1-7*°dONLNd
¬Ø§ª©) ií`°dONLNd
ƒØ©ªÁ)s Script Editor´‡°dONLNd
”ØÁªÈ)>
,+‡°dONLNd
‘Øͪ
7) an application pr˚@°dONLNd
ÊØ
7ª
f)M
ovided by ∏‡°dONLNd
Ø
fª
±)/Apple Computera`°dONLNd
˛Ø
±ª
Δ)K, Inc.ÅÄ°dONLNdØ
Δª
»)
,
Ä°dONLNdØ
…ª
fl) that °dONLNdºl»¥(≈lallows users to rîÄ°dONLNdº¥»Δ)Hecor‡°dONLNd º«»
Ú)Gd, edit, and execute scripts. The client application could also be any °dONLNdg…l’
(“l'other application that uses the standar¨ °dONLNdé…
’
)©d scripting component r†°dONLNd•…
Ä’
Ô)koutines to execute scripts‡°dONLNdø…
Ô’
Ù)o. °dONLNd¡÷l‚¨(fllScript Editor u!°dONLNd–÷≠‚
‹)ABses the Component Manager to open a connection with the scripting °dONLNd„lÔº(Ïlcomponent that crÎÄ°dONLNd#„ºÔ
A)Peated the script to be executedk °dONLNdB„
BÔ
G)Ü. 


*
"
¯4
*
"
¯"
*]

ˇ·ˇ‚7^
    °dONLNdE
l
ñ(
l
Figure 1-7°dONLNdP
Æ

`)B+How a scripting component executes a script


"lÄ
¯4
!k
"lò@@
˜@
˜
"l
bc¡¡?◊ˇ¯Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?ˆˇ¯Áˇ¸Ì?ˆˇ¯
Áˇ¸Ì?ˆˇ¯Áˇ¸Ì?ˆˇ¯ÁÁˇ¸Ì?ˆˇ¯
'Áˇ¸Ì?ˆˇ¯ÁÁˇ¸Ì?ˆˇ¯ «Áˇ¸Ì?ˆˇ¯@(áÁˇ¸Ì?ˆˇ¯ÄD˜Áˇ¸Ì?ˆˇ˘É.Áˇ¸Ì?ˆˇ˙
\Áˇ¸Ì?ıˇÇ∫Áˇ¸Ì?ˆˇ¸D    qÁˇ¸Ì?ˆˇ¸(áÁˇ¸Ì?ˆˇ¸0–Áˇ¸Ì?ˆˇ˙ ‡?Áˇ¸Ì?ˆˇ˙?Áˇ¸Ì?ˆˇ˘?Áˇ¸Ì?ˆˇ¯Ä8‡?Áˇ¸Ì?ˆˇ¯@ ^?Áˇ¸Ì?ˆˇ¯ AÊˇ¸Ì?ˆˇ¯Ä?Áˇ¸Ì?ˆˇ¯
Áˇ¸Ì?ˆˇ¯Áˇ¸Ì?ˆˇ¯
Áˇ¸Ì?ˆˇ¯Áˇ¸Ì?ˆˇ¯!Áˇ¸Ì?ˆˇ¯! Áˇ¸Ì?ˆˇ¯!@Áˇ¸Ì?ˆˇ¯ÄÁˇ¸Ìò@@Ä
˜@Ä
˜
bl
¢c?ˆˇ¯Áˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ìò@Ä¿
˜Ä¿
˜
¢l
‚c?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?‰ˇ¯˝˙ˇ¸Ì?‰ˇ¯˝˙ˇ¸Ì?Èˇ˝¯8˛˙ˇ¸Ì?ÈˇˇˇÄ¯D˛˛‡
ˇˇ¸Ì?ÈˇÄ¯Ç˛˛`
ˇˇ¸Ì?ÈˇÄ¯Å˛˛Ä
ˇˇ¸Ì?Èˇ    ˇ¸Ä¯áü‡˛
¡ˇˇ¸Ì?Èˇ    (ÑįO‡˛!ˇˇ¸Ì?Èˇ    ˇ¸Ä¯/f˛ˇˇ¸Ì?Èˇ    (Ñį
IJ …ˇˇ¸Ì?Èˇ    ˇ¸Ä¯@˛B•ˇˇ¸Ìò@¿

˜¿

˜
‚l"c?Èˇ    0į  ˛ D    Sˇˇ¸Ì?Èˇ    ¿
į@ê˛ à£ˇˇ¸Ì?Èˇ    Ç`¯ ÑH˛A Sˇˇ¸Ì?Èˇ    
ê¯@à§˛A@#ˇˇ¸Ì?Èˇ
¯A!D˛B@%ˇˇ¸Ì?Èˇ
‰¯Ç`§˛B ġˇ¸Ì?Èˇ!R¯Ç –D˛D Ä
ˇˇ¸Ì?Èˇ"©¯Ñ àH˛$!
ˇˇ¸Ì?ÈˇD—¯ÑAD8˛$A
ˇˇ¸Ì?Èˇ Ñ©¯àA¢˛A?
ˇˇ¸Ì?Èˇ à<ë¯HCQ˛G„
ˇˇ¸Ì?Èˇ! í¯HǮIJO„}ˇˇ¸Ì?Èˇ!@é¯ ÇT@˛
¯„˝ˇˇ¸Ì?Èˇ"įÇ* ˛¯„硡¸Ì?ÈˇÄ¯Ç˛=„硡¸Ì?Èˇ įÇ
ò˛:˜çˇˇ¸Ì?Èˇ įAd˛=Λˇˇ¸Ì?Èˇ į
A‰˛:˜≠ˇˇ¸Ì?Èˇ į¿ÅÑ˛}Λˇˇ¸Ì?Èˇ
 į@@å˛∫˜≠ˇˇ¸Ì?Èˇê@¯ Ä|˛}Λˇˇ¸Ì?ÈˇP@¯˛∫˜≠ˇˇ¸Ì?Èˇ1¿¯˛}Λˇˇ¸Ì?Èˇ¯˝˛Ôæ˘ˇˇ¸Ì?Èˇ˝
¯˝˙ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ìò@

@
˜

@
˜"lbc?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ìò@
@
Ä
˜
@
Ä
˜bl¢c?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì?◊ˇ¸Ì◊ˇ¸Ì¡¡¡¡¡¡¡¡¡¡¡¡

Ò«0»
àÇ    H»
òÇH»

Çp»

#t—ê»
!fê»
qò`»¡¡¡¡¡
¯∏˛

 ˚
˛


flê

˝
˙
˝
fl"âËŸ
uÌ+≠ºk(õ-∏M#GìÖÌ+ć! Y"Ñ
‚ï
!Qu&»*µuMVêßU…,
!Qufl!
K'‰$©&D»D•&I‰°ƒËZsí&fl!éD%*„Ki∞]HJìâ±ãs@û„Kfl!ãCér49"2Ip"J1y ˚tZ?9"2fl@¯@à@˜@fl@¯@à@˜@flį@p@˜@fl¡¡ò@
Ä
¿
˜
Ä
¿
˜¢l‚c8
éC
@@
¿ÄËê˝Ä‡@
ć@:H˝@į6D

ä@ÄÄ@Ä1¸@@Ä@@@Ä˝˜;7ƒıgG!L+[‚uÄÌ ÀJHÀ—l@-mdlåπ&¿[ÎC¢˘« [„eRíeË∂ ^≤;F^ã`˘;7•U    ®JQTUMEÜÅ4ïΩITí¥@V¶¨¥ïQS@çD•eQ+BPçEäÔR™IZ )´VMJ§ï†˘;7
©    'í·dòââtÅ%9%)í%$§@•"bí@âÖ)."JDêâéíJeíR I*R…ë)% ˘;7

*a÷ÇD˚” ÇM¢>R⁄˝µL#©    MØÛ§¡…K:ÛTΔ°…î∑~⁄¶“DÉì◊Ì™`˘;7âÙNõsN§íÑÈ#I)åë)"HIIE…¢Dëíàç≠"$ÑAíác$îë$"T¢“âI@˘Ù@ı ˆÑÏÙ@ı ˆÑÏÒ
ÈÑÏ¡¡
˛@Ä`0Ä@¿Ÿ§@˝íê$$@@Ÿ§èˆ^ãa”ííë\ÁTrg
Á
»®⁄
%òH§ï¢®é„©
T•†ùHït⁄
H∑â)%!·pE!0‚ô.âᪧ⁄l·—Ì™`r@e"X"≠h"I¡¢H⁄HæëICß∫ò¡ë√I∑6ÊéF›⁄ı˙˛@⁄ı˙˛@⁄ı˙˛@⁄¡¡¡¡¡¡¡¡¡¡¡¡¡¡
 
¿
Ã
 Äb
ÃbîàÄZ GïÖ≥ÕgzîÄ≠]…*’ÕíS8Å)IZròÕ
•†GRsD;Õ;8íåZ<$@Œ ˛… ˛… ˛…¡¡‡pÕ
 Õ
;Eê!x:≤>KŒ
ƒ ®"®êRET§Œ
$\pGp$†îNâ$Œ(u¿D@=0∂àΩHŒ»Z8˚∫) ‹áHàŒ˚»˚»¡¡¡
‡‡¿#ÄÓ‡Ä
֐
 @!D@)
÷
z¡± ˘6ADùb@)E˝óï∏ÿ
lìA¿“ïBöAyñ•@I )*@ÿò@
¿
Ú
˜
¿
Ú
˜‚lc
E¢B$îπ<íBà§ÆÄRY‚JJ8ÿ
'2¬ E5¢&Ç àÈ¿õpt{Tÿï§á»œ&fir$á—‹©Gà“[§R$pÿ˜
˛ “˜

@“Ù

Ä–¡¡ ¬?‡Ä
ÅÄŒ B@ÄB@Œa ÑQe≈`D@ŒbóJ"rÑääŃ@Œî¶\$ñxìÄ$@Œ
™êF‹ï$ÄŒ>”dñÈ    
ÀÕ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜
"l
bc
¡¡÷30Ì÷Ì ¬÷Ì÷Ì÷Ì ¬÷Ì ¬÷Ì÷Ì÷Ì ¬Ù
`ÂÌ
 ı@—ÙfwÊÌÙoJÊÌÙhJÊÌ
 ıgI—÷Ì ¬÷ÌÙ
@ÊÌÙ
ÊÌ ˆùL‹Œ“ı>SSÌ)ÁÌ ˆ&SQ-)“ıùN‰…ÁÌı
‰Ìı
‰Ì ¬÷Ì Ù–Ù

ÂÌ˛ˇ¿˙
ÂÌ˛ @˙‡ÁÌ 'ˇ‡˙
 “˛  ˙‡ÁÌ 3˛ ˙ ¿“˛ ˙@(ÄÁÌ˛ ˙ÄD˜ÊÌ˛ˇ†˚
É.ÊÌ  ˝
\—˛ˇ†˝Ç∫ÊÌ  ˝D    q—˛˛ ˛ˇ˝Ä(ÄÁÌ ˝D¿0–xÁÌê`˝à‡ ‡8ÁÌ ∞@˝`8“‡@¸¿
8ÁÌ @¿˝ˇÄÄ8‡8“¿
Ä˝@ ^8ÁÌˇˇ¸ A¯ÁÌÙÄ8ÁÌ 
¿ ˘

– @˙
ÂÌ 
ÜÓ‡˙

–˛i©@˙
ÂÌ(©@˙
!ÂÌ
«Æ ˙
! ÂÌ ˛˘
!@–˝˘
ÄÂÌò@@Ä
˜@Ä
˜
bl
¢c
 ıœ÷Ì÷Ì÷Ì ˜
¿ ≈—ˆ B@ÁÌ ˜
çÆ‚ÌÄ”ıs)CÂSÁ̈1)B%SÁ̈
œ.#›-ÁÌ ıœ
Ù‰Ì ¬÷Ì
Û?ÂÌ
Û)ÂÌ Ù!–
Û1ÂÌ Ù#–
Û!ÂÌ
Û%ÂÌ
Û)ÂÌ Ù!–
Û1ÂÌ Ù#–
Û!ÂÌ
Û%ÂÌ
Û)ÂÌ Ù!–
Û1ÂÌ Ù#–
Û!ÂÌ
Û%ÂÌ
Û)ÂÌ Ù!–
Û1ÂÌ     ı

„–Ù
Å¿ÊÌÛ
≈ÄÊÌ
ÛkÂÌ Ù6–
ÛÂÌ Ù–÷Ì÷Ì÷Ì ¬÷Ì
 ˘ˆˇ÷¯Ä˜Î̯ĘÎ̯ĘÎÌ ˘Ä˜÷¯Ä˜ÎÌ ˘Ä˜÷¯
Ä˝
 ˛Î̯
Ä2˝
&`˛ÎÌ¯Ä Õ8‹nvf„9∞ÎÌ ˘Ä!*•2˘%ØóÀ‡÷¯Ä#*•2â%©î  ÎÌ ˘Ä ∏“y'ìπ‡÷¯Ä ¸ÎÌ¯Ä ¸pÎ̯ĘÎÌò@Ä¿
˜Ä¿
˜
¢l
‚c
 ˘Ä˜÷¯Ä˜ÎÌ ˘Ä˜÷¯Ä˜Î̯ĘÎ̯ĘÎÌ
 ˘ˆˇ¯÷¯˜ˇ¯ÎÌ ¬÷Ì
Û?ÂÌ
Û)ÂÌ Ù!–
Û1ÂÌ Ù#–
Û!ÂÌ
Û%ÂÌ
Û)ÂÌ Ù!–
Û1ÂÌ Ù#–
Û!ÂÌ
Û%ÂÌ
Û)ÂÌ Ù!–
Û1ÂÌ Ù#–
Û!ÂÌ
Û%ÂÌ
Û)ÂÌ Ù!–
Û1ÂÌ Ù#–Ù
·¿ÊÌÛ
ƒ¿ÊÌÛ
iÄÙ˝0Ä˚Ì Ù3Û˝
 
ÂÛÛm-Üw33õé¸Ì ÙÛ¯øL¥˘¶XÁ‰à—    L¥I¶F¸̉xèw3∏ö\¸Ì¯˜ˇ¯ıD¯Ì ˘@˜ıD„¯@˜ÎÌ ˘@˜÷¯@˜Î̯@˜Î̯@˜ÎÌ ˘@˜÷¯@˜ÎÌ ˘@˜÷¯@˜Î̯@˜Î̯@˜ÎÌ ˘@˜÷¯@˜˜8ˆÌ ˘@˜˝ˇˇÄD˚
‡È¯@˜˝ÄÇ˚
`˛̯@˜˝ÄÅ˚
Ä˛Ì ¯@˜˝    ˇ¸Äáü‡˛
¿Ì ˘@˜˝    (ÑÄO‡˛ Í ¯@˜˝    ˇ¸Ä/f˛Ì ˘@˜˝    (ÑÄ
Ä »Í ¯@˜˝    ˇ¸Ä@B§Ìò@¿

˜¿

˜
‚l"c
$¯@
Ä˚˝    0Ä   D    RÌ$¯@Ä
˚
˝    ¿
Ä@ê à¢Ì& ˘@7sπ√6ég3∏˝    Ç` ÑHA RÍ'¯@
ÕI¶DÕIî˙P˝    
ê@à§A@"Ì& ˘@≈I¶DMIî¬P˝
A!DB@$Í'¯@=p•√µNd∫H˝
‰Ç`§B ÄÌ'¯@@@˛˝!RÇ –DD IJÌ&¯@@IJ˝"©Ñ àH$!˝Ì ˘@˜˝D—ÑAD8$AÈ ¯@˜˝ Ñ©àA¢˛A?˛Ì ˘@˜˝ à<ëHCQ˛G„È ¯@˜˝! íHÇ®ÄO„|Ì ¯@˜˝!@é ÇT@
¯„¸Ì ¯@˜˝"ÄÇ* ¯„åÌ ˘@˜˝IJ    Ç=„åÍ ¯@˜˝ IJÇ
ò:˜åÌ ˘@˜˝ IJ    Ad=Î‹Í ¯@˜˝ IJ
A‰:˜¨̯@˜˝ Ä˝¿ÅÑ}΋̯@˜˝
 Ä˝@@å∫˜¨Ì ˘@˜¸
ê@˝ Ä|}΋ͯ@˜¸
P@˝˝∫˜¨Ì ˘@˜¸
1¿˝˝}΋ͯ@˜¸˜Ôæ¯̯@˜Î̯@˜ÎÌ ˘@˜÷¯@˜ÎÌ ˘˜ˇ¸÷¯?˜ˇ¸ÎÌ÷Ì÷Ì ¬Û
Ĉ`¸‡¸p˛Ì Ù
¿ˆ˝

∞¸ÿÈÛ
`˜

ò˝
˝

å˛ÌÛ
0˜
˝
˝
˛ÌÛ
0˜
˝
˝
˛Ì Ù
88˜
˝
˝
ÈÛ
 ˜

˝
˝

˛Ì Ù
 ˜

˝
˝

ÈÛ
 ˜

˝
˝

˛ÌÛ
¸ ˜
à˝
?˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛Ìò@

@
˜

@
˜"lbc
 Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛÑ Ä˚
à˝
!˝
Ñ˛Ì!ÛÑ 
@
˛
à˝
!˝
Ñ˛Ì ÙÑ 
\ÈÉK;à˝
!˝
ÑÈ!ÛÑ 
“õ«Ø•¿à˝
!˝
Ñ˛Ì ÙÑ 2ö4%0à˝
!˝
ÑÈ!ÛÑ <È√£§‡à˝
!˝
Ñ˛ÌÛÑ Ä˚
à˝
!˝
Ñ˛ÌÛÑ Ä˚
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛Ì Ù
Ñ ˜
à˝
!˝
ÑÈÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
à˝
!˝
Ñ˛ÌÛ
Ñ ˜
¯˝
!¯˝
¸˛Ì Ù
ᇘ
Ä˝!¸
ÄÈÛш
Ä˝!¸
IJÌ Ùш
Ä˝!¸
ÄÈÛш
Ä˝!¸
IJÌÙ
ш
‡˝
·‡˝
p˛ÌÙĘ
``˝
¿¿˝
``˛Ì ı

Ɉ
0¿˝
aÄ˝
0¿ÈÛΔˆ
Ä˝3¸
IJÌ Ùlˆ¸¸ËÛ8ˆ¸¸˝Ì
ÛÂÌ÷Ì ¬÷Ì ¬÷Ì
¯·ˇÌ¯Ä‚Ì ˘Ä‚Î¯Ä‚Ì ˘Ä‚Î¯Ä‚Ì¯Ä‚Ì¯Ä‚Ìò@
@
Ä
˜
@
Ä
˜bl¢c
 ˘Ä˜@<ÛίĘ
@ 0ÛÌ ˘Ä˜
ÓX"[ª3s∞ˆÎ¯Ä˜    ô|=~R◊œß‡ˆ̯Ę    ô`!¢R‘ö ˆÌ¯Ä˜    Ó\=JìÀù‡ˆÌ ˘Äˆà˚ıίĈà˚8ıÌ ˘Ä‚Î¯Ä‚Ì¯Ä‚Ì¯Ä‚Ì ˘Ä‚Î¯Ä‚Ì
 ˘·ˇ¯Î¯‚ˇ¯Ì÷Ì÷Ì ¬÷Ì ¬÷Ì÷Ì÷Ì ¬÷Ì÷30Ì÷ÃÌ¡¡¡¡¡¡¡¡¡¡¡¡

Ò«0»
àÇ    H»
òÇH»

Çp»

#t—ê»
!fê»
qò`»¡¡¡¡¡
¯∏˛

 ˚
˛


flê

˝
˙
˝
fl"âËŸ
uÌ+≠ºk(õ-∏M#GìÖÌ+ć! Y"Ñ
‚ï
!Qu&»*µuMVêßU…,
!Qufl!
K'‰$©&D»D•&I‰°ƒËZsí&fl!éD%*„Ki∞]HJìâ±ãs@û„Kfl!ãCér49"2Ip"J1y ˚tZ?9"2fl@¯@à@˜@fl@¯@à@˜@flį@p@˜@fl¡¡ò@
Ä
¿
˜
Ä
¿
˜¢l‚c
8
éC
@@
¿ÄËê˝Ä‡@
ć@:H˝@į6D

ä@ÄÄ@Ä1¸@@Ä@@@Ä˝˜;7ƒıgG!L+[‚uÄÌ ÀJHÀ—l@-mdlåπ&¿[ÎC¢˘« [„eRíeË∂ ^≤;F^ã`˘;7•U    ®JQTUMEÜÅ4ïΩITí¥@V¶¨¥ïQS@çD•eQ+BPçEäÔR™IZ )´VMJ§ï†˘;7
©    'í·dòââtÅ%9%)í%$§@•"bí@âÖ)."JDêâéíJeíR I*R…ë)% ˘;7

*a÷ÇD˚” ÇM¢>R⁄˝µL#©    MØÛ§¡…K:ÛTΔ°…î∑~⁄¶“DÉì◊Ì™`˘;7âÙNõsN§íÑÈ#I)åë)"HIIE…¢Dëíàç≠"$ÑAíác$îë$"T¢“âI@˘Ù@ı ˆÑÏÙ@ı ˆÑÏÒ
ÈÑÏ¡¡
˛@Ä`0Ä@¿Ÿ§@˝íê$$@@Ÿ§èˆ^ãa”ííë\ÁTrg
Á
»®⁄
%òH§ï¢®é„©
T•†ùHït⁄
H∑â)%!·pE!0‚ô.âᪧ⁄l·—Ì™`r@e"X"≠h"I¡¢H⁄HæëICß∫ò¡ë√I∑6ÊéF›⁄ı˙˛@⁄ı˙˛@⁄ı˙˛@⁄¡¡¡¡¡¡¡¡¡¡¡¡¡¡
 
¿
Ã
 Äb
ÃbîàÄZ GïÖ≥ÕgzîÄ≠]…*’ÕíS8Å)IZròÕ
•†GRsD;Õ;8íåZ<$@Œ ˛… ˛… ˛…¡¡‡pÕ
 Õ
;Eê!x:≤>KŒ
ƒ ®"®êRET§Œ
$\pGp$†îNâ$Œ(u¿D@=0∂àΩHŒ»Z8˚∫) ‹áHàŒ˚»˚»¡¡¡
‡‡¿#ÄÓ‡Ä
֐
 @!D@)
÷
z¡± ˘6ADùb@)E˝óï∏ÿ
lìA¿“ïBöAyñ•@I )*@ÿò@
¿
Ú
˜
¿
Ú
˜‚lc

E¢B$îπ<íBà§ÆÄRY‚JJ8ÿ
'2¬ E5¢&Ç àÈ¿õpt{Tÿï§á»œ&fir$á—‹©Gà“[§R$pÿ˜
˛ “˜

@“Ù

Ä–¡¡ ¬?‡Ä
ÅÄŒ B@ÄB@Œa ÑQe≈`D@ŒbóJ"rÑääŃ@Œî¶\$ñxìÄ$@Œ
™êF‹ï$ÄŒ>”dñÈ    
ÀÕ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜lTc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜Tlîc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜îl‘c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜‘lc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜lTc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜Tlîc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜îl‘c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜‘lc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜lTc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜Tlîc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜îl‘c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜‘lc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜lTc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜Tlîc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜îl‘c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜‘lc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇCh@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@ä.Introduction to Interapplication Communication4⁄ä˙(‡äSupporting P).)AppleScript and Other Scripting Languages

, (‡1-15
ˇˇˇˇˇˇˇˇ4^4|lòÄ2^A|rMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^A|r^A|r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
^6|@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^6|@^6|@˜˜˜˜˜˜˜˜˜˜˜˜˜˙ˇˇ
˙ˇ
˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜
4Å4
w?òÄ
Å6
w@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""Å6
w@Å6
w@$˜
˙ˇ˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛
¸ˇ˛¸ˇ˝˚ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛
˙ˇ˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˛¸ˇˇ
ˇ˛ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˜˜˜˜
˙ˇ
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛˜˛˛ˇ˝
ˇˇˇ˛
ˇˇˇ˛    ˇˇˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
˙ˇ˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˝˛ˇ˛
˛ˇ˛ˇˇ    ˇ¸
ˇ    ˇ¸
ˇ
˛ˇ˛ˇˇ˜˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh¡(eäLike sound rH†°dONLNd\¬h⁄)8esourꇰdONLNd\⁄h
;)ces, scripts can be storfi@°dONLNd)\
;h)a/ed in applications and documents as well as in °dONLNdXiäuŒ(rädistinct script fiI`°dONLNdjiœu
R)Eles that can be manipulated fra`°dONLNdài
Ru
ê)Éom the Finderο°dONLNdïi
èu
”)=. Script Editor aÖ†°dONLNd¶i
‘u)Ellows users to °dONLNdµväÇfi(äexecute scripts storLJ°dONLNd…vfiLj)Ted in 
"°dONLNdœv˜Ç
)script fiE`°dONLNdÿv
Ç
!)"leô@°dONLNd⁄v
!Ç
%)
s    Ä°dONLNd€v
&Ç
()
.âÄ°dONLNd‹v
(Ç
6) Us¿°dONLNdflv
7Ç
“)%ers can also execute special script fiF°dONLNd
v
“Ç
˝)õles called 
°dONLNd
Éäè”(åäscript applicatio°dONLNd
!É‘èfi)Jnsö°dONLNd
#Éfiè‰)
 sW°dONLNd
%ÉÂè
)imply bdONLNd
,É
è
V)"y opening them fr…Ä°dONLNd
=É
Vè
j)Oom t’`°dONLNd
AÉ
jè
î)    he FinderS‡°dONLNd
JÉ
îè
ô)*. °dONLNd
Mïä°(ûäWDuring script execution, scripting components perform actions described in the script, °dONLNd
§¢äƵ*
using the å°dONLNd
Æ¢µÆ
;)+Apple Event Manager to send  °dONLNd
 ¢
<Æ
ø)áApple events when necessary °dONLNd
¢
æÆ
Ù)Ç. The server °dONLNd
ÚØäªÌ(∏äapplications shown in Y‡°dONLNdØÓª
)dFigur,†°dONLNdØ
ª
)e 1-7  °dONLNdØ
ª
>)     use the ÷‡°dONLNdØ
>ª)$,Apple Event Manager to examine the contents °dONLNdGºä»•(≈äof the »`°dONLNdNº•»˚)Apple events they rņ°dONLNdaº¸»
-)Weceive and  Ä°dONLNdlº
-»
8)1to `°dONLNdoº
9»
<)
r«`°dONLNdpº
<»
s)espond appr|°dONLNd{º
t»
õ)8    opriately6`°dONLNdѺ
õ»
†)'. ÿ°dONLNdܺ
ü»
¶)
A†°dONLNdáº
ß»
˚) server application °dONLNdõ…ä’Ø(“äalways r–Ä°dONLNd£…Ø’
)%esponds to the same ä`°dONLNd∑…
’
ã)\Apple event in the same way@°dONLNd“…
ã’
ì)Ä, r÷@°dONLNd’…
ì’
¶)egarÙ°dONLNdŸ…
¶’
)dless of whether the °dONLNdÓ÷ä‚
N(flä-event is sent by a scripting component or dirJ¿°dONLNd÷
O‚
Ã)≈ectly by a client application. °dONLNd;ËäÙê(Òä
Y@Ä°dONLNd<ËêÙ
&) ou can take advantage of the OSA≈`°dONLNd\Ë
%Ù
?)ï in thrW‡°dONLNdcË
@Ù
e)ee ways:,Zapf Dingbats°dONLNdl˛ä
è(
ä
n
°dONLNdn˚ñ
ú)
Y@Ä°dONLNdo˚ú
·)ou can make yo∞ °dONLNd}˚·

)Eur applicatio`°dONLNdä˚


")9n 
`¿°dONLNdå˚
"

Q)scriptable,ÿ°dONLNdó˚
Q

í)/ or capable of rzÄ°dONLNdß˚
ì

œ)Besponding to à@°dONLNd¥˚
œ
)<Apple events °dONLNd¡
ñ

+(
ñ"sent to it by a scripting componenG °dONLNd„

,

4)ñt. + °dONLNdÊ

4

æ)"An application is scriptable if it°dONLNd    
ñ
!õ(
ñ
n
°dONLNd
¢
"
)Responds to the appr¥‡°dONLNd


"
C)^opriate standaršdONLNd.

C
"
K)Cd `°dONLNd0

L
"
Ç)    Apple eventM °dONLNd;

Ç
"
ü)6s. See tÄ°dONLNdC

†
"
∑)he pr
†°dONLNdH

∑
"
˙)evious section, °dONLNdX
"¢
.
$(
+¢“Sending and Responding to h@°dONLNds
"
$
.
g)ÇApple Events.”°dONLNdÇ
3ñ
<õ(
:ñ
n
.°dONLNdÑ
1¢
=¨)PrR`°dONLNdÜ
1¨
=Ÿ)

ovides an Ù°dONLNdê
1ÿ
=
{),#Apple event terminology extension (,
CourierÙ°dONLNd≥
1
{
=
Å)£
'Ù°dONLNd¥
1
Å
=
ô)aeteÙ°dONLNd∏
1
ô
=
ü)
'Ù°dONLNdπ
1
ü
=
©)) rΔ`°dONLNdº
1
©
=
¿)
esourò¿°dONLNd¡
1
¿
=)ce that describes .
°dONLNd”
=¢
Iø(
F¢which Ù°dONLNdŸ
=ø
I
ß)3Apple events your application supports and the corr»¿°dONLNd
=
ß
I
ÿ)Ë
esponding .°dONLNd
I¢
U
ä(
R¢3human-language terminology for use in scripts. The °dONLNdI
I
ä
U
ê)Ë
'°dONLNdJ
I
ê
U
®)aete°dONLNdN
I
®
U
Æ)
'°dONLNdO
I
Æ
U
¥) rR`°dONLNdQ
I
¥
U
À)esour$¿°dONLNdV
I
À
U
˜)
ce allows .
°dONLNd`
U¢
a
.(
^¢scripting components to interprj °dONLNd
U
.
a
i)ået scripts corr@°dONLNdé
U
j
a
—)<ectly and send the appròÄ°dONLNd•
U
—
a
Ú)gopriate ¿°dONLNd≠
U
Û
a)"Apple °dONLNd≥
a¢
m
É(
j¢4events to your application during script execution. °dONLNdË
pñ
|˝(
yñBy executing scripts, us7@°dONLNd
p˛
|
à)h!ers of scriptable applications cad`°dONLNd!
p
à
|
ñ)än p∑‡°dONLNd$
p
ñ
|)erform almost any task that °dONLNd@
|ñ
à£(
Öñthe]`°dONLNdC
|§
àˇ)y would otherwise p—‡°dONLNdV
|ˇ
à
)[erforJ °dONLNd[
|

à
%)m b%¿°dONLNd^
|
&
à
˚)-y choosing menu commands, typing, and so on. °dONLNdã
àñ
î
˘(
ëñPUsers can also execute scripts to perform many tasks that might otherwise be dife¿°dONLNd€
à
˘
î
ˇ(
ë
˘
firÄ°dONLNd›
à
ˇ
î)cult °dONLNd‚
îñ
†

(
ùñto accomplish, especially rì°dONLNd˝
î


†
Î)t5epetitive or conditional tasks that involve multiple °dONLNd2
†ñ
¨Œ(
©ñapplications.°dONLNd@
µä
ºè(
ªä
n
°dONLNdB
≤ñ
æú)
Y@Ä°dONLNdC
≤ú
æ
")ou can make your application 
`¿°dONLNd`
≤
"
æ
R)Ü
recordable≤¿°dONLNdj
≤
R
æ
\)0
—≤¿°dONLNdk
≤
\
æ
—)
that is, capable of sending Ň°dONLNdá
≤
—
æ)uApple events °dONLNdî
æñ
 »(
«ñto itself in r§@°dONLNd¢
æ»
 )2Desponse to user actions such as choosing a menu command or changing °dONLNdÊ
 ñ
÷
(
”ñthe contents of a document. ñ@°dONLNd
 

÷
å)|After a user has turned on rΩÄ°dONLNd
 
å
÷
û)zecor1‡°dONLNd"
 
ü
÷
˙)ding for a particular °dONLNd8
֖
‚
h(
flñ.scripting component, the scripting component r‡°dONLNdf
÷
i
‚
ˆ)”!eceives copies of all subsequent °dONLNdá
‚ñ
Ó±(
ÎñApple˝Ä°dONLNdå
‚±
Ó≥)
 }Ä°dONLNdç
‚¥
ÓÍ)events and rπ‡°dONLNdô
‚Í
Ó¸)6ecor.@°dONLNdù
‚˝
Ó
á)!ds them in the form of a script. °dONLNdø
˜ä
˛è(
˝ä
n
°dONLNd¡
Ùñú)
Y@Ä°dONLNd¬
Ùú
ı)Nou can have your application manipulate and execute scripts with the aid of a °dONLNd    ñ¸(    ñscripting component. T+Ä°dONLNd    &¸
Ç)fo do so, your application must°dONLNd    Eñõ(ñ
n
°dONLNd    G¢¨)usƒ °dONLNd    I¨
æ)
:e the Component Manager to open a connection with the appr|@°dONLNd    É
ø(
øopriate componen¯†°dONLNd    ì)P
t°dONLNd    ï ñ)õ('ñ
n
°dONLNd    ó¢*¨)usƒ °dONLNd    ô¨*Â)
e the standarú†°dONLNd    ¶Â*
O)9d scripting component rÛ °dONLNd    Ω
O*
Å)joutines to rÔ`°dONLNd    …
Å*
ì)2ecorc¿°dONLNd    Õ
î*)d, edit, compile, save, load, °dONLNd    Î*¢6
1(3¢ or execute scripts when necessar6°dONLNd
*
26
7)ê
y°dONLNd
9ñE
«(BñFUsers of applications that execute scripts can modify the applicationsù`°dONLNd
S9
«E
…(B
«
’d†°dONLNd
T9
 E) behavior by °dONLNd
aEñQÁ(Nñediting the scripts.@ °dONLNd
uEËQ
à)R% For example, a user of an invoice prã¿°dONLNd
öE
àQ)†ogram might be able to write a °dONLNd
πQñ]
Ò(ZñOscript that checks and if necessary updates customer information in a separate °dONLNd]ñi
è*9database application each time the user posts an invoice.°dONLNdBnäzÍ(wäThe sections that folloG°dONLNdYnÎz
 )aw describe tü@°dONLNden
 z
C)5hese thrô†°dONLNdmn
Cz
–)#"ee kinds of scripting capabilitiesí°dONLNdèn
—z
)é in morZ@°dONLNdñn
Òz
¯) e °dONLNdò{äáÙ(Ñädetail. The chapter “Intr≠‡°dONLNd±{Ùá
ô)j&oduction to Scripting” in this book pr¥ °dONLNd◊{
ôá)•ovides an overview of the °dONLNdÒàäî(ëäQway scripting components work and how you can implement support for scripting in °dONLNdBïä°’*your application.ˇ%@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@l.Introduction to Interapplication Communication4⁄*˙
¯

(‡*1-16    )BSupporting P).)AppleScript and Other Scripting Languages4^*¿
¯

k*r
¯4l*r
¯ mlm
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\lk¨(glScriptable O˙°dONLNd\¨kı)@Applicationsˇˇˇˇˇˇ€r(g

1
°dONLNdrl~÷({lIf your application can rÓ@°dONLNd2r÷~
%)jespond to standarC°dONLNdCr
&~
.)Pd Ä`°dONLNdEr
.~
Í),Apple events sent by other applications, it °dONLNdqlãï(àl
can also r!Ä°dONLNd{ñãÌ)*espond to the same û`°dONLNdéÌã
À)W1Apple events sent by a scripting component. Befor@¿°dONLNdø
Ãã
”)fle °dONLNd¡ålòÊ(ïlexecuting a script that contr‡°dONLNdfiåÁò
Ï){;ols your application, a scripting component must associate °dONLNd
ôl•
g(¢l7the human-language terms used in the script with specifi6 °dONLNd
Qô
h•
n)¸c »°dONLNd
Sô
n•
Ú)Apple event codes supported °dONLNd
o¶l≤
8(Øl/by your application. Scriptable applications pr °dONLNd
û¶
9≤
Æ)Õovide this information in a߇°dONLNd
π¶
Æ≤
∂)un ö‡°dONLNd
ª¶
∂≤
Ó)Apple event .°dONLNd
«≥lø’(ºlterminology extension (,
Courier°dONLNd
fi≥’ø€)i
'°dONLNd
fl≥€øÛ)aete°dONLNd
„≥Ûø˘)
'°dONLNd
‰≥˘ø
)) rR`°dONLNd
Á≥
ø
)
esour$¿°dONLNd
Ï≥
ø
&)ce.$¿°dONLNd
Ô≥
&ø
()
 $¿°dONLNd
≥
(ø
*)
 $¿°dONLNd
Ò≥
*ø
,)
 °dONLNd
Û≈l—
a(Œl6Because scripting components can obtain information frR`°dONLNd)≈
a—
p)ıom R`°dONLNd,≈
p—
v)
'R`°dONLNd-≈
v—
é)aeteR`°dONLNd1≈
é—
î)
'R`°dONLNd2≈
î—
ö) r$¿°dONLNd4≈
ö—
±)esour˜ °dONLNd9≈
∞—
Ï)ces about the .
°dONLNdG“lfiÑ(€lnatur_‡°dONLNdL“Ñfi¢)e of dif@°dONLNdT“£fiØ)ferˇ¿°dONLNdW“Æfi˝)ent applications’ s’@°dONLNdj“˛fi
.)Pupport for Ë¿°dONLNdu“
.fi
d)0Apple event3İdONLNdē
efi
y)7s, a s-İdONLNdܓ
zfi
Ê)ingle script can describe °dONLNd†fllÎ
G(Ël/complex tasks performed cooperatively by severa¡`°dONLNdœfl
GÎ
Ñ)€l specialized a¡@°dONLNdfifl
ÖÎ
±)>
pplicationx °dONLNdËfl
≤Î
¿)-s. FD@°dONLNdÏfl
¡Î
˜)or example, °dONLNd¯Ïl¯À(ıla user can execute an Ù@°dONLNdÏÀ¯
)_AppleScript scripK†°dONLNdÏ
¯
")Nt tP`°dONLNd"Ï
"¯
W)    o locate all rµ¿°dONLNd0Ï
W¯
i)5ecor* °dONLNd4Ï
j¯
Ê)ds in a database with specifij@°dONLNdQÏ
ʯ
Ï)|c °dONLNdS˘l

d(
l;characteristics, update a series of charts based on those r¸Ä°dONLNdé˘
d

v)¯ecorp‡°dONLNdí˘
w

)ds, import the charts into a °dONLNdØ
l

V(
l2page-layout document, and send the document to a rî`°dONLNd·

V

ˆ)Í"emote computer on the network via °dONLNd
l
Ñ(
lelectrs@°dONLNd    
Ñ
±)onic mail. °dONLNd
%l
1
(
.l(When a user executes such a script, the ∫Ä°dONLNd=
%

1
Ò)Æ.AppleScript component attempts to perform the °dONLNdk
2l
>
9(
;l0actions the script describes, including sending !@°dONLNdõ
2
:
>
fi)Œ%Apple events to various applications °dONLNd¿
?l
K≤(
Hlwhen necessaryx@°dONLNdŒ
?±
Kº)E. TÆ°dONLNd—
?ª
K
ã)
,o map human-language terms used in the scripN¿°dONLNd˝
?
å
K
†)—t to tã`°dONLNd
?
†
K
æ)he corrC¿°dONLNd

?
ø
K
)
esponding °dONLNd
Ll
X
D(
Ul0Apple events supported by each application, the ∑‡°dONLNdD
L
D
X
È)ÿ#AppleScript component looks up the ˇˇÚD.°dONLNdg
Yl
e‚(
blterms in the applications’ ˇˇ÷ÃI°dONLNdÇ
Y„
eÈ)w
'I°dONLNdÉ
YÈ
e

)aeteI°dONLNdá
Y


e
)
'ˇˇÚDI°dONLNdà
Y

e
) r¥°dONLNdä
Y

e
$)esour‡°dONLNdè
Y
#
e
–)$ces. Each human-language term specifi©$°dONLNd¥
Y
—
e
˜)Æ    ed by an °dONLNdΩ
fl
r´(
olapplication’s °dONLNdÀ
f´
r±)?
'°dONLNdÃ
f±
r…)aete°dONLNd–
f…
rœ)
'°dONLNd—
fœ
r’) rR`°dONLNd”
f’
rÏ)esour$¿°dONLNdÿ
fÏ
r
#)ce has a corr˜ °dONLNdÂ
f
"
r
Q)6
esponding ò¿°dONLNdÔ
f
Q
r
§)/Apple event code. :`°dONLNd

f
§
r
—)S
After the .
°dONLNd
sl

    (
|l!AppleScript component has identifi °dONLNd-
s



')ûed the vÄ°dONLNd4
s
'

‡)*Apple event codes for the terms used in a °dONLNd^
Äl
å¨(
âlscript, it can crÓ`°dONLNdo
Ĩ
å˚)@eate and send the #‡°dONLNdÅ
ĸ
å
fi)P3Apple events that perform the actions described in °dONLNd¥
çl
ôy(
ñlthe]`°dONLNd∑
çz
ô|)
 ›`°dONLNd∏
ç|
ôó)script.°dONLNd¿
ül
´r(
®l
Tµ¿°dONLNd¡
üq
´|)o rp@°dONLNdƒ
ü}
´¥)espond appr$‡°dONLNdœ
üµ
´˙)8opriately to the ±‡°dONLNd‡
ü˙
´
})EApple events sent to it by the Ã`°dONLNdˇ
ü
}
´
Î)ÉAppleScript component, °dONLNd
¨l
∏
Ö(
µlAthe database application in this example must be able to locate r*@°dONLNdW
¨
Ü
∏
ò(
µ
Üecorû†°dONLNd[
¨
ò
∏
ÿ)ds with specifi∏†°dONLNdj
¨
ÿ
∏
fi)@c °dONLNdl
πl
≈
$(
¬l-characteristics so that it can identify and rtÄ°dONLNdô
π
$
≈
R)∏eturn the rÓ°dONLNd§
π
R
≈
ä).equested datd`°dONLNd∞
π
ã
≈
†)9a. ThVÄ°dONLNdµ
π
°
≈
¬)e other °dONLNdΩ
Δl
“
(
œl#applications involved must support ¨`°dONLNd‡
Δ

“
œ)†,Apple events that perform the other actions °dONLNd
”l
fl (
‹ldescribed in the scrip¸ °dONLNd"
” 
flœ)^t.°dONLNd%
Âl
Ò
V(
Ól7One line in such a script might be a statement like thi
¿°dONLNd\
Â
W
Ò
])Îs:.°dONLNd_
¸lr(l
c°dONLNd`
¸rÍ)opy Totals to chart °dONLNdt
¸Í)x
"°dONLNdu
¸
P)Summary of Sales°dONLNdÖ
¸
P
V)`
"°dONLNdÜ
¸
V
§) of document °dONLNdì
¸
§
™)N
"°dONLNdî
¸
™
Ï)Sales Chart°dONLNdü
¸
Ï
Ú)B
"°dONLNd°l ·(lIn this statement, the worR`°dONLNdª· È)ud R`°dONLNdΩÈ 
)TotalsR`°dONLNd√
 
Ú)$5 is a variable that has been set earlier in the same .
°dONLNd¯!l-
È(*lWscript to the value of the new data generated by a database application. The statement °dONLNd    O.l:õ*causes the ∫°dONLNd    Z.õ:
m)/-AppleScript component to send a Set Data eveni°dONLNd    á.
n:
y)”t u2Ä°dONLNd    ä.
z:
ã)pdaP`°dONLNd    ç.
ã:
¢)ting tû°dONLNd    ì.
¢:
È)he chart named °dONLNd    ¢;lG (Dl“Summary of Sales.” Ë¿°dONLNd    ∂; G‚)^FigurªÄ°dONLNd    ª;‚Gˆ)e 1-8Y°dONLNd    ¿;˜G
>) shows how the ç¿°dONLNd    œ;
>G
Ì)G$AppleScript component would execute °dONLNd    ÛHlT≤(Qlthis statement. (…¿°dONLNd
H≤T )FFigurúÄ°dONLNd
    H Tfi)e 1-6:°dONLNd
HflTÔ) on ć°dONLNd
HÔT
)page [¿°dONLNd
H
T
)1-12؆°dONLNd
H
T
+) sho≥Ä°dONLNd
H
+T
3)
w
Ä°dONLNd
 H
4T
?)    s a«Ä°dONLNd
#H
?T
A)
 GÄ°dONLNd
$H
BT
¬)database application that senò‡°dONLNd
AH
¬T
”)Äds aq†°dONLNd
EH
‘T
÷)
 Ò†°dONLNd
FH
÷T
˜)similar °dONLNd
NUlay(^lSetÀ¿°dONLNd
QUya{)
 K¿°dONLNd
RU|a®)    Data even÷@°dONLNd
[U®a≥),t d¥`°dONLNd
^U¥a∫)ira¿°dONLNd
`Uªa )ectlΔ`°dONLNd
dU aœ)
y9¿°dONLNd
eUœa—)
.π¿°dONLNd
fU—a÷)) °dONLNd
iglsr(pl
Tµ¿°dONLNd
jgqsó)    o interpr*¿°dONLNd
sgòs
G)'*et the terms in this script statement corr=Ä°dONLNd
ùg
Gs
[)ØectlyÄ°dONLNd
¢g
[s
p), the Ä°dONLNd
®g
ps
ı)AppleScript component must .°dONLNd
√tlÄ
l(}l9be able to look them up in the SurfCharter application’s °dONLNd
¸t
lÄ
r(}
l
'°dONLNd
˝t
rÄ
ä)aete°dONLNd
t
äÄ
ê)
'°dONLNdt
êÄ
ñ) rR`°dONLNdt
ñÄ
≠)esour$¿°dONLNd    t
≠Ä
ı)ce, which maps .
°dONLNdÅlçŒ(älthose terms to the corrR °dONLNd/Åœç
*)cesponding codes for Ï °dONLNdCÅ
*ç
Ì)[-Apple events, object classes, and so on used °dONLNdpélöâ(ólby the ¿°dONLNdwéäöÎ)Apple Event Manager@°dONLNdäéÎö
)a. The ‰†°dONLNdêé
ö
û)!AppleScript component can then cr7`°dONLNd±é
üö
Ó)ùeate and send the °dONLNd√õlßÌ(§lSet Data event to SurfCharterz °dONLNd‡õÌßÔ)Å
.ˇ|Í@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@ä.Introduction to Interapplication Communication4⁄ä˙(‡äSupporting P).)AppleScript and Other Scripting Languages

, (‡1-17
ˇˇˇˇˇˇˇˇ4^4|lòÄ2^A|rMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^A|r^A|r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
^6|@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^6|@^6|@˜˜˜˜˜˜˜˜˜˜˜˜˜˙ˇˇ
˙ˇ
˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜
4Å4
w?òÄ
Å6
w@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""Å6
w@Å6
w@$˜
˙ˇ˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛
¸ˇ˛¸ˇ˝˚ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛
˙ˇ˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˛¸ˇˇ
ˇ˛ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˜˜˜˜
˙ˇ
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛˜˛˛ˇ˝
ˇˇˇ˛
ˇˇˇ˛    ˇˇˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
˙ˇ˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˝˛ˇ˛
˛ˇ˛ˇˇ    ˇ¸
ˇ    ˇ¸
ˇ
˛ˇ˛ˇˇ˜˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh≥(eä    When it r‹ °dONLNd    \≥h
ª))=eceives the Set Data event, the SurfCharter application uses 0‡°dONLNdF\
ºh
Ã(e
ºthe /‡°dONLNdJ\
Ãh)Apple Event °dONLNdViäu≠(räManage`°dONLNd\iÆu∑)$r t‘`°dONLNd_i∑u
))    o determine what kind of ?†°dONLNdxi
*u
´)sApple event has been sent anp¿°dONLNdîi
´u
ÿ)Åd to pass tLJ°dONLNdüi
ÿu)-he event to °dONLNd´väÇæ(äSurfCharter§`°dONLNd∂vøÇ)5P’s handler for that event, which in turn locates the chart and changes its data °dONLNd
Éäèô(åäas r°dONLNd

Éöèƒ)    equested..°dONLNd
ïä°⁄(ûäThe chapter “IntrR`°dONLNd
%ï⁄°
»)P6oduction to Scripting” in this book describes how the ,
CourierR`°dONLNd
[ï
»°
Œ)Ó
'R`°dONLNd
\ï
Ρ
Ê)aeteR`°dONLNd
`ï
Ê°
Ï)
'R`°dONLNd
aï
Ï°
Ú) r$¿°dONLNd
cï
Ú°    )esour˜ °dONLNd
hï°)ce .
°dONLNd
k¢äÆ°(´äworkŒ@°dONLNd
o¢°Æß)s.ã@°dONLNd
q¢®Æ
&) The chapter “Apple Event T\°dONLNd
å¢
&Æ
z)~erminology Resour‡°dONLNd
ù¢
{Æ
Δ)Uces” describes ho«Ä°dONLNd
Æ¢
ΔÆ
Ì)Kw to defi»Ä°dONLNd
∑¢
ÌÆ
˙)'ne .°dONLNd
∫Øäª

(∏äterminology for use by the !†°dONLNd
’Ø

ª
ñ)wAppleScript component and how !†°dONLNd
ÛØ
ñª
©)ïto crÙ°dONLNd
¯Ø
®ª
À)eate an Ù°dONLNdØ
˻
—)#
'Ù°dONLNd
Ø
—ª
È)aeteÙ°dONLNdØ
Ȫ
Ô)
'Ù°dONLNdØ
Ôª
Ò)
 .
°dONLNdºä»ç(≈ä
rE°dONLNdºé»¶)esourç@°dONLNdº¶»±)ce.

ÍH˚4ÎH˚"ÎH]

ˇ·ˇ‚7^
    °dONLNd‡äÎ¥(Ëä
Figure 1-8°dONLNd‡ÃΓ)B
A0°dONLNd‡“Î
Ä), Set Data event sent during script execution

˙HÇ4˘F˙Gò@@
ˆ@
ˆ˙G
:=¡¡?…ˇ˙?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?˝ˇ‡¿“ˇÄ˚?˝ˇ‡ “ˇÄ˚?˝ˇ‡“ˇÄ˚?˝ˇ‡ü“ˇÄ˚?˝ˇ‡ ü“ˇÄ˚?˝ˇ‡@ ü“ˇÄ˚?˝ˇ‡Ä@“ˇÄ˚?˝ˇ·†.“ˇÄ˚?˝ˇ‚
‹“ˇÄ˚?˝ˇ‰∏“ˇÄ˚?˝ˇË    p“ˇÄ˚?˝ˇ˛Ë“ˇÄ˚?˝ˇÒ%ƒ“ˇÄ˚?˝ˇ†K¬“ˇÄ˚?˝ˇ¿WA—ˇÄ˚?˝ˇËÄ/Ä—ˇÄ˚?˝ˇËP—ˇÄ˚?˝ˇ‰|—ˇÄ˚?˝ˇ‚„Ä—ˇÄ˚?˝ˇ·Åx—ˇÄ˚?˝ˇ‡Ä
—ˇÄ˚?˝ˇ‡@—ˇÄ˚?˝ˇ‡ “ˇÄ˚?˝ˇ‡“ˇÄ˚?˝ˇ‡(“ˇÄ˚?˝ˇ‡H “ˇÄ˚?˝ˇ‡Ñ@“ˇÄ˚?˝ˇ‡ÑÄ“ˇÄ˚?˝ˇ‡Ö“ˇÄ˚ò@@Ä
ˆ@Ä
ˆ
:G
z=?˝ˇ‡F“ˇÄ˚?˝ˇ‡<“ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚ò@Ä¿
ˆÄ¿
ˆ
zG
∫=?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?fiˇ¯ÄÒˇÄ˚?fiˇ¯
ÄpÒˇÄ˚?fiˇ¯ÒˇÄ˚?fiˇ¯ÒˇÄ˚?fiˇ¯áÒˇÄ˚ò@¿

ˆ¿

ˆ
∫G
˙=?fiˇ¯@GÒˇÄ˚?fiˇ¯ Ä'ÒˇÄ˚?fiˇ¯AóÒˇÄ˚?fiˇ¯Å%OÒˇÄ˚?fiˇ¯Ç BèÒˇÄ˚?fiˇ˘ ÅOÒˇÄ˚?fiˇ˘AèÒˇÄ˚?fiˇ˘AóÒˇÄ˚?fiˇ˘ÇwÒˇÄ˚?fiˇ˘ÇÒˇÄ˚?fiˇ¯êÑÒˇÄ˚?fiˇ¯ë|ÒˇÄ˚?fiˇ¯A¸ÒˇÄ˚?fiˇ¯1åÒˇÄ˚?fiˇ¯?ç˜ÒˇÄ˚?fiˇ¯„è˜ÒˇÄ˚?fiˇ¯„é7ÒˇÄ˚?fiˇ¯˜é7ÒˇÄ˚?fiˇ¯Îfi7ÒˇÄ˚?fiˇ¯˜ØwÒˇÄ˚?fiˇ¯Îfi∑ÒˇÄ˚?fiˇ¯˜ØwÒˇÄ˚?fiˇ¯
Îfi∑ÒˇÄ˚?fiˇ¯˜ØwÒˇÄ˚?fiˇ¯
Îfi∑ÒˇÄ˚?fiˇ¯˜ØwÒˇÄ˚?fiˇ¯æ˚ÁÒˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚ò@

@
ˆ

@
ˆ
˙G:=?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚ò@
@
Ä
ˆ
@
Ä
ˆ:Gz=?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚ò@
Ä
¿
ˆ
Ä
¿
ˆzG∫=?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚?…ˇÄ˚…ˇÄ˚¡¡¡¡¡¡¡¡¡¡¡¡
é8`1Ä»
DêJ@»
ƒÄä@»
§pâ¿»
    †àÄ»
#0îÄ»    à|¿c«¡¡¡¡¡!¿0ÄÄÄ¿˛ÄÄÄflÄpHÇ@ÄÄ@¸Äfi"OF»HE≈•æ∑¡—∑gévï¡4çì`‡"R… pñJ䙑!ZÇ≤E©®∫ÇùW(©†‡"íY8'ê    ºS9<òìñI)    °qI ‡"Ãr  ê    ¶üû!Q<'Öúéfq•Ñ-Ÿ“`‡"úZp`3Üè(9Â÷äNëÌ—q"@‡"Ô ⁄"Ô ⁄Ô ⁄¡¡9pp0 @Äp˛àà
–@8˛$˜5  P 
à¸ÄÄ˛Äƒ¸ ˜:6'®;:9
aZfl¨nVZRF^ãb
kk#de…6flZ»∂9fl*îì/E±öıë⁄2Ù[¯:6*®MBR䢙j,4    §®ΩÍJ§ï¢µ5e§™äöj%+*âZÑj,WzïRJ—
MZ≤jU$≠¯:6›HI<ó$ƒLK§    )…)Lë)%"•%-)íL)IqR$ÑLtíS(îíëIRñLâI)¯:6QPì¥'fiûP¨mÚñ◊Ì™aHH:mù&ûJY◊ö¶5ûHÙ•ªˆ’0éí$ûømS¯:6O†“t€öu$î'IHÒLdâI@‚JJ.Hï$åîDmi$"î8£$§â q•îJHí¯ı˛
Ĉ
ˆ
 Ïı˛
Ĉ
ˆ
 ÏÒ
ÄÍ
 Ï¡¡$Ä0Ä@!Ä√ÿ  ˝A@Ä
$§ÿ$≤Ù[úêÉ
Á:£ê–$ƒW8E@⁄    ,¬E$≠•@%H
•(p„ƒÍ@´†⁄
EºII)Ä?flâá…p@DL8%› ⁄gèmSí    ¡k@aHñ-@⁄EÙäHí=–ÁéMπ∞Ê0dr6ÔÄ⁄ı˙ÄŸı˙ÄŸı˙ÄŸò@
¿
Ú
ˆ
¿
Ú
ˆ∫GÏ=¡¡¡¡¡¡¡¡¡¡¡¡¡¡

‡pÃ

 çD÷R<¨-òÕ;‘§jÓIPF®Õíôƒ    JJ”êD¿Õ•-:êìö âÿÕÿ»·ƒîb—‡…"Õ
!˝Ä…
!˝Ä…
!˝Ä…¡¡ÄÄ– ÕÄ
˛Ä@ Õ    ⁄,ÅÄ[¡’ëÚXŒ&UA@§Çí*• Œ    "„Ç;Å%¢tI ŒCÆ"
ÈÖ¥EÍ@ŒB—«›—I‰:D@Œ˚ »˚ »¡¡¡ê@
p¸Ä÷Äê    @
 
HÄ÷£÷ÕéW…≤$Î
J/Ϻ≠¿ÿdöΔõ*NPëIR◊
-
$•…‰íE%tíœRQ¿ÿ    9ñ)≠i4GHF€É£⁄†@ÿ≠$>Fy6Ûë$>éÂJ<Fí›"ë#Äÿ˜
Ä“˜
Ä“Ùœ¡¡ò@@
ˆ@
ˆ˙G
:=
¡¡»3˙…
˙  
˙»Ä˚…
˙»Ä˚  
˙…
˙  
˙»Ä˚…
˙˚
@–Ä˚ ¸3“
˙˚!MŒ“
˙ ¸!_$¡ÄÒ
˙˚#Q$Óp˙
¸ˇÄÒÄ˚˚O"ˇflÄ˚˛
ˇÄÛ
˙"Èˇ¸¸
?¿˝ˇ˝

ˇ˝
ˇ˛˛Ä˚' Ï
ˇ¸˝
‡˛
‡¸

ˇ˛

¯?ġ
˙ Ρ˙?¯˙
ˇ
‡‡

˙& ¸ÄÙÄ˙
¯˛¯
ˇ˛
?˛
Ä
˙˚ÙĢˇÄ˜

˘
ÄÄ˚¸7:ôπ∏ıį@Ï
Ä
˙¸|¶ß⁄dıÄ‚
ÄÄ˚ ˝L¶¢Zdˆ
`Ä‚
Ä
˙¸?:ù…§ıÄ‚
Ä
˙ ˝
 ÙÄ‚
Ä
˙¸
 ÚÄ‚
ÄÄ˚ÌÄÄ‚
Ä
˙ί‚
Ä˚ Ô·
 
˙Î0·
`
˙ ˛`·
‡
˙˚
¿Û@·¿Ä˚˚
 ˜@˛¿‚
Ä
˙˚
Ù

Ä‚ÄÄ˚ ¸Ä˙˛
·
˙˚ Ä˝ˇ¯˝·
˙ ¸@ Ä˝    IJ·
˙˚Ä@¸ˇÏ˝·Ä˚¸
†.¸˝
Ä‚
˙*¸
‹¸ˇƒ˝Ä¿@
¸
Û
ÄÄ˚0 ˝∏¸¸ÄÄ@@8!˘
Ä
˙0¸    p˛Ù¸Ä
Á@    Áà√»ÛF€z.#~;e˜
Ä
˙2 ˝Ë˛¸Äàà@íHD\A"H2L"    qàEĘ
Ä
˙0¸%ƒˇˇ¿¸Äüà@$íHD$I"HäH")ë    }ˆ
ÄÄ˚0¸†K¬DD@Ù¸Äc?„øÛfi7‹ÏÒ˛y›˚Δ¿˜
Ä
˙ ¸¿WA‡8à࿸ĸÇË
ÄÄ˚" ˝Ä/ć`@ˇƒ¸Ä˝

«Ë
Ä
˙¸P‡1@˛¸Ä‚
Ä
˙+ ˝|‡ˇˇ¿¥¸Ä¯`˛˜`˝
Ä
˙3¸„ć˛ú¸Ä˚> @
(‡¸
ÄÄ
ÄÄ˚7¸
Åx‡
ÿ¸Ä˛˜=∞*Áà!¿ÛÄ{Ñ€¿)ÔDo`9‡ B8rû
Ä
˙7˚
Ä
‡
ò0¸#Ä
í†    #D@äNa…VÆ1@DÄ‚D¿
ÄÄ˚8 ¸@‡˛
`¸"Ä
í†    d ¿L@ÇRA )V≤!@DÄE"|0
Ä
˙3˚
 ˚ˇ¿¸Ä˛˜@·ûˇÄ3Äo¿«÷ØxÄ9‡xˇô‡
Ä
˙ ¸
ÛÄ˝
@ÒĢ
Ä
˙#˚
(˚8
ĽĽ
9¿Ú
Ģ
ÄÄ˚˚
H ˚D¸Ä‚
Ä
˙$˚
Ñ@˚1µ‹¸Ä¸
0˙Ù
ÄÄ˚+ ¸
ÑÄ˚e(¸Ä¸
@˝    @8y
˜
Ä
˙+˚Ö˙F%(˝Ä˝„˜”ºAp‡âƒo≈˜
Ä
˙ò@@Ä
ˆ@Ä
ˆ
:G
z=
+ ¸F˙9ƒ¸Ä˝"@#R¨R@3ÑâÄÅ.1ˆ
Ä
˙)˚<˘
˚Ä˝"@'Ø“Håѯ`â2! ˜
ÄÄ˚&Ú

˝Ä˝„œ©ª0Ûfl3¿søx¿˜
Ä
˙
˝Ä‚
ÄÄ˚ ÏÄ‚
Ä
˙ÎÄ‚
Ä
˙ 0˛Ä√Ë
Ä
˙ÎÄAË
ÄÄ˚˝
¿ ΔÙÄÔAË
Ä
˙˝ B@ıÄ
¢"AË
ÄÄ˚" ˛
çÆ‚˘Ä˙˛Ä
Ù¶æAË
Ä
˙¸s)CÊeı¯n€˜¿È
Ä
˙ ˛1)B&eıx‚
Ä
˙˝
œ.#fi9ı0‚
ÄÄ˚˚ı  ‚
Ä
˙˚Ú`‚
Ä˚ Ï¿·
 
˙ÓÄ·
`
˙ Ô
Ä·
‡
˙χ¿Ä˚˙¸Ù·
Ä
˙˙åı
@·ÄÄ˚ ˚ÑÙ
Ä‚
˙˙îÙ
Ä‚
˙ ˚§ÛÄ‚
˙˙ÑıÄ‚Ä˚˙ƒÛÄ‚
˙˙åÛÄ‚
ÄÄ˚ ˚ÑÛÄ‚
Ä
˙˙îÙ
¿Ä‚
Ä
˙ ˚§ÛÄ‚
Ä
˙˙ÑÛÄ‚
ÄÄ˚˙ƒÛÄ‚
Ä
˙˙åÙ
ÄÚÚ
ÄÄ˚ ˚ÑÛÄÛˇ¿ı¯
Ä
˙˙îÛÄÙ
ˇflˇÄˆˇˇ·Ä
˙% ˚§Ûĸ`˙?¯?ˇ˚p˛¯ˇÄ
˙(˙ÑÛÄ˝
ˇ˚
ˇ˛
ˇ¸˝ˇÄÄÄÄ˚)˙ƒÛIJˇˇ¸
‡˛
ˇ¯˛fl¸¸˝
˙(˙åÛIJˇ¸ˇ˝
˛¸
ˇ‡˛ˇ‡¿¸Ä˚) ˚ÑÛÄ?ˇ¯
ˇ¿˚ˇ¿ˇ¸¸
˙&˚
óÛġ¿˛ˇÄ?¯˘?ˇ?Ä?¿¸
˙  ¸
#ÛÄ
ˇ˝¯ˇ˜
¸˜
˙˚

ÜÛIJ˚ˇˇ˜

‡ˆÄ˚˙ÃÛüˇÄ˚
˛Í
˙˙xÛ
ˇ‡˘¿ÈÄ˚ ˚0Ûx‡
˙…
˙  
˙»Ä˚
ˆˇ‡◊
˙
ˆ0÷Ä˚
 ˆ0◊
˙
ˆ0◊
˙
 ˆ0◊
˙
ˆ0÷Ä˚
ˆ0◊
˙
ˆ0÷Ä˚ ¿˝!˝0◊
˙ ˛
3˝0◊
˙ —ΔÊw3g1ŸÄ0◊
˙    ©)üJ-Ù˙}0÷Ä˚)©)òJ-î a0◊
˙
Δ©ΔóI)tπ›0÷Ä˚ò@Ä¿
ˆÄ¿
ˆ
zG
∫=
 
˚@0◊
˙
¸Ä0◊
˙
 ˆ0◊
˙
ˆ0÷Ä˚
ˆ0◊
˙
ˆ0÷Ä˚
 ˆ0◊
˙
ˆ0◊
˙
 ˆˇ◊
˙

ˆˇ÷Ä˚…
˙»Ä˚  
˙…
˙ ˚¸—
˙
˙Ñ–Ä˚
˙ƒ—
˙
˙å–Ä˚ ˚Ñ—
˙
˙î—
˙ ˚§—
˙
˙Ñ–Ä˚
˙ƒ—
˙
˙å–Ä˚ ˚Ñ—
˙
˙î—
˙ ˚§Ù·
˙˙ÑÙ
ĉÄ˚˙ƒÙΩÔဪ¿Â
˙˙åÙ∑øœˇ˝Ä‰Ä˚ ˚ÑÙ˜æv=ÄÂ
˙˙îÙ˝Ô«„˝¿Â
˙ ˚§Û
1Ä·
˙˙ÑÛ
1ćÄ˚
˙ƒ—
˙
˙å–Ä˚ ˚ѯ
ıˇ‡Ë
˙˚
ó¯
ı0Ë
˙ ¸
#¯
ı"0Ë
˙˚

ܯ
ı0ÁÄ˚˙ï
ı0˚Ô
˙˙x¯
ıà∞˚"ÓÄ˚! ˚0¯
˝<¸0˚ŒYÄÚ
˙
˝36˝0˚È}Ò
˙ Ò
˝">7ˇ‚˛"0˚#    °Ò
˙#
ˆˇ‡˛
˝˛6˝‡˛0˚ÈÄ˚
ˆ0˛
˝3Δ7ø`˛0Ë
˙
ˆ0˛
˝àûˇºˇË˛à∞ÁÄ˚
 ˆ0˛
ı0Ë
˙
ˆ0˛
ı0˙
†Ò
˙
 ˆ0˛
ı"0˙
ÄÒ
˙
ˆ0˛
ıˇ¸Œ¶nnÒÄ˚
ˆ0˛
ı0¸)©ˆôÚ
˙
ˆ0˛
ı0¸)®ñôÒÄ˚$
 ˛Ä
˝0˛
ı0¸ŒßriÚ
˙"    
@˛0˛
ı0¸

Ô
˙"     
NÈåmÁ˛0˛
ı0¸

Ô
˙(    
…õ√ôí˛0
˛2˝˛0ÍÄ˚)    )öâí˛0
˛ ˛0Î
˙/    .ÈŒy·˛0˛ˇ
˛Éçªç°ú˛0ˇ˝Ä˛
ÄÄ˚/
 ˛ÄIJ0Ä
Å˛Ç__S‰˛    0@¿
ÄpÒ
˙/
˛ÄIJ0Ä¡˛äSSR$˛    0@`Ò
˙'
 ˆ0Äa˛rO
OQ‹˛    0@`Ò
˙
ˆ0Ä¡ı
0@¿ÄÒÄ˚ò@¿

ˆ¿

ˆ
∫G
˙=
#
˙˛0ˇˇ˝Åı
0ˇ˝Ä@@Ú
˙'
˛f—ΔÊw˛0
ı0˛ Ä ÒÄ˚/
 ˛ô©)üJ˛0

‡˝'@0˛AêÚ
˙/
˛â©)òJ˛0
˝HÇÄ0˛Å%HÚ
˙-
 ˛v©ΔóI˛0˛
…i°¥åÊ2g0˚Ç BàÚ
˙*
˝
˚0˛
9US‰íA˙¸0¸
 ÅHÒÄ˚*
˝
˚0˛

URbíH É0¸
AàÚ
˙&
ˆ0˛
ÁUQ„G:~0¸
AêÒÄ˚!
 ˆ0˛
¸˚0¸
ÇpÚ
˙
ˆ0˛
¸˚0¸
Ç
˙
 ˆ0˛
ı0˚
êÑ
˙
ˆ0˛
˝Ñ˙0˚ë|Ä˚$
ˆ0˛
˛

˛˛0˚A¸Ò
˙$
ˆˇ˛
˛3úÕ-‹˛0˚1åÄ˚%
 
ˆˇ˛
˛I%3*Ω(˛0˚?çÚ
˙
˛I%1*°(˛0˚„èÚ
˙  Ò
˛1ŒÍù$˛0˚„é0Ú
˙
ı0˚˜é0ÒÄ˚˙ ¯
ı0˚Îfi0Ú
˙˙0¯
ı0˚˜ØpÒÄ˚$ ˚0¯    

x4˛0˚Îfi∞Ú
˙"˙0¯    

DÃ0˛0˚˜ØpÚ
˙$ ˚0¯
˛0”8áp˛0˚
Îfi∞Ú
˙"˙p¯
˛˜‡Ñæ ˛0˚˜ØpÒÄ˚"˙x¯
˛E4å¶ ˛0˚
Îfi∞Ú
˙"˙x¯
˛8Ûtû˛0˚˜ØpÒÄ˚ ˚x¯
ı0˚æ˚‡Ú
˙˙x¯
ı0Ë
˙ ˚¯¯
ı0Ë
˙˙¸¯
ı0ÁÄ˚˙¸¯
ı0Ë
˙˙¯
ı0ÁÄ˚ ˚¯
ı0¸8≤
˙˙¯
ıˇ¸D
  Ú
˙ ˚¯
ı0¸1;Éô¸¿Û
˙˙¯
ı0¸1Ç}>ÄÚÄ˚˙¯
ı0¸E1äe0ÄÛ
˙˙¯
ı0¸8Òr]ÄÚÄ˚ ˚¯
ı0Ë
˙˙¯
ı0Ë
˙ ˚¯
ı0Ë
˙˙¯
c0
Ï`±Äg0ÁÄ˚˙¯
î»2êJ@ò0Ë
˙˙¯
»RêJ@0ÁÄ˚" ˚¯
$»å` @a0Ò˙ˇ
‡
˙#˙¯
î»íê @â0Ùˇ‡@˙
0
˙* ˚¯
c0å`1Äˆ0¢ı" {Ó`@Ä
˙ ˙¯
ı0Äı z.fYÃÃflKÄ˚˙¯
ı0Äı z.FYHÃèK
˙#˙¯
ı
0˚àø˚à†z.fYÃÃè{Ä˚& ˚¯
ı0ĸ
 ĸ z.fYÃÃèC
˙#˙¯
ı0ĸ
1ĸ {Ó˝
˙! ˚¯
ı0¢˚"¢¸" @˙
0
˙!˙¯
ı0ĸ
 ĸ ˙ˇÄ˚!˙¯
ı0ĸ
$ĸ @˚0
˙ ˙¯
ı
0˚à®˚à†@˚∞Ä˚# ˚¯
ı0ĸ
 ĸ @˚
˙$˙¯
ı0ĸ
1ĸ Aê
˙% ˚¯
ıˇ¢˚"¢¸" BP∞
˙#˙˜ıˇĸ
 ĸ B∏l“Ã0Ä˚˙Èĸ
$ĸ BUËô˚‹
˙˙È˚à®˚à†AîËiö¯0Ä˚ ˚Èĸ
 ĸ @˚0
˙˙Èĸ
1ĸ @˚0
˙ò@

@
ˆ

@
ˆ
˙G:=
 ˚È¢˚"¢¸" B ˛0
˙˙Èĸ
 ĸ B 0Ä˚˙Èĸ
$ĸ C©€jq6@0
˙˙È˚à®˚à†Bi4™ìƇ0Ä˚  ˚Èĸ
 ĸ Cë”fqßp0
˙˙Èĸ
1ĸ @¸0
˙ ˚È¢˚"¢¸" @!¸0
˙˙Èĸ
 ĸ @˚0Ä˚˙Èĸ
$ĸ @˚0
˙˙È˚à®˚à†@˚0Ä˚ ˚Èĸ
 ĸ @˚0
˙˙Èĸ
1ĸ @˚0
˙ ˚È¢˚"¢¸" @˚0
˙˙Èĸ
 ĸ @˚0Ä˚˙Èĸ
$ĸ @˚0
˙˙È˚à®˚à†@˚0Ä˚ ˚Èĸ
 ĸ @˚0
˙˙Èĸ
1ĸ @˚0
˙ ˚È¢˚"¢¸" @˚0
˙˙Èĸ
 ĸ @˚0Ä˚˙Èĸ
$ĸ @˚0
˙˙È˚à
Ë˸à†@˚0Ä˚ ˚Èĸ
¿`¸ @˚0
˙˙Èĸ
q¿¸ @˝`0
˙  ˚È¢¸"
3¢¸" @N¥ŒÜ`0
˙˙Èĸ˚ @Mjjâ@0Ä˚˙Èĸ˚ @
Mj©â@0
˙˙ÈÙà†@=ji@0Ä˚ ˚ÈÄı @˛
0
˙˙ÈÄı @˛0
˙ ˚È¢ı" @˚0
˙˙ÈĢˇÄ @‚˛0Ä˚˙ÈĢ¿ @
F0
˙˙Èààê˘»à†@Œ®0Ä˚ ˚ÈĢ¿ @6‰0
˙˙ÈĢ¿ @
ŒN0
˙ ˚È¢"0˘‚" @˚0
˙˙ÈĢ¿ @˚0Ä˚˙ÈĢ¿ @˚0
˙˙Èààê˘»à†@˚0Ä˚! ˚ÈÄ
¿IJ¿ @˚0
˙"˙ÈÄ B@Ä¿ @9 0
˙$ ˚È¢"0
Ü‚Y‚" @?Ä
–0
˙#˙ÈÄoB|¯¿ @Δ`Ó∞0Ä˚"˙ÈÄ(Bd»¿ @)ë˜|H0
˙#˙Èààê
«#úx»à†0@iìúÃ∞0Ä˚ ˚ÈĢ¿ 8@íº0
˙˙ÈĢœˇˇ¸@Êgfi0
˙ ˚È¢"0˘Í""&@/20
˙#˙ÈIJ»@Ô0Ä˚"˙ÈIJàÃDDG@ˇw0
˙#˙Èààê
•ùŒn<ûààé@ˇ0Ä˚$ ˚ÈÄ◊“â˘MËœˇˇÏ@#0
˙"˙ÈÄâôM¿ 8@0
˙$ ˚È¢"0
—“Iy<Ë‚" 0@
"0
˙˙ÈĢ¿  @é0Ä˚˙ÈĢ¿ @4D0
˙˙Èààê˘»à†@1®å,p0Ä˚ ˚ÈĢ¿ @»‚8R@0
˙˙ÈĢ¿ @»q‡6`0
˙ ˚È¢"0˘‚" @»ÄH0
˙˙ÈĢ¿ @>`Ä˚˙ÈĢ¿ @˚∞
˙˙Èààê˘»à†@˚∞Ä˚ò@
@
Ä
ˆ
@
Ä
ˆ:Gz=
 ˚ÈĢ¿ @˚
˙˙ÈĢˇ¿ @˚∞
˙ ˚È¢"/˘ˇ‚" @˚0
˙˙ÈÄı @˚0Ä˚˙ÈÄı ˙ˇ

˙˙ÈÙà†@˚0Ä˚ ˚ÈÄı @˚∞
˙˙ÈÄı @˚∞
˙ ˚È¢ı" @˚∞
˙˙ÈÄı @˚∞Ä˚˙ÈÄı @˚∞
˙˙ÈÙà†˙ˇÄ˚ ˚ÈÄı ?˙ˇ

˙˙ÈĢˇÄ ˜
˙ ˚È¢"8˘‚" ˜
˙˙ÈĢ@ ˆÄ˚˙ÈÄ0˘@ ˜
˙˙Èàà†˘Hà†ˆÄ˚ ˚ÈÄ ˘@ ˜
˙˙ÈÄ ˘@ ˜
˙ ˚È¢" ˘b" ˜
˙˙ÈÄ ˘@ ˆÄ˚˙ÈÄ ˘@ ˜
˙˙Èàà†˘Hà†ˆÄ˚ ˚ÈÄ ˘@ ˜
˙˙ÈÄ ÄÄ˝@ ˜
˙ ˚È¢" Ç9ÁfvNfb" ˜
˙˙Áˇ‡DàÄO…Lü@ ˆÄ˚·Ä     |üÄH9Là@ ˜
˙·àà†òcGÊ<wHà†ˆÄ˚ ‚Ä ˘@ ˜
˙·Ä ˘@ ˜
˙$ ˘
˝
¯¢" ˘b" ˜
˙'¯Ä 
˝˝Ä ˘@ ˆÄ˚)¯ªìñÁ39ú}éNÜ·7LÊ;mÄ ˘@ ˜
˙)¯¶Wû_íLÀ3    MOó|¶_/ ∞àà†˘Hà†ˆÄ˚+ ˘fThíD 3    MIëL¶S(JåÄ0˘@ ˜
˙)¯{ìéGë;9¯-    =Gë<ùŒÁ ∏Ģ@ ˜
˙ ¯"Ù ¸¢"0˘‚" ˜
˙˜"Ù8
¿¸Ä˙
Ä ˆÄ˚·Ä˘ˇ ˜
˙·Ùà†ˆÄ˚ ‚Äı ˜
˙·Äı ˜
˙ ‚¢ı" ˜
˙·Äı ˆÄ˚·Äı ˜
˙·Ùà†ˆÄ˚ ‚Äı ˜
˙·Äı ˜
˙ ‚¢ı" ˜
˙·Äı ˆÄ˚·Äı ˜
˙·Ùà†ˆÄ˚ ‚Äı ˜
˙·Äı ˜
˙ ‚Ùˇ‡˜
˙»Ä˚…
˙»Ä˚  
˙…
˙  
˙»Ä˚ò@
Ä
¿
ˆ
Ä
¿
ˆzG∫=
…
˙»Ä˚  
˙…
˙»3˙…ÃÄ˚¡¡¡¡¡¡¡¡¡¡¡¡
é8`1Ä»
DêJ@»
ƒÄä@»
§pâ¿»
    †àÄ»
#0îÄ»    à|¿c«¡¡¡¡¡!¿0ÄÄÄ¿˛ÄÄÄflÄpHÇ@ÄÄ@¸Äfi"OF»HE≈•æ∑¡—∑gévï¡4çì`‡"R… pñJ䙑!ZÇ≤E©®∫ÇùW(©†‡"íY8'ê    ºS9<òìñI)    °qI ‡"Ãr  ê    ¶üû!Q<'Öúéfq•Ñ-Ÿ“`‡"úZp`3Üè(9Â÷äNëÌ—q"@‡"Ô ⁄"Ô ⁄Ô ⁄¡¡9pp0 @Äp˛àà
–@8˛$˜5  P 
à¸ÄÄ˛Äƒ¸ ˜:6'®;:9
aZfl¨nVZRF^ãb
kk#de…6flZ»∂9fl*îì/E±öıë⁄2Ù[¯:6*®MBR䢙j,4    §®ΩÍJ§ï¢µ5e§™äöj%+*âZÑj,WzïRJ—
MZ≤jU$≠¯:6›HI<ó$ƒLK§    )…)Lë)%"•%-)íL)IqR$ÑLtíS(îíëIRñLâI)¯:6QPì¥'fiûP¨mÚñ◊Ì™aHH:mù&ûJY◊ö¶5ûHÙ•ªˆ’0éí$ûømS¯:6O†“t€öu$î'IHÒLdâI@‚JJ.Hï$åîDmi$"î8£$§â q•îJHí¯ı˛
Ĉ
ˆ
 Ïı˛
Ĉ
ˆ
 ÏÒ
ÄÍ
 Ï¡¡$Ä0Ä@!Ä√ÿ  ˝A@Ä
$§ÿ$≤Ù[úêÉ
Á:£ê–$ƒW8E@⁄    ,¬E$≠•@%H
•(p„ƒÍ@´†⁄
EºII)Ä?flâá…p@DL8%› ⁄gèmSí    ¡k@aHñ-@⁄EÙäHí=–ÁéMπ∞Ê0dr6ÔÄ⁄ı˙ÄŸı˙ÄŸı˙ÄŸò@
¿
Ú
ˆ
¿
Ú
ˆ∫GÏ=
¡¡¡¡¡¡¡¡¡¡¡¡¡¡

‡pÃ

 çD÷R<¨-òÕ;‘§jÓIPF®Õíôƒ    JJ”êD¿Õ•-:êìö âÿÕÿ»·ƒîb—‡…"Õ
!˝Ä…
!˝Ä…
!˝Ä…¡¡ÄÄ– ÕÄ
˛Ä@ Õ    ⁄,ÅÄ[¡’ëÚXŒ&UA@§Çí*• Œ    "„Ç;Å%¢tI ŒCÆ"
ÈÖ¥EÍ@ŒB—«›—I‰:D@Œ˚ »˚ »¡¡¡ê@
p¸Ä÷Äê    @
 
HÄ÷£÷ÕéW…≤$Î
J/Ϻ≠¿ÿdöΔõ*NPëIR◊
-
$•…‰íE%tíœRQ¿ÿ    9ñ)≠i4GHF€É£⁄†@ÿ≠$>Fy6Ûë$>éÂJ<Fí›"ë#Äÿ˜
Ä“˜
Ä“Ùœ¡¡ò@@
ˆ@
ˆÏG,=

ˇ Õ
í ÕT íã˚.+"Õ∫Qî$TT"Õ•2·$≥ƒòî
"Õ≠TÇ6‡Ë¸®$Õˆòs$∑H®HXÕ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
ˆ@Ä
ˆ,Gl=¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
ˆÄ¿
ˆlG¨=¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

ˆ¿

ˆ¨GÏ=¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
ˆ

@
ˆÏG,=¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆ,Gl=¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆlG¨=¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆ¨Gfi=¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
ˆ@
ˆÏG,=


ˇ Õ
í ÕT íã˚.+"Õ∫Qî$TT"Õ•2·$≥ƒòî
"Õ≠TÇ6‡Ë¸®$Õˆòs$∑H®HXÕ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
ˆ@Ä
ˆ,Gl=
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
ˆÄ¿
ˆlG¨=
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

ˆ¿

ˆ¨GÏ=
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
ˆ

@
ˆÏG,=
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆ,Gl=
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆlG¨=
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆ¨Gfi=
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ&0@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@l.Introduction to Interapplication Communication4⁄*˙
¯

(‡*1-18    )BSupporting P).)AppleScript and Other Scripting Languages4^*¿
¯

k*r
¯4l*r
¯ mlm
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\lkµ(glRecordable ¶z°dONLNd\µk˛)IApplicationsˇˇˇˇˇˇ€r(g

1
°dONLNdrl~
™({lIIf you decide to make your application scriptable, you can also make it rÄ°dONLNdbr
´~
Ω({
´ecorz‡°dONLNdfr
Ω~
⁄)dable, °dONLNdmlãõ(àl
allowing uÌ@°dONLNdwõãΩ)/    sers to r†`°dONLNdÄæã–)#ecor¿°dONLNdÑ—ã
)d their action ¿°dONLNdí
ã
k):s in your application i_ °dONLNd©
lã
»)an the form of a script¥°dONLNdø
ȋ
Â)\. Even °dONLNdΔålòÖ(ïlusers =`°dONLNdÃåÜò
è)=with little or no knowledge of a particular scripting languagJÄ°dONLNd
    å
èò
ö(ï
èe c`°dONLNd
å
õò
¨)an r¿°dONLNd
å
¨ò
æ)ecorè °dONLNd
å
æò
Δ)d *‡°dONLNd
å
«ò
fi)    their °dONLNd
ôl•ú(¢lactions in r†°dONLNd
(ôù•Ø)1ecorí°dONLNd
,ôØ•
L)%dable applications in the form of a sà¿°dONLNd
Qô
M•
^)ûcrip÷ °dONLNd
Uô
^•
c)t.òÄ°dONLNd
Wô
d•
y) Mor»@°dONLNd
[ô
y•
Ò)e knowledgeable users can °dONLNd
u¶l≤o(Øl
rE°dONLNd
v¶p≤Ç)ecorπ`°dONLNd
z¶Ç≤
9))d scripts and then edit or combine them ai °dONLNd
£¶
:≤
V)∏s desirı‡°dONLNd
™¶
V≤
c)ed.[@°dONLNd
≠¶
d≤
f)
 €@°dONLNd
ƶ
f≤
h)
 °dONLNd
∞∏lƒ
Ì(¡lWApplications generally have two parts: the code that implements the application’s user °dONLNd≈l—
Ô*Xinterface and the code that actually performs the work of the application when the user °dONLNd_“lfiÁ*manipulates the interface. T°†°dONLNd{“Êfi
o)zo make your application fully r˘°dONLNdö“
ofi
Å)âecorm`°dONLNdû“
Çfi
”)dable, you should °dONLNd∞fllÎ
M(Ël4separate these two parts of your application, using †°dONLNd‰fl
NÎ
Ò)‚%Apple events to connect user actions °dONLNd    Ïl¯
&(ıl)with the work your application performs. °dONLNd3˛l

ù*
Any signifi¢¿°dONLNd>˛ù


)1cant user action within a rZ‡°dONLNdY˛



")secorœ@°dONLNd]˛
"


∫)"dable application should generate ˛†°dONLNd˛
∫


˜)òApple events °dONLNdå
l
˚(
l that a scripting component can rRÄ°dONLNd¨
˚

)èecorΔ‡°dONLNd∞



‚)1d as statements in a script. For example, when a °dONLNd·
l
$≈(
!luser chooses New fr˘°dONLNdÙ
≈
$
")Yom the File menu, a rÑÄ°dONLNd    

#
$
5)^ecor¯‡°dONLNd

5
$
 )#dable application sends itself a CrˇÄ°dONLNd0

 
$
fi)ïeate °dONLNd5
%l
1
z(
.l>Element event, and the application’s handler for that event cr…¿°dONLNds
%
z
1
Í(
.
zeates the new document. °dONLNdã
2l
>≠(
;lImplementing ÇÄ°dONLNdò
2≠
>
R)A&Apple events in this manner is called 
{‡°dONLNdæ
2
S
>
|)¶    factoringï °dONLNd«
2
|
>
Ã)) your application. Ï°dONLNd⁄
2
Ã
>
”)P
A&†°dONLNd€
2
‘
>
÷)
 °dONLNd‹
?l
KÖ(
Hlfactor¡°dONLNd‚
?Ö
K¸)ed application acts as both ¿°dONLNd˛
?˝
K
)xthe x °dONLNd
?

K
;)client and Ɇ°dONLNd
?
;
K
K).the ·°dONLNd
?
K
K
º)server application for the .†°dONLNd,
?
Ω
K
⁄)rApple °dONLNd2
Ll
X’(
Ulevents it sends to itself. °dONLNdN
^l
jo*
IfiÄ°dONLNdO
^o
j®)n general, a rC†°dONLNd]
^©
jª):ecor∏°dONLNda
^ª
j

)dable applicatior‡°dONLNdq
^

j
)Gn s
@°dONLNdt
^

j
T)hould generate Á`°dONLNdÉ
^
S
j
ç)DApple eventso °dONLNdè
^
é
j
Â); for any user action °dONLNd§
kl
w¨(
tlthat could be r]`°dONLNd≥
k¨
w
9)@eversed by the Undo command.ƒ¿°dONLNdœ
k
9
w
;)ç
 Ê`°dONLNd–
k
;
w
B)
A!°dONLNd—
k
C
w
I) rf°dONLNd”
k
I
w
[)ecor⁄`°dONLNd◊
k
[
w
n)dablf °dONLNd€
k
o
w
Æ)e application cV‡°dONLNdÍ
k
Ø
w
fl)@an usually °dONLNdı
xl
Ñù(
Ålhandle a grD†°dONLNd
xû
Ñ„)2eater variety of @°dONLNd
x„
Ñ
T)EApple events than it can r≤Ä°dONLNd+
x
T
Ñ
f)qecor&‡°dONLNd/
x
g
Ñ
∞)d, since it must r=Ä°dONLNdA
x
∞
Ñ
¬)Iecor±‡°dONLNdE
x
¬
Ñ
Ù)d the same °dONLNdP
Öl
ë
3(
él+action the same way every time even though !°dONLNd{
Ö
4
ë
€)»&Apple events might be able to trigger °dONLNd°
íl
û}(
õlthat÷ °dONLNd•
í}
û)
 V °dONLNd¶
íÄ
û÷)action in several dif̆°dONLNdª
í÷
û‚)Vfer– °dONLNdæ
í‚
û
)    ent ways.°dONLNd»
§l
∞s(
≠l
A∫†°dONLNd…
§s
∞u)
 
:†°dONLNd 
§v
∞y)
r@°dONLNdÀ
§z
∞¡)ecordable event`°dONLNd⁄
§¬
∞·)H is any ≤‡°dONLNd‚
§‡
∞
C)Apple event that any r˘@°dONLNd¯
§
C
∞
U)cecorm†°dONLNd¸
§
V
∞
„)"dable application sends to itself °dONLNd
±l
Ωã(
∫lwhile rá¿°dONLNd%
±ã
Ωù)ecor¸ °dONLNd)
±ù
Ω
I)'ding is turned on for the local compute^¿°dONLNdP
±
J
Ω
ˆ)≠)r (with the exception of events that the °dONLNdy
æl
 
/(
«l.application indicates it does not want to be r2¿°dONLNdß
æ
0
 
B)ƒecorß °dONLNd´
æ
B
 
X)ded).| °dONLNd∞
æ
Y
 
[)
 ù¿°dONLNd±
æ
[
 
Ω)After a user turns on ré@°dONLNd»
æ
Ω
 
œ)becor†°dONLNdÃ
æ
–
 
Ê)ding °dONLNd—
Àl
◊s(
‘lfrò‡°dONLNd”
Às
◊å)om thv °dONLNdÿ
Àç
◊”)e Script Editor aY†°dONLNdÈ
À‘
◊
)Gpplication, the Ä°dONLNd˘
À

◊
Ã)B(Apple Event Manager sends copies of all °dONLNd!
ÿl
‰o(
·l
rE°dONLNd"
ÿp
‰Ç)ecorπ`°dONLNd&
ÿÇ
‰ø)dable events t€`°dONLNd4
ÿø
‰ˇ)=o Script Editor-`°dONLNdC
ÿˇ
‰

)@
.≠`°dONLNdD
ÿ


‰
)
 ϡdONLNdE
ÿ

‰

)
A    †°dONLNdF
ÿ

‰
u) scripting component prFÄ°dONLNd]
ÿ
u
‰
ˆ)jeviously selected by the user °dONLNd{
Âl
ÒÎ(
Ólhandles each copied event fo°dONLNdó
ÂÏ
Ò
2)Är Script Editor bô °dONLNd®
Â
2
Ò
Â)F+y translating the event into the scripting °dONLNd”
Úl
˛»(
˚lcomponent’s scriptinj‡°dONLNdÁ
Ú…
˛

)]g language a¢¿°dONLNdÛ
Ú


˛
)8nd r‘‡°dONLNd˜
Ú

˛
%)ecorI@°dONLNd˚
Ú
&
˛
´) ding the translation as part of f °dONLNd    
Ú
´
˛
Ì)Öa Script Editor °dONLNd    +
ˇlp(l
sΩ°dONLNd    ,
ˇp
?).cript. When a scripting component executes a r °dONLNd    Z
ˇ
?
Q)œecordÄ°dONLNd    ^
ˇ
R
∏)ded script, it sends the °dONLNd    wl}(lcorr`°dONLNd    {~Ø)
esponding Û@°dONLNd    ÖÆ
è)02Apple events to the applications in which they wer‚`°dONLNd    ∑
è
ö)·e rÒ°dONLNd    ∫
ö
¨)ecore`°dONLNd    æ
≠
¿)ded.°dONLNd    √l*Ñ('lFigurR¿°dONLNd    »Ñ*ò)e 1-9@°dONLNd    Õò*fi) illustrates how +°dONLNd    fifl*
)GApple event r∫¿°dONLNd    Î
*
-)<ecor/ °dONLNd    Ô
.*
‹)&ding works. The user performs a signifiaÄ°dONLNd

‹*
Ò)Æcant °dONLNd
+l7¯(4laction (such as choosing New fr3`°dONLNd
:+˘7
I)çom the File menu)Õ¿°dONLNd
K+
I7
K)P
,M¿°dONLNd
L+
L7
›)! and the SurfCharter application °dONLNd
m8lD¨(Alsends itself an `°dONLNd
}8≠D‡)A
Apple even¿°dONLNd
á8‡DÈ)3t tÄ°dONLNd
ä8ÈD
ƒ)    4o perform the task associated with that action. If r@†°dONLNd
æ8
ƒD
÷)€ecorµ°dONLNd
¬8
÷D
ˆ)ding is °dONLNd
 ElQ≠(Nlturned on, the 8¿°dONLNd
ŸE≠Q
±)A8Apple Event Manager automatically sends a copy of each r6‡°dONLNdE
±Q
√(N
±ecor´@°dONLNdE
√Q
›)dable °dONLNdRl^
,([l+Apple event to the application (for example! °dONLNdFR
-^
m)¡, Script Editor)釰dONLNdVR
m^
Æ)@ that initiated r†°dONLNdgR
Ø^
¡)Becorì°dONLNdkR
¡^
Ì)
ding. The °dONLNdu_lk
=(hl.scripting component handles the copy of each rë@°dONLNd£_
=k
O)—ecor†°dONLNdß_
Pk
·)"dable event by translating it and °dONLNd…llxo(ul
rE°dONLNd lpxÇ)ecorπ`°dONLNdŒlÇx¯)ding it as part of a script. Tà¿°dONLNdÏl¯x
?)vo translate each b‡°dONLNd˝l
?x
â)GApple event corrÀ°dONLNdl
âx
ù)Jectly£°dONLNdl
ùx
€), the scripting °dONLNd"ylÖø(Çlcomponent must fi«`°dONLNd3yøÖ
…)S9rst check what equivalent human-language terminology the °dONLNdlÜlí
(èl&SurfCharter application uses for that `°dONLNdíÜ
í
÷)§+Apple event. The scripting component then rå`°dONLNdΩÜ
֒
Ë)Δecor¿°dONLNd¡Ü
Èí
ı)ds °dONLNdƒìlü
(úl%the equivalent statement in the scrip˘‡°dONLNdÈì
ü
)†t.ˇoö@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@ä.Introduction to Interapplication Communication4⁄ä˙(‡äSupporting P).)AppleScript and Other Scripting Languages

, (‡1-19
ˇˇˇˇˇˇˇˇ4^4|lòÄ2^A|rMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^A|r^A|r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
^6|@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^6|@^6|@˜˜˜˜˜˜˜˜˜˜˜˜˜˙ˇˇ
˙ˇ
˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜
4Å4
w?òÄ
Å6
w@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""Å6
w@Å6
w@$˜
˙ˇ˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛
¸ˇ˛¸ˇ˝˚ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛
˙ˇ˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˛¸ˇˇ
ˇ˛ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˜˜˜˜
˙ˇ
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛˜˛˛ˇ˝
ˇˇˇ˛
ˇˇˇ˛    ˇˇˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
˙ˇ˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˝˛ˇ˛
˛ˇ˛ˇˇ    ˇ¸
ˇ    ˇ¸
ˇ
˛ˇ˛ˇˇ˜˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh≈(eäThe chapter “~ °dONLNd\Δhfl)<Recor†Ä°dONLNd\flhı)ding &¿°dONLNd\ˆh
*)
Apple EvenÅ@°dONLNd!\
*h
6)4ts”†°dONLNd$\
7h
´) in this book describes the p °dONLNd@\
´h
Â)tApple Event °dONLNdLiäu±(räManagerœ`°dONLNdSi≤uø)(’s r†°dONLNdWi¿u“)ecorç°dONLNd[i“u
;)ding mechanism in mor„‡°dONLNdpi
;u
À)i!e detail and explains how to use ο°dONLNdëi
Àu)êApple events to °dONLNd°väÇÒ(äfactor your application.

§Hµ4•Hµ"•H]

ˇ·ˇ‚7^
    °dONLNd∫öä•¥*#
Figure 1-9°dONLNd≈öÕ
â)B0Recording user actions in a factored application


–H
◊4
—H
◊ 
“ä
“

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd˜
¡ä
–◊(
ÃäApplications »v°dONLNd

¡◊
–
∂)M#That Manipulate and Execute Scriptsˇˇˇˇˇˇ€r(
Ã
1
°dONLNd
)
׊
„¡(
‡äLike sound rH†°dONLNd
5
◊¬
„⁄)8esourꇰdONLNd
:
◊⁄
„Á)ces¿°dONLNd
=
◊Ë
„
<), scripts can be storfi@°dONLNd
R
◊
;
„
ù)Sed either as separate fiñ¿°dONLNd
j
◊
û
„)cles with their own icons in °dONLNd
Ü
‰ä

u(
Ìä6the Finder or within an application or its documents. ¿°dONLNd
º
‰
v

|)Ï
Y’@°dONLNd
Ω
‰
{

„)our application can storv‡°dONLNd
’
‰
‰

˛)ie and °dONLNd
€
Òä
˝¶(
˙äexecutı†°dONLNd
·
Ò¶
˝±)e s|@°dONLNd
‰
Ò≤
˝—)cripts ré°dONLNd
Ï
Ò—
˝‰)egar´¿°dONLNd

Ò‰
˝
)&dless of whether it is scriptable or rÇÄ°dONLNd
Ò

˝
ë)õecorˆ‡°dONLNd
Ò
ë
˝)dable. If your application is °dONLNd8
˛ä
‡(äscriptable, howeverì°dONLNdK
˛‡

m)V#, it can execute scripts that contr›°dONLNdn
˛
m

¡)çol its own behaviorÄ°dONLNdÅ
˛
¬

˙)U, thus acting °dONLNdèäì(äasΩ°dONLNdëìï)    
 =°dONLNdíñ
≥)Cboth the client application and the server application for the corr`°dONLNd’
≥
‰(
≥
esponding °dONLNdflä$•(!äApple˝Ä°dONLNd‰•$ß)
 }Ä°dONLNd®$…)events. °dONLNdÓ*ä6ê(3ä
Y@Ä°dONLNdÔ*ê6
)Pour application can establish a connection with any scripting component that is °dONLNd?7äCç(@ä
rE°dONLNd@7éC´)egisterî °dONLNdG7´C
¢)2ed with the Component Manager on the same computerΔ°dONLNdy7
¢C
Ë)˜. Each scripting °dONLNdäDäP
¨(Mä@component can manipulate and execute scripts written in the corriÄ°dONLNd D
¨P(M
¨esponding scripting °dONLNdfiQä]µ(Zä    language ®¿°dONLNdÁQµ]¡)+(orß`°dONLNdÍQ¡]
), as in the case of ›`°dONLNd˛Q
]
)L8AppleScript, one of the scripting language’s dialects) wÙ‡°dONLNd6Q
])Ùhen °dONLNd:^äj
(gä"your application calls the standar¬ °dONLNd\^
j
á)ìd scripting component r†°dONLNds^
àj
™)koutines.°dONLNd|pä|ê(yä
Y@Ä°dONLNd}pê|ï)
o∂°dONLNd~pï|°)u c≠`°dONLNdÅp¢|Ú)an use the standar`°dONLNdìpÛ|
])Qd scripting component rq‡°dONLNd™p
]|
ã)joutines to ,Zapf Dingbats°dONLNd∂Üäçè(åä
n
°dONLNd∏Éñèˆ)get a handle to a scripM‡°dONLNdœɘè
2)at so you can sÕ °dONLNd›É
2è
<);avs`°dONLNdflÉ
=è
r)e the script iOÄ°dONLNdÌÉ
sè
å)6n a prË°dONLNdÛÉ
åè
ú)eferî °dONLNd˜É
ùè
Ω)ences fi2¿°dONLNdˇÉ
æè)!le, in the data fork °dONLNdèñõ
B(òñ(of a document, or as a separate script fi    `°dONLNd=è
Cõ
E)≠
lÒ¿°dONLNd>è
Eõ
I)
e°dONLNd@§ä´è(™ä
n
°dONLNdB°ñ≠œ)manipulate s»`°dONLNdN°œ≠Í)9cripts  °dONLNdU°Î≠
#)associated w\°dONLNda°
#≠
˛)83ith any part of your application or its documents, °dONLNdî≠ñπŸ(∂ñincluding both ∞†°dONLNd£≠Ÿπ
+)CApple event objectKÄ°dONLNdµ≠
,π
7)Ss aÄ°dONLNd∏≠
8π
ë)nd other objects defi∫`°dONLNdÕ≠
ëπ
Ó)Yned by the applicatio ¿°dONLNd‚≠
Óπ
Û)]
n

¥H
©4≥A¥Bò@@
¸@
¸¥BÙ>¡¡
 ˇ‡˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
ıˇ⁄ˇ˙
ıˇ0⁄ˇ˙
ıˇ@
Ä⁄ˇ˙
ıˇÇ`⁄ˇ˙
ıˇ

ê⁄ˇ˙
ıˇ⁄ˇ˙
ıˇ
‰⁄ˇ˙
ıˇ!R⁄ˇ˙
ıˇ"©⁄ˇ˙
ıˇDQ⁄ˇ˙
ıˇ Ñ)⁄ˇ˙
ıˇ à ⁄ˇ˙
ıˇ! ⁄ˇ˙
ıˇ!@⁄ˇ˙
ıˇ"@⁄ˇ˙
ıˇÄ⁄ˇ˙
ıˇ èÄ⁄ˇ˙
ıˇ üÄ⁄ˇ˙
ıˇ#ÒÄ⁄ˇ˙
ıˇ'Òæ⁄ˇ˙
ıˇ¸q˛⁄ˇ˙
ıˇ
¸qΔ⁄ˇ˙
ıˇ
ÒΔ⁄ˇ˙
ıˇ
{Δ⁄ˇ˙
ıˇ
ıÓ⁄ˇ˙
ıˇ
{÷⁄ˇ˙
ıˇ
æıÓ⁄ˇ˙
ıˇ
]{÷⁄ˇ˙
ıˇ
æıÓ⁄ˇ˙
ıˇ
]{÷⁄ˇ˙
ıˇ
æıÓ⁄ˇ˙
ıˇ
˜fl|⁄ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙ò@@Ä
¸@Ä
¸ÙB
4>
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙ò@Ä¿
¸Ä¿
¸
4B
t>
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙ò@¿

¸¿

¸
tB
¥>
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙
 ˇ˙ ˇ˙¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
¸

@
¸
¥B
Ù>¡
«`Ä»
"êr@»
bÄ@»
Rp$@»
èê$@»
Ñ0$Ä»    ƒ>¿s«¡¡¡¡¡
†x4¸DÄtàfl
Ä8$$¸@˝ 
 Äfl"'¢»$DFVu≥ƒ\ÿ+‰õp∂
u>K'•$e»∂‡")eX™®§‘å°`UEMÄö*T§Zfi§™âZ‡"I-8àQ—)(îÖü†òäIq$2â$Úî…R‡"f: HIQm3@˚Œì¶<^ΩHñ)mö¶‡"N.80‰Ëëπ'π¿§â·$(THà{ΔHï$‡˘
Ģ@˛

‹˘
Ä˙

@˛

‹˘¯Ä˛

‹¡¡9p8


†Ä8˛HÅHÅ
– ˛
$˜5 (

ƒ¸@

@

˛Äb¸ ˜;7%‘ù91M€ë÷∑+-)#.â±
5µ£≤eË∂
€ŸËõÅ€ïñîëó"ÿÄZ⁄»ŸtMĢ;7*T&°RÖRïi*“T^ı%Tî—öö‰“™IZi"´%IM    Bi*/zí™%hÄ≠MYi*§¶Ä˘;7‹§$ûóî¢JI“î‰î¶Hô$ëíí¨ïíRJ$…híIBJrJS$LIHÅ)IKJD…$Ģ;7P®Iᥠ   ØõPV    6à˘Kk˝©0ç$$97~⁄¶õEYÀ⁄ìÑõD|•µ˛jòGRõ_ÌIĢ:6N–i:€ç=í#§ç$x¶2D© r%%-$îë$FíBmdëí<S"TDê8ííãí%Hâ¯ı
˛
@ıĘ
 Ïı
˛
@ıĘ
 ÏÒ
@Í
 Ï¡¡Ä
 Fç0!Ä"⁄    
¸à HBÄ
"⁄    #˙À¢l:‚Aêa]¡‘üñ4Δ‹%r¿€    f%4C%§£™T©J:†
^£@€-·&I$<N˚Ò1¿•J#ˇ‰¬@€r?jLà
"BX@©€@Ñ%Ñâb¿€/¢*DHuÁCú·ìê—n$lyŒ9vDÄ€ˆ˘ Ÿˆ˘ Ÿˆ˘ Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡

pÃ


àÃ
RBk)l≥Õò@
@
Ä
¸
@
Ä
¸
ÙB4>Í¢5w(∞’ÕâM¬    %%q–òÕíó
HIŸ ;ÕÃd‡‰J1p·$@ŒIJ@ÀIJ@ÀIJ@…¡¡ÄÕÄ
Õ    ⁄&A@|≤>+Œ&J°
†à)ETTŒ    "—¬¿$êJNàîŒCó1E[ຮŒB»ÁŒËœnáHHŒ˚»˚»¡¡¡‡
Ä#ÄÓ‡ˇ‘Å Ä!D@J‘Å≥ïπ6ADùb@JE˝ó∏÷
¿’*BöAyñ•@ä **@÷
$ôr<íBà§ÆÄîY‚LJ8÷     E;D&Ç àÈ¡pt~T÷ó»œ-ºr$á—‹©Gëî[§T$p÷˘
˛  –˘

@ –ˆ

ÄŒ¡¡
 `` †
 êê §_ŸqX ¨°"¢†q     Eû$ƒ†     ÁGÂ@â  E∫EB@r¿ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
¸
Ä
¿
¸4Bt>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
¸
¿
Ú
¸tB¶>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
¸@
¸¥BÙ>
¡¡
 3 ˙
 ˙
 0˙¡
 ˙¡
 0˙
 ˙
 0˙¡
 ˙¡
 0˙
 ˙
 0˙Û
—
Ù
0Ÿ˙Û@
Ä“
ÙÇ`⁄0˙
ı

ê⁄˙
ı⁄0˙    Ù
‰“
ı!R⁄˙    Ù"©“
ıDQ⁄0˙
ı Ñ)⁄˙
ı à ⁄0˙    Ù! “
ı!@⁄˙Ù"@—
ıÄŸ0˙
ı èÄ⁄˙
ı üÄ⁄0˙    Ù#ÒÄ“
ı'Òæ⁄˙Û¸q˛“
ı
¸qΔ⁄0˙
ı
ÒΔ⁄˙
ı
{Δ⁄0˙    Ù
ıÓ“
ı
{÷⁄˙    Ù
æıÓ“
ı
]{÷⁄0˙
ı
æıÓ⁄˙
ı
]{÷⁄0˙    Ù
æıÓ“
ı
˜fl|⁄˙¡
 0˙
 ˙
 0˙¡
 ˙¡
ˆ@Ÿ0˙
ˆÄ9@⁄˙
ˆKpsoò€0˙ı
 0O«–”
ˆ 1LΔ€˙ı:.K√–”
 0˙
 ˙ò@@Ä
¸@Ä
¸ÙB
4>

 0˙¡
 ˙¡
 0˙
˙ıˇ˛fl˙
˙Ù"fl0˙
˘ı◊
˙ıfl˙
˘ıàä◊
˙ıfl0˙
˙ıfl˙
˙Ù"fl0˙
˘ı◊
˙ıfl˙
˘ıàä◊
˙ıfl0˙
˙ıfl˙
˙Ù"fl0˙
˘ı◊
˙ıfl˙
˘ıàä◊
˙ıfl0˙
˙˘ˇ˛fl˙
˙"0˘""fl0˙˘ ˝˛@›
˙ ˛
@Â˙˘àêw&-Œàä˛
ÁL›
˙LØ<ø$˛îfiÂ0˙
˙î —$˛î–Â˙
˙"0˜'è"&"˛ÁNÂ0˙˘D¸˛˝Ñ‹
˙D¸¸˛Ñ‰˙˘àê˘∞Ÿ
˙˛ ·0˙
˙˛0˛Â˙
˙"0n<Ã8
¿ñÁÂ0˙˘˘Mˡ¯p_í›
˙ôM‡híÂ˙˘àêy<Ëéä8Gë›
˙˘‚0˙
˙¯ˇ
Ä„˙
˙"/¯ˇ""
¿¿„0˙˘ıp@€
˙ı`„˙˘ıàä0€
˙ı„0˙
˙ı„˙
˙Ù"„0˙˘ı
Ñ€
˙ı˛Δ„˙˘ıàä˛B€

 ı˛B„0˙

 ı˛B„˙

'l1π∏Ù"˛c„0˙
,¯zZdı˛!€

#àJdı˛!„˙˛Œx9…§ıàä˛!€
˙ı˛
1ĉ0˙
˙ı˛
ĉ˙
˙Ù"˛
ĉ0˙˘ı˛
1Ä‹
˙ı˛!„˙˘ıàä˛!€ò@Ä¿
¸Ä¿
¸
4B
t>

˙ı˛!„0˙
˙ı˛c„˙
˝0Ù"˛B„0˙¸Ñı˛B€
˛ ı˛B„˙˝
Äıàä˛Δ€
˛˛ı
Ñ„0˙
˛`ı„˙
˛Ù"„0˙¸0ı€
˙ı0„˙¸
ıàä`€
˝˘ˇ˛0@„0˙
˝H˘`¿„˙ 
˝ê"0@ ""
¡Ä„0˙ ˝ @@Êˇ‡¯(
ƒÄ ]òfÊp˜ıˇ¸0˙+ˇ˝˛∏ês–˘iHàäp˜Ä˜

Ä˝ˇ–¯-
}ÁÄ8NòiH¿0˜Ä˜

Ä˝0˙-
øɲˇ¸
π–w&H¸‡˜Ä˜

Ä˝    ˇò˙+
‡Ç˛"
&0˘?ˇĢĘ

Ä 0˙(
ÄDz
˘ ¯Ę
Ä0    ˇË¯.
?√DzD
G˘ ¯ÄÄÄ@@˚

Ä8˙1/˛˛àéê˛†˜ˇ˛¿Ä@ĸ    
èˇˇÏ¯4
8˛8˛ˇÏ˛ 
¯ˆ`Äy‹·õG3ô‹
àˇ0˙3
å‡˛8n<Ã?˛ı0ÄÊd”"f§ }(
â˙2
˝Ä˛20˘MË$Ù0Äbd”"&§ a(
ä""#    ˇ0˙.˛˝ôMÙ`ÄûxR·⁄ß2]$
௯/
˙y<Ëıˇ    ˛¿Ä  ˛

èˇˇÏH0˙'˘àê˘àäˆ    ÄÄ 
¿˛
Ä8ÿ ¯#
˙¯ˇ
ˆĘ

Ä0p 0˙#
˙¯ˇ
ˆĘ

IJ `˙#
˙Ù"˝0¸Ä˜

IJ‡¿0˙!˘ı˝» ¸Ä˜

IJ
ˇˇÄ¯
˙ı˝É:Cp¸ıˇÄ˘˙˘ıàä˝ѶD†¸ˆˇÄ˝
‡˜
˙ı˝å•D†Ï
0˙
˙ı˝s9É Î√w8˙
˙Ù"¸!È4‘ê0˙˘ı¸"Ù¿¯
Tê¯
˙ıÓ¿˜„◊˙˘ıàä˛
 
Û¿ˆ˜ 
˙ı˛
P
˛@˜¿ˆ0˙
˙ı˛Sπ`…n‡¯

‡Û˙
˙Ù"˛reÒ¢@¯

‡Û0˙˘ı˛äeÅâ@¯

‡Î
˙ı˛ãπp‰y ¯

‡Û˙˘ıàä˛
 Ù

Î
˙ı˛
 Ù
Û0˙
˙ıÓ@Û˙
˙Ù"Ó@Û0˙˘ıÓ@Î
˙ıÓ@Û˙˘ıàäÓ@Î
˙ıÓ@Û0˙
˙ıÓ@Û˙
˙Ù"Ó@Û0˙˘ıÓ@Î
˙ıÓ@Û˙˘ıàäÓ@Î
˙ıÓ@Û0˙
˙˘ˇ¿Ó@Û˙
˙",˘b""Ó@Û0˙˘˘ Ó@Îò@¿

¸¿

¸
tB
¥>

˙˘0Ó@Û˙˘àà˘àäÓ@Î
˙˘Ó@Û0˙
˙˘Ó@Û˙
˙"(˘""Ó@Û0˙˘˘Ó@Î
˙˘Ó@Û˙˘àà˘àäÓ@Î
˙ @˝Ó@Û0˙
˙!Òƒ•≥Ó@Û˙
˙"(ëB ≤eOüÏˇ¿Û0˙˘üK‡eD◊
˙Δ0¿πù;êfl˙˘àà˘àä◊ 
˙˘˛Ä@˚Ó0˙#
˙˘˛Ä@˛Ó˙$
˙"(˘""˛•£8M«ñ;ûá>`Ô0˙˘˘˛•Wß_)üOá’L@Á$
˙˘˛•T§S)ôLC@Ô˙˘àà˘àä˛ùS§O'w;É’N@Á
˙˘0˘
Í0˙
˙˘ ˘pÍ˙
˙",˘b""fl0˙˘˘¿¸ ˝‰
˙˘ˇÄ¸ Ï˙˘ıàä¸;¶,Ó39úÂ
˙ı¸&oæîLÀÌ0˙
˙ı¸¶h–îD Ì˙
˙Ù"¸ªßéí;9¯Ì0˙˘ı˚"fi
˙ı˚"Ê˙
˘ıàä◊
˙ıfl0˙
˙ıˇ˛fl˙
 0˙¡
 ˙¡
 0˙
 ˙
 0˙¡
 ˙¡
 0˙
 ˙
 0˙¡
 ˙¡
 30˙ UP˙¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
¸

@
¸
¥B
Ù>
¡
«`Ä»
"êr@»
bÄ@»
Rp$@»
èê$@»
Ñ0$Ä»    ƒ>¿s«¡¡¡¡¡
†x4¸DÄtàfl
Ä8$$¸@˝ 
 Äfl"'¢»$DFVu≥ƒ\ÿ+‰õp∂
u>K'•$e»∂‡")eX™®§‘å°`UEMÄö*T§Zfi§™âZ‡"I-8àQ—)(îÖü†òäIq$2â$Úî…R‡"f: HIQm3@˚Œì¶<^ΩHñ)mö¶‡"N.80‰Ëëπ'π¿§â·$(THà{ΔHï$‡˘
Ģ@˛

‹˘
Ä˙

@˛

‹˘¯Ä˛

‹¡¡9p8


†Ä8˛HÅHÅ
– ˛
$˜5 (

ƒ¸@

@

˛Äb¸ ˜;7%‘ù91M€ë÷∑+-)#.â±
5µ£≤eË∂
€ŸËõÅ€ïñîëó"ÿÄZ⁄»ŸtMĢ;7*T&°RÖRïi*“T^ı%Tî—öö‰“™IZi"´%IM    Bi*/zí™%hÄ≠MYi*§¶Ä˘;7‹§$ûóî¢JI“î‰î¶Hô$ëíí¨ïíRJ$…híIBJrJS$LIHÅ)IKJD…$Ģ;7P®Iᥠ   ØõPV    6à˘Kk˝©0ç$$97~⁄¶õEYÀ⁄ìÑõD|•µ˛jòGRõ_ÌIĢ:6N–i:€ç=í#§ç$x¶2D© r%%-$îë$FíBmdëí<S"TDê8ííãí%Hâ¯ı
˛
@ıĘ
 Ïı
˛
@ıĘ
 ÏÒ
@Í
 Ï¡¡Ä
 Fç0!Ä"⁄    
¸à HBÄ
"⁄    #˙À¢l:‚Aêa]¡‘üñ4Δ‹%r¿€    f%4C%§£™T©J:†
^£@€-·&I$<N˚Ò1¿•J#ˇ‰¬@€r?jLà
"BX@©€@Ñ%Ñâb¿€/¢*DHuÁCú·ìê—n$lyŒ9vDÄ€ˆ˘ Ÿˆ˘ Ÿˆ˘ Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡

pÃ


àÃ
RBk)l≥Õò@
@
Ä
¸
@
Ä
¸
ÙB4>
Í¢5w(∞’ÕâM¬    %%q–òÕíó
HIŸ ;ÕÃd‡‰J1p·$@ŒIJ@ÀIJ@ÀIJ@…¡¡ÄÕÄ
Õ    ⁄&A@|≤>+Œ&J°
†à)ETTŒ    "—¬¿$êJNàîŒCó1E[ຮŒB»ÁŒËœnáHHŒ˚»˚»¡¡¡‡
Ä#ÄÓ‡ˇ‘Å Ä!D@J‘Å≥ïπ6ADùb@JE˝ó∏÷
¿’*BöAyñ•@ä **@÷
$ôr<íBà§ÆÄîY‚LJ8÷     E;D&Ç àÈ¡pt~T÷ó»œ-ºr$á—‹©Gëî[§T$p÷˘
˛  –˘

@ –ˆ

ÄŒ¡¡
 `` †
 êê §_ŸqX ¨°"¢†q     Eû$ƒ†     ÁGÂ@â  E∫EB@r¿ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
¸
Ä
¿
¸4Bt>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
¸
¿
Ú
¸tB¶>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
¸@
¸¶BÊ>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
¸@Ä
¸ÊB&>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
¸Ä¿
¸&Bf>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

¸¿

¸fB¶>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
¸

@
¸¶BÊ>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
¸
@
Ä
¸ÊB&>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
¸
Ä
¿
¸&Bf>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
¸
¿
Ú
¸fBò>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
¸@
¸¶BÊ>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
¸@Ä
¸ÊB&>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
¸Ä¿
¸&Bf>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

¸¿

¸fB¶>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
¸

@
¸¶BÊ>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
¸
@
Ä
¸ÊB&>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
¸
Ä
¿
¸&Bf>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
¸
¿
Ú
¸fBò>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇK™@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@l.Introduction to Interapplication Communication4⁄*˙
¯

(‡*1-20    )BSupporting P).)AppleScript and Other Scripting Languages4^*¿
¯,Zapf Dingbats°dONLNd_lfq(el
n
°dONLNd\xh£)let users rv¿°dONLNd\£hµ)+ecorÎ °dONLNd\µh

)d and edit scripts°dONLNd$qlxq(wl
n
°dONLNd&nxzÚ)compile and execute scripts°dONLNdBlãÑ(àlFigurR¿°dONLNdGÑãù)e 1-10@°dONLNdMùã
£); shows how an application might execute a script that contrÆ °dONLNdà
§ã
÷(à
§ols its own °dONLNdîålòì(ïlbehavior‹°dONLNdúåíò¢)&. ThŒ °dONLNd†å£òø)e appr·°dONLNd¶åøò
=)opriate user action handler eN†°dONLNd√å
>ò
ú)xecutes the script in r* °dONLNd⁄å
úò
Í)^esponse to a user °dONLNdÏôl•°(¢laction, whic‚‡°dONLNd¯ô°•¿)5h can b}Ä°dONLNdˇô¡•
„) ?e almost anything: choosing a menu command, clicking a button, °dONLNd
>¶l≤ó(Øl
tabbing fr≥`°dONLNd
H¶ó≤
)+om one table cell to another%`°dONLNd
d¶
≤
·)z2, and so on. The script might consist of a single °dONLNd
ñ≥lø
€(ºlVstatement that describes some default action, such as saving or printing, or a series °dONLNd
Ï¿lÃw*of …`°dONLNd
Ô¿wÃ
ú)Fstatements that describe a series of tasks, such as setting default prÄ°dONLNd5¿
ùÃ
≠(…
ùefer †°dONLNd9¿
≠Ã
Ï)ences or stylesB °dONLNdH¿
ÌÃ
Ú)@. °dONLNdJÕlŸÑ(÷lFigurR¿°dONLNdOÕÑŸù)e 1-10@°dONLNdUÕùŸ£) s≠@°dONLNdWÕ§Ÿ
)hows a script that corrH`°dONLNdnÕ
Ÿ
])cesponds to a single Ç °dONLNdÇÕ
]Ÿ
ê)V
Apple evenäÄ°dONLNdåÕ
êŸ
ù)3t, bTÄ°dONLNdêÕ
ûŸ
)ut the script could °dONLNd§⁄lÊ∑(„ljust as easily corr °dONLNd∑⁄∏Êfi)Lespond tK‡°dONLNdø⁄fiÊÍ)&o aA`°dONLNd¬⁄ÎÊ
2) whole series of ‰Ä°dONLNd”⁄
1Ê
s)FApple events. I ¿°dONLNd‚⁄
tÊ
‰)Cf your application allows °dONLNd¸ÁlÛÍ(lusers to modify such a scriptx`°dONLNdÁÎÛ

), they c’ °dONLNd!Á

Û
È)3an modify the behavior of your application to suit °dONLNdTÙl
ü(˝ltheir needs.


"*
3
¯4
#*
3
¯"
#*]

ˇ·ˇ‚7^
    °dONLNda
l
#ú*#Figure 1-10°dONLNdm
Æ
#
)BControlling an application’[0°dONLNdà


#
¶)g$s own behavior by executing a script
°dONLNdÆ0l<r(9l
Y@Ä°dONLNdØ0r<
@)0our application can associate a script with any `°dONLNdfl0
@<
°)ŒApple event object or °dONLNdı=lI±(Flapplication-defi|‡°dONLNd=≤I
fl)FEned object and execute the script when that object is manipulated in °dONLNdJJlVò(Slsome wayÄ°dONLNdRJòV
À),I. The script can describe actions to be taken by your application, as in °dONLNdúWlcÑ(`lFigurR¿°dONLNd°WÑcù)e 1-10@°dONLNdßWùc
ÿ)K, or actions to be taken by several applications. For example, a user of a °dONLNdÚdlp}(mlworÄ°dONLNdıd~pë)d-prH@°dONLNd˘dëp
)ocessing application mighé@°dONLNdd
p
)st aP†°dONLNdd
p
y)ttach a script to a specifiâ¿°dONLNd0d
yp
ë)jc worÄ°dONLNd5d
íp
À)d so that the °dONLNdCql}
G(zl1application executes the script whenever that wor4`°dONLNdtq
H}
û)‹d is double-clicked.A °dONLNdàq
û}
ˆ)V Such a script could °dONLNdù~läå(áltrigger ôÄ°dONLNd•~åä
;) 'Apple events that look up and display rP°dONLNdÃ~
<ä
ó)∞elated information fr˛°dONLNd·~
óä
÷)[om a separate °dONLNdÔãló°(îldocument, r†°dONLNd˙ã¢óÿ)6un a QuickTP°dONLNdãÿó
Ó)6?ime movie, perform a calculation, play a voice annotation, and °dONLNdDòl§Ö(°lso on.


2l
¯4
0j
1kò@@
˜@
˜
1k
qb¡¡?fiˇ¸Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?Èˇ˛˝¸ˇ˛Ê?Èˇ˛˝¸ˇ˛Ê?Èˇ
˛˛¸ˇ˛Ê?Èˇ
˛˛¸ˇ˛Ê?Èˇ˛ ĸˇ˛Ê?Èˇ˛ @¸ˇ˛Ê?Èˇ˛!Á¯¸ˇ˛Ê?Èˇ˛¯¸ˇ˛Ê?Èˇ˛¿Ä¸ˇ˛Ê?Èˇ˛Ç`¸ˇ˛Ê?Èˇ˛
ê¸ˇ˛Ê?Èˇ˛¸ˇ˛Ê?Èˇ˛
‰¸ˇ˛Ê?Èˇ˛!R¸ˇ˛Ê?Èˇ˛"©¸ˇ˛Ê?Èˇ˛DQ¸ˇ˛Ê?Èˇ˛ Ñ)¸ˇ˛Ê?Èˇ˛ à4¸ˇ˛Ê?Èˇ˛!"¸ˇ˛Ê?Èˇ˛!Q¸ˇ˛Ê?Èˇ˛"hĸˇ˛Ê?Èˇ˛‘@¸ˇ˛Ê?Èˇ˛ ™ ¸ˇ˛Ê?Èˇ˛ ï¸ˇ˛Ê?Èˇ˛ äà¸ˇ˛Ê?Èˇ˛ ÖD¸ˇ˛Ê?Èˇ˛
 Ƕ¸ˇ˛Ê?Èˇ˛êAY¸ˇ˛Ê?Èˇ˛P@π¸ˇ˛Ê?Èˇ˛0 a¸ˇ˛Ê?Èˇ˛#¸ˇ˛Ê?Èˇ˛ ¸ˇ˛Ê?Èˇ˛@¸ˇ˛Ê?Èˇ˛Ä¸ˇ˛Ê?Èˇ˛˝¸ˇ˛Ê?Èˇ˛˝¸ˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Êò@@Ä
˜@Ä
˜
qk
±b?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Êò@Ä¿
˜Ä¿
˜
±k
Òb?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Êò@¿

˜¿

˜
Òk1b?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Ê?fiˇ˛Êfiˇ˛Ê¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡
«0@»
"H9¿»
b@@»
R8Ä»
ç–Ä»ò@

@
˜

@
˜1kqb
ÑòÄ»
ƒ>`9¿»¡¡¡¡¡*‡¿pÄ?@˝$IJ
 ˛
È'@89!àĸ IJ¸È+''£d
"
mÏí[x-Ç©J2Ù[    ◊bÑ≤Í+êM#G;<(Ái\È+')dä"¥ëRMêVÖw™U$≠U£J’*TêßU -HQ
ã®È+'I,úí"•dâêîâ%4âI)$•"\ôLî°ƒË\IHêë0È+'f9AM¢∂”`˘èJ^ømS
(™bêøV®·ãvs07XÈ+'N-89Ä‚I!$퇩
1îJHí“C*$H†˚t\Rp°…êȯ
BÙ ˝à˯
Bı

@˝à˘‡Bı

Ä˝pË¡¡ 88



‡@8˛Dfi
(
˛Äƒ¸@fi!Í›Ö0≠oâ÷∑+*î£/E±µµë≤2‰õfl!ï*#a)EQU5“TWz•RJ—
Zö≤“UEMfl!nR"^KÖíb&%“î‰íSHîíëRíñîâäIfl!(TD«Z    ÔO(V    6àٕΈ’0é§$6øŒìfl"'hd∫mÕ:íJ§ç$x£D§â q%%$Jâ@‡ı
˛
 ıćı
˛
 ıćÒ
 ”¡¡ê†@8˛H⁄Ä
ƒ¸@⁄∑≤:'—69∑+-)#.E±µµë≤2Ëõ€“EVJíöÑ“T^ı%TJ—
Zö≤“UIM€îIí—$í$Ñî‰î¶HòíëRíñîâíI€    6ä≥óµ&5    6à˘Kk¸’0é§$6ø⁄ì€$Ñ⁄…"$"$x¶2D®â q%%$Jë€ı
@œı
@œı
@œ¡¡¿ê`Üê1Ç@
Ä⁄ÄIJíêêJN@Ä⁄¢˛À—l:r@íêƇÍè÷B
Óí∫¿€    í¥Bïé·’*îöƒP/S@€    ,Ò%$§<.E ò‡S% $    é    rb@€∏:=µLHe!, U≠ñB$¬D≤¿€    -“)"Ht˜Cò¿…»i7$6yŒúçª$Ä€ˆ
˘Ÿˆ
˘Ÿˆ
˘Ÿ¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜qk±b¡¡¡
ÄpÃ
Ä
àÃ
äR"
k)V±ÄŒ
ùÍRµw$®“ÄŒIL‚•%i»îÕRñÅHIÕ    5ÄŒÏdp‚J1hç" ŒIJ@
ÀIJ@
ÀIJ@…¡¡Ä
¿Õ@ÄÕÌ@Ñ@|Y%Äœ*†ä†à)"™RŒëq¡¿$êJ'DíŒ°◊
E[D^§Œ!h„ÓËœnC§DŒ˚»˚»¡¡¡ɇ¿¸ÄœA @
HÄœA± ‹∂
J/Ϻ¨–Å¿“ï!ZNPëIP–$îπRíœRP–Ç E5¢¶€É£⁄†–O»œ&fi9$Fí›"ë –¯ÄÀ¯ÄÀ¡¡¡¯
`0 ê
êH í?≠y,à ñaíêpà "fi§êà     ≥á'µ àê "˙%" r` ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜±kÒb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜Òk#b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜
1k
qb
¡¡›30Ê›Ê fiÊ›Ê›Ê›Ê fiÊ›Ê fiÊ›Ê›Ê›Ê fiÊ›Ê fiÊ
Á¯Ê
Á¯ÊÁ
 ĢÊ Ë
 @˘ÊÁ!Á¯˙Ê Ë¯˙ÊÁ¿Ä˚ÊÁÇ`˚ÊÁ
ê˚Ê Ë˚ÊÁ
‰˚Ê Ë!R˚ÊÁ"©˚ÊÁDQ˚ÊÁ Ñ)˚Ê Ë à4˚ÊÁ!"˚Ê Ë!Q˚ÊÁ"hÄ˚ÊÁ‘@˚ÊÁ ™ ˚Ê Ë ï˚ÊÁ äà˚Ê Ë ÖD˚ÊÁ
 Ƕ˚ÊÊêAY˚ÊÊP@π˚Ê Á0 a˚ÊÊ#˚Ê Á ˚ÊÊ
@˙ÊÊ
Ä˙Ê›Ê fiÊ›Ê Û$
ÊÚ$ÊÚ$ÌÜ77˚pH@˚ÊÚ%üKLĸàH˚Ê Û$q    CLĸdæ´{`¸ÊÚœ94ĸ¶≤W¿¸Ê Ëå•≤T@¸ÊÁs•K¿¸Ê›Ê›Ê fiÊ›Êò@@Ä
˜@Ä
˜
qk
±b
 `Ê
Ê@Ùˇ
ÄÊ˛Ùà
ÄÊ ÌÙ
ÄÊ¿Ù
ÄÊ ÒÙ"
ÄÊÔdÙ
ÄÊÔÙ
ÄÊÔÙà
ÄÊ @Ù
ÄÊÔê¯ˇÄÊ Ò
 "(˘
¢"ÄÊ˛ê
ÄÄÊÒ
â˛ê
ÄÄÊÚˇÚ˛òàì∂Ωú
ààÄÊ ÛÛfl˛ñ|>VR
ÄÄÊÚ˛ëƒ&R
ÄÄÊ Û0
¡
˛ˇÛ(g<Õí
¢"ÄÊÚx
˛

à˘
ÄÄÊÚÜ
˝Dà˘
ÄÄÊÚ_¸
˛à
âà˘
ààÄÊ Ûa¯p
˛˛
ÄÄÊÚ>¿
˛ˇˆ˛
ÄÄÊ Û
Ô˝>(ôœ3
¢"ÄÊÒ<˝}3z
ÄÄÊÏe3B
ÄÄÊÏàà]/:
ààÄÊ Ì˘
ÄÄÊϯˇÄÄÊ Ì"'¯ˇ¢"ÄÊÏÙ
ÄÊϸ
˚
ÄÊϸà
äò˚à
ÄÊ Ì¸
˚
ÄÊϸ
˚
ÄÊ Ì˚"2˚"
ÄÊϸ
˚
ÄÊϸ
P˚
ÄÊϸà
äò˚à
ÄÊ Ì¸
˚
ÄÊϸ
˚
ÄÊ Ì˚"2˚"
ÄÊϸ
˚
ÄÊϸ
P˚
ÄÊϸà
äò˚à
ÄÊ Ì¸
˚
ÄÊϸ
˚
ÄÊ Ì˚"2˚"
ÄÊϸ
˚
ÄÊϸ
\˚
ÄÊϸà
òå˚à
ÄÊ Ì¸
˚
ÄÊϸ
0˚
ÄÊ Ì¸"
#b˚"
ÄÊϸ

¿˚
ÄÊÏÙ
ÄÊÏÙà
ÄÊ ÌÙ
ÄÊÏÙ
ÄÊ ÌÙ"
ÄÊÏÙ
ÄÊÏÙ
ÄÊÏÙà
ÄÊò@Ä¿
˜Ä¿
˜
±k
Òb
 ̸ˇ‡¸
ÄÊ
ˆˇ¯˙¸ ¸
ÄÊ
 ˆ˙¸"3ˇÚ¸"
ÄÊ
ˆ˙¸¸
ÄÊ
ˆ˙¸¸
ÄÊ
ˆ
˚¸à⡸à
ÄÊ
 ˆ
˚¸¸
ÄÊ
ˆ
˚¸    ˇ–¸
ÄÊ 0˝
@˛
7ˆˇ‚,¸"
ÄÊ»˝
L¿˛
`ˆ ˇ–¸
ÄÊÅöq∏‹ÏÕΔv`ƒˆD`¸
ÄÊÇUJeÚK_/ü@»ˆà®âˇ¸à
ÄÊ äUJeKS)ò@`ˆ!¯¸
ÄÊqïq§Ú*O'w@7ˆˇ„»0¸
ÄÊ
 ˛@¸˚¸"
X˚"
ÄÊ 
˛@¸‡˚˝p ¸
ÄÊ
ˆ
˚˝``¸
ÄÊ
ˆ˙˝à䇻¸à
ÄÊ
 ˆ˙˝ˇˇÄ¸
ÄÊ
ˆ˙Ù
ÄÊ
 ˆˇ¸˙Ù"
ÄÊ
ˆˇ¸˙¸
‡˚
ÄÊÏ˝
 ¸
ÄÊϸàÀˇ¯¸à
ÄÊ Ì¸4‘†¸
ÄÊ˙~Ù˝
T†¸
ÄÊ ˚bÙ¸"„˜2¸"
ÄÊ˙BÙ˚˚
ÄÊ˙FÙ˚˚
ÄÊ˙JÙÙà
ÄÊ ˚BÙÙ
ÄÊ˙RÙÙ
ÄÊ ˚bÙÙ"
ÄÊ˙BÙÙ
ÄÊ˙FÙÙ
ÄÊ˙JÙÙà
ÄÊ ˚BÙÙ
ÄÊ˙RÙÙ
ÄÊ ˚bÙÙ"
ÄÊ˙BÙÙ
ÄÊ˙FÙÙ
ÄÊ˙JÙÙà
ÄÊ ˚BÙÙ
ÄÊ˙RÙÙ
ÄÊ ˚bÙÙ"
ÄÊ˙BÙÙ
ÄÊ˚
«¿ıÙ
ÄÊ˚
âÄıÙà
ÄÊ ˚√ÙÙ
ÄÊ˙vÙÙ
ÄÊ ˚<ÙÙ"
ÄÊ˙ÙÙ
ÄÊÏÙ
ÄÊÏÙà
ÄÊ Ì¯ˇÄÊÏ˘
ÄÄÊ
 ˆˇ¯˙"(˘
¢"ÄÊ
ˆ˙Ä˝
ÄÄÊ
ˆ˙
@

ÄÄÊ
ˆ˙àà
\ÈÉKsÄ
ààÄÊ
 ˆ˙
“õ«Ø…
ÄÄÊ
ˆ˙2ö4I
ÄÄÊ  

˙
?˙ˇˆ(<È√£»Ä
¢"ÄÊ ˚  ˙Ä˝
ÄÄÊò@¿

˜¿

˜
Òk1b
#mÁsÜmŒgp ˙
àÄ˝
ÄÄÊôìLâöì)Ù† ˘à˘
ààÄÊ$ âìLàöì)ц ˙
à˛
ÄÄÊ$y·Kájú…tê?˙ˇÛ˛
ÄÄÊ$
 ˛ÄIJ˙6(ôœ3
¢"ÄÊ$
˛Ä˛˙}3z
ÄÄÊ
ˆ˙e3B
ÄÄÊ
ˆ˙àà]/:
ààÄÊ
 ˆ˙˘
ÄÄÊ
ˆ˙¯ˇÄÄÊ
 ˆˇ¸@˛"'¯ˇ¢"ÄÊ
ˆˇ¸
@Ù
ÄÊÚ
ÁLY‹Ù
ÄÊÚîfi=}(Ùà
ÄÊ Ûî–!°(Ù
ÄÊÚÁN$Ù
ÄÊ ÚÑ˝Ù"
ÄÊÒÑ˝Ù
ÄÊÏÙ
ÄÊÏÙà
ÄÊ ÌÙ
ÄÊÏÙ
ÄÊ ÌÙ"
ÄÊÏÙˇ
ÄÊ›Ê›Ê fiÊ›Ê fiÊ›Ê›Ê›Ê fiÊ›Ê fiÊ›ÃÊfiUTÊ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡
«0@»
"H9¿»
b@@»
R8Ä»
ç–Ä»ò@

@
˜

@
˜1kqb

ÑòÄ»
ƒ>`9¿»¡¡¡¡¡*‡¿pÄ?@˝$IJ
 ˛
È'@89!àĸ IJ¸È+''£d
"
mÏí[x-Ç©J2Ù[    ◊bÑ≤Í+êM#G;<(Ái\È+')dä"¥ëRMêVÖw™U$≠U£J’*TêßU -HQ
ã®È+'I,úí"•dâêîâ%4âI)$•"\ôLî°ƒË\IHêë0È+'f9AM¢∂”`˘èJ^ømS
(™bêøV®·ãvs07XÈ+'N-89Ä‚I!$퇩
1îJHí“C*$H†˚t\Rp°…êȯ
BÙ ˝à˯
Bı

@˝à˘‡Bı

Ä˝pË¡¡ 88



‡@8˛Dfi
(
˛Äƒ¸@fi!Í›Ö0≠oâ÷∑+*î£/E±µµë≤2‰õfl!ï*#a)EQU5“TWz•RJ—
Zö≤“UEMfl!nR"^KÖíb&%“î‰íSHîíëRíñîâäIfl!(TD«Z    ÔO(V    6àٕΈ’0é§$6øŒìfl"'hd∫mÕ:íJ§ç$x£D§â q%%$Jâ@‡ı
˛
 ıćı
˛
 ıćÒ
 ”¡¡ê†@8˛H⁄Ä
ƒ¸@⁄∑≤:'—69∑+-)#.E±µµë≤2Ëõ€“EVJíöÑ“T^ı%TJ—
Zö≤“UIM€îIí—$í$Ñî‰î¶HòíëRíñîâíI€    6ä≥óµ&5    6à˘Kk¸’0é§$6ø⁄ì€$Ñ⁄…"$"$x¶2D®â q%%$Jë€ı
@œı
@œı
@œ¡¡¿ê`Üê1Ç@
Ä⁄ÄIJíêêJN@Ä⁄¢˛À—l:r@íêƇÍè÷B
Óí∫¿€    í¥Bïé·’*îöƒP/S@€    ,Ò%$§<.E ò‡S% $    é    rb@€∏:=µLHe!, U≠ñB$¬D≤¿€    -“)"Ht˜Cò¿…»i7$6yŒúçª$Ä€ˆ
˘Ÿˆ
˘Ÿˆ
˘Ÿ¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜qk±b
¡¡¡
ÄpÃ
Ä
àÃ
äR"
k)V±ÄŒ
ùÍRµw$®“ÄŒIL‚•%i»îÕRñÅHIÕ    5ÄŒÏdp‚J1hç" ŒIJ@
ÀIJ@
ÀIJ@…¡¡Ä
¿Õ@ÄÕÌ@Ñ@|Y%Äœ*†ä†à)"™RŒëq¡¿$êJ'DíŒ°◊
E[D^§Œ!h„ÓËœnC§DŒ˚»˚»¡¡¡ɇ¿¸ÄœA @
HÄœA± ‹∂
J/Ϻ¨–Å¿“ï!ZNPëIP–$îπRíœRP–Ç E5¢¶€É£⁄†–O»œ&fi9$Fí›"ë –¯ÄÀ¯ÄÀ¡¡¡¯
`0 ê
êH í?≠y,à ñaíêpà "fi§êà     ≥á'µ àê "˙%" r` ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜±kÒb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜Òk#b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜#kcb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜ck£b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜£k„b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜„k#b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜#kcb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜ck£b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜£k„b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜„kb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜#kcb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜ck£b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜£k„b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜„k#b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜#kcb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜ck£b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜£k„b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜„kb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇrB@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@ä.Introduction to Interapplication Communication4⁄ä˙(‡äSupporting P).)AppleScript and Other Scripting Languages

, (‡1-21
ˇˇˇˇˇˇˇˇ4^4|lòÄ2^A|rMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^A|r^A|r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
^6|@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""^6|@^6|@˜˜˜˜˜˜˜˜˜˜˜˜˜˙ˇˇ
˙ˇ
˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜
4Å4
w?òÄ
Å6
w@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""Å6
w@Å6
w@$˜
˙ˇ˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛
¸ˇ˛¸ˇ˝˚ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛
˙ˇ˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˛¸ˇˇ
ˇ˛ˇ˛˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˜˜˜˜
˙ˇ
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˛¸ˇˇ
ˇ˛ˇ˛˜˛˛ˇ˝
ˇˇˇ˛
ˇˇˇ˛    ˇˇˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜˙ˇ˛
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
˙ˇ˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˝˛ˇ˛
˛ˇ˛ˇˇ    ˇ¸
ˇ    ˇ¸
ˇ
˛ˇ˛ˇˇ˜˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜
¸ˇ˛˚ˇ˛
˝ˇ˝˚ˇ˛˚ˇ˛
˝ˇ˝˜˜˛˝ˇ˛ˇ˙˛ˇ˚
¸ˇ˛˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛ˇˇ˝˛ˇˇ˝
ˇˇˇ˛
ˇˇˇ˛˛˛ˇ˝ˇ˙˛¸ˇˇ
ˇ˛ˇ˛˜    
¸ˇˇ˜˛˛ˇ˝
ˇ˛ˇ˛
ˇ˛ˇ˛˛˛ˇ˝˜
¸ˇ˛¸ˇ˝˚ˇ˛
˝ˇ˝˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh¢(eäFigurR¿°dONLNd\¢h∂)e 1-1c†°dONLNd
\∂hª)
1c†°dONLNd\ªh
ì)1 shows one way that a script can be used to contrG¿°dONLNd<\
ìh
œ)ÿol two or mor´ °dONLNdI\
œh)<e applications. °dONLNdYiäu
ß(rä=When a user chooses the Post Invoice command in the accountin„`°dONLNdñi
ßu
„(r
ßg application,)`°dONLNd§i
‰u)=
 the user °dONLNdÆväÇ(äTaction handler for that menu command executes a default script for posting an invoic˜†°dONLNd
vÇ(e. °dONLNd
Éäè
g(åä3That script might describe actions such as saving tÔÄ°dONLNd
8É
gè)›(he invoice, updating the sales journal, °dONLNd
`êäú
F(ôä)and so on. The scripting component sends Í`°dONLNd
âê
Fú
…)ºApple events to the accountin≤°dONLNd
¶ê
 ú    )Ñg application t:`°dONLNd
µê
ú)@o °dONLNd
∑ùä©Ó(¶äperform these actions. 

ÀH‹4ÃH‹"ÃH]

ˇ·ˇ‚7^
    °dONLNd
œ¡äÃ∫*#Figure 1-11°dONLNd
€¡ÃÓ)B
PÄ¿°dONLNd
‹¡“Ã
œ)?osting an invoice and updating a database by executing a script
°dONLNdBäN»(KäThe accountinÊ`°dONLNd*B»N
    )>g application a,`°dONLNd9B

N)B:lso allows users to open the default invoice-posting scrip¿°dONLNdsBN)˚t in °dONLNdxOä[…(XäScript Editor a‡°dONLNdáO [
~)@*nd modify it so that additional actions arH¿°dONLNd±O
~[)¥!e performed when it is executed. °dONLNd“\äh˝(eäFor example, as shown in dONLNdÎ\˝h
)sFigurg`°dONLNd\
h
))e 1-1x@°dONLNdı\
)h
.)
1x@°dONLNdˆ\
.h
é), the script could instr´ °dONLNd\
éh)`uct the SurfDB application to °dONLNd,iäu(räXupdate a database of customer information in addition to performing the default posting °dONLNdÑväÇ
n*5actions. In this case, the scripting component sends $@°dONLNdπv
nÇ)‰"Apple events to both the accountin|¿°dONLNd€vÇ)ög °dONLNd›Éäè√(åäapplication a∂‡°dONLNdÍÉ√è
–)9?nd SurfDB to carry out all the actions described by the script.

‹â*4€à‹âò@@
˜@
˜‹â
Ä¡¡?›ˇ¯Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?ˡ‡ ˚ˇ¸Á?ˡ‡P˚ˇ¸Á?ˡ‡à˚ˇ¸Á?ˡ‡
˚ˇ¸Á?ˡ‡˚ˇ¸Á?ˡ‡
˚ˇ¸Á?ˡ‡Ä˚ˇ¸Á?ˡ‡@˚ˇ¸Á?ˡ‡  ˚ˇ¸Á?ˡ‡@˚ˇ¸Á?ˡ‡Ä˚ˇ¸Á?ˡ·˚ˇ¸Á?ˡ‚˚ˇ¸Á?ˡ‰
˚ˇ¸Á?ˡˇü˚ˇ¸Á?ˡ_˚ˇ¸Á?ˡË?˚ˇ¸Á?ˡ‰&_˚ˇ¸Á?ˡ‚9ü˚ˇ¸Á?ˡ·
œÒ˙ˇ¸Á?ˡ‡ÄF˙ˇ¸Á?ˡ‡@ ˙ˇ¸Á?ˡ‡ ˙ˇ¸Á?ˡ‡˙ˇ¸Á?ˡ‡¸˙ˇ¸Á?ˡ‡C˙ˇ¸Á?ˡ‡Ä˙ˇ¸Á?ˡ‡

˚ˇ¸Á?ˡ‡Ç˚ˇ¸Á?ˆˇ¸¸˙ˇ‡D˚ˇ¸Á?ˆˇ¸¸˙ˇ‡(˚ˇ¸Á?ˆˇ¸¸˙ˇ‡˚ˇ¸Á?˚ˇøˇˇˇ¸¸Ôˇ¸Á?˚ˇø˝ˇ¸¸Ôˇ¸Á?˚ˇ∏d«s«¸¸Ôˇ¸Á?˚ˇªd€g∑¸¸Ôˇ¸Áò@@Ä
˜@Ä
˜
â
\Ä?˚ˇªd€gḸÔˇ¸Á?˚ˇªd€gø¸¸Ôˇ¸Á?˚ˇªe€eø¸¸Ôˇ¸Á?ˆˇ¸¸Ôˇ¸Á?ˆˇ¸¸Ôˇ¸Á?ˆˇ¸¸Ôˇ¸Á?ˆˇ¸¸Ôˇ¸Á?›ˇ¸Á?¸ˇÄˆ?Ôˇ¸Á?¸ˇÄˆ?Ôˇ¸Á?¸ˇÄˆ?Ôˇ¸Á?¸ˇÄ@¿
IJ?Ôˇ¸Á?¸ˇÄG6@œ6yúp?Ôˇ¸Á?¸ˇÄM∂@Õ∂M¥ÿ?Ôˇ¸Á?¸ˇÄÕ∂@Õ∂M∞ÿ?Ôˇ¸Á?¸ˇÄœ∂@Õ∂M∞¯?Ôˇ¸Á?¸ˇÄL∂@Õ¥M¥»?Ôˇ¸Á?¸ˇÄG?ÄÕºyúp?Ôˇ¸Á?¸ˇÄˆ?Ôˇ¸Á?¸ˇÄˆ?Ôˇ¸Á?¸ˇÄˆ?Ôˇ¸Á?¸ˇÄˆ?Ôˇ¸Á?¸ˇÄˆ?Ôˇ¸Á?¸ˇÄÄ¿00`˛?Ôˇ¸Á?¸ˇÄ¿00˚?Ôˇ¸Á?¸ˇÄfifix3ƒŒg?Ôˇ¸Á?¸ˇÄ‹€03d€d∂?Ôˇ¸Á?¸ˇÄ€03d€d>?Ôˇ¸Á?¸ˇÄ€03d€d0?Ôˇ¸Á?¸ˇÄ€03dõd≤?Ôˇ¸Á?¸ˇÄ€3gg?Ôˇ¸Á?¸ˇÄˆ?Ôˇ¸Á?¸ˇÄˆ?Ôˇ¸Á?¸ˇÄˆ?Ôˇ¸Á?›ˇ¸Á?›ˇ¸Á?˚ˇ¯ˇˇ˛Ρ¸Á?˚ˇ˚ˇˡ¸Á?˚ˇ˚uflvÕˆoÔÏˇ¸Á?˚ˇ¯dœvM∂OgÏˇ¸Á?˚ˇ    ˚‰«vM∂O˜Ìˇ¸Á?˚ˇ    ˚‰ÁvM∂O˜Ìˇ¸Á?˚ˇ    ˚ı˜ˇvOˆoˇ˜Ìˇ¸Á?Úˇ
˜Óˇ¸Á?Úˇ˜Ìˇ¸Á?Úˇ˜Ìˇ¸Á?Úˇ˜Ìˇ¸Á?¸ˇ˜ÄÔˇ¸Á?¸ˇ˜ÄÔˇ¸Á?¸ˇ˜¿Ôˇ¸Á?¸ˇˆ
¿Ôˇ¸Á?¸ˇˆ
@Ôˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Áò@Ä¿
˜Ä¿
˜
\â
úÄ?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Áò@¿

˜¿

˜
úâ
‹Ä?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Áò@

@
˜

@
˜
‹âÄ?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?ˡIJ?˚ˇ¸Á?ˡᡡ¿?˚ˇ¸Á?ˡÑ@?˚ˇ¸Á?ˡÑ@?˚ˇ¸Á?ˡÑˇ˛@?˚ˇ¸Á?ˡÑîB@?˚ˇ¸Á?ˡÑˇ˛@?˚ˇ¸Á?ˡÑîB@?˚ˇ¸Á?ˡÑˇ˛@?˚ˇ¸Á?ˡÑò@?˚ˇ¸Á?ˡч¿?˚ˇ¸Á?ˡÑ¡0?˚ˇ¸Á?ˡÑÄ»?˚ˇ¸Á?ˡÖ?˚ˇ¸Á?ˡÜÚ?˚ˇ¸Á?ˡÑÅ©?˚ˇ¸Á?ˡàTø˚ˇ¸Á?ˡà"hø˚ˇ¸Á?ˡêB
Tø˚ˇ¸Á?ˡêDHø˚ˇ¸Á?ˡêÑI?˚ˇ¸Á?ˡêà G?˚ˇ¸Á?ˡë?¿?˚ˇ¸Á?ˡâ@?˚ˇ¸Á?ˡâ@?˚ˇ¸Á?ˡÑ@?˚ˇ¸Á?ˡÉ@?˚ˇ¸Á?ˡÅ@?˚ˇ¸Á?ˡÄê@?˚ˇ¸Á?ˡÄH ?˚ˇ¸Á?ˡÄ( ?˚ˇ¸Á?ˡć?˚ˇ¸Á?ˡÄ?˚ˇ¸Á?ˡIJ?˚ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Áò@
@
Ä
˜
@
Ä
˜â\Ä?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á?›ˇ¸Á›ˇ¸Á¡¡¡¡¡¡¡¡¡¡¡
«0    Ä»
"H:@»
b@@»
R8Ä»    ç–«    Ñò«
ƒ>`;¿»¡¡¡¡¡*‡A‡@
˛
¿0D
˝˝
@ÄÍ#    @89¿ê¯
@@

˝¸ÄÍ,('£d@í~vx]Öæ뱃TrÂ∑Çá.Z+ëDÑ“4z€¡G;U¿Í,()däÄ•ÑZê¶Ñ“©*ä“å∫•DŸ
T≠T)¨äu\ílÇàTzÄÍ+'I,úêÅ    xíë$àî GîÖì)àô    ô)ìÒ%NÖ§LÑáÑìÈ,f9˛!Å
ÊaÈç5S\5á%oÕ6˝Í¡Gh∑6õÅ∏ÂÄÍ+'N-89√Ñ˧·I    ""#ï&≈ô∫â.
©Lß9Ö∑E§óHôÈ˙

˘ ˚
˝Ä È˙

˘ ˚
˝Ä È˘‡˘ ˚˝˛ È¡¡988



‡@8˛DÅ$Å˛Ë
 ˛
˜5
(
˛Äƒ¸@

 

˛@
1¸˜;7Í›Ö0≠oâ÷∑+*î£/E±µµë≤2‰õ
o¨éâÙ[Aoä’JIã¢ÿ@Mz»Ìz-Ģ;7ï*#a)EQU5“TWz•RJ—
Zö≤“UEM5Uí§≠¢5+ΩJï%h@¶≠Y5*íVĢ;7nR"^KÖíb&%“î‰íSHîíëRíñîâäI&d¥I)"&9I)î&IHA$©K&D§îĢ;7(TD«Z    ÔO(V    6àٕΈ’0é§$6øŒìO"¨ÂÌSDO"zR›øjò#IO_∂©Ä˘:6'hd∫mÕ:íJ§ç$x£D§â q%%$JâFJ!6≤HíÜJQåí*DêâRãJ%$I¯ı
˛
 ıĘ
Ïı
˛
 ıĘ
ÏÒ
 Í
Ï¡¡¿ê`Üê1Ü@
Ä⁄ÄIJíêêJI@Ä⁄¢˛À—l:r@íêƇÍè÷I
Óí∫¿€    í¥Bïé·’*îö8éP/S@€    ,Ò%$§<.E ò‡S%    é    rb@€∏:=µLHe!, U≠ñF¬D≤¿€ò@
Ä
¿
˜
Ä
¿
˜\âúÄ    -“)"Ht˜Cò¿…»i7$6;Ãúçª$Ä€ˆ
˘Ÿˆ
˘Ÿˆ
˘Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡
ÄpÃ
Ä
àÃ
äR"
k)V±ÄŒ
ùÍRµw$®“ÄŒIL‚•%i»îÕRñÅHIÕ    5ÄŒÏdp‚J1hç" ŒIJ@
ÀIJ@
ÀIJ@…¡¡Ä
¿Õ@ÄÕÌ@Ñ@|Y%Äœ*†ä†à)"™RŒëq¡¿$êJ'DíŒ°◊
E[D^§Œ!h„ÓËœnC§DŒ˚»˚»¡¡¡ɇ¿¸ÄœA @
HÄœA± ‹∂
J/Ϻ¨–Å¿“ï!ZNPëIP–$îπRíœRP–Ç E5¢¶€É£⁄†–O»œ&fi9$Fí›"ë –¯ÄÀ¯ÄÀ¡¡¡¯
`0 ê
êH í?≠y,à ñaíêpà "fi§êà     ≥á'µ àê "˙%" r` ¡¡¡ò@
¿
Ú
˜
¿
Ú
˜úâŒÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜‹â
Ä
¡¡‹30Á‹Á ¬‹Á‹Á‹Á ¬‹Á ¬‹Á‹Á‹Á ¬Ê
@˘Á
 ÁeflÊAM‹˙ÁÊA_(˙ÁÊEQ(˙Á
 Á9O$fl‹Á ¬‹Á‹Á‹Á ¬‹Á Ê fi
ÂP˘Á
Âà˘ÁÊ

˘Á     Á
fiÊ

˘Á
 ÁÄflÊ@˙ÁÊ  ˙ÁÊ@˙Á
 ÁÄflÁ
˙Á ËflÁ
˙ÁÁ‡Ä˚ÁÁ@˚Á Ë ‡Á&@˚Á Ë9ćÁ

œÒ‡˚ÁÊÄF‡˚ÁÊ@ ‡˚Á Á ‡‡Ê‡˚Á Á¸‡‡ÊC‡˚ÁÊć˚ÁÊ


˘Á ÊÇfi˚˚ˇ¸ÚD˘Á ¸˚ˇ¸Ú(fi˚˚ˇ¸Ú˘Á˚ˇøˇˇˇ¸ÈÁ˚
ˇø˝ˇ¸ÈÁ ¸ˇ∏d«s«¸Œ˚ˇªd€g∑¸ÈÁò@@Ä
˜@Ä
˜
â
\Ä
 ¸ˇªd€gḌ˚ˇªd€gø¸˜˛@ ˝Á˚ˇªe€eø¸˜˛Ä@˝Á˚˚ˇ¸˜
ö]‹qùÃÃʇ˛Á ¸˚ˇ¸˜
&fR“ì”->iê„˚˚ˇ¸˜
¢&R“íS-iê˛Á ¸˚ˇ¸˜
ùŸ“Rq›ÃÓ&ê„˚ıˇ¯
˙Á˚Ĉ0¯
‡˙Á˚Ĉ0ÔÁ ¸Äˆ0‘˚Ä@¿
IJ0ÔÁ ¸ÄG6@œ6yúp0‘˚ÄM∂@Õ∂M¥ÿ0ÔÁ˚ÄÕ∂@Õ∂M∞ÿ0ÔÁ˚Äœ∂@Õ∂M∞¯0ÔÁ ¸ÄL∂@Õ¥M¥»0‘˚ÄG?ÄÕºyúp0ÔÁ ¸Äˆ0‘˚Ĉ0ÔÁ˚Ĉ0Ûˇ
ÄÁ˚Ĉ0Ûà
ÄÁ ¸Äˆ0ÛÄÊ˚ÄÄ¿00`˛0Û
ÄÁ ¸Ä¿00˚0Û"ÄÊ˚Äfifix3ƒŒg0Û
ÄÁ˚Ä‹€03d€d∂0Û
ÄÁ˚Ä€03d€d>0Ûà
ÄÁ ¸Ä€03d€d00ÛÄÊ˚Ä€03dõd≤0¯ˇÄÄÁ  ¸Ä€3gg0"$¯‚""ÄÊ˚Ĉ0ê˛¿ÄÁ˚Ĉ0ê˛¿ÄÁ˚Ĉ0àåì∂‹‹»ààÄÁ ¸ıˇñ|=-2¿ÄÊ˚ıˇëƒ%2¿ÄÁ& ¸ˇ¯ˇˇ˛˛ˇ˛ˇ˚$g<‰“‚""ÄÊ˚ˇ˚ˇ˚ˇÄ
ѯ¿ÄÁ˚ˇ˚uflvÕˆoÔˇˇƒ˛Dƒ¯¿ÄÁ˚ˇ¯dœvM∂Ogˇˇ˝àï»ààÄÁ& ¸ˇ˚‰«vM∂O˜ˇÄ
Ñ
IJ¿ÄÊ%˚ˇ˚‰ÁvM∂O˜ˇ˛ˇ˚
IJ¿ÄÁ& ¸ˇ˚ı˜ˇvOˆoˇ˜ˇ.$ç«õ˛‚""ÄÊ˚˜ˇ˜_)æ˛¿ÄÁ˚˜ˇ˜ˇS)¢˛¿ÄÁ˚˜ˇ˜ˇàåO'û˛»ààÄÁ ¸˜ˇ˜ˇ¯¿ÄÊÒ
IJ¯¿ÄÁ Ú
IJ"'¯ˇ‚""ÄÊÒ
¿˛¯ˇ¿ÄÁ¿˛Û
ÄÁ@˛¸à
ã¯˙à
ÄÁ ̸
˙ÄÊϸ
˙
ÄÁ Ì˚"*˙"ÄÊϸ
˙
ÄÁϸ
H˙
ÄÁϸàä˘à
ÄÁ ̸
˙ÄÊϸ
˙
ÄÁ Ì˚"*˙"ÄÊϸ
˙
ÄÁϸ
H˙
ÄÁϸàä˘à
ÄÁò@Ä¿
˜Ä¿
˜
\â
úÄ
 ̸
˙ÄÊϸ
˙
ÄÁ Ì˚"*˙"ÄÊϸ
˙
ÄÁϸ
H˙
ÄÁϸà
éé˙à
ÄÁ ̸
˙ÄÊϸ
˙
ÄÁ ̸"
#2˙"ÄÊϸ

‡˙
ÄÁÏ˚¿˙
ÄÁÏÛà
ÄÁ ÌÛÄÊÏÛ
ÄÁ ÌÛ"ÄÊÏÛ
ÄÁÏÛ
ÄÁϸà
ˇˇ˙à
ÄÁ ̸¿Ä˚ÄÊϸO˛Ä˚
ÄÁ
 ˆˇ¸˙¸"@‚˚"ÄÊ
ˆ˙¸O¸@˚
ÄÁ
ˆ˙¸`@˚
ÄÁ
ˆ˙¸àߡH˚à
ÄÁ
 ˆ
˚¸ @˚ÄÊ
ˆ
˚¸ @˚
ÄÁ ˝
 ˛
˜ˇ˛"/ˇb˚"ÄÊd˝
F`˛
0˜ @˚
ÄÁ@⁄9úŒÊlÊ;`dˆD/¸@˚
ÄÁA5&SÈEæüO¿H˜àå臻˚à
ÄÁ E5&S    E≤ôL@`˜@Ä˚ÄÊ8’9íÈ%.ó;¿1˜¿Ä˚
ÄÁ
 ˛ ¸˜ˇ˛3Ä
¢˚"ÄÊ
˛ ¸p˚˝Ä˙
ÄÁ
ˆ
˚˝˙
ÄÁ
ˆ˙˝àèˇ¸˙à
ÄÁ
 ˆ˙ÛÄÊ
ˆ˙˝

˘
ÄÁ
 ˆˇ˛˙˝"
*¢˘"ÄÊ

ˆˇ˛˙˝7w˙
ÄÁÏ˝
ÕJ˙
ÄÁϸà
Õ ˙à
ÄÁ ˚Ù˝=q˙ÄÊ˙QÙ˚@˙
ÄÁ ˚cÙ˚"b˙"ÄÊ˙AÙÛ
ÄÁ˙EÙÛ
ÄÁ˙IÙÛà
ÄÁ ˚AÙÛÄÊ˙QÙÛ
ÄÁ ˚cÙÛ"ÄÊ˙AÙÛ
ÄÁ˙EÙÛ
ÄÁ˙IÙÛà
ÄÁ ˚AÙÛÄÊ˙QÙÛ
ÄÁ ˚cÙÛ"ÄÊ˙AÙÛ
ÄÁ˙EÙÛ
ÄÁ˙IÙÛà
ÄÁ ˚AÙÛÄÊ˙QÙÛ
ÄÁ ˚cÙÛ"ÄÊ˙AÙÛ
ÄÁò@¿

˜¿

˜
úâ
‹Ä
˙EÙÛ
ÄÁ˚
…¿ıÛà
ÄÁ ¸
Ä¿ıÛÄÊ˙
—ÄıÛ
ÄÁ ˚cÙÛ"ÄÊ˙6ÙÛ
ÄÁ˙ÙÛ
ÄÁÏàè¯ˇ˛à
ÄÁ
 
ˆˇ˛˙¯¿ÄÊ

ˆ˙¯¿ÄÁ
 
ˆ˙"$˛IJ‚""ÄÊ

ˆ˙˛(IJ¿ÄÁ

ˆ˙˛)‹∞˛¿ÄÁ

ˆ˙åå˛92¯˛»ààÄÁ
 
ˆ˙˛E2¿˛¿ÄÊ

ˆ
˙ˇ
˚˛E‹∏˛¿ÄÁ
 
ˆ
˙

§˛

˝‚""ÄÊ

ˆ
˘ƒ˛

˝¿ÄÁ

ˆ
˘ƒ¯¿ÄÁ

ˆ
˙

å˝    @P»ààÄÁ
 
ˆ
˙ˇ
˚˛    @P¿ÄÊ

ˆ˙ñÁqπ”`¿ÄÁ
 
ˆ˙.$_íKÊW¿‚""ÄÊ

ˆ˙híJfT@¿ÄÁ

ˆ˙GëI”¿¿ÄÁ

ˆ˙à寻ààÄÁ
 
ˆ˙¯ˇ¿ÄÊ

ˆ˙¯ˇ¿ÄÁ
 
ˆ˙Û"ÄÊ

ˆ 
˝Û
ÄÁ

ˆP
˛
@Û
ÄÁ

ˆSπ`…nÓÛà
ÄÁ
 
ˆreÒ¢XÛÄÊ

ˆäeÅâFÛ
ÄÁ
 
ˆãπp‰y<Û"ÄÊ

ˆ ˝Û
ÄÁ

ˆ ˝¯ˇÄÄÁ

ˆ˙à寻ààÄÁ
 
ˆ˙˛IJ¿ÄÊ

ˆ˙˛(IJ¿ÄÁ
 
ˆ˙.$˛)‹∞˛‚""ÄÊ

ˆ˙˛92¯˛¿ÄÁ

ˆ
˙ˇ
˚˛E2¿˛¿ÄÁ

ˆ
˙

å˛E‹∏˛»ààÄÁ
 
ˆ
˘ƒ˛

˝¿ÄÊ

ˆ
˘ƒ˛

˝¿ÄÁ
 
ˆ
˙

§¯‚""ÄÊ

ˆ
˙ˇ
˚˝    @P¿ÄÁ

ˆ˙˛
@P¿ÄÁ

ˆ˙ååñÁqπ”`»ààÄÁ
 
ˆ˙_íKÊW¿¿ÄÊ

ˆ˙híJfT@¿ÄÁ
 
ˆ˙"$GëI”¿‚""ÄÊ

ˆ˙¯¿ÄÁ

ˆ˙¯ˇ¿ÄÁ

ˆ˙àã¯ˇ»ààÄÁ
 
˝p˝˙ÛÄÊ

˝à˝˙Û
ÄÁ
 
˝ckªé˛˙Û"ÄÊ

˝ ZR˛˙Û
ÄÁ

˝åJZR˛˙Û
ÄÁ

˝sÀäN˛˙Ûà
ÄÁ
 
¸˛˙ÛÄÊ

¸˛˙Û
ÄÁò@

@
˜

@
˜
‹âÄ

 
ˆ˙Û"ÄÊ

ˆ˙Û
ÄÁ

˘ ˙Ûˇ
ÄÁ

˛mŒgpÍÁ
 
˛    öì)Ù†œ

˛öì)цÍÁ
 
˛jú…têœ

¸¸ÍÁ

¸¸ÍÁ

ˆÍÁ    
 
ˆœ

ˆÍÁ    
 
ˆœ

ˆÍÁ

ˆÍÁ

ˆÍÁ
 
ˆ˜`ˇˇ¿fl

ˆ˜p@˙Á
 
ˆ
¯ˇÿ@fl

ˆ
¯ˇ˛@˙Á

ˆ
¯îB@˙Á

ˆ
¯ˇ˛@˙Á
 
ˆ
¯îB@fl

ˆ
¯ˇÃˇ˛@˙Á
 
ˆ˜Xò@fl

ˆ˜p‡¿˙Á

ˆ˜`¡0˙Á

ˆıÄ»˙Á
 
ˆıfl

ˆıÚ˙Á
 
ˆıÅ©fl

ˆ@˙TÄ˚Á

ˆ@˝"hÄ˚Á

ˆ    ÓX2[ªÄ˛B
TÄ˚Á
 
ˆô|y~V˝DHć

ˆ    "ô`A¢QIJÑI˙Á
 
ˆ"Ó\9O˝à Gfl

ˆ˛à˘?¿˙Á

ˆ˛à˘    @˘Á

ˆı    @˘Á
 
ˆ˜`@fi

ˆ˜p@˘Á
 
ˆ
¯ˇÿ
@fi

ˆ
¯ê@˘Á

ˆ
¯H ˘Á

ˆ
¯( ˘Á
 
ˆ
¯‡fi

ˆ
¯ˇÃ¯Á
 
ˆ˜X⁄

ˆ˜pıÁ

ˆ˜`ıÁ

ˆÍÁ    
 
ˆœ

ˆı
¿<˙Á
 
ˆı ¢fl

ıˇı
캢˙Á
ıˇÙsº˙ÁÁ3¢˙Á Ë
œ<fl‹Á ¬‹Á‹Á‹Áò@
@
Ä
˜
@
Ä
˜â\Ä
 ¬‹Á ¬‹Á‹Á‹Á ¬‹Á ¬‹ÃÁ›UTÁ¡¡¡¡¡¡¡¡¡¡¡
«0    Ä»
"H:@»
b@@»
R8Ä»    ç–«    Ñò«
ƒ>`;¿»¡¡¡¡¡*‡A‡@
˛
¿0D
˝˝
@ÄÍ#    @89¿ê¯
@@

˝¸ÄÍ,('£d@í~vx]Öæ뱃TrÂ∑Çá.Z+ëDÑ“4z€¡G;U¿Í,()däÄ•ÑZê¶Ñ“©*ä“å∫•DŸ
T≠T)¨äu\ílÇàTzÄÍ+'I,úêÅ    xíë$àî GîÖì)àô    ô)ìÒ%NÖ§LÑáÑìÈ,f9˛!Å
ÊaÈç5S\5á%oÕ6˝Í¡Gh∑6õÅ∏ÂÄÍ+'N-89√Ñ˧·I    ""#ï&≈ô∫â.
©Lß9Ö∑E§óHôÈ˙

˘ ˚
˝Ä È˙

˘ ˚
˝Ä È˘‡˘ ˚˝˛ È¡¡988



‡@8˛DÅ$Å˛Ë
 ˛
˜5
(
˛Äƒ¸@

 

˛@
1¸˜;7Í›Ö0≠oâ÷∑+*î£/E±µµë≤2‰õ
o¨éâÙ[Aoä’JIã¢ÿ@Mz»Ìz-Ģ;7ï*#a)EQU5“TWz•RJ—
Zö≤“UEM5Uí§≠¢5+ΩJï%h@¶≠Y5*íVĢ;7nR"^KÖíb&%“î‰íSHîíëRíñîâäI&d¥I)"&9I)î&IHA$©K&D§îĢ;7(TD«Z    ÔO(V    6àٕΈ’0é§$6øŒìO"¨ÂÌSDO"zR›øjò#IO_∂©Ä˘:6'hd∫mÕ:íJ§ç$x£D§â q%%$JâFJ!6≤HíÜJQåí*DêâRãJ%$I¯ı
˛
 ıĘ
Ïı
˛
 ıĘ
ÏÒ
 Í
Ï¡¡¿ê`Üê1Ü@
Ä⁄ÄIJíêêJI@Ä⁄¢˛À—l:r@íêƇÍè÷I
Óí∫¿€    í¥Bïé·’*îö8éP/S@€    ,Ò%$§<.E ò‡S%    é    rb@€∏:=µLHe!, U≠ñF¬D≤¿€ò@
Ä
¿
˜
Ä
¿
˜\âúÄ
    -“)"Ht˜Cò¿…»i7$6;Ãúçª$Ä€ˆ
˘Ÿˆ
˘Ÿˆ
˘Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡
ÄpÃ
Ä
àÃ
äR"
k)V±ÄŒ
ùÍRµw$®“ÄŒIL‚•%i»îÕRñÅHIÕ    5ÄŒÏdp‚J1hç" ŒIJ@
ÀIJ@
ÀIJ@…¡¡Ä
¿Õ@ÄÕÌ@Ñ@|Y%Äœ*†ä†à)"™RŒëq¡¿$êJ'DíŒ°◊
E[D^§Œ!h„ÓËœnC§DŒ˚»˚»¡¡¡ɇ¿¸ÄœA @
HÄœA± ‹∂
J/Ϻ¨–Å¿“ï!ZNPëIP–$îπRíœRP–Ç E5¢¶€É£⁄†–O»œ&fi9$Fí›"ë –¯ÄÀ¯ÄÀ¡¡¡¯
`0 ê
êH í?≠y,à ñaíêpà "fi§êà     ≥á'µ àê "˙%" r` ¡¡¡ò@
¿
Ú
˜
¿
Ú
˜úâŒÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜ŒâÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜âNÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜NâéÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜éâŒÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜ŒâÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜âNÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜NâéÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜éâ¿Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜ŒâÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜âNÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜NâéÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜éâŒÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜ŒâÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜âNÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜NâéÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜éâ¿Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇñ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
1,    Helvetica    ˇˇ—ÚˇÆ(@l.Introduction to Interapplication Communication4⁄*˙
¯

(‡*1-22    )BExchanging Message Blocks4^*¿
¯
°dONLNd\lhÄ(elTher¿°dONLNd\Åh
7)-e is no limit to the actions such a script ca}°dONLNd1\
7h
f)∂n describe.@°dONLNd<\
gh
Œ)0 In addition to sending °dONLNdTilu|(rlthe °dONLNdXi|u‰)Apple events shown in Ï¿°dONLNdni‰u¸)hFigurøÄ°dONLNdsi¸u
)e 1-1–`°dONLNdxi
u
)
1–`°dONLNdyi
u
◊)., the invoice-posting script could be used to °dONLNdßvlÇå(ltrigger ôÄ°dONLNdØvåÇ
ã) :Apple events that cause other applications to perform a crj@°dONLNdÈv
åÇ
Â(
åedit check, send the °dONLNd˛Élè˚(ål!invoice to the customer by electrìÄ°dONLNd
É˚è
F)èonic mail, forwar/¿°dONLNd
0É
Gè
À)Ld inventory information to a r8`°dONLNd
NÉ
Àè
Ë)Ñemote °dONLNd
Têlúˇ(ôl!server on the network, and so on.°dONLNd
v¢lÆ
Ë*SThe chapter “Scripting Components” in this book describes how your application can °dONLNd
…ØlªØ*use the standarú†°dONLNd
ÿØت
)Cd scripting component rÛ °dONLNd
ÔØ
ª
ı)j2outines to manipulate and execute its own scripts °dONLNd!ºl»
(≈l)and allow users to modify those scripts. …‡°dONLNdJº
»
 )≤
 I‡°dONLNdKº
!»
#)
 

œ*Í
¯4–*Í
¯

˙*

¯4˚*

¯ ¸*¸
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNdNÁ*˙Ù(ı*Exchanging Message BlocksˇˇˇˇˇˇV˛(ı

1
°dONLNdi
l
r(
l
Y@Ä°dONLNdj
r
‡)ou should be able to meev@°dONLNdÇ
‡
Ó)nt m†°dONLNdÖ
Ô

ø)/ost of your application’s IAC needs by using th6°dONLNd¥

ø

Δ)–e !@°dONLNd∂

Δ

”)Ap͆°dONLNd∏

”

„)ple °dONLNdº
l
$∑(
!lEvent Manager o&‡°dONLNdÀ
∏
$¡)Lr t€‡°dONLNdŒ
¡
$
)    he Event Manager͇°dONLNdfi


$
?)P    . HoweverwÄ°dONLNdÁ

?
$
∫)., if you need low-level contr`°dONLNd

ª
$
À)|ol od¿°dONLNd

À
$
’)r s`°dONLNd

÷
$
˜)ervices °dONLNd
%l
1Ü(
.lnot prP`°dONLNd
%á
1Æ)ovided b]@°dONLNd!
%Æ
1Δ)'y the k`°dONLNd'
%Δ
1
/)Apple Event Manager o¿°dONLNd<
%
0
1
ä)jr the Event Manager”¿°dONLNdO
%
â
1
Í)Y, you can use the PPC °dONLNde
2l
>r(
;l
Tµ¿°dONLNdf
2q
>¬)oolbox. The PPC T †°dONLNdw
2¬
>
+)Qoolbox lets you send lar¢°dONLNdè
2
+
>
fl)i)ge amounts of data to other applications °dONLNd∏
?l
K
(
Hl#located on the same computer or acr”¿°dONLNd€
?

K
})†oss a network. The PPC T
†°dONLNdÛ
?
}
K
ı)qoolbox can also be used by °dONLNd
Ll
X…(
Ulpieces of code that arZ†°dONLNd$
L…
X
N)]e not event-driven. The PPC T¢`°dONLNdA
L
M
X
‘)Ñ oolbox is usually called by the °dONLNda
Yl
e
Ù(
blYOperating System; device drivers, desk accessories, or other code modules can also use itÎ`°dONLNd∫
Y
Ù
e
ˆ(
b
Ù
.°dONLNdº
kl
wr(
tl
Y@Ä°dONLNdΩ
kr
wµ)ou cannot use tX °dONLNdÃ
kµ
w›)Che PPC TS °dONLNd‘
k›
w
U)(oolbox to send data betwee”‡°dONLNdÓ
k
U
w
π)xn applications unless b•@°dONLNd
k
∫
w
‹)eoth you∫@°dONLNd
k
‹
w
‚)"r °dONLNd
xl
Ñ•(
Ålapplication a∂‡°dONLNd
x•
Ѻ)9nd th7¿°dONLNd 
xΩ
Ñ˛)e application yG`°dONLNd/
x˛
Ñ
)Aou’rP@°dONLNd3
x

Ñ
~)e communicating with ar¸ °dONLNdJ
x
~
Ñ
Î)ne open at the same time. °dONLNdc
Öl
ër(
él
Tµ¿°dONLNdd
Öq
ë

) o initiate communication, one prå@°dONLNdÑ
Ö


ë
d)êogram opens a port an% °dONLNdô
Ö
e
ë
q)dd rÖ‡°dONLNdú
Ö
q
ë
ô)    equests aı¿°dONLNd•
Ö
ô
ë
‘)( session with °dONLNd≥
íl
ûö(
õl
another prfi°dONLNdΩ
íö
û€).ogram. The tarÏ`°dONLNdÀ
í€
û
«)A6get application must also open a port and accept the rq °dONLNd

í
»
û
È)Ìequest. °dONLNd    
ül
´
(
®l)Once a session is established, the two prч°dONLNd2
ü

´
V)±ograms can rì¿°dONLNd>
ü
V
´
È)9 ead and write low-level message °dONLNd^
¨l
∏à(
µlblocks°‡°dONLNdd
¨à
∏ç). °dONLNdg
æl
 õ(
«l    The PPC Tõ¿°dONLNdp
æö
 ÿ).oolbox also prˆ‡°dONLNd~
æÿ
 
 )>ovides a standarN‡°dONLNdé
æ
!
 
Î)I/d user interface that allows a user working in °dONLNdΩ
Àl
◊
Ì(
‘lWone application to select another application with which to exchange data, whether the °dONLNd
ÿl
‰
*&communication is achieved by means of LJ°dONLNd:
ÿ

‰
‘)≥*Apple events, other high-level events, or °dONLNdd
Âl
Ò≤(
Ólmessage blocks.°dONLNdt
˜lr*
T†¿°dONLNdu
˜r±)he chapter “PrL¿°dONLNdÉ
˜≤Ë)@ogram-to-PrF@°dONLNdé
˜Ë
\)6ogram Communications T[Ä°dONLNd§
˜
[
‚)soolbox” in this book describes °dONLNd√lq(l
hQ`°dONLNdƒrå)ow pre°dONLNd…å)ograms can exchange lu@°dONLNdfi
X)dow-level message blockı °dONLNdÙ
X
^)hs.≤ °dONLNdˆ
_
a)
 2 °dONLNd˜
b
d)
 ≤ °dONLNd¯
d
f)
 2 °dONLNd˘
g
i)
 ˇ †@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,    Helvetica    .
(‡∫Contents,Palatino

, (‡    2-1    3,Ã(#∫CHAPTER ÿ)h
2
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜ˇˇˇˇˇˇ(JH
Figure 2-0*    Listing 2-0*    
T)able 2-0

zH
,
4zH
, 
H
°dONLNd
∫
*˘+m Contentsˇˇˇˇˇˇ

ˇ·ˇ‚7^ˇˇ∫Ρ◊(qH
2°dONLNd[∫x
)rEdition Manager
°dONLNd
;∫
G *”Intr∑@°dONLNd
; 
Gˇ)oduction to È`°dONLNd)
;ˇ
G
¢)5%Publishers, Subscribers, and Editionsm`°dONLNdP
;
∑
G
ƒ)∏2-4°dONLNdT
H∫
T
3(
Q∫About the Edition Manager¿°dONLNdo
H
H
T
Z)é2-12°dONLNdt
U∫
a
1(
^∫Using the Edition ManagerN°dONLNdè
U
F
a
X)å2-12°dONLNdî
bƒ
nÚ(
kƒ
Receiving *†°dONLNdû
bÚ
n
9).Apple Events Frÿ†°dONLNd≠
b
9
n
§)Gom the Edition Manager£°dONLNd≈
b
π
n
À)Ä2-13°dONLNd 
oƒ
{œ(
xƒCr\°dONLNdÃ
oœ
{
8)eating the Section Recor‡°dONLNd‰
o
9
{
U)jd and Δ`°dONLNdÍ
o
T
{
Ü)Alias Recor=¿°dONLNdı
o
á
{
ç)3
dYÄ°dONLNd¯
o
°
{
≥)2-15°dONLNd˝
|ƒ
à
u(
Öƒ%Saving a Document Containing Sections’Ä°dONLNd
$
|
â
à
õ)≈2-19°dONLNd
)
âƒ
ï
µ(
íƒ2Opening and Closing a Document Containing SectionsP`°dONLNd
]
â
 
ï
‹(
í
 2-22°dONLNd
b
ñƒ
¢
(
üƒReading and Wå°dONLNd
o
ñ

¢
J)Driting a Section›Ä°dONLNd
Å
ñ
^
¢
p)V2-24°dONLNd
Ü
£Œ
Ø
-(
¨ŒFormats in an Editiong@°dONLNd
ù
£
B
Ø
T)t2-24°dONLNd
¢
∞Œ
º
%(
πŒOpening an Edition§¿°dONLNd
∂
∞
9
º
K)k2-26°dONLNd
ª
ΩŒ
…
(
ΔŒFormat MarksA†°dONLNd
…
Ω
!
…
3)S2-27°dONLNd
Œ
 Œ
÷
(
”ŒReading and Wå°dONLNd
€
 

÷
d)Driting Edition DataÉ`°dONLNd

 
y
÷
ã)g2-27°dONLNd
ı
◊Œ
„
 (
‡ŒClosing an Edition›†°dONLNd    
◊
4
„
F)f2-28°dONLNd
‰ƒ
œ(
̃Cr\°dONLNd
‰œ

)eating a Publisher䠡dONLNd$
‰
2

D)c2-29°dONLNd)
Ҍ
˝Ÿ(
˙ŒCr\°dONLNd+
ÒŸ
˝
V)eating the Edition Container∂°dONLNdI
Ò
j
˝
|)ë2-32°dONLNdN
˛Œ

k(Œ!Opening an Edition Container to W5Ä°dONLNdo
˛
k

ë)ù    rite Dataú °dONLNdz
˛
•

∑):2-35°dONLNdƒœ(ƒCr\°dONLNdÅœ
")eating a SubscriberKÄ°dONLNdñ
7
I)h2-37°dONLNdõŒ$
è(!Œ)Opening an Edition Container to Read Data‡°dONLNdΔ
§$
∂)÷2-41°dONLNdÀ%Œ1
Å(.Œ%Choosing Which Edition Format to Read?°dONLNdÚ%
ñ1
®)»2-41°dONLNd˜2ƒ>
u(;ƒ&Using Publisher and Subscriber Options@°dONLNd2
ä>
ú)Δ2-43°dONLNd$?ŒK
∂(HŒ1Publishing a New Edition While Saving or Manuallyq¿°dONLNdW?
ÀK
›)˝2-47°dONLNd\LŒX
@(UŒSubscribing to an Edition c†°dONLNdvL
@X
∏)rAutomatically or ManuallyŒÄ°dONLNdëL
ÃX
fi)å2-48°dONLNdñYŒe
-(bŒCanceling Sections Wo °dONLNd™Y
-e
v)_ithin Documents=Ä°dONLNdªY
ãe
ù)^2-48°dONLNd¿fŒr
;(oŒLocating a Publisher Thrw†°dONLNdÿf
;r
ä)mough a SubscriberÔ`°dONLNdÎf
ûr
∞)c2-49°dONLNdsƒ
Ñ(|ƒ'Renaming a Document Containing SectionsÄ°dONLNds
ô
´)’2-50°dONLNdăå
w(âƒ'Displaying Publisher and Subscriber Bor6‡°dONLNdEÄ
xå
ã)¥dersK‡°dONLNdKÄ
üå
±)'2-50°dONLNdPçŒô‘(ñŒ
Tµ¿°dONLNdQç”ôÚ)ext Bor¿†°dONLNdXçÚô
)ders’†°dONLNd^ç
ô
+)'2-54°dONLNdcöŒ¶›(£ŒSpr܇°dONLNdfö›¶
)eadsheet Bor&Ä°dONLNdrö
¶
))9ders;Ä°dONLNdxö
=¶
O)'2-55ˇû@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+ú"CHAPTER à)>
24⁄*˙
¯
(‡*2-2,    Helvetica    )rContents4^*¿
¯
°dONLNd\∞h
3(e∞Object-Oriented Graphics Bor◊ °dONLNd\
3h
F)ÉdersÏ °dONLNd"\
Zh
l)'2-56°dONLNd'i∞u
(r∞Bitmapped Graphics Bor◊@°dONLNd=i
u
0)mdersÏ@°dONLNdCi
Du
V)'2-57°dONLNdHv∞Ç
^(∞&Duplicating Publishers and Subscribers»@°dONLNdpv
rÇ
Ñ)¬2-58°dONLNduɶè
(å¶Modifying a Subscriber5`°dONLNdçÉ
"è
4)|2-59°dONLNdíê¶ú
(ô¶Relocating an Edition≥‡°dONLNd©ê
ú
+)s2-60°dONLNdÆù¶©
(¶¶Customizing Dialog BoxesÎ`°dONLNd»ù
/©
A)â2-60°dONLNdÕ™ú∂
,(≥ú Subscribing to Non-Edition Files¿¿°dONLNdÔ™
@∂
R)§2-62°dONLNdÙ∑¶√Ô(¿¶Getting the CurrkÄ°dONLNd
∑Ô√
C)Ient Edition Opener†°dONLNd
∑
X√
j)i2-63°dONLNd
ƒ¶–
(Õ¶Setting an Edition Openero °dONLNd
8ƒ
-–
?)á2-63°dONLNd
=—¶›
(⁄¶Calling an Edition Opener»¿°dONLNd
X—
.›
@)à2-64°dONLNd
]fi¶Í
+(Á¶Opening and Closing Editionsx@°dONLNd
{fi
@Í
R)ö2-68°dONLNd
Äζ˜
P(Ù¶&Listing Files That Can Be Subscribed TƆ°dONLNd
¶Î
O˜
T)©
o$ °dONLNd
©Î
i˜
{)2-68°dONLNd
Ư¶
÷(

¶
Reading Fr0`°dONLNd
∏¯◊

)1om and W©†°dONLNd
¿¯


>)-riting to Files.@°dONLNd
—¯
S

e)O2-68°dONLNd
÷
¶

-(
¶Calling a Format I/O FunctionQ`°dONLNd
ı

B

T)ú2-68°dONLNd
˙
ú

(
úEdition Manager Refer˝†°dONLNd



)dence“Ä°dONLNd

(

:)(2-71°dONLNd
¶
+…(
(¶Data Str``°dONLNd"
 
+·)$ucturÊ@°dONLNd'
·
+Í)esχ°dONLNd+
˛
+
)2-71°dONLNd0
,∞
8
.(
5∞The Edition Container RecorÖ‡°dONLNdK
,
.
8
4)~
d°†°dONLNdN
,
H
8
Z)2-71°dONLNdS
9∞
E˛(
B∞The Section RecorI`°dONLNdd
9ˇ
E
)O
de °dONLNdg
9

E
+)2-72°dONLNdl
F¶
R
(
O¶Edition Manager Routines–‡°dONLNdÜ
F
.
R
@)à2-73°dONLNdã
S∞
_
=(
\∞ Initializing the Edition Manager]Ä°dONLNd≠
S
R
_
d)¢2-74°dONLNd≤
`∞
lª(
i∞Cr\°dONLNd¥
`ª
l
H) eating and Registering a Section¸‡°dONLNd÷
`
\
l
n)°2-74°dONLNd€
m∞
yª(
v∞Cr\°dONLNd›
mª
y
p)(eating and Deleting an Edition Container[@°dONLNd
m
Ö
y
ó) 2-79°dONLNd
z∞
Ü
J(
É∞!Setting and Getting a Format Mark
 °dONLNd/
z
_
Ü
q)Ø2-81°dONLNd4
á∞
ì
(
ê∞Reading in Edition Data' °dONLNdM
á
/
ì
A)2-83°dONLNdR
î∞
†∫(
ù∞
W¬†°dONLNdS
îπ
†
)    riting out Edition Data˘°dONLNdl
î
1
†
C)x2-86°dONLNdq
°∞
≠
(
™∞Closing an Edition ˇ@°dONLNdÑ
°

≠
Z)TAfter Reading or W °dONLNdñ
°
[
≠
s)WritingÜ@°dONLNdû
°
á
≠
ô),2-88°dONLNd£
Æ∞
∫
(
∑∞Displaying Dialog Boxesx@°dONLNdº
Æ
1
∫
C)Å2-90°dONLNd¡
ª∞
«
M(
ƒ∞#Locating a Publisher and Edition Frì@°dONLNd‰
ª
M
«
ì)ùom a Subscriberw`°dONLNdı
ª
®
«
∫)[2-98°dONLNd˙
»∞
‘
%(
—∞Edition Container Formatsr`°dONLNd
»
:
‘
Q)ä2-101°dONLNd
’∞
·Ù(
fi∞Reading and Wå°dONLNd(
’Ù
·
])Driting Non-Edition Files”‡°dONLNdB
’
q
·
à)}2-102°dONLNdH
‚¶
Ó(
ζApplication-Defi†°dONLNdX
‚
Ó
*)Jned RoutinesI¿°dONLNdf
‚
?
Ó
V)O2-105°dONLNdl
Ôú
˚
0(
¯úSummary of the Edition Manager∫‡°dONLNdå
Ô
D
˚
[)®2-106°dONLNdí
¸¶Ô(¶Pascal Summary‡°dONLNd¢
¸

)^2-106°dONLNd®    ∞‹(∞    ConstantsÆ°dONLNd≥    
)@2-106°dONLNdπ∞"Õ(∞Data T:`°dONLNdøÕ"·)ypes“@°dONLNd≈ı"
)(2-108°dONLNdÀ#∞/
$(,∞Edition Manager Routines–‡°dONLNdÂ#
8/
E)à2-1ò °dONLNdË#
E/
J)
1Ä°dONLNdÈ#
J/
O)
1°dONLNdÎ0∞<˙(9∞Application-Defi†°dONLNd˚0˙<
4)Jned RoutinesI¿°dONLNd    0
I<
V)O2-1°dONLNd0
V<
`)13°dONLNd=¶I€(F¶    C SummaryᆰdONLNd=ÔI¸)I2-1N‡°dONLNd=¸I
)14°dONLNd J∞V‹(S∞    ConstantsÆ°dONLNd+JV˝)@2-1u@°dONLNd.J˝V
)14°dONLNd1W∞cÕ(`∞Data T:`°dONLNd7WÕc·)ypes“@°dONLNd=Wıc
)(2-1ôÄ°dONLNd@W
c
)16°dONLNdCd∞p
$(m∞Edition Manager Routines–‡°dONLNd]d
8p
E)à2-1ò °dONLNd`d
Ep
O)19°dONLNdcq∞}˙(z∞Application-Defi†°dONLNdsq˙}
4)Jned RoutinesI¿°dONLNdÅq
I}
`)O2-122°dONLNdá~¶ä‡(á¶Result Codesï`°dONLNdï~Ùä
)N2-122ˇ6ƒ@ˇˇˇˇˇ@

ˇ·ˇ‚7^,Palatino
&e.
3+ä"CHAPTER à)>
2
4⁄ä˙
, (‡    2-3
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜,    Helvetica    ˇˇ—ÚˇÆ°dONLNd8äC»(@äEdition Managerˇˇˇˇˇˇ≠>(@
2
°dONLNd\äh
¸(eäRThis chapter describes how you can use the Edition Manager to allow your users to °dONLNdciäuù*sharS`°dONLNdgiùu
5)"e and automatically update data fr¿°dONLNdâi
5u
c)òom numerƒ†°dONLNdëi
cu
Ù).ous documents and applications.°dONLNd±{äá
â(Ñä:The Edition Manager is available only in System 7 or later+°dONLNdÎ{
âá
ˆ)ˇ. It can be used by many °dONLNd
àäîñ(ëädif™`°dONLNd
àñî¢)fer凰dONLNd

à¢î
m)0ent applications located on a single disk or thr„‡°dONLNd
:à
mî
¯)Àoughout a network of Macintos     °dONLNd
Wà
˘î
)åh .°dONLNd
Yïä°é(ûä
c°dONLNd
Zïé°¬)omputers. Tï°dONLNd
eï¡°
ê)3/o test for the existence of the Edition Manager◊†°dONLNd
îï
è°
∂)Œ
, use the ,
Courier◊†°dONLNd
ûï
∂°
‡)'Gestalt◊†°dONLNd
•ï
‡°)* function, .
°dONLNd
∞¢äƬ(´ädescribed in `°dONLNd
Ω¢√Æ
})9-Inside Macintosh: Operating System Utilities.‰ °dONLNd
Í¢
}Æ
)∫
 °dONLNd
Ï¥ä¿(ΩäURead the information in this chapter if you want your application’s documents to sharO‡°dONLNdA¥¿(Ωe °dONLNdC¡äÕ
u( ä5and automatically update data, or if you want to shar0@°dONLNdx¡
vÕ)Ï e and automatically update data °dONLNdòŒä⁄‹(◊äwith documents crˇ`°dONLNd©Œ‹⁄
Í)R<eated by other applications that support the Edition ManagerÕ`°dONLNdÂŒ
Í⁄
Ï(◊
Í
.°dONLNdÁ‡äÏ
@(Èä(For example, a user might want to capturÙ¿°dONLNd‡
@Ï
e)∂    e sales fi˜ °dONLNd‡
eÏ
t)%gurR`°dONLNd‡
uÏ
µ)es and totals fr˛†°dONLNd,‡
µÏ
Ï)@om within a °dONLNd8Ìä˘ò(ˆäsprÑ °dONLNd;Ìò˘
|)3eadsheet and then include this information in a wor(°dONLNdnÌ
}˘
ê)Âd-pr^¿°dONLNdrÌ
ê˘
˚)ocessing document that °dONLNdâ˙ä

˙(
äQsummarizes sales for a given month. The Edition Manager establishes a connection °dONLNd⁄
ä

l*.between these two documents. When a user modifiÄ@°dONLNd    

l

ñ)‚
es the sprh`°dONLNd

ñ
)*eadsheet, the information in °dONLNd0
ä
 ¨(
äthe worn‡°dONLNd7
¨
 ø)"d-pr•†°dONLNd;
ø
 
Ù)Eocessing document can be automatically updated to contain the latest °dONLNdÄ
!ä
-∏(
*ä
changes. T^Ä°dONLNdä
!∏
-
>).o accomplish this, both the spr
¿°dONLNd©
!
?
-
“)á eadsheet application and the worÁ°dONLNd…
!
—
-
‰)íd-pr¿°dONLNdÕ
!
Â
-)    ocessing °dONLNd÷
.ä
:
'(
7ä#application must support the featur熰dONLNd˘
.
'
:
ò)ùes of the Edition Manager° °dONLNd
.
ò
:
ö)q
.°dONLNd
@ä
Lê(
Iä
Tµ¿°dONLNd
@è
L‹)o use this chapterw °dONLNd'
@‹
L
õ)M+, you should be familiar with sending and r¯¿°dONLNdR
@
õ
L)øeceiving high-level events, °dONLNdn
Mä
Y
R(
Vä,described in the chapter “Event Manager” in ü@°dONLNdö
M
R
Y
–)»Inside Macintosh: Macintosh TÒ¿°dONLNd∑
M
œ
Y
Î)}oolbox °dONLNdæ
Zä
fµ(
cäEssentials.å°dONLNd…
Zµ
f∑)+
 fi`°dONLNd 
Z∑
fΩ)
Yû‡°dONLNdÀ
ZΩ
f
U)"our application must also support Œ‡°dONLNdÌ
Z
U
f
k)òApplÇ¿°dONLNdÒ
Z
l
f
x)e eñ°dONLNdÙ
Z
x
f
°)
vents to r”Ä°dONLNd˛
Z
°
f
æ))eceive P‡°dONLNd
Z
ø
f)Apple events frqÄ°dONLNd
Z
f)Dom °dONLNd
gä
sÂ(
päthe Edition Manager√Ä°dONLNd*
g‰
s˙)Z. See Ä°dONLNd0
g˚
s
)the s‡°dONLNd4
g

s)<following chapters in this book for detailed information on °dONLNdp
tä
Ä«(
}äApple events.á¿°dONLNd}
t«
Ä…)=
 °dONLNd
Üä
íÙ(
èäThe Edition Manager pr¶`°dONLNdï
ÜÙ
í
u)jovides you with the ability to,Zapf Dingbats°dONLNd¥
úä
£è(
¢ä
n
°dONLNd∂
ôñ
•≤)captur‡°dONLNdº
ô≥
•
—)?e data within a document and integrate it into another document°dONLNd¸
Æä
µè(
¥ä
n
°dONLNd˛
´ñ
∑
˚)Lmodify information in a document and automatically update any document that °dONLNdJ
∑ñ
√©*sharS`°dONLNdN
∑©
√‘)es its data°dONLNdZ
Ãä
ӏ(
“ä
n
°dONLNd\
…ñ
’©)sharS`°dONLNd`
…©
’
≈)>e information between applications on the same computer or acr˘`°dONLNdû
…
≈
’(
“
≈oss a network of °dONLNdØ
’ñ
·ı(
fiñMacintosh computers°dONLNd√
Êä
Ú
ï(
Ôä=Building the capabilities of the Edition Manager into your prÄ°dONLNd
Ê
ñ
Ú(
Ô
ñogram is similar to building °dONLNd
Ûä
ˇ„(
¸äcut-and-paste featur≈¿°dONLNd1
Û„
ˇ
#)Yes into your prÉÄ°dONLNd@
Û
$
ˇ
K)Aogram. TÑÄ°dONLNdH
Û
K
ˇ
ñ)'ext, graphics, spr® °dONLNdZ
Û
ñ
ˇ)Keadsheet cells, database °dONLNdsäç(    ä
rE°dONLNdté)Xeports—any data that you can select, you can make accessible to other applications that °dONLNdÃä

(äsupport the Edition Manager6`°dONLNdÁ


c)Ä. The next section pr'¿°dONLNd¸
c
)Yovides an overview of the main °dONLNd    ä&
(#äelements of the Edition Managerˆ‡°dONLNd    :
&)è4. Following sections discuss how to implement these °dONLNd    n'ä3§(0äfeatur¨°dONLNd    t'§3
)es in your application°†°dONLNd    ä'
3
)`
.°dONLNd    å9äEê(Bä
T†¿°dONLNd    ç9êE
W)-his chapter also describes an advanced featurW°dONLNd    ∫9
XE
È)»"e that allows applications to sharP °dONLNd    ‹9
ÈE)ëe data °dONLNd    „FäRñ(OädirI °dONLNd    ÊFóRµ)ectly fr’¿°dONLNd    ÓFµR”)om a fi,°dONLNd    ıF‘Rfi)le.ˇfiå@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-4    )B5Introduction to Publishers, Subscribers, and Editions4^*¿
¯

^*x
¯4^*x
¯

à*ê
¯4â*ê
¯ ä*ä
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNdu*àD(É*Intr∏X°dONLNduDàö)oduction to ê°dONLNduõà
§)W%Publishers, Subscribers, and EditionsˇˇˇˇˇˇV˛(É

2
°dONLNd7ôl•s(¢l
A∫†°dONLNd8ôs•u)
 
:†°dONLNd9ôv•ñ)sectionm¿°dONLNd@ôñ•
5) % is a portion of a document that shar‡°dONLNdeô
6•
Ô)†*es its contents with other documents. The °dONLNdè¶l≤
ø(ØlLEdition Manager supports two types of sections: publishers and subscribers. x@°dONLNd€¶
ø≤
Δ(Ø
ø
A≤‡°dONLNd‹¶
Δ≤
»)
 
°dONLNd›≥løò(ºl    publisher͆°dONLNdÊ≥òø
»),G is a section within a document that makes its data available to other °dONLNd
-¿lÃÊ(…ldocuments or applications. t†°dONLNd
H¿ÊÃÌ)z
AØ@°dONLNd
I¿ÌÃÔ)
 
/@°dONLNd
J¿Ã
)
subscriberÓ`°dONLNd
T¿
Ã
Ì)/1 is a section within a document that obtains its °dONLNd
ÖÕlŸâ(÷ldata frw°dONLNd
åÕâŸ
+)#om other documents or applications.°dONLNd
∞fllÎr(Ël
Y@Ä°dONLNd
±flrÎ
µ)Kour application writes a copy of the data in each publisher to a separate fi¿°dONLNd
˝fl
∂Î
Í(Ë
∂le called an 
°dONLNd
Ïl¯∫(ıledition container˜‡°dONLNdÏπ¯ª)M
.w‡°dONLNdϺ¯
ª)> The actual data that is written to the edition container is r/†°dONLNdZÏ
º¯
–(ı
ºeferrŒ`°dONLNd_Ï
–¯
Ù)    ed to as °dONLNdh˘l
|(
lthe 
›`°dONLNdl˘|
°)    edition. r°dONLNdu˘¢
®)&
Y2Ä°dONLNdv˘®

û)9our application obtains the data for each subscriber by rÖ@°dONLNdØ˘
û

‘)ˆeading data °dONLNdª
l
s(
lfrò‡°dONLNdΩ
s
É)om b`°dONLNd¿
Ñ
fl)the edition container1@°dONLNd’
fl

)[. Note that thr0Ä°dONLNd‰



y)>oughout this chapterä¿°dONLNd¯

x

§)[, the term :¿°dONLNd

•

¿)-edition °dONLNd


¡

«) rE °dONLNd

«

È)    efers to °dONLNd
l

1(
l.the edition container and the data it containsœ‡°dONLNdC

1

3)≈
.O‡°dONLNdD

4

6)
 °dONLNdF
%l
1r(
.l
Y@Ä°dONLNdG
%r
1)ou 
= °dONLNdJ
%Ä
1£)publishƒ °dONLNdQ
%£
1
«)#@ data when you want to make it available to other documents and °dONLNdë
2l
>
7(
;l0applications. When data is published, it is storC °dONLNd¡
2
8
>
©)Ãed in an edition container• °dONLNd€
2
®
>
≠)p. wÄ°dONLNd›
2
≠
>
≥)
Y8°dONLNdfi
2
≥
>
¿)ou 
4†°dONLNd·
2
¡
>
Ï)    subscribe °dONLNdÍ
2
Ì
>
Ô),
 °dONLNdÎ
?l
K
/(
Hl-to data that a publisher makes available by rÄ°dONLNd
?
0
K
á)ƒeading an edition frÊ`°dONLNd,
?
Ü
K
Õ)Vom its containerI¿°dONLNd<
?
Õ
K
“)G. 


Y*
g
¯4
Z*
g
¯
    °dONLNd?
Xl
c(
`lNote

ˇ·ˇ‚7^
°dONLNdD
el
qâ*Section °dONLNdK
eä
qü) and @°dONLNdP
e†
q‰)edition containerD†°dONLNda
e‰
qÔ)D ar↰dONLNdd
eÔ
q
)e prö`°dONLNdh
e

q
U)ogrammatic terms. 6†°dONLNdz
e
V
q
\)V
Y˜ °dONLNd{
e
[
q
¨)ou should not use °dONLNdç
ql
}
[(
zl4them in your application or your documentation. Use Ä`°dONLNd¡
q
[
}
Ü)Ôpublishers,MÄ°dONLNdÃ
q
á
}
â),
 °dONLNdÕ
}l
âõ(
Ülsubscribers,°dONLNdŸ
}ú
â±)0 and Ì °dONLNdfi
}±
â”)    editions. °dONLNdÁ
}‘
â÷)#
 hÄ°dONLNdË
}÷
â‹)
Y)°dONLNdÈ
}‹
â
#)ou should also r†°dONLNd˘
}
#
â
F)G    efrain frw`°dONLNd
}
F
â
ß)#om using other terms °dONLNd
âl
ïé(
ílsuch as B¿°dONLNd
âè
ïº)#publicationû°dONLNd*
âº
ï )- or  °dONLNd.
âÀ
ï¸)subscription‘¿°dONLNd:
â¸
ï
ô)1$ to describe the dynamic sharing of °dONLNd^
ïl
°≠(
ûlinformation prÇÄ°dONLNdl
ï≠
°
7)Aovided by the Edition Manager‚°dONLNdâ
ï
6
°
z)â. Use the terms ‡°dONLNdô
ï
{
°
ò)Epublishø °dONLNd†
ï
ò
°
≠) and °dONLNd•
°l
≠ë(
™l    subscribe∏¿°dONLNdÆ
°ë
≠
=)%' to describe the Edition Manager featur\`°dONLNd’
°
>
≠
I)≠es.,Zapf Dingbats„°dONLNdŸ
§
N
¨
T)
u
°dONLNd‹
≤l
æ
(
ªl+Each edition has an icon that is visible fr°dONLNd
≤

æ
\)≤om the Finder®`°dONLNd
≤
[
æ
`)=. ®`°dONLNd
≤
`
æ
x)Figur{ °dONLNd
≤
x
æ
å)e 2-1†°dONLNd 
≤
ç
æ
ª)
 shows the‡°dONLNd*
≤
º
æ
æ)/
 °dONLNd+
øl
Àã(
»ldefaultÎ °dONLNd2
øã
Àç)
 k °dONLNd3
øé
Àƒ)edition icon.


Ì*
˛
¯4
Ó*
˛
¯"
Ó*]

ˇ·ˇ‚7^
    °dONLNdB
„l
Óñ(
Îl
Figure 2-1°dONLNdM
„Æ
Ó
)BThe default edition icon
°dONLNdg:lF(ClThe name that the user specifiÿ°dONLNdÖ:F
Œ)Ñ6es for the edition is located next to the edition iconAÄ°dONLNdª:
œF
Â)fl. For °dONLNd¡GlS∫(Plinformation on prI`°dONLNd“GªS‚)O    oviding iÄ°dONLNd€G„Sˆ)(cons†°dONLNdflG˜S
G) for the editions crY†°dONLNdÛG
GS
∏)Peated by your applicationó°dONLNdG
∏S
›)q
, see the °dONLNdTl`î(]l    chapter “B`°dONLNdTï`€))Finder InterfaceüÄ°dONLNd/T€`Ì)F” in Y@°dONLNd4TÓ`
l)Inside Macintosh: Macintosh T´¿°dONLNdQT
k`
≤)}oolbox Essentials.¿°dONLNdcT
≤`
¥)G
 p¿°dONLNddT
µ`
Õ)FigurCÄ°dONLNdiT
Õ`
·)e 2-2·°dONLNdnT
·`
„)
 °dONLNdoalm
P(jl4illustrates a document containing a single publisherX °dONLNd£a
Pm
s)‰
, its corr›@°dONLNd≠a
sm
„)#esponding edition, and a °dONLNdΔnlz
8(wl.subscriber to the edition in another document.


ˇj"
¯4
˛`
ˇaòB@
@

ˇa?bø    
˛ˇÄ≈    
˛ˇÄ≈    
˛ˇÄ≈    Ä≈    ˇûÄ≈    ˇøÄ≈    ˇsÉÄ≈    ˇaÉÄ≈    ˇa˚Ä≈    ˇs˚Ä≈    ?Ä≈    ˆÄ≈    Ä≈    ÜÄ≈    9«˚Ä≈    pÁ˚Ä≈    ˇÄ≈    ˇÄ≈    Ä≈    
˛ˇÄ≈    
˛ˇÄ≈    
˛ˇÄ≈ø˝@ƒ˝@ƒ
ªGLƒŒ§fiƒv§–ƒ
ûßNƒ˛√˛√˛√øøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB@Ä
@Ä
?abøøøøøøø

Ò‡
ÇΔ

êFΔ


DΔ

¡DΔ
ADΔ
 hÑΔ
 !    Δ
Á¿~Δøøøø
ÒÄ
˝Ä` @
Ä’
˛$§Ä P¿—

˝!@@êÄ“
¡ù≠!a
EÊ¥∏SÃÁűœ÷Ch¶4!¶Üöâêi¶ôÉJ%÷ID8¬A'úë)r$íÑ*÷≤X@$BH·À†Ç˘&%ÑúK÷sË8x‚Gù} qo9…cí÷
˛à˘
Ã
˛à˘Ã
˛p˘Ãø
6«
«
!(«
¿ßôœ(◊çZÀCM2%I"íi¨ÀI$*í%"I»ÀÚLK    uß2À‚fisíq©q–À˜à ˜à ˜p ø%‡
Ép˝&
ÄIJ
Ä‚    
@Δ˝ ˝`˝⁄"êÄ @ ˛@!˚·'#êô û;AJ4Δ˜8ÎOqh◊ûFcyú@;OL”Δ√yπ‡„'#SI äNi°RI,RE-E&±"ILîì"P@Eµ¥QM$ìD†„'#cãA$â¡dä¢Ñâä'"$QâíB†@Ö%$¢äíÖ@„'#$ÅôæDûr¥äRãHBtí”9‰ƒ∞FäNM*“i‰â`„'##â§ÓY√\iù$sí!“GA´,úΔß9 8rJIÙùÜßr@„Ú ˛
 ‘Ó
 ‘Ó
p‘ø
√¿˛¡Ü``’
$¢˚˛
BI¸ ’H≤˛@˛
ÄDz @’
à¨8fiÁ&Qk¬ÉosÅD'Ä◊GD    EäI    -¶ÄëMÇ¢≈$Üö“@◊BDÖDJ'
ëǬä"ú‰@◊DHäVíí¯
:◊ÄÇ    E+I·Ä◊ò0,s§ú    g ‘ã<9“NúÎ÷˝ ˚ ˝¸÷òBÄñ
Äñ
aïb˝ ˆ¸÷˝pˆ8¸÷øøøøøøøøøøøøø@˸ÿ0
¸Ã
@ ˛ÄÃ
Cœ!¥œ5ƒ–    „ÕA$¶Ñ[Dîö`§ÄŒ‚(«RH®ú@HÕ"Ihh§…K ÄiÄŒòÇ@
HH

\*LûIJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@

ˇa?b'
ÅÅÅÅˇˆ„ˇÅÅÅ®ˆ„ˇÅÅÅ®ˆ„ˇÅÅÅ®ˆ˛ˇÈ˛ˇÅÅÅ®ˆ˛ˇ˜ˇ
˝ˇ˙˛ˇÅÅÅ®ˆ˛ˇ˜ˇ˚ˇ˚˛ˇÅÅÅ®ˆ˛ˇ¯ˇ˛ˇ
˛ˇ¸˛ˇÅÅÅ®ˆ˛ˇ¯ˇˇˇ˝
ˇˇ¸˛ˇÅÅÅ®ˆ˛ˇ¯ˇˇˇ˝˚ˇ˛ˇÅÅÅ®ˆ˛ˇ¯ˇ˛ˇ
˙ˇ˛ˇÅÅÅ®ˆ˛ˇ¸ˇ˚˚ˇ˛ˇˇ˛ˇÅÅÅ® ˆ˛ˇ¸ˇˇˇ˝˝ˇ˝ˇˇ˛ˇÅÅÅ®ˆ˛ˇ˚˝ˇ¸
ˇˇ˝ˇˇ˛ˇÅÅÅ®ˆ˛ˇ¸˚ˇ˝
ˇˇ˝ˇˇ˛ˇÅÅÅ®ˆ˛ˇ˝˛ˇ
˛ˇ˛˘ˇ˛ˇÅÅÅ®ˆ˛ˇ˛˛ˇ˝˛ˇ
˘ˇ˛ˇÅÅÅ®ˆ˛ˇ
ıˇ˜˛ˇÅÅÅ®ˆ˛ˇ
ıˇ˜˛ˇÅÅÅ®ˆ˛ˇÈ˛ˇÅÅÅ®ˆ„ˇÅÅÅ®ˆ„ˇÅÅÅ®ˆ„ˇÅÅÅ®
ÅÅÅÅˇ‡ˇÅÅÅ°‡ˇÅÅÅ°!Úˇˇ˛ˇˇˇˇ˛˛ˇˇˇˇÅÅÅ• Û˝ˇ
˛ˇˇˇˇˇˇ˝ˇÅÅŶ!Ûˇˇ˛ˇˇˇˇˇˇˇˇˇÅÅÅ£!Úˇˇ˝ˇˇˇ˛ˇˇ˛ˇÅÅŶ‰ˇÅÅÅù‰ˇÅÅÅù‰ˇÅÅÅù
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇòÇ@Ä
HH

\*HüIJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@Ä
?ab'
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇÚ¸ˇ˛˝ˇ˘˛ˇ¯
ˇˇ¸ˇÅÅÅ∂'Úˇ˛ˇ˝ˇˇ˘ˇ¯ˇˇ˛
ˇˇÅÅÅ∂$Úˇ˙ˇ˝ˇ˚ˇ¯ˇ˛ˇ˛ˇÅÅŵ$Ú˛ˇ¸ˇ˝ˇ˚ˇ˘ˇ˝ˇ˛ˇÅÅŵ'Ûˇˇ¸ˇ˝ˇ˚ˇ˘ˇ˝ˇ˛ˇÅÅŵ*Ûˇ˙ˇ˝ˇˇˇˇ˚ˇˇˇ˛ˇ˝ˇÅÅŵ*Ûˇ˝ˇˇ˛ˇ˙ˇ˝ˇ˝ˇˇ˝ˇÅÅÅ¥Ù˚ˇ
¸ˇ˙˚ˇ˚
ˇˇ˝˛ˇÅÅŵ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ?Ú¸ˇ˛
ˇˇÁ
ˇˇ˜ˇ˘˚ˇˇˇÒ
ˇˇ˙ˇÛˇˇˇˇˇ˝
ˇˇ
ˇˇÅÅ®9Úˇ˛ˇ„ˇˇ˘
ˇˇ˘ˇˇˇˇˇ˚ˇˇı
ˇˇÔˇÅÅå1Úˇ‹ˇ˘ˇˆˇ˝ˇˇ˙ˇÛˇˇÚˇ˝ˇÅÅêÖÚ˛ˇ¸ˇˇ˛ˇ    ˇˇˇˇˇˇ˝ˇ˘ˇ˘ˇˆˇ˝ˇˇˇ˝ˇ˙ˇˇ˛
ˇ˝ˇˇˇˇˇˇˇˇ˛ˇ˚ˇ¸ˇˇ˝ˇˇˇ˛ˇ
˝ˇ˚ˇˇˇˇ˛˛ˇ
˝ˇÅÅ∑õÛˇˇ˝ˇˇˇˇˇ˛ˇˇˇˇ˛ˇˇˇ˚ˇ¯ˇˆˇ˝    ˇˇˇˇˇˇ˝ˇˇˇˇˇˇˇ˛ˇˇ˛ˇˇˇˇ¸ˇˇˇˇˇˇˇˇˇˇˇˇ˛ˇˇˇ¸ˇˇˇˇˇ˛ˇˇˇÅÅ∑íÛˇ˙ˇˇˇˇˇ˛ˇ˝˛ˇ˚ˇ˝
ˇˇ˝ˇ˜ˇ¸ˇˇ˛ˇ˝ˇ˛ˇ˛ˇˇˇ˛ˇˇˇˇ˛ˇ¸˛ˇˇ˛ˇˇˇˇˇ˝ˇˇˇ˚ˇˇ˝ˇ˝ˇˇˇÅÅ∂åÛˇ˚ˇˇˇˇˇˇˇˇ˝ˇ˘ˇˇ˙ˇˆˇ˝ˇˇˇ˙
ˇ¸ˇ˝ˇ˛ˇ˝ˇˇ˛ˇ
ˇ¸ˇ¸
ˇ¸ˇ    ˇˇˇˇ˛ˇˇˇˇ˝ˇˇ˛ˇ˛ˇˇˇˇÅÅ∑ÖÙ˛ˇ¸˛ˇ˛ˇ
¸ˇ
ˇ¸˛ˇ˝˝ˇ˙˛ˇ¯˛ˇ˛ˇˇ˛˛ˇ¸ˇˇˇ˛ˇ
ˇ˝ˇˇˇ¸ˇˇˇ˚˛ˇ˛ˇˇˇ˝ˇ
˛ˇ
˛ˇˇˇ¸˛ˇˇˇ˛˛ˇˇˇÅÅ∂Èˇ˛ˇ∑ˇÅÅÅÁÈˇ˛ˇπ
ˇˇÅÅÅÊ˲ˇ∏ˇÅÅÅÂ
ÅÅÅÅˇ#Ú¸ˇ˚ˇˇˇˇ˝
ˇˇÒ
ˇˇ¸
ˇˇÅÅÅΩÚˇ˛ˇ˙ˇÁ
ˇˇ˛
ˇˇÅÅźÚˇ˜ˇ˝ˇÎˇˇˇˇÅÅźMÚ˛ˇ˚ˇˇ˝ˇˇˇ˛ˇ
˝ˇ¸ˇˇˇˇ˛ˇˇˇ˝ˇ˛ˇˇˇ˛˛ˇ˛ˇˇˇˇÅÅÅfiXÛˇˇ˝ˇˇˇˇˇˇˇˇˇ˛ˇˇˇ¸ˇˇˇˇˇˇ˛ˇˇˇˇˇˇˇˇˇˇˇˇÅÅÅ›SÛˇ˚ˇ˛ˇˇˇˇˇ˝ˇˇˇ˚    ˇˇˇˇˇ˛ˇˇˇˇ˛ˇˇˇ˛ˇˇÅÅÅ‹TÛˇ˝ˇˇ¸ˇ    ˇˇˇˇ˛ˇˇˇˇ˝ˇˇ˛ˇˇ˛ˇˇˇˇˇ˛ˇˇˇˇ˝ˇÅÅÅ€OÙ˚ˇ˛ˇˇˇ˝ˇ
˛ˇ
˛ˇˇˇ¸ˇˇˇ˛ˇ˛ˇˇˇˇˇ˛ˇˇˇ˛ˇ˛˛ˇ
ˇÅÅÅ€±ˇ˛ˇÅÅÅ‘±ˇ˛ˇÅÅÅ‘∞˛ˇÅÅÅ”
ÅÅÅÅˇRÛ
ˇˇ˛
ˇˇÓ˛ˇˆ
ˇˇ¸
ˇˇ˘
ˇˇ¸
ˇˇÙ
ˇˇÏ
ˇˇˆ˛ˇ€ˇˇˇÒ
ˇˇÓ˛ˇ
ˇ›
ˇˇÒ
ˇˇÅê5Úˇ˝ˇÌˇÌˇ¯
ˇˇ˛
ˇˇ€ˇıˇ€
ˇˇŸˇ˛ˇÅÅ◊CÛˇˇˇÌˇÌˇ˜ˇˇˇˇÍˇÙˇıˇ˘ˇ„ˇˇÎˇ˝ˇŒˇÅãÌÛˇˇˇ˝
ˇˇˇˇˇ¸ˇ˝ˇ˛˛ˇˇˇ˛ˇˇ˛ˇ¸ˇˇˇˇ˛ˇˇˇˇˇ˛ˇˇ˝ˇ˛ˇ
˛ˇ˛˛ˇˇˇˇ¯ˇ˝ˇ˛ˇ˛ˇˇˇˇ˛ˇˇˇ˝ˇ
˝ˇˇ˛ˇˇˇˇ˛ˇˇ˝ˇˇˇ˛ˇ
˝ˇ¸ˇ˘˛ˇˇˇˇ˝ˇˇˇˇˇˇˇ˝ˇ˛ˇˇˇˇ˝ˇˇ˝ˇˇˇ˛ˇ
˝ˇÅö
Ûˇˇˇˇˇˇˇˇˇ¸ˇ˛ˇˇˇ˛ˇˇˇˇˇˇˇ˝ˇˇˇˇˇˇˇˇˇˇ˛ˇˇˇˇ˛
ˇˇˇˇˇˇ¯ˇ˛ˇˇˇˇˇˇˇˇ˛ˇˇ˛$ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ˛ˇˇˇ¸ˇ˙ˇ˛ˇˇˇˇˇˇˇˇˇˇˇ˛ˇˇ˛ˇˇˇˇˇˇˇˇˇˇˇˇ˛ˇˇˇÅö˜Ûˇˇˇ˛˛ˇ˛ˇˇˇˇ¸ˇ˛ˇˇ˝ˇˇˇ˛ˇ˛ˇ¸    ˇˇˇˇˇ˛ˇˇ¸ˇ˛ˇˇ˛ˇˇ˝ˇˇ˛ˇˇ˘ˇ˛ˇˇ˛ˇ˛ˇˇ˛ˇ˛ˇˇ˛ˇˇ˛
ˇˇ˛ˇˇ˝ˇ˛    ˇˇˇˇ˝ˇˇˇ˚ˇ˚ˇ˝ˇˇˇˇˇˇˇˇˇ˛ˇˇ˛ˇˇ¸ˇ˛ˇˇˇˇ˝ˇˇˇÅô˙Ùˇ˝ˇˇ˚ˇˇˇˇ˚ˇ˛ˇˇˇˇˇˇˇˇ¸ˇ˙ˇˇ˛ˇˇ˝ˇ
˛ˇˇˇˇˇˇˇ˛
ˇˇˇˇˇ¯ˇ˛ˇˇˇˇˇ˝ˇ˝ˇ˛ˇˇˇˇˇˇˇˇˇˇ˛ˇ
˝ˇˇˇˇ˛ˇˇˇˇ¸ˇ˛ˇˇˇ˛ˇˇˇ˛ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ˝ˇˇˇ˛ˇˇˇˇÅö˙Ù
ˇˇ˛ˇ˛˛ˇ˛ˇˇ˚˛ˇˇˇ˛ˇ˛ˇˇˇˇ˛ˇ˝ˇˇˇ˛ˇ˛    ˇˇˇˇˇ˛ˇˇˇˇ˛˛ˇ
˛ˇˇˇ˛ˇ˝˛ˇˇˇˇ˛˛ˇ
ˇ¸ˇˇˇˇˇˇˇˇˇˇ˛ˇˇˇ˛ˇˇˇˇ˛ˇ
˛ˇˇˇ˙˛ˇ˝˛ˇˇˇˇˇˇˇ¸ˇˇˇ˛ˇˇˇ˝ˇˇˇˇ˛ˇ˛ˇˇˇÅôᡇˇ¸ˇÅŢš¸ˇÅÅ¢ÅÊ˛ˇ˛˛ˇÅÅ£
ÅÅÅÅˇ<Ò
ˇˇ˝
ˇˇ˛˛ˇÔ
ˇˇÊ
ˇˇ˝
ˇˇÊ
ˇˇ¸
ˇˇ˝
ˇˇÔ
ˇˇÎ
ˇˇÅÅ™2Úˇˇˇˇˇ˛ˇÃˇÂˇ˝    ˇˇˇˇ◊ˇÅÅ™3ˇˇ˛ˇˇˇˇÁˇËˇÂˇ˙ˇ¸ˇÊˇÛˇÅÅ©éÚ
ˇˇ˛ˇ˛ˇˇˇˇ¸˝ˇ˛˛ˇ˛ˇˇ˝ˇ˛ˇ
˛ˇ˛ˇˇˇˇˇˇˇˇ˛ˇ¯ˇˇˇ˝ˇ˝ˇˇ¸
ˇˇ˝
ˇˇ˚˝ˇ˛˛ˇ˛ˇˇ˝ˇ˛ˇ
˛ˇ˚ˇˇ˛ˇ˝ˇ˝ˇÅÅ∏ûˇ˛˛ˇ
ˇ˛ˇ˚ˇˇˇ˛ˇˇˇ˛ˇˇˇˇˇ˝ˇˇˇˇˇˇˇˇˇˇˇ˙ˇˇ˛ˇˇˇˇˇ˘ˇ¸ˇ˚ˇˇˇ˛ˇˇˇ˛ˇˇˇˇˇ˝ˇˇˇˇˇˇˇˇˇˇˇÅÅπöˇ˝ˇˇ˛ˇ¸ˇ˛
ˇˇ˝ˇˇ˛ˇˇ˛ˇ˛ˇ˚
ˇˇˇˇˇˇ˛ˇ˛ˇ˙ˇ˛ˇˇˇˇ˛ˇ˘ˇ¸ˇ¸ˇ˛
ˇˇ˝ˇˇ˛ˇˇ˛ˇ˛ˇ¸ˇ˛ˇ˛ˇ
˛ˇˇ˛ˇÅÅπëˇ˛ˇ˛ˇˇ˚ˇˇˇ˛ˇˇˇˇˇˇˇˇˇ¸ˇˇˇˇˇˇ¸ˇ˜ˇ˛ˇˇˇˇˇ˝ˇ˙ˇ¸ˇ¸ˇˇˇ˛ˇˇˇˇˇˇˇˇˇ˝
ˇ¸ˇ˝ˇ¸ˇˇÅÅ∏ôÙ˝ˇˇˇ¸
ˇˇ˚ˇˇˇ˛˛ˇ
˛ˇ    ˇˇˇ˛ˇ˚ˇˇ˛˛ˇˇˇˇ˛ˇˇ¸ˇˇˇˇˇ˛ˇˇˇ˝˝ˇ
˝ˇ¸ˇˇˇ˛˛ˇ
˛ˇ    ˇˇˇ˛ˇ˚ˇˇˇ˛ˇ
˛ˇˇˇˇÅÅ∑flˇ ˇŸˇ—ˇÅÅ¥òÇÄñ
HH

\*L†Ä˛ˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêêÄñ
aïb'flˇ°ˇ—ˇÅÅ¥‡˛ˇ£˛ˇ”˛ˇÅŵ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ◊◊ı˛◊
◊“˛◊ÅÅÅÊÒ
◊◊Ò
◊◊ˆ◊˛◊–◊ÅÅÅÂ"Ú◊◊Ò◊ˆ◊˝◊Â◊Ó◊ÅÅʼnVÚ◊◊˝˝◊
˝◊◊˝◊¸◊˘˛◊
◊◊◊◊◊˝◊◊◊◊˛◊˛◊◊◊◊˘◊˝◊˛
◊◊ÅÅÅÔaÛ◊◊¸◊◊◊◊◊◊◊◊˝◊˙◊˛◊◊◊◊◊◊˛◊◊◊◊◊◊◊◊◊◊¯◊˛◊◊◊◊ÅÅÅWÛ¸◊˛◊˛◊◊˛
◊◊˛˛◊¸◊˚◊˝◊◊◊◊◊˛◊◊◊˛◊˛◊˛◊¯◊˛◊◊◊ÅÅÅÏ`Ù◊˝◊˛◊◊◊◊◊◊◊˘◊˛◊◊◊˛◊◊◊◊◊◊◊◊◊◊◊◊¸◊˜◊˛    ◊◊◊◊◊◊ÅÅÅòB@
@
ïa’bıñGá$ñ}Ñ:FŒ˝À˝»8˝8»ø    
‡¿¿§…ê
 ˛

l…
˛H ÄÕ
ûx‹H—ˆõ«hŒ
J)§HRc$à∞Œ#îQê°"Dꆌ DZHŸ,ƒO@Œ¡ɧìÒë˜D5@Œ˙
«øøø
—¸
…≥¸
        …    
" 
…    
"hˇFÛ¥
…    
"))â$X…    DPâ(P…    fñR»†    …    D˚íG <^…øøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB@Ä
@Ä
’abøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòBÄñ
Äñ
a+bøøøøøøøøøøøøøøøøøøøøøøòÇ@
HH

\*H°Ä˛ˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@
ïa’b'bı◊◊˝◊◊◊◊◊◊◊◊˛˛◊˚˛◊˝˛◊◊◊◊◊◊◊¸◊
◊˛˛◊◊˝◊˝˛◊◊◊˛
◊◊˝◊ÅÅÅÛÏ◊¸◊⁄◊Ë◊ÅÅÅ›Ï◊¸◊⁄◊ÅÅÅ√Ì˛◊˛˛◊‹˛◊ÅÅŃ
ÅÅÅÅˇÚ˝ˇˆ˝ˇÎ
ˇˇı˛ˇˇˇÅÅÅÕ Òˇˇˆˇˇ›ˇˇˇˇˇÅÅÅÕ*Úˇ˝ˇ¯ˇ˝ˇflˇˇˇÙˇÙˇÅÅÅËYÚˇ˝ˇ¯ˇ˝ˇ˝ˇ˝ˇ
˝ˇ˛ˇˇ˛ˇ˘ˇˇˇ˛ˇˇˇ˛¸ˇ    ˇˇˇˇˇ˝ˇ˛˛ˇˇˇˇÅÅÅÙbÚˇ˝ˇ¯ˇ˝ˇˇˇˇˇˇ˛ˇˇˇˇˇˇ˘ˇˇˇ˝    ˇˇˇˇˇ˛
ˇˇˇˇˇ˛ˇ˛ˇˇˇÅÅÅÛ^Ûˇ˝ˇ¯ˇ˝ˇ˛˛ˇˇˇ˛ˇˇ˛ˇ˛ˇ¯ˇˇˇ˝ˇˇ˝ˇˇ˛ˇˇ˛ˇˇˇ˝ˇˇÅÅÅÚ_Ûˇ˛ˇ˜ˇ˛ˇ˛ˇ¸ˇˇˇˇˇˇˇˇˇ˘ˇˇˇˇˇˇˇˇˇˇˇ˛ˇ˛ˇ˝ˇ˛ˇ˛ˇˇÅÅÅÒVÙ¸ˇ¸ˇ˝¸ˇ¸˛ˇˇˇˇˇ˚ˇ˛ˇ˝˛ˇˇˇ˛¸ˇ˛ˇ
ˇ˛ˇ˝ˇˇˇˇ˝˛ˇˇÅÅÅÒ¬ˇÅÅÅø
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇÚ˛ˇ
ˇ˛ˇ‘
ˇˇ˚
ˇˇÅÅÅŒ!Òˇˇˇˇˇ’ˇˇ˝ˇˇÅÅÅœ#Úˇˇ˛ˇÙˇÙˇÓˇ˘ˇÅÅÅœ<Úˇˇ˛ˇˇˇˇ˛˘ˇ
ˇ˛ˇˇ˝ˇ
˛ˇˇˇˇ˚
ˇˇ¯ˇÅÅÅœAÚˇˇ˛ˇ˛ˇˇˇˇˇˇˇ˛    ˇˇˇˇ˛ˇˇˇ¯ˇ˙ˇÅÅÅŒ?Ûˇˇ˛ˇ˛ˇˇ˝ˇ˛ˇˇ˛ˇ˛ˇˇˇ˝ˇˇ˜ˇ˚ˇÅÅÅÕAÛˇˇˇˇˇˇˇˇˇˇˇˇ˝ˇ˝ˇˇ˛ˇˇˆˇ¸ˇˇÅÅÅœ>Ù˛ˇ
ˇ˛ˇ¸ˇ˛ˇˇˇ¸ˇˇˇˇ˛˛ˇˇ˙˝ˇ˛
ˇ˝ˇÅÅÅŒ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇòÇ@Ä
HH

\*L¢Ä˛ˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@Ä
’ab'
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇòÇÄñ
HH

\*H£Ä˛ˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêêÄñ
a+b'
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇòB@
@
+akbøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB@Ä
@Ä
ka´bøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòBÄñ
Äñ
´a¡bøøøøøøøøøøøøøøøøøøøøøøòÇ@
HH

\*L§Ä˛ˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@
+akb'
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇòÇ@Ä
HH

\*H•Ä˛ˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@Ä
ka´b'
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇòÇÄñ
HH

\*L¶Ä˛ˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêêÄñ
´a¡b'
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇÅÅÅÅ
òB@
@
¡a
bøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB@Ä
@Ä

aAbøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòBÄñ
Äñ
AaWbøøøøøøøøøøøøøøøøøøøøøøòÇ@
HH

\*HßIJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@
¡a
b'
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇÅÅÅÅ
òÇ@Ä
HH

\*L®Ä˛ˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@Ä

aAb'
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇòÇÄñ
HH

\*H©Ä˛ˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêêÄñ
AaWb'
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇòB@
@
WaóbøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB@Ä
@Ä
óa◊bøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòBÄñ
Äñ
◊aÌbøøøøøøøøøøøøøøøøøøøøøøòÇ@
HH

\*L™Ä˛ˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@
Waób'
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇòÇ@Ä
HH

\*H´Ä˛ˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@Ä
óa◊b'
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇòÇÄñ
HH

\*L¨Ä˛ˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêêÄñ
◊aÌb'
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇ
ÅÅÅÅˇˇ∑“@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡ä5Introduction to Publishers, Subscribers, and Editions

, (‡    2-5
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHw4gHw"hH]

ˇ·ˇ‚7^    °dONLNd\äg¥(dä
Figure 2-2°dONLNd\Ãg“)B
A0°dONLNd\“g˘)
 publisherÖ °dONLNd\¯g
k)&, an edition, and a subscriber
°dONLNd7
 ä
,
E(
)ä*Note that the publisher and subscriber bor˜@°dONLNda
 
E
,
ï)ªders illustrated in †°dONLNdu
 
ñ
,
Æ)QFigurr¿°dONLNdz
 
Æ
,
¬)e 2-2@°dONLNd
 
√
,
¸) may appear °dONLNdã
-ä
9∫(
6äslightly difRÄ°dONLNdó
-∫
9Δ)0fer5°dONLNdö
-Δ
9›)ent fr´@°dONLNd†
-›
9
)
om the borî@°dONLNd™
-

9
T)0ders you see on à °dONLNd∫
-
T
9
d)Gthe )Ä°dONLNdæ
-
e
9
q)scrõ¿°dONLNd¡
-
q
9
Ö)een. `°dONLNdΔ
-
Ü
9
û)Figur” °dONLNdÀ
-
ù
9
Ÿ)e 2-6 on page í`°dONLNdŸ
-
⁄
9
‚)=2-Ê@°dONLNd€
-
‚
9
Á)
9Ê@°dONLNd‹
-
Á
9
) showA °dONLNd·
-
9)s °dONLNd„
:ä
Fç(
Cä
t¬`°dONLNd‰
:ç
F
)he publisher and subscriber bor–¿°dONLNd

:

F
')åder®¿°dONLNd

:
(
F
U)s as they a@°dONLNd

:
V
F
ä).ppear onscr‡°dONLNd

:
ä
F
õ)4een.°dONLNd
!
Lä
X…(
UäData always fló‡°dONLNd
/
L…
X
)?ows in one dir¥¿°dONLNd
=
L

X
.)?
ection, fry °dONLNd
G
L
/
X
“)'%om publisher to edition to subscriber¯Ä°dONLNd
l
L
—
X)¢. Documents °dONLNd
x
Yä
e
(
bäWthat contain publishers and subscribers do not have to be open at the same time to sharz °dONLNd
œ
Y

e(
b
e °dONLNd
—
fä
r
∂(
oäBdata. Whenever the user saves a document that contains a publisher-Ä°dONLNd
f
∂
r(
o
∂, the edition changes °dONLNd)
sä
ô(
|äto r|‡°dONLNd-
sô
£)eflS@°dONLNd0
s§
’)ect the curr€‡°dONLNd<
s’

)1ent data fr0@°dONLNdG
s


N).om the publisherΔ°dONLNdW
s
M

R)J. g†°dONLNdY
s
R

˛)(All subscribers update their contents frj†°dONLNdÅ
s
˛
)¨om °dONLNdÑ
Ää
åæ(
âäthe edition. æ`°dONLNdë
Äæ
å
«)4<Any number of subscribers can subscribe to a single edition.°dONLNdŒ
íä
ûê(
õä
Tµ¿°dONLNdœ
íè
ûü)o cr‡Ä°dONLNd”
íü
û
í)8eate a publisher within a document, a user selects an arh@°dONLNd
í
ì
û
ı)Ùea of the document to °dONLNd!
üä
´ù(
®äsharS`°dONLNd%
üù
´°)
e°dONLNd&
ü¢
´§)
 ù°dONLNd'
ü§
´Á)and chooses Cr÷`°dONLNd5
üÁ
´
/)Ceate Publisher fr¯†°dONLNdF
ü
/
´
Ä)Hom the Edit menu ˜‡°dONLNdW
ü
Å
´
î)R(see ú°dONLNd\
ü
ï
´
≠)Figurn¿°dONLNda
ü
≠
´
È)e 2-7 on page .°dONLNdo
ü
Í
´
Ú)=2-Ň°dONLNdq
ü
Ú
´
¸)10Ň°dONLNds
ü
¸
´
ˇ)

)’¿°dONLNdt
ü
ˇ
´). °dONLNdv
¨ä
∏¢(
µäFigurR¿°dONLNd{
¨¢
∏∂)e 2-3@°dONLNdÄ
¨∂
∏
˝)I shows the dialog box that your application should display when the user °dONLNd…
πä
≈π(
Š
chooses CrL@°dONLNd”
π∫
≈¯)0eate Publisher@°dONLNd·
π¯
≈˙)>
.


ËH
˘4
ÈH
˘"
ÈH]

ˇ·ˇ‚7^
    °dONLNd‰
fiä
È¥(
Êä
Figure 2-3°dONLNdÔ
fiÃ
È
.)BThe publisher dialog box

wI
    4ˇb3ˇc4ò@@
˜@
˜ˇc4ˇ£+¡¡?Ãˇ¸¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯ò@@Ä
˜@Ä
˜ˇ£4ˇ„+?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯ò@Ä¿
˜Ä¿
˜ˇ„4#+?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯Ãˇ˛¯¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡>xÄ1Ä…"$
J@… Bà@…8B
@…HB
Ä…
@Ñd»Bà!"@…˝¿«Ä…¡¡¡¡">`¿ò0¸
l0˛
Ä@@‚ "˛Å !ĸ ¸ÄÄÄ‚  ˝Ä
! ¸B˝
˛ÄÄ‚%!8cµ¢Ä
ö9Ï&Äk¿AO3û◊ÖÉË„õF·4„%!HÕÕ
@J%2t”ëA¶ödJ
"ö    ®î•åñò„%!@â(éÄTF!$‚
Å»íHT%"QA    „%!A&KÅ !•[L…
:¬‰òñuØâïiNh „%!·Œ}¿gã>"wH‰ ‘Å≈ºÁ$A©¯é2á „˛˚¸ ˚@Ÿ
˛˚Ã
˛˚á>É
É…"˛Δ…   …8)Ûs¡J5„G@ŒH”&âARH§öiÄŒA%
ÅdâHíqÕC|…¬DùiÃÇÕ¸∑N‰É\jFúrÕ˜"Ãò@¿

˜¿

˜#4c+˜"Øá$c8aÄ0`¿˝¿0†˝¿0‰
!Ä¿˛
˝˝
@›#R 
@IJ@¸„'#RH'ée)Fò˝«¿‹-Û»ÿo7<”iöxÿfi7<Â'#JjH"í⁄h*I%îàß@H÷$I)§íhîm6ä)•$hîÂ'#Lr–E¢p,ëA(êí@"à‰Dä1AP®!I$îQB$P®Â'#ÑÉ`E•/ÄHìŒmLÄ"—NíZM<ë,¢ìI•ZNxë,Â'#ƒr@È9÷pkç3…tàtêË5eì∞‘ÓHíI>ì±®ÓHÂÚ˛

÷Ó

÷Ó
é÷¡
 @
ɲ&0`ÿ@ĸ
˛0I¸ ÿ
ÅIJ ¡˛ @ÿ)¬É«∏ÊIä xP!Aé?q¡D¿⁄J$Å(≤ë"K4–)†"BQe"Föi ⁄˛/¬0•Ç“D‡"R '‰aJ!úr ⁄AQM¢Cdfl'Z@â¢õDã‡Ç@⁄Åéy#ÇG,‰ë`‡ûÚGúuÄ⁄˝˚¸¸Ÿ˝ı¸Ÿ˝ı¸Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¸

¿œ"˚Äœ(B˛
Œ(Û» ÄvôÊ∏¥
<`–HI(–ÄãhíìX
ê–|ä0‡Å
Iê)œÑíYçô)d -0–
üeê‡p‰íœ£†áHƒ–
˝˛ÄŒ
˝ é˝ ¡<xxËÕ$˛$
Õ!B˛ LÕ!B#œ†pt<Ä–!B—E4†Hò‘Ä–BÑ‚ä" åê‚Ä–DâÀI@ài·œ¯!‰í~AÒ܆‚œÙœÙœÙœ¡:@˝
ÅÄÃò@

@
˜

@
˜c4£+¿˝B@Ã
$ÄÄ@Ã
$çiºvÉ@Ã
$Ö&2HãÄÄà    I
$I
ÅÀ
MíÃDÒÇ@Ã
ÈtCP‰Äá¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜£4„+¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜„4
#+¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜
#4
U+¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜ˇc4ˇ£+
¡¡À30¯À¯ ïÀ¯À¯À¯ ïÀ¯ ïÀ¯À¯À¯ ˚˜ˇ¿Û˜ˇ¯¯¯˙˜`Û˜¯¯ ˚˜pÛ˜¯¯˙˜XÛ˜¯¯˙˜LÛ˜
Ģ¯˙˜FÛ˜
¿˘¯ ˚˜CÛ˜
`˘¯˙˜
AÄÙ˜
0˘¯ ˚˜
@¿Ù˜
˘¯˙˜
@`Ù˜
˘¯˙˜
@0Ù˜
˘¯˙˜
@Ù˜
˘¯ ˚˜
@Ù˜
Ä˙¯˙˜
@Ù˜¿˙¯ ˚˜
@Ù˜`˙¯˙˜@
Äı˜0˙¯˙˜@¿ı˜˙¯˙˜@`ı˜˙¯ ˚˜@0ı˜˙¯!˙†¿»Äˇ¯ı˜ˇ˛˙¯! ˚ˇ˝¿ø˝¿{‡ıı˙¯˙ø˝¿ˇ˝¿{‡ıı˙¯˙ııı˙¯˙ııı˙¯! ˚ˇ/
Ø€˝mıı˙¯˙óm
mYógıı˙¯! ˚fl.
Óö˝kıı˙¯˙    @Ä@˛ıı˙¯˙ıı˘d˘˙¯#˙ˇ/
ÔŸˇ/ıi˛˘˙¯% ˚ïe
%Kùmıy~˘˙¯˙˛k
Ôôˇ.ıı˙¯! ˚    @Ä@˛ıı˙¯˙ııˇ¢r˚˙¯&˙˝o
ÔY◊mıı‚˚o¯¸˙¯&˙∑e
/Àø/ıØ„˚O¯¸˙¯! ˚ˇn
Ô€˜oıı˙¯˙    @Ä@˛ıı˙¯ ˚ııı˙¯˙fl/
ß[˜mıı˙¯˙øe
oŸùgıı˙¯˙ˇk
Á€Áeıı˙¯! ˚    @Ä@˛ıı˙¯˙ıı†¿`à"˙¯! ˚ıı˜nÌˇ{˙˚ÛÔ˛˙¯˙ıı∑nÌˇ{˙˙ÛÔ˛˙¯$˙ı˝˛ˇÄ˛˚ ˙¯˙ı˝˛ˇÄ˛ı˙¯  ˚ı˝˛ˇÄ˛ı˙¯"˚»¯˝IJı˙¯ò@@Ä
˜@Ä
˜ˇ£4ˇ„+
$ ¸
ı˝ˇûIJ¯3
8˙¯+˚
@
à
ë˛˝ˇøIJ¯Ã
˙¯-˚‹
ÔÓ˝¿˛0ˇsÉIJ
˘
˙¯2˚ˇÿ
oÏ˝¿˛8ˇaÉIJbd@˙¯6 ‡E˛˝?˝ˇÏˇa˚ŸˇÉÔÄ{˚Ä=
¯2    êD˘
1˝ˇs˚Ÿ¡Ô[˚=
¯6 ôu73>ˇ'
Ô€˝e¸"#?Ÿ"c

˛
ó3kõ¯1ÈM|˙ïo
-[ó/ ˝ˆŸ0¯    î¸ ~¯7âMl¬fl'
Ø€ˇ'$˝DFŸDaº‡{ˆ¿?YAˇˇëîÏJb¯7áu4∫@Ä@(˝àåÜŸà¿ï‡KV¿%À¿w3Àû¯) ¸
ˆ?˝ˇ¯9«˚ŸˇÉú‡kˆ¿?…√˙¯2˚ˇg
€˜/˛0pÁ˚IJ
 
˙¯/ ¸ï/
/Kùo˛ ˇIJ˘˙¯1˚˝o
Áõ˜o˝ˇIJº‡yv¿=À¿˙¯0˚
»˛Dƒ˝D@˝IJ
ï‡K“¿'[¡˙¯*˙¯à
˝˛ˇÄ˛ù‡yÊ¿=€¿˙¯- ˚flo
ÌK◊e˝˛ˇÄ˛;˘3
˙¯*˙µ%
'€ø/˝˛ˇÄ˛
¯U
8˙¯! ˚›n
Ô€˜oıı˙¯˙    @Ä@˛ıı˙¯˙ı˝x@@IJı˙¯'˙˜/
≠[ˇo˝Ä@@IJı˙¯) ˚üm
o…ó%˝wLa˘˛ı˙¯'˙ˇn
Ô€Ô/˝)fiÚLò˛ı˙¯2 ˚    @Ä@˛˝é–“t˲
†˛
 ˙¯'˙ı˝sŒa‹¯˛øœ˚w›ˇ€˘ø˙¯(˙ˇ/
Á…◊oıøœ˚w›ˇ€˘ø˙¯#˙óe
m€Ω%ı˛˘˙¯! ˚ˇo
ÔÀ˜iıı˙¯(˙    @Ä@˛ı
ÄBÄ
Ç(˙¯! ˚ıı
flœˆˇfl∑ÔÌÄ˙¯˙ıı
flœˆˇfl∑ÔÌ˙¯˙ıı˛¸
˙¯˙ııı˙¯ ˚ıı
B@¸˙¯˙ıı
{˜˚›¿¸˙¯ ˚ıı
{˜˚›¿¸˙¯˙ııı˙¯˙ııı˙¯(˙ˇ/
߀ˇmı˛    0a
˙¯* ˚ïm
oYùgı
øø~ˇ◊w}˙¯(˙fl.
ØöÔkı
øø~ˇ◊w}˙¯* ˚    @Ä@˛ı ˛@˛˙¯˙ııı˙¯(˙ˇo
ÌY˜/ıò@!†˙¯(˙ï%
'Àùmı
øfl˘fl{˚flΩ˚ˇ˙¯* ˚˝k
ÌŸ˜nı
fl˘fl{˚flΩ˚ˇ˙¯&˙    @Ä@˛ı˝¿˝˙¯ ˚ııı˙¯#˙flo
ÁY◊mıAĢ˙¯#˙µ%
-Àø/ı
Ô‡˘˙¯#˙›n
Á€˜oı
Ô¿˘˙¯% ˚    @Ä@˛ı˛@˘˙¯˙ııı˙¯! ˚˜%
ß[ˇ-ıı˙¯˙üo
oŸóoıı˙¯˙ˇo
Á€Ôoıı˙¯˙    @Ä@˛ıı˙¯ ˚ııı˙¯˙ııı˙¯ ˚ııı˙¯˙ııı˙¯˙ııı˙¯˙ııı˙¯ò@Ä¿
˜Ä¿
˜ˇ„4#+
 ˚ıˇ¸ıÙˇ˙¯˙ıˇ¸ı
Ùˇ˙¯ ïÀ¯À¯À¯ ïÀ¯ ïÀ¯À¯À¯ ïÀ¯À32¯Àï¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡>xÄ1Ä…"$
J@… Bà@…8B
@…HB
Ä…
@Ñd»Bà!"@…˝¿«Ä…¡¡¡¡">`¿ò0¸
l0˛
Ä@@‚ "˛Å !ĸ ¸ÄÄÄ‚  ˝Ä
! ¸B˝
˛ÄÄ‚%!8cµ¢Ä
ö9Ï&Äk¿AO3û◊ÖÉË„õF·4„%!HÕÕ
@J%2t”ëA¶ödJ
"ö    ®î•åñò„%!@â(éÄTF!$‚
Å»íHT%"QA    „%!A&KÅ !•[L…
:¬‰òñuØâïiNh „%!·Œ}¿gã>"wH‰ ‘Å≈ºÁ$A©¯é2á „˛˚¸ ˚@Ÿ
˛˚Ã
˛˚á>É
É…"˛Δ…   …8)Ûs¡J5„G@ŒH”&âARH§öiÄŒA%
ÅdâHíqÕC|…¬DùiÃÇÕ¸∑N‰É\jFúrÕ˜"Ãò@¿

˜¿

˜#4c+
˜"Øá$c8aÄ0`¿˝¿0†˝¿0‰
!Ä¿˛
˝˝
@›#R 
@IJ@¸„'#RH'ée)Fò˝«¿‹-Û»ÿo7<”iöxÿfi7<Â'#JjH"í⁄h*I%îàß@H÷$I)§íhîm6ä)•$hîÂ'#Lr–E¢p,ëA(êí@"à‰Dä1AP®!I$îQB$P®Â'#ÑÉ`E•/ÄHìŒmLÄ"—NíZM<ë,¢ìI•ZNxë,Â'#ƒr@È9÷pkç3…tàtêË5eì∞‘ÓHíI>ì±®ÓHÂÚ˛

÷Ó

÷Ó
é÷¡
 @
ɲ&0`ÿ@ĸ
˛0I¸ ÿ
ÅIJ ¡˛ @ÿ)¬É«∏ÊIä xP!Aé?q¡D¿⁄J$Å(≤ë"K4–)†"BQe"Föi ⁄˛/¬0•Ç“D‡"R '‰aJ!úr ⁄AQM¢Cdfl'Z@â¢õDã‡Ç@⁄Åéy#ÇG,‰ë`‡ûÚGúuÄ⁄˝˚¸¸Ÿ˝ı¸Ÿ˝ı¸Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¸

¿œ"˚Äœ(B˛
Œ(Û» ÄvôÊ∏¥
<`–HI(–ÄãhíìX
ê–|ä0‡Å
Iê)œÑíYçô)d -0–
üeê‡p‰íœ£†áHƒ–
˝˛ÄŒ
˝ é˝ ¡<xxËÕ$˛$
Õ!B˛ LÕ!B#œ†pt<Ä–!B—E4†Hò‘Ä–BÑ‚ä" åê‚Ä–DâÀI@ài·œ¯!‰í~AÒ܆‚œÙœÙœÙœ¡:@˝
ÅÄÃò@

@
˜

@
˜c4£+
¿˝B@Ã
$ÄÄ@Ã
$çiºvÉ@Ã
$Ö&2HãÄÄà    I
$I
ÅÀ
MíÃDÒÇ@Ã
ÈtCP‰Äá¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜£4„+
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜„4
#+
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜
#4
U+
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜
U4
ï+¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜
ï4
’+¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜
’4+¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜4U+¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜U4ï+¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜ï4’+¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜’4+¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜4G+¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜
U4
ï+
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜
ï4
’+
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜
’4+
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜4U+
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜U4ï+
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜ï4’+
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜’4+
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜4G+
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡4uFvGò@@
˜@
˜vG∂>¡¡?Ãˇ¸¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯ò@@Ä
˜@Ä
˜∂Gˆ>?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯ò@Ä¿
˜Ä¿
˜ˆG
6>?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯?Ãˇ˛¯Ãˇ˛¯¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡>xÄ1Ä…"$
J@… Bà@…8B
@…HB
Ä…
@Ñd»Bà!"@…˝¿«Ä…¡¡¡¡">`¿ò0¸
l0˛
Ä@@‚ "˛Å !ĸ ¸ÄÄÄ‚  ˝Ä
! ¸B˝
˛ÄÄ‚%!8cµ¢Ä
ö9Ï&Äk¿AO3û◊ÖÉË„õF·4„%!HÕÕ
@J%2t”ëA¶ödJ
"ö    ®î•åñò„%!@â(éÄTF!$‚
Å»íHT%"QA    „%!A&KÅ !•[L…
:¬‰òñuØâïiNh „%!·Œ}¿gã>"wH‰ ‘Å≈ºÁ$A©¯é2á „˛˚¸ ˚@Ÿ
˛˚Ã
˛˚á>É
É…"˛Δ…   …8)Ûs¡J5„G@ŒH”&âARH§öiÄŒA%
ÅdâHíqÕC|…¬DùiÃÇÕ¸∑N‰É\jFúrÕ˜"Ãò@¿

˜¿

˜
6G
v>˜"Øá$c8aÄ0`¿˝¿0†˝¿0‰
!Ä¿˛
˝˝
@›#R 
@IJ@¸„'#RH'ée)Fò˝«¿‹-Û»ÿo7<”iöxÿfi7<Â'#JjH"í⁄h*I%îàß@H÷$I)§íhîm6ä)•$hîÂ'#Lr–E¢p,ëA(êí@"à‰Dä1AP®!I$îQB$P®Â'#ÑÉ`E•/ÄHìŒmLÄ"—NíZM<ë,¢ìI•ZNxë,Â'#ƒr@È9÷pkç3…tàtêË5eì∞‘ÓHíI>ì±®ÓHÂÚ˛

÷Ó

÷Ó
é÷¡
 @
ɲ&0`ÿ@ĸ
˛0I¸ ÿ
ÅIJ ¡˛ @ÿ)¬É«∏ÊIä xP!Aé?q¡D¿⁄J$Å(≤ë"K4–)†"BQe"Föi ⁄˛/¬0•Ç“D‡"R '‰aJ!úr ⁄AQM¢Cdfl'Z@â¢õDã‡Ç@⁄Åéy#ÇG,‰ë`‡ûÚGúuÄ⁄˝˚¸¸Ÿ˝ı¸Ÿ˝ı¸Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¸

¿œ"˚Äœ(B˛
Œ(Û» ÄvôÊ∏¥
<`–HI(–ÄãhíìX
ê–|ä0‡Å
Iê)œÑíYçô)d -0–
üeê‡p‰íœ£†áHƒ–
˝˛ÄŒ
˝ é˝ ¡<xxËÕ$˛$
Õ!B˛ LÕ!B#œ†pt<Ä–!B—E4†Hò‘Ä–BÑ‚ä" åê‚Ä–DâÀI@ài·œ¯!‰í~AÒ܆‚œÙœÙœÙœ¡:@˝
ÅÄÃò@

@
˜

@
˜
vG
∂>¿˝B@Ã
$ÄÄ@Ã
$çiºvÉ@Ã
$Ö&2HãÄÄà    I
$I
ÅÀ
MíÃDÒÇ@Ã
ÈtCP‰Äá¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜
∂G
ˆ>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜
ˆG6>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜6Gh>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜vG∂>
¡¡À30¯À¯ ïÀ¯À¯À¯ ïÀ¯ ïÀ¯À¯À¯ ˚˜ˇ¿Û˜ˇ¯¯¯˙˜`Û˜¯¯ ˚˜pÛ˜¯¯˙˜XÛ˜¯¯˙˜LÛ˜
Ģ¯˙˜FÛ˜
¿˘¯ ˚˜CÛ˜
`˘¯˙˜
AÄÙ˜
0˘¯ ˚˜
@¿Ù˜
˘¯˙˜
@`Ù˜
˘¯˙˜
@0Ù˜
˘¯˙˜
@Ù˜
˘¯ ˚˜
@Ù˜
Ä˙¯˙˜
@Ù˜¿˙¯ ˚˜
@Ù˜`˙¯˙˜@
Äı˜0˙¯˙˜@¿ı˜˙¯˙˜@`ı˜˙¯ ˚˜@0ı˜˙¯!˙†¿»Äˇ¯ı˜ˇ˛˙¯! ˚ˇ˝¿ø˝¿{‡ıı˙¯˙ø˝¿ˇ˝¿{‡ıı˙¯˙ııı˙¯˙ııı˙¯! ˚ˇ/
Ø€˝mıı˙¯˙óm
mYógıı˙¯! ˚fl.
Óö˝kıı˙¯˙    @Ä@˛ıı˙¯˙ıı˘d˘˙¯#˙ˇ/
ÔŸˇ/ıi˛˘˙¯% ˚ïe
%Kùmıy~˘˙¯˙˛k
Ôôˇ.ıı˙¯! ˚    @Ä@˛ıı˙¯˙ııˇ¢r˚˙¯&˙˝o
ÔY◊mıı‚˚o¯¸˙¯&˙∑e
/Àø/ıØ„˚O¯¸˙¯! ˚ˇn
Ô€˜oıı˙¯˙    @Ä@˛ıı˙¯ ˚ııı˙¯˙fl/
ß[˜mıı˙¯˙øe
oŸùgıı˙¯˙ˇk
Á€Áeıı˙¯! ˚    @Ä@˛ıı˙¯˙ıı†¿`à"˙¯! ˚ıı˜nÌˇ{˙˚ÛÔ˛˙¯˙ıı∑nÌˇ{˙˙ÛÔ˛˙¯$˙ı˝˛ˇÄ˛˚ ˙¯˙ı˝˛ˇÄ˛ı˙¯  ˚ı˝˛ˇÄ˛ı˙¯"˚»¯˝IJı˙¯ò@@Ä
˜@Ä
˜∂Gˆ>
$ ¸
ı˝ˇûIJ¯3
8˙¯+˚
@
à
ë˛˝ˇøIJ¯Ã
˙¯-˚‹
ÔÓ˝¿˛0ˇsÉIJ
˘
˙¯2˚ˇÿ
oÏ˝¿˛8ˇaÉIJbd@˙¯6 ‡E˛˝?˝ˇÏˇa˚ŸˇÉÔÄ{˚Ä=
¯2    êD˘
1˝ˇs˚Ÿ¡Ô[˚=
¯6 ôu73>ˇ'
Ô€˝e¸"#?Ÿ"c

˛
ó3kõ¯1ÈM|˙ïo
-[ó/ ˝ˆŸ0¯    î¸ ~¯7âMl¬fl'
Ø€ˇ'$˝DFŸDaº‡{ˆ¿?YAˇˇëîÏJb¯7áu4∫@Ä@(˝àåÜŸà¿ï‡KV¿%À¿w3Àû¯) ¸
ˆ?˝ˇ¯9«˚ŸˇÉú‡kˆ¿?…√˙¯2˚ˇg
€˜/˛0pÁ˚IJ
 
˙¯/ ¸ï/
/Kùo˛ ˇIJ˘˙¯1˚˝o
Áõ˜o˝ˇIJº‡yv¿=À¿˙¯0˚
»˛Dƒ˝D@˝IJ
ï‡K“¿'[¡˙¯*˙¯à
˝˛ˇÄ˛ù‡yÊ¿=€¿˙¯- ˚flo
ÌK◊e˝˛ˇÄ˛;˘3
˙¯*˙µ%
'€ø/˝˛ˇÄ˛
¯U
8˙¯! ˚›n
Ô€˜oıı˙¯˙    @Ä@˛ıı˙¯˙ı˝x@@IJı˙¯'˙˜/
≠[ˇo˝Ä@@IJı˙¯) ˚üm
o…ó%˝wLa˘˛ı˙¯'˙ˇn
Ô€Ô/˝)fiÚLò˛ı˙¯2 ˚    @Ä@˛˝é–“t˲
†˛
 ˙¯'˙ı˝sŒa‹¯˛øœ˚w›ˇ€˘ø˙¯(˙ˇ/
Á…◊oıøœ˚w›ˇ€˘ø˙¯#˙óe
m€Ω%ı˛˘˙¯! ˚ˇo
ÔÀ˜iıı˙¯(˙    @Ä@˛ı
ÄBÄ
Ç(˙¯! ˚ıı
flœˆˇfl∑ÔÌÄ˙¯˙ıı
flœˆˇfl∑ÔÌ˙¯˙ıı˛¸
˙¯˙ııı˙¯ ˚ıı
B@¸˙¯˙ıı
{˜˚›¿¸˙¯ ˚ıı
{˜˚›¿¸˙¯˙ııı˙¯˙ııı˙¯(˙ˇ/
߀ˇmı˛    0a
˙¯* ˚ïm
oYùgı
øø~ˇ◊w}˙¯(˙fl.
ØöÔkı
øø~ˇ◊w}˙¯* ˚    @Ä@˛ı ˛@˛˙¯˙ııı˙¯(˙ˇo
ÌY˜/ıò@!†˙¯(˙ï%
'Àùmı
øfl˘fl{˚flΩ˚ˇ˙¯* ˚˝k
ÌŸ˜nı
fl˘fl{˚flΩ˚ˇ˙¯&˙    @Ä@˛ı˝¿˝˙¯ ˚ııı˙¯#˙flo
ÁY◊mıAĢ˙¯#˙µ%
-Àø/ı
Ô‡˘˙¯#˙›n
Á€˜oı
Ô¿˘˙¯% ˚    @Ä@˛ı˛@˘˙¯˙ııı˙¯! ˚˜%
ß[ˇ-ıı˙¯˙üo
oŸóoıı˙¯˙ˇo
Á€Ôoıı˙¯˙    @Ä@˛ıı˙¯ ˚ııı˙¯˙ııı˙¯ ˚ııı˙¯˙ııı˙¯˙ııı˙¯˙ııı˙¯ò@Ä¿
˜Ä¿
˜ˆG
6>
 ˚ıˇ¸ıÙˇ˙¯˙ıˇ¸ı
Ùˇ˙¯ ïÀ¯À¯À¯ ïÀ¯ ïÀ¯À¯À¯ ïÀ¯À32¯Àï¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡>xÄ1Ä…"$
J@… Bà@…8B
@…HB
Ä…
@Ñd»Bà!"@…˝¿«Ä…¡¡¡¡">`¿ò0¸
l0˛
Ä@@‚ "˛Å !ĸ ¸ÄÄÄ‚  ˝Ä
! ¸B˝
˛ÄÄ‚%!8cµ¢Ä
ö9Ï&Äk¿AO3û◊ÖÉË„õF·4„%!HÕÕ
@J%2t”ëA¶ödJ
"ö    ®î•åñò„%!@â(éÄTF!$‚
Å»íHT%"QA    „%!A&KÅ !•[L…
:¬‰òñuØâïiNh „%!·Œ}¿gã>"wH‰ ‘Å≈ºÁ$A©¯é2á „˛˚¸ ˚@Ÿ
˛˚Ã
˛˚á>É
É…"˛Δ…   …8)Ûs¡J5„G@ŒH”&âARH§öiÄŒA%
ÅdâHíqÕC|…¬DùiÃÇÕ¸∑N‰É\jFúrÕ˜"Ãò@¿

˜¿

˜
6G
v>
˜"Øá$c8aÄ0`¿˝¿0†˝¿0‰
!Ä¿˛
˝˝
@›#R 
@IJ@¸„'#RH'ée)Fò˝«¿‹-Û»ÿo7<”iöxÿfi7<Â'#JjH"í⁄h*I%îàß@H÷$I)§íhîm6ä)•$hîÂ'#Lr–E¢p,ëA(êí@"à‰Dä1AP®!I$îQB$P®Â'#ÑÉ`E•/ÄHìŒmLÄ"—NíZM<ë,¢ìI•ZNxë,Â'#ƒr@È9÷pkç3…tàtêË5eì∞‘ÓHíI>ì±®ÓHÂÚ˛

÷Ó

÷Ó
é÷¡
 @
ɲ&0`ÿ@ĸ
˛0I¸ ÿ
ÅIJ ¡˛ @ÿ)¬É«∏ÊIä xP!Aé?q¡D¿⁄J$Å(≤ë"K4–)†"BQe"Föi ⁄˛/¬0•Ç“D‡"R '‰aJ!úr ⁄AQM¢Cdfl'Z@â¢õDã‡Ç@⁄Åéy#ÇG,‰ë`‡ûÚGúuÄ⁄˝˚¸¸Ÿ˝ı¸Ÿ˝ı¸Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¸

¿œ"˚Äœ(B˛
Œ(Û» ÄvôÊ∏¥
<`–HI(–ÄãhíìX
ê–|ä0‡Å
Iê)œÑíYçô)d -0–
üeê‡p‰íœ£†áHƒ–
˝˛ÄŒ
˝ é˝ ¡<xxËÕ$˛$
Õ!B˛ LÕ!B#œ†pt<Ä–!B—E4†Hò‘Ä–BÑ‚ä" åê‚Ä–DâÀI@ài·œ¯!‰í~AÒ܆‚œÙœÙœÙœ¡:@˝
ÅÄÃò@

@
˜

@
˜
vG
∂>
¿˝B@Ã
$ÄÄ@Ã
$çiºvÉ@Ã
$Ö&2HãÄÄà    I
$I
ÅÀ
MíÃDÒÇ@Ã
ÈtCP‰Äá¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜
∂G
ˆ>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜
ˆG6>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜6Gh>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜hG®>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜®GË>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜ËG(>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜(Gh>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜hG®>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜®GË>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ËG(>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜(GZ>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜hG®>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜®GË>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜ËG(>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜(Gh>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜hG®>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜®GË>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ËG(>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜(GZ>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡†Ç†é


˙âÇ
’ò@0
˛0
˛
˙â
’¬ˇ¸Ä√Ä√ü√ˇÏü√ˇÃò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√LòÔ˘
ˆˇ¸ÎLòÊ
ˆÎLòÔ˘
ˆÎLòÊ
ˆÎLòÔ˘
¿
3¿˝ÎL'ò¸Ä0
?ÅÄ0¸ˆ

IJ|¿L*ò¸
¿ˆ˘
AÅÛ<«èáˆ

IJf¿L-ò¸Õû31„3Ú
¸AÉ3˛ÃÅˇΔ¯ˇ¡Éœ¯ffiyÁÄL.ò¸
Œ¸3˚˘
A„3ÃÃŒˇÜ¯!ÜlÕfÊû¿L*ò¸
å¸3Ú
AÉ3Ãë¯!Ülï|Δë¿L1ò¸?33Û3˚˘

AÉ3ÃÃ√Ä>¯!ÜlÕò`Δ¸Ã¿L-ò¸0333Ú

AÉ3ÃÅį!ÜlÕò`Δ¿Ã¿L1ò¸1232˚˘
¡ÒÛ«å«¯ˇ¡ÜlÕò`ΔƒÃ¿L&ò¸<1„¸Ú
ˇ¿˘ˆ
ÛÃï`Δxg¿LòÔ˘
ˆÎLòÊ
ˆÎLòÔ˘
ˆÎLòÊ
ˆˇ˛ÎLòÔ¯ˆˇ˛ÎLò√L
òÔ÷Lò√L
òÔ÷LòÌ?ÁˇÛLòÔ ÈÛLòÌ ÈÛLòÔ È˘ˇ˛LòÌ ˝00Û(˘
ÄL!òÔ ‡˛00ÛD¯ÄL òÌ!Ä1·¿><xÙÇ ¯@L"òÔ!@#33 fF1Ù    
 ¯@L&òÌ!@33Äf>0¯Ù«ê *Ä@L,òÙ¿˝!@33Ò¿ff1òÙD 
˛@L*òÙ‡˚!@33‡ff1òÙD  †¢Ä@Lò@0`
˛0`
˛â8
’+òÙ‡˝!@33`ff1òÙD ˛˛@L*òÙ‡˚!@1·¿>>¯Ù| (àÄÄ@L#òÙ‡˝ ˇÄÎ Q
˛@LòÙÄ˚ È      ˛Ä@L!òÙÄ˝ Èˇ 
˛@L"ò˜Ä˚ È *††Ä@L"ò˜Ä˝ È ˛¸@L ò˜Ä˚ È ˛à¸@L"ò˜Ä˝ È ˛P¸@L$ò˜˙ ™Ä ˚ı¯ÄL%ò˜˙!U@˚
ı˘
ÄL'ò˜¯ ÄÄ

 †Ä(˛†
¢Äˆ˘ˇ˛L"ò˜˙
!@
Q˛AıÛL ò˜<¯ ÄÄ
""Ä ˛àÇıÛL"ò˜L˙!@Q@AQ
ıÛL%ò˙X
˙ ÄÄ""† ÄààÇıÛL'ò˙˝
Ä˝!U@˛@A

ıÛL&ò˙˝
Ä˚ ™Ä

 †Ä ˛†
ÄĈÛLò˙0˝
Ä˝ ˘
ÚÛLò˚
`˝˙ ¯ÄÛÛL"ò˚
@˛
–¸ È˘ˇ˛L ò˚
¿˛
@˙ È˘
ÄL!ò˚Ä@‡¸ ȯÄL ò¸p˛‡˙ È ¯@Lò¸ı È ¯@L"ò¸@ˆ È ¯
Ä¿˛@L$ò¸@¯ È Ã
Ä¿˛@L%ò¸    @@˘ È Ãxqô„«¿@L'ò¸@¿˚ È ÃÃ…∞Δf`@L%ò¸@
¿˘ È Ã÷‡Δf`@L'ò¸‡
¿˚ È øq¿Δf`@L%ò¸Ë‡@˘ È ÿ9‡Δf`@L'ò˝
∏¿˙ È Ãô∞Δf`@L%ò˝
∏
Ä
‰¯ È ¯xqòc«¿@Lò˜¯˙ È ˚@Lò˜p¯ È ˚@LòÔ È ¯@Lò˚ ˆ ȯÄLò˚8¯ È˘
ÄLò˚<Ę È˘ˇ˛Lò˚ ?‡˘ ÈÛLò˚ ?¯˜ ÈÛLò˚0˛˘ ÈÛLò˚ˇ¿¯ ÈÛLò˚ˇ˙ ÈÛLò˚–ˇˇ¯ ÈÛLò˚ˇˇ‡˙ ÈÛLò¸

ˇˇ‡¯ È˘ˇ˛Lò@`ê
˛`ê
˛8âX
’!ò¸
‡
ˇˇ¿˙ È˘
ÄLò˙ˇˇ¿¯ ȯÄL!ò˙ˇˇ¿˙ È ˚@L ò˙ˇˇ¿¯ È ¸
@L$ò˙ˇˇÄ˙ È Dzˇ¯@L"ò˙ˇˇ¿¯ È ¬˛@L%ò˚
Ôˇˇ‡˙ È ‚<f`@L#ò˚˛ˇ‡¯ È Úff`@L%ò˚flˇˇ¯˙ È ∫ff`@L#ò˚˛ˇ¸¯ È û~f`@L$ò˚
ø˛ˇ˙ È é`f`@L#ò˚˝ˇ¿˘ È Übf@@L%ò˚˝ˇ¯˚ È Ç<Ä@Lò˚¸ˇ¯˘ È ¸@L!ò˚¸ˇ¸˚ È ¸ˇ¸@Lò¸
¸ˇ˛˘ È ¯@Lò¸
¸ˇ˛˚ ȯÄLò¸
¸ˇ˛˘ È˘
ÄL ò¸¸ˇ˛˚ È˘ˇ˛Lò¸¸ˇ¸˘ ÈÛLò¸?¸ˇ¯˚ ÈÛLò¸¸ˇ¯˘ ÈÛLò¸¸ˇ˚ ÈÛLò¸¸ˇ˛˘ ÈˇÛLò˝
˙ˇÄ¸ ÈÛLò˝˙ˇÄ˙ ÈÛLò˝˙ˇÄ¸ È|ÛLò˝˙ˇÄ˙ ÈDÛLò˝˙ˇÄ¸ ÈDÛLò˝˙ˇÄ˙ ÈD˜U@Lò˝˝ˇ˛ˇˇÄ¸ È«êÛLò˝˝ˇ¸?ˇÄ˙ È    
ÛLò¸?˛ˇˇ¸ ÈÇÛLò¸˛ˇ‡
¸˙ ÈDÛLò¸èˇˇ
∏¸ È(ÛLò¸˛ÿ
Ä˚ ÈÛLò¸¸Äp¿˝ ÈÛLò¸¸¿~`˚ ÈÛLò¸¸`˚‡˝?ÁˇÛLò¸¸˛8<p—Lò¸¸É¯<å˝÷Lò¸‹˛
—Lò¸ú˛

Ä˝‚˘ˇ˛Lò¸ú˛
p¿›˘
ÄLò¸‹˛@˝‚¯ÄLò¸‹√h› ¯@Lò¸ˇ‹ņ˝‚ ¯@Lò¸?ÿ=sÄâÙ› ¿˛@Lò@ê¿
˛ê¿
˛Xâw
’ò˘2'É¿êt˝‚  ˛@Lò¯epÄ4› «√áå@Lò˘K)@˝‚ ffLÃ@L)ò¯K˚

¸8¸1åÛ ÊfÃ@L*ò¯kFĸ
Ѹ`¸
ÄÛ ffÃ@L/ò¯-É˙
ƒxˇáÄx>303Ãx¯¿ˆ ff@L/ò¯
9˙    
‰åÃÿÃ`˛30331åÃÿˆ &ffLL@L.ò¯9 ˙
t|ÃÿÃ`˛30331åÃÃı √Êcáå@L*ò¯r@¸
<ÃÃœ¿Ã`3?30?31åÃÃı ¯@L&ò¯

¿¯

˛ÃÃ`3030031åÃÃı ¯@L)ò¯
§˙
˛Ã@Ã`313 131åÃÿˆ ¯@L'ò¯
¯
|ëÄx`3?¿0Ãxÿˆ¯ÄLò˜˙‚˘
ÄLòœ˘ˇ˛L
òÔ÷Lò√L
òÔ÷Lò√LòÔ?ÁˇÛLòÌ ÁÛLòÔ ÁÛLòÌ Á¯ˇÄLòÔ Á¯ˇ‡LòÌ Á˜ˇLòÔ!‡˛¿¿Ó
¯¯LòÌ
#˛¿Ï
«˘ˇ˛8L òÔ#gè`«èáÄÒÿ˘
ºLòÌ
#àÃÿûÃÿÒê¯úLòÔ#sÃÿëÃÿÒ†¯\LòÌ#3Ãÿ˝Ã¿Ò†¯\L$òÔ#3Ãÿ˝Ã¿Ò†Ä0\L"òÌ#3Ãÿ˝Ã¿Ò†Ä0\L%òÔ!„뿯«Ã«ÄÒ†ôüé>\LòÌ ¸¿Ì†˝ô3\LòÔ ¸¿Ì†ôôú3\LòÌ Á†ôôé3\LòÔ Á†ôôá3\LòÌ Á†ôôì3\LòÔ Á†üé3\LòÌ?Áˇ†¯\LòÔ„
†¯\Lò–
†¯\LòÔ„
ê¯úLò–
ÿ˘
ºLòÔ„

«˘ˇ˛8Lò–

¯¯L
òœ˜ˇLòœ¯ˇ‡Lò@¿
˛¿
˛wâñ
’òœ¯ˇÄLò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√Lü√ˇÃê√Ä√¬ˇ¸¬ˇ¸¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
 
˛
 
˛ñâµ
’'˘‡
‡
á‡|@˛ÄÄ?ê˛0Ä
Â&
Å@@@˝@
˛

Â)%Å Ä@√»ó8@àûá\0·áÁ(Å!Ä@DHòD@"Hëàô"`˝"HëÁ)%Ò    Ò„‰ @xDHêDèÅ"Hëà"@Ò"HäÁ(Å  @DHê|
Ä>Hëá>@˝"HÑÁ(Å  @DHê@Ä HëÄë @˝"HäÁ(ÅD@@DIêD"Iëàë"@˝"HëÁ)%˘‡
‡
ÉÄ@CΔê8¿Üûá@ÒáÁı@¯ˆ‰ˆ
@¯ˆ"‰ˆ
Äω¡¡¡¡¡¡¡¡¯ Ç Ä˛Δ ÄÛa≈Ä™8∞·„ãÄ–Å"&@íD…$LœÒ"$@Ç<àÚ$HœÅ"$@ÇDâ'»œÅ"$@ÇDâ$œÅ"$@ÇDâ$Hœ¯Ò!ƒ@Ç<àÒ„àœı Œˆ
 Œˆ

¿Œ¡¡¡¡+ƒ
  ÇÄ

˝0Ä@¸Ï(ƒ
˛ Δ˛

˝
˙Î0,§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`Ó0,§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âêÓ0,îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚âÓ0,
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"âÓ0,åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"âÓ0åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"âÓ0,ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àqÓÔ
¸
€Ô¸
€¡ò@
 
2
˛
 
2
˛µâ¡
’¡¡¡¡
Ä˝Ä—Ä
˝Ä—(xá
‚Ãxâ√ãÄa¿”(DààÅ
2DàÑLí ”DDààÅ
"DàÑH“DDàèÅ
"Dàồ˛Dàà

"DàÑ“ÇDààÅ    "DòÑH ”Çxá‚"xhcàƒ”˛
@ĸ@˛–˛
@ĸ@˛ –¡¡¡†è†Éˇ†@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-6    )B5Introduction to Publishers, Subscribers, and Editions4^*¿
¯
°dONLNd\lhr(el
Y@Ä°dONLNd
\rh¬)our application pr-¿°dONLNd\¬h
Ä)P+ovides a thumbnail sketch of the edition daÄ°dONLNd>\
Åh
Ø)øta, which t_†°dONLNdI\
Øh
º).he °dONLNdLiluè(rlEdition ëÄ°dONLNdTièu
)#Manager displays in the pryÄ°dONLNdni
u
+)weview ar7`°dONLNdvi
,u
¥)& ea of the publisher dialog box. =@°dONLNdñi
¥u
∫)à
Y˝¿°dONLNdói
πu
‘)our pr¥ °dONLNdùi
’u
Ò)eview °dONLNd£vlÇ
#(l+of the edition in this dialog box should prΔ °dONLNdŒv
#Ç
¬)∑%ovide a visual cue about the type of °dONLNdÛÉlè
C(ål2information that the user has selected to publish.°dONLNd
&ïl°s*
A∫†°dONLNd
'ïs°) pr
¿°dONLNd
*ïÄ°•)eview arø†°dONLNd
2ï•°
{)%2ea also appears in the subscriber dialog box (see †°dONLNd
dï
|°
î)◊Figurfi`°dONLNd
iï
ì°
ß)e 2-4{‡°dONLNd
nï
®°
´)
)œ¿°dONLNd
oï
´°
À). This pi`°dONLNd
wï
ð
œ)!
r.`°dONLNd
xï
–°
Í)eviewº@°dONLNd
}ï
È°
Î)
,<@°dONLNd
~ï
Ï°
Ó)
 °dONLNd
¢lÆÉ(´ltoo, sÍ`°dONLNd
Ö¢ÉÆ©)hould prɆ°dONLNd
碙Æ
⁄)'Fovide a visual cue about the type of information the edition contains.º@°dONLNd
Ӣ
ڮ
‹(´
⁄
 °dONLNd
‘Ølªz(∏lForw@°dONLNd
◊Ø{ª})
 ˜@°dONLNd
ÿØ}ª
 )Kexample, it should allow users to distinguish between text information and °dONLNd#ºl»z(≈lsprÑ °dONLNd&ºz»¡)eadsheet arrays.°dONLNd7Œl⁄
î(◊lCThe publisher dialog box uses the extended interface of the standarñ °dONLNdzŒ
î⁄
¢(◊
îd fi>†°dONLNd~Œ
£⁄
Ú)le dialog box that °dONLNdë€lÁ†(‰l
accompanie/Ä°dONLNdõ€°Á≤)5s Syª`°dONLNdü€≤Áæ)ste`°dONLNd¢€øÁ—)m 7.ÿ`°dONLNd¶€—Á
5) The user navigates thr•`°dONLNdΩ€
6Á
„)e(ough the contents of the disk using the °dONLNdÂËlÙª(Òlmouse or keyboarÈ`°dONLNdı˪Ù√)Od.°dONLNd¯˙l
s(
l
A∫†°dONLNd˘˙s

—)P user can modify a publisher within a document just like any other portion of a °dONLNdI
l
ù(
l
document. €†°dONLNdS
ù

’)1FAs a default, each time a user saves a document containing a publisher≠‡°dONLNdô

’

Ò(

’, your °dONLNd†
l
 
T(
l4application should automatically write the publisherÿ‡°dONLNd‘

U
 
¥)È’s data to the edition. ‚@°dONLNdÏ

¥
 
∫)_
Y¢¿°dONLNdÌ

∫
 
Ù)ou also need °dONLNd˙
!l
-Å(
*lto pr°dONLNdˇ
!Å
-
˜)Tovide the user with the choice of sending new publisher data to an edition manually °dONLNdS
.l
:”(
7l(that is, only at the userÎ@°dONLNdm
.‘
:˘)h    ’s specifi›†°dONLNdw
.˙
:
)&c r퇰dONLNdz
.

:
*)    equest). l°dONLNdÉ
.
*
:
0)%
Y,Ä°dONLNdÑ
.
0
:
i)ou should prˇ`°dONLNdê
.
h
:
È)8ovide these options by using °dONLNd≠
;l
G
D(
Dl2the publisher options dialog box described later i¿°dONLNdfl
;
D
G
L)ÿn B °dONLNd·
;
M
G
‡)     “Using Publisher and Subscriber °dONLNd

Hl
TÎ(
QlOptions” beginning on page b¿°dONLNd
HÏ
T˛)Ä2-43∂†°dONLNd 
H˛
T
)
.°dONLNd"
Zl
f
    (
cl"For example, one user may choose t[@°dONLNdD
Z


f
)ûo uW‡°dONLNdG
Z

f
b)pdate an edition Ä°dONLNdX
Z
c
f
¢)Kautomatically  `°dONLNdf
Z
¢
f
÷)?each time a °dONLNdr
gl
s
à(
pl?document is saved. This update mode is useful for a user who cr%`°dONLNd±
g
â
s
ı(
p
âeates a publisher within °dONLNd 
tl
ÄÅ(
}la spr °dONLNdœ
tÇ
Ę)eadsheet application that rÄ°dONLNdÍ
t˜
Ä
    )uecor쇰dONLNdÓ
t
    
Ä
Û)5ds stock information. Each time the user updates the °dONLNd#
Ål
ç
    (
äl#stock information and saves the sprh °dONLNdF
Å
    
ç
€)ù.eadsheet, a new edition automatically becomes °dONLNdt
él
ö’(
ólavailable to subscribers.°dONLNdé
†l
¨
o*8Another user may choose to update an edition only upon r¬°dONLNdΔ
†
o
¨
„(
©
oequest. This update mode °dONLNdfl
≠l
π˛(
∂l!might be useful for a user who crë °dONLNd
≠˛
π
É)íeates a publisher within a worÓ`°dONLNd
≠
É
π
ñ)Öd-pr% °dONLNd"
≠
ó
π
Û)ocessing application °dONLNd7
∫l
Δ…(
√lfor a quarterly sales r6°dONLNdN
∫ 
Δ
 )^eport. The user incrW`°dONLNdb
∫
 
Δ
†)Vementally updates the sales rn†°dONLNd
∫
†
Δ
Δ)Ä    eport thr=†°dONLNdà
∫
«
Δ
Ô)'oughout °dONLNdê
«l
ӑ(
–l    the entirh °dONLNdô
«ë
”¥)%e quarteP†°dONLNd°
«µ
”¿)$r bJ‡°dONLNd§
«¡
”
Ÿ)Aut does not want this information to be available to subscribers °dONLNdÂ
‘l
‡Ä(
›luntilk†°dONLNdÍ
‘Å
‡É)
 Ά°dONLNdÎ
‘É
‡‚)the end of the quarter˙†°dONLNd

‘‚
‡
Ã)_6. Only at the end of each quarter does the user specifi?¿°dONLNd8
‘
Õ
‡
‰)Îcally °dONLNd>
·l
Ìo(
Íl
rE°dONLNd?
·p
Ì
°)Fequest to update the edition and make it available to any subscribers.°dONLNdÜ
Ûl
ˇr(
¸l
Tµ¿°dONLNdá
Ûq
ˇÅ)o cr‡Ä°dONLNdã
ÛÅ
ˇ
ı)Ueate a subscriber within a document, the user places the insertion point and chooses °dONLNd‡lü(    lSubscribe T›¿°dONLNdÎû≠)2o frÏ °dONLNdÔ≠

)om the Edit menu. k`°dONLNd    


)UFigur> °dONLNd    

.)e 2-4€†°dONLNd    
.
), shows the dialog box that your application °dONLNd    7l
I(l0should display when the user chooses Subscribe T9°dONLNd    g
I
S)›o. ˇMñ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡ä5Introduction to Publishers, Subscribers, and Editions

, (‡    2-7
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHw4gHw"hH]

ˇ·ˇ‚7^    °dONLNd\äg¥(dä
Figure 2-4°dONLNd\Ãg
3)BThe subscriber dialog box
°dONLNd'
    ä

…(
äIThe subscriber dialog box also uses the extended interface of the standar†°dONLNdp
    
 

ÿ(

 d fi≈ °dONLNdt
    
ÿ
)le dialog box °dONLNdÇ
ä
"ô(
äintrA °dONLNdÜ
ö
"À)
oduced wit0‡°dONLNdê
Ã
"fl)2h SyQ °dONLNdî
fl
"Î)steö °dONLNdó
Î
"˝)m 7.n °dONLNdõ
˛
"
#)
 Initiallyu@°dONLNd•

"
")$7, the dialog box should highlight the name of the last °dONLNd‹
#ä
/
å(
,ä<edition published or subscribed to. This allows a user to crU°dONLNd

#
å
/
Á(
,
åeate a publisher and °dONLNd
-
0ä
<
*(
9ä%immediately subscribe to its edition.°dONLNd
S
Bä
Në*
A∫†°dONLNd
T
Bë
N«) subscriber rÄ°dONLNd
a
B»
N
)7eceives its data fr°dONLNd
t
B

N)L9om a single edition. By default, your application should °dONLNd
≠
Oä
[
(
XäRautomatically update a document containing a subscriber whenever a new edition is °dONLNd
ˇ
\ä
h∂*available. °dONLNd

\∑
hΩ)-
Y√Ä°dONLNd
\º
h
)ou also need to pr⁄`°dONLNd
\

h
°)O#ovide the user with the choice of rπ‡°dONLNd@
\
°
h)ñeceiving the latest edition °dONLNd\
iä
u
M(
rä,manually (that is, only when the user specifi)`°dONLNdâ
i
N
u
i)ƒcally r>Ä°dONLNdê
i
i
u
ö)equests it). ˇ`°dONLNdù
i
ö
u
†)1
Yø‡°dONLNdû
i
†
u
…)    ou can prE@°dONLNdß
i
 
u
˛)*ovide these °dONLNd≥
vä
Ç
≤(
äDoptions by using the subscriber options dialog box described later i¶`°dONLNd˜
v
≤
Ç
∫(

≤n ˜¿°dONLNd˘
v
∫
Ç)“Using Publisher °dONLNd

Éä
è
N(
åä*and Subscriber Options” beginning on page ÍÄ°dONLNd4
É
N
è
`)ƒ2-43>`°dONLNd8
É
a
è
c)
.°dONLNd:
ïä
°
'(
ûä"For example, one user may choose t[@°dONLNd\
ï
(
°
3)ûo r¿°dONLNd_
ï
4
°
ç)eceive new editions _‡°dONLNds
ï
ç
°
Ã)Yautomatically m¿°dONLNdÅ
ï
Ã
°)?as they become °dONLNdê
¢ä
Æ
Ì(
´äQavailable. This update mode is useful for a user who subscribes to information frÁ °dONLNd·
¢
Ì
Æ(
´
Ìom an °dONLNdÁ
Øä
ª
&(
∏ä&edition that consists of daily sales fi, °dONLNd
Ø
'
ª
6)ùgurá`°dONLNd
Ø
6
ª
 )"es. This user automatically acquirq†°dONLNd3
Ø
 
ª)îes each version °dONLNdC
ºä
»
[(
≈ä1of the sales information as it becomes available.°dONLNdu
Ί
⁄
*Another user may choose to rÒ¿°dONLNdë
Œ

⁄
ú)Ç eceive a new edition only upon rR`°dONLNd±
Œ
ù
⁄)ëequest. This update mode °dONLNd 
ۊ
Á¸(
‰äis useful for a user who crÜ°dONLNdÂ
€¸
Á)r@eates a subscriber to an edition that consists of graphics data °dONLNd%
Ëä
Ù
A(
Òä((such as a company logo). The user may rÕ†°dONLNdM
Ë
A
Ù
X)∑equir‰‡°dONLNdR
Ë
X
Ù    ))e only periodic versions of the logo and °dONLNd{
ıä
∫(
˛änot need fr¢Ä°dONLNdÜ
ı∫

ù)04equent updates. In this case, your application shoul‡@°dONLNd∫
ı
ù

´)„d uÉ °dONLNdΩ
ı
¨
)pdate the subscriber °dONLNd“äfl(äwith a new edition Ä°dONLNd‡ˆ)Vonly B‡°dONLNd͈
S)when the user specifi“ °dONLNdˇ
S
n)]cally rÁ@°dONLNd
n
ö)equests it.°dONLNdä ë(ä
A∫†°dONLNdë 
) user can select, cut, copy¸‡°dONLNd.ˇ 
K)n, or paste an entirå@°dONLNdA
L 
Ä)Me subscriber∞`°dONLNdM
Ä 
Ö)4. R°dONLNdO
Ö )Although the contents of the °dONLNdl!ä-
'(*ä"subscriber as a whole can be modifií°dONLNdè!
'-
Ô)ù/ed, a user cannot edit portions of a subscriberèÄ°dONLNdæ!
Ô-)». For °dONLNdƒ.ä:
f(7ä4example, a user can underline or italicize the entirΔ†°dONLNd¯.
f:
™)‹e subscriber tex\¿°dONLNd.
´:
∂)Et b¶¿°dONLNd.
∂:)ut cannot delete a °dONLNd;äG¬(Däsentence or rú`°dONLNd+;¬G
)8otate a single graphiU¿°dONLNd@;
G
()Zc oªÄ°dONLNdC;
(G
Z)bject. This rr†°dONLNdP;
[G
ê)3estriction prø†°dONLNd];
êG
Ÿ)5otects the user frß`°dONLNdo;
ŸG)I
om losing °dONLNdyHäT(QäUchanges to a subscriber when a new edition arrives. Remember that, as a default, new °dONLNdŒUäa
f*1editions should automatically update a subscriber§‡°dONLNdˇU
fa
k)‹. FÄ°dONLNd
U
ka)$Any changes that a user made to the °dONLNd%bän
 (kä"subscriber text would have to be rv°dONLNdGb
 n)ñ5eapplied by the user when the new edition arrives. SeDÄ°dONLNd|bn)Ìe °dONLNd~oä{
#(xä!“Modifying a Subscriber” on page W °dONLNdüo
${
6)ö2-59´°dONLNd£o
6{
;) f~‡°dONLNd•o
<{
†)or further information.†Ç†é

xäÒ
÷ò@0
˛0
˛xäó
÷¬ˇ¸Ä√Ä√ü√ˇÏü√ˇÃò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√LòÔ˘
ˆˇ¸ÎLòÊ
ˆÎLòÔ˘
ˆÎLòÊ
ˆÎLòÔ˘
¿
3¿˝ÎL'ò¸Ä0
?ÅÄ0¸ˆ

IJ|¿L*ò¸
¿ˆ˘
AÅÛ<«èáˆ

IJf¿L-ò¸Õû31„3Ú
¸AÉ3˛ÃÅˇΔ¯ˇ¡Éœ¯ffiyÁÄL.ò¸
Œ¸3˚˘
A„3ÃÃŒˇÜ¯!ÜlÕfÊû¿L*ò¸
å¸3Ú
AÉ3Ãë¯!Ülï|Δë¿L1ò¸?33Û3˚˘

AÉ3ÃÃ√Ä>¯!ÜlÕò`Δ¸Ã¿L-ò¸0333Ú

AÉ3ÃÅį!ÜlÕò`Δ¿Ã¿L1ò¸1232˚˘
¡ÒÛ«å«¯ˇ¡ÜlÕò`ΔƒÃ¿L&ò¸<1„¸Ú
ˇ¿˘ˆ
ÛÃï`Δxg¿LòÔ˘
ˆÎLòÊ
ˆÎLòÔ˘
ˆÎLòÊ
ˆˇ˛ÎLòÔ¯ˆˇ˛ÎLò√L
òÔ÷Lò√L
òÔ÷LòÌ?ÁˇÛLòÔ?Èˇ¯ÛLòÌ?Èˇ¯ÛLòÔ?Èˇ¯˘ˇ˛LòÌ?U√˛ˇÁˇÁÚˇ¯(˘
ÄLòÔ>™øù˛ˇÁˇ¯D¯ÄL!òÌ?üì‡Áıˇ¯Ç ¯@L#òÔ>ˇøüéÊfgÊfÊfgıˇ˘
 ¯@L'òÌ?ëüfgÊgfgıˇ˚«ê *Ä@L-òÙ¿˝
>ˇøôûffgÊ˛fgıˇ¯D 
˛@L+òÙ‡˚?ôûffgÊ˛fgıˇ¯D  †¢Ä@Lò@0`
˛0`
˛óä∑
÷,òÙ‡˝
>™øôûffgÊ˛fgıˇ¯D ˛˛@L+òÙ‡˚?U√üg‡Ágıˇ¯| (àÄÄ@L%òÙ‡˝?˙ˇÁÒˇ¯ Q
˛@L#òÙÄ˚?˙ˇÁÒˇ    ¯  ˛Ä@LòÙÄ˝?Áˇ     
˛@L"ò˜Ä˚?Èˇ¯ *††Ä@L"ò˜Ä˝ È ˛¸@L ò˜Ä˚ È ˛à¸@L"ò˜Ä˝ È ˛P¸@Lò˜˙ ȯÄLò˜˙ È˘
ÄL$ò˜¯
 ‡˛¿¿Û˘ˇ˛L ò˜˙!Ä¿¿ÛÛLò˜<¯!@8x«á¯Ò„¿ÙÛL!ò˜L˙!@dåÃÃÅôƒ`ÙÛL$ò˙X
˙!@p|ÃŒ
ò¯√‡ÙÛL&ò˙˝
Ä˝!@8Ãœ«
ôòΔ`ÙÛL$ò˙˝
Ä˚!@ÃÃÅôòΔ`ÙÛL&ò˙0˝
Ä˝!@LÃÃIÅôòΔ`ÙÛL$ò˚
`˝˙ ˇÄ8|«á¯¯c‡ÙÛL"ò˚
@˛
–¸ È˘ˇ˛L ò˚
¿˛
@˙ È˘
ÄL!ò˚Ä@‡¸ ȯÄL ò¸p˛‡˙ È ¯@Lò¸ı È ¯@L"ò¸@ˆ È ¯
Ä¿˛@L$ò¸@¯ È Ã
Ä¿˛@L.ò¸    @@˘ ™Ä¿˚ı Ãxqô„«¿@L0ò¸@¿˚!U@¿˚ı ÃÃ…∞Δf`@L1ò¸@
¿˘ ÄÄ8x«á
≥«√Δfiı Ã÷‡Δf`@L3ò¸‡
¿˚!@dåÃÃÅΔffgı øq¿Δf`@L1ò¸Ë‡@˘ ÄÄp|ÃŒ
ܲfı ÿ9‡Δf`@L3ò˝
∏¿˙!@8Ãœ«
áÊffı Ãô∞Δf`@L1ò˝
∏
Ä
‰¯ ÄÄÃÃÅÜffı ¯xqòc«¿@L*ò˜¯˙!U@LÃÃIÅÜ&ffı ˚@L(ò˜p¯ ™Ä8|«á
É«√Δı ˚@LòÔ ˘Ú ¯@Lò˚ ˆ ˘Ú¯ÄLò˚8¯ È˘
ÄLò˚<Ę È˘ˇ˛Lò˚ ?‡˘ ÈÛLò˚ ?¯˜ ÈÛLò˚0˛˘ ÈÛLò˚ˇ¿¯ ÈÛLò˚ˇ˙ ÈÛLò˚–ˇˇ¯ ÈÛLò˚ˇˇ‡˙ ÈÛLò¸

ˇˇ‡¯ ÈÛLò@`ê
˛`ê
˛∑ä÷
÷ò¸
‡
ˇˇ¿˙ ÈÛLò˙ˇˇ¿¯ ÈÛLò˙ˇˇ¿˙ ÈÛLò˙ˇˇ¿¯ ȘU@Lò˙ˇˇÄ˙ ÈÛLò˙ˇˇ¿¯ ÈÛLò˚
Ôˇˇ‡˙ ÈÛLò˚˛ˇ‡¯ ÈÛLò˚flˇˇ¯˙ ÈÛLò˚˛ˇ¸¯ ÈÛLò˚
ø˛ˇ˙ ÈÛLò˚˝ˇ¿˘ ÈÛLò˚˝ˇ¯˚ ÈÛLò˚¸ˇ¯˘ ÈÛLò˚¸ˇ¸˚ ÈÛLò¸
¸ˇ˛˘ ÈÛL ò¸
¸ˇ˛˚ È˘ˇ˛Lò¸
¸ˇ˛˘ È˘
ÄLò¸¸ˇ˛˚ ȯÄLò¸¸ˇ¸˘ È ¯@Lò¸?¸ˇ¯˚ È ¯@L#ò¸¸ˇ¯˘ È ¿˛@L%ò¸¸ˇ˚ È  ˛@L#ò¸¸ˇ˛˘ È «√áå@L%ò˝
˙ˇÄ¸ È ffLÃ@L#ò˝˙ˇÄ˙ È ÊfÃ@L%ò˝˙ˇÄ¸ È ffÃ@L#ò˝˙ˇÄ˙ È ff@L%ò˝˙ˇÄ¸ È &ffLL@L#ò˝˙ˇÄ˙ È √Êcáå@L"ò˝˝ˇ˛ˇˇÄ¸ È ¯@L ò˝˝ˇ¸?ˇÄ˙ È ¯@L"ò¸?˛ˇˇ¸ È ¯@L ò¸˛ˇ‡
¸˙ ȯÄL#ò¸èˇˇ
∏¸ È˘
ÄL"ò¸˛ÿ
Ä˚ È˘ˇ˛Lò¸¸Äp¿˝ ÈÛLò¸¸¿~`˚ ÈÛLò¸¸`˚‡˝ ÈÛLò¸¸˛8<p˚ ÈÛLò¸¸É¯<å˝ ÈÛLò¸‹˛
˚ ÈÛLò¸ú˛

Ä˝ ÈÛL!ò¸ú˛
p¿˚ ȯˇÄL#ò¸‹˛@˝ ȯˇ‡L ò¸‹√h˚ ȘˇL#ò¸ˇ‹ņ˝ È
¯¯L"ò¸?ÿ=sÄâÙ˚ È
«˘ˇ˛8Lò@ê¿
˛ê¿
˛÷äı
÷!ò˘2'É¿êt˝ Èÿ˘
ºLò¯epÄ4˚ Èê¯úL ò˘K)@˝ Ȇ¯\Lò¯K˚ Ȇ¯\L$ò¯kFĸ Ȇ00\L"ò¯-É˙ Ȇ0˛0\L"ò¯
9˙ Ȇ3>8€>\L"ò¯9 ˙ Èˇ†332d„33\L$ò¯r@¸ Ȇ338`√33\L ò¯

¿¯ Ȇ33`√3?\L"ò¯
§˙ È|†33`√30\L ò¯
¯ ÈD†33&d√31\L!ò˜˙ ÈD†>8√>\LòÌ ÈD†¯\LòÔ È«ê†¯\LòÌ È    
†¯\LòÔ ÈÇê¯úLòÌ ÈDÿ˘
ºLòÔ È(
«˘ˇ˛8LòÌ È
¯¯LòÔ È˜ˇLòÌ È¯ˇ‡LòÔ?Áˇ¯ˇÄLò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√Lü√ˇÃê√Ä√¬ˇ¸¬ˇ¸¡¡¡¡¡¡¡¡¡¡ò@¿
˛¿
˛ıä

÷¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡(˝    ˘‡
‡
Ä |@˛ÄÄ?ê˛

Ë'˝Å@`@˝@
IJ˛

Ë*˝$Å †@√»ó8@Äàû8ª\0·áÍ)˝Å! @DHòD@Ä"Hë"D¡"`˝"HëÍ*˝$Ò    Ò„‰" xDHêDèàÄ"ë @Å"@Ò"HäÍ)˝Å$ @DHê|
Ä>àë@Å>@˝"HÑÍ)˝Å'@DHê@¿ Hë@Å @˝"HäÍ)˝Å@ @DIêDÄ"Ië"DÅ"@˝"HëÍ*˝$˘‡
‡
Ä @CΔê8¿ÄÜû8Å@ÒáÍ
Û@ÎÁÙ
@Î"ÁÙ
ÄÎÁ¡¡¡˝¯ ÇÃ˝Ä˛ΔÃò@

˛

˛
ä
0
÷˝ÄÛa≈Ä™8∞·„ãÄ“˝Å"&@íD…$L—˝Ò"$@Ç<àÚ$H—˝Å"$@ÇDâ'»—˝Å"$@ÇDâ$—˝Å"$@ÇDâ$H—˝¯Ò!ƒ@Ç<àÒ„à—Û –Ù
 –Ù

¿–¡¡¡¡+˝ƒ
  ÇÄ

˝0Ä@¸Ó(˝ƒ
˛ Δ˛

˝
˙Ì0˝*§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`0˝*§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âê0˝*îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚â0˝*
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"â0˝*åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"â0˝
åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"â0˝*ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àqÌ
¸
›Ì¸
›¡¡¡¡¡˝
Ä˝Ä”˝Ä
˝Ä”˝(xá
‚Ãxâ√ãÄa¿’˝(DààÅ
2DàÑLí ’˝DDààÅ
"DàÑH‘˝DDàèÅ
"Dàố˝˛Dàà

"DàÑ‘˝ÇDààÅ    "DòÑH ’˝Çxá‚"xhcàƒ’¸
@ĸ@˛“¸
@ĸ@˛ “¡†è†Éˇ\¬@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-8    )B5Introduction to Publishers, Subscribers, and Editions4^*¿
¯
°dONLNd\lhs(el
A∫†°dONLNd
\sh
ƒ)I single document can contain any number or combination of publishers and °dONLNdJilu¢(rlsubscribers. T‡°dONLNdWi£uª)7Figur'†°dONLNd\iªuœ)e 2-5≈ °dONLNdaiœu
Á)= shows an example of a document that contains two publishers °dONLNdûvlÇ

(l"and one subscriber (and their corr,@°dONLNd¿v
Ç
„)ñ0esponding editions). Remember that data always fl*`°dONLNdÒv
„Ç
˜)·ows °dONLNdıÉlèñ(ål
in one dir`°dONLNdˇÉóèΩ)+
ection, fr◊¿°dONLNd
    ÉΩè
`)&%om publisher to edition to subscriberW °dONLNd
.É
`è
®)£. The “Concert flÏ`°dONLNd
?É
®è
Ì)Hyer” document °dONLNd
Mêlú
a(ôl8contains a publisher that is subscribed to by the “Benefií °dONLNd
Üê
aú
”)ıt concert” document. The °dONLNd
üùl©ú(¶l
“Concert flŸÄ°dONLNd
™ùú©
Δ)0Cyer” document also subscribes to a portion of the “Pianos & palm trôÄ°dONLNd
Ìù
«©
‹(¶
«ees” °dONLNd
Ú™l∂
(≥l%document. In addition, the “Concert fl2@°dONLNd™
∂
)©1yer” document as a whole is subscribed to by the °dONLNdI∑l√ö(¿l    “Sample fl‘†°dONLNdS∑ö√fl).yer” document.

Â*ˆ
¯4Ê*ˆ
¯"Ê*]

ˇ·ˇ‚7^
    °dONLNdc€lÊñ(„l
Figure 2-5°dONLNdn€ÆÊ¥)B
A0°dONLNdo€¥Ê
X)( document and its corresponding editions

ı*Ñ
¯4ÛÙ ò@@@Ù 
4 ¡¡¡    
–ˇÄı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ıò@@Ä@Ä
4 
t     
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ıò@Ä¿Ä¿
t 
¥     
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ıò@¿
¿

¥ 
Ù     
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ıò@

@

@
Ù 4     
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ıò@
@
Ä
@
Ä4 t     
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ıò@
Ä
¿
Ä
¿t ¥     
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı    
–ˇ¿ı¡¡¡¡¡¡¡¡¡¡¡¡¡¡˛û
¿p ˛âÄ$Ä ˛ÅE¿ ˛ÅÑ@ ˛ÅÑ  ˛!2à  ˛¢ê@ ˛?|‡cÄ ¡¡¡¡˛    ò
Ä8
0˙√˘ÿaĉ˛    Ä@@˙@˘@
‚˛˝@‡ ˝ ÄÄ˙Ä„'˛!⁄–Ä@ ß÷òèpk¬É«;t#ºs¬üá
yúÒ¿Ê'˛!6äc@Ä    H§SkE ëMâEò‘íâM2ö4”"R@Ê&˛ $îCÅÑP¿¢Kä!ëÑ Ö‚#
ë%DíB°Â'˛!K%Ñ@ ÖÒM,úA:◊â&ä!    %◊Õå_$ƒ¥ÄÊ&˛ 8w>ÉáÅ¿3¬Œ1Ùìí@‘ãr ÓX‰ãy-Á9'½
ÄÌ@˛"‡˝
ÄÌ@˛"‡˝χ˛‡¡˛ÉaÄ`¿À˛
Å˛
1ÄÀ˛2ÄÀ˛

yúRçx—≈†œ˛
4”"PTí)&ö¿œ˛
DíB†Y"R$úÄœ˛    fl$ƒ∞ë'Zs!Œ˛    ?-Á9 ◊ëߌˆ
ÄŒˆ
ÄŒˆÕ¡$˛¿0`0`¿˝`Ë˝`Âò@
¿
Ú
¿
Ú¥ Ê ˛@ `˝
@˝˝

fi#˛Ä@† IJ
¸
‰'˛!Öí    „±D£Losé∞˜çy‰f7ôœ¥ÙÕ<l7õûÊ'˛!öí§Êö$í≈$R–Rk$î…I2%[[E“I4JÊ'˛!¥BHúH†ä(Hê¢r"Eêâ$*RRJ(†â(TÊ'˛!! ÿiõ‡$IÁ+H• ¥Ñ'I-3ûLKh§‰“≠&ûHñÊ'˛!1ê:NÂú5Δô“G9"$t≤…Ãjsíá$§üIÿjw$Ê
Ò˝Ç◊ÏÇ◊Ì

«◊¡˛
˛aÄ`@Ÿ˛ ˚Ä$êÄ˝Ÿ˛ `
˛    ÄŸ˛
p†Ò«Óqíeº(1É«‹‡Q    ‡€˛â J,§êí⁄h    –‰Å(±I!¶¥ê€˛?ãå)D@¥¢p)O¬0¢àÇ'9€˛ê@îSi Ÿ/Ä≠xÅQJ“B¯A €˛`AcûI¿ë÷rH∞Û
étìÅg:¿€¸
˚¸¸⁄¸
ı¸⁄¸
Ĉ¸⁄¡¡¡¡¡¡¡¡¡¡¡¡¡˛
ĸ‡–˛˚@–˛
!˛Ä–˛
<Ú@;LÛ\Mû0—˛Jh@E¥II¶äH—˛"åp@Ö$äâƒ
Ä—˛!$ñÄFäLî≤
ò—˛gŸdp8rIg—»C§a—˝A˝
˛@œ
˝A˝
À˝
„IJ
ÄᲠ   <<:Œ˛Ä˛DŒ˛@!˛&ÑŒò@@@Ù 
4 
¡¡¡
–UÙ
√Œ¿ı    
–@ıŒ¿ı
√    
–@ı
√Œ¿ı    
–@ıŒ¿ı
‚˘ˇ¯Ï
‚E¸U@˘@ı
‚C¸3˛Ï‡D¸Ã¿˘¿ı
‚E˝
@    Ä˙@ı‡Dà˛¿¿˙¿ı
‚C" 
˛
`Ì
‚
E
@0˙@ı
‚C" 
˛
̇Dà˛¿˙¿ı
‚
EDD
@˛˙@ı‡Dà˛¿˛˙¿ı
‚C" 
˝Ì
‚E
@˛˙@ı
‚C>.
˝Ì‡Då˛¿˛˙¿ı
‚EL\
@˛˙@ı‡D®˛¿˛˙¿ı
‚C6h
˝Ì
‚EP
@˛˙@ı
‚C2∞
˝Ì‡Dò¿˛˙¿ı
‚EgTqÑ!@˛˙@ı‡D"0sP¿˛˙¿ı
‚Crx¶!˝Ì
‚E˝

@˛˙@ı
‚C˝
˝Ì‡D¸¿˛˙¿ı
‚E˝

@˛˙@ı‡D˝
Ä¿˛˙¿ı
‚C˝·˝Ì
‚E˛
Ò@˛˙@ı
‚C˛
°˝Ì‡D¸¿˛˙¿ı
‚E˝

@˛˙@ı‡D¸¿˛˙¿ı
‚C˝
˝Ì
‚E˝

@˛˙@ı
‚C˝
˝Ì‡D¸¿˛˙¿ı
Ρˇ˛Ä˝E˛
@˛˙@ıÈ˛ˇÄ˝D˛∞¿˛˙¿ı
βˇÄ˝C˛
·˝Ì
Î
Ä˝E˛
°@˛˙@ı
Θû
Ä˝C˝
˝ÌÍ0˜ü
IJ
ÄD¸¿˛˙¿ı 
Ï8Ô1ÅIJ
¿E˝

@˛˙@ı$˘ÛˇÏÔ ÅÅ˛ˇ
‡D¸¿˛
·Ä¿ı$
˚Û˜†˘Å˛
0C˝
˝
ÄÚ)
¸
ëÛ˜±˘Å˛
E˝

@˛
”Δn„`@ıò@@Ä@Ä
4 
t 
%
¸Ú"#    Å˛"
,C˝
˝≥/öó¿Û$˙ÚÚ    Å˛
D¸¿˛3-äî@¿ı(
¸ÚDFÉ    Å˛D
pE˝
!@˛
œΔz„¿@ı"˙ÚˇÏ√    Å˛ˇ
‡D˛Î0¿˛˙¿ı!
¸
@Û8„˘Ä˛
¿C˛
∂a˝Ì&
¸
¿Û00s˘Ä˛
ÄE˛‹Q@˛˙@ı
¸
ÄÚ
ĽC

˝Ì!˙
ÄÚ
ĽD
Ä¿˛˙¿ı"
¸
ÄÚ
Ä˝E¸U@˛˙@ı˙
ÄÚˇˇ˝Ä˝D¸Ã¿˛˙¿ı
¸
ÄÚ˛ˇ¿˝C¸3˝Ì$
¸
ÄÚ˛ˇ¿˝
@@@    8˙@ı
¸
ÄÈ
@Q )ú∏úû@Ì˙
ÄÈ
@{øflY{˘kz‡˙¿ı
¸
ÄÈ
@Qí )ö∏öö@˙@ı˙
ÄÒ
ò˚@¯˙¿ı
¸
ÄÒ
˚@¯Ì"
¸
ÄÒπĸ
@A
††<Ä˙@ı
¸
ÄÒõ¿¸
@eÕôµ≤MW†Ì˙
ÄÒ
ö˚
@_µz≠ØMJ˙¿ı"
¸
ÄÒô¿¸
@e≠Y≤™<ñ†˙@ı˙
ÄÈ@
˛˙¿ı
¸
ÄÈ@¯Ì
¸
ÄÈ
@p
(†˙@ı
¸
ÄÈ
@Es™≈≠…-Ì˙
ÄÈ
@{mÌ¢´∑˜Ä˙¿ı
¸
ÄÈ
@DÎÍ•≠I-˙@ı˙
ÄÈ@˝˝˙¿ı
¸
ÄÈ@˝˝Ì
¸
ÄÈ@¯˙@ı
¸
ÄÈ
@ (0    êÌ˙
ÄÈ
@_4;*j9Ωr˙¿ı
¸
ÄÈ
@7.Vˇ≠7´€◊˙@ı˙
ÄÈ
@74:∫j5πR˙¿ı
¸
ÄÈ@¯Ì
¸
ÄÈ@¯˙@ı
¸
ÄÈ
@˛Ä0ÄÌ˙
ÄÈ
@.mï“Õ»∫N¨˙¿ı
‚
@zU˝ØµΩzΩ¯˙@ı‡
@:Wì´≠®¥M®˙¿ı
¸Ë@˚Ì
¸Ë@¯˙@ı
¸Ë@¿¸Ì˙Ë@.âπ¿¸˙¿ı
¸Ë@{÷∂¿¸˙@ı˙Ë@:âu–¸˙¿ı
˙ˇ¸Ï@¯Ì˙Ï@¯˙@ı˙Ï@¯Ì˛˙ϯˇ˛˙¿ıÚˇÚ?¯ˇ˛˙@ı˛Å˛ˇÄ¯

Ä·¿ıÄ"" ˜

¿‘ň

¿Òê
¯@ıÄ"" ˜

`Ò    

βÄààĘ

0Ò    7πôÃœÄ˘¿ıÄDD@˜

Ò|Ωíe3ȯ@ı˛ÄààĘ

Ò    D°í%1    ¯¿ıÄ"" ˜

Ò<ùôŸ.ÈÄÏň

·@ıÄ"" ˜

‘˛ÄààĘ

Ä‚¿ıÄDD@˜
¿‚@ı˛ÄààĘ
`‚¿ıò@Ä¿Ä¿
t 
¥ 
Ä"" ˜
0’ň
0‚@ıÄ"" ˜
’˛Äüàèį
‚¿ıÄGD^˜
‚@ı˛Äèàæ˜
ˇˇ‚¿ıÄ'¢<ı’Åë|ı‚@ıÄ+¢¸ı’˛Äãàòı‚¿ıÄ_≈¯ı‚@ı˛Äõã∏ı‚¿ıÄ3¢8ı’Åó0ı‚@ıÄ3Æpı’˛Ä©àı‚¿ıÄe‹p˛˘Ù˘ˇ˛˘@ı˛Ä©¯‡ıÙ˘˘¿ıÄcÚ‡ıÙ˘
ÄÌ$ÅQÒ‡p˛˛Ù˘
Ä˙@ı#ÄA¿‡ê    ˛˛
0ı˚" ¿Ì$˛Ä¡¡¿
@˛˛
ı˘
`˙¿ı'ġŇÅ $˛˛
ı˚D@0˙@ı'˛ÉÒ¯
¿8˛˛
ı
ĸÄ˙¿ıĘ
˛
ı˘
ÌĘ
˛
ı˘
˙@ıĘ
h˛
ı˚ ˇÌ ˛Ä˜
¯˛
ı
˚

Ä˚¿ı$Ę
˛
ı@
Ä@
Ä˚@ı"˛Ä˜8˝
ıÄ
¿Ä
Ä˚¿ıį
0x˝
ı
¿¸

ÄÓ į0¸
ı

˚

Ä˚@ıįp¸
ı
Å˛ 
ÄÓ!˛Ä˙¿¿¸
ı
˚

Ä˚¿ı$Ģ
ܸ
ı@
ü˛@
Ä˚@ı"˛Ä¯¸
ıÄé˛Ä
Ä˚¿ıÄ˙¸¸
ıáÄ˚

ÄÓ$Ä˚
î ˛
ı
É˙

Ä˚@ı#Ä˚
(`˛
ıÄ˝ 
ÄÓ#˛Ä˚l˛
ı
˙¿
Ä˚¿ı'Ä˚»IJ
ı\`˝@¯
Ä˚@ı"˛Ä˜
IJ
ıÄp˝Ä?ÿ
Ä˚¿ıÄÚ
ı`¸ˆ€
ÄÓÄÚ
ı ˛
ÚœÅÄ˚@ıÄÚ
ı‡˛#Ë¡ÄÓ˛ÄÚ
ı‡z˛x·Ä˚¿ı"Äı
ı@p˛G¿ÅÄ˚@ı!˛Äı
ÄıÄp˛ܯ¡Ä˚¿ıį˛¿ı˙¸¡ÄÓ!į˛‡ı˙Ôd·Ä˚@ıįı˚!ŒÙ
ÄÓ!˛Ä¯Xı˚
é‹
Ä˚¿ı#įÄHı
@¸@¿
Ä˚@ı#˛Ä¯‡jıÄ8˝Ä@
Ä˚¿ı!į
0*ı8
˛@
ÄÓ+Ĉ
ò/˛˛ˇ¿˝8
Ä@
Ä˚@ı'Ĉ˛å-˛˛ˇ¿˝`
¿ @
ÄÓ.˛Ä˚˝cÑ-˛˛ˇ¿˝‡

‡@
Ä˚¿ı0Ä˚˛ÒÜ!˛
¿˝@‡
¿∞@@
Ä˚@ı/˛Ä˚$˛¬#˛ˇœ
¿˝Ä
‡êÄ@
Ä˚¿ı-Ä˚uÑB" ˇflÅ¿ ˛˛∞‹`
ÄÓ1Ä˚&ö?¸c¯`ˇπ¡¿`˛ÿ\ 
Ä˚@ı-Ä˚$úpÅF‡ˇ∞¡¿‡˛7Ã\ 0
ÄÓ3˛Ä˚%I x·Ã
øˇˇ∞˝¡øˇˇ¸‹ΔT0
Å¿ä˛¿ıò@¿
¿

¥ 
Ù 
3Ä˚IxπÄ?ÉDEˇπ˝√˝D@1¸bƒ@
Å à˛@ı.˛ÄˆÃÄ|Êàâ¯çΔ˛àåÄs"ÑÄ
Å2Ínf¿ı,Ĉ
Ü<
˚Δ˛«˜è‡˛
Å“ö˘ÙÚ0ʡ√É√˛é
‚ò0˛
ÅöŸÑ@ı.į#`

É
øˇ√¡øˇˇ¸ªÄ¯ 
ÅÍitÚ-˛Ä¯p
Ä√‡„˝¿‡˛Ì
‡¿
Ä˚¿ı.įp?ÉÄÄ~C`8s˝¿`˛@1Δ@¯
Ä˚@ı,˛Ä¯@3>É√c˛¯
¿˝É
ˇ√IJ
Ä˚¿ı)į@`Ç
£˛¯
¿˝

r>
ÄÓ.Ģ
¿¿ „˛
¿˝·¡Ùÿ?
Ä˚@ı*Ģ
¿Ä ˛3˛˛ˇ¿˝oqèû 
ÄÓ+˛Ä˜ ˛˛ˇ¿˝ÿà‡x
Ä˚¿ı-įò0
ɲ˛ˇ¿˝N
 Ê@˙Ó
Ä˚@ı$˛Ä¯9¯–ÉıĬ0;ÄflÊ
Ä˚¿ı!į1˘ò[√ıc∂è‡
ÄÓ%įˇl√ıw>x¸
¿
Ä˚@ı(įˇ»t˛
¿
¸F»| 
`
ÄÓ,˛Ä˙    ˇÃ‹˛ 
˚`ˇ»§
 
Ä˚¿ı.Ä˙    ˇƒå˛ù”¸@‡ˇÏ‡@
0
Ä˚@ı.˛Ä˙    ˇÑ˛”4Ä˝Å·ˇƒ Ä

Ä˚¿ı,ĸ<nñˇ˛sS4¸¡ˇƒ

ÄÓ1ĸìˇ˛
±›3Ä˝ˇÑ0

Ä˚@ı)ĸ#?ˇÑ¸˚ˇƒ  
ÄÓ,˛Ä¸%<*
ˇˇÑ¸˚ˇƒ 
Ä˚¿ı-ĸX‘$ˇˇ‰¸˚@ˇÙ @
Ä˚@ı(˛Ä¸@˛ˇˇ¸ıġˇ˛ Ä
Ä˚¿ı$ĸ@˛ˇˇ˛ı
˛ˇ ˝

ÄÓ(ĸ‡˛˛ˇı
˛ˇ ˝

Ä˚@ı!į˛ˇı
˛ˇ  
ÄÓ#˛Ä¯?˛ˇıˇˇ˛0˝

Ä˚¿ı#į˝ˇıGˇˇ˛@
Ä˚@ı#˛Ä¯˛ˇ˛ı
è˛ˇÄ
Ä˚¿ıį˛ˇ˛ı
˛ˇê˝

ÄÓ$Ģ˝ˇàı
?˛ˇê˝

Ä˚@ı!Ģ˝ˇÃı
?˛ˇò 
ÄÓ$˛Ä˘˝ˇƒı
?˛ˇà>
Ä˚¿ı%Ģ˝ˇƒı
G˛ˇà@|
Ä˚@ı$˛Ä˘˝ˇƒıÉ?ˇIJÅÄ˚¿ı!Ģ˝ˇΔı?Δˇ
ÄÓ#į˝ˇÇı?ܡ˝
Ä˚@ı!įs˛ˇı?Ü!ˇ˛
ÄÓ$˛Ä¯c¯áıÜ
ˇˇ
Ä˚¿ı%įc¯
á
ÄıCˇÜCˇ˜AÄ˚@ı$˛Ä¯c¯
ÄıÉ~ÜÄÈ
Ä˚¿ıįg¯
ı˙~`
ÄÓ įg∏
ı˙m
Ä˚@ıį¯
ı˚" *
ÄÓ˛Ä¯∞0ı¯

Ä˚¿ıÄÚÙ¯

Ä˚@ı˛ÄÚÙ¯

Ä˚¿ıĈˇÄÙ˜ˇÄÓĈˇÄÙ˜ˇÄ˚@ıĈˇÄ’˛ÄÚ‚¿ıÄÚÛÄ
@¯@ı˛ÄÚÛ    Ä@¯¿ıÄÚÛ        ªå¡r–˚ÄÌ'IJ
 D˝Û    éSʃö®Wø¿˙@ı$IJ
˚€˚ˇÌˇ¿˛Û    ∂S§ÑÍ®T#@Ì'˛Ä˛˚€ÒøÕˇ¿˛Û    ûL√G:®sùÄ˙¿ıÄ˚@¿˛Ôı@ı˛ÄÚÔı¿ıÄ˝Ω@Ñ
˝ÔËÄ˝4∑oˇœfiP˝‚@ıò@

@

@
Ù 4 
Ä˝5ßoˇœfi–˝’˛Ä˚¿˚‚¿ıÄÚ‚@ı˛Ä
†ää†
˛‚¿ıÄfløflº˛Îfiˇ?∏’Äfløflº˛Îfiˇ?∏‚@ıÄÚ’˛ÄÚ‚¿ıÄFÅ
r˛‚@ı˛Ä
˛ˇ{ÔfiÔüøÁ/ˇÄ‚¿ıÄ
˛ˇ{ÔfiÔóø«ˇÄ’Ę@˝‚@ıÄÚ’˛Ä˛#îCâ˝‚¿ıIJ:˝Î€}Àœø¯˛‚@ı˛Ä˛;˝Ô⁄}flÀø¯˛‚¿ıÄÚ’ÄÚÙ˘ˇ˛˘@ıÄ˝‡
Ä`˝Ù˘Ï!˛Ä˝vˇoΩˇüÔ˝Ù˘
Ä˙¿ı"Ä˝vˇoΩˇüÔ˝Ù˘
¿˙@ı˛Ä˜˝Ù˘
`˙¿ıÄÚÙ˘
0Ì#Ä˚@˚Ù
$Ä ˙@ıÄ˚π¿˚Ù
=h°    7(Ì"˛Ä˚ª¿˚Ù
'‹Ûü™º˙¿ı!Ä˚
˘Ù
%H°â´(˙@ı˛ÄÚÙ˝˛ˇÄ˚¿ıÄÚÙ˝˝

ÄÓÄÚÙ¯

Ä˚@ıÄÚÙ
˘

ÄÓ˛ÄÚÙ:ò˙

Ä˚¿ıÄÚÙ;–˙

Ä˚@ı˛ÄÚÙ4î˙

Ä˚¿ıÄÚÙ
˘

ÄÓÄÚÙ
˙UT
Ä˚@ıˇÙ
˙30
ÄÓ˛ÒˇÙ
˘Ã

Ä˚¿ı
‚
˙
Ä˚@ı‡ĸ
Ä˚¿ıÄÚÙ" ¸
ÄÓ¿ÚÙ¸
Ä˚@ıÚˇ¸Ù" ¸
ÄÓˆÏĸ
Ä˚¿ı
¯Ï@¸
Ä˚@ıˆÏĸ
Ä˚¿ı
¯Ï.,¸
ÄÓ
¯Ï¸
Ä˚@ı
¯Ï&0¸
ÄÓ˛
Á
–¸
Ä˚¿ıÄ
ÁP¸
Ä˚@ı˛å€Ä˛~Ï
ê¸
Ä˚¿ı&SÒ˝BÏ+" ˛
ÄÓ!¶Q˝RÏ1F"
Ä˚@ıNÒIJbÏÒòD
ÄÓˆBı˛ˇ¿˝
¸»
Ä˚¿ı"
¯Fı˛ˇ¿˝
¸∏
Ä˚@ı ˆJı˛ˇ¿˝
˝    ∞
Ä˚¿ı!˙Bı˛¿˝
˝Ä
ÄÓ%˙Rıˇœ
¿˝
˝6
Ä˚@ı$∂¿¸bıˇœ¿˝
˛
ÄÓ)˛ØĸBˆ0ˇôÅ¿˛ ˛0
Ä˚¿ı*®Ä¸gˆ8ˇ∞¿¿˛0˛,`
Ä˚@ı*˛Gĸ)ˆˇÏˇ∞¡¡˛ˇ¯¸`
Å·Ä¿ıò@
@
Ä
@
Ä4 t 
%@˚ ˆˇ∞¸¡˛˙
Ç
ÄÚ+Ä˚1ˆ¯ç¡˛˝
Å”Δn„`@ı&
¯ˆ"#˚¡˛"#˝
Ä
Ä≥/öó¿Û%ˆˆÉ¡˛˝¿
Ç3-äî@¿ı)
¯
ƒ˜DF√¡˛DL˝‡
ÅœΔz„¿@ı!ı˜ˇÏ„¡˛ˇ¯¸
Ä˚¿ı
Ï88s¸¿˛0˛p
ÄÓ"
Ï0¯
¿˛ ˛\˝p
Ä˚@ı
Î¯¿˝
˛∏˘‹
ÄÓÈ
¿˝
˝∂
Ä˚¿ı
Ρˇ˛¿˝
¸å
Ä˚@ıÈ˛ˇÄ˝
˝›á
Ä˚¿ı
βˇ¿˝
˝˛ü
ÄÓ
‚
˝0Êøî
Ä˚@ı
‚
˝Ú&ê
ÄÓ‡
˝˛/
Ä˚¿ı
Í˙
˛ˇ=
Ä˚@ıË˙æ˝4
Ä˚¿ı
Í[`¸ 
˝`
ÄÓ
ÍW¿¸ˇ@
Ä˚@ı
ÍT@¸ˇ¿
ÄÓË#¿¸
˝ˇ‡
Ä˚¿ı
È ˚
˝ˇ 
Ä˚@ıÁ@˚
˝?ˇ†
Ä˚¿ı
‚
˝ˇ†
ÄÓ
‚
˝ˇ∞
Ä˚@ı
‚
˝áê
ÄÓ‡
˝çò
Ä˚¿ı
‚
˝âÄ
Ä˚@ı‡˝ˇ
Ä˚¿ı
‚˝ˇ
ÄÓ
‚
˙
Ä˚@ı
‚
˙
ÄÓ‡Ôˇˇ¿
Ä˚¿ı
‚
˙
Ä˚@ı‡=ˇ˛
Ä˚¿ı
‚
˙
ÄÓ
‚ˇ˝˛
Ä˚@ı
‚
˙
ÄÓ‡?Ô˛ˇˇ
Ä˚¿ı
‚
˙
Ä˚@ı‡ˇˇÔ‡
Ä˚¿ı
‚
˙
ÄÓ
‚
˙
Ä˚@ı
‚ˇˇÄ
ÄÓ‡
˙
Ä˚¿ı
‚
˛?˛
Ä˚@ı‡
˘Ã

Ä˚¿ı
‚
˙30
ÄÓ
‚
˙UT
Ä˚@ı
‚˜ˇÄÓ‡˜ˇÄ˚¿ı    
–@ıŒ¿ı
√
flx
ˆ@ı
flÄÈ›w4Âá[0¯¿ı
fl)™ó√W†¯@ı›é™ñT ¯¿ı
fls™Â√#†Î
›Ä ˜@ı
›Ä@Í
€Äı¿ıò@
Ä
¿
Ä
¿t ¥ 
    
–@ıŒ¿ı
√    
–@ı
√Œ¿ı    
–@ıŒ¿ı
√    
–@ı
√    
–ÿı    
–U@ı¡¡¡¡¡¡¡¡¡¡¡¡¡¡˛û
¿p ˛âÄ$Ä ˛ÅE¿ ˛ÅÑ@ ˛ÅÑ  ˛!2à  ˛¢ê@ ˛?|‡cÄ ¡¡¡¡˛    ò
Ä8
0˙√˘ÿaĉ˛    Ä@@˙@˘@
‚˛˝@‡ ˝ ÄÄ˙Ä„'˛!⁄–Ä@ ß÷òèpk¬É«;t#ºs¬üá
yúÒ¿Ê'˛!6äc@Ä    H§SkE ëMâEò‘íâM2ö4”"R@Ê&˛ $îCÅÑP¿¢Kä!ëÑ Ö‚#
ë%DíB°Â'˛!K%Ñ@ ÖÒM,úA:◊â&ä!    %◊Õå_$ƒ¥ÄÊ&˛ 8w>ÉáÅ¿3¬Œ1Ùìí@‘ãr ÓX‰ãy-Á9'½
ÄÌ@˛"‡˝
ÄÌ@˛"‡˝χ˛‡¡˛ÉaÄ`¿À˛
Å˛
1ÄÀ˛2ÄÀ˛

yúRçx—≈†œ˛
4”"PTí)&ö¿œ˛
DíB†Y"R$úÄœ˛    fl$ƒ∞ë'Zs!Œ˛    ?-Á9 ◊ëߌˆ
ÄŒˆ
ÄŒˆÕ¡$˛¿0`0`¿˝`Ë˝`Âò@
¿
Ú
¿
Ú¥ Ê 
˛@ `˝
@˝˝

fi#˛Ä@† IJ
¸
‰'˛!Öí    „±D£Losé∞˜çy‰f7ôœ¥ÙÕ<l7õûÊ'˛!öí§Êö$í≈$R–Rk$î…I2%[[E“I4JÊ'˛!¥BHúH†ä(Hê¢r"Eêâ$*RRJ(†â(TÊ'˛!! ÿiõ‡$IÁ+H• ¥Ñ'I-3ûLKh§‰“≠&ûHñÊ'˛!1ê:NÂú5Δô“G9"$t≤…Ãjsíá$§üIÿjw$Ê
Ò˝Ç◊ÏÇ◊Ì

«◊¡˛
˛aÄ`@Ÿ˛ ˚Ä$êÄ˝Ÿ˛ `
˛    ÄŸ˛
p†Ò«Óqíeº(1É«‹‡Q    ‡€˛â J,§êí⁄h    –‰Å(±I!¶¥ê€˛?ãå)D@¥¢p)O¬0¢àÇ'9€˛ê@îSi Ÿ/Ä≠xÅQJ“B¯A €˛`AcûI¿ë÷rH∞Û
étìÅg:¿€¸
˚¸¸⁄¸
ı¸⁄¸
Ĉ¸⁄¡¡¡¡¡¡¡¡¡¡¡¡¡˛
ĸ‡–˛˚@–˛
!˛Ä–˛
<Ú@;LÛ\Mû0—˛Jh@E¥II¶äH—˛"åp@Ö$äâƒ
Ä—˛!$ñÄFäLî≤
ò—˛gŸdp8rIg—»C§a—˝A˝
˛@œ
˝A˝
À˝
„IJ
ÄᲠ   <<:Œ˛Ä˛DŒ˛@!˛&ÑŒò@@@Ê & ˛@!    Áç–8
› —˛@!4¢öP$

&i —˛ÄB9EF
$p†—˛DAe§†D
xÄ¿—˛>¯:I? ¯@·®pÄ—ÚÄ—Û
–Û–¡˛
¸
``Õ˛
0¸
êêÕ˛
 Ä Õ˛
&èÙo;@¿Õ˛
"íòíEÄ  Õ˛EëÖ @Õ˛ie!<ä êÕ˛<Oπ ‘r≈‡Õ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä@Ä& f ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿Ä¿f ¶ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿
¿
¶ Ê ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@

@Ê & ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
@
Ä& f ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
Ä
¿f ¶ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
¿
Ú¶ ÿ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@@Ê & 
˛@!    Áç–8
› —˛@!4¢öP$

&i —˛ÄB9EF
$p†—˛DAe§†D
xÄ¿—˛>¯:I? ¯@·®pÄ—ÚÄ—Û
–Û–¡˛
¸
``Õ˛
0¸
êêÕ˛
 Ä Õ˛
&èÙo;@¿Õ˛
"íòíEÄ  Õ˛EëÖ @Õ˛ie!<ä êÕ˛<Oπ ‘r≈‡Õ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä@Ä& f 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿Ä¿f ¶ 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿
¿
¶ Ê 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@

@Ê & 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
@
Ä& f 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
Ä
¿f ¶ 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
¿
Ú¶ ÿ 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇN≤@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡ä5Introduction to Publishers, Subscribers, and Editions

, (‡    2-9
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähê(eä
Y@Ä°dONLNd
\êh)Vou should distinguish each selected publisher and subscriber within a document with a °dONLNdWiäuò(räborB °dONLNdZiôuß)der\¿°dONLNd]ißu
). Display a publisher bor'`°dONLNdvi
u
>)m
der as thr °dONLNdÄi
>u
±)*ee pixels wide with 50 per3 °dONLNdöi
±u    )scent gray lines, and °dONLNdØväÇÛ(ädisplay a subscriber bor¿°dONLNd«vÙÇ
)j
der as thrÄ°dONLNd—v
Ç
ë)*ee pixels wide with 75 per Ä°dONLNdÎv
ëÇ
÷)scent gray lines. …`°dONLNd¸v
’Ç
‹)D
A°dONLNd˝v
݂
„) rI°dONLNdˇv
„Ç)ectangle of °dONLNd
Éäè
F(åä+one white pixel should separate the data fr›@°dONLNd
6É
Fè
v)º
om the borΔ@°dONLNd
@É
vè
±)0der itself. Bor‚ °dONLNd
OÉ
±è);ders should be drawn °dONLNd
dêäú¶(ôäoutsidea¿°dONLNd
kêßú
”)F the contents of publishers and subscribers so that data is not obscur”Ä°dONLNd
±ê
”ú
Ù(ô
”ed. See °dONLNd
∫ùä©¢(¶äFigurR¿°dONLNd
øù¢©∂)e 2-6@°dONLNd
ƒù∂©
2) for an illustration of the borä`°dONLNd
„ù
3©
£)}ders as they appear onscr¬Ä°dONLNd
¸ù
£©
¡)peen. Se0Ä°dONLNdù
©
…)e z °dONLNdù
…©
)“Displaying °dONLNd™ä∂

(≥äPublisher and Subscriber Bor¿°dONLNd-™
∂
K)Åders” on page HÄ°dONLNd;™
K∂
])@2-50ú`°dONLNd?™
]∂
b) fp@°dONLNdA™
c∂
˚)"or detailed information on how to °dONLNdc∑ä√À(¿äimplement bor‰°dONLNdp∑À√
)Aders for specifi# °dONLNdÄ∑
√
L)Bc applications.°dONLNdê…ä’¢(“äFigurR¿°dONLNdï…¢’∂)e 2-6@°dONLNdö…∂’
ˆ)E shows a document containing a publisher and a document containing a °dONLNdfl÷ä‚∑(flä
subscriberZÄ°dONLNdÈ÷∑‚·)-
, with borÔ¿°dONLNdÛ÷·‚
J)*ders displayed for each..°dONLNdËäÙö(ÒäBorR`°dONLNdËöÙ
Ø)>ders for publishers and subscribers should behave like the bor$¿°dONLNdMË
ØÙ
œ(Ò
Øders of ,
Courier$¿°dONLNdUË
œÙ
Û) 'PICT'$¿°dONLNd[Ë
ÛÙ
ı)$
 .
°dONLNd\ıä

Î(˛ägraphics within a worâ@°dONLNdqıÎ

˛)ad-pr¿°dONLNduı˛


W)ocessing document. >†°dONLNdàı
X


^)Z
Yˇ °dONLNdâı
]


˝)$our application should display a bor±@°dONLNd≠ı
˛

)°der °dONLNd±
ä

U(
ä.whenever the user clicks within the content ar–¿°dONLNdfl

U

·)À!ea of a publisher or a subscriber“†°dONLNd

·

Ê)å. •°dONLNd

Ê

Ï)
YeÄ°dONLNd

Ï

˝)our °dONLNd
ä

(
äapplication should hide the bor†°dONLNd&



ı)ã3der whenever the user clicks outside the content arj@°dONLNdY

ı
)‡ea. Se=@°dONLNd_

)e °dONLNda
ä
(
B(
%ä(“Displaying Publisher and Subscriber Bor6‡°dONLNdâ

C
(
É)πders” on page m†°dONLNdó

É
(
ï)@2-50¡Ä°dONLNdõ

ï
(
ö) fï`°dONLNdù

õ
()or detailed information on °dONLNd∏
)ä
5Ï(
2ähow to implement bor9¿°dONLNdÃ
)Ì
5
.)cders for specifix‡°dONLNd‹
)
.
5
m)Ac applications.


WH
h4
XH
h"
XH]

ˇ·ˇ‚7^
    °dONLNdÌ
Mä
X¥(
Uä
Figure 2-6°dONLNd¯
MÃ
X
P)B Publisher and subscriber borders


gàùòÄ.
¿
bHH



M2@

ˇˇˇˇˇˇ

¿
b
ko+
—
˛„ˇ˛ˆ
˛„ˆ
˛„ˆ
˛„ˆ˛Ô˛¸ˇÒ˝ˇfl˝˚ˆ˛˚Ä¿
Ä˙Dˆ"˛Ë¸ˇ¿
Ä˝ˇ–E˚ˆ˛˚Ãœå«√Δœè˚Dˆ!˛Ë¸ˇ
˝Ã
ôôúfgôú˝ˇ–E˚ˆ˛˚åÃÃŒôòffôò˚Dˆ"˛Ë¸ˇÃëüòffüò˝ˇfl≈˚ˆ˛˚ÃÃ√ôòffò˚ˆ"˛Ë¸ˇÃÃ…ôòòffòò˝ˇ–˚ˆ˛˚œå«è√Δè˚ˆ˛Ô˛¸ˇÒ˝ˇfl˝˚ˆ
˛„ˆ
˛„ˆ
˛„ˆ˛‚ˇˆ˛Â
ˆ˛Â
ˆ˛Â
ˆ˛Â
Ɉ˛Â
Cˆ˛Â
#ˆ˛Â
 ˆ˛Â
x{ˆ˛Â
Cˆ˛Â
Cˆ˛Â
Cˆ˛Â
√ˆ˛Â
ˆ˛Ô
ˇˇ¿˚
ˆ˛Ômġ¸
ˇˇˆ˛Ô˛ˇMˇ¸˛
ˇˇˆ˛Ô~›∑m€e‘˛
Ĉ˛ˇˇ˝ˇflt˛
Ĉ˛›€wmŸ6L˛
Ĉ˛ˇˇ›ˇwÌ‹˛
Ĉ˛Ò
›ô≥wdÕô4˛
Ĉ˛
˘U@˝˛ˇ››ªwt˛
Ĉ˛˘™†˝ô33wfL‘˛
Ĉ˛
˘U@˝¸&fL›ŸÙ˛
Ĉ ˛Ä˙†˛
áˇÄ˝
3T˛
Ĉ$˛
˛~˝@˛    
ˇˇ¯gÙ˛
Ĉ$˛ÄÛIJ†˛
˝ˇÕt˛
Ĉ$˛
˛@˛

˝
ˇüÙ˛
Ĉ$˛Ä<ˇÄ†˛
ˇ¸˝
7Ù˛
Ĉ%˛
 8‡@˛

˛ˇÄ
|˛
Ĉ%˛Ä`<†˛    

ġ¿
⁄˲
ˇˇˆ%˛
¿œ«Ä@˛    

¸ˇ◊¯˛
ˆ%˛Ä
√¯‡†˛    

Á˛–˛
DGˆ%˛
?ˇáÛè˛@˛    
?ˇˇÒ∞˛
ˆ$˛á>Ïs†˛

˝Ò`˛
DGˆ#˛
Ô¡ˇ@˛

¸
¿˛
ˆ#˛àû¯†˛

ĸ
IJ
DGˆ#˛
?˛Ä@˝
ˇ‡˝
IJ
ˆ#˛∏Ôˇ„ˇ;Ć˝+˛

˝
DGˆ&˛
1áˇ¯Ä#Ä@˝+Uøˇ¸
˝
¯
?ˇ#˛∏ᡡc†˝+U≠Vfl¸
ƒ˝
DGˆ#˛
ˇˇ¡‹√@˝/ı≠V◊wˇÃ˝
ˆ#˛é˜ˇ¯~ÉĆ˝?ˇVfltuX˝
DGˆ&˛
?ˇ˛ÁÄ@˝
ˇˇ◊˝_ıP˝
¯
?˛ ˛ġˇÁˇÄ†˙ˇÄ_’p˝
DGˆ"˛
˛{ˇ˝ª@˘ˇˇı`˝
¯
?˛˛ġ˝¸†˜
¿˝
DGˆ˛
˛flı<@Ò
¯
?˛˛Ä
ˇ˜|†Ò
DGˆ˛
˝?˛¸@Ò
¯
?˛˛IJ
ˇ¯†Ò
DGˆ˛
¸¯¸@Ò
¯
?˛˛ĸd†Ò
DGˆ˛
˚(@Ò
¯
?˛˛ĸ,†Ò
DGˆ˛
˚4@Ò
ˆ˛ĸ<†Ò
DGˆ˛
˘@Ò
¯
?ˇ˛Ä˙†Ò
DGˆ˛
˘U@˚
‡˘
ˆ˛˘™†˚
p>˘
DGˆ˛
˘U@¸
«€ˇ˙
ˆ˛6¡¯˚
DGˆ˛~ˇ∑fl¸¸
ˆ˛0€∂˝4‡˝
DGˆ˛Áˆˇ∑ˇÌ∞˝
ˆ˛Ò
å›≤m∂€0˝
DGˆ˛Ò?˜Ôˇ˝˛˝
ˆ˛ÒdÕªm∑Hê˝
DGˆ˛ÒyˇøÔˇ}˚ê˝
ˆ˛Ò√fdõ-”n˝
DGˆ˛Úè›fl˛ˇÿ0˝
ˆ˛Ú;7vÀ¥€0˝
DGˆ˛Ú8Ó˝flæˇˆaê˝
ˆ˛Úaôì6Ì∂]√p˝
DGˆ˛Û    
œˇ˛ˇø˝˜–˝
ˆ˛Û        àôílóDp˝
DGˆ˛Û    {˜˚˝‹–˝
ˆ˛Û    Õ€n€0Kp˝
DGˆ˛Û    üv€æ·ˇ–˝
ˆ˛Û¸˛fl∂˘Ékp˝
DGˆ˛Ù

á¯ˇ∑ˇ˝
ˆ˛Ù

¯¸`˝
DGˆ˛Ù

Ävˆ¿˝
ˆ˛Ù

ˇ‡ˇpflˇÄ˝
DGˆ˛Ù    

˛
¡∂Ú¸
ˆ˛Ù    
?˛„áˇÓ¸
DGˆ˛Ù    
?¿>ñÿ¸
ˆ˛Ù    
ˇ¿?¸
DGˆ˛Ù
˛¸$÷@¸
ˆ˛Ù
˝ˇ˙ˇ˝¿¸
DGˆ˛Ù
˝
ˇÜ”˚
ˆ˛Ù

˝˛˚
DGˆ˛Ù

á˝ÿ˚
ˆ˛Ûá˝˚
DGˆ˛Û«˝¿˚
ˆ˛Û
IJÄ˚
DGˆ˛Ú¯˛
˙
ˆ˛Ú˙
ˇˇˆ˛Ò˙
ˆ˛Ò¸0˙
ˆ˛¿‡˙
√ˆ˛ÔÉÄ˙
Cˆ˛Óˇ˘
Cˆ˛Ó˘
Cˆ˛Â
x{ˆ˛Â
 ˆ˛Â
#ˆ˛Â
Cˆ˛Â
Ɉ˛Â
ˆ˛Â
ˆ˛Â
ˆ˛‚ˇˆ˛?ˇ‰ÍDÄ
ˆ˛ 01ÍÄň˛`0$ÍDÄ¡?Ɉ˛†01ÍÄ° Ɉ˛>0$ÍDèë ˚ˆ˛01Íà     ãˆ˛0$ÍDà ãˆ˛01Íà ãˆ˛0$ÍDà    ?ãˆ˛>01Íèëˆ˛†0$ÍDÄ°ˆ˛`01ÍÄ¡ˆ˛ 0$ÍDÄÅ˚ˆ˛?ˇÒÍÄ
ˆ˛‚ˇˆ˛‚ˇˆ”””””””˛‚ˇˆ˛„

ʲ„

ʲ„

ʲ˜ˇ˝ˇÄÚ?˝ˇÔ˛˝Ä˜˛
˚p
ÄÄ`˙"
Ę$˛Ù
˝ˇÄ»
Ä
Ä`?˝ˇË"˝Ä˜!˛
˚¡ô·ΔŸÒ∞|<l¯Ò∞¸"
Ę$˛Ù
˝ˇÄ·ôôì'ôô¿ffqôô¿?˝ˇË"˝Ä˜!˛
˚qôô√ôôÄffaôôĸ"
Ę$˛Ù
˝ˇÄ9ôò„ô˘Äffaô˘Ä?˝ˇÔ‚˝Ä˜!˛
˚ôòsôÅÄffaôÅĸ
Ę$˛Ù
˝ˇÄ˛ô3&ôâÄffaôâÄ?˝ˇË˝Ä˜!˛
˚p˘·ΔÒÄ|<`¯Òĸ
ʲ˜ˇ˝ˇÄÚ?˝ˇÔ˛˝Ä˜˛„

ʲ„

ʲ„

Ę
˛‚ˇÄ˜˛‰Ä
Ę˛‰Ä
Ę˛‰ÅÅĘ˛‰ÇAĘ˛‰Ñ!Ę˛‰àĘ˛‰ê    Ę˛‰º=Ę˛‰Ñ!Ę˛‰Ñ!Ę˛‰Ñ!Ę˛‰á·Ä˜˛‰Ä
Ę˛‰Ä
Ę˛‰ˇˇÄ˜˛‰ˇˇÄ˘
?ˇ˛‰¿Ģ
$˛‰¿Ģ
˛‰¿Ģ
$˛‰¿Ģ
˛‰¿Ģ
$|&˛0é8Ä
Ä˝ ¸¿Ģ
@&˛QDÄ
IJ˝ ¸¿Ģ
$@)˛ Á@Ƀ¡Ã∑f„9ñpeò8À:    ñ`¿Ģ
@)˛ îîÉê8ÑÖ% íƒíêíXÄ$$,IPXê¿Ģ
$@)˛ >îóÄPÑ%‡ûÑíìíP`t<$ËIQ–¿Ģ
|)˛ "îîQDÑ•%êÑíîíPî %(H¢PÄ¿Ģ
$)˛ "Áé8Ƀ¿LÑíìâê‡t$Ë8°–`¿Ģ
˛˛ÑË¿Ģ
$˛˛ÑË¿Ģ
˛‰ˇˇÄ˘
?ˇ˛‰àâĢ
?ˇ˛‰¢#Ę$˛ 
 D 
«@Ü@¸àâĘ$˛˛
 D (¢@Ç@¸¢#Ę&˛9ëf1√∏ŒÓc89ÅÇ Aå‚`qñ`˛àâĘ&˛JJ)J
$$D§@A»BBíêJXê˛¢#Ę&˛K (yÅ$‰Dt$A¿(BíK–˛àâĘ&˛J)@A%$Dî§BB(¢BRíÄJIJ¢#Ę)˛9Ñ&3ħ‚"s$    Å¡«Aé‚bIê`˛àâĢ
?ˇ˛‰¢#Ę˛‰àâĘ˛‰¢#ʲ‰àâĢ
?ˇ˛‰¢#Ę%˛˝
 ¸
 @
 ˝àâĢ
?ˇ˛˝
 ¸
 @˛˙¢#Ę)˛vI‹8¡ΔΔYÉ∏ŒÇ`Ê[≥qúÀ8n˛àâĢ
?ˇ&˛IJ%!)    )bA$)TêIbIHI,@)
˛¢#Ę)˛IIà%·)    )C¡$ÈTêOBII…(0)˛àâĢ
?ˇ&˛IHH%
)    )B
%)(êHBIJI()    ˛¢#Ę)˛I;Ñ8¡&    &AħÈ(`&BIIƒ»p)˛àâĢ
?ˇ˛‰¢#ʲ‰àâĢ
?ˇ˛‰¢#Ę˛‰àâĘ˛‰¢#ʲ8„à@ÏàâĢ
?ˇ˛EHÍ¢#ʲA3å‹Ïàâʲ9àJBRÏ¢#ʲHBNRÏàâʲEHJRRÏ¢#ʲ    8„à2NR@ÌàâĘ˛‰¢#ʲˆ;˙ªÄ¯àâʲˆ.˙Óį¢#ʲˆ;˙ªÄ¯àâʲˆ(˚
į¢#ʲˆ8˚
įàâʲˆ(‡į¢#ʲˆ8
ˇ8įàâʲˆ(
aœį¢#ʲˆ8¿¯įàâʲˆ(éį¢#ʲˆ8Û¿įàâʲˆ(|¸xį¢#ʲˆ8
Ô?éįàâʲˆ(ˇ¯8ˇ‚į¢#ʲˆ8s‡~¿`3įàâʲˆ(fi¸¿
“į¢#ʲˆ8âÔˇÄsįàâʲˆ)ɡ·ˇ˙į¢#ʲˆ;顲?ªÄ¯àâʲˆ+ˇÅÿ:į¢#ʲˆ;àˇ3įàâʲˆ)∞?ˇ¸Ã2į¢#ʲˆ8‡ˇáË;įàâʲˆ(ˇˇ‡˛zį¢#ʲˆ8ˇˇ˛˚įàâʲˆ(øˇ€≤į¢#ʲˆ8
ˇˇfl√įàâʲˆ(˛=ˇS¬Ä¯¢#ʲˆ8˛ˇw√įàâʲˆ(˛ˇÔ¬Ä¯¢#ʲˆ8˝ˇÉįàâʲˆ(˝è¬Ä¯¢#ʲˆ8¸Cįàâʲˆ(¸ÇįˇˇÄ˜˛ˆ8¸√įÄ
ʲˆ(¸BįÄ
ʲˆ8¸√įá·Ä˜˛ˆ(˚
įÑ!ʲˆ;˙ªÄ¯Ñ!ʲˆ.˙ÓįÑ!ʲˆ;˙ªÄ¯º=Ę˛‰ê    Ę˛‰àĘ˛‰Ñ!Ę˛‰ÇAĘ˛‰ÅÅĘ˛‰Ä
Ę˛‰Ä
Ę
˛‚ˇÄ˜˛ˇÚÍ"@Ä
ʲÍà¿@Ä
ʲ0Í"@`ü¡Ä˜˛PÍà¿PêAʲüÍ"G»ê}ʲ    
ÍàƒêEʲ

Í"DêEʲ

ÍàƒêEʲ    
Í"Dü≈ʲüÍà«»ÑʲPÍ"@PÑʲ0Íà¿`ÑʲÍ"@@á˝Ä˜˛ˇ¯Íà¿Ä
Ę
˛‚ˇÄ˜
˛‚ˇÄ˜”””””””””””””””””””””””””””””””””””””””””’
?ˇ’
’
’
’
’
>’
 ’
 ’
 ’
 ’
>’
’
’
’
’
?ˇ’
?ˇ””””””””””*    ˘‡
‡
Å¿ƒ˝    8p
¸Ä˛D˝)ÅB¸    DÄ
¸Ä˛˝/-Å$<âsÄÑ

    ¬0‚√ãÅ≈áÄ‚'á.«áá<qsÄ/-Å'¿DâÑ@

    "$L&HÅ$Hë0DHòHòDâÑ@/-Ò    Ò„‰$ ÑDâ@˘
Ò"$H
‰HÅ$H DHêHêDâ/-Å$ Dâ¿


"‚'»$HÄ‚$G DOêHêD˘Ä/-Å$ Dâ 


"$$HÄ$@ê DHHêDÅ@/-ÅD Dô@@


2"$H$HÅdHë DHêHêDâ@/-˘‡
‡
É¿<iĸ
”¬‚#à
‰GÄ·ßá Gáá<qĘfi˜Dfi˜8fi””””””””””””””””””””
¯ Ç⁄
IJΔ⁄ÄÛa≈Ä™8∞·„ãćÅ"&@íD…$LflÒ"$@Ç<àÚ$HflÅ"$@ÇDâ'»flÅ"$@ÇDâ$flÅ"$@ÇDâ$Hfl¯Ò!ƒ@Ç<àÒ„àfl˜ fi¯
 fi¯

¿fi””””)ƒ
  ÇÄ

˝0Ä@¸¸&ƒ
˛ Δ˛

˝
˙˚.*§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`˛.*§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âê˛.*îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚â˛.*
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"â˛.*åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"â˛.
åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"â˛.*ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àq˛Ò
¸
ÎÒ¸
Ï ‘ ’
<’
"’
"’
"
Ä˝Ä„
"Ä
˝Ä„
"(xá
‚Ãxâ√ãÄa¿Â
<(DààÅ
2DàÑLí „DDààÅ
"DàÑH‚DDàèÅ
"DàỂ˛Dàà

"DàÑ‚ÇDààÅ    "DòÑH „Çxá‚"xhcà¿„@ĸ@˛„@ĸ@˛ ‡ˇ&r@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-10    )B5Introduction to Publishers, Subscribers, and Editions4^*¿
¯
°dONLNd\lhr(el
Y@Ä°dONLNd
\rh
)#ou also need to support the standarí°dONLNd$\
h
Œ)ú'd Edition Manager menu commands in the °dONLNdKilu~(rlEdit‚@°dONLNdOi~uÄ)
 b@°dONLNdPiÅu
)menu. These menu items include,Zapf Dingbats°dONLNdolÜq(Öl
n
°dONLNdq|xàÉ)Cr\°dONLNds|ÉàÀ)eate Publisher…°dONLNdÉëlòq(ól
n
°dONLNdÖéxö´)Subscribe T›¿°dONLNdêé™öπ)2o…°dONLNdì£l™q(©l
n
°dONLNdï†x¨
)Publisher/Subscriber Options…°dONLNd≥µlºq(ªl
n
°dONLNdµ≤xæø)Show/Hide Borb@°dONLNd¬≤øæ
)Gders (optional)°dONLNd“«lŒq(Õl
n
°dONLNd‘ƒx–é)Stop õ`°dONLNdŸƒé–)All Editions (optional)°dONLNdÒ’l·(filUse Õ‡°dONLNdı’·¨)a divider t{°dONLNd
’≠·
ê)./o separate the Edition Manager menu commands frø†°dONLNd
/’
ê·
“)„om the standar°dONLNd
=’
”·
€)Cd °dONLNd
?‚lÓ~(ÎlEdit‚@°dONLNd
C‚~ÓÄ)
 b@°dONLNd
D‚ÅÓ˝)menu commands Cut, CopyÚ¿°dONLNd
[‚¸Ó
0){, and Paste. ≤Ä°dONLNd
h‚
1Ó
I)5FigurÖ@°dONLNd
m‚
IÓ
])e 2-7"¿°dONLNd
r‚
^Ó
∞) shows the standar…Ä°dONLNd
Ñ‚
∞Ó
€)R
d Edition °dONLNd
éÔl˚Â(¯lManager menu commands.


*
.
¯4
*
.
¯"
*]

ˇ·ˇ‚7^
    °dONLNd
¶
l
ñ*#
Figure 2-7°dONLNd
±
Æ

a)B)Edition Manager commands in the Edit menu
°dONLNd
‹
’l
·
ˆ(
filRThe Subscriber Options menu command should toggle with the Publisher Options menu °dONLNd.
‚l
Ó
+*)command. When a user selects a subscriber'¿°dONLNdW
‚
,
Ó
.)¿
 ß¿°dONLNdX
‚
.
Ó
A)and ‡°dONLNd\
‚
B
Ó
π)then accesses the menu bar˛¿°dONLNdv
‚
∏
Ó
Ω)v, ˛¿°dONLNdx
‚
Ω
Ó
‘)your °dONLNd}
Ôl
˚
+(
¯l,application should adjust its menus so that bÄ°dONLNd©
Ô
,
˚
’)¿"the Subscriber Options menu comman<`°dONLNdÀ
Ô
÷
˚
fi)™d °dONLNdÕ
¸lq(l
a°dONLNdŒ
¸qä)ppear@Ä°dONLNd”
¸ãè)
s}Ä°dONLNd‘
¸è≠) in the dONLNd‹
¸≠¡)Edit v‡°dONLNd·
¸¬€)menuÌ°dONLNdÂ
¸€›)
.m°dONLNdÊ
¸fi‡)
 Ì°dONLNdÁ
¸‡

)When aŸ`°dONLNdÌ
¸

f)" user selects a publisheª†°dONLNd
¸
g
m)er .@°dONLNd
¸
n
Å)and õ`°dONLNd
¸
Å
Í)then accesses the menu °dONLNd"    lz(lbar<‡°dONLNd%    z
Y)4, your application should adjust its menus so that t‡ °dONLNdY    
Y
‘)flhe Publisher Options menu °dONLNdsl"í(lcommanfl °dONLNdyí"ü)&d az‡°dONLNd|†"π)ppear;`°dONLNdÅ∫"æ)
sx`°dONLNdÇæ"‹) in the èÄ°dONLNdä‹")Edit q¿°dONLNdèÒ"
Δ)-menu. In addition, you may support a Show Bor>‡°dONLNdº
«"
‹)÷ders °dONLNd¡#l/
,(,l'menu command that toggles with Hide BorT¿°dONLNdË#
,/
„)¿+ders to display or hide all publishers and °dONLNd0l<´(9lsubscriber borZ°dONLNd!0´<
)?ders within documents. E@°dONLNd80
<
)k
Y¿°dONLNd90
<
ó)ou may also support a Stop †°dONLNdT0
ó<
Í){All Editions menu °dONLNdf=lI∞(Flcommand to pry‡°dONLNds=∞I
Ÿ)DCovide a method for temporarily suspending all update activity in a °dONLNd∂JlV
Û(SlSdocument. When the user chooses this command, you should place a checkmark next to °dONLNd    Wlcw*it. } °dONLNdWwc})
Y=†°dONLNdW}c
)%ou should also stop all publishers fr. °dONLNd3W
c
Ì)û0om sending data to editions and all subscribers °dONLNdcdlps(mlfrò‡°dONLNdedspá)om r'`°dONLNdidàp
∑)Beceiving new editions. When the user chooses this command again, rÌ°dONLNd´d
∑p
Á(m
∑
emove the °dONLNdµql}
7(zl,checkmark and update any subscribers that arO°dONLNd·q
8}
k)Ãe set up to rÁ¿°dONLNdÓq
k}
ƒ)3eceive new editions °dONLNd~lä®(álautomaticallyÚ °dONLNd~ßä©);
.


-j
Ω
¯òÄ0
u
rHH



M2@

ˇˇˇˇˇˇ

u
r
0/#

ˆ
¸ˇ¿„
ˆ
¸ˇ¿„
ˆ
¸ˇ¿„
ˆ
¸ˇ¿„ˆ
ˇÉÛ9ˇ¿„ˆ
ˇüÛ˘ˇ¿„ˆ
ˇüÉ0ˇ¿„ˆ
ˇü39ˇ¿„ˆ
ˇá39ˇ¿„ˆ
ˇü39ˇ¿„ˆ
ˇü39ˇ¿„ˆ
ˇü39ˇ¿„ˆ
ˇÉÉ<ˇ¿„
ˆ
¸ˇ¿„
ˆ
¸ˇ¿„
ˆ
¸ˇ¿„
ˆ
¸ˇ¿„
ˆ
¸ˇ¿„
ˆ
Ôˇ‡
ˆ
Ô 
ˆ
Ô0
ˆ
Ô0ˆ

ò˜c0ˆ

ò˜ê00ˆ

ô¯¯ê00ˆ

˛ôò¯‡`0ˆ

˛ôò¯Ä¿0ˆ

˛ôò¯·Ä0ˆ

˛ôò¯ì0ˆ

˛ôò¯ì0ˆ
Òò¯¯c0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô™∞
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0ˆ
¿˜c00ˆ

࿘ì00ˆ

Åô‡˜ì00ˆ

Åò¿˜„00ˆ

Åò¿˜Ň0ˆ

Åò¿˜„00ˆ

Åò¿˜ì00ˆ

âò¿˜ì00ˆ
¯`˜c00
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0ˆ
ıa‡0ˆ

àıì0ˆ

ÄÒÒò¯ì0ˆ

Åôôò¯„0ˆ

Åôôò¯É0ˆ

Åôôò¯„0ˆ

Åôôò¯ì0ˆ

âôôò¯ì0ˆ
Ò¯¯a‡0ˆ
˛
Äı0ˆ
˛
Åı0ˆ
¸ı0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0ˆ


įc00ˆ

ò
įì00ˆ

ò„«Ä˘ì00ˆ

ôëå¿˘„00ˆ

˘¡å¿˘É00ˆ

Åò·è¿˘„00ˆ

Åòqå¯ì00ˆ

Åô1å@˘ì 0ˆ

į‡«Ä˘c¿0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0ˆ

‡0ĸa‡0ˆ


ê0ôĸì00ˆ


Å„xôĸì00ˆ


√3320ôĸ„00ˆ

„3300ôĸÉ0ˆ

sÛ?00ôĸ„00ˆ
3˛0ôĸì00ˆ


3120ôĸì00ˆ

·„ôĸc00
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô™∞
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0ˆ


Åò¸0ˆ

à
ò
Åĸ0ˆ

Å≥√«è
ôôÒò„·„`0ˆ

ÅΔdcÅ˝ôì33Ä0ˆ    

ÅÜc„ÅÒ˛ô√33˛0ˆ

ÅáÊcÅÅôôò„3Û˛0ˆ

ÅÜc
Åôôòs3˛0ˆ    

âÜ&cÅÅ˛ô33Ã0ˆ
ÒÉ√·è
ĢÒò„1„Ã0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0ˆ
‡˛3~˙0ˆ

ê˛˙0ˆ

É3·√ç≥·‡x˚0ˆ

√33&N330Ã˚0ˆ
„33Ü330Ã˚0ˆ
s31Δ33Ã˚0ˆ
330Ê33Ã˚0ˆ

332fL33Ãÿ˝0ˆ
·Û·√å3·‡xÿ˝0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0ˆ


Åò˛xc¸0ˆ

ò
ÅIJÃ`¸0ˆ

ôôÒò„·„`ïÛ>0ˆ

˝ôì33ÄÃÃc3320ˆ

Ò˛ô√33ÃÃc3380ˆ

Åôôò„3ÛÃÃc330ˆ

Åôôòs3ÃÃc330ˆ

Å˛ô33ÃÃc33&f`0ˆ

ĢÒò„1„x¯33f`0ˆ
ˆ¿˚0ˆ
ˆ¿˚0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô™∞
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0
ˆ
Ô0ˆ
„˛
„0˝¿˛0ˆ

ì˛˝¿˛0ˆ

É·„33„··„g¿˛0ˆ

√˛3
˛323å¿˛0ˆ
„˛3
˛31Û¿˛0ˆ
s˛3
¸3
¿˛0ˆ
˝3
¸3
¿˛0ˆ

˛32¸3
¿˛0ˆ
„1„¸
„3„··Û¿˛0ˆ
˘¯0ˆ
˘¯0
ˆ
Ô0
ˆ
Ô0
ˆ
Ôˇ
ıˇ——————————————————————————————————————————————————————————————————————————————————%¸¯¿|ê˛
¿¸    DÄĈÄà‡J˚$ÄÑ "˝
"@Ä@¡ÄˆÄàB˚1/ÄÇ"§V`@Äita`¡ú,ph≈ÉYñcÖÜú    `ÎKã0¬ƒ@1/ÄÇ"dXêÄÄôDëꢢ2àô&ífYîFI¢    êåí …#$@1/¸Ç¿"î$QÄ˝    E    ¢Ü"
!DQƒP†    à°ËJä$@1/ÄLJ'"$Q¯‡ÄÅ    E    îö"iÙ!DQDPú    àøJãÚ$@1/ÄÇ "$Q
Å    E    î¢"â
!DQDPÇ    à†Jä$@1/ÄÑ "d–ê 
ÄôDëà¶"òô$íDQƒI¢    àí â"$¿1/¸¯¿£P`>
¸i4aàô"dhƒDQ$Fú    hå„Iàà¬#@
¯ Ú΢
@Úê΢

ÄÚ`Η——————————————————————
¯ Çÿ
IJΔÿÄÛa≈Ä™8∞·„ãÄfiÅ"&@íD…$L›Ò"$@Ç<àÚ$H›Å"$@ÇDâ'»›Å"$@ÇDâ$›Å"$@ÇDâ$H›¯Ò!ƒ@Ç<àÒ„à›˜ ‹¯
 ‹¯

¿‹————)ƒ
  ÇÄ

˝0Ä@¸˙&ƒ
˛ Δ˛

˝
˙˘.*§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`¸.*§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âê¸.*îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚â¸.*
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"â¸.*åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"â¸.
åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"â¸.*ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àq¸Ò
¸
ÈÒ¸
È—————
Ä˝ÄflÄ
˝Äfl(xá
‚Ãxâ√ãÄa¿·(DààÅ
2DàÑLí ·DDààÅ
"DàÑH‡DDàèÅ
"Dàệ˛Dàà

"DàчÇDààÅ    "DòÑH ·Çxá‚"xhcà¿·@ĸ@˛·@ĸ@˛ fiˇC¨@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡ä5Introduction to Publishers, Subscribers, and Editions

, (‡2-11
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh¨(eäIf you fiJ‡°dONLNd    \≠h
‹)#Fnd that you need all of the available space in the Edit menu for your °dONLNdOiäu
,(rä"application’s commands, you may cr °dONLNdqi
-u
c)£eate a hierar'¿°dONLNd~i
cu)6$chical menu for the Edition Manager °dONLNd¢väÇ
u(ä2menu commands. If you choose to implement this strê@°dONLNd‘v
uÇ
å)Îuctur °dONLNdŸv
çÇ)e, you should allow users to °dONLNdˆÉäè
a(åä,access the Edition Manager menu commands thr´¿°dONLNd
"É
aè
)◊"ough a Publishing menu command in °dONLNd
Dêäú
-(ôä$the Edit menu. Because this menu str&`°dONLNd
hê
.ú
E)§uctur¨@°dONLNd
mê
Eú
¸),e is not as accessible to users, you should °dONLNd
ôùä©
h(¶ä3implement it only if you have no other alternative.°dONLNd
ÕØ䪢*FigurR¿°dONLNd
“Ø¢ª∂)e 2-8@°dONLNd
◊Ø∂ª
∞)4 shows the Edition Manager menu commands in a hierar´¿°dONLNdØ
±ª
Ù)˚chical menu strÄ°dONLNdØ
ıª)Ducturà`°dONLNdØª)e.

›HÓ4fiHÓ"fiH]

ˇ·ˇ‚7^
    °dONLNd#”äfi¥(€ä
Figure 2-8°dONLNd.”Ãfi
”)B:Edition Manager commands under the Publishing menu command
°dONLNdj
Ää
å
˛(
âäRFor each publisher or subscriber within an open document, you must have a section °dONLNdº
çä
ôç*
rE°dONLNdΩ
çé
ô†)ecorπ`°dONLNd¡
ç†
ô„)d and an alias rf`°dONLNd—
ç‰
ôˆ)Decor⁄¿°dONLNd’
çˆ
ô
9)d. The section r_¿°dONLNdÂ
ç
:
ô
L)Decor‘ °dONLNdÈ
ç
L
ô
œ)d contains a time stamp that r °dONLNd
ç
–
ô
‚)ÑecorçÄ°dONLNd
ç
‚
ô
ˇ)ds the °dONLNd
öä
¶ˆ(
£äversion of the data that rÓ¿°dONLNd,
öˆ
¶
ã)l$esides in the section. The section ri°dONLNdP
ö
å
¶
û)ñecor›`°dONLNdT
ö
û
¶
⁄)d also identifij†°dONLNdc
ö
€
¶
ˆ)=es the °dONLNdj
ßä
≥
@(
∞ä+section as either a publisher or subscriberñ`°dONLNdï
ß
@
≥)∂0, and it establishes a unique identity for each °dONLNd≈
¥ä
¿(
Ωäpublisher or subscriberÓ‡°dONLNd‹
¥Ô
¿
,)e. The section rX °dONLNdÎ
¥
-
¿
?)>ecorÃÄ°dONLNdÔ
¥
?
¿
^)d does Ä °dONLNdˆ
¥
_
¿
l) not”`°dONLNd˘
¥
l
¿)& contain the data within the section. °dONLNd
¡ä
Õ∑(
 äThe alias rÄ°dONLNd*
¡∏
Õ ).ecorLJ°dONLNd.
¡ 
ÕÁ)d is a r    °dONLNd6
¡Ë
Õ¯)eferµ °dONLNd:
¡¯
Õ
~) ence to the edition container frg°dONLNdZ
¡

Õ
)áom the document that contains °dONLNdx
Ί
ڬ(
◊äthe corrz¿°dONLNdÄ
ά
⁄
g)"*esponding publisher or subscriber section.°dONLNd´
‡ä
Ïû(
ÈäTher¿°dONLNdØ
‡ü
ÏØ)e ar`°dONLNd≥
‡Ø
Ï)Oe special options associated with publishers and subscribers within documents. °dONLNd
Ìä
˘ê(
ˆä
Y@Ä°dONLNd
Ìê
˘
·)Lour application can use the publisher and subscriber options dialog boxes prœÄ°dONLNdO
Ì
·
˘(
ˆ
·
ovided by °dONLNdY
˙ä
¢(ä?the Edition Manager to make these choices available to the userË¿°dONLNdò
˙
°(
°. For example, a user can °dONLNd≤ä    (äVselect Open Publisher within the subscriber options dialog box to access the document °dONLNdä ˆ*containing the publisher»`°dONLNd ı ˙)k. ö¿°dONLNd"˙ 
)
Y[@°dONLNd#
 )?our application can also allow a user to cancel subscribers or °dONLNdb!ä-
∞(*äApublishers within documents, specify when to update an edition fr`°dONLNd£!
±-
Û(*
±om a publisherø¿°dONLNd±!
Ú-)A, or °dONLNd∂.ä:
Ã(7äHspecify when to update a subscriber with a new edition. These options ar∫†°dONLNd˛.
Ã:
¯(7
Ã
e describe√ °dONLNd.
¯:),d in °dONLNd;äG
ú(Dä;“Using Publisher and Subscriber Options” beginning on page k`°dONLNdH;
ùG
Ø(D
ù2-43ø@°dONLNdL;
ØG
±)
.

Ìà
hòÄD
nHH



M2@

ˇˇˇˇˇˇ

n8
fi
î
Ú˝ˇ˛“
Ú˝ˇ˛“
Ú˝ˇ˛“
Ú˝ˇ˛“Ú˛ÃÁ˛“Ú˛œÁ˛“Ú˛~√˛“Ú˛|ÃÁ˛“Ú˛ÃÁ˛“Ú˛|ÃÁ˛“Ú˛|ÃÁ˛“Ú˛|ÃÁ˛“Ú˛Û˛“
Ú˝ˇ˛“
Ú˝ˇ˛“
Ú˝ˇ˛“
Ú˝ˇ˛“
Ú˝ˇ˛“
Úڡě
ÚÚÄ›
ÚÚÄ›
ÚÚ¿›Ú00˙1è¿¿›Ú00˙J@¿¿›Ú3·Ò‡˚J@¿¿›Ú˛30˚?ÅÄ¿›Ú˛30˚
¿›Ú˛30˚?Ü¿›Ú˛30˚JL¿›Ú˛30˚JL¿›Ú
„1Ò‡˚1è¿¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚU¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›Ú
‡
Ä˙1å¿¿›Ú
Ä˙JL¿¿›Ú3¿˙JL¿¿›Ú1Ä˙?å¿¿›Ú1Ä˙
Ä¿›Ú1Ä˙?å¿¿›Ú1Ä˙JL¿¿›Ú1Ä˙JL¿¿›Ú
·¿˙1å¿¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›Ú
‡¯1áÄ¿›Ú¯JL@¿›Ú
„„0˚JL¿›Ú330˚?å¿›Ú330˚
¿›Ú330˚?å¿›Ú330˚JL¿›Ú330˚JL@¿›Ú
·„·˚1áÄ¿›Ú˛0¯¿›Ú˛0¯¿›Ú˝

‡¯¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›Ú‡˙1å¿¿›Ú0˙JL¿¿›Ú1·«è˚JL¿¿›Ú23#ĸ?å¿¿›Ú·ÛÉĸ
¿¿›Ú1√ĸ?å¿¿›Ú0„˚JL¿¿›Ú2cĸJLÄ¿›Ú
Ò¡è˚1è¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›Ú    
¿`3˛1áÄ¿›Ú     `33˛JL¿¿›Ú    Δ<833˛JL¿¿›Ú    Üffd`33˛?å¿¿›Ú    
Δff``?3˛
¿¿›Ú    ÁÊ~``33˛?å¿¿›Úf˛`
33˛JL¿¿›Ú    f&bd`33˛JL¿¿›Ú    
√Δ<8033˛1å¿¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚU¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›
ÚÚ¿›ÚÛˇ˛ÓÚÛˇÓÚÛˇÓÚÙˇ
flÓ$Úˇ¸¸¸œ˘˘¸ˇœ˛0Ä0˝Ó#Úˇ¸œ¸¸ˇ˘˚ˇ«Ä0Ä0˝Ó'Ú
ˇ¸ÃÃŒ89É¡˛ˇ√<<xôüé>6Ó$Úˇ¸˝ÃŸ˛ô˛ˇ    ¡fF1ò˝ô338Ó&Úˇ¸˛Ãy˛ô˛ˇ¿f>1òôôú330Ó&Úˇ¸¸ÃÃŒ9˛ô˛ˇ¡~f1¯ôôé3?0Ó&Úˇ¸¸ÃÃœ˛ô˛ˇ√`f1Äôôá300Ó%Úˇ¸¸ÃÃÕ˝ô˛ˇ«òbf1àôôì310ÿÓ'Ú
ˇ¸˛Œ9ôô¡˛ˇœ<>üé30ÿÓÚ¯ˇ˘˛ˇ
flÓÚ¯ˇπ˝ˇÓÚ¯ˇ√˝ˇÓÚÛˇÓÚÛÓÚÛÓÚÛÓÚÛ00‡˚ÓÚÛ0˛0
Ä˚ÓÚÛ3>8€>
áĸÓÚÛ332d„33
忸ÓÚÛ338`√33
忸ÓÚÛUP33`√3?
忸ÓÚÛ33`√30
忸ÓÚÛ33&d√31
åÃÃ˝ÓÚÛ>8√>
áåÃ˝ÓÚÛÓÚÛÓÚÛÓÚÛÓÚÛÓÚÛÓÚÛÓ&Ú
Δ˛Δ`˛
êÄ0Ä0˝Ó%Ú&˛&˛
êÄ0¿¸Ó'Ú!√Δfg«√√Δœêôüé>6œè1„·¿Ó&Úܲf
˛fdgê˝ô338ÃΔ˛3 Ó'Ú
Δ˛f
˛fcÊêôôú330ÃΔ˛3ÄÓ%ÚÊ˛f
¸fêôôé3?0ÃΔ331¿Ó$Ú˝f
¸fêôôá300ÃΔ330‡Ó%Ú˛fd&¸fêôôì310ÃΔ332ffÓ'Ú!
Δc«¯Δg«√√Êêüé30èÉ1„1ΔfÓÚ˘¸˜˚ÓÚ˘¸˜˚ÓÚÛÓÚÛÓÚ‡ˇÓÒ‡ˇÓΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩ2~|
‡˛
¯Ä˛
‡D Äı˛B¯


Ù

0@B"˛Ä˝
!@ ı˛
BÑ


Û

E@A"˛:Åáë.p
!Ãqá8∞·„ãÅ√ã1fXx‡"Xx‚‡‚√ÄÑâ·qcòqb 8qf,√ãE@A
Ä"˛:Äàë0à
D àôäD…$L$L…ô"dâ"dâC$@Ñââë"dâí Dâô3$LëE~A`˛:àë à!ƒD àëä<àÚ$HHâDâ"DâB$@¯âÅ"Dâ @â"#»ëE@Apë"˛:Äàë ¯!D àëRDâ'»Hâ"Dà‡"DâÚB'¿Äâq"D˘ @â"$HëE@A"˛:Äàë Ä!D àëRDâ$Hâ"Dà"DâB$Äâ    "DÅ @â"$HëE@B"˛:Äàì à!D àë"Dâ$H$Hâ"Dâ&DâB$@Äôâ"Dâ`Dâ"$HëE~|
‡˛:Äáç p„ƒá"<àÒ„à
√àâDx‡Dx‚2#ÄÄi·qDq†8q"#»èˆÄÒ ËÙ˜
ÄÚ
 Ë"Ù˜Ò

¿ËÙΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩΩ
¯ ǃ
Ä˛ΔƒÄÛa≈Ä™8∞·„ãÄ Å"&@íD…$L…Ò"$@Ç<àÚ$H…Å"$@ÇDâ'»…Å"$@ÇDâ$…Å"$@ÇDâ$H…¯Ò!ƒ@Ç<àÒ„à…˜ »¯
 »¯

¿»ΩΩΩΩ)ƒ
  ÇÄ

˝0Ä@¸Ê&ƒ
˛ Δ˛

˝
˙Â.*§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`Ë.*§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âêË.*îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚âË.*
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"âË.*åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"âË.
åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"âË.*ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àqËÒ
¸
’Ò¸
’ΩΩΩΩΩ
Ä˝ÄÀÄ
˝ÄÀ(xá
‚Ãxâ√ãÄa¿Õ(DààÅ
2DàÑLí ÕDDààÅ
"DàÑHÃDDàèÅ
"Dàá»Ã˛Dàà

"DàÑÃÇDààÅ    "DòÑH ÕÇxá‚"xhcà¿Õ@ĸ@˛Õ@ĸ@˛  ˇÏ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-12    )BAbout the Edition Manager4^*¿
¯

^*x
¯4^*x
¯

à*ê
¯4â*ê
¯ ä*ä
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNdu*à(É*About the Edition ManagerˇˇˇˇˇˇV˛(É

2
°dONLNdôl•
:(¢l/The next section discusses how to save, open, r=†°dONLNdJô
;•
⁄)œ#ead, and write a document that shar±†°dONLNdmô
ڥ
Â)ües °dONLNdp¶l≤
(Øl&data. In addition, it describes how to,Zapf Dingbats°dONLNdóºl√q*
n
°dONLNdôπx≈
1)*make data accessible to other applications°dONLNdƒŒl’q(‘l
n
°dONLNdΔÀx◊È)integrate data into numer^`°dONLNdflÀÈ◊
,)qous documents°dONLNḋlÁq(Êl
n
°dONLNdÔ›xÈ…)set update options°dONLNd
Úl˘q(¯l
n
°dONLNd
Ôx˚π)implement bor‰°dONLNd
Ôπ˚Ã)Aders°dONLNd

l
q(

l
n
°dONLNd


x
≠)modify shar°dONLNd
#

Æ
Œ)6ed data°dONLNd
+
l
q(
l
n
°dONLNd
-
x
⁄)customize dialog boxeR¿°dONLNd
B
€
fl)c
s°dONLNd
D
(l
/q(
.l
n
°dONLNd
F
%x
1
)"subscribe to data in non-edition fi-@°dONLNd
i
%

1
)ïles


7*
R
¯4
8*
R
¯


b*
j
¯4
c*
j
¯ 
d*
d
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNd
n
O*
bK(
]*Usini(°dONLNd
r
OL
bg)"g th2°dONLNd
v
Oh
bÌ)e Edition ManagerˇˇˇˇˇˇV˛(
]

2
°dONLNd
â
sl

?(
|l/This section describes how your application can°dONLNd
π
âl
êq*
n
°dONLNd
ª
Üx
í{)
rE°dONLNd
º
Ü|
íô)eceive ¬`°dONLNd
√
Üô
í›)Apple events fr„°dONLNd
“
Ü›
í
H)Dom the Edition Manager°dONLNd
È
õl
¢q(
°l
n
°dONLNd
Î
òx
§¬)set up a section r¿°dONLNd
˝
ò¬
§‘)JecorÙ °dONLNd

ò‘
§

)d and alias rO¿°dONLNd
ò

§
)7ecorƒ °dONLNd
ò

§
’)(d for open documents containing sections°dONLNd;
≠l
¥q(
≥l
n
°dONLNd=
™x
∂
#)&save a document that contains sections°dONLNdd
øl
Δq(
≈l
n
°dONLNdf
ºx
»
%)&open a document that contains sections°dONLNdç
—l
ÿq(
◊l
n
°dONLNdè
Œx
⁄{)
rE°dONLNdê
Œ|
⁄fi)ead and write sections°dONLNdß
„l
Íq(
Èl
n
°dONLNd©
‡x
ÏÄ)crµ@°dONLNd´
‡Ä
Ï
))&eate a publisher within a document, cr3@°dONLNd—
‡
*
Ï
ñ)™eate its edition container‚ °dONLNdÎ
‡
ï
Ï
Ó)k, and write data to it°dONLNd
ıl
¸q(
˚l
n
°dONLNd
Úx
˛Ä)crµ@°dONLNd
ÚÄ
˛
9))eate a subscriber within a document and r¿°dONLNd/
Ú
:
˛
v)∫ead its data fr_‡°dONLNd>
Ú
v
˛
≥)<om an edition°dONLNdLlr(l
Tµ¿°dONLNdMq
∞)Fo begin, you must determine whether the Edition Manager is available ou`°dONLNdì
±
Õ(
±n the sa °dONLNdö
Œ
Î)ystem .°dONLNd†l§(lby using the ,
Courier°dONLNd≠§Œ)8Gestalt°dONLNd¥Œ
!)* function with the °dONLNd«
!
ü)SgestaltEditionMgrAttr°dONLNd‹
ü
•)~ (°dONLNdfi
•
…)'edtn'°dONLNd‰
…
Ú)$
) selector¬†°dONLNdÓ
Ò
ˆ)(. °dONLNdl)à(&lIf the °dONLNd˜à)∏)response°dONLNdˇ∏))0 parameter rR`°dONLNd)
R)8eturns 1 in the bit defiR`°dONLNd#
R)
É)bned by the °dONLNd.*l6¸(3lgestaltEditionMgrPresent°dONLNdF*¸6
∫)ê, constant (bit 0), the Edition Manager is prR`°dONLNdr*
∫6
‘)æesent.°dONLNdy<lHÍ(ElIf the Edition Manager is prR`°dONLNdï<ÍH
å)~%esent, load it into memory using the R`°dONLNd∫<
åH
Ê)¢InitEditionPackR`°dONLNd…<
ÊH
Ë)Z
 .
°dONLNd IlU
Ù(RlVfunction. This function determines whether the machine has enough space in the system °dONLNd Vlb
*(heap for the Edition Manager to operate..°dONLNdImlyˆ*err := InitEditionPack;°dONLNdaÖlëà*If the °dONLNdhÖàë‚)InitEditionPack°dONLNdwÖ‚ë
)Z function rR`°dONLNdÇÖ
ë
+),eturns R`°dONLNdâÖ
+ë
I)noErrï°dONLNdéÖ
Hë
Í)$, you have enough space to load the .
°dONLNd≤ílû
Ì(õlYpackage. If you do not have enough space, the application can either terminate itself or °dONLNdül´
l*9continue with the Edition Manager functionality disabled.ˇ:@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-13
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

kHr4lHr mäm

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\äk…(gä
Receiving ¨L°dONLNd
\…k
ª)?%Apple Events From the Edition Managerˇˇˇˇˇˇ€r(g
2
°dONLNd1rä~
Ü({ä7Applications that use the Edition Manager must support 釰dONLNdhr
Ü~
fl)¸Apple events. This rs °dONLNd|r
fl~
ˆ)Yequirä`°dONLNdÅr
ˆ~)es that °dONLNdâäã
(àäyour application support the r Ä°dONLNdß
ã
&)Öequir·¿°dONLNd¨
&ã
±)ed Open Documents event and 4†°dONLNd»
≤ã)åApple events sent by °dONLNd›åäòÂ(ïäthe Edition Manager√Ä°dONLNdå‰òÛ)Z. SeÇ°dONLNdÙåÛò˙)e Ä°dONLNdˆå˚ò
)the c‰ °dONLNd˚å
ò
')hapte√†°dONLNd
å
(ò
C)r “IntrmÄ°dONLNd
å
Dò
y)oduction to A@°dONLNd
å
yò
ø)5Apple Events” iÉÄ°dONLNd
"å
øò
”)Fn thi—°dONLNd
'å
”ò
ı)s book fc†°dONLNd
/å
ˆò
)#or °dONLNd
2ôä•≠(¢ägeneral Œ¿°dONLNd
:ô≠•È)#information o†°dONLNd
GôÍ•Ú)=n r†°dONLNd
IôÚ•˘)
A9‡°dONLNd
Jô˙•
/)pple events.°dONLNd
W´ä∑
“(¥äJApple events sent by the Edition Manager arrive as high-level events. The ,
Courier.°dONLNd
°∏äƒÃ*EventRecord°dONLNd
¨∏Ã
)B data type defPÄ°dONLNd
∫∏
ƒ
Q)@ines the event r"‡°dONLNd
 ∏
Qƒ
c)Eecorı@°dONLNd
θ
bƒ
k)d.°dONLNd
—œä€ˆ(ÿäTYPE EventRecord =°dONLNd
›úÈ¿+RECORD°dONLNd
ÓÎƘÃ+what:°dONLNd
˜Îˆ˜
&)HInteger;°dONLNdÎ
>˜
§)H{kHighLevelEvent}°dONLNd˘Æ
fi(
Æmessage:°dONLNd#˘ˆ

&)HLongInt;°dONLNd/˘
>

D)H
{°dONLNd0˘
D

h)'sect'°dONLNd6˘
h

n)$
}°dONLNd:
Æ
Ã(
Æwhen:°dONLNdC
ˆ

&)HLongInt;°dONLNdN
Æ
!“(
Æwhere:°dONLNdX
ˆ
!
)HPoint;°dONLNdb

>
!
D)H
{°dONLNdc

D
!
h)'read'°dONLNdi

h
!
t)$, °dONLNdk

t
!
ò)'writ'°dONLNdq

ò
!
§)$, °dONLNds

§
!
»)'cncl'°dONLNdy

»
!
‘)$, °dONLNd{

‘
!
¯)'scrl'°dONLNdÅ

¯
!
˛)$
}°dONLNdÖ
#Æ
/¥(
,Æ
m°dONLNdÜ
#¥
/Í)    odifiers:°dONLNdì
#ˆ
/
&)BInteger;°dONLNdù
1ú
=¥(
:úEND;.
°dONLNd¢
Iä
U
(
RäThe Edition Manager can send tW°dONLNd¿
I

U
-)çhese @°dONLNd≈
I
-
U
4)
A·Ä°dONLNdΔ
I
4
U
f)pple events¢°dONLNd—
I
g
U
)3& with the event class and event ID as .°dONLNd˜
Vä
bπ(
_ä    shown herR`°dONLNd
Vπ
b¡)/e:,Zapf Dingbats.
°dONLNd
lä
sè(
rä
n
.°dONLNd
iñ
uˆ)Section Read events (°dONLNd
iˆ
u
D)`'sect' 'read'°dONLNd'
i
D
u
H)N
).
°dONLNd)
~ä
Öè(
Ñä
n
.°dONLNd+
{ñ
áƒ)    Section W¬†°dONLNd4
{√
á˘)-rite events (¬†°dONLNdA
{˘
á
G)6'sect' 'writ'¬†°dONLNdN
{
G
á
K)N
).
°dONLNdP
êä
óè(
ñä
n
.°dONLNdR
çñ
ô˝)Section Cancel events (°dONLNdi
ç˝
ô
K)g'sect' 'cncl'°dONLNdv
ç
K
ô
O)N
).
°dONLNdx
¢ä
©è(
®ä
n
.°dONLNdz
üñ
´«)Section ScrR`°dONLNdÖ
ü«
´˘)1oll events (R`°dONLNdë
ü˘
´
G)2'sect' 'scrl'R`°dONLNdû
ü
G
´
K)N
).
°dONLNd†
∞ä
º
(
πäEach time your application crê@°dONLNdΩ
∞

º
ô)Ç!eates a publisher or a subscriberë¿°dONLNdfi
∞
ô
º
˚)ç, the Edition Manager °dONLNdÙ
Ωä
…ç(
Δä
rE°dONLNdı
Ωé
…)Xegisters its section. When an edition is updated, the Edition Manager scans its list to °dONLNdM
 ä
÷™(
”älocate rü °dONLNdU
 ™
÷«) egisterÓ@°dONLNd\
 «
÷
7)ed subscribers. For each r°dONLNdv
 
7
÷
T)pegister? °dONLNd}
 
U
÷
‹)!ed subscriber that is set up to rá°dONLNdû
 
‹
÷
˘)áeceive °dONLNd•
׊
„
(
‡äupdated editions automaticallyª@°dONLNd√
◊

„
g)â, your application r5Ä°dONLNd◊
◊
h
„
Á)Ueceives a Section Read event.°dONLNdı
Èä
ı
e(
Úä2If the Edition Manager discovers that an edition fim@°dONLNd(
È
f
ı
æ)‹le is missing while rK†°dONLNd=
È
æ
ı
Û)Xegistering a °dONLNdJ
ˆä¥(
ˇä    publisherÓ‡°dONLNdS
ˆ≥…)), it crŒ‡°dONLNdZ
ˆ…
&)eates a new edition fi†°dONLNdp
ˆ
'
—)^&le and sends the publisher a Section Wß°dONLNdñ
ˆ
–
˛)©rite event. °dONLNd£äæ(ä
When you rΩ °dONLNd≠æ
≈)4<eceive a Section Cancel event, you need to cancel the specifiœ`°dONLNdÍ
≈(
≈ed section. Note °dONLNd˚ä!¿(äthat the curr‚Ä°dONLNd¿!)6Hent Edition Manager does not send you Section Cancel events, but you do °dONLNdP"ä.∑(+ä
need to pr`°dONLNdZ"∑.
$)-ovide a handler for futurÒÄ°dONLNds"
$.
Z)me expansion.°dONLNdÄ4ä@(=äZIf the user selects a subscriber within a document and then selects Open Publisher in the °dONLNd⁄AäM
å*;subscriber options dialog box, the publishing application rg °dONLNdA
åM(J
åeceives the Open Documents °dONLNd0NäZ
Ä(Wä5event and opens the document containing the publisheri¿°dONLNdeN
ÄZ)ˆ". The publishing application also °dONLNdá[ägç(dä
rE°dONLNdà[égÁ)eceives a Section Scræ°dONLNdù[Ág
)Yoll event. ScrFÄ°dONLNd´[
 g
¥)9$oll to the location of the publisherw`°dONLNdœ[
¥g)î, display this section °dONLNdÊhätª(qäon the userb°dONLNdÒhºt“)2’s scrXÄ°dONLNd˜h“t
8)een, and turn on its bor(Ä°dONLNdh
9t
G)gderC °dONLNdh
Gt
I)
.°dONLNdzäÜî(ÉäSeâ`°dONLNdzîÜõ)
e ”°dONLNdzõÜ
Ó)G“Opening and Closing a Document Containing Sections” beginning on page ˘Ä°dONLNd_z
ÓÜ(É
Ó2-22M`°dONLNdcz
Ü) f!@°dONLNdezÜ)or °dONLNdháäì˘(êädetailed information on r• °dONLNdÅá˘ì
J)oegistering and unrı`°dONLNdìá
Jì)Q,egistering a section and writing data to an °dONLNdøîä†∏(ùäedition. Se»¿°dONLNd î∏†ø).e `°dONLNdÃ
“);“Using Publisher and Subscriber Options” beginning on page ˝¿°dONLNd    î
Ҡ
‰(ù
“2-43Q†°dONLNd    î
†
Í) f%Ä°dONLNd    î
Ά
ˆ)or °dONLNd    °ä≠
b(™ä0information on publisher and subscriber options.ˇÍ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-14    )BUsing the Edition Manager4^*¿
¯
°dONLNd\lhâ(elAfter rfi¿°dONLNd\âhΩ)eceiving an ,¿°dONLNd\æh
s)5'Apple event sent by the Edition Managerl °dONLNd:\
sh
ô)µ
, use the ¯‡°dONLNdD\
ôh
”)&Apple Event °dONLNdPilu
Ø(rlKManager to extract the section handle. In addition, you must also call the ,
Courier.°dONLNdõvlÇfi*IsRegisteredSection°dONLNdÆvfiÇ
¨)r/ function to determine whether the section is rR`°dONLNd›v
¨Ç
À)Œegister$¿°dONLNd‰v
ÀÇ
Ô)
ed. It is .
°dONLNdÓÉlèí(ål    possible †°dONLNd˜ÉìèÀ)'(because of a °dONLNd
ÉÃè
")9 race condition) to r*@°dONLNd
É
"è
À)V(eceive an event for a section that you rp°dONLNd
AÉ
Àè
Ì)©ecently °dONLNd
IêlúΩ(ôldisposed of or unr™ °dONLNd
[êΩú⁄)Qegister˘@°dONLNd
bê⁄ú
8)ed. One way to ensur†°dONLNd
vê
9ú
é)_e that an event corrÛ`°dONLNd
äê
çú
fl)Tesponds to a valid .°dONLNd
ùùl©»(¶lsection is to call the °dONLNd
¥ù»©
:)\IsRegisteredSection°dONLNd
«ù
:©
ë)r function after you rR`°dONLNd
‹ù
ë©
÷)Weceive an eventR`°dONLNd
Îù
֩
€)E. R`°dONLNd
Ìù
۩
›)
 °dONLNd
Ô¥l¿
P(Ωl&err := IsRegisteredSection (sectionH);.
°dONLNdÃlÿö*Listing 2-1 @°dONLNd!Ãõÿ
)/ illustrates how to use the ~°dONLNd=Ã
ÿ
)s1Apple Event Manager and install an event handler °dONLNdnŸlÂı(‚lto handle Section Read events. Ɇ°dONLNdçŸıÂ˚)â
YD °dONLNdéŸ˚Â
®)'ou can write similar code for Section W2 °dONLNdµŸ
®Â
⁄)≠rite events, °dONLNd¬ÊlÚú(ÔlSection Scr`@°dONLNdÕÊúÚ
@)0&oll events, and Section Cancel events.


*

¯4
*

¯"
*_

ˇ·ˇ‚7^
    °dONLNdı
l
ò(
lListing 2-1°dONLNd

∞

√)DFAccepting Section Read events and verifying if a section is registered
.°dONLNdI
%l
1~(
.l{th°dONLNdL
%~
1
Ä)+e following goes in your initialization cod°dONLNdw
%
Ä
1
å(
.
Äe}°dONLNdz
3l
?x(
<lmy°dONLNd|
3x
?
‘):Err := AEInstallEventHandler(sectionEventMsgClass {'sect'}°dONLNd∂
3
‘
?
⁄(
<
‘
,°dONLNd¬
A
 
M
&(
J
 
 °dONLNd√
A
&
M
,)
s°dONLNdƒ
A
,
M
º)ectionReadMsgID {'read'}°dONLNd‹
A
º
M
¬)ê
,°dONLNdË
O
 
[
&(
X
 
 °dONLNdÈ
O
&
[
,)
@°dONLNdÍ
O
,
[
Œ)MyHandleSectionReadEvent, 0°dONLNd
O
Œ
[
‘)¢
,°dONLNd
]
 
i
&(
f
 
 °dONLNd
]
&
i
,)
F°dONLNd
]
,
i
P)ALSE);°dONLNd
yl
Ö~(
Çl{th°dONLNd
y~
Ö
Œ)8is is the routine the Apple Event Manager calls when a }°dONLNdW
ál
ì
(
êl{ Section Read event arrive°dONLNdr
á

ì
)¢s}°dONLNdv
£l
Ø
Ü(
¨l/FUNCTION MyHandleSectionReadEvent(theAppleEvent°dONLNd•
£
Ü
Ø
å(
¨
Ü
,°dONLNd≤
±
2
Ω
8(
∫
2
 °dONLNd≥
±
8
Ω
>)
r°dONLNd¥
±
>
Ω
û)eply: AppleEvent°dONLNdƒ
±
û
Ω
§)`
;°dONLNd—
ø
2
À
8(
»
2
 °dONLNd“
ø
8
À
>)
r°dONLNd”
ø
>
À
í)efCon: LongInt°dONLNd·
ø
í
À
û)T):°dONLNd„
ø
û
À
») OSErr;°dONLNdÎ
Õl
Ÿx(
÷lVA°dONLNdÌ
Õx
Ÿ~)
R°dONLNd
€~
Áê+myE°dONLNdÛ
ې
Á¢)rr:°dONLNd˙
€Δ
ÁÍ)6OSErr;°dONLNd
È~
ı¥(
Ú~    sectionH:°dONLNd
ÈΔ
ı
)HSectionHandle;°dONLNd
˜lä(lBEGIN°dONLNd%~ê+{ge°dONLNd(ê
∂)1t section handle out of Apple event message buffe°dONLNdY
∂
¬(
∂r}°dONLNd]~ê(~myE°dONLNd`ê¥)rr := °dONLNdf¥¿)$My°dONLNdh¿
Ï)2GetSectionHandleFromEvent(theAppleEvent, sectionH)°dONLNdö
Ï
Ú(
Ï
;°dONLNdù!~-¢(*~IF myE°dONLNd£!¢-¸)$rr = noErr THEN°dONLNd¥/~;ñ(8~BEGI°dONLNd∏/ñ;ú)
N°dONLNdº=êIñ(Fê
I°dONLNdΩ=ñI
Ä)'F IsRegisteredSection(sectionH) = noErr°dONLNd‰=
ÄI
û)Í THEN°dONLNdÌK¢W
∞(T¢-{if section is registered, read the new data}°dONLNdY¢e®*
M°dONLNdY®e
⁄)3yHandleSectionReadEvent := DoSectionRead(sectionH);°dONLNdTg~sê(p~END°dONLNdWgêsñ)
 °dONLNdZu~ÅÑ(~~
E°dONLNd[uÑÅê)LS°dONLNd]uêÅñ)
E°dONLNdaÉêèñ*
M°dONLNdbÉñè
,)yHandleSectionReadEvent :°dONLNd{É
,è
J)ñ= myE°dONLNdÄÉ
Jè
V)rr°dONLNdÇÉ
Vè
\)
;°dONLNdÑëlùr(öl
E°dONLNdÖërù
&)ND; {MyHandleSectionReadEvent}ˇ3Z@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-15
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\äh¥(eä{this r°dONLNd\¥h“)*outin°dONLNd\“h‰)e r°dONLNd\‰hˆ)ead°dONLNd\ˆh¸)
s°dONLNd\¸h
∞) in subscriber data and update°dONLNd1\
∞h
∂)¥
s°dONLNd2\
∂h
º)
 °dONLNd3\
ºh)its display}°dONLNd@jäv
™(sä0FUNCTION DoSectionRead(subscriber: SectionHandle°dONLNdpj
™v
∂(s
™):°dONLNdrj
∂v
‡) OSErr;°dONLNdzxäÑ¢(ÅäBEGI°dONLNd~x¢Ñ®)
N°dONLNdÅÜúíÆ(èú{yo°dONLNdÑÜÆí)ur code her°dONLNdèÜí¸)Be}°dONLNdíî䆢(ùäEND;°dONLNdòîƆ
)${DoSectionRead}°dONLNd®¨ä∏ú(µä{th°dONLNd´¨ú∏
û)+is is part of your Apple event–handling cod°dONLNd÷¨
û∏
™(µ
ûe}°dONLNdŸ∫äΔ¿(√ä    FUNCTION °dONLNd‚∫¿ΔÃ)6My°dONLNd‰∫ÃΔ)4GetSectionHandleFromEvent(theAppleEvent: AppleEvent;°dONLNd
%»
b‘
h+ñ
 °dONLNd
&»
h‘
)VAR sectionH: SectionHandle°dONLNd
A»
‘)¢
)°dONLNd
O÷
b‚
h(fl
b
 °dONLNd
P÷
h‚
t): °dONLNd
R÷
t‚
ò)OSErr;°dONLNd
Y‰äú(ÌäVAR°dONLNd
^Úú˛fi+ignoreType:°dONLNd
nÚˆ˛
,)Z    DescType;°dONLNd
y
ú
fi(
    úignoreSize:°dONLNd
â
ˆ

)ZSize;°dONLNd
è
ä
®(
äBEGIN°dONLNd
ñ
ú
(Æ+{pa°dONLNd
ô
Æ
(
ò)'rse section handle out of message buffe°dONLNd
¿

ò
(
§)Ír}°dONLNd
ƒ
*ú
6®(
3úMy°dONLNd
Δ
*®
6
>)GetSectionHandleFromEvent°dONLNd
‚
8Æ
D
n+ := AEGetParamPtr( theAppleEvent,°dONLNd
8
Ü
D
Ê)ÿ{event to parse}°dONLNd'
F

R
z(
O
keyDirectObject,°dONLNd=
F
Ü
R
ò)l{lo°dONLNd@
F
ò
R
Ú)ok for direct }°dONLNd^
T
Ü
`
∞(
]
Ü{ objec°dONLNde
T
∞
`
º)*t}°dONLNdp
b

n
n(
k
typeSectionH, °dONLNdÑ
b
Ü
n
ò)l{wa°dONLNdá
b
ò
n
)nt a SectionHandle}°dONLNd£
p

|
\(
y
ignoreType,°dONLNd¥
p
Ü
|
ò)l{ig°dONLNd∑
p
ò
|)nore type it could }°dONLNd⁄
~
Ü
ä
û(
á
Ü{ ge°dONLNdfi
~
û
ä
™)t}°dONLNdÈ
å

ò
\(
ï
@sectionH, °dONLNd˙
å
Ü
ò
ò)l{pu°dONLNd˝
å
ò
ò
˛)t SectionHandle }°dONLNd
ö
Ü
¶
§(
£
Ü{ her°dONLNd"
ö
§
¶
∞)e}°dONLNd-
®

¥
z(
±
SizeOf(sectionH)°dONLNd=
®
z
¥
Ä)`
,°dONLNdD
®
Ü
¥
å)
{°dONLNdE
®
å
¥
)size of storage for }°dONLNdi
∂
Ü
¬
Ê(
ø
Ü{ SectionHandle}°dONLNdÇ
ƒ

–
b(
Õ
ignoreSize);°dONLNdî
ƒ
Ü
–
ò)l{ig°dONLNdó
ƒ
ò
–
˛)nore storage it }°dONLNd∑
“
Ü
fi
§(
€
Ü{ use°dONLNdº
“
§
fi
∞)d}°dONLNdø
‡ä
ÏÆ(
ÈäEND; {°dONLNd≈
‡Æ
Ï∫)$My°dONLNd«
‡∫
Ï
V)GetSectionHandleFromEvent}°dONLNd·
‡
V
Ï
\)ú
 .
°dONLNd„
¯ä
C(
ä*In addition to the Section Read, Section WÉ °dONLNd
¯
C
fl)π%rite, Section Cancel, and Section Scr-`°dONLNd2
¯
‡)ùoll events, °dONLNd>äˇ(äyour application can also r÷¿°dONLNdYˇ
H)uespond to the Cr3`°dONLNdi
I
À)Jeate Publisher event. For mor¿°dONLNdÜ
À    )Çe information °dONLNdîä
´(äBon this event, as well as additional information on how to handle †°dONLNd÷
¨(
¨Apple events, see the °dONLNdÏä+ı((ächapter “Responding to ˛ °dONLNdı+
q)kApple Events” in this book. 

PHW4QHW RäR

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd!AäP
T(Lä Creating the Section Record and 1¿°dONLNdAA
TP
°) Alias Recordˇˇˇˇˇˇ€r)∫
2
°dONLNdOWäcê(`ä
Y@Ä°dONLNdPWêc„)our application is r—°dONLNddW„c
+)Sesponsible for crp‡°dONLNduW
,c
v)Ieating a section rÛ@°dONLNdáW
vc
à)Jecorg†°dONLNdãW
âc
Ã)d and an alias r†°dONLNdõW
Õc
fl)Decorâ°dONLNdüW
flc)d for each °dONLNd™däp
ê(mä9publisher and subscriber section within an open document.°dONLNd‰väǬ*The section rÈ@°dONLNdÒv¬Ç‘)8ecor]†°dONLNdıv’Ç˝)    d identifi–°dONLNdˇv˝Ç
Ÿ)(3es each section as a publisher or subscriber and prg‡°dONLNd2v
ڂ
˘)›ovides °dONLNd9Éäè©(åäidentifiV†°dONLNdAÉ™è
I) &cation for each section. The section r—Ä°dONLNdgÉ
Iè
[)üecorE‡°dONLNdkÉ
\è)'d does not contain the data within the °dONLNdíêäú
^(ôä5section; it describes the attributes of the section. †°dONLNd«ê
_ú
e)’
YΔ °dONLNd»ê
dú
Ã)our application must pr燰dONLNdflê
Õú)iovide its own °dONLNdÌùä©
©(¶äCmethod for associating the data within a section with its section rk@°dONLNd0ù
©©
ª(¶
©ecorfl†°dONLNd4ù
ª©
Δ)d. Õ¿°dONLNd7ù
Δ©
Ã)
Yé@°dONLNd8ù
é)our application °dONLNdH™ä∂´(≥ä    is also r@°dONLNdQ™¨∂
o)".esponsible for saving the data in the section.ˇ`^@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-16    )BUsing the Edition Manager4^*¿
¯
.°dONLNd\lhÄ(elThe ,
Courier°dONLNd\Ähû)alias°dONLNd    \ûhß) fi°dONLNd\ßh˙)    eld of the section rR`°dONLNd \˙h
)Secor$¿°dONLNd$\
h
ù)"d contains a handle to its alias r˜ °dONLNdF\
úh
Æ)êecor…Ä°dONLNdJ\
Æh
Á)d. The alias .
°dONLNdWiluo(rl
rE°dONLNdXipuÇ)ecorπ`°dONLNd\iÇuü)d is a r?Ä°dONLNddi†u∞)eferΆ°dONLNdhi∞u
6) ence to the edition container frùÄ°dONLNdài
7u
”)á"om the document that contains the °dONLNd™vlǯ(l!publisher or subscriber section. Á °dONLNdÀv¯Ç˛)å
Y߆°dONLNdÃv˛Ç
Ü)ou should be familiar with the ™`°dONLNdÎv
ÜÇ
Δ)àAlias ManagerN¿°dONLNd¯v
Ȃ
—)B’s °dONLNd˚Élèª(ålconventions for cr@°dONLNd
ɺèÙ)Peating alias r?‡°dONLNd
ÉÙè
)8ecor¥@°dONLNd
É
è
_)ds and identifying fi|†°dONLNd
4É
`è
€)Zles, folders, and volumes to °dONLNd
Qêlúé(ôllocate fiʇ°dONLNd
Zêéú
5)"&les that have been moved, copied, or rë`°dONLNd
Äê
6ú
K)®estor‡°dONLNd
Öê
Lú
`)ed frì °dONLNd
äê
`ú
ì)
om backup.l‡°dONLNd
îê
îú
Ï)4 For information on °dONLNd
®ùl©|(¶lthe °dONLNd
¨ù|©º)Alias Manager®†°dONLNd
πùº©—)@, see ¯‡°dONLNd
øù—©
1)Inside Macintosh: Files.°dONLNd
ÿØlª
w(∏l:When a user saves a document, your application should stor釰dONLNdØ
wª
∞(∏
we all section rV¿°dONLNd!Ø
±ª
√):ecorÀ °dONLNd%Ø
û
„)ds and °dONLNd,ºl»Ü(≈lalias r“¿°dONLNd3ºÜ»ò)ecorG °dONLNd7ºô»˚)ds in the document’s r∫@°dONLNdMº˚»
)besourÄ°dONLNdRº
»
K)ce fork. CorrK†°dONLNd_º
K»
°)7esponding section r≠`°dONLNdrº
°»
≥)Vecor!¿°dONLNdvº
¥»
Í)ds and alias °dONLNdÉ…l’o(“l
rE°dONLNdÑ…p’Ç)ecorπ`°dONLNdà…Ç’ı)ds should have the same rflÄ°dONLNd°…ı’
)sesour'¿°dONLNd¶…
’
')ce ID.°dONLNd≠€lÁÑ(‰lFigurR¿°dONLNd≤€ÑÁò)e 2-9@°dONLNd∑€òÁ
ñ)7 shows a document containing a publisher and subscriber≤ °dONLNdÓ€
ñÁ
æ)˛
, and the °dONLNd¯ËlÙ}(Òlcorr`°dONLNd¸Ë~Ù‘)esponding section r °dONLNdË‘ÙÊ)VecorÛÄ°dONLNdËÊÙ
 )ds and alias rå °dONLNd!Ë
!Ù
3);ecorÄ°dONLNd%Ë
4Ù
>)dsY@°dONLNd'Ë
>Ù
@)

.


*
'
¯4
*
'
¯"
*]

ˇ·ˇ‚7^
    °dONLNd*
l
ñ(
l
Figure 2-9°dONLNd5
Æ
¥)B
A0°dONLNd6
¥

∞)? document with a publisher and subscriber and its resource fork


&*Æ
¯4
%(
&)ò@@
˜@
˜
&)
f ¡¡? ˇ¸˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙ò@@Ä
˜@Ä
˜
f)
¶ ? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙ò@Ä¿
˜Ä¿
˜
¶)
Ê ? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙ò@¿

˜¿

˜
Ê)& ? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙ò@

@
˜

@
˜&)f ? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙ò@
@
Ä
˜
@
Ä
˜f)¶ ? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙ò@
Ä
¿
˜
Ä
¿
˜¶)Ê ? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙? ˇ˛˙ ˇ˛˙¡¡¡¡¡¡¡¡¡¡¡¡¡¡
|√»DH
$Ä…@Ñ(Ä…pÑ(Ä…
êÑ'»
Å    ê4B»
ÖÑÑ»

˚‡?»¡¡¡¡/|¿
Ä
ĸ
˛L˛ÄIJ
aÄ˚
ÄÚ,D˛@Ä˚˛¿˛


˝ ˙(ÄÚ.@˛@(
˝
à˛Ä˛

˝
@@˚
 
Ò40pŒ÷Ñ@(8Δ¥ƒ{åìÀCÕç÷ÅØ
—«fô¬–5·AÁŒkL˜i`Ú40ë¥SÄHE"õZ)ñçÅ%öZkE4Q)ì1-`H¶ÉIjQ)íhH±@Ú40Å$¢a|"Ü\Q§âÇ*#rJD¢%".@âHÇDq!Q pP°ÄÚ40ÇY, Ñ/äid‡Z…    ¬R≠§§ÑÎ^%*”4J–ÄùkƒíÑ¢ñ&ÄëB†Ú40
√πÙ<
ûqè§úíèÖü?$tR,9ÒƒqÄjEáúw˙péB@Ú˛DÒËÄ˛DÒÈÔ˛8ÒÈÔ¡|…D
å…@Ä
î…pSÃÁÇîkΔé-Õë¶ôǧëI4÷ÕÇ$í…ë$‰Õܢ&%Ñâ:”ôÕ
˘o9…∏‘ç8ËÕ˜DØDØ8á%Δp
É¡Ä8˝¿@˛¿‰    B 
c˝˝0˝
Ä›#§@e
 ˛ ĸ„'#§,êOä •c{úuÄ'∏¥kœ#1ºŒx ߶i„aº‹Â'#î‘êE'4–©$ñ)"ñÄ"ìXë$¶JIë( "⁄⁄(¶íI¢PÂ'#ò†äD‡≤EQBDÄEë(ƒÑI!P BííQEIB†Â'#
    ¿ãLfl
"O9ZE)E§!:IiúÚbX#E'&ïi4ÚD∞Â'#
à‰Å“w,·Æ4Œí9…È#†’ñNcSúê9%$˙N√Sπ Âò@
¿
Ú
˜
¿
Ú
˜Ê) Ú˛
÷Ó
÷Ó
8÷¡
@Ä0˛`«ÿÅ˚˛!(¢¸ÿ1˛ ˛@L≤˛ÿSÖé?såì(Ä5·Aã,«‹‡Q    ‡⁄îIQe$Ññ”@H¶ÄQD
(±I!¶¥ê⁄
¸_ÑaJ"•ÄâHÄQD0¢àÇ'9⁄$Ç¢õI…|ùk¿RHQJ“B¯A ⁄#ÚNé≥êjEáå0étìÅg:¿⁄˝˚¸¸Ÿ˝ı¸Ÿ˝ı¸Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡t¸Œ0ฌP
˛@ŒQÁêÇ
⁄gö‚hÒÄ–êíSB-¢JM0R@–˘cÇ)$TN §œ
    $¥4Rd•ê@¥¿–>À#Å√íK>éB#–˝Õ˝ ˝ ¡x
‡`A‡
–Õ$ê˛@ê ÕB
˛Å0 ÕB
O<nÅ¿ËπœB
    •“Å     3IœÑ (àÇ0#Öœà"-% ”ƒœ
á¡“I˘¬Cќٜٜò@@
˜@
˜
&)
f 
¡¡…30˙…˙  ˙…˙…˙…˙  ˙…˙  ˙…˙…˙…˙  ˙˘¯ˇ˛‹˙ ˙@¯‹˙˘@¯
Ä›˙˘@¯
¿›˙˘@    0#Dz
`›˙ ˙@}ßπ˚ÿ0›˙˘@}øπ}˚ÿ›˙ ˙@Ä˚
›˙˘@¯
›˙˘@¯
›˙˘@     @@

Äfi˙ ˙@?èı˝∂˜˘¬¿fi˙˘@ˇèı˝∂˜˘¬`fi˙ ˙@˘Ä0fi˙˘@¯fi˙˘@˘ 8@0Äfi˙˘@•oó˛ˇÓfi˙ ˙@Ø˘ÔΩ˛ˇÓfi˙˘
@˛˝
Äfl˙ ˙@¯¿fl˙˘@



Äɡˇ‡fl˙˘@∑˝üœ˜∑ü∑Ä`fl˙˘@∑˝üœ˜∑ü∑Ä`fl˙ ˙@ ¿˛0¸`fl˙˘@ı`fl˙ ˙    @√"B˛`fl˙˘    @˚Ûıˇ€Û˜€˛`fl˙˘    @˚Ûıˇ€Û˜€˛`fl˙˘@˝†¿˛`fl˙ ˙@ı`fl˙˘@î˜`fl˙ ˙@◊Ωflˇx˚`fl˙˘@◊Ωflˇx˚`fl˙˘@˝˙`fl˙˘@ı`fl˙ ˙@ı`fl˙˘@ı
`¯ˇÄÍ˙ ˙
@`ˆ
`b¯"‡Í˙˘
A¿ˆ
`@¯0Í˙˘CË(¸`˜DXÍ˙˘Bkonˇfi¿˝
`H˜àÍ˙ ˙B˚onÔfi¿˝
`¯ˇÍ˙˘Bı`¯

îÍ˙ ˙Bı`˜¶Í˙˘Bı`˜ÇÍ˙˘B ä‡ PÅ`˜ΔÍ˙˘B˛fl˚˚ü(ØØ^˜Ä`˜äÍ˙ ˙B˛fl˚˚üÔØ^˜Ä`˜ÇÍ˙˘B˙˝`˜íÍ˙ò@@Ä
˜@Ä
˜
f)
¶ 
 ˙Bı`˜¢Í˙!
·
ÄB¿
 
`˜ÇÍ˙!
ÄB˚æˆˇ?›ª˘˝`˜ΔÍ˙!
”Δm„`B˚æˆˇ?›ª˘˝`˜äÍ˙ ≥/ôó¡ˇ˛˙
 IJ`˜ÇÍ˙3-âî@Bı`˜íÍ˙! 
œΔy„¿BÄÑ ÄÄ``˜¢Í˙˘B˛ˇ∑üo˛ÔªÔ¯`˜ÇÍ˙˘B˛ˇ∑üo˛ÔªÔ`˜ΔÍ˙˘B˜`˜äÍ˙ ˙Bı`˜ÇÍ˙˘    BP    0≈˛`˜íÍ˙ ˙B‹ˇª˚Ûæ1_¿`˜¢Í˙˘B‹ˇª˚Ûæfl¿`˜ÇÍ˙˘BÄ¿˛Ä`˜ΔÍ˙˘Bı`˜äÍ˙ ˙B†˙`˜ÇÍ˙˘C̸ˇø˙`˜íÍ˙ ˙AüÌ|ˇø˙`˜¢Í˙˘@‡

˘`˜ÇÍ˙˘@ı`˜ΔÍ˙˘@ı`˜äÍ˙ ˙@ı`˜ÇÍ˙˘@ı`˜íÍ˙ ˙@ı`˜¢Í˙˘@ı`˜ÇÍ˙˘@ı`˜ΔÍ˙˘@ı`˜äÍ˙ ˙
@‡ˆ`˜ÇÍ˙˘
CĈ`˜íÍ˙ ˙BC˛Â ¸`˜¢Í˙˘    B7Òäü«ø˚IJ`˜ÇÍ˙˘    B/Û˛ˇ«ø˚èˇ˛`˜ΔÍ˙˘
B˚‡`˜äÍ˙ ˙B˙¸`˜ÇÍ˙˘B@Ä@0˜Ä`˜íÍ˙ ˙B7{˛fl˝Ä>ˇ‡¯¢Í˙˘B7{˛fl˝Ä˛õfi8¯ÇÍ˙˘B˚uœÿ0zDN¯ΔÍ˙PÄB˚ÄÒ¸ àä¯äÍ˙"     @ÄB0å˛
˛¿Ñ¯ÇÍ˙"    ûV„`B;Ω˚ôJˇè‡«ˇ—¯íÍ˙# ô_ó¿B;Ω˚õ˛ÖˇÒ¸¿`cĢ¢Í˙ ô]îAˇ˛˚Hˇ˛?≥`0ĢÇÍ˙!~Vì¿B¸    
ˇœ„Ä`ĢΔÍ˙˘B@¯$ˇÒ˚¿`ĢäÍ˙ ˙B7˝Δ+ˆˇ˛ˇ¿`ĢÇÍ˙˘B7˝œ˚ˆ˛ˇ˝`ĢíÍ˙ ˙B˘ˇÓ`Ģ¢Í˙˘B˘ˇf`ĢÇÍ˙˘B4IJÚ`ĢΔÍ˙˘B€¸˜ü∑ÿÍ`ĢäÍ˙ ˙B€¸˜ü∑ÿ˛
`ĢÇÍ˙˘Bı`ĢíÍ˙ ˙B˜`Ģ¢Í˙˘B  !
ˇ˛`ĢÇÍ˙˘B??øÌŸE¿˝`ĢΔÍ˙˘C??øÌ€ˇ¿˝`ĢäÍ˙ ˙
A‡ˆ`ĢÇÍ˙˘@ı`ĢíÍ˙ ˙@ı`Ģ¢Í˙˘@ı`ĢÇÍ˙˘@ı`ĢΔÍ˙˘@ı`ĢäÍ˙ò@Ä¿
˜Ä¿
˜
¶)
Ê 
 ˙@ı`ĢÇÍ˙˘@ı`ĢíÍ˙ ˙ıˇ‡Ģ¢Í˙˘?ıˇ‡ĢÇÍ˙Î
ĢΔÍ˙Î
ĢäÍ˙ Ï
ĢÇÍ˙Î
ĢíÍ˙ Ï
Ģ¢Í˙Î
ĢÇÍ˙Î
ĢΔÍ˙Î
ĢäÍ˙ Ï
ĢÇÍ˙Î
ĢíÍ˙ Ï
Ģ¢Í˙Î
ĢÇÍ˙Î
ĢΔÍ˙Î
ĢäÍ˙ Ï
ĢÇÍ˙Î
ĢíÍ˙ Ùp˛Ģ¢Í˙ÛH˛Ä˙ÉÄÎ˙Û    Iôìôé⁄¿Ä˙EÄÎ˙Û    s˛S'≈3Ä˙

ãÍ˙ Ù    J6S"2ÄĢΔÍ˙Û    IŸèƒ“@Ģ|Í˙ Ï
Ģ8Í˙Î
Ä·˙Î
Ä·˙Î
Ä·˙ ı
˘ˇˡ¯˙˙Ù
˘
ÄÈ˙˙ ı
˘
ÄÈ˙˙Ù
˘
ÄÈ˙˙Ù
˘
ÄÈ˙˙Ù
˘
ÄÈ˙˙ ı
˘
ÄÈ˙˙Ù
˘
Ä˝
‡˝ ı˙˙ ı
˘
Ä˝˝ ı˙˙Ù
˘
Ä˝
Ãnnff‡ı˙˙Ù
˘
ĸæñô˘ï ı˙˙Ù
˘
Ä˝0Üôàï ı˙˙  ı
˘
Ä˝
Œviwd‡ı˙˙Ù
˘
ÄÈ˙˙ ı
˘
ÄÈ˙˙Ù
˘
ÄÈ˙˙Ù
˘
ÄÈ˙˙Ù
˘
Ä˝˘ˇ¿ˆ˙˙ ı
˘
Ä˝Ä˙`ˆ˙˙Ù
˘
Ä˝Ä˙`ˆ˙˙ ı
˘
Ä˝Ä˙`ˆ˙˙Ù
˘
Ä˝Ä˙`ˆ˙˙Ù
˘
Ä˝ÄÄ˝`ˆ˙˙Ù
˘
Ä˝Ä˙`ˆ˙˙! ı
˘
Ä˝Å~ú‰˛`ˆ˙˙Ù
˘
ĽĮ–¢ê˛`ˆ˙˙! ı
˘
Ä˝ÄØâê˛`ˆ˙˙Ù
˘
ĽĮB¢ê˛`ˆ˙˙Ù
˘
Ä˝ÄG‹úî˛`ˆ˙˙Ù
˘
Ä˝Ä˙`ˆ˙˙ ı
˘
Ä˝Ä˙`ˆ˙˙Ù
˘
Ä˝Ä˙`ˆ˙˙ ı
˘
Ä˝Å
¸`ˆ˙˙Ù
˘
Ä˝Å
¸`ˆ˙˙ò@¿

˜¿

˜
Ê)& 
Ù
˘
Ä˝Å+è@˝`ˆ˙˙Ù
˘
Ä˝ÅJQ¸`ˆ˙˙ ı
˘
Ä˝ÅäQ¸`ˆ˙˙Ù
˘
Ä˝ÅJQ¸`ˆ˙˙  ı
˘
Ä˝Å*O@˝`ˆ˙˙Ù
˘
Ä˝Ä˙`ˆ˙˙Ù
˘
Ä˝Ä˙`ˆ˙˙Ù
˘
Ä˝Ä˙`ˆ˙˙ ı
˘
Ä˝Ä
¸`ˆ˙˙Ù
˘
Ä˝Ä
¸`ˆ˙˙  ı
˘
Ä˝ÄÌœ9˝`ˆ˙˙Ù
˘
Ä˝Äí1D˝`ˆ˙˙Ù
˘
Ä˝Äí1|˝`ˆ˙˙Ù
˘
Ä˝Äí1@˝`ˆ˙˙  ı
˘
Ä˝Äìœ=˝`ˆ˙˙Ù
˘
Ä˝Ä˙`ˆ˙˙ ı
˘
Ä˝Ä˙`ˆ˙˙Ù
˘
Ä˝Ä˙`ˆ˙˙Ù
˘
Ä˝Ä.IJ`ˆ˙˙Ù
˘
Ä˝Ä)IJ`ˆ˙˙! ı
˘
Ä˝ÄÌËπ¯Ä`ˆ˙˙Ù
˘
Ä˝Äí(у˛`ˆ˙˙! ı
˘
Ä˝Äí(º¸˛`ˆ˙˙Ù
˘
Ä˝Äí)$¿˛`ˆ˙˙Ù
˘
Ä˝ÄìÓ¸Ä`ˆ˙˙Ù
˘
Ä˝Ä˙`ˆ˙˙ ı
˘
Ä˝Ä˙`ˆ˙˙Ù
˘
Ò‡˝Ä˙`ˆ˙˙! ı
˘
b`˝ÄÄ¿`ˆ˙˙Ù
˘
0¿˝Ä `ˆ˙˙Ù
˘
Ä˝ÄÁ7úÂ`ˆ˙˙Ù
˘¸Å ¢ï`ˆ˙˙  ı
˘¸Äœ¬¢ï`ˆ˙˙Ù
ÛÄ(J¢ï `ˆ˙˙ ı
ÛÅ«≥úï¬`ˆ˙˙Ù
ÛÄ˙`ˆ˙˙Ù
ÛÄ˙`ˆ˙˙Ù
ÛÄ˙`ˆ˙˙ ı
ÛÄX¸`ˆ˙˙!Ù
¸0˛
ħ¸`ˆ˙˙) ı
¸ ˛
Å›¬sê˛`˙Á˛˙˙'Ù
¸csp337Å"¿ä@˛`˙˙˙+Ù
¸Ù¥»'éÅ>¬ä@˛`˙
˛ˇ¯˙+Ù
¸Ñ4»$D©Å §ä@˛`˙
˛ˇ¯˙- ı
¸s≥H#ª'ÅòrP˛`˙
˛ˇ¯˙Ù
ÛÄ˙`˙

¿8˙ ı
ÛÄ˙`¯
œy‡8˙Ù
ÛÄ˙`˙

œ{8˙"Ù
Û
Ä
˚`˛#˝@
Œ˜88˙(Ù
˝˙ˇ¸Ä˚cÄR˝@8
Œˆ8˙- ı
˝˙Å „ê˝c¯Sqç埿?Åœv∏˙*Ù
˝˙Ä*¸cˇsÀ”2@?Òœw?∏˙+ ı
˝˙ÅÍÛ˚ˇãkJ2@ˇˇÒœ∏˙+Ù
˝˙Å*êÄ˝c¯ã9⌗¿?Åœa‡∏˙(Ù
˝˝ÄÍw˝c¿¯8
¿`∏˙$Ù
˝˙Ä˙`˙

¡¯`∏˙( ı
˝
ªÙÁ Ä˙`¯

√ú∏˙&Ù
˝
FÖÄÄ˙`¯

«∏˙* ı
˝
~eÄÄ˙`˙

«ˇ8˙(Ù
˝
BÄÄ˙`˙

«ˇ8˙(Ù
˝
>‰‰†Ä˙`˙

¿8˙$Ù
˝˙Ä˙`˙
˛ˇ¯˙& ı
˝˙Ä˙`˙
˛ˇ¯˙$Ù
˝˙Ä˙`˙¸˛
˛ˇ¯˙ò@

@
˜

@
˜&)f 
! ı
˝@˝Ä˙`ˆ˙˙Ù
˝˝Ä˙`ˆ˙˙Ù
˝    \z˝Ä˙`ˆ˙˙#Ù
˝
Rà˝Ä˙`ˆ
Ê=˙) ı
˝Rà˝ÄA‡˛`ˆ    A ˙'Ù
˝
Rà˝ÄA˛`ˆ
–9|˙) ı
˝    Rz˝ÄÈy˛`ˆ∞≤˙$Ù
˝˙Å    E·D˛`ˆ)E≤˙$Ù
˝˙Ä…ED˛`ˆ
Δ9¨˙ Ù
˝˙Ä)E    D˛`ˆ˙˙% ı
˝˝Å«yG˛`ˆ˙˙Ù
˝˝Ä˙`ˆ˙˙" ı
˝ny»˛Ä˙`ˆ˙˙ Ù
˝ëä ˛Ä˙`ˆ˙˙$Ù
˝ëã‡˛
Ä
0``ˆ˙˙#Ù
˝ëä˝
Ä
H@`ˆ˙˙& ı
˝ûy˲
ÄÁ/¡ÃÁ9`ˆ˙˙ Ù
˝˙
Äò©:2h§`ˆ˙˙" ı
˝˙
Äüëh§`ˆ˙˙ Ù
˝˙
Äò)Üh§`ˆ˙˙$Ù
˝
p˛
ÄóÌ˘Ïg%`ˆ˙˙ Ù
˝
H˛Ä˙`ˆ˙˙" ı
˝
oEœƒÄ˙`ˆ˙˙ Ù
˝
ëD& Ä˙`ˆ˙˙& ı
˝ëEÁ‡Ä
úÄ`ˆ˙˙$Ù
˝ëI&˛
Ä
íÄ`ˆ˙˙$Ù
˝üpÁ‰Ä«;Óíú…@`ˆ˙˙ Ù
˝˙
Å(•ëû£*`ˆ˙˙" ı
˝˙
Å•ëë£`ˆ˙˙ Ù
˝˙
Å(•ëë£*`ˆ˙˙& ı
˝.Ä«%éûú…@`ˆ˙˙ Ù
˝
)Ä˙`ˆ˙˙ Ù
˝
9ºÁ(êÄ˙`ˆ˙˙ Ù
˝
FU®ÄÄ˙`ˆ˙˙$ ı
˝~®ÄÄb¸`ˆ˙˙"Ù
˝
BU©Ä≤¸`ˆ˙˙& ı
˝=ú‰ÆÅ›Úì¥˛`ˆ˙˙ Ù
˝˙Å"™íH˛`ˆ˙˙ Ù
˝˙Å>™íH˛`ˆ˙˙ Ù
˝˙Å ¶íH˛`ˆ˙˙% ı
˝¿˝Å¢rL˛`ˆ˙˙Ù
˝ ˝Ä˙`ˆ˙˙" ı
˝
ÓúÄÄ˙`ˆ˙˙$Ù
˝    R˛Ä˙`˙Á˛˙˙#Ù
˝    ˆR˛
˘ˇ‡˙˙˙(Ù
˝    $R˛˙ˇ‡˙
˛ˇ¯˙& ı
˝Ù√íĈ˙
˛ˇ¯˙ Ù
˝˙ˆ˙
˛ˇ¯˙" ı
˝˙ˆ˙

¿8˙Ù
˝˙ˆ¯
œy‡8˙"Ù
˝P¸ˆ˙

œ{8˙(Ù
˝@¸¯˛
"IJ@0
Œ˜88˙+ ı
˝WIJ¯‡R˝@>
Œˆ8˙)Ù
˝
P†˝¯˛RÒåÃÕ¿?¡œv∏˙& ı
˝Wò
Úˇrõ…Û*@ˇˇÒœw?∏˙)Ù
˝    TÑ˝¯¸äÎI*@?¡œ∏˙*Ù
˝S∏IJ¯‡äπàÓ…¿>
œa‡∏˙ Ù
˝˙¯¯0
¿`∏˙" ı
˝˙ˆ˙

¡¯`∏˙Ù
˝˙Ó

√ú∏˙ ı
˝˙Ó

«∏˙ Ù
˝˙ˆ˙

«ˇ8˙ Ù
˝˙ˆ˙

«ˇ8˙ Ù
˝˙ˆ˙

¿8˙ò@
@
Ä
˜
@
Ä
˜f)¶ 
" ı
˝˙ˆ˙
˛ˇ¯˙ Ù
˝˙ˆ˙
˛ˇ¯˙" ı
˝˙ˆ˙¸˛
˛ˇ¯˙Ù
˝˙Ï˙˙Ù
˝˙Ï˙˙Ù
˝˙Ï˙˙  ı
˝ Ï ˙Ù
˝Ä Ï˛ ˙  ı
˝K»Û¯Ïg¢Ó}Ä˙Ù
˝J/
 ÏıRì3˙Ù
˝J(z ÏÖRù3˙Ù
˝
J(J ÏuRó=˙ ı
˝;»:8Ï˙˙Ù
˝˙Ï˙˙ ı
˝˙Ï˙˙Ù
˝˙Ï˙˙Ù
˝    ÄÏ˙˙Ù
˝
@Ï˙˙ ı
˝9~g9»Ï˙˙Ù
˝≈I—ìE Ï˙˙ ı
˝¸à?ÉE Ï˙˙Ù
˝¡L0ìE Ï˙˙Ù
˝øoœc9(Ï˙˙Ù
˝˙Ï˙˙ ı
˝˙Ï˙˙Ù
˝˙Ï˙˙ ı
˝‰@Ï˙˙Ù
˝î@Ï˙˙Ù
˝9fltîÊJÏ˙˙Ù
˝    E,åıPÏ˙˙ ı
˝E,åç`Ï˙˙Ù
˝    E,åçPÏ˙˙ ı
˝9,tÙÊJÏ˙˙Ù
˝˙Ï˙˙Ù
˝˙Ï˙˙Ù
˝˙Ï˙˙ ı
˝˝Ï˙˙Ù
˝ê˝Ï˙˙ ı
˝Ôîù†Ï˙˙Ù
˝    Tí@Ï˙˙Ù
˝    ıTí@Ï˙˙Ù
˝    4í@Ï˙˙ ı
˝ıí`Ï˙˙Ù
˝˙Ï˙˙ ı
˝˙Ï˙˙Ù
˝˙Ï˙˙Ù
˝˙ˇ˛Ï˙˙Ù
˝˙ˇ˛Ï˙˙ ı
fl˙˙Ù
fl˙˙ ı
fl˙˙Ù
fl˙˙Ù
fl˙˙Ù
fl˙˙ ı
fl˙˙Ù
flˇ¯˙˙  ˙…˙…˙…˙  ˙…˙  ˙…˙ò@
Ä
¿
˜
Ä
¿
˜¶)Ê 
…˙…˙  ˙…˙…32˙…Ã˙¡¡¡¡¡¡¡¡¡¡¡¡¡¡
|√»DH
$Ä…@Ñ(Ä…pÑ(Ä…
êÑ'»
Å    ê4B»
ÖÑÑ»

˚‡?»¡¡¡¡/|¿
Ä
ĸ
˛L˛ÄIJ
aÄ˚
ÄÚ,D˛@Ä˚˛¿˛


˝ ˙(ÄÚ.@˛@(
˝
à˛Ä˛

˝
@@˚
 
Ò40pŒ÷Ñ@(8Δ¥ƒ{åìÀCÕç÷ÅØ
—«fô¬–5·AÁŒkL˜i`Ú40ë¥SÄHE"õZ)ñçÅ%öZkE4Q)ì1-`H¶ÉIjQ)íhH±@Ú40Å$¢a|"Ü\Q§âÇ*#rJD¢%".@âHÇDq!Q pP°ÄÚ40ÇY, Ñ/äid‡Z…    ¬R≠§§ÑÎ^%*”4J–ÄùkƒíÑ¢ñ&ÄëB†Ú40
√πÙ<
ûqè§úíèÖü?$tR,9ÒƒqÄjEáúw˙péB@Ú˛DÒËÄ˛DÒÈÔ˛8ÒÈÔ¡|…D
å…@Ä
î…pSÃÁÇîkΔé-Õë¶ôǧëI4÷ÕÇ$í…ë$‰Õܢ&%Ñâ:”ôÕ
˘o9…∏‘ç8ËÕ˜DØDØ8á%Δp
É¡Ä8˝¿@˛¿‰    B 
c˝˝0˝
Ä›#§@e
 ˛ ĸ„'#§,êOä •c{úuÄ'∏¥kœ#1ºŒx ߶i„aº‹Â'#î‘êE'4–©$ñ)"ñÄ"ìXë$¶JIë( "⁄⁄(¶íI¢PÂ'#ò†äD‡≤EQBDÄEë(ƒÑI!P BííQEIB†Â'#
    ¿ãLfl
"O9ZE)E§!:IiúÚbX#E'&ïi4ÚD∞Â'#
à‰Å“w,·Æ4Œí9…È#†’ñNcSúê9%$˙N√Sπ Âò@
¿
Ú
˜
¿
Ú
˜Ê) 
Ú˛
÷Ó
÷Ó
8÷¡
@Ä0˛`«ÿÅ˚˛!(¢¸ÿ1˛ ˛@L≤˛ÿSÖé?såì(Ä5·Aã,«‹‡Q    ‡⁄îIQe$Ññ”@H¶ÄQD
(±I!¶¥ê⁄
¸_ÑaJ"•ÄâHÄQD0¢àÇ'9⁄$Ç¢õI…|ùk¿RHQJ“B¯A ⁄#ÚNé≥êjEáå0étìÅg:¿⁄˝˚¸¸Ÿ˝ı¸Ÿ˝ı¸Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡t¸Œ0ฌP
˛@ŒQÁêÇ
⁄gö‚hÒÄ–êíSB-¢JM0R@–˘cÇ)$TN §œ
    $¥4Rd•ê@¥¿–>À#Å√íK>éB#–˝Õ˝ ˝ ¡x
‡`A‡
–Õ$ê˛@ê ÕB
˛Å0 ÕB
O<nÅ¿ËπœB
    •“Å     3IœÑ (àÇ0#Öœà"-% ”ƒœ
á¡“I˘¬Cќٜٜò@@
˜@
˜)X Ù0œ¡xÄ˝
À9Ä˝ÑÄÃ
Q
ÄÃ
Q4£y⁄Äà    Qîƒí,

À    ¢(Dàî(
À
≥K)    ‰P
ÄÃ    
‚}…£ê/À¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜X)ò ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜ò)ÿ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜ÿ) ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜)X ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜X)ò ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ò)ÿ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜ÿ)
 ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜)X 
Ù0œ¡xÄ˝
À9Ä˝ÑÄÃ
Q
ÄÃ
Q4£y⁄Äà    Qîƒí,

À    ¢(Dàî(
À
≥K)    ‰P
ÄÃ    
‚}…£ê/À¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜X)ò 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜ò)ÿ 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜ÿ) 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜)X 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜X)ò 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ò)ÿ 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜ÿ)
 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ46@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-17
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähë(eä
A∫†°dONLNd
\ëh∏)
 section rh °dONLNd\πhÀ)(ecor‹Ä°dONLNd\Àh)Ld contains information to identify the data contained within a section as a °dONLNd[iäu˜(räpublisher or a subscribern‡°dONLNdti˜u
F)m, a time stamp to r    †°dONLNdái
Gu
Y)Pecor~°dONLNdãi
Yu
°)d the last modifiπ@°dONLNdúi
°u
˝)Hcation of the section, .°dONLNd≥väÇù(äand °dONLNd∑vùÇfl)unique identifi°dONLNdΔvflÇ
\)Bcation for each section. The ,
Courier°dONLNd„v
\Ç
™)}SectionRecord°dONLNdv
™Ç
Ì)N data type defi°dONLNdˇv
ÌÇ)Cnes the .
°dONLNd
ÉäèØ(åä    section r≠Ä°dONLNd
ÉØè¡)%ecor!‡°dONLNd
ɬè )d..°dONLNd
öä¶ê(£ä
T°dONLNd
öê¶
)YPE SectionRecord = °dONLNd
.®ú¥¿+RECORD°dONLNd
7∂Ƭfi+version:°dONLNd
D∂
¬
J)ZSignedByte;°dONLNd
T∂
b¬
»)Z{always 1 in 7.0}°dONLNd
hƒÆ–Ã(ÕÆkind:°dONLNd
rƒ
–
P)ZSectionType;°dONLNd
Ƀ
b–
¯)Z{publisher or subscriber}°dONLNd
ü“ÆfiÃ(€Æmode:°dONLNd
©“
fi
J)ZUpdateMode;°dONLNd
π“
bfi
‡)Z{automatic or manual}°dONLNd
—‡ÆÏÿ(ÈÆmdDate:°dONLNd
›‡
Ï
D)Z
TimeStamp;°dONLNd
χ
bÏ
¯)Z{last change in document}°dONLNdÓÆ˙Í(˜Æ
sectionID:°dONLNdÓ
˙
8)ZLongInt;°dONLNd$Ó
b˙
Ú)Z{application-specific, }°dONLNdI¸
b

Ê*{ unique per document}°dONLNdb

Æ
ÿ(
ÆrefCon:°dONLNdn




8)ZLongInt;°dONLNd{


b

Ê)Z{application-specific}°dONLNdî
Æ
$“(
!Æalias:°dONLNdü


$
P)ZAliasHandle;°dONLNd∞

b
$
Ú)Z{handle to alias record}°dONLNdÃ
4Æ
@(
=Æ9{The following fields are private and are set up by the }°dONLNd
BÆ
N
˛*8{ RegisterSection function described later within this }°dONLNdC
PÆ
\
º*-{ chapter. Do not modify the private fields.}°dONLNdt
lÆ
xfi*subPart:°dONLNdÅ
l

x
8)ZLongInt;°dONLNdé
l
b
x
ò)Z    {private}°dONLNdö
zÆ
܈(
ÉÆnextSection:°dONLNd´
z

Ü
\)ZSectionHandle;°dONLNdæ
z
b
Ü)Z{private, do not use as a }°dONLNdÊ
à
b
î
∂*{ linked list}°dONLNd˜
ñÆ
¢¸(
üÆcontrolBlock:°dONLNd    
ñ

¢
2)ZHandle;°dONLNd
ñ
b
¢)Z{may be used for comparison }°dONLNd?
§
b
∞
å*{ only}°dONLNdI
≤Æ
æÿ(
ªÆrefNum:°dONLNdU
≤

æ
\)ZEditionRefNum;°dONLNdh
≤
b
æ
ò)Z    {private}°dONLNdr
¿ä
â(
…äEND;


ŸH
Ë4
⁄H
Ë
    .
°dONLNdw
Ÿä
‰÷*Field descriptions

ˇ·ˇ‚7^
.°dONLNdä
Êä
Ú¥*version.
°dONLNdí
ÊÊ
Ú
Ö)\&Indicates the version of the section rm†°dONLNd∏
Ê
Ö
Ú
ó)üecor‚°dONLNdº
Ê
ó
Ú
¥)d, curr,¿°dONLNd√
Ê
µ
Ú
fl)
ently $01..°dONLNdœ
ıä
¢(
˛äkind.
°dONLNd‘
ıÊ
¯)\Defi†°dONLNdÿ
ı˘
    )@nes the section type as either publisher or subscriber with the .°dONLNd
Ê
((
ÊstPublisher°dONLNd#

(
5)B or °dONLNd'

5
})stSubscriber°dONLNd3

}
ß)H
 constant.°dONLNd>ä¢(ämode.
°dONLNdCÊ
H)\Indicates if editions arj‡°dONLNd[
H
Ï)b#e updated automatically or manuallyg‡°dONLNd~
Î
Ì)£
..°dONLNdÄä+Æ((ämdDate.
°dONLNdáÊ+
r)\Indicates which version (modifiº†°dONLNd¶
r+)å'cation date) of the section’s contents ˇˇ‚™.°dONLNdÕ+Ê7
∂(4Ê/is contained within the publisher or subscriberú°dONLNd¸+
∂7
Œ)–. The ˇˇß˛◊°dONLNd+
Œ7
Ú)mdDateˇˇ‚™◊°dONLNd+
Ú7
Û)$
 ∫ö°dONLNd    +
Ù7
˚)
fi∫ö°dONLNd+
˚7)eld ùD°dONLNd+7)is .
°dONLNd7ÊC
>(@Êset to 0 when you cr@°dONLNd&7
?C
π)Yeate a new subscriber sectio{‡°dONLNdB7
πC
Δ)zn aÕ@°dONLNdE7
ΔC
À)
nû†°dONLNdF7
ÃC
◊)d t|¿°dONLNdI7
ÿC)
o the curr˛†°dONLNdS7C)*ent °dONLNdWCÊO
3(LÊtime when you crÿ°dONLNdgC
3O
é)Meate a new publisherÉ@°dONLNd{C
éO
Æ)[. Be surÒ¿°dONLNdÉC
ÆO
˙) e to update this fiÍ °dONLNdñC
˚O)Meld °dONLNdöOÊ[
|(XÊ!each time publisher data is modifi›¿°dONLNdºO
|[
‰)ñed. The section’s modifiΔ°dONLNd‘O
Â[)ication °dONLNd€[Êg
&(dÊdate is comparN°dONLNdÈ[
'g
ñ)Aed to the edition’s modifif†°dONLNd[
ñg)ocation date to determine °dONLNdgÊs
˝(pÊ?whether the section and the edition contain the same data. The °dONLNd[sÊ
$*section modifiB‡°dONLNdis
%
Î)?.cation date is displayed in the publisher and °dONLNdóÊã
Ä(àÊ#subscriber options dialog boxes. Se°dONLNd∫
Äã
á)öe .†°dONLNdº
àã
Ù)“Closing an Edition” on °dONLNd‘ãÊó˝(îÊpage Z‡°dONLNdŸã˛ó
)2-28Æ¿°dONLNd›ã
ó
) fdž°dONLNdflã
ó
)or detailed information.ˇò@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-18    )BUsing the Edition Manager4^*¿
¯,
Courier
.°dONLNd\lh¢(el    sectionID.
°dONLNd
\»h—)\PrN†°dONLNd\“h
‡)
;ovides a unique number for each section within a document. (Ä°dONLNdG\
‡h
Á(e
‡
Ac °dONLNdH\
Áh
È)
 °dONLNdIh»t
k(q»%simple way to implement this is to crπ°dONLNdnh
kt
–)£eate a counter for each °dONLNdÜt»Ä
·(}»>document that is saved to disk with the document. The counter °dONLNdƒÄ»å
r*)should start at 1. The section ID is currö@°dONLNdÌÄ
rå
Ã)™ently used as a tie br†°dONLNd
Ä
Õå
Ú)[    eaker in .°dONLNd
å»ò⁄(ï»the °dONLNd
å⁄ò
R)GoToPublisherSection°dONLNd
$å
Rò
©)x function when therR`°dONLNd
7å
©ò
∫)We ar$¿°dONLNd
;å
∫ò
Î)e multiple .
°dONLNd
Fò»§
Û(°»Dpublishers to the same edition in a single document. The section ID °dONLNd
䧻∞
:*should not be 0 or –1. See $¿°dONLNd
•§
;∞
ı)s)“Duplicating Publishers and Subscribers” °dONLNd
Œ∞»ºÌ(π»on page !¿°dONLNd
÷∞Óº
)&2-58u†°dONLNd
⁄∞
º
Ø)( for information on multiple publishers..°dONLNdølÀê(»lrefCon.
°dONLNd
ø»Àfl)\Refer⁄ °dONLNdøflÀ
®).ence constant available for application-specififi¿°dONLNd>ø
®À
¿)…c use..°dONLNdEŒl⁄ä(◊lalias.
°dONLNdKŒ»⁄
P)\ Contains a handle to the alias rÔÄ°dONLNdkŒ
P⁄
b)àecorc‡°dONLNdoŒ
c⁄
Ò)"d for a particular section within °dONLNdë⁄»Ê˛(„»a document..°dONLNdùÎl˜Ã(ÙlWhenever the user crR`°dONLNd±ÎØ
S)`eates a publisher or subscriberï°dONLNd–Î
R˜
})Ü, call the ï°dONLNd€Î
}˜
π)+
NewSectionï°dONLNdÂÎ
π˜
Ï)< function to .
°dONLNdÚ¯l
t(

lcrµ@°dONLNdÙ¯t
æ)eate the section rï¿°dONLNd¯æ
–)Jecor
 °dONLNd
¯—

)d and the alias r√ °dONLNd¯


))Fecor7Ä°dONLNd¯
*

2)d..°dONLNd"
l

‡(
l>err := NewSection(container, sectionDocument, kind, sectionID,°dONLNdf
Δ
)
b+Z   initialMode, sectionH);°dONLNdÅ
5l
AÄ(
>lThe °dONLNdÖ
5Ä
Aº)
NewSection°dONLNdè
5º
AÏ)< function crR`°dONLNdõ
5Ï
A
G)0eates a new section r$¿°dONLNd∞
5
G
A
Y)[ecor˜ °dONLNd¥
5
X
A
Ò)$d (either publisher or subscriber), .
°dONLNdÿ
Bl
NÏ(
Klindicates whether editions arzÄ°dONLNdı
BÏ
N
ê)Ä#e updated automatically or manuallywÄ°dONLNd
B
è
N
‘)£, sets the modifi5@°dONLNd)
B
’
N
Ú)Fcation °dONLNd0
Ol
[ü(
Xldate, and crJ °dONLNd<
O†
[‡)4eates an alias rć°dONLNdL
O‡
[Ú)@ecorı@°dONLNdP
OÚ
[

)d fr©‡°dONLNdT
O

[
Ú)6om the document containing the section to the edition °dONLNdä
\l
hï(
el    container2 °dONLNdì
\ï
hó))
..°dONLNdï
nl
zs(
wl
Yï°dONLNdñ
nr
z∞)ou can set the ï°dONLNd•
n∞
z∂)>
sï°dONLNd¶
n∂
z

)ectionDocumentï°dONLNd¥
n


z
8)T     parameteï°dONLNdΩ
n
8
z
I).r to ï°dONLNd¬
n
I
z
O)
Nï°dONLNd√
n
O
z
[)IL6†°dONLNd≈
n
[
z
a) i6†°dONLNd«
n
a
z
})f the c6†°dONLNdŒ
n
}
z
ä)urr    °dONLNd—
n
ä
z
Ù)ent document has never °dONLNdË
{l
á«(
Ñlbeen saved. Use the °dONLNd¸
{«
á
')[AssociateSection°dONLNd
{
'
á
¨)` function to update the alias rR`°dONLNd+
{
¨
á
æ)Öecor$¿°dONLNd/
{
æ
á
Ÿ)d of a .
°dONLNd6
àl
îo(
ël
rE°dONLNd7
àp
îç)egisterî °dONLNd>
àç
î
+)#ed section when the user names or r\@°dONLNda
à
,
î
’)ü#enames a document by choosing Save ¶`°dONLNdÑ
à
’
î
„)©As .°dONLNdá
ïl
°t(
ûlfrR`°dONLNdâ
ït
°Ï)om the File menu. If you ar$¿°dONLNd§
ïÏ
°˚)xe cr˜ °dONLNd®
ï˙
°
z)eating a subscriber with the ˜ °dONLNd≈
ï
z
°
º)ÄinitialMode˜ °dONLNd–
ï
º
°
)B parameter .
°dONLNd€
¢l
Æâ(
´lset to rE‡°dONLNd„
¢ä
Æ
)!eceive new editions automatically °dONLNd
¢

Æ
s)ï, your application r|`°dONLNd
¢
s
Æ
Ú)Teceives a Section Read event °dONLNd5
Øl
ª
y(
∏l=each time a new edition becomes available for this subscriberñ‡°dONLNdr
Ø
y
ª
{(
∏
y
..°dONLNdt
¡l
Õê(
 l    If an errR`°dONLNd}
¡ê
Õœ)$or is encounter$¿°dONLNdå
¡œ
ÕÒ)?ed, the $¿°dONLNdî
¡Ò
Õ
-)"
NewSection$¿°dONLNdû
¡
-
Õ
Y)< function r˜ °dONLNd©
¡
X
Õ
u)+eturns ˜ °dONLNd∞
¡
u
Õ
á)NILò¿°dONLNd≥
¡
á
Õ
¶) in the ò¿°dONLNdª
¡
¶
Õ
÷)sectionHò¿°dONLNd√
¡
÷
Õ
ÿ)0
 °dONLNdƒ
Œl
ړ(
◊lparamet°dONLNdÀ
Γ
⁄ò)'
e°dONLNdÃ
Θ
⁄ú)
r¬†°dONLNdÕ
Λ
⁄û)
.¬†°dONLNdŒ
Ξ
ڠ)
 ¬†°dONLNdœ
Π
⁄÷)Otherwise, ¬†°dONLNd⁄
Œ÷
⁄
)6
NewSection¬†°dONLNd‰
Œ

⁄
)< rï°dONLNdÊ
Œ

⁄
–)*eturns a handle to the allocated section rg`°dONLNd
Œ
–
⁄
‚)∏ecor9¿°dONLNd
Œ
‚
⁄
ı)d in °dONLNd
€l
Á~(
‰lthe °dONLNd
€~
ÁÑ)
s°dONLNd
ۄ
Á®)ection°dONLNd$
€®
ÁÆ)$
H°dONLNd%
ۮ
Á‡)
 parameter¬†°dONLNd/
€fl
Á‚)1
.ˇC@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-19
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿.°dONLNd\äh≠(eäSet the ,
Courier°dONLNd\≠hÔ)#initialMode°dONLNd\Ôh)B@ parameter to the update mode for each subscriber and publisher .
°dONLNdSiäuí(räcrµ@°dONLNdUiíuÆ)eated. y°dONLNd\iØuµ)
Y9Ä°dONLNd]iµu
§)5ou can specify the update mode using these constants:.°dONLNdìÄäå®(âäCONST°dONLNdõÄ¿å
)6sumAutomatic°dONLNd¨Ä
å
2)Z= 0;°dONLNd≥Ä
På
Ï)6{subscriber receives new }°dONLNdŸé
Pö
Ê*{ editions automatically}°dONLNdˆú¿®ˆ(•¿    sumManual°dONLNd
ú
®
2)Z= 1;°dONLNd
ú
P®
Ï)6{subscriber receives new }°dONLNd
1™
P∂
»*{ editions manually}°dONLNd
I∏¿ƒˆ(¡¿    pumOnSave°dONLNd
W∏
ƒ
2)Z= 0;°dONLNd
^∏
Pƒ
‘)6{publisher sends new }°dONLNd
ÄΔ
P“
¬*{ editions on save}°dONLNd
󑿇ˆ(›¿    pumManual°dONLNd
•‘
‡
2)Z= 1;°dONLNd
¨‘
P‡
Ï)6{publisher does not send }°dONLNd
“‚
PÓ
Ú*{ new editions until user }°dONLNd
ı
¸
(˘

 °dONLNd
˙
P¸
å)H
{ request}.
°dONLNd
ä
õ(
äSee ”°dONLNd    
õ

≠);“Using Publisher and Subscriber Options” beginning on page æ`°dONLNdD

Æ

¿(

Æ2-43@°dONLNdH

¡

˘) for detailed °dONLNdV
ä
!
¨(
ä@information on update modes for publishers and subscribers. See Ÿ`°dONLNdñ

¨
!
⁄(

¨Listing 2-4y†°dONLNd°

€
!)/ beginning .°dONLNd¨
"ä
.ñ(
+äon °dONLNdØ
"ñ
.Æ)page °dONLNd¥
"Æ
.¡)2-33°dONLNd∏
"¡
.
%) for code that uses the °dONLNd–
"
%
.
a)d
NewSection°dONLNd⁄
"
a
.
ú)< function to crR`°dONLNdÈ
"
ú
.
Ê);eate a publisherï°dONLNd˘
"
Â
.
¸)I. See °dONLNdˇ
/ä
;‡(
8äListing 2-6 on page °dONLNd
/‡
;È)V2-°dONLNd
/È
;Û)    40°dONLNd
/Û
;
E)
 for code that uses °dONLNd+
/
E
;
Å)R
NewSection°dONLNd5
/
Å
;
ñ)< to crR`°dONLNd;
/
ñ
;
‡)eate a subscriberï°dONLNdL
/
fl
;
‰)I. 


`H
g4
aH
g 
bä
b

ˇ·ˇ‚7^ˇˇ‹..
ˇ◊°dONLNdP
Qä
`
(
\ä%Saving a Document Containing Sectionsˇˇˇˇˇˇ€r(
\
2
°dONLNdw
gä
s
¯(
päQWhen saving a document that contains sections, you should write out each section .°dONLNd»
tä
Äé*
rR`°dONLNd…
té
Ć)ecor$¿°dONLNdÕ
t†
Ä¿)d as a r˜ °dONLNd’
tø
Ä÷)esour…Ä°dONLNd⁄
t÷
Ä
)ce of type …Ä°dONLNdÂ
t

Ä
')-'sect'…Ä°dONLNdÎ
t
'
Ä
ù)$ and write out each alias rõ‡°dONLNd
t
ù
Ä
Ø)vecorn@°dONLNd

t
Ø
Ä
œ)d as a r@†°dONLNd
t
œ
Ä
Ê) esour°dONLNd
t
Ê
Ä)ce of type °dONLNd"
Åä
çÆ(
ää'alis'°dONLNd(
ÅÆ
ç
E)$" with the same ID as the section rR`°dONLNdJ
Å
E
ç
W)óecor$¿°dONLNdN
Å
W
ç
Ü)d. See the $¿°dONLNdY
Å
Ü
ç
±)/    chapter “$¿°dONLNdb
Å
±
ç
œ)+Resour˜ °dONLNdh
Å
Œ
ç
)
ce Manager˜ °dONLNdr
Å

ç)3
”˜ °dONLNds
Å
ç)
 ˜ °dONLNdt
Å
ç)in .
°dONLNdw
éä
öÊ(
óäInside Macintosh: Mor¯Ä°dONLNdå
éÊ
ö
)\e Macintosh TÆ°dONLNdô
é

ö
8)9oolboxÖ†°dONLNdü
é
9
ö
>) fYÄ°dONLNd°
é
?
ö
∫)or detailed information on rf¿°dONLNdΩ
é
∫
ö
“){esourØ°dONLNd¬
é
“
ö
‰)ces. °dONLNd»
†ä
¨
e(
©ä2If a user closes a document that contains newly crc†°dONLNd˙
†
e
¨)€'eated publishers without attempting to °dONLNd!
≠ä
π
‡(
∂äOsave its contents, you should display an alert box similar to the one shown in §¿°dONLNdp
≠
‡
π
¯(
∂
‡FigurwÄ°dONLNdu
≠
¯
π)e 2-10°dONLNd{
≠
π)
.


€H
Ï4
‹H
Ï"
‹H]

ˇ·ˇ‚7^
    °dONLNd~
—ä
‹∫(
ŸäFigure 2-10°dONLNdä
—Ã
‹
:)BThe new publisher alert box


ÎàZòÄ4
X
ùHH



\*D

ˇˇˇˇˇˇ

X
ù
ÏäÃ
ñŒˇ¯ÄœÄœüœˇ»üœˇ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»
ò˝‘»
ò˝<‘»
ò˝<‘»*ò˝f˝ÿ˚˛
Ä˚Ä0˝
ĸ»)ò˝f˝˚˛

Ä˙Ä0˝
ĸ»3ò˝√˝%‡f√««Ä·„„«å¯pòôüé>6pèIJ»1ò˝√˝ôê332˝fc
ì31àÃûôôò˝ô338»ôôIJ»4ò˛
ÅIJô¿330˝fc
É31áÃÇôôòôôú330‡ôIJ»5ò˛
ôIJ%ò‡330ffgÊc
É31åÃÃpüôòôôé3?0pôIJ»5ò˛<¿˛òp330˛fc
É31åÃÃ8òòôôá3008ôIJ»5ò˛<¿˛ô0332˛f&c
ì31åÃÃòòôêôôì310ôÄôIJ»5ò˛<`˛%ò‡>fcΔaÄ·„0«ÃÃpè‡üé30qÄIJ»ò˛<`’»ò˛<0’»ò˛<0’»ò˛<’»ò˛<’»ò˛0<’»ò˛0<’»%ò˛`<˙`˝˚¿`˛
ˆ»%ò˛`˙`˝˚¿`˛
ˆ»0ò˛¿˛ ¸f8<f<ü‡f√««Å„¿f<<|ü˘»/ò˛¿˛ffd`2Fffôê332˝fcΔ`l˛fôôò˘»/ò
Ä
Äffp`8>ffô¿330˝fcΔ`x˛fôôò˘»0*ò
Ä
Äff8`ff~ò‡330ffgÊcΔ`p~~füôò˘»0ò<¿ff`ff`òp330˛fcΔ`x``fòò˘»1ò<¿ffL`&fdbô0332˛f&cΔ`lbbfòôôÄ˙»1+ò`f>80>x<
ôò‡>fcΔaÄc¿f<<|
ôèôÄ˙»ò˛`‰`Ù»ò˛0‰`Ù»ò˛ˇ÷»ò˛ˇ‡÷»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»(ò¯
IJ

ĸ0‡?0
ĸ

Ä˚»(ò¯
@˛

ĸ0
Ä0
ĸ

Ä˚»,ò¯å«ÄqÒ¯‡<x>
˛á<fxè3?·„„¿˚»+ò¯Ãÿ…ô˛ôêÃ33
å»Ãôåff0ôô˝3
1Ä˚»+ò¯áÃÿ¡ò˘˛ô¿Ã33
å«Ãåff0ôò˝3
1Ä˚»+ò¯
ÃÃœ¿¡˝ô¯‡Ã3?
èÃÃå~<0ôò˛3Û1Ä˚»)ò˜˛Ã
¡˝ôÄpÃ30
åÃå`f0ôò˛31Ä˚»+ò¯ÃÃå@…˝ôâ0Ã31
åLÃôåbf0ôô˛31Ä˚»,ò¯"áœÄqò˘ò¯‡x3
áá«å<fè31„0¿˚»
òÔ‚»ò

‚»
òÔ‚»òœ»òœ»òœ»òœ»ò¯@1åÿ˝0<Ó»ò¯Ä
åÿ˝0˝FÓ»ò¯Ãœè3Ãx|H<l1·Δ|>Ó»ò¯ÃÃΔ1åÃÃêôåfqò33&ffÓ»ò˜ÃΔ1åÃÃôåfaò33ÜffÓ»ò˜ÃΔ1å¸Ãüåfa¯31ΔffÓ»ò˜ÃΔ1å¿ÃòfaÄ30ÊffÌ»ò˜ÃΔ1åƒÃòåfaà32˛fÓ»ò˜Ã√0Ãx|<`1·Δf>Ó»
ò‰Ì»
ò‰FÌ»
ò‰<Ì»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»ò›
˜ˇÄ»ò›˜ˇ‡»ò›˜ˇ»ò›˜x»ò¯?¯ˇÄ˚˙ˇ¯˘ˇ˛8»ò¯¿¯`¸

Ä˙=Ģ
º»ò¯Ä¯ ¸
˘9˜ú»ò˘
˜¸˘
:˜\»ò˘
˜¸˘
:˜\»+ò˘
¯Δ
¿˛¸
‡˛
:˛p˚\»+ò˘
ÃΔ ˛¸˛
:˛»˚\».ò˘
Ãx¯OΔc¿¸
„·√Δ
:˛¿Òò˛\».ò˘

˛ÃÜÑff`¸33&f
:˛·ôò˛\».ò˘

˛Ã
√Êf`¸
Û3f
:˛p˘ôò˛\».ò˘

˛ÃÊfg‡¸33Ê
:˛9ôô¯˛\».ò˘

˛Ã
˛f
¸33
:˛ôôIJ\».ò˘

˛ÃffF ¸33&&
:˛ôôëà˛\».ò˘
¯xÃ
√ÁÉ¿¸
·Û1√Δ
:˛p˘‡˛\»ò˘
˜¸˘
:˜\»ò˘
˜¸˘
:˜\œò˘
˜¸˘
:˜\»ò¯Ä¯ ¸
˘9˜ú»ò¯¿¯`¸

Ä˙=Ģ
ºœò¯?¯ˇÄ˚˙ˇ¯˘ˇ˛8œò›˜¯»ò›˜ˇ»ò›˜ˇ‡»ò›
˜ˇÄ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»òœ»üœˇ»üœˇ»ÄœÄœŒˇ˙ÕŒŒŒŒÕÕÕÕÕÕÕÕÕŒŒŒŒŒŒŒÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕŒŒŒÕŒÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕÕŒŒŒÕŒÕÕÕÕ&üx
‚˝80»˙@¬@˛¿ı%
ÄÑĸD0H˙@@@˛@ı/)@ÄÄDπ¿Ñ√àà"xFXqp8Cã∏"¯/)@`
Ä"D¬ Ñë$Hà"DB"dâÄDDLë"¯/)ê@
Ĭ"DÇ |Ñë$EP"DB Dâ<DHë¯/)\·Ä"DɇÑü'≈P"DBD˘DG»ë¯/)@
Ä"DÇ Ñê$ "DBDÅDDë¯/)ÄÑ
Ä"LÇ @Hë$B &DB"DâDDHë"¯/)üx
4Å¿|0é#Ç xBDq<Cà"¯
ıÛÈ
ı"ÛÈı⁄ÕՌՌŒŒÕÕÕÕÕÕÕÕÕÕÕŒŒÕ    !@◊
˛
¿ÿcå8∞G<qp‹"!D»Hô"DâÄ‹"!DàGëDâ€"!DàHë"D˘€"!DàHë"DÅ€"!DàHë"D†ƒ8àGë<q€ı⁄ıD⁄ı8⁄ÕÕÕÕ+Ä @
  ˝¸A¯(Ä ¿
  ˝˛!˘@¯0,é" "√å<pG1cá,"«.q„¬0·«q` Yã1Δ8„,˙0,ë" #$DDàHëëë2#"0â""âê "fL…""DA2˙0,ë@"$DàGêê""" y"
‚â "DHâ" <A"˙0,ü@"#ÑD¯Hêé""" â""â "DHâ" DA"˙0,êÄ" DDÄHêÅ""" â""â "DHâ" DA"˙0,ëÄ"$DDàHëë""" â""â!"DHâ2""DA"˙0,éÄ"#Ñ<pGé«" "!é y„¬··àqDHà“"<1"˙Ó ˝

ÁÓ@˝

ÁÕÕÕÕÕ0˝›!˝›‡ Yè8qp,8flë "fHëâÄ2Dflàë "DHëâ"@flàë "DHë˘"@fl»ë "DHëÅ"@flHë!"DHìâ"DflO‡DOq"8fl˛
¸˛˛@‡˛
¸˛‹ˇl@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-20    )BUsing the Edition Manager4^*¿
¯
°dONLNd\lh÷(elIf you keep the section rmÄ°dONLNd\÷hË)jecor·‡°dONLNd\Ëh
")ds and alias rzÄ°dONLNd+\
#h
5);ecorÓ‡°dONLNd/\
5h
„)(ds for each publisher and subscriber as .°dONLNdWilup(rl
rR`°dONLNdXipuá)esour$¿°dONLNd]iáufi)ces, you can use the ,
Courier$¿°dONLNdrifiu
8)WChangedResource$¿°dONLNdÅi
8u
E)Z or $¿°dONLNdÖi
Eu
ì)WriteResource$¿°dONLNdíi
ìu
⁄)N function. If you .
°dONLNd§vlÇ¡(ldetach the section rÙ@°dONLNd∏v¡Ç”)Uecorh†°dONLNdºv‘Ç
)ds and alias r
@°dONLNd v
Ç
!);ecoru†°dONLNdŒv
!Ç
5)ds frg@°dONLNd”v
5Ç
·)'om each section, you need to clone the .°dONLNd˙Élè»(ålhandles and use the °dONLNd
É»è

)\AddResource°dONLNd
É

è
¢)B" function. See the chapter “ResourR`°dONLNd
;É
¢è
Á)òce Manager” in .
°dONLNd
Jêlú»(ôlInside Macintosh: Mor¯Ä°dONLNd
_ê»ú

)\e Macintosh TÆ°dONLNd
lê

ú
)9oolboxÖ†°dONLNd
rê
ú
®)! for detailed information on the .°dONLNd
ìùl©Δ(¶lChangedResource°dONLNd
¢ùΔ©À)Z, °dONLNd
§ùÀ©
)WriteResource°dONLNd
±ù
©
1)N, and °dONLNd
∑ù
1©
s)AddResource°dONLNd
¬ù
s©
†)B functions.°dONLNd
ŒØlªë(∏lUse the °dONLNd
÷ØëªÎ)%PBExchangeFiles°dONLNd
ÂØΪ
5)Z function to ensurR`°dONLNd
˜Ø
5ª
<)Je R`°dONLNd
˘Ø
<ª
l)
that the fiR`°dONLNdØ
lª
â)0le ID r$¿°dONLNdØ
âª
€)emains the same e$¿°dONLNdØ
ۻ
Ó)Rach .
°dONLNd ºl»
<(≈l.time you save a document that contains sectioni‡°dONLNdNº
=»
C)—s.&‡°dONLNdPº
D»
t) Saving a fi‚Ä°dONLNd\º
t»
◊)0le typically involves cr@†°dONLNdtº
ÿ»
ı)deating °dONLNd{…l’é(“la new fi~¿°dONLNdÉ…è’
Í)#Rle (with a temporary name), writing data to it, closing it, and then deleting the °dONLNd’÷l‚ó(fll
original fiéÄ°dONLNd‡÷ó‚—)+le that you arÁ`°dONLNdÓ÷—‚‹):e rˆ°dONLNdÒ÷‹‚
)
eplacing. 5†°dONLNd˚÷
‚
)+
Yˆ °dONLNd¸÷
‚
)ou r∑¿°dONLNd÷
‚
Ö)ename the temporary fi&Ä°dONLNd÷
Ü‚
‹)hle with the original .°dONLNd+„lÔs(Ïl
fi°dONLNd-„sÔ
)lename, which leads to a new fi°dONLNdL„
Ô
2)èle ID. The °dONLNdW„
2Ô
å)0PBExchangeFiles°dONLNdf„
åÔ
‰)Z function swaps the .
°dONLNdzl¸»(˘lcontents of the two fiV@°dONLNdê…¸
)]les (even if they ar¿°dONLNd§
¸
ÿ)Q,e open) by getting both catalog entries and °dONLNd–˝l
    
!(
l*swapping the allocation pointers. If the fi °dONLNd˚˝
!
    
8)µles ar$ °dONLNd
˝
9
    
q)e open, the fiÍÄ°dONLNd˝
q
    
í)8le contr€°dONLNd˝
í
    
‹)!ol block (FCB) is °dONLNd)

l
»(
lupdated so that the rw¿°dONLNd>

»
ÿ)\efer#‡°dONLNdB

Ÿ

ÿ)9ence numbers still access the same contents (under a new .°dONLNd{
l
#ò(
 l    name). Se°dONLNdÑ
ò
#ü),e .
°dONLNdÜ
ü
#¸)Inside Macintosh: Files.F‡°dONLNdù
˝
#
)^ fF‡°dONLNdü


#
é)or detailed information on the F‡°dONLNdæ

é
#
Ë)ãPBExchangeFilesF‡°dONLNdÕ

Ë
#
Í)Z
 .
°dONLNdŒ
$l
0ì(
-l    function.°dONLNdÿ
6l
Bö*Listing 2-2 @°dONLNd„
6õ
B
)/ illustrates how to save a fi™‡°dONLNd
6

B
—)u0le that contains sections. If the contents of a °dONLNd0
Cl
O
Ç(
Ll?publisher have changed since the last save, the application-defiÒ‡°dONLNdp
C
Ç
O
ü(
L
Çned prÔ¿°dONLNdv
C
ü
O
Ω)ocedurá°dONLNd|
C
æ
O
≈)e .°dONLNd~
Pl
\¿(
YlMySaveDocument°dONLNdå
P¿
\
)T writes the publisher=`°dONLNd°
P
 
\
€)`.’s data to its edition. It then writes out to .
°dONLNdœ
]l
i|(
flthe ›`°dONLNd”
]|
i˝)saved document the section r͇°dONLNdÔ
]˝
i
)Åecor_@°dONLNdÛ
]

i
J)ds and alias r˜‡°dONLNd

]
J
i
\):ecorl@°dONLNd
]
]
i
Δ)ds of all publishers and .°dONLNd
jl
v°(
slsubscribers. °dONLNd+
j°
vı)5MySaveDocument°dONLNd9
jı
v
Å)T calls another application-defi°dONLNdX
j
Å
v
ó)åned rR`°dONLNd]
j
ó
v
∏)outine, °dONLNde
wl
ÉÍ(
ÄlMyGetSectionAliasPair¬†°dONLNdz
wÈ
É˝)}, to rï°dONLNdÄ
w˝
É
X)eturn a handle and rg`°dONLNdî
w
X
É
o)[esour9¿°dONLNdô
w
o
É
ø)ce ID to a section. €`°dONLNd≠
w
æ
É
Ã)OAs .
°dONLNd∞
Ñl
êµ(
çldescribed earlierfÄ°dONLNd¡
ѵ
ê
r)I-, you should write out the eligible section rT¿°dONLNdÓ
Ñ
r
ê
Ñ)Ωecor… °dONLNdÚ
Ñ
Ñ
ê
æ)ds and alias ra¿°dONLNd
Ñ
ø
ê
—);ecor÷ °dONLNd
Ñ
—
ê
È)ds as °dONLNd

ël
ùo(
öl
rE°dONLNd
ëp
ùà)esourç@°dONLNd
ëà
ù‰)ces to allow for futur~¿°dONLNd&
ë‰
ù
&)\e compatibility•Ä°dONLNd5
ë
%
ù
>)A. Ther&@°dONLNd;
ë
?
ù
O)e ar4‡°dONLNd?
ë
O
ù
Ñ)e several difz`°dONLNdL
ë
Ñ
ù
ê)5fer\‡°dONLNdO
ë
ê
ù
·)ent techniques for °dONLNdb
ûl
™Ω(
ßlsaving or adding rŸ†°dONLNdt
ûΩ
™’)Qesour!‡°dONLNdy
û÷
™
Ì)Cces; this listing illustrates one technique. The section handles ar˛†°dONLNdº
û
Ï
™
Û(
ß
Ïe .°dONLNdæ
´l
∑‚(
¥lstill valid after using the °dONLNd⁄
´‚
∑
$)vAddResource°dONLNdÂ
´
$
∑
Ë)B0 function because this listing illustrates just .
°dONLNd
∏l
ƒŸ(
¡lsaving, not closing, the fisÄ°dONLNd0
∏⁄
ƒ‰)nle.°dONLNd4
 l
փ(
”lBeforÛ¿°dONLNd9
 É
÷
∏)He you write out sections, you need to see if any publisher sections shar¡¿°dONLNdÅ
 
π
÷
Í(
”
πe the same °dONLNdå
◊l
„Ç(
‡lcontr>Ä°dONLNdë
׃
„
)ol block. Publishers that sharõÄ°dONLNdØ
◊

„
I)e the same contr[†°dONLNdø
◊
J
„
Ç)Hol block sharq¿°dONLNdÃ
◊
Ç
„
‘)8e the same edition.°dONLNd‡
Èl
ıö(
ÚlIf a user crË°dONLNdÏ
Èö
ı
).eates an identical copy of a fi;†°dONLNd    
È

ı
s)Äle by choosing Save  °dONLNd    
È
s
ı
à)YAs fr•@°dONLNd    $
È
à
ı
Î)om the File menu and .°dONLNd    9
ˆl
!(
ˇl'does not make any changes to this new fi°dONLNd    a
ˆ
!
Ö)µle, you simply use the °dONLNd    x
ˆ
Ö
Â)dAssociateSection°dONLNd    à
ˆ
Â
Á)`
 .
°dONLNd    âl
ÿ(lRfunction to indicate to the Edition Manager which document a section is located inLJ°dONLNd    €
ÿ
⁄(
ÿ
.ˇ3‹@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-21
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHn4gHn"hH_

ˇ·ˇ‚7^    °dONLNd\äg∂(däListing 2-2°dONLNd\Œg
j)D%Saving a document containing sections,
Courier
.°dONLNd4väÇΔ(ä
PROCEDURE °dONLNd>vΔÇ“)<My°dONLNd@v“Ç
‡)-SaveDocument(thisDocument: MyDocumentInfoPtr;°dONLNdsщê+  °dONLNdxÑ
ê
 )6
 °dONLNdyÑ
 ê
º)numberOfSections: Integer)°dONLNdìÑ
ºê
¬)ú
;°dONLNdïíäûê(õä
V°dONLNdñíêûñ)
A°dONLNdóíñûú)
R°dONLNdö†ú¨¢+
a°dONLNdõ†¢¨ÿ)    SectionH:°dONLNd™†
¨
V)fSectionHandle°dONLNd∑†
V¨
\)N
;°dONLNd∫Æú∫¢(∑ú
c°dONLNdªÆ¢∫ˆ)opiedSectionH:°dONLNdœÆ
∫
,)fHandle°dONLNd’Æ
,∫
2)$
;°dONLNdÿºú»¢(≈ú
c°dONLNdŸº¢»Í)opiedAliasH:°dONLNdκ
»
,)fHandle°dONLNdÒº
,»
2)$
;°dONLNdÙ ú÷¢(”ú
r°dONLNdı ¢÷¿)esID:°dONLNd
 
÷
2)fInteger°dONLNd
 
2÷
8)*
;°dONLNd

ÿú‰¢(·ú
t°dONLNd
ÿ¢‰Ã)hisone:°dONLNd
ÿ
‰
2)fInteger°dONLNd
ÿ
2‰
8)*
;°dONLNd
"ÊúÚ¿(ÔúmyErr:°dONLNd
.Ê
Ú
,)lOSErr;°dONLNd
5Ùä
¢(˝äBEGI°dONLNd
9Ù¢
®)
N°dONLNd
<
ú
¢(
ú
F°dONLNd
=
¢

Ä)%OR thisone := 1 TO numberOfSections D°dONLNd
b

Ä

Ü)fi
O°dONLNd
e
ú
¢(
ú
B°dONLNd
f
¢
¥)EGI°dONLNd
i
¥
∫)
N°dONLNd
m
Æ
*¥(
'Æ
a°dONLNd
n
¥
*¸)SectionH := °dONLNd
z
¸
*
)HMy°dONLNd
|


*
˛))GetSectionAliasPair(thisDocument, thisone°dONLNd
•

˛
*
)ˆ, °dONLNd
µ
,
t
8
Ä(
5
t  °dONLNd
∑
,
Ä
8
Ü)
r°dONLNd
∏
,
Ü
8
§)esID)°dONLNd
Ω
,
§
8
™)
;°dONLNd
¡
:Æ
F¥(
CÆ
I°dONLNd
¬
:¥
F
Ü)#F (aSectionH^^.kind = stPublisher) °dONLNd
Â
:
Ü
F
å)“
&°dONLNd
Í
H¿
TΔ(
Q¿
(°dONLNd
Î
HΔ
T
z)aSectionH^^.mode = pumOnSave) °dONLNd    
H
z
T
Ä)¥
&°dONLNd
V¿
b“(
_¿(My°dONLNd
V“
b
å)CheckForDataChanged(aSectionH))°dONLNd0
V
å
b
™)∫ THEN°dONLNd9
d¿
pΔ(
m¿
D°dONLNd:
dΔ
p
J)oWriteEdition(aSection°dONLNdP
d
J
p
V)ÑH)°dONLNdR
d
V
p
\)
;°dONLNdU
rú
~¢(
{ú
E°dONLNdV
r¢
~¿)ND; {°dONLNd[
r¿
~Í)end of °dONLNdb
rÍ
~¸)*for°dONLNde
r¸
~
)
}°dONLNdh
Äú
åÆ(
âú{se°dONLNdk
ÄÆ
å
)t the curResFile t°dONLNd}
Ä

å
,)lo t°dONLNdÄ
Ä
,
å
Ê)he resource fork of thisDocumen°dONLNdü
Ä
Ê
å
Ú)∫t}°dONLNd£
éú
ö¢(
óú
U°dONLNd§
é¢
ö
Ü)&seResFile(thisDocument^.resForkRefNum)°dONLNd 
é
Ü
ö
å)‰
;°dONLNdÕ
úú
®Æ(
•ú{wr°dONLNd–
úÆ
®
Œ)0ite all section and alias records to the documen°dONLNd
ú
Œ
®
⁄(
•
Œt}°dONLNd
™ú
∂¢(
≥ú
F°dONLNd
™¢
∂
Ä)%OR thisone := 1 TO numberOfSections D°dONLNd*
™
Ä
∂
Ü)fi
O°dONLNd-
∏ú
Ģ(
¡ú
B°dONLNd.
∏¢
ƒ¥)EGI°dONLNd1
∏¥
ĺ)
N°dONLNd5
ΔÆ
“¿(
œÆ{gi°dONLNd8
Δ¿
“
¯)4ven an index, get the next section handle and resID °dONLNdl
Δ
¯
“
˛(
œ
¯
}°dONLNdp
‘Æ
‡¥(
ݮ
{°dONLNdq
‘¥
‡
⁄)1 from your internal list of sections for this fil°dONLNd¢
‘
⁄
‡
Ê(
›
⁄e}°dONLNdß
‚Æ
Ó¥(
ÎÆ
a°dONLNd®
‚¥
Ó¸)SectionH := °dONLNd¥
‚¸
Ó
)HMy°dONLNd∂
‚

Ó
)+GetSectionAliasPair(thisDocument, thisone, °dONLNdÔ

t
¸
Ä+l  °dONLNdÒ

Ä
¸
Ü)
r°dONLNdÚ

Ü
¸
§)esID)°dONLNd˜

§
¸
™)
;°dONLNd˚
˛Æ
¿(Æ{ch°dONLNd˛
˛¿

º)*eck for duplication of control block value°dONLNd(
˛
º

»)¸s}°dONLNd-Æ¿(ÆMyC°dONLNd0¿
»),heckForDupes(thisDocument, numberOfSections)°dONLNd\
»
Œ(
»
;°dONLNd`Æ&¿(#Æ{sa°dONLNdc¿&
P)ve section record to dis°dONLNd{
P&
\)êk}°dONLNdÄ(Æ4¥(1Æ
c°dONLNdÅ(¥4
Ä)"opiedSectionH := Handle(aSectionH)°dONLNd£(
Ä4
Ü)Ã
;°dONLNdß6ÆB‰(?Æ    myErr := °dONLNd∞6‰BÍ)6
H°dONLNd±6ÍB
Ä)andToHand(copiedSectionH)°dONLNd 6
ÄB
Ü)ñ
;°dONLNdŒDÆP¥(MÆ
A°dONLNdœD¥P
Ê)3ddResource(copiedSectionH, rSectionType, resID, '')°dONLNdD
ÊP
Ï(M
Ê
;°dONLNdRÆ^¿([Æ{sa°dONLNd    R¿^
D)ve alias record to dis°dONLNdR
D^
P)Ñk}°dONLNd$`Æl¥(iÆ
c°dONLNd%`¥l
§)(opiedAliasH := Handle(aSectionH^^.alias)°dONLNdM`
§l
™)
;°dONLNdQnÆz‰(wÆ    myErr := °dONLNdZn‰zÍ)6
H°dONLNd[nÍz
t)andToHand(copiedAliasH)°dONLNdrn
tz
z)ä
;°dONLNdv|Æà¥(ÖÆ
A°dONLNdw|¥à
⁄)1ddResource(copiedSectionH, rAliasType, resID, '')°dONLNd®|
ڈ
‡(Ö
⁄
;°dONLNd´äúñ¢(ìú
E°dONLNd¨ä¢ñ¿)ND; {°dONLNd±ä¿ñÍ)end of °dONLNd∏äÍñ¸)*for°dONLNdªä¸ñ
)
}°dONLNdæòú§Æ(°ú{wr°dONLNd¡òƧ
P)ite rest of document to dis°dONLNd‹ò
P§
\)¢k}°dONLNdfl¶ä≤ú(ØäEND°dONLNd‚¶ú≤®); ˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-22    )BUsing the Edition Manager4^*¿
¯

k*r
¯4l*r
¯ mlm
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\lk
∑(gl2Opening and Closing a Document Containing Sectionsˇˇˇˇˇˇ€r(g

2
°dONLNd4rl~
ÿ({lPWhen opening a document that contains sections, your application should use the ,
Courier.°dONLNdÑlãÆ*GetResource°dONLNdèÆã
()B function to get the section rR`°dONLNd≠
(ã
:)zecor$¿°dONLNd±
:ã
Ö)d and the alias r˜ °dONLNd¬
Ñã
ñ)Jecor…Ä°dONLNdΔ
ñã
Û)d for each publisher ˇˇ¨°dONLNd€ålò™(ïland subscribern®°dONLNdÈå™ò—)>
. Set the ˇˇr¿°dONLNdÛå—òÔ)'aliasˇˇ¨r¿°dONLNd¯åÔò˜) fi»°dONLNd˚å¯ò
I)    eld of the section r°H°dONLNd
å
Iò
[)Qecors®°dONLNd
å
[ò
·)d to be the handle to the alias'‡°dONLNd
2å
‚ò
¯)á. See .
°dONLNd
8ôl•ƒ(¢lthe chapter “Resourñ°dONLNd
Kôƒ•

)Xce Manager” in õ†°dONLNd
Zô

•
f)FInside Macintosh: Mor °dONLNd
oô
g•
†)]e Macintosh TË@°dONLNd
|ô
ü•
∏)8oolbox°@°dONLNd
Çô
π•
–) for dy°dONLNd
àô
—•
Ò)etailed .°dONLNd
ê¶l≤¬(Ølinformation on the °dONLNd
£¶¬≤
)VGetResource°dONLNd
ƶ
≤
*)B     function°dONLNd
∑¶
*≤
-)&
.°dONLNd
π∏lƒs(¡l
Yï°dONLNd
∫∏rƒπ)ou also need to rg`°dONLNd
À∏πƒ
>)Gegister each section using the g`°dONLNd
Í∏
>ƒ
ò)ÖRegisterSectiong`°dONLNd
˘∏
òƒ
◊)Z function. The °dONLNd≈l—Δ(ŒlRegisterSection°dONLNd≈Δ—
œ)Z< function informs the Edition Manager that a section exists.°dONLNdT‹lË
í(Âl1err := RegisterSection(sectionDocument, sectionH,°dONLNdçÍ͈
\+~  aliasWasUpdated);ˇˇ—°dONLNd°
l
(
lThe ˇˇs0Q°dONLNd•
Ä
⁄)RegisterSectionˇˇ—Q°dONLNd¥
⁄

P)Z function adds the section r8¿°dONLNd–

P

b)vecor °dONLNd‘

b

“)d to the Edition Manager¿°dONLNdÏ

”

¯)q’s list of ˇˇ«Ê°dONLNd˜
l
p(
l
rR`°dONLNd¯
p
è)egister$¿°dONLNdˇ
è

N),ed sections. This function assumes that the ˇˇW≤ú
°dONLNd+

N

l)øaliasˇˇ«Êú
°dONLNd0

l

t) fic°dONLNd3

u

Õ)    eld of each section rUË°dONLNdH

Õ

fl)Xecor(H°dONLNdL

fl

¯)d is a .
°dONLNdS
l
(√(
%lhandle to the alias rXÄ°dONLNdh
√
(’)WecorÇ°dONLNdl
’
(
)d. The alias rw °dONLNdz


(
 )9ecorÎÄ°dONLNd~

 
(
=)d is a rq†°dONLNdÜ

>
(
N)efer¿°dONLNdä

O
(
’) ence to the edition container frœ†°dONLNd™

’
(
ˆ)Üom the .°dONLNd±
)l
5fl(
2lsection’s document. If the °dONLNdÃ
)fl
5
9)sRegisterSection°dONLNd€
)
9
5
Ô)Z+ function successfully locates the edition .
°dONLNd
6l
B
?(
?l4container for a particular section, the section is r6 °dONLNd:
6
@
B
])‘egisterÖ@°dONLNdA
6
]
B
w)ed thr√`°dONLNdG
6
w
B
™)ough a shars‡°dONLNdR
6
´
B
œ)4ed contró¿°dONLNdZ
6
œ
B
ˆ)$
ol block. °dONLNdd
Cl
Oñ(
Ll    The contrz@°dONLNdm
Cñ
OÙ)*ol block is a private fi˛Ä°dONLNdÖ
CÙ
O
E)^eld in the section r‡°dONLNdô
C
F
O
X)RecorÖ@°dONLNdù
C
X
O
`)d..°dONLNd†
Ul
aà(
^lIf the °dONLNdß
Uà
a‚)RegisterSection°dONLNd∂
U‚
a
0)Z function cannot fi°dONLNd…
U
0
a
Ê)N*nd the edition container for a particular °dONLNdÛ
bl
nò(
kl
subscriber¬†°dONLNd˝
bó
nú)+, ¬†°dONLNdˇ
bú
nˆ)RegisterSection¬†°dONLNd
bˆ
n¸)Z rï°dONLNd
b¸
n
+)eturns the ï°dONLNd
b
+
n
£)/containerNotFoundWrnï°dONLNd/
b
£
n
©)x rg`°dONLNd1
b
©
n
‰)esult code. If °dONLNd@
ol
{~(
xlthe °dONLNdD
o~
{ÿ)RegisterSection°dONLNdS
oÿ
{
&)Z function cannot fi°dONLNdf
o
&
{
‹)N*nd the edition container for a particular °dONLNdê
|l
àò(
Öl    publisher¬†°dONLNdô
|ó
àú)+, ¬†°dONLNdõ
|ú
àˆ)RegisterSection¬†°dONLNd™
|ˆ
à
)Z crï°dONLNd≠
|

à
Ô)
6eates an empty edition container for the publisher in .
°dONLNd„
âl
ï
‚(
ílUthe last place the edition was located. The Edition Manager sends your application a °dONLNd8
ñl
¢ò*    Section W-‡°dONLNdA
ñò
¢
),rite event for that section. °dONLNd_
®l
¥
Ú(
±lVWhen a user attempts to open a document that contains multiple publishers to the same °dONLNdµ
µl
¡
Ü*@edition, you should warn the user by displaying an alert box (se¶°dONLNdı
µ
Ü
¡
ç(
æ
Üe Ô†°dONLNd˜
µ
ç
¡
…)“Duplicating °dONLNd
¬l
Œ
(
Àl$Publishers and Subscribers” on page ◊@°dONLNd(
¬

Œ
")§2-58+ °dONLNd,
¬
#
Œ
&)
)°dONLNd-
¬
&
Œ
()
.°dONLNd/
‘l
‡
Î(
›lTWhen a user opens a document that contains a subscriber (with an update mode set to °dONLNdÉ
·l
̧*automatic), rΔ‡°dONLNdê
·§
Ì
È)8Geceives a new edition, and then closes the document without making any °dONLNd◊
Ól
˙≥(
˜lchanges to the fiJ¿°dONLNdË
Ó¥
˙
Ô)HFle, you should update the document and simply allow the user to close °dONLNd.
˚lw(lit. } °dONLNd2
˚w})
Y=†°dONLNd3
˚}◊)ou do not need to prT °dONLNdG
˚◊
Ä)Z&ompt the user to save changes to the fio`°dONLNdn
˚
Ä
á)©le!`°dONLNdq
˚
à
ä)
.°dONLNdsl
Å(l<When closing a document that contains sections, you must unrj°dONLNdØ
Å
˜(
Åegister each section (using .°dONLNdÀl&~(#lthe °dONLNdœ~&‰)UnRegisterSection°dONLNd‡‰&
{)f# function) and dispose of each corrR`°dONLNd    
{&
œ)óesponding section r$¿°dONLNd    
œ&
·)Tecor˜ °dONLNd    
‡&
Ë)d .
°dONLNd    'l3ô(0land alias r?‡°dONLNd    ''ö3¨).ecor¥@°dONLNd    +'¨3¥)d..°dONLNd    .>lJˆ(Glerr := UnRegisterSectio°dONLNd    E>ˆJ
)än(°dONLNd    G>
J
>)
sectionH);°dONLNd    RVlbÄ(_lThe °dONLNd    VVÄbÊ)UnRegisterSection°dONLNd    gVÊb
)f function rR`°dONLNd    rV
b
l),emoves the section r$¿°dONLNd    ÜV
lb
~)Zecor$¿°dONLNd    ãV
~b
é)d fr˜ °dONLNd    èV
çb
À)om the list of .
°dONLNd    ûcloo(ll
rE°dONLNd    ücpoç)egisterî °dONLNd    ¶cço
)!ed sections and unlinks itself frŸ`°dONLNd    «c
o
J)âom the shar”†°dONLNd    “c
Jo
n)4ed contr˜Ä°dONLNd    ⁄c
no
ì)$    ol block.ˇ42@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-23
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh∏(eäListing 2-3 @°dONLNd\πh
[)/& illustrates how to open an existing fi‡°dONLNd2\
\h
…)£le that contains sections. D`°dONLNdM\
…h)mAs described °dONLNdZiäu¶(räearlier‡°dONLNdai¶u„), you should rk¿°dONLNdoi„u
c)=etrieve the section and alias rí°dONLNdéi
cu
{)Äesour⁄@°dONLNdìi
{u
„)ces, connect the pair thri °dONLNd¨i
‰u)i    ough the ,
Courier.°dONLNdµväÇ®(äalias°dONLNd∫v®ÇÆ) fPÄ°dONLNdºvÆÇ
)ield of the section r"‡°dONLNd—v
Ç
)Wecorı@°dONLNd’v
Ç
8)d, and r«†°dONLNd›v
8Ç)",egister the section with the Edition Manager
@°dONLNd
    vÇ)À. .
°dONLNd
Éäèû(åäTher¿°dONLNd
ÉüèØ)e ar`°dONLNd
ÉØèfi)
e many dif7‡°dONLNd
ÉfièÍ)/fer`°dONLNd
 ÉÍè
?)ent techniques for rß°dONLNd
4É
?è
m)Uetrieving rã¿°dONLNd
?É
mè
Ö).esour‘°dONLNd
DÉ
Öè
˘)ces; this listing shows one °dONLNd
`êäú
õ(ôä>technique. If an alias was out of date and was updated by the *Ä°dONLNd
ûê
õú
ˇ(ô
õAlias Manager during .°dONLNd
≥ùä©ú(¶äthe °dONLNd
∑ùú©†)
rR`°dONLNd
∏ù†©
G)%esolve, the Edition Manager sets the R`°dONLNd
›ù
G©
°)ßaliasWasUpdatedR`°dONLNd
Ïù
°©
Ú)Z parameter of the °dONLNd
˛™ä∂‰(≥äRegisterSection°dONLNd™‰∂
)Z function to °dONLNd™
∂
/)3TRUE°dONLNd™
/∂)0. This means that you should save the document. .
°dONLNdN∑ä√¬(¿äAdditionally‡°dONLNdZ∑¬√
ó)82, your application must maintain its own list of rö†°dONLNdå∑
ó√
¥)’egisterÈ¿°dONLNdì∑
¥√)ed sections for each °dONLNd®ƒä–
5(Õä&open document that contains sections. 䇰dONLNdŒƒ
5–
;)´
YK`°dONLNdœƒ
;–
˝)/ou use this list to write out new editions for °dONLNd˛—ä›
8(ڊ%updated publishers within a document.


H
4

H
"

H_

ˇ·ˇ‚7^
    °dONLNd%ˆä

∂*$Listing 2-3°dONLNd1ˆŒ


p)D&Opening a document containing sections
.°dONLNdY
ä
Δ(
ä
PROCEDURE °dONLNdc
Δ
“)<My°dONLNde
“
)5OpenExistingDocument(thisDocument: MyDocumentInfoPtr)°dONLNdö

(

;°dONLNdú
ä
*ú(
'äVAR°dONLNd°
,ú
8“+    sectionH:°dONLNd±
,

8
n)~SectionHandle;°dONLNd¡
:ú
FΔ(
CúaliasH:°dONLNdœ
:

F
b)~AliasHandle;°dONLNd›
Hú
T¸(
QúaliasWasUpdated:°dONLNdÙ
H

T
J)~Boolean;°dONLNd˛
Vú
b‰(
_úregisterErr:°dONLNd
V

b
>)~OSErr;°dONLNd
dú
p¿(
múresID:°dONLNd&
d

p
D)~Integer°dONLNd-
d
D
p
J)*
;°dONLNd0
rú
~fi(
{útheResType:°dONLNdB
r

~
J)~ResType;°dONLNdL
Äú
åÃ(
âúthisone:°dONLNd[
Ä

å
J)~Integer;°dONLNde
éú
ö
(
óúnumberOfSections:°dONLNd}
é

ö
J)~Integer;°dONLNdá
úú
®¿(
•úaName:°dONLNdî
ú

®
>)~Str255°dONLNdö
ú
>
®
D)$
;°dONLNdú
™ä
∂¢(
≥äBEGI°dONLNd†
™¢
∂®)
N°dONLNd£
∏ú
Ģ(
¡ú
U°dONLNd§
∏¢
ƒ
Ü)&seResFile(thisDocument^.resForkRefNum)°dONLNd 
∏
Ü
ƒ
å)‰
;°dONLNdÕ
Δú
“Æ(
œú{fi°dONLNd–
ΔÆ
“
å)%nd out the number of section resource°dONLNdı
Δ
å
“
ò)fis}°dONLNd˘
‘ú
‡
¬(
›ú1numberOfSections := Count1Resources(rSectionType)°dONLNd*
‘
¬
‡
»(
›
¬
;°dONLNd-
‚ú
Ó¢(
Îú
F°dONLNd.
‚¢
Ó
Ü)&OR thisone := 1 TO numberOfSections DO°dONLNdV
ú
¸∫(
˘úBEGIN°dONLNd^
˛Æ

Ú+6sectionH := SectionHandle(Get1IndResource(rSectionType°dONLNdî
˛
Ú

¯(
Ú
,°dONLNd†
>
D(
>
 °dONLNd°
D
J)
 °dONLNd£
P
V)
 °dONLNd®
ò
û)H
 °dONLNd©
û
§)
t°dONLNd™
§
‘)hisone))°dONLNd≤
‘
⁄)0
;°dONLNd∂Æ&
2(#ÆIF sectionH = NIL THEN°dONLNd‘
>&
Ú)ê{something could be wrong with°dONLNdÚ
Ú&
¯)¥
 °dONLNdÛ
¯&
˛)
}°dONLNd¯(¿4
(1¿MySectionErr;°dONLNd(
>4
)~"{ the file, handle appropriately} °dONLNd16ÆB“(?Æ{get r°dONLNd76“Bÿ)$
e°dONLNd86ÿB
)source I°dONLNd@6
B
b)0D of the sectio°dONLNdO6
bB
˛)Zn & use same ID for alias}°dONLNdlDÆP
z(MÆ"GetResInfo(Handle(sectionH), resID°dONLNdéD
zP
»)Ã, theResType,°dONLNdõD
»P
¯)N aName);°dONLNd¶RÆ^
⁄([Æ2{detaching is not necessary, but it is convenient}°dONLNd€`Æl
n* DetachResource(Handle(sectionH))°dONLNd˚`
nl
t)¿
;°dONLNdˇnÆz
(wÆ{get the alias}°dONLNd|Æà¥*
a°dONLNd|¥à
Ú)5liasH := AliasHandle(Get1Resource(rAliasType, resID))°dONLNdG|
Úà
¯(Ö
Ú
;°dONLNdKäÆñ
&(ìÆIF aliasH = NIL THEN°dONLNdgä
>ñ
˛)ê {something could be wrong with }°dONLNdãò¿§
(°¿MyAliasErr;°dONLNdùò
>§
)~"{ the file, handle appropriately} °dONLNd¬¶Æ≤
b(ØÆDetachResource(Handle(aliasH))°dONLNd‡¶
b≤
h)¥
;ˇ@@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-24    )BUsing the Edition Manager4^*¿
¯,
Courier
.°dONLNd\êh¢(eê{co°dONLNd\¢h
\)nnect section and alias togethe°dONLNd"\
\h
h)∫r}°dONLNd'jêv
,(sêsectionH^^.alias := aliasH°dONLNdAj
,v
2)ú
;°dONLNdExêÑ¢(Åê{re°dONLNdHx¢Ñ
)gister the sectio°dONLNdYx
Ñ
)fn}°dONLNd^Üêí
‘(èê6registerErr := RegisterSection(thisDocument^.fileSpec,°dONLNdöîΔ†fi+6    °dONLNd°î¸†
)6
 °dONLNd•î
2†
8)6
 °dONLNdßî
D†
Ê) sectionH, aliasWasUpdated)°dONLNd¬î
ʆ
Ï)¢
;°dONLNdΔ¢êÆ
‘(´ê6{The RegisterSection function may return an error if }°dONLNdˇ∞êº
Ú*;{ a section is not registered. This is not a fatal error. }°dONLNd
=æê 
¬*3{ Continue looping to register remaining sections.}°dONLNd
sÃêÿ¢*{ad°dONLNd
vâÿ
‡)5d this section/alias pair to your internal bookkeepin°dONLNd
´Ã
‡ÿ
Ï(’
‡g}°dONLNd
∞⁄êÊñ(„ê
M°dONLNd
±⁄ñÊ
»)3yAddSectionAliasPair(thisDocument, sectionH, resID)°dONLNd
‰⁄
»Ê
Œ(„
»
;°dONLNd
ËËêÙñ(Òê
I°dONLNd
ÈËñÙ
)F aliasWasUpdated THE°dONLNd
˛Ë
Ù
 )~N °dONLNdˆ¢

∞(ˇ¢-{If alias has changed, make a note of this. }°dONLNd5
¢

∞*-{ It's important to know this when you save.}°dONLNdf
¢
¥*MyA°dONLNdi
¥

J)liasHasChanged(sectionH);°dONLNdÑ
 ~
,¢(
)~END; {°dONLNdä
 ¢
,¿)$end o°dONLNdè
 ¿
,‰)f FOR}°dONLNdñ
.l
:~(
7lEND°dONLNdô
.~
:ê);  


`*
g
¯4
a*
g
¯ 
bl
b
¯

ˇ·ˇ‚7^ˇˇ‹..
ˇ◊°dONLNdû
Ql
` (
\lReading and WÊv°dONLNd´
Q 
`
$)^riting a Sectionˇˇˇˇˇˇ€r(
\

2
°dONLNdΩ
gl
sr(
pl
Y@Ä°dONLNdæ
gr
s
≥)Iour application writes publisher data to an edition. New publisher data rÛÄ°dONLNd
g
≥
s
Ê(
p
≥eplaces the °dONLNd
tl
Äu(
}lprG °dONLNd
tv
Ä
;)
-evious contents of the edition, making the pr£Ä°dONLNdB
t
;
Ä
æ)≈evious edition information irr– °dONLNd`
t
æ
Ä
Ó)Éetrievable. °dONLNdl
Ål
çr(
äl
Y@Ä°dONLNdm
År
çº)our application r+†°dONLNd~
ź
çÔ)Jeads data fr≈°dONLNdä
ÅÔ
ç
€)34om an edition for each subscriber within a document.°dONLNdø
ìl
ü
(
úl&The following sections describe how to,Zapf Dingbats°dONLNdÊ
©l
∞q*
n
°dONLNdË
¶x
≤ï)use dif8 °dONLNdÔ
¶ñ
≤¢)fer†°dONLNdÚ
¶¢
≤
)ent formats to write to or r‚@°dONLNd
¶

≤
/)tead fr`Ä°dONLNd
¶
0
≤
m)om an edition°dONLNd"
ªl
¬q(
¡l
n
°dONLNd$
∏x
ƒ
)(open an edition to initiate writing or rûÄ°dONLNdL
∏

ƒ
=)ßeading°dONLNdS
Õl
‘q(
”l
n
°dONLNdU
 x
÷≈)set a format mark°dONLNdg
fll
Êq(
Âl
n
°dONLNdi
‹x
˨)write to or r#°dONLNdv
‹≠
ËΔ)5ead fr°@°dONLNd|
‹Δ
Ë
)om an edition°dONLNdä
Òl
¯q(
˜l
n
°dONLNdå
Óx
˙
@)0close an edition after successfully writing or rEÄ°dONLNdº
Ó
A
˙
u)…eading data

*
¯4*
¯ l
¯

ˇ·ˇ‚7^°dONLNd…
l›(lFormats in an Editionˇˇˇˇˇˇ‘@(
Ò
2
°dONLNd‡l*r('l
Y@Ä°dONLNd·r*
5).ou can write data to an edition in several dif °dONLNd
5*
A)√fer˚†°dONLNd
@*
¡)ent formats. These formats arˇ °dONLNd/
¡*
Ú)Åe the same °dONLNd:+l7q(4l
a°dONLNd;+q7Ä)s scÍ@°dONLNd?+Ä7
))&rap format types. Scrap format types a]°dONLNde+
*7
-)™
r"°dONLNdf+
.7
à)e indicated by a fourÌ¿°dONLNd{+
à7
Δ)Z-character tag.°dONLNdã=lIr(Fl
T∫¿°dONLNdå=qIî)ypicallyË¿°dONLNdî=ìI
H)"*, when a user copies data, you identify th≠‡°dONLNdæ=
II
™)∂e scrap format types aΔ °dONLNd‘=
™I
Ë)and then write °dONLNd‚JlVù(Slthe data to Û`°dONLNdÓJùV≠)1the P¿°dONLNdÚJÆV‘)scrap. Wf °dONLNd˙J‘V
=)&ith the Edition Manager%¿°dONLNdJ
=V
Â)i', when a user decides to publish data, °dONLNd8Wlc≠(`lyou identify thL`°dONLNdGWÆcÙ)Be format types aB†°dONLNdWWıc
ñ)G&nd then write the data to an edition. s°dONLNd}W
ñc
ú)°
Y3Ä°dONLNd~W
úc
’)ou can write °dONLNdãdlp
(ml"multiple formats of the same data.°dONLNdÆvlÇ
*(For an edition, you should write your pr&`°dONLNd÷v
Ç
3)≥eferr≈ °dONLNd€v
3Ç
k)ed formats fiΔ†°dONLNdËv
kÇ
Á)8rst. In general, to write data ˇˇƒÏ.°dONLNdÉlèv(ålto °dONLNd
Éwè
F)/an edition, your application should use either ˇˇNƒ‚t°dONLNd9É
Fè
j)œ'TEXT'ˇˇƒÏ‚t°dONLNd?É
jè
ó)$ format or ˇˇNƒ18°dONLNdJÉ
òè
º).'PICT'ˇˇƒÏ18°dONLNdPÉ
ºè
¯)$ format. This .
°dONLNd^êlúı(ôlallows your application to sharö¿°dONLNd}êıú
ú)â&e data with most other applications. TÕ†°dONLNd£ê
õú
⁄)¶o subscribe to .°dONLNd≤ùl©y(¶lan °dONLNdµùy©
?)-edition, your application should be able to rR`°dONLNd‚ù
?©
i)Δ    ead both R`°dONLNdÎù
i©
ç)*'TEXT'R`°dONLNdÒù
ç©
¢)$ and R`°dONLNdˆù
¢©
Δ)'PICT'R`°dONLNd¸ù
Δ©
œ)$ fiR`°dONLNdˇù
ϩ
Ï)    les. In .
°dONLNd™l∂
Ú(≥lXaddition, your application can write any other private formats that you want to support.ˇ><@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-25
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh‰(eäScrap format types aQ`°dONLNd\ÂhË)[
r`°dONLNd\Èh
9)e described in the Q¿°dONLNd(\
9h
a)P    chapter “ °dONLNd1\
bh
§))Scrap Manager ‡°dONLNd>\
§h
∂)B” in ц°dONLNdC\
∑h
)Inside Macintosh: °dONLNdUiäuõ(räMorÄ°dONLNdXiúu’)e Macintosh T͆°dONLNdei‘uÌ)8oolbox£†°dONLNdkiÓu)
.°dONLNdm{äáë(Ñä
A∫†°dONLNdn{ëáÙ) few special formats arM@°dONLNdÖ{ıá
)de defiâ°dONLNdã{
á
W)ned as constants.,
Courier.°dONLNdùíäû®(õäCONST°dONLNd§íÆû
>)$kPublisherDocAliasFormat°dONLNd≈í
Pû
Ü)¢    = 'alis';°dONLNdœí
Üû)6{alias record from the }°dONLNdˆ†
ܨ*{ edition to publisher}°dONLNd
ÆÆ∫¸(∑ÆkPreviewForma°dONLNd
Ƹ∫
)N
t°dONLNd
'Æ
P∫
V)T
=°dONLNd
(Æ
V∫
Ü) 'prvw';°dONLNd
1Æ
Ü∫
¯)0{'PICT' thumbnail }°dONLNd
Sº
Ü»
º*    { sketch}°dONLNd
_ Æ÷
(”ÆkFormatListForma°dONLNd
o 
÷
)`
t°dONLNd
y 
P÷
V)B
=°dONLNd
z 
V÷
Ü) 'fmts';°dONLNd
É 
Ü÷
)0{lists all available }°dONLNd
®ÿ
܉
¬*
{ formats}°dONLNd
≥ä¸û(˘äThe °dONLNd
∑û¸
.)kPublisherDocAliasFormat°dONLNd
œ
.¸
4)ê (°dONLNd
—
4¸
X)'alis'°dONLNd
◊
X¸
)$#) format is written by the Edition .
°dONLNd
˙˝ä
    ±(
äManagerT†°dONLNd
˝±
    )'. It is an alias rø°dONLNd˝
    
)?ecor3`°dONLNd˝

    
)d frË°dONLNd˝

    
ö)om the edition to the publisherM °dONLNd:˝
ú
    
◊)ä’s document. -°dONLNdG˝
◊
    );Appended to °dONLNdS

ä

n(
ä7the end of the alias is the section ID of the publishere@°dONLNdä


n
)‰$, which the Edition Manager uses to °dONLNdÆ
ä
#
í(
 ä=distinguish between multiple publishers to a single edition. &†°dONLNdÎ

ì
#
ô(
 
ì
YÁ °dONLNdÏ

ò
#)ou should discourage users °dONLNd
$ä
0ë(
-äfrò‡°dONLNd    
$ë
0
k)/om making multiple copies of the same publisherw‡°dONLNd8
$
k
0
z)⁄. SeÅ@°dONLNd<
$
z
0
Å)e  ‡°dONLNd>
$
Å
0
)“Duplicating Publishers and °dONLNdZ
1ä
=È(
:äSubscribers” on page y`°dONLNdo
1Í
=¸)`2-58Õ@°dONLNds
1¸
=

) f° °dONLNdu
1

=
k)or detailed information..°dONLNdé
Cä
O
"(
Lä"In addition to writing a publisher=`°dONLNd∞
C
#
O
ú)ô’s data to an edition in the =`°dONLNdÕ
C
ú
O
¿)y'TEXT'=`°dONLNd”
C
¿
O
Ó)$ format or =`°dONLNdfi
C
Ó
O).'PICT'=`°dONLNd‰
C
O)$
 °dONLNdÂ
Pä
\
≠(
YäBformat, your application can also write data to an edition in the °dONLNd'
P
≠
\
(
Y
≠kPreviewFormat°dONLNd5
P

\)T
 °dONLNd6
]ä
ié(
fä
(°dONLNd7
]é
i≤)'prvw'°dONLNd=
]≤
i
)$) format. If you prR`°dONLNdP
]

i
&)Povide a R`°dONLNdX
]
&
i
,)$
'R`°dONLNdY
]
,
i
J)prvw'R`°dONLNd^
]
J
i)+ format in an edition, the Edition Manager .
°dONLNdâ
jä
vË(
säuses it to display a prØ@°dONLNd†
jË
v
})^#eview of the edition data in the prJ†°dONLNd√
j
~
v
£)ñeview arÄ°dONLNdÀ
j
§
v
¸)&ea of the subscriber ˇˇò.°dONLNd‡
wä
É–(
Äädialog box. The ˇ˛»H°dONLNd
w—
Éı)G'prvw'ˇˇòH°dONLNdˆ
wı
É
á)$! format has the same format as a ˇ˛»X°dONLNd
w
à
É
¨)ì'PICT'ˇˇòX°dONLNd
w
¨
É
¥)$ fi†`°dONLNd 
w
¥
É
«)le. TMh°dONLNd%
w
«
É
¯)o draw a prÁ‡°dONLNd0
w
¯
É)1eview °dONLNd6
Ñä
êß(
çäin the °dONLNd=
Ñß
êÀ)'prvw'°dONLNdC
ÑÀ
ê
i)$# format, the Edition Manager calls °dONLNdf
Ñ
i
ê
´)ûDrawPicture°dONLNdq
Ñ
´
ê
“)B     with a rR`°dONLNdz
Ñ
“
ê)'ectangle of .
°dONLNdÜ
ëä
ùõ(
öä120 °dONLNdä
ëú
ù©)by ñ¿°dONLNdç
ë©
ùÓ)120 pixels. (See ø¿°dONLNdû
ëÓ
ù
Z)EInside Macintosh: ImagingÉÄ°dONLNd∑
ë
[
ù
~)m for morN°dONLNdø
ë

ù
Ÿ)$e information about .°dONLNd”
ûä
™Ã(
ßäDrawPicture°dONLNdfi
ûÃ
™’)B.) R`°dONLNd·
û’
™‹)    
Yg`°dONLNd‚
û€
™
N)our application should pr9¿°dONLNd˚
û
N
™
ï)sovide data in a 9¿°dONLNd
û
ï
™
π)G'prvw'9¿°dONLNd
û
π
™)$ format so that the .
°dONLNd%
´ä
∑Û(
¥ädata displays well in a rΔ°dONLNd>
´Û
∑
N)iectangle of this size. ò†°dONLNdU
´
N
∑
T)[
YY °dONLNdV
´
T
∑
Ó)$our application can also use this pri¿°dONLNdz
´
Ó
∑
)öeview °dONLNdÄ
∏ä
ƒ
ó(
¡ä=to display subscriber data within a document (to save space)..°dONLNdæ
 ä
÷
*If your application does not prR`°dONLNd›
 

÷
@)à
ovide a pr$¿°dONLNdÁ
 
@
÷
{).eview in the $¿°dONLNdÙ
 
{
÷
ü);'prvw'$¿°dONLNd˙
 
ü
÷)$ format for an edition, the °dONLNd
׊
„
(
‡äEdition Manager attempts to prR`°dONLNd4
◊

„
F)é
ovide a pr$¿°dONLNd>
◊
F
„
Δ).eview by using the edition’s $¿°dONLNd[
◊
Δ
„
Í)Ä'PICT'$¿°dONLNda
◊
Í
„)$     format. °dONLNdj
‰ä
ê(
Ìä
Tï°dONLNdk
‰è
¬)o draw a prg`°dONLNdv
‰¬
˝)3eview in the g`°dONLNdÉ
‰˝

!);'PICT'g`°dONLNdâ
‰
!
)$0 format, the Edition Manager examines the pictur9¿°dONLNdπ
‰
)fle’s °dONLNdΩ
Òä
˝∏(
˙ä
bounding rR`°dONLNd«
Ò∏
˝
).ectangle and calls R`°dONLNd⁄
Ò

˝
M)SDrawPictureR`°dONLNdÂ
Ò
M
˝
t)B     with a r$¿°dONLNdÓ
Ò
t
˝
˝)'ectangle that scales the pictur˜ °dONLNd
Ò
¸
˝)àe .
°dONLNd
˛ä
ì(äprG °dONLNd
˛î

m)
3oportionally and centers it in a 120-by-12-pixel ar-`°dONLNdD
˛
m

{)Ÿea. .°dONLNdIäû(äThe °dONLNdMû
)kFormatListFormat°dONLNd^


)f (°dONLNd`


.)'fmts'°dONLNdf
.
–)$&) format is a virtual format that is rR`°dONLNdå
–)¢ead but never .
°dONLNdöä)
v(&ä<written. It is a list of all the formats and their lengths. `°dONLNd÷
w))Ì$Applications can use this format in .°dONLNd˙*ä6¬(3äplace of the °dONLNd    *¬6
")8EditionHasFormat°dONLNd    *
"6
Ü)` function (described in °dONLNd    /*
Ü6
˛)d“Choosing Which Edition .
°dONLNd    G7äC˚(@äFormat to Read” on page ˙†°dONLNd    _7˚C
)q2-41NÄ°dONLNd    c7
C
>)), which pr;‡°dONLNd    n7
>C
o)0ovides a pr)Ä°dONLNd    y7
oC
˚)1 ocedural interface to determine °dONLNd    ôDäP’(Mäwhich formats ar¶¿°dONLNd    ©D’P
)Ke available..°dONLNd    ∂Väb˜(_äIf your application can rR`°dONLNd    œV˜b
9)mead two or mor$¿°dONLNd    ›V
9b
≈)B e of the available formats, use $¿°dONLNd    ˝V
≈b
È)å'fmts'$¿°dONLNd
V
Èb
ˆ)$ to °dONLNd
cäo
…(läHdetermine the priority of these formats for a particular edition. The orR`°dONLNd
Oc
…o
Â(l
…der of R`°dONLNd
Vc
Âo    )'fmts'R`°dONLNd
\c    o)$
 .
°dONLNd
]pä|ç(yä
rE°dONLNd
^pé|ò)efl`°dONLNd
apô|≈)ects the orÏÄ°dONLNd
lp≈|
E),der in which the formats wer#°dONLNd
àp
F|
p)Å
e written.ˇt@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-26    )BUsing the Edition Manager4^*¿
¯
.°dONLNd\lhÄ(elThe ,
Courier°dONLNd\Äh‡)FormatsAvailable°dONLNd\‡h
#)` data type defi°dONLNd#\
#h
?)Cnes a rR`°dONLNd*\
?h
Q)ecor$¿°dONLNd.\
Qh
z)
d for the $¿°dONLNd8\
zh
û))'fmts'$¿°dONLNd>\
ûh
¬)$ format.°dONLNdGsl
P(|l&TYPE FormatsAvailable = ARRAY[0..0] OF°dONLNdoÅ~ç¢+RECORD°dONLNdxèêõ¿+theType:°dONLNdÑèÿõ
)HFormatType;°dONLNdîè
2õ
⁄)Z{format type for an edition}°dONLNd≥ùê©Ã(¶ê
theLength:°dONLNd¡ùÿ©
)HLongInt;°dONLNdŒù
2©
‘)Z{length of edition format }°dONLNdı´
2∑
\*{ type}°dONLNd˛π~≈ñ(¬~END;°dONLNd
—l›
u(⁄l9For example, an edition container may have a format type °dONLNd
<—
u›
ô(⁄
u'TEXT'°dONLNd
B—
ô›
ı)$ of length 100, and a °dONLNd
Xfilͧ(Álformat type °dONLNd
dfi§Í»)8'styl'°dONLNd
jfi»Í
)$ of length 32. !†°dONLNd
yfi
Í
)<
Aï°dONLNd
zfi
Í
fi)2 subscriber to this edition can open it and then rg`°dONLNd
¨fi
fiÍ
Ò)”ead ˇˇr⁄°dONLNd
∞Îl˜¥(Ùlthe format type ˇ˛Xéÿé°dONLNd
¿Î¥˜ÿ)H'fmts'ˇˇr⁄ÿé°dONLNd
ΔÎÿ˜
≥)$5 to list all available formats. In this example, it r'r°dONLNd
˚Î
¥˜
¯)‹eturns 16 bytes: °dONLNd¯l
ê(

l'TEXT'°dONLNd¯ê
¬)$ $00000064 °dONLNd¯¬
Ê)2'styl'°dONLNd#¯Ê

)$ $00000020.


"*
)
¯4
#*
)
¯ 
$l
$
¯

ˇ·ˇ‚7^.
°dONLNd0
l
#“(
lOpening an Editionˇˇˇˇˇˇ‘@(

Ò
2
.°dONLNdD
)l
5±(
2lFor a publisher¬†°dONLNdS
)∞
5◊)D
, use the ¬†°dONLNd]
)◊
5
+)'OpenNewEdition¬†°dONLNdk
)
+
5
ı)T0 function to initiate the writing of data to an .
°dONLNdõ
6l
Bã(
?leditionø`°dONLNd¢
6ã
B
B)+. (Note that the edition container must alrÕ‡°dONLNdÕ
6
B
B
á)∑eady exist befor|°dONLNd›
6
à
B
È)Fe you initiate writing; °dONLNdı
Cl
O|(
Llsee –@°dONLNd˘
C|
Oå)“Cr¨@°dONLNd¸
Cå
O
e)0eating the Edition Container” beginning on page \`°dONLNd,
C
f
O
x)⁄2-32∞@°dONLNd0
C
x
O
}).).°dONLNd3
Zl
f‰(
clerr := OpenNewEditio°dONLNdG
Z‰
f)xn(°dONLNdI
Z
f
ò)publisherSectionH, fdCreator°dONLNde
Z
ò
f
û)®
,°dONLNdn
hÍ
t(
qÍ
 °dONLNdo
h
tˆ)
p°dONLNdp
hˆ
t
º)!ublisherSectionDocument, refNum);ˇˇe¯°dONLNdí
Äl
å(
âlThe ˇ˛1˯°dONLNdñ
Ä
åÂ)publisherSectionHˇˇe¯¯°dONLNdß
ÄÂ
å
≤)f/ parameter is the publisher section that you arË°dONLNd÷
Ä
≤
å
˜)Õe writing to the °dONLNdÁ
çl
ô¶(
ñledition. The °dONLNdÙ
ç¶
ô‹):    fdCreator°dONLNd˝
ç‹
ô
F)6 parameter is the Finde°dONLNd
ç
F
ô
P)jr c°dONLNd
ç
P
ô
T)

rR`°dONLNd
ç
T
ô
“)eator type of the new editioR`°dONLNd4
ç
“
ô
‹)~n. .
°dONLNd7
öl
¶Ç(
£l(The †°dONLNd<
öÉ
¶÷)edition container fiÀ@°dONLNdP
ö÷
¶Ï)Sle alr™†°dONLNdV
öÏ
¶
%)eady has a cr‚¿°dONLNdc
ö
%
¶
œ)9'eator type; you can specify the same crs °dONLNdä
ö
–
¶
Ë)´eator °dONLNdê
ßl
≥‹(
∞ltype or establish a new cr‹`°dONLNd™
ß‹
≥
O)peator type for the edition.)ˇˇ™™.°dONLNd«
πl
≈(
¬lThe ˇ˛ˇ˛*™°dONLNdÀ
πÄ
≈
)publisherSectionDocumentˇˇ™™*™°dONLNd„
π

≈
=)ê     paramete’T°dONLNdÏ
π
=
≈
`)-r specifi˛°dONLNdı
π
a
≈
o)$es t*®°dONLNd˘
π
p
≈
¯)he document that contains the .
°dONLNd
Δl
“ñ(
œl    publisherÓ‡°dONLNd 
Δï
“
)). This parameter is used to crS`°dONLNd>
Δ

“
T)Äeate an alias fr°°dONLNdN
Δ
T
“
‹)?om the edition to the publisher °dONLNdm
Δ
fi
“
Á)ä’s .°dONLNdp
”l
flÕ(
‹ldocument. If you pass °dONLNdÜ
”Õ
flfl)aNIL!†°dONLNdâ
”fl
fl) for !†°dONLNdé
”
fl
Ä)publisherSectionDocument!†°dONLNd¶
”
Ä
fl
Ï)ê, an alias is not made in °dONLNd¿
‡l
Ï®(
Èlthe edition fi°dONLNdŒ
‡®
Ï )<le. The °dONLNd÷
‡ 
ÏÓ)"refNum°dONLNd‹
‡Ó
Ï
&)$ parameter rR`°dONLNdË
‡
&
Ï
Y)8eturns the r$¿°dONLNdÙ
‡
Y
Ï
k)3efer˜ °dONLNd¯
‡
j
Ï
Ê)ence number for the edition.°dONLNd
Úl
˛±(
˚lFor a subscriber¬†°dONLNd%
Ú∞
˛◊)D
, use the ¬†°dONLNd/
Ú◊
˛
)'OpenEdition¬†°dONLNd:
Ú

˛
à)B function to initiate the rï°dONLNdU
Ú
à
˛
‘)oeading of data frg`°dONLNdf
Ú
‘
˛
„)Lom .
°dONLNdj
ˇlõ(lan edition..°dONLNdvl"“*err := OpenEditio°dONLNdá“"fi)fn(°dONLNdâfi"
Ü)subscriberSectionH, refNum);°dONLNd¶.l:Ä(7lThe °dONLNd™.Ä:Ï)subscriberSectionH°dONLNdº.Ï:
ó)l' parameter is a handle to the section rR`°dONLNd„.
ó:
©)´ecor$¿°dONLNdÁ.
©:
„)d for a given °dONLNdı;lG§(Dlsection. The °dONLNd;§G»)8refNum°dONLNd;»G
)$ parameter rR`°dONLNd;
G
3)8eturns the r$¿°dONLNd ;
3G
E)3efer˜ °dONLNd$;
DG
¿)ence number for the edition..
°dONLNdAMlYÆ(VlThe user may r‰@°dONLNdOMÆY
_)B'ename or move the edition in the Finder’¿°dONLNdvM
_Y
{)±. BeforIÄ°dONLNd}M
|Y
¡)e writing to or rµ`°dONLNdéM
¡Y
˜)Eeading data °dONLNdöZlfs(clfrò‡°dONLNdúZsf
*)(om an edition, the Edition Manager verifiÀ†°dONLNd≈Z
*f
¿)∑#es the name of the edition. This pr„`°dONLNdËZ
¿f
„)ñ    ocess is °dONLNdÒglso(pl
rE°dONLNdÚgpsÑ)eferr„¿°dONLNd˜gÑs®)    ed to as >°dONLNdg©sÕ)%synching°dONLNdgŒs˙)%
 or synchr%@°dONLNdg˙s
m),onization. Synching ensur°dONLNd+g
ms
Á)ses that the Edition Manager0°dONLNdFg
Ës
Ò){’s °dONLNdItlÄ„(}lexisting edition names corr+†°dONLNddt‰Ä
?)xespond to the FinderäÄ°dONLNdxt
@Ä
Ë)\&’s existing edition names by updating °dONLNdûÅlçì(äl    the contrõ‡°dONLNdßÅìç∏)'    ol block.ˇ5‚@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-27
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

jHp4jHp käk

ˇ·ˇ‚7^°dONLNd\äj”(fäFormat Marksˇˇˇˇˇˇ‘@(f
2
°dONLNdpä|
Õ(yäIEach format has its own mark. The mark indicates the next position of a r¢Ä°dONLNdWp
Õ|(y
Õead or write °dONLNdd}äâ‹(Üäoperation. Initially¨†°dONLNdx}€â
{)Q&, a mark automatically defaults to 0. ‡°dONLNdû}
|â
ô)°After rp†°dONLNd•}
ôâ)eading or writing data, the °dONLNd¡ääñ
x(ìä9format mark is set past the last position written to or r¢Ä°dONLNd˙ä
xñ
ë)Óead fr ¿°dONLNd
ä
íñ)om. The mark is similar to °dONLNd
ó䣑(†äthe File Manager÷@°dONLNd
+ó’£)K’s currâÄ°dONLNd
2óÒ£
)ent r´‡°dONLNd
7ó
£
 ).ead or write position marker for a data fork. ^‡°dONLNd
eó
 £    )≈Any time that .°dONLNd
s§ä∞
,(≠ä&an edition is open (after calling the ,
Courier°dONLNd
ô§
,∞
n)¢OpenEdition°dONLNd
§§
n∞
ç)B or the °dONLNd
¨§
ç∞
·)OpenNewEdition°dONLNd
∫§
·∞)T function), .
°dONLNd
Δ±äΩ
z(∫ä7any of the marks for each format can be queried or set.!‡°dONLNd
˝±
{Ω
})Ò
 °dONLNd
ˇ√äœê(Ãä
Tµ¿°dONLNd√蜻)o set the curr†°dONLNd√…œ
Ω):9ent mark for a section format to a new location, use the .°dONLNdG–ä‹
(ŸäSetEditionFormatMark°dONLNd[–
‹
+)x
 function.°dONLNdfÁäÛ
&(äerr := SetEditionFormatMar°dONLNdÄÁ
&Û
2)úk(°dONLNdÇÁ
2Û
»)whichEdition, whichFormat°dONLNdõÁ
»Û
Œ)ñ
,°dONLNd¶ı
,


2(˛
,
 °dONLNdßı
2


8)
s°dONLNd®ı
8


t)
etMarkTo);ˇˇí°dONLNd≥
ä
ê(
ä
Tï°dONLNd¥
è
ª)o get the cf∂°dONLNdø
º
…)-urr9°dONLNd¬
…
Í)ent mar)®°dONLNd…
Î
ˆ)"k f:°dONLNdÃ
˜

l)or a format in an edition fiΩ¶°dONLNdË

l

õ)ule, use the ˇˇ—∂è\°dONLNdÙ

ú
)0GetEditionFormatMarkˇˇíè\°dONLNd

)x
 .
°dONLNd    
ä
&±(
#ä    function..°dONLNd
1ä
=
&*err := GetEditionFormatMar°dONLNd-
1
&
=
2)úk(°dONLNd/
1
2
=
»)whichEdition, whichFormat°dONLNdH
1
»
=
Œ)ñ
,°dONLNdS
?
,
K
2(
H
,
 °dONLNdT
?
2
K
8)
c°dONLNdU
?
8
K
Ä)urrentMark);


jH
q4
kH
q 
lä
l

ˇ·ˇ‚7^.
°dONLNdc
]ä
k‹(
gäReading and W˘@°dONLNdp
]‹
k
:)Rriting Edition Dataˇˇˇˇˇˇ‘@(
g
2
°dONLNdÖ
qä
}ï(
zäThr °dONLNdá
qñ
}„)e Edition Managel†°dONLNdó
q‰
}
)N
r allows y»†°dONLNd°
q

}
)+
o> °dONLNd¢
q

}
,)u to r¬ °dONLNd®
q
,
}
ß)ead or write data a few byteC°dONLNdƒ
q
®
}
≥)|s a°dONLNd«
q
¥
}
–)t a timA °dONLNdŒ
q
–
})e (as with a °dONLNd€
~ä
ä˛(
áädata fork of a Macintosh fi‰‡°dONLNdˆ
~˛
ä
)tle) iS °dONLNd˚
~

ä
&)nsteamÄ°dONLNd
~
&
ä
J)    d of in o
‡°dONLNd    
~
K
ä
r)%    ne block Å¿°dONLNd
~
r
ä
u)'
(’†°dONLNd
~
u
ä
z)
a’†°dONLNd
~
z
ä
†)    s with thyÄ°dONLNd
~
°
ä
Á)'e Scrap Manageá@°dONLNd+
~
Á
ä
Û)Fr). † °dONLNd/
~
Û
ä
˘)
Y`†°dONLNd0
~
˘
ä)ou °dONLNd3
ãä
óü(
îäcan r†°dONLNd8
ã†
ó
l)/ead sequentially by setting the mark to 0 and r¿†°dONLNdg
ã
l
ó
Ω)Ãepeatedly calling rD °dONLNdz
ã
æ
ó)Read, or you can °dONLNdä
òä
§“(
°äjump to a specifiZ°dONLNdõ
ò”
§‚)Ic ofÊ°dONLNdü
ò‚
§
^)fset by setting the mark ther√`°dONLNdº
ò
^
§)|%e. The Edition Manager also adds the °dONLNd·
•ä
±Œ(
Æäcapability to str‡°dONLNdÚ
•œ
±)EFeam multiple formats by keeping a separate mark for each format. This °dONLNd8
≤ä
æ
˚(
ªäTallows you to write a few bytes of one format and then write a few bytes of another °dONLNdå
øä
À‰*format, and so forth.°dONLNd¢
—ä
›
ø*EOnce you have opened the edition container for a particular publisher’ °dONLNdÁ
—
æ
›(
⁄
æ, you can begin .°dONLNd˜
fiä
Í
.(
Áä%writing data to the edition. Use the °dONLNd
fi
.
Í
v)§WriteEdition°dONLNd(
fi
v
Í)H% function to write publisher data to .
°dONLNdM
Îä
˜π(
Ùäan edition..°dONLNdYäˆ*err := WriteEditio°dONLNdkˆ
)ln(°dONLNdm
)-whichEdition, whichFormat, buffPtr, buffLen);°dONLNdõä&û(#äThe °dONLNdüû&Ê)WriteEdition°dONLNd´Ê&
])H function writes the specifi°dONLNd«
]&
Î)w ed format (beginning at the currR`°dONLNdÁ
Î&)é    ent mark °dONLNd'ä3Ù(0äfor that format type) frR`°dONLNd'Ù3
#)j
om the buf$¿°dONLNd'
#3
Å)/fer pointed to by the $¿°dONLNd('
Å3
´)^buffPtr$¿°dONLNd/'
´3
˜)* parameter up to °dONLNd@4ä@¥(=äbuffLen°dONLNdG4¥@”)* bytes. .
°dONLNdPFäR(OäUAfter you open the edition container for a subscriber and determine which formats to .°dONLNd•Sä_é*
rR`°dONLNd¶Sé_Δ)ead, use the R`°dONLNd≥SΔ_
)8ReadEditionR`°dONLNdæS
_
?)B function to r$¿°dONLNdÃS
?_
é)7ead edition data.°dONLNdfijäv(säerr := ReadEditio°dONLNdÔjv¸)fn(°dONLNdÒj¸v
)-whichEdition, whichFormat, buffPtr, buffLen);ˇÿ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-28    )BUsing the Edition Manager4^*¿
¯
.°dONLNd\lhÄ(elThe ,
Courier°dONLNd\Äh¬)ReadEdition°dONLNd\¬hÓ)B function rR`°dONLNd\Óh
x),eads the data with the specifiR`°dONLNd8\
xh
™)äed format (R`°dONLNdC\
™h
Ï)2whichFormatR`°dONLNdN\
Ïh
Ú)B) °dONLNdPilut(rlfrR`°dONLNdRituÏ)om the edition into the buf$¿°dONLNdmiÏu˘)xferg`°dONLNdpi¯u
). The g`°dONLNdvi
u
S)ReadEditiong`°dONLNdÅi
Su
ù)B function begins r9¿°dONLNdìi
ùu
‹)Jeading at the °dONLNd°vlÇ}(lcurrR`°dONLNd•v}Ç
;)+ent mark for that format and continues to r$¿°dONLNd–v
;Ç
f)æ
ead up to $¿°dONLNd⁄v
fÇ
ê)+buffLen$¿°dONLNd·v
êÇ
‚)* bytes. The actual °dONLNdÙÉlè∑(ålnumber of bytes rR`°dONLNd
É∑èÿ)Kead is r$¿°dONLNd
Éÿè
)!eturned in the $¿°dONLNd
É
è
C)AbuffLen$¿°dONLNd
#É
Cè
u)*
 parameterg`°dONLNd
-É
tè
£)1. Once the g`°dONLNd
8É
£è
Õ)/buffLeng`°dONLNd
?É
Õè
œ)*
 .
°dONLNd
@êlú†(ôlparameter rV°dONLNd
Kê†ú
ç)45eturns a value smaller than the value you have specifiƒÄ°dONLNd
Åê
çú
Æ)Ìed, therL@°dONLNd
âê
Øú
Õ)"e is no .°dONLNd
ëùl©«(¶ladditional data to rR`°dONLNd
•ù«©
)[ead, and the R`°dONLNd
≤ù
©
D);ReadEditionR`°dONLNd
Ωù
D©
p)B function r$¿°dONLNd
»ù
p©
ï),    eturns a $¿°dONLNd
—ù
ï©
≥)%noErr$¿°dONLNd
÷ù
≥©
π) r˜ °dONLNd
ÿù
∏©
È)esult code. 

∑*≈
¯4∏*≈
¯
    .
°dONLNd
Â∂l¡(ælNote

ˇ·ˇ‚7^
°dONLNd
Í√lœÖ*The TˆÄ°dONLNd
Ô√Ñœ
®)Franslation Manager (if it is available) attempts implicit translation °dONLNd5œl€µ(ÿlunder certain cirv¿°dONLNdFœµ€
Ü)I/cumstances. For instance, it does so when your °dONLNdu€lÁÿ(‰lapplication attempts to r◊†°dONLNdé€ÿÁ·)lea°@°dONLNdꀂÁÒ)
d frU‡°dONLNdî€ÚÁ
)om a`°dONLNdò€
Á
))n editiofi¿°dONLNd†€
)Á
6)!n a0 °dONLNd£€
7Á
©) format type that is not in °dONLNdøÁlÛï(l
the editioK`°dONLNd…ÁñÛfl)*n. In this case, th`°dONLNd‹Á‡ÛÌ)Je Tî¿°dONLNdflÁÏÛ
q)ranslation Manager attempts tË°dONLNd¸Á
qÛ
x)Öo °dONLNd˛Ûlˇo(¸l
t¬`°dONLNdˇÛoˇî)    ranslate 7¿°dONLNdÛïˇ„)&the data into the rá@°dONLNdÛ„ˇ
S)Nequested format. For mor˜†°dONLNd3Û
Sˇ
î)pe information, °dONLNdBˇl
|(
lsee –@°dONLNdFˇ|
å)the -†°dONLNdJˇç
ª)
chapter “T*¿°dONLNdTˇª

$).ranslation Manager” in QÄ°dONLNdkˇ
$

n)iInside Macintosh: °dONLNd}
l
}(
lMorÄ°dONLNdÄ
~
Ñ)e z °dONLNdÇ
Ñ
±)
Macintosh ͆°dONLNdå
±
∑)-
T͆°dONLNdç
∂
œ)oolbox£†°dONLNdì
–
“)
.,Zapf Dingbats#†°dONLNdï
ÿ
fi)
u


4*
;
¯4
5*
;
¯ 
6l
6
¯

ˇ·ˇ‚7^°dONLNdô
'l
5Ã(
1lClosing an Editionˇˇˇˇˇˇ‘@(
1
Ò
2
.°dONLNd≠
;l
G¶(
DlWhen you arR`°dONLNd∏
;¶
G
):e done writing to or r$¿°dONLNdŒ
;

G
C)\eading data fr˜ °dONLNd‹
;
B
G
™)@om an edition, call the ˜ °dONLNdÙ
;
™
G
Ú)hCloseEdition˜ °dONLNd
;
Ú
G
Ù)H
 .
°dONLNd

Hl
Tì(
Ql    function..°dONLNd
_l
kÿ*err := CloseEditio°dONLNd
_ÿ
k‰)ln(°dONLNd
_‰
k
Ä)whichEdition, successful);.
°dONLNd:
wl
É
◊(
ÄlOEach time a user edits a publisher within a document, you must update the modifi5`°dONLNdä
w
ÿ
É
ı(
Ä
ÿcation °dONLNdë
Ñl
ê¬(
çldate in the section rÏ`°dONLNd¶
Ѭ
ê‘)Vecor`¿°dONLNd™
Ñ’
ê
Ô)Ad (even if the data is not yet written). When the update mode is °dONLNdÎ
ël
ù∞(
ölset to Manually¿°dONLNd˙
ë∞
ù
)D, the user can compar3°dONLNd
ë

ù
C)^e the modifi4`°dONLNd
ë
C
ù
fi)5%cation dates for a publisher and its °dONLNd@
ûl
™
_(
ßl6edition in the publisher options dialog box. One modifi °dONLNdw
û
`
™
Ë)Ùcation date indicates when the °dONLNdñ
´l
∑∂(
¥lpublisher last wr0°dONLNdß
´∑
∑
w)K,ote data to the edition, and the other modifiŒ†°dONLNd‘
´
w
∑
Ô)¿cation date indicates when °dONLNdÔ
∏l
ƒ
(
¡l&the publisher section was last edited..°dONLNd
 l
÷à*If the °dONLNd
 à
÷ƒ)
successful°dONLNd'
 ƒ
÷
G)< parameter for a publisher is °dONLNdE
 
G
÷
_)ÉTRUE°dONLNdI
 
_
÷
v), the °dONLNdO
 
v
÷
æ)CloseEdition°dONLNd[
 
æ
÷
Ê)H
 function .
°dONLNde
◊l
„
Ø(
‡lHmakes the newly written data available to subscribers and sets the modifiH¿°dONLNdÆ
◊
∞
„
Ó(
‡
∞cation date in ˇˇ√6.°dONLNdΩ
‰l
}(
Ìlthe ˇˇI¢C6°dONLNd¡
‰~
¢)mdDateˇˇ√6C6°dONLNd«
‰¢
™)$ fil°dONLNd 
‰´

)    eld of the edition to corr®⁄°dONLNd‰
‰


q)kespond to the modifiÚ|°dONLNd¯
‰
q

Ó)[cation date of the publisherº¥°dONLNd
‰
Ô

˜)~’s .
°dONLNd
Òl
˝ë(
˙l    section r≠Ä°dONLNd 
Òë
˝£)%ecor!‡°dONLNd$
Ò§
˝
)d. If the two dates difk`°dONLNd;
Ò

˝
)^feræ °dONLNd>
Ò

˝
Ù)4, the Edition Manager sends a Section Read event to °dONLNdr
˛l
ã(lall currˇ¿°dONLNdz
˛ã
œ)ent subscribers.ˇˇÏN.°dONLNdãlá(lIf the ˇˇƒÍXú°dONLNdíàƒ)
successfulˇˇÏNXú°dONLNdúƒ
F)< parameter for a subscriber is ˇˇƒÍ‚p°dONLNdª
F
^)ÇTRUEˇˇÏN‚p°dONLNdø
^
t), the ˇˇƒÍª°dONLNd≈
u
Ω)CloseEditionˇˇÏNª°dONLNd—
Ω
˜)H function sets .
°dONLNd‡l)ô(&l    the modifi7¿°dONLNdÍö)
).cation date of the subscriber=`°dONLNd
)
E)}’s section rÔ °dONLNd
E)
W).ecorcÄ°dONLNd
X)
})    d to corr‘Ä°dONLNd 
})
ÿ)%espond to the modifiØÄ°dONLNd4
Ÿ)
ˆ)\cation °dONLNd;*l6ø(3ldate of the edition..°dONLNdP<lH‚*If you cannot successfully rR`°dONLNdl<‚H˝)vead fr$¿°dONLNdr<˝H
©)(om or write data to an edition, set the $¿°dONLNdö<
©H
Â)¨
successful$¿°dONLNd§<
ÂH
Á)<
 ˇˇí™°dONLNd•IlU®(Rlparameter to ˇ˛∑˛•T°dONLNd≤I®UΔ)<FALSEˇˇí™•T°dONLNd∑IΔU
). For a publisherüÚ°dONLNd»I
U
˜)H:, data is not written to the edition, but it should still .
°dONLNd    Vlb
ı(_lWbe saved with the document that contains the section. When the document is next saved, °dONLNd    Yclo
#*+data can then be written to the edition. SeœÄ°dONLNd    Ñc
#o
*)∑e  °dONLNd    Üc
+o
Ñ)“Closing an Edition ò`°dONLNd    öc
Ño
–)YAfter Reading or .°dONLNd    ´pl|w(yl
W¬†°dONLNd    ¨pv|ª)
riting” on page ¬†°dONLNd    ºpª|Œ)E2-88¬†°dONLNd    ¿pŒ|‘) f¬†°dONLNd    ¬p‘|
i)!or additional information on the ¬†°dONLNd    „p
i|
±)ïCloseEdition¬†°dONLNd    Ôp
±|
⁄)H
 function.ˇH@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-29
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

kHr4lHr mäm

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\äk
(gäCreating a Publisherˇˇˇˇˇˇ€r(g
2
°dONLNdrä~ê({ä
Y@Ä°dONLNdrê~˘)ou need to support a CrD@°dONLNd.r˘~)i:eate Publisher menu command in the Edit menu. When a user °dONLNdhäã
Y(àä.selects a portion of a document and chooses Cr¿‡°dONLNdñ
Yã
°)œeate Publisher fr„ °dONLNdß
°ã
ˆ)Hom this menu, you °dONLNdπåäò
m(ïä3should display the publisher dialog box on the userÃ`°dONLNdÏå
nò
Ñ)‰’s scr¬‡°dONLNdÚå
Ñò
∂)een. The Cr?@°dONLNd˝å
∑ò)3eate Publisher menu °dONLNd
ôä•›(¢äcommand should rO°dONLNd
!ôfi•
Ì)T<emain dimmed until the user selects a portion of a document..°dONLNd
^´ä∑Ø(¥äUse the ,
Courier°dONLNd
f´Ø∑
)%NewPublisherDialog°dONLNd
x´
∑)l5 function to display the publisher dialog box on the °dONLNd
≠∏äƒú(¡äuser=`°dONLNd
±∏ùƒ≤)’s scr¿°dONLNd
∑∏≤ƒ
N)%een. This function is similar to the ¿°dONLNd
‹∏
Nƒ
ú)úCustomPutFile¿°dONLNd
È∏
úƒ
®)N pr‚ °dONLNd
Ï∏
߃
ƒ)ocedur¥Ä°dONLNd
Ú∏
ƒƒ)e described in the .
°dONLNd≈ä—≤(Œä    chapter “B`°dONLNd≈≥—’))Standarv†°dONLNd≈’—
)"d File PackagT°dONLNd"≈
—
');e” in ◊`°dONLNd(≈
'—
Ñ)Inside Macintosh: Filesû@°dONLNd?≈
Ö—
á)^
..°dONLNdA‹äË
(Âäerr := NewPublisherDialo°dONLNdY‹
Ë
&)êg(°dONLNd[‹
&Ë
P)reply);.
°dONLNdcÙä

1(˝ä&The dialog box contains space for a prø°dONLNdâÙ
1
)ß0eview (a thumbnail sketch) of the edition and a °dONLNdπ

ä
Ù(

äspace for the user to typû@°dONLNd“

Ù
˛)je t*@°dONLNd’

ˇ
)=he name of the edition in which to write the publisher data. °dONLNd
ä
¢(
äFigurR¿°dONLNd
¢
∂)e 2-1c†°dONLNd
∂
ª)
1c†°dONLNd
ª

s)+ illustrates a sample publisher dialog box.


<H
M4
=H
M"
=H]

ˇ·ˇ‚7^
    °dONLNdJ
2ä
=∫(
:äFigure 2-11°dONLNdV
2Ã
=“)B
A0°dONLNdW
2“
=
D) sample publisher dialog box
.°dONLNdu
Ôä
˚û(
¯äThe °dONLNdy
Ôû
˚

)NewPublisherDialog°dONLNdã
Ô


˚
x)l function displays the prR`°dONLNd§
Ô
x
˚
§)n    eview (pr$¿°dONLNd≠
Ô
§
˚
”),
ovided by .
°dONLNd∑
¸ä°(äyour ˛`°dONLNdº
¸°
—)Gapplication), displays a text box with the default name of the edition °dONLNd    äó(ä(prõ°dONLNd    ó∏)ovided  @°dONLNd    πΔ)"by ∑°dONLNd    Δ›)your 5`°dONLNd    fi
Ê)?application), and handles all user input until the user clicks °dONLNdUä"≠(äPublish wÄ°dONLNd]Æ"⁄)$
or Cancel.†Ç†é


Pä
◊
÷ò@0
˛0
˛
Pä
o
÷¬ˇ¸Ä√Ä√ü√ˇÏü√ˇÃò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√LòÔ˘
ˆˇ¸ÎLòÊ
ˆÎLòÔ˘
ˆÎLòÊ
ˆÎLòÔ˘
¿
3¿˝ÎL'ò¸Ä0
?ÅÄ0¸ˆ

IJ|¿L*ò¸
¿ˆ˘
AÅÛ<«èáˆ

IJf¿L-ò¸Õû31„3Ú
¸AÉ3˛ÃÅˇΔ¯ˇ¡Éœ¯ffiyÁÄL.ò¸
Œ¸3˚˘
A„3ÃÃŒˇÜ¯!ÜlÕfÊû¿L*ò¸
å¸3Ú
AÉ3Ãë¯!Ülï|Δë¿L1ò¸?33Û3˚˘

AÉ3ÃÃ√Ä>¯!ÜlÕò`Δ¸Ã¿L-ò¸0333Ú

AÉ3ÃÅį!ÜlÕò`Δ¿Ã¿L1ò¸1232˚˘
¡ÒÛ«å«¯ˇ¡ÜlÕò`ΔƒÃ¿L&ò¸<1„¸Ú
ˇ¿˘ˆ
ÛÃï`Δxg¿LòÔ˘
ˆÎLòÊ
ˆÎLòÔ˘
ˆÎLòÊ
ˆˇ˛ÎLòÔ¯ˆˇ˛ÎLò√L
òÔ÷Lò√L
òÔ÷LòÌ?ÁˇÛLòÔ ÈÛLòÌ ÈÛLòÔ È˘ˇ˛LòÌ ˝00Û(˘
ÄL!òÔ ‡˛00ÛD¯ÄL òÌ!Ä1·¿><xÙÇ ¯@L"òÔ!@#33 fF1Ù    
 ¯@L&òÌ!@33Äf>0¯Ù«ê *Ä@L(òÔ!@33Ò¿ff1òÙD 
@@L&òÌ!@33‡ff1òÙD  †¢Ä@Lò@0`
˛0`
˛
oä
é
÷'òÔ!@33`ff1òÙD ˛˛@L&òÌ!@1·¿>>¯Ù| (àÄÄ@LòÔ ˇÄÎ Q
˛@LòÌ È      ˛Ä@LòÔ Èˇ 
˛@LòÌ È *††Ä@LòÔ È ˛¸@LòÌ È ˛à¸@L ò˜

Ä˚ È ˛P¸@L#ò˜

¿˘ ™Ä ˚ı¯ÄL%òˆ†˚!U@˚
ı˘
ÄL'òˆ˘ ÄÄ

 †Ä(˛†
¢Äˆ˘ˇ˛L"òˆX˚
!@
Q˛AıÛL òˆL˘ ÄÄ
""Ä ˛àÇıÛL"òˆD˚!@Q@AQ
ıÛL#ò˘
Ģ ÄÄ""† ÄààÇıÛL%ò˘
¿"˚!U@˛@A

ıÛL#ò¯#˘ ™Ä

 †Ä ˛†
ÄĈÛLò¯f!˚ ˘
ÚÛLò¯#!Ä˙ ¯ÄÛÛLò¯10∞¸ È˘ˇ˛Lò¯Ä∞˙ È˘
ÄLò¯¿∞¸ ȯÄLò˙
¯`˙ È ¯@L ò˙0¿¸ È ¯@L$ò˙
√à¿˙ È ¯
Ä¿˛@L%ò˘`‡ĸ È Ã
Ä¿˛@L#ò˙px˘ È Ãxqô„«¿@L'ò˚
¿¸ È ÃÃ…∞Δf`@L%ò˚˙ È Ã÷‡Δf`@L'ò˚˛¸ È øq¿Δf`@L&ò˚¯0˚ È ÿ9‡Δf`@L(ò˚ 0˝ È Ãô∞Δf`@L&ò˚?ć `˚ È ¯xqòc«¿@L%ò˚88¿˝ È ˚@L ò¯
Ä˚ È ˚@L!ò˘‡¬@{¿˛ È ¯@Lò˘>`¿
˚ ȯÄL!ò˘É0Ä
ú˝ È˘
ÄLò¯·˚ È˘ˇ˛Lò¯0Ã|˝ ÈÛLò˙˛F˚ ÈÛLò˙<¯c
IJ ÈÛLò˙‡!˛¿¸ ÈÛLò˚
Ä1Ä`˛ ÈÛLò˚˛Ä0¸ ÈÛLò˚¸0@¸˛ ÈÛL"ò˚¯ @¸ È˘ˇ˛Lò@`ê
˛`ê
˛
éä
≠
÷$ò˚`@
Δ˛ È˘
ÄL ò˙0p
¿@b¸ ȯÄL%ò˙`¿@@2˛ È ˚@L&ò¸√ɲ¸ È ¸
@L*ò¸ܲ¯˛ È Dzˇ¯@L(ò¸v)å˛≥¸ È ¬˛@L*ò¸ƒ—˛†˛ È ‚<f`@L(ò¸    ç:6ú¿¿¸ È Úff`@L+ò˝

&Ë0ê¿`˛ È ∫ff`@L(ò¸    ì`Ñ0 ¸ È û~f`@L+ò˝

@É`>0˛ È é`f`@L)ò˝
&Å¿¿ò–¸ È Übf@@L+ò˝

hDÄ@Éx˛ È Ç<Ä@L'ò˝
¿¿74Ä@
Ѹ È ¸@L*ò˛
Ä≈ÄCëÙ˛ È ¸ˇ¸@Lò˘5lÅú˚ È ¯@L%ò˛
$2 ô#˝ ȯÄL#ò˝    H .˚ È˘
ÄL$ò˝@ x¸ È˘ˇ˛Lò˝Ä
 p˙ ÈÛLò˝&Äì4`¸ ÈÛLò˛
!.ÖĢ ÈÛLò˛@Å˚ ÈÛLò˛
Å@¿d˘ ÈˇÛL ò˛

ãÄÄ˝ ÈÛLò˛

#˛¿˚ ÈÛLò¸

l˛ ˝ È|ÛLò˚ò˛0˙ ÈDÛLò˚˛`¸ ÈDÛLò˚DzÑ@˚ ÈD˜U@Lò˚˛dÄ˝ È«êÛLò˚Å˛Ä˚ È    
ÛLò˜˝ ÈÇÛLò˚
˛˚ ÈDÛLò˜
IJ È(ÛLò˙ÄYÇĸ ÈÛLò¯êIJ ÈÛLò˙@ĸ ÈÛLò˙ x¿˛?ÁˇÛLò¯¿`“Lò˙Ä1É0˛÷Lò˙"AœLò˘$    ˚‚˘ˇ˛Lò˙d)€˘
ÄLò˚ÄH
ĸ‚¯ÄLò˙0¿Ä‹ ¯@Lò¸
¿
∞ĸ‚ ¯@Lò˚¸?ÄDÄ‹ ¿˛@Lò@ê¿
˛ê¿
˛
≠ä
Ã
÷!ò¸á‡@ĸ‚  ˛@Lò¸˛Åê€ «√áå@Lò¸˛˘‚ ffLÃ@L%ò¯˜

¸8¸1åÛ ÊfÃ@L*ò¯@¸
Ѹ`¸
ÄÛ ffÃ@L/ò¯
¿˙
ƒxˇáÄx>303Ãx¯¿ˆ ff@L1ò¯v@¸    
‰åÃÿÃ`˛30331åÃÿˆ &ffLL@L.ò¯¿`˙
t|ÃÿÃ`˛30331åÃÃı √Êcáå@L*ò¯4†¸
<ÃÃœ¿Ã`3?30?31åÃÃı ¯@L(ò¯(˙

˛ÃÃ`3030031åÃÃı ¯@L+ò¯ ¸
˛Ã@Ã`313 131åÃÿˆ ¯@L&ò¯`˜
|ëÄx`3?¿0Ãxÿˆ¯ÄLò¯@˘‚˘
ÄLò¯@Ÿ˘ˇ˛Lò¯@˘÷L
ò¯@ÕLò¯@˘÷L
ò¯¿ÕLòÔ?ÁˇÛLòÌ ÁÛLòÔ ÁÛLòÌ Á¯ˇÄLòÔ Á¯ˇ‡LòÌ Á˜ˇLòÔ!Δ¸
Ú
¯¯LòÌ# ¸Ò
«˘ˇ˛8L"òÔ#«Δ<Êœ‡Ûÿ˘
ºLòÌ
#Ü˝fg˛ôêÛê¯úL òÔ!Δ˝ff˛ôÄÛ†¯\LòÌ
 Ê˛f~f˛ôÄÛ†¯\L&òÔ ˝f`f˛ôÄÛ†Ä0\L$òÌ"˝fbf˛ôêÛ†Ä0\L'òÔ!ΔfgΔ<Êüò‡Û†ôüé>\L!òÌ ˛`†˝ô3\L$òÔ `†ôôú3\LòÌ ¸
¿Ó†ôôé3\LòÔ Á†ôôá3\LòÌ Á†ôôì3\LòÔ Á†üé3\LòÌ?Áˇ†¯\LòÔ„
†¯\Lò–
†¯\LòÔ„
ê¯úLò–
ÿ˘
ºLòÔ„

«˘ˇ˛8Lò–

¯¯L
òœ˜ˇLòœ¯ˇ‡Lò@¿
˛¿
˛
Ãä
Î
÷òœ¯ˇÄLò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√Lü√ˇÃê√Ä√¬ˇ¸¬ˇ¸¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
 
˛
 
˛
Îä

÷¡¡¡,˝

Û¿¿

¯Ä˛˝
Ä ˛D¿
Ì*˝    
  Ä˝Ä¸Ä˛@@
Ì0˝*


Åáë.pÄ
·≈òá
‚'Ña≈áÃ8CáÅ·ƒ@0˝"


Äàë0àÄ

&dààÅ$D"&Hò˛DHÅ$@0˝*
‚„«¡
àë à


‰DààÅ$D"HêD<DHÅ"Ä/˝"
 

Äàë ¯‚$DàèÅ$D!ƒOê˛DHÅ!Ô0˝"
 

Äàë Ä?Ä$Dàà
$D $H˛DHÅ"Ä0˝"
  

Äàì à Å$DààÅdD"$Hê˛DHÅ$@0˝*
Û¿¿

Äáç pÄ Ä·‰Dá
·ßÑ!ƒGƒ<CáÅ·ƒ@ÚÄıÄ
ıÄÌÛ
ÄıÄ
ˆ
ÄÌ
ÛÊÏ¡¡¡¡¡¡˝
"@
Õ˝
 
åÕ˝

Ê8√ã
Tqa√«“˝
"DLÅ$âí$Hò“˝
‚"DHÅy‰Hê“˝
"DHÅâ$Oê“˝
"DHÅâ$H“˝
"DHÅâ$Hê“˝
Ò‚CàÅy„«“Ú@—Û
@—Û
Ä—¡¡¡¡,˝
à@@

 ˝a Ä
‡¸ Ô)˝
à˛@
å˛ ˝  ˙Ó1˝+
H‚",8√«
Tp„8p‚¿,p‚Á<#qá
≈ò≥,a√é0‚¿Ò1˝+
I"2DDHÅ$ââ 2!ë"!" àô&dÃë2"$D Ò1˝+
)T"@DHÅy
â "!ë"! àë$Dàë""ƒ Ò1˝+
)ÒT"8DOÅâ
à‚ "!Úë"!" àë$Dàë""D Ò1˝+
à"DH
â
à "!ë"!" àë$Dàë""D Ò1˝+
à"DDHÅââ "!ë"!" àë$Dàì""$D Ò1˝+
‡à"8C«
x·p‚""‚û<!á
·ƒDàç"!√√‚ Òϸ
 fiϸ
 fiò@
 
2
˛
 
2
˛
ä
÷¡¡¡¡¡¸ 
‡˛
˛ ‘¸ 
˛
˛ ‘¸PÒ·
≈òÒá"√Ä÷¸Pâ&dâò#$@÷¸àâ$Dâê"$’¸àâ$Dâê"$’˝
¸â$Dâ"$’˝
â$Dâ1ê"$@÷˝
Ò·
·ƒD–« "#à÷˚Å˚IJ ”˚Å˚IJ@”¡¡†è†Éˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-30    )BUsing the Edition Manager4^*¿
¯
.°dONLNd\lhs(el
Yï°dONLNd
\rh‚)ou pass a new publisher rg`°dONLNd\‚h˝)peply r9¿°dONLNd \˝h
)ecor °dONLNd$\
h
z)d as a parameter to the ,
Courier °dONLNd<\
zh
Ê)kNewPublisherDialog °dONLNdN\
Êh
Ë)l
 .
°dONLNdOiluì(rl    function..°dONLNdYÄlå
*TYPE NewPublisherReply = °dONLNdté~ö¢+RECORD°dONLNd}úꮿ+canceled°dONLNdÖú¿®Δ)0
:°dONLNdäúÿ®fi)
B°dONLNdãúfi®
)oolean;°dONLNdòú
D®
h)f{user °dONLNdûú
h®
§)$
clicked Ca°dONLNd®ú
§®
∂)<nce°dONLNd´ú
∂®
¬)l}°dONLNd∞™ê∂Δ(≥ê    replacing°dONLNdπ™Δ∂Ã)6
:°dONLNdæ™ÿ∂fi)
B°dONLNdø™fi∂
)oolean;°dONLNdÙ
D∂
»)f{user chose existing }°dONLNdÔ∏
Dƒ
J*
{°dONLNd∏
Jƒ
‡) filename for an edition}°dONLNd
Δê“∫(œêusePart°dONLNd
Δ∫“¿)*
:°dONLNd
Δÿ“fi)
B°dONLNd
Δfi“
)oolean;°dONLNd
&Δ
D“
Ú)f{always FALSE in version 7.0}°dONLNd
F‘ê‡∫(›êpreview°dONLNd
M‘∫‡¿)*
:°dONLNd
R‘ÿ‡fi)
H°dONLNd
S‘fi‡
)andle;°dONLNd
_‘
D‡
Ï)f{handle to 'prvw', 'PICT', }°dONLNd
à‚
DÓ
⁄*{ 'TEXT', or 'snd ' data}°dONLNd
§급(˘êpreviewFormat:°dONLNd
º
D¸
™)¥{type of preview}°dONLNd
‘˛ÿ

fi(
ÿ
F°dONLNd
’˛fi


)    ormatType°dONLNd
fi˛



)6
;°dONLNd
Á
ê
Δ(
ê    container°dONLNd

Δ
Ã)6
:°dONLNd
ı
ÿ

V)EditionContainerSpec;°dONLNd

V

Ú)~{initially, default name }°dONLNd8

D
&
Ï(
#
D{ and location of edition; }°dONLNda
(
D
4
Ú*{ on return, edition name & }°dONLNdã
6
D
B
Ê*{ location chosen by the } °dONLNd≥
D
D
P
‡*{ user to publish data to}°dONLNdœ
R~
^Ñ(
[~
E°dONLNd–
RÑ
^ñ)ND;°dONLNd‘
jl
vs(
sl
Yï°dONLNd’
jr
vÖ)ou fiï°dONLNd⁄
jÖ
v¨)
ll in the ï°dONLNd‰
j¨
v÷)'usePartï°dONLNdÎ
j÷
v€)*, ï°dONLNdÌ
j€
v
)preview™°dONLNdÙ
j

v
    )), ™°dONLNdˆ
j
    
v
W)previewFormat™°dONLNd
j
W
v
o)N, and ™°dONLNd    
j
o
v
•)    container™°dONLNd
j
•
v
Æ)6 fi™°dONLNd
j
Æ
v
Ù)    elds of the new .
°dONLNd%
wl
Éú(
Älpublisher rÒ@°dONLNd0
wú
ɵ)0eply ryİdONLNd6
w∂
É»)ecoṙ°dONLNd:
w»
É–)d.ˇˇé“.°dONLNd=
âl
ï±(
ílAlways set the ˇ˛¨v,v°dONLNdL
â≤
ï‹)FusePartˇˇé“,v°dONLNdS
â‹
ï‰)* fiªH°dONLNdV
â‰
ïˇ)eld to ˇ˛¨vÿÏ°dONLNd]
âˇ
ï
)FALSEˇˇé“ÿÏ°dONLNdb
â

ï
5). The ˇ˛¨vˆê°dONLNdh
â
5
ï
_)previewˇˇé“ˆê°dONLNdo
â
_
ï
g)* fiÖb°dONLNdr
â
h
ï
⁄)    eld should contain either ˇ˛¨v¿™°dONLNdå
â
⁄
ï
Ï)rNILˇˇé“bJ°dONLNdè
â
Ï
ï
¯) or °dONLNdì
ñl
¢Ó(
ülthe data to display in the prR`°dONLNd∞
ñÓ
¢

)Çeviewg`°dONLNdµ
ñ
    
¢
"). The g`°dONLNdª
ñ
"
¢
p)previewFormatg`°dONLNd»
ñ
p
¢
y)N fig`°dONLNdÀ
ñ
y
¢
Œ)    eld should contain g`°dONLNdfi
ñ
Œ
¢
Ú)U'PICT'g`°dONLNd‰
ñ
Ú
¢
˜)$, °dONLNdÊ
£l
Øê(
¨l'TEXT'°dONLNdÏ
£ê
Øï)$, °dONLNdÓ
£ï
Øπ)'snd '°dONLNdÙ
£π
Ø…)$, or °dONLNd˘
£…
ØÌ)'prvw'°dONLNdˇ
£Ì
Ø)$
.°dONLNd

µl
¡è(
ælSet the °dONLNd    
µè
¡≈)#    container°dONLNd
µ≈
¡Œ)6 fi°dONLNd
µŒ
¡
ˆ)    Celd to be the default name and folder for the edition. The default .
°dONLNdX
¬l
Ϋ(
Àlname should rC °dONLNde
¬
Œ∂)@eflÄ°dONLNdh
·
Œ
`)'ect the data contained in the publishero‡°dONLNdè
¬
_
Œ
Ú)®#. For example, if a user publishes °dONLNd≤
œl
€
Ÿ(
ÿlVa bar chart of sales information entitled “sales data,” then the default name for the °dONLNd
‹l
Ë
◊*Pedition could also be “sales data.” Otherwise, you should use the document name °dONLNdX
Èl
ı
€*Qfollowed by a hyphen (-) and a number to establish uniqueness. For example, your °dONLNd©
ˆl

* default name could be “January T@°dONLNd…
ˆ


*)ïotals - 3.”°dONLNd’l
€(lRIf the document has not been saved, the default name should be “untitled edition <ê °dONLNd'
€
‡(
€
n@°dONLNd(
·
Ó)>” °dONLNd+l!Ç(lwher7°dONLNd/É!ä)e Ć°dONLNd1ä!è)
n¿°dONLNd2ê!
Í)O is a number to establish uniqueness. The default folder should be the same as °dONLNdÅ"l.
(+l%the edition for the last publisher crˇ`°dONLNd¶"
.
¡)ò,eated in the same document. If this is the fiÄ°dONLNd”"
¬.
œ)ærst °dONLNd◊/l;
Œ(8lQpublisher in the document, the default folder should be the same folder that the °dONLNd(<lH∞*document is in.ˇˇe4.°dONLNd8NlZ*The ˇ˛/úÂ4°dONLNd<NZØ)canceledˇˇe4Â4°dONLNdDNØZ∑)0 fiJh°dONLNdGN∏Z
()    eld of the new publisher rðdONLNdaN
)Z
C)qeply rN`°dONLNdgN
CZ
U)ecor ¿°dONLNdkN
UZ
¯)%d indicates whether the user clicked °dONLNdê[lg§(dlCancel. The °dONLNdú[§g⁄)8    replacing°dONLNd•[⁄g„)6 fi°dONLNd®[„g
ö)    )eld indicates whether the user chose to rR`°dONLNd—[
ög
Ì)∑eplace an existing °dONLNd‰hltñ(ql    edition fi°dONLNdÓhñtÆ)*le. If °dONLNdıhÆt‰)    replacing°dONLNd˛h‰tÍ)6 rR`°dONLNdhÍt
)eturns R`°dONLNdh
t
%)FALSER`°dONLNdh
%t
P), call the R`°dONLNdh
Pt
Ï)+CreateEditionContainerFileR`°dONLNd1h
Ït
Ó)ú
 .
°dONLNd2ulÅß(~lfunction to cr{`°dONLNd@ußÅ);eate an edition fiÓÄ°dONLNdRuÅ˙)Ile.ˇ9“@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-31
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿.°dONLNd\ähû(eäThe ,
Courier°dONLNd\ûh‘)    container°dONLNd\‘h›)6 fi°dONLNd\›h
2)    eld is of data type °dONLNd$\
2h
™)UEditionContainerSpec°dONLNd8\
™h
≠)x
.°dONLNd:sä
2(|äTYPE EditionContainerSpec = °dONLNdXÅúç¿+RECORD°dONLNdaèÆõfi+theFile:°dONLNdnè
õ
,)ZFSSpec°dONLNdtè
,õ
2)$
;°dONLNdyè
Põ
˛)${record that identifies the }°dONLNd¢ù
P©
V*
{°dONLNd£ù
V©
\)
 °dONLNd§ù
\©
Ú)file to contain edition d°dONLNdΩù
Ú©
)ñata}°dONLNdƒ´Æ∑
(¥ÆtheFileScript:°dONLNd◊´
∑
D)Z
ScriptCode°dONLNd·´
D∑
J)<
;°dONLNdÊ´
P∑
V)
{°dONLNdÁ´
V∑
Ê)script code of filename}°dONLNd
πÆ≈fi(¬ÆthePart:°dONLNd
π
≈
2)ZLongInt°dONLNd
π
2≈
8)*
;°dONLNd
π
P≈
V)
{°dONLNd
π
V≈
Œ)which part of file, °dONLNd
0π
Œ≈
‘)x
}°dONLNd
=«
P”
V(–
P
{°dONLNd
>«
V”
⁄) always kPartsNotUsed}°dONLNd
W’Æ·ˆ(fiÆthePartName:°dONLNd
h’
·
&)ZStr31°dONLNd
m’
&·
,)
;°dONLNd
r’
P·
V)*
{°dONLNd
s’
V·
Ê)not used in version 7.0}°dONLNd
é„ÆÔ
(ÏÆthePartScript:°dONLNd
°„
Ô
D)Z
ScriptCode°dONLNd
´„
DÔ
J)<
;°dONLNd
∞„
PÔ
V)
{°dONLNd
±„
VÔ
Ê)not used in version 7.0}°dONLNd
ÀÒú˝¥(˙úEND;ˇˇËR°dONLNd
–
    ä
§(
äThe fihR°dONLNd
÷
    •
µ)eld ˇˇ∏ˆP§°dONLNd
⁄
    ∂
⁄)theFilP§°dONLNd
‡
    ⁄
‡)$
eˇˇËRP§°dONLNd
·
    ‡
˙) is a fi    ö°dONLNd
È
    ˚

D)le system specifi⁄>°dONLNd
˙
    
D

e)Ication rî°dONLNd
    
f

x)"ecorgP°dONLNd
    
x

Æ)d, a data strF°dONLNd
    
Ø

≈)7ucturfi¶°dONLNd
    
ƒ

 )e Δ¯°dONLNd
    
À

Ï)of type ˇˇ∏ˆóú°dONLNd"
    
Ì
)"FSSpecˇˇËRóú°dONLNd(
    
)$. .
°dONLNd*
ä
"ê(
ä
Y@Ä°dONLNd+
ê
"
?)(ou identify the edition using a volume r
†°dONLNdS

@
"
P)∞efer≠¿°dONLNdW

P
"
â)ence number5†°dONLNdb

â
"
ö)9, dir˛¿°dONLNdg

ö
"
·)ectory ID, and fiᇰdONLNdx

‚
")Hlename. °dONLNdÄ
#ä
/
Y(
,ä.When specifying an edition, follow the standar‡°dONLNdÆ
#
Y
/
 )œd conventions described iÖ†°dONLNd«
#
 
/
“)qn °dONLNd…
0ä
<§(
9äInside qÄ°dONLNd–
0•
<Á)Macintosh: FilesF‡°dONLNd‡
0Ë
<Í)C
.°dONLNd‚
Bä
N©(
KäAfter fi&Ä°dONLNdÍ
B™
N‚) lling in the fid°dONLNd˘
B‚
N
X)8elds of the new publisher rx¿°dONLNd
B
X
N
q)veply r
°dONLNd
B
r
N
Ñ)ecoru`°dONLNd
B
Ñ
N)!d, pass it as a parameter to the .°dONLNd?
Oä
[ˆ(
XäNewPublisherDialog°dONLNdQ
Oˆ
[
›)l3 function, which displays the publisher dialog box.°dONLNdÖ
fä
r
(
oäerr := NewPublisherDialo°dONLNdù
f

r
&)êg(°dONLNdü
f
&
r
P)reply);°dONLNdß
~ä
ä
o(
áä3After displaying the publisher dialog box, use the °dONLNd⁄
~
o
ä)ÂCreateEditionContainerFile°dONLNdÙ
~
ä)ú
 °dONLNdı
ãä
ó√(
îäfunction to crR`°dONLNd
ã√
ó
8)9eate the edition containerï°dONLNd
ã
7
ó
v)t, and then use ï°dONLNd,
ã
v
ó
à)?the ï°dONLNd0
ã
à
ó
ƒ)
NewSectionï°dONLNd:
ã
ƒ
ó
ˇ)< function to crg`°dONLNdI
ã
ˇ
ó);eate .
°dONLNdN
òä
§ø(
°äthe section r
‡°dONLNd[
ò¿
§“)6ecor@°dONLNd_
ò“
§
)d and the alias r8@°dONLNdp
ò

§
+)Gecor¨†°dONLNdt
ò
+
§
@)d. Se—¿°dONLNdy
ò
@
§
å)e the next sectionÁ@°dONLNdã
ò
å
§
ë)L, Á@°dONLNdç
ò
ë
§
°)“Cr√@°dONLNdê
ò
°
§
Ú)eating the Edition °dONLNd£
•ä
±∂(
Æä    Containerÿ‡°dONLNd¨
•µ
±º)+,”X‡°dONLNdÆ
•Ω
±ƒ) aÿ‡°dONLNd∞
•ƒ
±“)nd F°dONLNd≥
•”
±„)“Cr"°dONLNd∂
•„
±
L)eating the Section Recor·‡°dONLNdŒ
•
L
±
h)id and å`°dONLNd‘
•
h
±
ö)Alias Recor¿°dONLNdfl
•
õ
±
Œ)3d” on page A@°dONLNdÍ
•
Œ
±
‡)32-15ï °dONLNdÓ
•
‡
±
Â) fi°dONLNd
•
Ê
±
Ò)or °dONLNdÛ
≤ä
æÁ(
ªädetailed information.°dONLNd    
Ċ
–
∫*CThe following code segment illustrates how your application might rp °dONLNdL
ƒ
∫
–
¯(
Õ
∫espond to the °dONLNdZ
—ä
ݟ(
⁄äuser `°dONLNd_
—†
›Â)choosing the Crl@°dONLNdn
—Â
›
Í)E=eate Publisher menu item. In this case, the code sets up the °dONLNd´
fiä
Íì(
ÁäprG °dONLNd≠
fiî
Í∞)
eview @°dONLNd≥
fi±
Í
ø)@for the edition, sets the default name for the edition containera °dONLNdÛ
fi
ø
Í
˙(
Á
ø, and calls an .°dONLNd
Îä
˜÷(
Ùäapplication-defi°dONLNd
Î÷
˜
)Lned function (°dONLNd 
Î

˜
f)<DoNewPublisher¬†°dONLNd.
Î
e
˜
î)S, shown in ¬†°dONLNd9
Î
î
˜
Í)/Listing 2-4 on page ¬†°dONLNdM
Î
Í
˜
Û)V2-¬†°dONLNdO
Î
Û
˜
˝)    33¬†°dONLNdQ
Î
˝
˜)
) to .
°dONLNdV
¯ä
L(
ä,display the publisher dialog box on the userΩ@°dONLNdÇ
¯
M
c)√’s scr≥¿°dONLNdà
¯
c
w)een. ∫°dONLNdç
¯
w
˙)An application might call the .°dONLNd´äfi(äDoNewPublisher°dONLNdπfi
)T function in rR`°dONLNd«

h)7esponse to the user¿°dONLNd⁄
i
¶)T’s choosing Cr‚ °dONLNdË
•
Ò)<eate Publisher fr¥Ä°dONLNd˘
Ò)Lom the .
°dONLNdä’(äEdit menu or in r?@°dONLNd÷
L)Lesponse to handling the CrˆÄ°dONLNd+
L
·)v"eate Publisher event. The chapter °dONLNdMä+“((ä“Responding to ;¿°dONLNd\“+
Ú)HAApple Events” in this book gives an example of a handler for the °dONLNdù,ä8ï(5äCr\°dONLNdü,ï8©)eate ±†°dONLNd§,©8)Publisher event..°dONLNdµCäOú(LäVAR°dONLNd∫Qú]+thisDocument: °dONLNdœQ
]
å)~MyDocumentInfoPtr; °dONLNd‰_úk
(húpromptForDialog: °dONLNd¸_
k
J)~Boolean;°dONLNdmúy“(vú    preview: °dONLNdm
y
J)~Handle; °dONLNd {úáˆ(ÑúpreviewFormat: °dONLNd6{
á
b)~FormatType; °dONLNdDâúï
(íúdefaultLocation: °dONLNd\â
ï
ò)~EditionContainerSpec;°dONLNdsóú£¿(†úmyErr:°dONLNdÄó
£
>)~OSErr;ˇ.@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-32    )BUsing the Edition Manager4^*¿
¯,
Courier
.°dONLNd\lhä(elBEGIN°dONLNdj~v
¯+?{Get a preview to show the user. The MyGetPreviewForSelection }°dONLNdHx~Ñ
Ü*,{ function returns a handle to the preview.}°dONLNdvÜ~í
™*2preview := MyGetPreviewForSelection(thisDocument);°dONLNd™î~†
*previewFormat := 'TEXT';°dONLNdƒ¢~Æ
‘*9defaultLocation := MyGetDefaultEditionSpec(thisDocument);°dONLNdˇ∞~º
*promptForDialog := TRUE;ˇ˛Ã»°dONLNd
æ~ 
˜*@myErr := DoNewPublisher(thisDocument, promptForDialog, preview, °dONLNd
cÃ
ÿ
Œ+ê previewFormat, defaultLocation);°dONLNd
Ñ⁄lÊÑ(„lEND;


*

¯4
*

¯ 
l

¯

ˇ·ˇ‚7^.
°dONLNd
ä¯l

*Creating the Edition Containerˇˇˇˇˇˇ‘@(

Ò
2
.°dONLNd
™
l
ë(
lUse the °dONLNd
≤
ë

-)%CreateEditionContainerFile°dONLNd
Ã

-

h)ú function to crR`°dONLNd
€

h

Â);eate an edition container to .
°dONLNd
¯
l
%’(
"lhold the publisher data..°dONLNd
0l
<
,* err := CreateEditionContainerFil°dONLNd1
0
,
<
8)¿e(°dONLNd3
0
8
<
º)editionFile, fdCreator°dONLNdI
0
º
<
¬)Ñ
,°dONLNdV
>
2
J
8(
G
2
 °dONLNdW
>
8
J
>)
e°dONLNdX
>
>
J
¬)ditionFileNameScript);.
°dONLNdo
Vl
b±(
_lThis function cr€°dONLNd
V±
b
")Eeates an edition container0Ä°dONLNdô
V
"
b
Û)q3. The edition container is empty (that is, it does °dONLNdÃ
cl
o
(
ll¬ contain any formats) at this time.°dONLNdÛ
ul
År*
Tµ¿°dONLNdÙ
uq
Å
7).o associate an icon with the edition containerí@°dONLNd"
u
7
Å
D)Δ, cr«Ä°dONLNd&
u
D
Å
})eate the apprC¿°dONLNd3
u
~
Å
Ù):opriate entries for the icon °dONLNdP
Çl
é
ë(
ãlDin your application’s bundle. See the chapter “Finder Interface” in *¿°dONLNdî
Ç
í
é
‹(
ã
íInside Macintosh: °dONLNd¶
èl
õü(
òlMacintosh TÄ°dONLNd±
èû
õ‚)2oolbox EssentialsµÄ°dONLNd¬
è„
õ
Û)E> for additional information. Depending on the contents of the .°dONLNd
úl
®´(
•ledition, the fi°dONLNd
ú´
®Ô)?le type will be °dONLNd
úÔ
®
)D'edtp'°dONLNd%
ú

®
Y)$ (for graphics), °dONLNd6
ú
Y
®
})F'edtt'°dONLNd<
ú
}
®
∏)$ (for text), or °dONLNdL
ú
∏
®
‹);'edts'°dONLNdR
ú
‹
®
fi)$
 .
°dONLNdS
©l
µ~(
≤l(for ‡°dONLNdX
©
µ†)sound)..°dONLNd`
ªl
«è(
ƒlAfter crR`°dONLNdh
ªè
«
)#eating the edition containerï°dONLNdÑ
ª

«
3)}
, use the ï°dONLNdé
ª
3
«
o)'
NewSectionï°dONLNdò
ª
o
«
™)< function to crg`°dONLNdß
ª
™
«
Û);eate the section .
°dONLNd∏
»l
‘o(
—l
rE°dONLNdπ
»p
‘Ç)ecorπ`°dONLNdΩ
Ȃ
‘∏)d and alias r°dONLNd 
»π
‘À)7ecorâ`°dONLNdŒ
»À
‘
)d for the section..°dONLNd·
⁄l
Êú(
„lListing 2-4°dONLNdÏ
⁄ú
Ê˘)0 illustrates how to crR`°dONLNd
⁄˘
Ê
C)]eate a publisherï°dONLNd
⁄
B
Ê
[)I. The ï°dONLNd
⁄
[
Ê
Ø)DoNewPublisherï°dONLNd&
⁄
Ø
Ê
ˆ)T function shown .
°dONLNd6
Ál
ÛË(
lin the listing is a function pr™‡°dONLNdU
ÁË
Û
˜)|>ovided by an application. Note that an application might call .°dONLNdì
Ùl~(
˝lthe °dONLNdó
Ù~“)DoNewPublisher°dONLNd•
Ù“Û)T functio°dONLNd≠
ÙÛ
    )!n in rR`°dONLNd≥
Ù
    
\)esponse to the user¿°dONLNdΔ
Ù
]
¨)T’s choosing the Cr‚ °dONLNdÿ
Ù
´
Ã)Neate Pu‚ °dONLNdfl
Ù
Ã
Ô)!blisher .
°dONLNdÁ
lö(
lcommand z‡°dONLNdÔ
õ∂)/or in ra¿°dONLNdˆ
∂fl)    esponse tz`°dONLNdˇ
flÍ))o t≤@°dONLNd
Í
)he Cr©@°dONLNd


[)eate Publisher eventˇ‡°dONLNd

[
fl)Y. The chapter “Responding to °dONLNd8l
ó(lCApple Events” in this book gives an example of a handler for the Cr`Ä°dONLNd{
ó
Ú(
óeate Publisher event..°dONLNdë l,”()lThe parameters to the °dONLNdß ”,
')gDoNewPublisher°dONLNdµ 
',
‡)T+ function include a pointer to information .
°dONLNd‡-l9
Â(6lVabout the document, a Boolean value that indicates if the function should display the °dONLNd6:lF¸* new publisher dialog box, the prY†°dONLNdV:¸F
w)êeview for the edition, the prO¿°dONLNds:
wF
◊){eview format, and an °dONLNdàGlS∑(Pledition containerÒÄ°dONLNdôG∂S∏)J
.°dONLNdõYle
I(bl3The function displays the publisher dialog box if rcÄ°dONLNdŒY
Ie
‰)›%equested, letting the user accept or °dONLNdÛflr
W(ol4change the name of the edition and the location wher_Ä°dONLNd'f
Wr
µ)Îe the edition should rö°dONLNd=f
µr
Ù)^eside. Use the .°dONLNdLsl
(|lCreateEditionContainerFile°dONLNdfs

C)ú function to crR`°dONLNdus
C
Ó);%eate the edition with the given name °dONLNdöÄlåŒ(âland location. Use the °dONLNd∞ÄŒå

)b
NewSection°dONLNd∫Ä

å
E)< function to crR`°dONLNd…Ä
Eå
Â);$eate a new section for the publisherï°dONLNdÌÄ
‰å
Á)ü
.ˇ/ä@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-33
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähÁ(eäAfter the section is cr∫@°dONLNd\Áh
¡)]2eated, you must write out the edition data. Be sur¯@°dONLNdI\
¡h)⁄e to add the newly °dONLNd\iäuí(räcrµ@°dONLNd^iíu
ô)>eated section to your list of sections for this document. Ther4@°dONLNdúi
öu
™(r
öe arB‡°dONLNd†i
™u
fl)e several difà`°dONLNd≠i
flu
Î)5ferj‡°dONLNd∞i
Îu
˚)ent °dONLNd¥väÇ”(ätechniques for crÄ°dONLNd≈v‘Ç)JFeating publishers and unique IDs; this listing displays one technique.°dONLNd
àäî´(ëäAfter crO°dONLNd
à¨î
C)"#eating the edition container and cr“Ä°dONLNd
7à
Cî
£)óeating a new section rΔ‡°dONLNd
Mà
£î
µ)`ecor;@°dONLNd
Qà
∂î
¡)d, .°dONLNd
Tïä°ú(ûäthe ,
Courier°dONLNd
Xïú°)DoNewPublisher°dONLNd
fï°
¢)T' function calls another application-defi°dONLNd
éï
¢°
∏)≤ned rR`°dONLNd
ìï
∏°
Ÿ)outine, °dONLNd
õ¢äÆfi(´äDoWriteEdition°dONLNd
©¢fiÆ
ñ)T+, to open the edition and write data to it.

—HŸ4“HŸ"“H_

ˇ·ˇ‚7^
    .
°dONLNd
÷«ä“∂(œäListing 2-4°dONLNd
‚«Œ“
)DCreating a publisher
.°dONLNd
¯·äÌ
b(Íä$FUNCTION DoNewPublisher(thisDocument°dONLNd·
bÌ
Ü)ÿ: MyDo°dONLNd"·
ÜÌ
‘)$cumentInfoPtr°dONLNd/·
‘Ì
⁄)N
;°dONLNd9Ô
˚
 (¯

p°dONLNd:Ô
 ˚
∞)romptForDialog: Boolean;°dONLNdRÔ
∞˚
∂)ê
 °dONLNd\˝

    
 (


p°dONLNd]˝
 
    
t)review: Handle°dONLNdk˝
t
    
z)T
;°dONLNdu



 (


p°dONLNdv

 

h)reviewFormat°dONLNdÇ

h

z)H: F°dONLNdÖ

z

∞)    ormatType°dONLNdé

∞

∂)6
;°dONLNdò


%
 (
"

e°dONLNdô

 
%
\)
ditionSpec°dONLNd£

\
%
n)<: E°dONLNd¶

n
%
‡)ditionContainerSpec°dONLNdπ

‡
%
Ê)r
)°dONLNd√
'

3
 (
0

:°dONLNdƒ
'
 
3
J) OSErr;°dONLNdÃ
5ä
Aú(
>äVAR°dONLNd—
Cú
O
 +getLastErr, dialogErr:°dONLNdÔ
C
,
O
P)êOSErr;°dONLNd˜
Qú
]
 (
ZúcreateErr, sectionErr:°dONLNd
Q
,
]
P)êOSErr;°dONLNd
_ú
k¿(
húresID:°dONLNd+
_
,
k
\)êInteger;°dONLNd5
mú
yÍ(
vúthisSectionH:°dONLNdJ
m
,
y
Ä)êSectionHandle;°dONLNdZ
{ú
á¿(
Ñúreply:°dONLNdh
{
,
á
ò)êNewPublisherReply;°dONLNd{
âä
ï®(
íäBEGIN°dONLNdÇ
óú
£Æ+{se°dONLNdÖ
óÆ
£
§))t up info for new publisher reply record}°dONLNd∞
•ú
±
2(
Æúreply.replacing := FALSE;°dONLNdÀ
≥ú
ø
&*reply.usePart := FALSE;°dONLNd‰
¡ú
Õ
2*reply.preview := preview;°dONLNdˇ
Ϝ
€
z*%reply.previewFormat := previewFormat;°dONLNd&
›ú
È
P*reply.container := editionSpec°dONLNdD
›
P
È
V)¥
;°dONLNdG
Îú
˜¢(
Ùú
I°dONLNdH
΢
˜
,)F promptForDialog THEN °dONLNda
˘ú¥(úBEGI°dONLNde
˘¥∫)
N°dONLNdh
˘¿Δ)
{°dONLNdi
˘Δ
h)user interaction is allowed°dONLNdÑ
˘
h
n)¢
}°dONLNdàÆ¿(Æ{di°dONLNdã¿
í)#splay dialog box and let user selec°dONLNdÆ
í
û)“t}°dONLNd≥Æ!
ò(Æ'dialogErr := NewPublisherDialog(reply);°dONLNd›#Æ/¿*{di°dONLNd‡#¿/
b)spose of preview data handl°dONLNd˚#
b/
n)¢e}°dONLNd1Æ=“(:ÆDispos°dONLNd1“=ÿ)$
e°dONLNd1ÿ=
V)Handle(reply.preview)°dONLNd1
V=
\)~
;°dONLNd ?ÆK¥(HÆ
I°dONLNd!?¥K
⁄)1F dialogErr <> noErr THEN MyErrHandler(dialogErr)°dONLNdR?
⁄K
‡(H
⁄
;°dONLNdVMÆY¥(VÆ
I°dONLNdWM¥Y
2)F reply.canceled THEN°dONLNdo[ÆgÃ(dÆBEGIN°dONLNdw[‰g
í)6{do nothing if user canceled}°dONLNdòi¿u
å(r¿"DoNewPublisher := userCanceledErr;°dONLNdæw¿É
>*EXIT(DoNewPublisher);°dONLNd÷ÖÆëΔ(éÆEND;°dONLNd‹ìúü¥(úúEND;°dONLNd‚ì¿ü
8)${of promptForDialog}ˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-34    )BUsing the Edition Manager4^*¿
¯,
Courier
.°dONLNd\~hÑ(e~
I°dONLNd
\Ñh
 )F NOT reply.replacing THEN°dONLNdj~vñ(s~BEGI°dONLNd!jñvú)
N°dONLNd'xêÑ
¯(Åê<{if user isn't replacing an existing file, create a new one}°dONLNdfÜêífi*createErr := °dONLNdw
Œ+2CreateEditionContainerFile(reply.container.theFile°dONLNd©î
Π
‘(ù
Œ
,°dONLNd∂¢
2Æ
8(´
2
 °dONLNd∑¢
8Æ
>)
 °dONLNd∏¢
>Æ
D)
k°dONLNdπ¢
DÆ
å)AppSignature°dONLNd≈¢
åÆ
í)H
,°dONLNd“∞
2º
8(π
2
 °dONLNd”∞
8º
>)
 °dONLNd‘∞
>º
D)
r°dONLNd’∞
Dº
Ú)eply.container.theFileScript)°dONLNdÚ∞
Úº
¯)Æ
;°dONLNdˆæê ñ(«ê
I°dONLNd˜æñ 
,)F createErr <> noErr THEN°dONLNd
ÃêÿÆ(’êBEGIN°dONLNd
⁄¢Ê
í+(DoNewPublisher := errAEPermissionDenied;°dONLNd
HË¢Ù
 *EXIT(DoNewPublisher);°dONLNd
`ˆê
®(ˇêEND;°dONLNd
f
~
ñ(
~END;°dONLNd
j
ñ

) {of not replacing}°dONLNd

~

⁄(
~:{Advance counter to make a new unique sectionID for this }°dONLNd
ª
 ~
,
‡*;{ document. It is not required that you equate section IDs °dONLNd
ˆ
 
‡
,
Ê(
)
‡
}°dONLNd
˘
.~
:ê(
7~{ w°dONLNd
¸
.ê
:®)ith °dONLNd
.®
:Í)resources.}°dONLNd
<~
HÑ(
E~
t°dONLNd
<Ñ
H
Ú)=hisDocument^.nextSectionID := thisDocument^.nextSectionID + 1°dONLNdK
<
Ú
H
¯(
E
Ú
;°dONLNdN
J~
Vê(
S~{cr°dONLNdQ
Jê
V
)eate a publisher sectio°dONLNdh
J

V
&)än}°dONLNdl
X~
d
t(
a~)sectionErr := NewSection(reply.container,°dONLNdü
f

r
∞+ê thisDocument^.fileSpecPtr,°dONLNd¬
tÍ
Ä(
}Í
 °dONLNd≈
t

Ä
V)$ stPublisher°dONLNd—
t
V
Ä
\)H
,°dONLNd‹
Ç

é
(
ã

 °dONLNd›
Ç

é
º)thisDocument^.nextSectionID,°dONLNd

êÍ
ú(
ôÍ
 °dONLNd
ê

ú
™)$ pumOnSave, thisSectionH);ˇˇ@°dONLNd 
û~
™
Ú(
ß~?IF (sectionErr <> noErr) & (sectionErr <> multiplePublisherWrn)@°dONLNd_
û
Û
™
¯(
ß
Û
 °dONLNdd
¨¢
∏¥(
µ¢& (°dONLNdg
¨¥
∏
í)%sectionErr <> notThePublisherWrn) THE°dONLNdå
¨
í
∏
ò)fi
N°dONLNdê
∫ê
Δñ(
Ð
M°dONLNdë
∫ñ
Δ
 )yErrHandler(sectionErr)°dONLNd®
∫
 
Δ
&)ä
;°dONLNd´
»~
‘Ñ(
—~
r°dONLNd¨
Ȅ
‘
V)#esID := thisDocument^.nextSectionID°dONLNdœ
»
V
‘
\)“
;°dONLNd“
÷~
‚ê(
fl~{ad°dONLNd’
֐
‚
2)d this section/alias pair t°dONLNd
÷
2
‚
h)¢    o app's i°dONLNd˘
÷
h
‚
‘)6nternal bookkeepin°dONLNd
÷
‘
‚
‡)lg}°dONLNd
‰~
ä(
Ì~My°dONLNd
‰ä

Œ)6AddSectionAliasPair(thisDocument, thisSectionH, resID)°dONLNdG
‰
Œ

‘(
Ì
Œ
;°dONLNdJ
Ú~
˛ê(
˚~{wr°dONLNdM
Úê
˛
)ite out first editio°dONLNda
Ú

˛
)xn}°dONLNde~
(    ~DoWriteEdition(thisSection°dONLNd

&)úH)°dONLNdÅ
&
,)
;°dONLNdÑ~Ñ(~
{°dONLNdÖÑ
‘)8Remember that the section and alias records need to be }°dONLNdø~(
¬(%~6{ saved as resources when the user saves the document.°dONLNdı
¬(
»(%
¬
}°dONLNd¯*~6ê(3~{se°dONLNd˚*ê6
h)$t the function result appropriately}°dONLNd!8~D
>(A~ DoNewPublisher := MyGetLastError°dONLNdA8
>D
D)¿
;°dONLNdCFlR~(OlEND°dONLNdFF~Rä); ˇ3H@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-35
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

jHp4jHp käk

ˇ·ˇ‚7^°dONLNd\äj
C(fä!Opening an Edition Container to W™@°dONLNd!\
Cj
p)π    rite Dataˇˇˇˇˇˇ‘@)Ã
2
°dONLNd,pä|∞(yä    Several r@°dONLNd5p±|‹)'
outines ar›†°dONLNd?p‹|Á)+e rÏ@°dONLNdBpÁ|˛)equirÄ°dONLNdGpˇ|
y)ed to write (publish) data frÌÄ°dONLNddp
x|
˜)yom a publisher to an edition °dONLNdÅ}äâ≥(Üä    container2 °dONLNdä}≥â
)). (For information on cr4¿°dONLNd¢}
â
ê)geating an edition containerÃÄ°dONLNdΩ}
èâ
æ)u, see the prA@°dONLNd…}
øâ)0evious section.) .°dONLNd⁄ääñ£(ìäBeforR`°dONLNdflä£ñ
o)/e writing data to an edition, you must use the ,
CourierR`°dONLNd
ä
oñ
√)ÃOpenNewEditionR`°dONLNd
ä
Ö)T function. This .
°dONLNd
,óä£(†äUfunction should be used only for a publisher within a document. Use this function to °dONLNd
ŧä∞
:*+initiate the writing of data to an edition..°dONLNd
≠ªä«
*err := OpenNewEditio°dONLNd
¡ª
«
)xn(°dONLNd
û
«
∂)publisherSectionH, fdCreator°dONLNd
߻
∂«
º)®
,°dONLNd
Ë…
’
(“

 °dONLNd
È…
’
)
p°dONLNd
Í…
’
⁄)!ublisherSectionDocument, refNum);.
°dONLNd·äÌë(Íä
A∫†°dONLNd·ëÌ)Y user may try to save a document containing a publisher that is unable to write its data °dONLNdfÓä˙
l(˜ä2to an edition—because another publisher (that sharÿ`°dONLNdòÓ
l˙
ı)‚!es the same edition) is writing, °dONLNdπ˚ä

(
äanother subscriber (that shar, °dONLNd÷˚
    

p)es the same edition) is rË`°dONLNdÔ˚
p

ı)geading, or a publisher located °dONLNd
ä
ó(
äon F‡°dONLNd
ò
˜)another computer is râ¿°dONLNd&
˜

)_egisterÿ‡°dONLNd-



ˆ)5ed to the section. In such a case, you may decide to °dONLNdb
ä
!ç(
ä
rE°dONLNdc
é
!±)    efrain frß¿°dONLNdl
±
!
À)#Bom writing to the edition so that the user does not have to wait. W‡°dONLNdÆ

Ã
!
“(

Ã
Y`°dONLNdØ

“
!
)
ou should °dONLNdπ
"ä
.û(
+äalso ö‡°dONLNdæ
"û
.°)
r_‡°dONLNdø
"¢
.≈)    efrain fr¬†°dONLNd»
"≈
.
!)#om displaying an err‚`°dONLNd‹
"
!
.
[)\or to the user¢¿°dONLNdÍ
"
[
.
Ï):". The contents of the publisher arä`°dONLNd
"
Ï
.)ëe saved °dONLNd
/ä
;
î(
8ä<to disk with the document. The next time that the user savesöÄ°dONLNdP
/
î
;
”(
8
î the document1‡°dONLNd]
/
‘
;
˛)@
, you can °dONLNdg
<ä
H
6(
Eä)write the publisher data to the edition. ÿ°dONLNdê
<
6
H
<)¨
Yç@°dONLNdë
<
<
H
k)
ou should ô°dONLNdõ
<
k
H
t)/diù °dONLNdù
<
t
H
Ü)    splaƒ†°dONLNd°
<
Ü
H
ì)y a”¿°dONLNd§
<
ì
H
ƒ)n alert box 1‡°dONLNd∞
<
≈
H)2to discourage °dONLNdæ
Iä
U´(
Räusers frV@°dONLNdΔ
I´
U)!Mom making multiple copies of the same publisher and pasting them in the same °dONLNd
Vä
b„(
_äor other documents §†°dONLNd&
V„
bÔ)Y(seˇ °dONLNd)
VÔ
bˆ)e H¿°dONLNd+
V˜
b
◊)1“Duplicating Publishers and Subscribers” on page ≤¿°dONLNd\
V
◊
b
È)‡2-58†°dONLNd`
V
Í
b
Ì)
)ZÄ°dONLNda
V
Ì
b
Ô)
.°dONLNdc
hä
t
¯(
qäTIf a user clicks Send Edition Now within the publisher options dialog box (to write °dONLNd∑
uä
Å*]publisher data to an edition manually), and the publisher is unable to write its data to its °dONLNd
Çä
é*edition (for any of the rÄ°dONLNd-
ÇÒ
é
Õ)g1easons outlined above), you should display an errU†°dONLNd^
Ç
Õ
é)‹or message..°dONLNdj
îä
†¡(
ùäAfter you arR`°dONLNdv
î¡
†œ)7e fiR`°dONLNdz
îœ
†
å)+nished writing data to an edition, use the R`°dONLNd•
î
å
†
‘)ΩCloseEditionR`°dONLNd±
î
‘
†)H function to .
°dONLNdæ
°ä
≠‘(
™äclose the edition.°dONLNd—
≥ä
ø∏*Listing 2-5 @°dONLNd‹
≥π
ø
r)/, illustrates how to write data to an editionV°dONLNd
≥
r
ø)π#. For an existing edition container≥°dONLNd+
≥
ø)ì
,3°dONLNd,
≥
ø
)
 .°dONLNd-
¿ä
Ã
Å(
…ä7you must open the edition, write each format using the °dONLNdd
¿
Å
Ã
…)˜WriteEdition°dONLNdp
¿
…
Ã)H function, and ˇˇ∂⁄°dONLNd
Õä
Ÿ
(
÷äclose the edition using the ˇˇ$éB°dONLNdõ
Õ


Ÿ
I)wCloseEditionˇˇ∂⁄B°dONLNdß
Õ
I
Ÿ)H0 function. This listing shows how to write text .
°dONLNd◊
ڊ
Êù(
„äonly"†°dONLNd€
⁄ù
Ê
>)(. If the edition is written successfully@°dONLNd
⁄
=
Ê
z)†, subscribers r
 °dONLNd
⁄
{
Ê
)>eceive Section Read eventsÓ¿°dONLNd,
⁄

Ê
Ú)u
.ˇd@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-36    )BUsing the Edition Manager4^*¿
¯

g*n
¯4g*n
¯"h*_

ˇ·ˇ‚7^
°dONLNd\lgò(dlListing 2-5°dONLNd\∞g∏)D
W’ê°dONLNd\∏g
)riting data to an edition,
Courier
.°dONLNd)vlÇ
™(l5PROCEDURE DoWriteEdition(thePublisher: SectionHandle)°dONLNd^v
™Ç
∞(
™
;°dONLNd`Ñlêr(çl
V°dONLNdaÑrê~)AR°dONLNdeí~ûÆ+eRefNum:°dONLNdríÿû
,)ZEditionRefNum;°dONLNddž~¨Æ(©~openErr:°dONLNdè†ÿ¨¸)ZOSErr;°dONLNdóÆ~∫¥(∑~    writeErr:°dONLNd•Æÿ∫¸)ZOSErr;°dONLNd≠º~»¥(≈~    closeErr:°dONLNdªºÿ»¸)ZOSErr;°dONLNd√ ~÷Ã(”~thisDocument:°dONLNd’ ÿ÷
D)ZMyDocumentInfoPtr;°dONLNdÈÿ~‰¿(·~textHandle:°dONLNd˘ÿÿ‰¸)ZHandle°dONLNdˇÿ¸‰
)$
;°dONLNd

ÊlÚr(Ôl
B°dONLNd
ÊrÚä)EGIN°dONLNd
Ù~
ê+{fi°dONLNd
Ùê

ò),nd out which document this section belongs t°dONLNd
7Ù
ò

§(˝
òo}°dONLNd
;
~
Ñ(
~
t°dONLNd
<
Ñ
fi)hisDocument := °dONLNd
K
fi
Í)ZMy°dONLNd
M
Í

Ü)FindDocument(thePublisher)°dONLNd
g

Ü

å)ú
;°dONLNd
j
~
ê(
~{op°dONLNd
m
ê

)en edition for writin°dONLNd
Ç



)~g}°dONLNd
Ü
~
*
¬(
'~6openErr := OpenNewEdition(thePublisher, kAppSignature,°dONLNd
¡
,¥
8¿+6  °dONLNd
≈
,ÿ
8‰)$  °dONLNd
 
,

8
Ú)6&  thisDocument^.fileSpecPtr, eRefNum);°dONLNd
Ú
:~
F
(
C~IF openErr <> noErr THE°dONLNd    
:

F
)ä
N°dONLNd
Hê
Tñ(
Qê
M°dONLNd
Hñ
T
)yErrHandler(openErr)°dONLNd"
H

T
)x
;°dONLNd$
H

T
û){handle error and exit}°dONLNd=
V~
bê(
_~{ge°dONLNd@
Vê
b
)t the text data to writ°dONLNdW
V

b
&)äe}°dONLNd[
d~
pÑ(
m~
t°dONLNd\
dÑ
p“)extHandle := °dONLNdi
d“
pfi)NMy°dONLNdk
dfi
p
Ê),GetTextInSection(thePublisher, thisDocument)°dONLNdó
d
Ê
p
Ï(
m
Ê
;°dONLNdö
r~
~ê(
{~{wr°dONLNdù
rê
~)ite out text dat°dONLNd≠
r
~¸)`a}°dONLNd±
Ä~
åÍ(
â~HLock(textHandle);°dONLNd≈
é~
ö
¬*6writeErr := WriteEdition(eRefNum, 'TEXT', textHandle^,°dONLNd
ú¥
®∫+6
 °dONLNd
úÿ
®fi)$
 °dONLNd
ú

®
∂)6 GetHandleSize(textHandle));°dONLNd%
™~
∂ˆ(
≥~HUnLock(textHandle);°dONLNd;
∏~
ƒ
*IF writeErr <> noErr THEN°dONLNdV
Δ~
“ú*BEGIN°dONLNd^
‘ê
‡
Ê+9{There were problems writing; simply close the edition. }°dONLNdö
‚ê
Ó
‡*8{ When successful = FALSE, the edition data <> section }°dONLNd’
ê
¸
‘*6{ data. Note: this isn't fatal or bad; it just means }°dONLNd
˛ê

Ú*;{ that the data wasn't written and no Section Read events }°dONLNdLê
*{ will be generated.}°dONLNddê&
Ü*)closeErr := CloseEdition(eRefNum, FALSE);°dONLNdè(~4ê(1~END°dONLNdí(ê4ñ)
 °dONLNdï6~BÑ(?~
E°dONLNdñ6ÑBñ)LSE°dONLNdõD~Pú(M~BEGIN°dONLNd£Rê^
¬+3{The write was successful; now close the edition. }°dONLNdŸ`êl
Ú*;{ When successful = TRUE, the edition data = section data.}°dONLNdnêz
Œ*5{ This edition is now available to any subscribers. }°dONLNdO|êà
Ú*;{ Section Read events will be sent to current subscribers.}°dONLNdçäêñ
Ä*(closeErr := CloseEdition(eRefNum, TRUE);°dONLNd∑ò~§ñ(°~END;°dONLNdº¶l≤~(ØlEND°dONLNdø¶~≤ä); ˇF&@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-37
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

kHr4lHr mäm

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\äk
(gäCreating a Subscriberˇˇˇˇˇˇ€r(g
2
°dONLNdrä~ê({ä
Y@Ä°dONLNdrê~…)ou need to cr™†°dONLNd%r…~
)9eate a Subscribe Tfi°dONLNd7r
~
Ú)N-o menu command in the Edit menu. When a user °dONLNddäã‚(àächooses Subscribe TŒ°dONLNdw·ã)Wo fr‹`°dONLNd{ã)=om this menu, your application should display the subscriber °dONLNd∏åäòÏ(ïädialog box on the userx‡°dONLNdŒåÌò
)c’s scro`°dONLNd‘å
ò
)een..°dONLNdŸûä™Ø(ßäUse the ,
Courier°dONLNd·ûØ™
!)%NewSubscriberDialog°dONLNdÙû
!™    )r6 function to display the subscriber dialog box on the °dONLNd
*´ä∑ú(¥äuser=`°dONLNd
.´ù∑≤)’s scr¿°dONLNd
4´≤∑
N)%een. This function is similar to the ¿°dONLNd
Y´
N∑
ú)úCustomGetFile¿°dONLNd
f´
ú∑
®)N pr‚ °dONLNd
i´
ß∑
ƒ)ocedur¥Ä°dONLNd
o´
ķ)e described in the .
°dONLNd
Ç∏äƒ≤(¡ä    chapter “B`°dONLNd
ã∏≥ƒ’))Standarv†°dONLNd
í∏’ƒ
)"d File Package†°dONLNd
†∏
ƒ
)@
”†°dONLNd
°∏
ƒ
)
 ù†°dONLNd
¢∏
ƒ
')in ◊`°dONLNd
•∏
'ƒ
Ñ)Inside Macintosh: Filesû@°dONLNd
º∏
Öƒ
á)^
.°dONLNd
æ ä÷ê(”ä
Tµ¿°dONLNd
ø è÷ü)o cr‡Ä°dONLNd
√ ü÷Ë)eate a subscriberꆰdONLNd
‘ Ë÷
h)I, you must get information frf@°dONLNd
Ò 
h÷
ú)Äom the user– °dONLNd
¸ 
õ÷
Ó)3, such as the name °dONLNd◊ä„ï(‡äof …`°dONLNd◊ï„•)the &¿°dONLNd◊¶„
˜)Pedition being subscribed to. The dialog box displays a listing of all available °dONLNdf‰äØ(Ìä    editions |`°dONLNdo‰∞√)&and ÈÄ°dONLNds‰√
5)allows the user to see a pr¿°dONLNdé‰
5)r2eview (thumbnail sketch) of the edition selected. °dONLNd¿Òä˝¢(˙äFigurR¿°dONLNd≈Ò¢˝ª)e 2-12@°dONLNdÀÒª˝
g)& shows a sample subscriber dialog box.


H
04
 H
0"
 H]

ˇ·ˇ‚7^
    °dONLNdÛ
ä
 ∫(
äFigure 2-12°dONLNdˇ
Ã
 “)B
A0°dONLNd
“
 
I) sample subscriber dialog box
°dONLNd
Š
Œ
ˆ(
ÀäTThe subscriber dialog box allows the user to choose an edition to subscribe to. The .°dONLNds
ϊ
€¸*NewSubscriberDialog°dONLNdÜ
œ¸
€
Û)r; function handles all user interaction until a user clicks .
°dONLNd¡
‹ä
Ë
ó(
Âä=Subscribe or Cancel. When a user selects an edition containerr†°dONLNd˛
‹
ó
Ë
˘(
Â
ó, the Edition Manager °dONLNd
Èä
ı (
Úäaccesses the prO@°dONLNd#
ÈÀ
ı
‰)AEeview for the edition container (if it is available) and displays it.


/à
™òÄ@
W
˛HH



M2@

ˇˇˇˇˇˇ

W
˛
2ä
’¬ˇ¸Ä√Ä√ü√ˇÏü√ˇÃò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√LòÔ˘
ˆˇ¸ÎLòÊ
ˆÎLòÔ˘
ˆÎLòÊ
ˆÎLòÔ˘
¿
3¿˝ÎL(ò¸Ä0
?ÅÄ0¸˜

IJ|¿˛L+ò¸
¿ˆ˘
AÅÛ<«èá˜

IJf¿˛L.ò¸Õû31„3Ú
¸AÉ3˛ÃÅˇΔ˘ˇ¡Éœ¯ffiyÁÄL/ò¸
Œ¸3˚˘
A„3ÃÃŒˇÜ˘!ÜlÕfÊû¿L+ò¸
å¸3Ú
AÉ3Ãë˘!Ülï|Δë¿L2ò¸?33Û3˚˘

AÉ3ÃÃ√Ä>˘!ÜlÕò`Δ¸Ã¿L.ò¸0333Ú

AÉ3ÃÃ…Ä˘!ÜlÕò`Δ¿Ã¿L2ò¸1232˚˘
¡ÒÛ«å«˘ˇ¡ÜlÕò`ΔƒÃ¿L'ò¸<1„¸Ú
ˇ¿˘˜
ÛÃï`Δxg¿LòÔ˘
ˆÎLòÊ
ˆÎLòÔ˘
ˆÎLòÊ
ˆˇ˛ÎLòÔ¯ˆˇ˛ÎLò√L
òÔ÷Lò√L
òÔ÷LòÌ?ÁˇÛLòÔ?Èˇ¯ÛLòÌ?Èˇ¯ÛLòÔ?Èˇ¯˘ˇ˛L"òÌ?U«?ˇˇ?˝ˇ
¸¸ˆˇ¯(˘
ÄL"òÔ>™øõ˛ˇ?˝ˇ¸ıˇ¯D¯ÄL#òÌ
?ü08É&˛„˜ˇ¯Ç ¯@L$òÔ>ˇøè˝3?3˛ÃÕ˜ˇ˘
 ¯@L(òÌ?«˝3?3>ÃÃœ˜ˇ˚«ê *Ä@L+òÔ>ˇø„˛30?3<˛Ãœ˜ˇ¯D 
˛@L,ò˜0¯?Û˝3ˇ3<˛Ãœ˜ˇ¯D  †¢Ä@L-ò˜<˙>™ø≥˝3ø3<˛ÃÕ˜ˇ¯D ˛˛@L-ò˜¯?U«338É>ʡ¯| (àÄÄ@L*ò˜˙?¸ˇ?ˇˇÛˇ¸Ùˇ¯ Q
˛@L(ò˜    ¯?¸ˇ?ˇˇsˇ¸Ùˇ    ¯  ˛Ä@L$ò˜
    Ä˚?˘ˇáˇ     
˛@L ò˜
Ģ?Èˇ¯ *††Ä@L"ò˘@˚ È ˛¸@L ò˘`˘ È ˛à¸@L"ò˘¿ ˚ È ˛P¸@Lò˘@ ˘ ȯÄLò˘ 0˚ È˘
ÄLò˘0˘ È˘ˇ˛L#ò˘
˚ ‡˛¿¿ÛÛL"ò˙Å˘
!Ä¿¿ÛÛL%ò˙8ÒÉ:˚!@8x«á¯Ò„¿ÙÛL#ò˙Å:˘!@dåÃÃÅôƒ`ÙÛL%ò˙
Ä2˚!@p|ÃŒ
ò¯√‡ÙÛL$ò˚
ˇÄ˘!@8Ãœ«
ôòΔ`ÙÛL&ò˚ÅÄ˚!@ÃÃÅôòΔ`ÙÛL$ò˚
Ģ!@LÃÃIÅôòΔ`ÙÛL+ò˚p˛@˙ ˇÄ8|«á¯¯c‡Ù˘ˇ˛L ò˚¡ˇÄB¸˙ È˘
ÄL!ò˚áB¸ ȯÄLò˚¸F˙ È ¯@L"ò˚¿ÄD
¿˝ È ¯@L#ò¯¿D0`˚ È ¯
Ä¿˛@L&ò˘˛H˝ È Ã
Ä¿˛@L#ò˘„Δ<˙ È Ãxqô„«¿@L.ò˘8#7¸ ™Ä¿˚ı ÃÃ…∞Δf`@L-ò˘1ÄÄ˚!U@¿˚ı Ã÷‡Δf`@L1ò˘Ä¸ ÄÄ8x«á
≥«√Δfiı øq¿Δf`@L1ò˙?ÒÑ@
‡˚!@dåÃÃÅΔffgı ÿ9‡Δf`@L4ò˚
‡Ü` ˝
 ÄÄp|ÃŒ
ܲfı Ãô∞Δf`@L2ò˚0˚!@8Ãœ«
áÊffı ¯xqòc«¿@L1ò˚
˝ ÄÄÃÃÅÜffı ˚@L/ò˚0
˚!U@LÃÃIÅÜ&ffı ˚@L.ò˚?‡É˝ ™Ä8|«á
É«√Δı ¯@L$ò˚p‡Ç¿·˚ ˘Ú¯ÄL(ò˚AÅ¿Ê1IJ ˘Ú˘
ÄL"ò˚
<ĸ È˘ˇ˛Lò¸˛
IJ ÈÛLò¸ ƒ00>˚ ÈÛL ò˝

ÒL``cÅIJ ÈÛLò˝
&à¿p‡Ä¸ ÈÛLò˝    9¿px ˝ ÈÛLò˝    (—0a…Ä˚ ÈÛLò˝    6@c    ˝ ÈÛLò˝    08ËDnÃ˚ ÈÛLò˝    ê dLt˝ ÈÛLò˝    DHc˚ ÈÛL ò˛

ªH
P1˝ ÈÛL"ò˛˛DH`P=˚ ȘU@Lò˙@ê 7¸ ÈÛLò˛    †
Ä$C˙ ÈÛLò˝@@0¡¸ ÈÛLò˛
 0O˘ ÈÛLò˛N˚ ÈÛLò˝≤»êÄL˘ ÈÛLò˛å
p8†¿˚ ÈÛLò˛    `¿¯ ÈÛLò˛åX˝
Ä`¸ ÈÛLò˛ ˝
Ä˙ ÈÛLò˝H˝
Åò¸ ÈÛLò¸
    `˝
É˙ ÈÛL"ò¸
¿˝
ܸ È˘ˇ˛L ò˚ 
`å˙ È˘
ÄL"ò¸
àò¸ ȯÄL ò¸
†
˙ È ¯@L#ò¸˛
ÄÄ˝ È ¯@L'ò¸
Ä¿˚ È ¿˛@L%ò¯
 ¿`˝ È  ˛@L'ò¸˛8@ ˚ È «√áå@L(ò˚D¿ ˝ È ffLÃ@L'ò¸˛8@ ˚ È ÊfÃ@L)ò¸
@0˝ È ffÃ@L$ò˘@˚ È ff@L)ò¸Ä88`˝ È &ffLL@L#ò˙@ ` ˘ È √Êcáå@L!ò¸@Å ˚ È ¯@Lò¸ ¿Ö ˘ È ¯@L!ò¸
Ä ˚ È ¯@Lò¸˜ ȯÄL"ò¸@˚ È˘
ÄLò¸·¯4ů È˘ˇ˛Lò¸<?$!˚ ÈÛLò¸`˛h˘ ÈÛLò¸¿˛–˚ ÈÛLò¯Ä˘ ÈÛLòˆ(˚ ÈÛLò˘
¿H˘ ÈÛLò˘

˚ ÈÛLò˘
0$˘ ȯˇÄLò˘¿˚ ȯˇ‡Lò˘
¿˙ ȘˇLò˘˛@¸ È
¯¯Lò˘ˆ È
«˘ˇ˛8Lò˘¯ Èÿ˘
ºLò˘ˆ Èê¯úLò˘¯ Ȇ¯\Lò˘ˆ Ȇ¯\L!ò˘¯ Ȇ00\LòÌ È†0˛0\LòÔ È†3>8€>\LòÌ Èˇ†332d„33\LòÔ È†338`√33\LòÌ È†33`√3?\LòÔ È|†33`√30\LòÌ ÈD†33&d√31\OòÔ ÈD†>8√>\LòÌ ÈD†¯\LòÔ È«ê†¯\OòÌ È    
†¯\OòÔ ÈÇê¯úLòÌ ÈDÿ˘
ºLòÔ È(
«˘ˇ˛8LòÌ È
¯¯LòÔ È˜ˇLòÌ È¯ˇ‡LòÔ?Áˇ¯ˇÄLò√Lò√Lò√Lò√Lò√Lò√Lò√Lò√Nò√Nò√Oü√ˇŒê√Ä√¬ˇ˛¬ˇ˛¬¡¡¡¡¡¡¡¡¡¡¡¡¬¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¬¡¡¡¡¡¡¡¡¬¡¡¡¡¡¡¬¬¬¬¬¬¬¡¡¡¡¡¬¡¡¡¡¡¡¡¡¡¡¡¬¡¡¡¡¡¡¡¡¡¡¡,˚    œÄ<ÉÄ
Ò˝8˝˛˛à˛à
Ä-˚@B
Ñ@
¸D"˝
˛˛˛ÄÄÒ1˚+ @Ä@
"\‡B
√ã1·
ƒO]è.òpá√àÄÛ1˚# 0Ä@

"a$L…$Hë"`àë0˛àë$HÄÛ0˚*» ÄÄ
·"A>"»âHê @àë àxàë$EÚ0˚#.pÅ

"A"
ƒHâ
ƒHé @àü ˛àë$BÚ0˚# Ç

"A $Hâ$HÅ @àê ˛àë$EÚ1˚#@BÑ

&A@ A$Hâ$»ë"@àë ˛àë$HÄÛ1˚+œÄ<á¿

@‡|~A
√»â·
√O@è àxá√àÄÛÒ
ı
Ú
ÔÒı
ÚÔ
ÒÂÔ¡¡¡¡¡¡¡¡¬¡¡¡¡¡¡¡¬¬¬¡¬¡˚!@œ˚
˛
¿œ˚cå8∞G<qp‘˚"!D»Hô"DâÄ‘˚"!DàGëDâ”˚"!DàHë"D˘”˚"!DàHë"DÅ‘
˚"!DàHë"Dâ‘
˚ ƒ8àGë<q‘
Ò”
ÒD”
Ò8“¡¡¡¡+˚Ä @
  ˝¸A*˚Ä ¿
  ˝˛!˘@Ò0˚*é" "√å<pG1cá,"«.q„¬0·«q` Yã1Δ8„,Ú2˚*ë" #$DDàHëëë2#"0â""âê "fL…""DA2Û2˚*ë@"$DàGêê""" y"
‚â "DHâ" <A"Û2˚*ü@"#ÑD¯Hêé""" â""â "DHâ" DA"Û0˚*êÄ" DDÄHêÅ""" â""â "DHâ" DA"Ú0˚*ëÄ"$DDàHëë""" â""â!"DHâ2""DA"Ú0˚*éÄ"#Ñ<pGé«" "!é y„¬··àqDHà“"<1"ÚÍ ˝

flÍ@˝

fl¡¡¡¡¡˚0˝÷˚!˝’˚‡ Yè8qp,8◊˚ë "fHëâÄ2Dÿ˚àë "DHëâ"@ÿ˚àë "DHë˘"@◊˚»ë "DHëÅ"@◊˚Hë!"DHìâ"D◊˚O‡DOq"8 ÿ˙
¸˛‘˙
¸˛‘ˇÿ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-38    )BUsing the Edition Manager4^*¿
¯
.°dONLNd\lhs(el
Yï°dONLNd
\rh‚)ou pass a new subscriber rg`°dONLNd\‚h˝)peply r9¿°dONLNd!\˝h
)ecor °dONLNd%\
h
z)d as a parameter to the ,
Courier °dONLNd=\
zh
Ï)kNewSubscriberDialog °dONLNdP\
Ïh
Ó)r
 .
°dONLNdQiluì(rl    function..°dONLNd[Älå~*TYP°dONLNd^Ä~åÑ)
E°dONLNdaÄêåñ)
N°dONLNdbÄñå
)ewSubscriberReply =°dONLNdxéêö¥(óêRECORD°dONLNdÇú¢®“+canceled°dONLNdäú“®ÿ)0
:°dONLNdèúÍ®)
B°dONLNdêú®
)oolean°dONLNdñú
®
)$
;°dONLNdõú
2®
8)
{°dONLNdúú
8®
J)use°dONLNdüú
J®
í)r clicked Ca°dONLNd´ú
í®
§)Hnce°dONLNdÆú
§®
∞)l}°dONLNd¥™¢∂®(≥¢
f°dONLNdµ™®∂‰)
ormatsMask°dONLNdø™‰∂Í)<
:°dONLNdƒ™Í∂)
S°dONLNd≈™∂
&)    ignedByte°dONLNdŒ™
&∂
,)6
;°dONLNd”™
2∂
8)
{°dONLNd‘™
8∂
û)formats required}°dONLNdÈ∏¢ƒfi(¡¢
container:°dONLNd˜∏̓
h)HEditionContainerSpec;°dONLNd
∏
hƒ
Ê)~{initially, default }°dONLNd
3Δ
2“
Ê(œ
2{ name & location of edition }°dONLNd
]‘
2‡
Ï*{ to subscribe to; on return, }°dONLNd
à‚
2Ó
‘*{ edition name & location }°dONLNd
Ø
2¸
∞*{ chosen by the user}°dONLNd
«˛ê

ñ(
ê
E°dONLNd
»˛ñ

®)ND;°dONLNd
Ã
l
"Ä(
lThe °dONLNd
–
Ä
"∞)canceled°dONLNd
ÿ
∞
"π)0 fi°dONLNd
€
π
"Œ)    eld rR`°dONLNd
‡
Œ
"
A)eturns a Boolean value of R`°dONLNd
˙

A
"
Y)sTRUER`°dONLNd
˛

Y
"
ÿ) if the user clicked Cancel. Tg`°dONLNd

◊
"
fi)~o .
°dONLNd
#l
/
fi(
,lUindicate which edition format types (text, graphics, or sound) your application can rÇ°dONLNds
#
fi
/
Ú(
,
fiead, .°dONLNdx
0l
<ü(
9lyou set the °dONLNdÑ
0ü
<·)3formatsMask°dONLNdè
0·
<Í)B fi°dONLNdí
0Í
<
3)    eld to one or morR`°dONLNd£
0
3
<
å)Ie of these constants:°dONLNdπ
Gl
Sä(
PlCONST°dONLNd¿
Gê
SÍ)$kPICTformatMask°dONLNd’
G¸
S
)l= 1°dONLNdÿ
G

S
)
;°dONLNdfi
G
V
S
h)H{ca°dONLNd·
G
h
S
‡)n subscribe to 'PICT°dONLNdı
G
‡
S
Ï)x'}°dONLNd˜
G
Ï
S
Ú)
 °dONLNd˚
Uê
aÍ(
^êkTEXTformatMask°dONLNd
U¸
a
)l= 2°dONLNd
U

a
)
;°dONLNd
U
V
a
»)H{can subscribe to '°dONLNd,
U
»
a
‡)rTEXT°dONLNd0
U
‡
a
Ï)'}°dONLNd5
cê
o‰(
lêksndFormatMask°dONLNdI
c¸
o
)l= 4;°dONLNdR
c
V
o
\)Z
{°dONLNdS
c
\
o
»)can subscribe to '°dONLNde
c
»
o
‡)lsnd °dONLNdi
c
‡
o
Ï)'}.
°dONLNdl
{l
ár(
Ñl
Tµ¿°dONLNdm
{q
á
á)>o support a combination of formats, add the constants together#°dONLNd´
{
á
á
œ(
Ñ
á. For example, a .°dONLNdº
àl
îÆ(
ëlformatsMask°dONLNd«
àÆ
î
–)BB of 3 displays both graphics and text edition format types in the .
°dONLNd    
ïl
°Õ(
ûlsubscriber dialog box.ˇˇ¬.°dONLNd 
ßl
≥*The ˇˇF$B°dONLNd$
ßÄ
≥∂)    containerˇˇ¬B°dONLNd-
ß∂
≥æ)6 fi°dONLNd0
ßø
≥
)    eld is of data type ˇˇF$ŒT°dONLNdD
ß

≥
ä)SEditionContainerSpecˇˇ¬ŒT°dONLNdX
ß
ä
≥
é)x. b¿°dONLNdZ
ß
è
≥
ñ)
Yw¿°dONLNd[
ß
ï
≥
¯)ou must initialize the °dONLNdr
¥l
¿¢(
Ωl    container°dONLNd{
¥¢
¿®)6 fPÄ°dONLNd}
¥®
¿
V)&ield with the default edition volume r"‡°dONLNd£
¥
V
¿
h)Æeferı@°dONLNdß
¥
g
¿
ú)ence number7‡°dONLNd≤
¥
ú
¿
Ø)5, dir
@°dONLNd∑
¥
Ø
¿
fi)ectory ID, °dONLNd¬
¡l
Õs(
 l
fi°dONLNdƒ
¡s
ÕÀ)lename, and part. Tï°dONLNd◊
¡ 
Õ
)Wo do so, use the ï°dONLNdË
¡

Õ
∞)DGetLastEditionContainerUsedï°dONLNd
¡
∞
Õ
„)¢ function to .
°dONLNd
Œl
⁄
(
◊l@obtain the name of the last edition displayed in the dialog box..°dONLNdQ
Âl
Ò
2*!err := GetLastEditionContainerUse°dONLNdr
Â
2
Ò
>)Δd(°dONLNdt
Â
>
Ò
Ä)container);.
°dONLNdÄ
˝l    ≠(lThis function rj¿°dONLNdè
˝≠    
√)A@eturns the last edition container for which a new section was cr•°dONLNdœ
˝
√    
›(
√eated ˇˇÚ⁄.°dONLNd’
lñ(l
using the ˇˇÿée¥°dONLNdfl
ó”)+
NewSectionˇˇÚ⁄e¥°dONLNdÈ
”
)< function. If ther¢°dONLNd˚


¯)I5e is no last edition, or if the edition was deleted, °dONLNd0l#
( lGetLastEditionContainerUsed°dONLNdK
#
*)¢ still rR`°dONLNdS
*#
j)eturns the corr$¿°dONLNdb
j#
†)@ect volume r˜ °dONLNdn
ü#
±)5efer…Ä°dONLNdr
±#
Ë)ence number °dONLNd~$l0ç(-land dirR`°dONLNdÖ$ç0
 )!"ectory ID to use, but leaves the fiR`°dONLNd®$
 0
v)ìlename blank and r$¿°dONLNd∫$
v0
•)Veturns the $¿°dONLNd≈$
•0
…)/fnfErr$¿°dONLNdÀ$
…0
À)$
 .
°dONLNdÃ1l=o(:l
rE°dONLNdÕ1p=á)esult ˝Ä°dONLNd”1á=û)code.ˇ1F@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-39
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿.°dONLNd\ähû(eäThe ,
Courier°dONLNd\ûh‘)    container°dONLNd\‘h›)6 fi°dONLNd\›h
2)    eld is of data type °dONLNd$\
2h
™)UEditionContainerSpec°dONLNd8\
™h
≠)x
.°dONLNd:sä
2(|äTYPE EditionContainerSpec = °dONLNdXÅúç¿+RECORD°dONLNdaèÆõfi+theFile:°dONLNdoè
õ
D)lFSSpec;°dONLNd{è
tõ)Z{file containing edition }°dONLNd£ù
t©
û*{ data}°dONLNd≠´Æ∑
(¥ÆtheFileScript:°dONLNd¡´
∑
\)lScriptCode;°dONLNd—´
t∑
)Z{script code of filename}°dONLNdÌπÆ≈fi(¬ÆthePart:°dONLNd˚π
≈
J)lLongInt;°dONLNd
π
t≈
¯)Z{which part of file, }°dONLNd
,«
t”
˛*{ always kPartsNotUsed}°dONLNd
F’Æ·ˆ(fiÆthePartName:°dONLNd
X’
·
>)lStr31;°dONLNd
c’
t·
∞)Z
{reserved}°dONLNd
p„ÆÔ
(ÏÆthePartScript:°dONLNd
Ñ„
Ô
\)lScriptCode;°dONLNd
î„
tÔ
∞)Z
{reserved}°dONLNd
†Òú˝¥(˙úEND;°dONLNd
•
    ä
•(
äThe fi°dONLNd
´
    •
∂)eld °dONLNd
Ø
    ∂
‡)theFile°dONLNd
∂
    ‡

)* is of type °dONLNd
¬
    


2).FSSpec°dONLNd
»
    
2

I)$. See .
°dONLNd
Œ
    
I

¶)Inside Macintosh: Files.F‡°dONLNd
Â
    
ß
)^ for further information .
°dONLNd
˛
ä
"ù(
äon fiS†°dONLNd
û
"Ê)le system specifi\‡°dONLNd
Ê
"
)Hcation rÉ¿°dONLNd


"
)!ecor¯ °dONLNd 


"
%)ds.°dONLNd$
(ä
4©(
1äAfter fi&Ä°dONLNd,
(™
4‚) lling in the fid°dONLNd;
(‚
4
[)8elds of the new subscriber r‰`°dONLNdW
(
[
4
t)yeply rl†°dONLNd]
(
u
4
á)ecor·°dONLNda
(
á
4)!d, pass it as a parameter to the .°dONLNdÇ
5ä
A¸(
>äNewSubscriberDialog°dONLNdï
5¸
A
„)r4 function, which displays the subscriber dialog box.°dONLNd 
Lä
X
V(
Uä"err := NewSubscriberDialog(reply);°dONLNdÌ
dä
p
s*5After displaying the subscriber dialog box, call the °dONLNd"
d
s
p
Ø)È
NewSection°dONLNd,
d
Ø
p
Í)< function to crR`°dONLNd;
d
Í
p);    eate the .
°dONLNdD
qä
}Ø(
zä    section r≠Ä°dONLNdM
qØ
}¡)%ecor!‡°dONLNdQ
q¬
}
)d and the alias r⁄‡°dONLNdb
q

}
)FecorO@°dONLNdf
q

}
7)d. See æ°dONLNdm
q
7
}
G)“Crö°dONLNdp
q
G
}
∞)eating the Section RecorY‡°dONLNdà
q
±
}
Õ)jd and `°dONLNdé
q
Õ
}
ˇ)Alias Recor{¿°dONLNdô
q
ˇ
})2d” °dONLNdú
~ä
äfi(
áäbeginning on page V °dONLNdÆ
~fl
äÒ)U2-15™°dONLNd≤
~Ò
ä
`) for detailed information.°dONLNdÕ
êä
ú
    (
ôä If the subscriber is set up to r °dONLNdÌ
ê


ú
˘)Ä6eceive new editions automatically (not manually), the °dONLNd#
ùä
©
Ê(
¶äKEdition Manager sends your application a Section Read event. Whenever your °dONLNdn
™ä
∂¬*application r{‡°dONLNd{
™¬
∂
r)8)eceives a Section Read event, it should r_`°dONLNd§
™
r
∂)∞%ead the contents of the edition into °dONLNd…
∑ä
√«(
¿äthe subscriber∑‡°dONLNd◊
∑«
√…)=
.°dONLNdŸ
…ä
’∏(
“äListing 2-6 @°dONLNd‰
…π
’
)/ illustrates how to cr&Ä°dONLNd˙
…

’
\)Zeate a subscriber÷†°dONLNd
…
[
’
`)H. x@°dONLNd
…
`
’
∏)As described earlier„°dONLNd!
…
∑
’)W, you must set up °dONLNd3
֊
‚
π(
fläFand display the subscriber dialog box to allow the user to subscribe tÜ`°dONLNdy
÷
π
‚
Ô(
fl
πo any of the °dONLNdÜ
„ä
Ôè(
Ïä
a°dONLNdá
„è
Ô‹)vailable editions. Œ†°dONLNdö
„‹
Ô
I)MAfter your application crR‡°dONLNd≥
„
J
Ô
ó)neates a subscriber@°dONLNd≈
„
ó
Ô
Î)M, your application r∫@°dONLNdŸ
„
Î
Ô)T
eceives a °dONLNd„
ä
¸Ô(
˘äSection Read event to r»¿°dONLNd˙
Ô
¸
©)e+ead in the data being subscribed to. Be sur$‡°dONLNd%

™
¸
˛)ªe to add the newly °dONLNd8
˝ä    í(äcrµ@°dONLNd:
˝í    
Y)1eated section to your list of sections for this fi@°dONLNdl
˝
Z    
{)»le. Ther9°dONLNdt
˝
{    
ã)!e arG†°dONLNdx
˝
ã    
∫)
e many difp °dONLNdÇ
˝
∫    
Δ)/ferR†°dONLNdÖ
˝
Δ    )ent techniques °dONLNdî
ä°(äfor crÒ@°dONLNdö
°
’)Geating subscribers and unique IDs; this listing displays one technique.ˇh@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-40    )BUsing the Edition Manager4^*¿
¯

g*n
¯4g*n
¯"h*_

ˇ·ˇ‚7^
°dONLNd\lgò(dlListing 2-6°dONLNd\∞g
)DCreating a subscriber,
Courier
.°dONLNd$vlÇ
»(l:PROCEDURE DoNewSubscriber(thisDocument: MyDocumentInfoPtr)°dONLNd^v
Ȃ
Œ(
»
;°dONLNd`Ñlêr(çl
V°dONLNdaÑrê~)AR°dONLNdeí~û¿+getLastErr:°dONLNduíÿû¸)ZOSErr;°dONLNd}†~¨∫(©~
dialogErr:°dONLNdå†ÿ¨¸)ZOSErr;°dONLNdîÆ~∫¿(∑~sectionErr:°dONLNd§Æÿ∫¸)ZOSErr;°dONLNd¨º~»¢(≈~resID:°dONLNd∑ºÿ»
)ZInteger;°dONLNd¡ ~÷Ã(”~thisSectionH:°dONLNd” ÿ÷
,)ZSectionHandle;°dONLNd„ÿ~‰¢(·~reply:°dONLNdÓÿÿ‰
D)ZNewSubscriberReply°dONLNd
ÿ
D‰
J)l
;°dONLNd
ÊlÚr(Ôl
B°dONLNd
ÊrÚä)EGIN°dONLNd
    Ù~
ê+{pu°dONLNd
Ùê

z)'t default edition name into reply recor°dONLNd
3Ù
z

Ü)Íd}°dONLNd
7
~
Δ(
~getLastErr :°dONLNd
C
Δ
ÿ)H= G°dONLNd
F
ÿ

⁄)+etLastEditionContainerUsed(reply.container)°dONLNd
q

⁄

‡(

⁄
;°dONLNd
t
~
ê(
~{ca°dONLNd
w
ê

D)n subscribe to pictures or tex°dONLNd
ï

D

P)¥t}°dONLNd
ô
~
*
8(
'~reply.formatsMask := kPICTforma°dONLNd
∏

8
*
D)∫tM°dONLNd
∫

D
*
§)ask + kTEXTforma°dONLNd
 

§
*
∞)`tM°dONLNd
Ã

∞
*
¬)ask°dONLNd
œ

¬
*
»)
;°dONLNd
“
,~
8ê(
5~{di°dONLNd
’
,ê
8Í)splay dialog bo°dONLNd
‰
,Í
8
)Zx & l°dONLNd
È
,

8
V)et user selec°dONLNd
ˆ
,
V
8
Ú)Nt edition to subscribe to}°dONLNd
:~
F
h(
C~'dialogErr := NewSubscriberDialog(reply)°dONLNd9
:
h
F
n)Í
;°dONLNd<
H~
TÑ(
Q~
I°dONLNd=
HÑ
T
)F dialogErr <> noErr THEN°dONLNdV
H

T
 )ñ
 °dONLNdZ
Vê
bñ(
_ê
M°dONLNd[
Vñ
b
)yErrHandler(dialogErr)°dONLNdq
V

b
 )Ñ
;°dONLNd{
V
2
b
º){handle error and exit}°dONLNdî
d~
pÑ(
m~
I°dONLNdï
dÑ
p¸)F reply.canceled THE°dONLNd©
d¸
p
)xN °dONLNd∏
rê
~ñ(
{ê
E°dONLNdπ
rñ
~
)XIT(DoNewSubscriber);°dONLNd◊
r
2
~
‡)ú{do nothing if user canceled}°dONLNdˆ
Ä~
åê(
â~{Ad°dONLNd˘
Äê
å
⁄)7vance counter to make a new unique sectionID for this }°dONLNd2
é~
ö
Ê(
ó~<{ document. It is not necessary to equate section IDs with }°dONLNdp
ú~
®Ã*{ resources.}°dONLNd
™~
∂
Ú*>thisDocument^.nextSectionID := thisDocument^.nextSectionID + 1°dONLNdΩ
™
Ú
∂
¯(
≥
Ú
;°dONLNd¿
∏~
Đ(
¡~{cr°dONLNd√
∏ê
ƒ
 )eate a subscriber sectio°dONLNd€
∏
 
ƒ
,)ên}°dONLNdfl
Δ~
“
t(
œ~)sectionErr := NewSection(reply.container,°dONLNd
‘¥
‡∫+6
 °dONLNd
‘

‡
∞)Z thisDocument^.fileSpecPtr,°dONLNd8
‚

Ó
h* stSubscriber, °dONLNdQ


¸
º* thisDocument^.nextSectionID,°dONLNds
˛¥
∫(¥
 °dONLNdy
˛


º)Z sumAutomatic, thisSectionH);°dONLNdò~
(~IF sectionErr <> noErr THE°dONLNd≤

 )ú
N°dONLNd∂ê&ñ(#ê
M°dONLNd∑ñ&
&)yErrHandler(sectionErr);°dONLNd–
&&
∞)ê{handle error and exit}°dONLNdÈ(~4Ñ(1~
r°dONLNdÍ(Ñ4
V)#esID := thisDocument^.nextSectionID°dONLNd(
V4
\)“
;°dONLNd6~Bê(?~{ad°dONLNd6êB
2)d this section/alias pair t°dONLNd.6
2B
h)¢    o app's i°dONLNd76
hB
‘)6nternal bookkeepin°dONLNdI6
‘B
‡)lg}°dONLNdMD~Pä(M~My°dONLNdODäP
Œ)6AddSectionAliasPair(thisDocument, thisSectionH, resID)°dONLNdÖD
ŒP
‘(M
Œ
;°dONLNdàR~^Ñ([~
{°dONLNdâRÑ^
Ú)=Remember that you will receive a Section Read event to read }°dONLNd»`~l
‘(i~9{ in the edition that you just subscribed to because the °dONLNd
`
‘l
⁄(i
‘
}°dONLNdn~z
b(w~&{ initial mode is set to sumAutomatic.°dONLNd*n
bz
h)‰
}ˇˇ¸°dONLNd-|~àÑ(Ö~
{°dONLNd.|Ñà
˜)?Remember that the section and alias records need to be saved } °dONLNdoä~ñ
û(ì~0{ as resources when the user saves the document.°dONLNdüä
ûñ
§(ì
û
}°dONLNd°òl§~(°lEND°dONLNd§ò~§ä); ˇ9Ó@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-41
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

jHp4jHp käk

ˇ·ˇ‚7^°dONLNd\äj
q(fä)Opening an Edition Container to Read Dataˇˇˇˇˇˇ‘@(f
2
.°dONLNd+pä|£(yäBeforR`°dONLNd0p£|Æ)e r$¿°dONLNd3pÆ|Ô)eading data fr˜ °dONLNdApÓ|
{)@ om an edition, you must use the ,
Courier˜ °dONLNdap
{|
Ω)çOpenEdition˜ °dONLNdlp
Ω|
Ë)B function. …Ä°dONLNdwp
Ë|
Ô)+
YfiÄ°dONLNdxp
Ó|
˛)our .
°dONLNd|}äâ
Ö(Üä:application should only use this function for a subscriberp°dONLNd∂}
Öâ)˚$. Use this function to initiate the °dONLNd⁄ääñç(ìä
rE°dONLNd€äéñ◊)eading of data fr3†°dONLNdÏä◊ñ
)Iom an edition..°dONLNd˚°ä≠(™äerr := OpenEditio°dONLNd
°≠¸)fn(°dONLNd
°¸≠
§)subscriberSectionH, refNum);.
°dONLNd
+πä≈©(¬äAs a prK`°dONLNd
2π™≈
) ecaution, you should r]‡°dONLNd
Hπ
≈
)c;etain the old data until the user can no longer undo. This °dONLNd
ÉΔä“
:(œä(allows you to undo changes if the user r`°dONLNd
´Δ
;“
g)±equests it..°dONLNd
∑ÿä‰ë(·ä
Yï°dONLNd
∏ÿê‰
)our application can supply a prg`°dONLNd
◊ÿ
‰
9)åocedur9¿°dONLNd
›ÿ
9‰
b)
e such as 9¿°dONLNd
Áÿ
b‰
∞))DoReadEdition9¿°dONLNd
Ùÿ
∞‰
¡)N to r °dONLNd
˘ÿ
¡‰
ˇ)ead in data frfiÄ°dONLNdÿ
˛‰)=om .
°dONLNd
ÂäÒ¸(Óäthe edition to a subscriber/ °dONLNd%¸Ò
ˆ)r6. When your application opens a document containing a °dONLNd[Úä˛
(˚äsubscriber that is set up to rbÄ°dONLNdyÚ
˛
ô)z!eceive new editions automatically¿°dONLNdöÚ
ô˛
˚)ï, the Edition Manager °dONLNd∞ˇä

Û(
äQsends you a Section Read event if the edition has been updated. The Section Read °dONLNd

ä
§*event M@°dONLNd
•

R))supplies the handle to the section that r”¿°dONLNd0

R

i)≠equirΰdONLNd5

i

¢)es updating. !‡°dONLNdB

£

—):Listing 2-7¬ °dONLNdM

—

”).
,B °dONLNdN

‘

÷)
 ¬ °dONLNdO

÷
)shown in the °dONLNd\
ä
%√(
"änext section, ÓÄ°dONLNdj
√
%Ã)9prµ†°dONLNdl
Õ
%
1)
ovides an example of r∂@°dONLNdÇ

1
%
n)deading data fr[Ä°dONLNdê

o
%
Æ)>om an edition.


CH
J4
DH
J 
Eä
E

ˇ·ˇ‚7^°dONLNd†
6ä
D
`(
@ä%Choosing Which Edition Format to Readˇˇˇˇˇˇ‘@(
@
2
°dONLNd«
Jä
V
Æ(
SäCAfter your application opens the edition container for a subscriberA`°dONLNd

J
Æ
V
˛(
S
Æ, it can look in the ˇˇìî.°dONLNd
Wä
c
@(
`ä*edition for formats that it understands. T
x°dONLNdI
W
@
c
¥)∂o accomplish this, use the ˇ˛∫ºÏ\°dONLNdd
W
¥
c)tEditionHasFormatˇˇìîÏ\°dONLNdt
W
c)`
 .
°dONLNdu
dä
p±(
mä    function..°dONLNd
{ä
á
*err := EditionHasForma°dONLNdï
{

á
)Ñt(°dONLNdó
{

á)'whichEdition, whichFormat, formatSize);°dONLNdø
ìä
üû(
úäThe °dONLNd√
ìû
ü˛)EditionHasFormat°dONLNd”
ì˛
ü
*)` function rR`°dONLNdfi
ì
*
ü
Y),eturns the R`°dONLNdÈ
ì
Y
ü
è)/    noTypeErrR`°dONLNdÚ
ì
è
ü
ï)6 r$¿°dONLNdÙ
ì
ï
ü
Ÿ)esult code if a r˜ °dONLNd
ì
ÿ
ü
)C    equested .
°dONLNd
†ä
¨
(
©ä!format is not available. If the rÜ`°dONLNd/
†

¨
Õ)Ö-equested format is available, this function rS`°dONLNd\
†
Œ
¨
¸)øeturns the .°dONLNdg
≠ä
π®(
∂änoErr°dONLNdl
≠®
πÆ) rR`°dONLNdn
≠Æ
π
)esult code, and the R`°dONLNdÇ
≠

π
@)V
formatSizeR`°dONLNdå
≠
@
π)<0 parameter contains the size of the data in the °dONLNdº
∫ä
Δ®(
√äspecifi°dONLNd√
∫®
Δ·)ed format or °dONLNd–
∫·
Δ
Y)9kFormatLengthUnknown°dONLNd‰
∫
Y
Δ
Ø)x (–1), which signifi°dONLNd¯
∫
Ø
Δ
)Ves that the size is .
°dONLNd
«ä
Ӵ(
–äunknownV‡°dONLNd
«µ
”∑)+
.


·H
Ô4
‚H
Ô
    °dONLNd
‡ä
Îù(
ËäNote

ˇ·ˇ‚7^
°dONLNd
Ìä
˘£*The TˆÄ°dONLNd
Ì¢
˘
Δ)Franslation Manager (if it is available) attempts implicit translation °dONLNde
˘ä”(äunder certain cirv¿°dONLNdv
˘”
§)I/cumstances. For instance, it does so when your °dONLNd•äˆ(äapplication attempts to r◊†°dONLNdæˆ
)lead frU‡°dONLNdƒ

º)(om an edition a format type that is not °dONLNdÏäï(äin π¿°dONLNdÔï
) the edition. In this case, the TŒÄ°dONLNd

¢)Äranslation Manager attempts to °dONLNd.ä)≤(&ä
translate 7¿°dONLNd8≥)

))the data into the rá@°dONLNdK

)
q)Nequested format. For mor˜†°dONLNdc
q)
≤)pe information, °dONLNdr)ä5ö(2äsee –@°dONLNdv)ö5™)the -†°dONLNdz)´5Ÿ)
chapter “T*¿°dONLNdÑ)Ÿ5
B).ranslation Manager” in QÄ°dONLNdõ)
B5
å)iInside Macintosh: °dONLNd≠5äAõ(>äMorÄ°dONLNd∞5úA¢)e z °dONLNd≤5¢Aœ)
Macintosh ͆°dONLNdº5œA’)-
T͆°dONLNdΩ5‘AÌ)oolbox£†°dONLNd√5ÓA)
.,Zapf Dingbats#†°dONLNd≈8ˆ@¸)
u
°dONLNd»FäRë(Oä
AG@°dONLNd…FíR
Ù)Ofter your application opens the edition container and determines which formats .°dONLNdSä_î(\äit °dONLNdSî_¿)

wants to rR`°dONLNd%S¿_¸),ead, call the R`°dONLNd3S¸_
>)<ReadEditionR`°dONLNd>S
>_
u)B function to r$¿°dONLNdLS
u_
Ó)7ead in the edition data. Se$¿°dONLNdgS
Ó_
ı)ye .
°dONLNdi`äl”(iä“Reading and Wå°dONLNdw`”l
S)Iriting Edition Data” on page • °dONLNdî`
Sl
e)Ä2-27˘°dONLNdò`
el
j) fÇ°dONLNdö`
kl
‘)or detailed information.°dONLNd≥rä~({äXAfter you have completed writing the edition data into the subscriber section, call the .°dONLNd    äã“*CloseEdition°dONLNd    “ã
`)H" function to close the edition. Se°dONLNd    9
`ã
g)ée °dONLNd    ;
gã
Í)“Closing an Edition” on page °dONLNd    X
Íã
˝)É2-28°dONLNd    \
˝ã) f°dONLNd    ^ã)or .
°dONLNd    aåäòÁ(ïädetailed information.ˇ.@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-42    )BUsing the Edition Manager4^*¿
¯
°dONLNd\lhö(elListing 2-7 @°dONLNd\õh)/ illustrates how to r∂@°dONLNd \h
)Uead data fr†°dONLNd+\
 h
b)0om an edition. Ä°dONLNd:\
bh
∫)BAs described earliery@°dONLNdN\
πh
Í)W, you must .°dONLNdYilu
?(rl.open the edition, determine which formats to rR`°dONLNdái
?u
w)”ead, use the ,
CourierR`°dONLNdîi
wu
π)8ReadEditionR`°dONLNdüi
πu
Ï)B function to °dONLNd¨vlÇp(l
rR`°dONLNd≠vpÇı)ead in data, and then use the R`°dONLNdÀvıÇ
=)ÖCloseEditionR`°dONLNd◊v
=Ç
˜)H- function to close the edition. This listing .
°dONLNd
ÉlèØ(ålshows how to r2†°dONLNd
É∞èÎ)Dead only text.

≤*∫
¯4≥*∫
¯"≥*_

ˇ·ˇ‚7^
    °dONLNd
"®l≥ò(∞lListing 2-7°dONLNd
.®∞≥
)DReading in edition data
.°dONLNd
G¬lŒ
∞(Àl6PROCEDURE DoReadEdition(theSubscriber: SectionHandle);°dONLNd
~–l‹~*VAR°dONLNd
Éfi~ÍÆ+eRefNum:°dONLNd
ëfiÍÍ
>)lEditionRefNum;°dONLNd
°Ï~¯Æ(ı~openErr:°dONLNd
ØÏͯ
)lOSErr;°dONLNd
∑˙~
Æ(
~readErr:°dONLNd
≈˙Í

)lOSErr;°dONLNd
Õ
~
¥(
~    closeErr:°dONLNd
‹
Í

)lOSErr;°dONLNd
‰
~
"Ã(
~thisDocument:°dONLNd
˜
Í
"
V)lMyDocumentInfoPtr;°dONLNd
$~
0¿(
-~textHandle:°dONLNd
$Í
0
)lHandle;°dONLNd%
2~
>∫(
;~
formatLen:°dONLNd5
2Í
>
)lSize;°dONLNd;
@l
Lä(
IlBEGIN°dONLNdB
N~
Z
§+1{find out which document this section belongs to}°dONLNdu
\~
h
í*.thisDocument := MyFindDocument(theSubscriber);°dONLNd•
j~
v
2*{open the edition for reading}°dONLNd≈
x~
Ñ
ò*/openErr := OpenEdition(theSubscriber, eRefNum);°dONLNdˆ
Ü~
í
*IF openErr <> noErr THEN°dONLNd
îê
†
+MyErrHandler(openErr);°dONLNd/
î
 
†
™)ê{handle error and exit}°dONLNdH
¢~
Æ
(
´~{look for 'TEXT' format}°dONLNdb
∞~
º
Ê*<IF EditionHasFormat(eRefNum, 'TEXT', formatLen) = noErr THEN°dONLNd†
æ~
 ú*BEGIN°dONLNd®
Ãê
ÿ
z+'{get the handle of location to read to}°dONLNd“
ڐ
Ê
∞*0textHandle := MyGetTextInSection(theSubscriber, °dONLNd
Ë
D
Ù
J+¥
 °dONLNd
Ë
J
Ù
P)
 °dONLNd
Ë
P
Ù
§)thisDocument);°dONLNd"
ˆê
n(
ˇê%SetHandleSize(textHandle, formatLen);°dONLNdJê¸*HLock(textHandle);°dONLNd_ê
Œ*5readErr := ReadEdition(eRefNum, 'TEXT', textHandle^, °dONLNdû 
,
\+~  formatLen);°dONLNdÆ.ê:
Ú(7ê;MyUpdateSubscriberText(theSubscriber, textHandle, readErr);°dONLNdÏ<êH
*HUnLock(textHandle);°dONLNdJêV
*IF readErr = noErr THEN°dONLNdXêdÆ*BEGIN°dONLNd(f¢r
Ï+7{The read was successful; now close the edition. When }°dONLNdct¢Ä
Ê*6{ successful = TRUE, the section data = edition data.}°dONLNdùÇ¢é
í*(closeErr := CloseEdition(eRefNum, TRUE);°dONLNd…ê¢ú
*EXIT(DoReadEdition);°dONLNd‡ûê™®(ßêEND;°dONLNdÚ¨~∏ñ(µ~END;°dONLNd¯¨¢∏
 )${of EditionHasFormat}ˇ@–@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-43
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\úh
Ê(eú7{'TEXT' format wasn't found or read error; just close }°dONLNd9júv
¯*:{ the edition. FALSE tells the Edition Manager that your }°dONLNduxúÑ
∞*.{ application did not get the latest edition.}°dONLNd•Üúí
í*)closeErr := CloseEdition(eRefNum, FALSE);°dONLNdœî䆮(ùäEND; 

ΔHÕ4«HÕ »ä»

ˇ·ˇ‚7^ˇˇ‹..
ˇ◊°dONLNd÷∑äΔ
|*%&Using Publisher and Subscriber Optionsˇˇˇˇˇˇ€r(¬
2
°dONLNd˛ÕäŸê(÷ä
Y@Ä°dONLNdˇÕêŸ
$)#ou can allow users to set several sË¿°dONLNd
"Õ
$Ÿ
Ô)î.pecial options associated with publishers and °dONLNd
P⁄äÊ∑(„ä
subscriber‡°dONLNd
Z⁄∏Êæ).s.‘‡°dONLNd
\⁄æÊ¿)
 T‡°dONLNd
]⁄¡Ê«)
T䆰dONLNd
^⁄ΔÊ
)o set these prt@°dONLNd
l⁄
Ê
):efer `°dONLNd
p⁄
Ê
Ì)2ences, users change settings in two dialog boxes pT‡°dONLNd
¢⁄
ÌÊ
)‹
r‡°dONLNd
£⁄
ÒÊ)ovided °dONLNd
™ÁäÛÚ(äby the Edition Manager†°dONLNd
¿ÁÛÛ
∏)i-: publisher options and subscriber options. TK °dONLNd
ÌÁ
∑Û
«)ƒo m†°dONLNd
Á
»Û)ake these dialog °dONLNd
Ùä
˙(˝äboxes available to the use°dONLNdÙ˚
˛)q
r5@°dONLNdÙ˛

), pr¸`°dONLNd Ù


3)    ovide a cV °dONLNd)Ù
4

π)(ommand in the Edit menu thad°dONLNdDÙ
π

Ê)Öt toggles bÛ °dONLNdOÙ
Ê
)-etween °dONLNdV

ä

Ê(

äMPublisher Options (when the user has selected a publisher within a document) °dONLNd£
ä
ù*and Ì °dONLNdß
ù

ı)LSubscriber Options (when a user has selected a subscriber within a document)Ω†°dONLNdÛ

ˆ

¯(

ˆ
.=†°dONLNdÙ

˘

˚)
 °dONLNdˆ
 ä
,Ë(
)äWhen a user chooses ]°dONLNd

 È
,
)_one of 6‡°dONLNd
 

,
’)+these menu commands, you need to display th[`°dONLNd<
 
’
,
Ò)Œe apprn@°dONLNdB
 
Ò
,)opriate ˇˇË∫.°dONLNdJ
-ä
9ê(
6ä
d°dONLNdK
-ê
9‚)ialog box. Use the ˇˇ∫."Ë°dONLNd^
-„
9
[)SSectionOptionsDialogˇˇË∫"Ë°dONLNdr
-
[
9
æ)x function to display th≈–°dONLNdâ
-
æ
9)ce publisher options .
°dONLNdù
:ä
FÔ(
Cäor subscriber options dB°dONLNd¥
:
F
L)fialog box on the user °dONLNd…
:
M
F
c)]’s scr†°dONLNdœ
:
c
F
t)een..°dONLNd‘
Qä
]
&(
Zäerr := SectionOptionsDialo°dONLNdÓ
Q
&
]
2)úg(°dONLNd
Q
2
]
\)reply);.
°dONLNd¯
iä
u
5(
rä&Each dialog box contains information r‰‡°dONLNd
i
5
u
H)´egar†°dONLNd"
i
I
u
÷)"ding the section and its edition. A`°dONLNdD
i
÷
u
Ó)çFigur °dONLNdI
i
Ó
u)e 2-13±†°dONLNdO
i
u    )
 °dONLNdP
vä
Ç
‚(
äLshows the publisher options dialog box with the update mode set to On Save. 


§H
µ4
•H
µ"
•H]

ˇ·ˇ‚7^
    °dONLNdû
öä
•∫*#Figure 2-13°dONLNd™
öÃ
•
’)B@The publisher options dialog box with update mode set to On Save


¥à2òÄ>
V
ÌHH



\*4

ˇˇˇˇˇˇ

V
Ì
∑ãß
Àƒˇ¯Ä≈Ä≈ü≈ˇ»ü≈ˇ»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»òÙˇ¯Â»òÙ»òÙ»òÙ»òÙ»$
ò>03`˛™„¸
˛»#
ò300`˛U
ê¸˝»&ò33>3|<l<`˛
É?„„
Ûgèèåpˇå»$
ò˝32ffpf`

√˝33à˛Ã»
ˇ»%ò>˛38ff`f˛
„˝33˛Ã¿˛»&ò0˛3f~`f
s˛3?3˛Ã¿|»%ò0˛3f``f˛˝303˛Ã¿8»%ò0˛3&fb`f`U
˝313˛Ã»»& ò0>3f<`<`™„33„
ÛœåÃp»òÙ¸˛0¸»òÙ¸0¸»òÙ˘

‡˙»òÙ»òÙ»òÙˇ¸Â»òÙ
ˇ¸Â»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»    
ò»ˇ¯»ò≈»    
ò»ˇ¯»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò
Å3¿–»
òÄ
ÅÄ0œ»òÅÅÛ<«èá”»
òôôÅÉ3˛Ãò”»òôôÅ„3ÃÃŒ“»ò
ÉüôôÅÉ3Ãëș®Úˇ˛»ò
òôÅÉ3ÃÃ√ÄÈÚ
Ä»ò    òôôÅÉ3ÃÃ…òÊÒÄ»òèÅÒÛ«å«È Ò@»òÿ Ò@»ò› <˝¿¯¿Ã
IJ@»òÿ b˝¿Ã¿¿
IJ@»ò› `<|8x¿ÃïÃqÒ∞@»òÿ `Ffdÿ˝Ã…ôô¿@»ò› `>f`ÿ¯˛Ã·ôôÄ@»òÿ `ff`¸¿¿˛Ãqô˘Ä@»ò› `ff`˛¿˛Ã9ôÅÄ@»òÿ bffdƒ¿¿˛ÃôôâÄ@»ò› <>f8x¿¿|¯ÃqòÒÄ@»ò¸xfi Ò@»
ò
Ü
‡Â Ò@»ò˝
02‚ Ò@»òy3‡0<f<ËÒÄ»ò˝¸É308FffÂÚ
Ä»ò¸É30>ffËÚˇ˛»ò˝¸É30ff~“»ò¸É30ff`ËÏ»ò˝y30&fdb“»ò

„0>x<ËÏ»ò˝

ÜÀ»ò˛x·Ï»ò≈»ò›Ï»ò≈»òÔÚˇ¯Ï»òÌ`ÚÍ»òÔ@ÚÏ»ò¸xÛÄÚ
Í»ò
ÜÛÄÚ
Ï»%ò˝

˝3˙Ä
Å3¿Ç˛
Í»(ò
˝3˙ÄÄ
ÅÄ0˛¬˛
Ï»'ò˝    Éá>333˚ÄÅÅÛ<«èÄ‚<f`
Í»*òÉœ#33#33˚ÄôôÅÉ3ÃÿÚff`
Ï»'ò˝    Ç˚3333˚ÄôôÅ„3Ãÿ∫ff`
Í»&òÇs˚3˚ÄüôôÅÉ3Ãÿûff`
Ï»#ò˝
#˚3˚Ä
òôÅÉ3Ãÿéff`
Í»&ò
˚3˚Ä    òôôÅÉ3ÃÿÜff@
Ï»'ò˝    
Ü33˚ÄèÅÒÛ«å¿Ç<Ä
Í»ò˛x˙˚ÄÚ
Ï»òÙ#˚ÄÚ
Í»òˆ˚ÄÚ
Ï»òÌ@ÚÍ»òÔ`ÚÏ»òÌÚˇ¯Í»ò›Ï»ò≈»ò›Ï»ò≈»ò›Ï»ò≈»ò›Ï»ò≈»ò›Ï»òÿ*Ò™†»+    ò xI¸¿8G¿q«¿‡Ä„É» Ï»)ò @A˚
D¿@ä(Ñ
ÅB,`λ-ò Œc∏A€≥8@˛
cú…DŒg`@Ää(áÖÖB*†Ï»+
ò $îrI§˝
î$)E$î•Ä@Äy«ÄAÅC… λ,
ò ‰ÛBI§˝
Û$ÈEîΩA
 ÄA¡B Ï»+
ò!$ÄêBI§˝
Ä•)E$î°A!AÅB λ-ò<‚gy»ì$@˛
gÁ8¬gAaΔÑ‡Ñ„Ç Ï»òÔ

˚Í˙ˇ»òÒ
˚ˆˆ˙ˇ¿»òœ˙ˇ‡»ò›ˆ>˚
»òÿ˚ˇ‡8˚ˇ¸p»ò›˚{˚x»òÿ˚r˚
8»ò› ˚t˙∏»òÿ ˚t˙∏»ò› ˝0t¿∏»òÿ IJ0tôÄ∏»ò› 0tõ˛∏»òÿ ôô30tû˛∏»ò› ôò30tú˛∏»òÿ ôò?0tû˛∏»ò› ôò00tõ˛∏»òÿ
 ˛ô10tôÄ∏»ò› ôé0t¿∏»òÿ ˚t˙∏»ò› ˚t˙∏»òÿ ˚t˙∏»ò›˚r˚
8»òÿ˚{˚x»ò›UT˚ˇ‡8˚ˇ¸p»òœ>˚
»òœ˙ˇ‡»òœ˙ˇ¿»òœ˙ˇ»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ü≈ˇ»ü≈ˇ»Ä≈Ä≈ƒˇ¯√√√√√√√√√√√ƒ√√ƒƒ√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√ƒ√ƒ√√√√√√√√√√√√√√√√ƒ√√√√√√ƒ
ƒ
<    ?>‰˛A¿˛Ä@ ˛Ä@˛

D˛
@ ˛˚
: !
˝Ĭ Ä ˛˛˝D˛
@ ˛˚
=7  Å

iòÅ@ ∞¿∞ä¬N,1`≈éå,pNÉB¡àÑEuÅÉN9Åf4`8cĸ
<6  Ä¿
ô$Ä@ … »ã"Q2IÅ&Hí2à&QD√"EEFAD—"Aô$LêDí˚
<6? Ä0Â    B
@¿äÑäP"Ö(°"ÄBC(B%©DA(C$!BÖA
˚
:6  ∏    ¬
    ~8@ ãÑäN"˝(°"pBM(B"©DA(M'·BÖ¯9˙˙:6  Ä
    @@ äÑäA"Å(°"BQ(B%
DA(Q$
BÖ˙:6 !
ô4$B â »õ"Q"I
&Hí"à&SD√"E
DA6D”"A$LêDí˙;7?>h‘ÄA¿à¿∞j¬N"1≈Üå"pLëÉB¡àÅ4@’ÉLôÅ4`8aÄ˚˜˜Ä˚˘@˚˜ê˜Ä˚˙
Ä˚Ò˜`˜Ä˚˙˙√√Ô<Ä€ÔB@€Ô¿Å,›Ô Å2ë$›ÔÅ"
ÅäB›ÔÅ"Fä~›ÔÅ"HÑ@›Ô B"IÑ$›Ô¿<"ÜD›√√√√√√√√√√√√√√√√√√√√√√√¯ ÇÀIJΔÀÄÛa≈Ä™8∞·„ãÄ—Å"&@íD…$L—Ò"$@Ç<àÚ$H–Å"$@ÇDâ'»–Å"$@ÇDâ$–Å"$@ÇDâ$H–¯Ò!ƒ@Ç<àÒ„à–ˆ œ˜
 œ    ˜

¿–ƒƒ√ƒ*ƒ
  ÇÄ

˝0Ä@¸Ì'ƒ
˛ Δ˛

˝
˙Ï/+§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`Ô/+§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âêÔ/+îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚âÔ/+
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"âÔ/+åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"âÔ/åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"âÔ/+ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àqÔ
¸
‹¸
‹√√√√√
Ä˝Ä“Ä
˝Ä“(xá
‚Ãxâ√ãÄa¿’(DààÅ
2DàÑLí ‘DDààÅ
"DàÑH‘DDàèÅ
"Dàố˛Dàà

"DàÑ‘ÇDààÅ    "DòÑH ‘Çxá‚"xhc଑@ĸ@˛—@ĸ@˛ —ˇ4“@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-44    )BUsing the Edition Manager4^*¿
¯
°dONLNd\lhÑ(elFigurR¿°dONLNd\Ñhù)e 2-14@°dONLNd\ùh
√)A shows the publisher options dialog box with the update mode set °dONLNdLiluw(rlto ∑‡°dONLNdOiwu°)ManuallyI¿°dONLNdWi°u£)*
.

ó*®
¯4ò*®
¯"ò*]

ˇ·ˇ‚7^
    °dONLNdZçlòú(ïlFigure 2-14°dONLNdfçÆò
î)B9The publisher options dialog box with update mode set to êê°dONLNdüç
îò
∫)Ê    Manually 
°dONLNd™
3l
?€(
<lAs a shortcut for the userS@°dONLNdƒ
3€
?
ı)o?, you should display the publisher options dialog box when the °dONLNd

@l
L∑(
Iluser double-clickf†°dONLNd

@∏
L√)Ls a#†°dONLNd

@ƒ
L
) publisher sectiog°dONLNd
(
@

L
)Hn i†¿°dONLNd
+
@

L
X)n a document. °dONLNd
:
Rl
^Ñ(
[lFigurR¿°dONLNd
?
RÑ
^ù)e 2-15@°dONLNd
E
Rù
^
—)E shows the subscriber options dialog box with the update mode set to °dONLNd
ä
_l
k´(
hlAutomaticallyπ`°dONLNd
ó
_™
kØ)>. 


ç*
û
¯4
é*
û
¯"
é*]

ˇ·ˇ‚7^
    °dONLNd
õ
Él
éú(
ãlFigure 2-15°dONLNd
ß
ÉÆ
é
ô)B:The subscriber options dialog box with update mode set to ê°dONLNd
·
É
ô
é
—)ÎAutomatically 

ßj

¯òÄF
U+HH



\*4

ˇˇˇˇˇˇ

U+´`
à
»ƒˇ˚
≈
˚
≈
˚
≈ˇ˘˚
≈ˇ˘˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚ÛˇÂ˚Û@Ò

ÄÊ˚Û@Ò

ÄÊ˚Û@Ò

ÄÊ˚Û@Ò

ÄÊ˚*¿`
IJ@U@``˝
ÅÄ
ÄÊ˚*`
IJ@™†2˛`˝

IJ

ÄÊ˚+fgΔcèáçÉ«å˛@0g¸|c¿>l˛ÒéÒÄÊ˚)˝fLÃŒ
åÃ@Ä 8˝f`fq˛ô?·ÄÊ˚*ΔffgÃÃ
å¿˛@˝f
`f`˘ôôò¡ÄÊ˚+ffcåœÃ
å¿@Ä ˛fg‡fa˛ôòÅÄÊ˚*ffaÃÃ
å¿˛@˝ffa˛ôò
ÄÊ˚)ffdÃÃL
åÃ@™†&˝f fa˝ô
ÄÊ˚+#ÁΔcå«å«å@U@ff|c¿>`˘Òôé
ÄÊ˚Û@¸`
Ä˝

ÄÊ˚Û@¸`F
Ä˝

ÄÊ˚Û@˘<˙

ÄÊ˚Û@Ò

ÄÊ˚Û@Ò

ÄÊ˚ÛˇÄÊ˚Û?ˇÄÊ˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚»ˇ
˚
≈˚»ˇ
˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚˛‡0>c–˚
ê00œ˚
Å„·0>gòÒ„”˚
√3300fcôôì”˚˛
„330<fcôô¿”˚
PsÛ300fcôò‡ÈU˛Òˇ¿˚ 3300fcôòpËÄÒ0˚
3300fcôô3ÊÒ˚ ·„1>>aòÒò„ËÄÒ˚ÿÒ˚!‹ÄIJÄ0˛˚ÿ@˛Ä0˛˚!‹Äèáôüé>6˚ÿÃÃôò˝ô338˚!‹ÄÃÃòôôú330˚ÿÃÃòôôé3?0˚!‹ÄÃÃ˛
ôôá300˚ÿLÃÃòòôôì310˚%˛‡Äáëüé30˚¸
0¿flÒ˚˛@ <ÄÂÄÒ˚¸@ f@„Ò˚ ˛Äf|å«ÄËÄÒ˚¸ÄffÃÿÊÒ0˚ ˛ÄffáÃÿËÄÒˇ¿˚¸Äff
ÃÃœ¿”˚˛@ ff˛ÃÁÄÌ˚¸@ ffÃÃå@”˚˛0¿<fáœÄËÄÌ˚¸À˚‹ÄÌ˚
≈˚‹ÄÌ˚
≈˚ÔÒˇÄÌ˚ÌÒ¿Î˚ÔÒ@ÄÌ˚¸ÛÒ Î˚˛
0¿ÙÒ ÄÌ˚+¸@ @ ˛
`˚‡0>c@˛ Î˚/˛O ``˛
`˚
ê00˛
@˛ ÄÌ˚,¸    üêp„«ΔcΔf`¸
Å„·0>gòÒGåà Î˚0˛    üêy‰ffdff`¸
√3300fcôòLÃà ÄÌ˚,¸    üê_cÊfcÊf`¸„330<fcôòLÃà Î˚-˛üêN˚f`¸sÛ300fcôò˛Ã ÄÌ˚)¸O D˚f`¸3300fcôò˛Ã
 Î˚-˛@ @˚f`¸
3300fcôòÃû ÄÌ˚,¸    0¿@cÊc„Êc‡¸·„1>>aòÒòGè Î˚˛˘`¸Ò ÄÌ˚Ù
`¸Ò Î˚ˆ
¿¸Ò ÄÌ˚ÌÒ@Î˚ÔÒ¿ÄÌ˚ÌÒˇÍ˚‹ÄÌ˚
≈˚‹ÄÌ˚
≈˚‹ÄÌ˚
≈˚‹ÄÌ˚
≈˚‹ÄÌ˚ÿÒUT˚0Ä    "˝CÄq«Ä·
ÛÉ» ˝ÄÌ˚,Ä ˝ƒ@ä(ÅÅ$B,`Ë˚1%Ãw;vg©ús$∏¿D@ä(ÇÑDB*†˝ÄÌ˚-%íÇI"îÄJR꧕ CÄyËÑÄ!„√… Ë˚1%ûbI"îÄ
Rì§
•‡D@(á¿AB ˝ÄÌ˚-%$êI"îÄ
Rî§
•D@HÄÄÅ
Ç Ë˚1%úL·9dà    ísú „§¿CÑaáÖÒ„ ˝ÄÌ˚
 ˝Ê˚ˇ‡˚Ú
@˝ÚĘ
˙ˇ¯˚œ˙ˇ¸˚‹Ä˜
¿˚>˚◊˚ˇ¸˚ˇé˚‹Ä˚`˚o˚7    @˚CÄq«Ä·
ÛÉ» ˚˚
@˚'˚8    @˚ƒ@ä(ÅÅ$B,`˝Ä˙ÄÄ˚˚9Óqús˛©ús$∏¿D@ä(ÇÑDB*†˚˙ÄÄ˚˚BHRîIJJR꧕ CÄyËÑÄ!„√… ˝Ä
‡˛ÄÄ
„˚@ƒI“óIJ
Rì§
•‡D@(á¿AB ˚˛ÄÄ30˚A$$JRî˝
Rî§
•D@HÄÄÅ
Ç ˝Ä
„·√ΔÄÄ3`˚@ù¬I“s˛    ísú „§¿CÑaáÖÒ„ ˚33&fÄÄ3¿˚.˚˘
 ˝ÚÄ
Û3fÄÄ3Ä˚*˘`˘
@˝33ÊÄÄ3¿˚!‹Ä33ÄÄ3`˚ÿ33&&ÄÄ30˚!‹Ä
·Û1√ΔÄÄ
„˚ÿ˙ÄÄ˚˚‹Ä˙ÄÄ˚˚ÿ˙ÄÄ˚˚‹Ä˚
@˚'˚ÿ˚`˚o˚‹™Ä˚ˇ¸˚ˇé˚œ
¿˚>˚œ˙ˇ¸˚œ
˙ˇ¯˚Œ˚ˇ‡˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈˚
≈ˇ˘˚
≈ˇ˘˚
≈
˚
≈
˚ƒˇ˚ªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªªF¸¯¿à˛
¿@Ú˛˝
˛Ä ˛
@@˛
˛
˛`CÄÑ ˝ ¿0Dz˝˝ ˝@@˛
˛
å˛ GEÄÇ((yÁ @PÇ√ÄÒ¬0‚√ãÅ«é0‚√Äyáp<8àXû8·¿Yá
Î
Tqb#Ñ" G"ÄÇHâÄ @êÉ$@â"$L$D$@˛àâ"Dàdë"DB fHë"$D
$âí$D" GE¸Ç¿àâÄAAÇ$@â"$H$D$àáàâ"DP
°Dë"<B DHë"D
y#ƒ" G"ÄLJ'¸âÄÄBÇ'¿â"‚'»$D#IJàâ"D
°Dë"DC‡DHë>
«ƒ
â$D" G"ÄÇ â
C¯Ç$â"$$D @˛àâ"DPADë"DBDHë $
â$D" G"ÄÑ â2Ç@Ç$@â2"$H$D$@˛àâ"DàAD    ë"DB DHë"$D
âdD" GE¸¯¿x“‡@Ç#Ä”¬‚#à
«É‚#Äxáàp<8àADû<1¿DG
Ã
é
y£ƒ!‡¯ˆÄ˙¯˘Ì ¯àˆÄ˙˘

˘Ó
 ¯p‰‡Â

¿ªªªªªªªªªªªªªªªªªªªªª
¯ Ǭ
Ä˛Δ¬ÄÛa≈Ä™8∞·„ãÄ»Å"&@íD…$L«Ò"$@Ç<àÚ$H«Å"$@ÇDâ'»«Å"$@ÇDâ$«Å"$@ÇDâ$H«¯Ò!ƒ@Ç<à҄૘ Δ¯
 Δ¯

¿Δªªªª)ƒ
  ÇÄ

˝0Ä@¸‰&ƒ
˛ Δ˛

˝
˙„.*§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`Ê.*§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âêÊ.*îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚âÊ.*
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"âÊ.*åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"âÊ.
åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"âÊ.*ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àqÊÒ
¸
”Ò¸
”ªªªªª
Ä˝Ä…Ä
˝Ä…(xá
‚Ãxâ√ãÄa¿À(DààÅ
2DàÑLí ÀDDààÅ
"DàÑH DDàèÅ
"Dàá» ˛Dàà

"DàÑ ÇDààÅ    "DòÑH ÀÇxá‚"xhcà¬À@ĸ@˛»@ĸ@˛ »


ùj
¯òÄ>
L
ÌHH



\*4

ˇˇˇˇˇˇ

L
Ì
ûmv
≠ƒˇ¯Ä≈Ä≈ü≈ˇ»ü≈ˇ»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»òÙˇ¯Â»òÙ»òÙ»òÙ»òÙ»$ò``™„¸
˛»#ò2`˛`U
ê¸˝»&ò0f|8q∂|<l<`˛
É?„„
Ûgèèåpˇå»%ò8ffd…Δffpf`

√˝33à˛Ã»
ˇ»%òffp¡Üff`f˛
„˝33˛Ã¿˛»&òff8¡Üf~`f
s˛3?3˛Ã¿|»%òff¡Üf``f˛˝303˛Ã¿8»%ò&ffL…Üfb`f`U
˝313˛Ã»»& ò>|8qÜ|<`<`™„33„
ÛœåÃp»òÙ¸˛0¸»òÙ¸0¸»òÙ˘

‡˙»òÙ»òÙ»òÙˇ¸Â»òÙ
ˇ¸Â»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»    
ò»ˇ¯»ò≈»    
ò»ˇ¯»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»
òćf1Äœ»    ò@`0Œ»òèÊyè0“»    òΔf1˛ô0“»ò
çÃΔΔf1ôôúË™®Úˇ˛»òœΔf1ôôéÁÚ
Ä»òÃf1ôôá‰ÒÄ»òÃFf1ôôì0Ë Ò@»òáÉ„Êèé0 Ò@»ò› ¿˛
ò˛@»òÿ  ˛IJ˛@»ò› «√áåümü@»òÿ ffLÃôô2qôôú@»ò› ÊfÃôú0aôôò@»òÿ ffÃôôé0aôüò@»ò› ff
ôôá0aôò@»òÿ &ffLL    ôôì2aôòò@»"ò˛<· √Êcáåüaü@»ò¸√fi Ò@»
ò
Ň
IJcfÏ Ò@»ò˝
<É0
IJ`fÈ Ò@»!ò~C33«è¯xÛ<ffÌÒÄ»ò˝~C31åÃÃåc2FffÍÚ
Ä»"ò~CÛ1åÃÃ|c0>ffÌÚˇ˛»ò˝~C31å˛Ã
c0˛f◊»
ò
<É31å˛Ã
c0˛fÌÏ»ò˝
É31å˛Ã
c2˛f◊»ò˛√1«åÃ|3>f>ÌÏ»ò¸<ˆ◊»òÚFÌÏ»
ò<◊»ò›Ï»ò≈»òÔÚˇ¯Úˇ˛»òÌ`Ú˝Ú
Ä»òÔ@ÚÒÄ»ò¸<ÛÄÚ
˝ Ò@»ò˛√ÛÄÚ
 Ò@»7ò˝
Ç
˝3˙Ä<01å ˛
˝ 
‡˛>03`˝@»9ò
É˝3˙Äb0
Ä ˛
 0˛300`˝@»:ò˝    Cá>333˚Ä`<x3Ãx¯#Δf
˝ 3·„‡33>3|<l@»;òCœ#33#33˚Ä`f031åÃÃ&ff
 ˛30˝32ffp@»:ò˝    B˚3333˚Änf031åÃöff
˝ ˛3
0>˛38ff`@»8òBs˚3˚Äf~031åÃà    Êff
 33Û00˛3f~`@»6ò˝
Ç#˚3˚Äf`031åÃÃÊff
˝ 3300˛3f``@»8ò
Ç˚3˚Äfb031åÃÃffd
 3300˛3&fb`@»9ò¸√33˚Ä<<0ÃxÃ#«¯
˝ 
„·„00>3f<`@»"ò˛<˙˚ÄÚ
 Ù@»òÙ#˚ÄÚ
˝ Ù@»òˆ˚ÄÚ
 Ò@»òÌ@Ú˝ÒÄ»òÔ`ÚÚ
Ä»òÌÚˇ¯˝Úˇ˛»ò›Ï»ò≈»ò›Ï»ò≈»ò›Ï»ò≈»ò›Ï»ò≈»ò›Ï»òÿ*Ò™†»+    ò xI¸|@Ä@@|áp|8<ÇÏ»(ò @A˚@˛@
à¢à@D"ΔÍ»-ò Œc∏A€≥8@˛&9ÃêLÊqñà¢àxQ(QD"™Ï»*
ò $îrI§˝)BBêRIJXáúxHD<íÍ»,
ò ‰ÛBI§˝/2NêPIK–Ä¢|D ÇÏ»*
ò!$ÄêBI§˝(
RêRIJÅ"DD ÇÍ»-ò<‚gy»ì$@˛ÊqŒpÉå&qê@Ü`8NN8 ÇÏ»òÔ
Ä˚@Í˙ˇ»òÒa˙Ĉˆ˙ˇ¿»òœ˙ˇ‡»ò›ˆ>˚
»òÿ˚ˇ‡8˚ˇ¸p»ò›˚{˚x»òÿ˚r˚
8»ò› ˚t˙∏»òÿ ˚t˙∏»ò› ˝0t¿∏»òÿ IJ0tôÄ∏»ò› 0tõ˛∏»òÿ ôô30tû˛∏»ò› ôò30tú˛∏»òÿ ôò?0tû˛∏»ò› ôò00tõ˛∏»òÿ
 ˛ô10tôÄ∏»ò› ôé0t¿∏»òÿ ˚t˙∏»ò› ˚t˙∏»òÿ ˚t˙∏»ò›˚r˚
8»òÿ˚{˚x»ò›UT˚ˇ‡8˚ˇ¸p»òœ>˚
»òœ˙ˇ‡»òœ˙ˇ¿»òœ˙ˇ»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ò≈»ü≈ˇ»ü≈ˇ»Ä≈Ä≈ƒˇ¯√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√;

Û¿¿
¿ƒ˝8!¯˘˛
˛˝
˛@˝Ñ 
 ˝Ä9    
  ¸DaA˛
˛
˝˝˝ 
 ˝Ä?=

<âsÄÑ!Aa¿8â·√ã±·≈¿„«qa¿<√Ñ8xDâé,Op‡,√áé>%

ÄDâÑ@!Aí Dâ$L&
"âí ˝Dà"DàÑ2Hë"!3$Hë?=
‚„«¡@ÑDâ@x A @â$
"âDCƒDà"(PÑ"Hë!"$Hë>%
 
@Dâ¿ A‡8⃉
"â¿˝Dà"PÑ"Hë"!"$Hü>%
 
@Dâ  Aâ$
"â ˝Dà"( Ñ"Hë"!"$Hê>%
  
@Dô@@!A Dô$H$
"â ˝Dà"D Ñ"»ë"!"$Hë?;
Û¿¿
Ä<iĸ A¿8i·√à·ƒ„¡àq¿<Cƒ8xD É"O‡"#áéˇˆÌ¯˘˜ˆDÌ¯à˘˜
ˆ8„pÓ√√√ÎÄ ˛ Ä1ÄÁÎÄ ˛ ÄÁÌ8q¿p‡
8qfqáàÄËÌDàÄ!
âô" àëàÄËÌ@àÄ!â ààÄËÌ8¯Ä!â" ààÄËÌÄÄ!?ëâ" ààÄËÌDàÄ! ìâ" àëàÄËÌ8p`‡ çqááÄË›ÄËfi
ÄËfiÁ√√√√√ƒ√√ƒƒ√√√√√√√√√
"@
À
 
åÀ

Ê8√ã
Tqa√«–
"DLÅ$âí$Hò–
‚"DHÅy‰Hê–
"DHÅâ$Oê–
"DHÅâ$H–
"DHÅâ$Hê–
Ò‚CàÅy„«–ˆ@œ˜
@œ˜
Äœ√√√√*
à@@

 ˝a Ä
‡¸ Ì'
à˛@
å˛ ˝  ˙Ï/+
H‚",8√«
Tp„8p‚¿,p‚Á<#qá
≈ò≥,a√é0‚¿Ô/+
I"2DDHÅ$ââ 2!ë"!" àô&dÃë2"$D Ô/+
)T"@DHÅy
â "!ë"! àë$Dàë""ƒ Ô/+
)ÒT"8DOÅâ
à‚ "!Úë"!" àë$Dàë""D Ô/+
à"DH
â
à "!ë"!" àë$Dàë""D Ô/+
à"DDHÅââ "!ë"!" àë$Dàì""$D Ô/+
‡à"8C«
x·p‚""‚û<!á
·ƒDàç"!√√‚ Ô¸
 ‹¸
 ‹√√ƒ√ƒ 
‡˛
˛ “ 
˛
˛ “PÒ·
≈òÒá"√Ä‘Pâ&dâò#$@‘àâ$Dâê"$”àâ$Dâê"$”
¸â$Dâ"$”
â$Dâ1ê"$@‘
Ò·
·ƒD–« "#Ñ‘Å˚IJ —Å˚IJ@—ˇF\@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-45
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh¢(eäFigurR¿°dONLNd\¢hª)e 2-16@°dONLNd\ªh
‰)B shows the subscriber options dialog box with the update mode set °dONLNdMiäuï(räto ∑‡°dONLNdPiïuø)ManuallyI¿°dONLNdXiøu¡)*
.

óH®4òH®"òH]

ˇ·ˇ‚7^
    °dONLNd[çäò∫(ïäFigure 2-16°dONLNdgçÃò
€)BBThe subscriber options dialog box with update mode set to Manually
°dONLNd´
2ä
>˘(
;äAs a shortcut for the userS@°dONLNd≈
2˘
>)o<, you should display the subscriber options dialog box when °dONLNd


?ä
KÊ(
Häthe user double-clickƒ°dONLNd

?Ê
KÒ)\s aÅ°dONLNd

?Ú
K
=) subscriber sectio0°dONLNd
+
?
>
K
I)Ln ii¿°dONLNd
.
?
I
K
à)n a document..°dONLNd
<
Qä
]ë(
Zä
Yï°dONLNd
=
Qê
]
)ou pass a section options rg`°dONLNd
X
Q

]
)reply r9¿°dONLNd
^
Q

]
/)ecor °dONLNd
b
Q
/
]
ö)d as a parameter to the ,
Courier °dONLNd
z
Q
ö
])kSectionOptionsDialog °dONLNd
é
Q
])x
 .
°dONLNd
è
^ä
j±(
gä    function..°dONLNd
ô
uä
Å
,*TYPE SectionOptionsReply = °dONLNd
∂
Éú
è¿+RECORD°dONLNd
ø
ëÆ
ù‰+    canceled:°dONLNd
Ã
ëˆ
ù
&)HBoolean;°dONLNd
⁄
ë
b
ù
å)l{user c°dONLNd
·
ë
å
ù
¬)*    licked Ca°dONLNd
Í
ë
¬
ù
‘)6nce°dONLNd
Ì
ë
‘
ù
‡)l}°dONLNd
Ú
üÆ
´fi(
®Æchanged:°dONLNd
˛
üˆ
´
&)HBoolean;°dONLNd
ü
b
´
Ú)l{changed section record}°dONLNd'
≠Æ
π‰(
∂Æ    sectionH:°dONLNd4
≠ˆ
π
P)HSectionHandle; °dONLNdI
≠
b
π
˛)l{handle to the specified }°dONLNdp
ª
b
«
»*{ section record}°dONLNdÑ
…Æ
’ÿ(
“Æaction:°dONLNdè
…ˆ
’
&)HResType;°dONLNdù
…
b
’
∂)l{action codes}°dONLNd≠
◊ú
„¥(
‡úEND;°dONLNd≤
Ôä
˚≠(
¯äSet the °dONLNd∫
Ô≠
˚›)#sectionH°dONLNd¬
Ô›
˚
ì)0) parameter to the handle to the section rR`°dONLNdÎ
Ô
ì
˚
•)∂ecor$¿°dONLNdÔ
Ô
•
˚
)d for the section the .
°dONLNd
¸äü(äuser `°dONLNd

¸†≈)    selected..°dONLNdä®(äUpon rR`°dONLNd®fi)eturn of the R`°dONLNd'fi
V)6SectionOptionsDialogR`°dONLNd;
V
ì)x function, the R`°dONLNdJ
ì
√)=canceledR`°dONLNdR
√
ÿ)0 and R`°dONLNdW
ÿ)changedR`°dONLNd^)*
 °dONLNd_ä'ë($ä
fi°dONLNdaë'∞)elds arR`°dONLNdh∞'Â)e set. If the R`°dONLNdvÂ'
)5canceleR`°dONLNd}
'
)*
dR`°dONLNd~
'
) fiR`°dONLNdÅ
'
3)    eld iR`°dONLNdÜ
3'
S)    s set to R`°dONLNdè
S'
k) TRUER`°dONLNdì
k'
ñ), the user R`°dONLNdû
ñ'
Δ)+
clicked CaR`°dONLNd®
Δ'
œ)0ncR`°dONLNd™
œ'
€)    el.R`°dONLNd≠
€') Otherwise, °dONLNdπ(ä4ô(1äthi°dONLNdº(ô4¶)s fi°dONLNd¿(¶4ª)eld i°dONLNd≈(ª4¡)s °dONLNd«(¡4€)set to °dONLNdŒ(€4˘)FALSE°dONLNd”(˘4
)    . If the °dONLNd‹(
4
>)!change°dONLNd‚(
>4
D)$
d°dONLNd„(
D4
M) fi°dONLNdÊ(
M4
b)    eld i°dONLNdÎ(
b4
h)s °dONLNdÌ(
h4
Ç)set to °dONLNdÙ(
Ç4
ö)TRUE°dONLNd¯(
ö4
÷), the section rR`°dONLNd(
÷4
Ë)<ecor$¿°dONLNd(
Ë4
˙)d is .
°dONLNd5äA
π(>ä@changed. For example, the user may have changed the update mode.

ßà
òÄ@
D
ÙHH



\*4

ˇˇˇˇˇˇ

D
Ù™á
}
À
ƒˇ

ƒ

ƒ


?≈ˇ
ê

?≈ˇ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê

0ÙˇÊ
ê

0ÙÊ
ê

0ÙÊ
ê

0ÙÊ
ê

0ÙÊ
ê'
08¿¿T
Δ¸
˛Ê
ê&
0d¿˛¿
™ ¸˝Ê
ê)
0`ïp„l¯xÿ<x¿˛«Δ<Êœ‡ˇÊ
ê(
0pÃÃ…ìåÃÇÿÜ˝fg˛ôê˛Ê
ê(
08Ã÷ÉÃÿÃ˛

Δ˝ff˛ôÄ
¸Ê
ê)
0ÃÃqÉø¿ÃÊ˛f~f˛ôįÊ
ê(
0ÃÃ9Éÿ¿Ã˛˝f`f˛ôÄpÊ
ê(
0LÃÃôìÿÿ
™˝fbf˛ôê Ê
ê)!
08|¯p„¯x¿x¿T
ΔfgΔ<Êüò‡Ê
ê

0Ù¸˛`¸Ê
ê

0Ù¸`¸Ê
ê

0Ù˘
¿˙Ê
ê

0ÙÊ
ê

0ÙÊ
ê

0Ùˇ¯Ê
ê

0Ùˇ¯Ê
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê
0»ˇ
ê    

0Δ
ê
0»ˇ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê

0¿Ãcœ
ê

0Ä¿`œ
ê
0ÃÛ>`”
ê
0åÃc332`”
ê
0ôååÃc338
ËUPÚˇ¸
ê
0 üåÃc33Á0Ú
ê
0òÃc33‰ Ú

ê
0 òåÃc33&`Ë@ÒÄ
ê
0«Ã33`Â@ÒÄ
ê 
0 ›@IJ00˛Ä
ê

0ÿ@@˛0˛0˛Ä
ê 
0 ›@èá3>8€>6Ä
ê

0ÿ@ÃÃôò332d„338Ä
ê 
0 ›@ÃÃò338`√330Ä
ê

0ÿ@ÃÃò33`√3?0Ä
ê 
0 ›@ÃÃ33`√300Ä
ê

0ÿ@LÃÃòò33&d√310Ä
ê$
0 ˛x·@áë>8√>0Ä
ê

0˝

Üfi@ÒÄ
ê!

0 
¿˝ΔÃÏ@ÒÄ
ê

0˝
`˝¿ÃÈ@ÒÄ
ê$
0 ÜfgèÒÊ8xÃÃÌ Ú

ê 

0˝ÜfcôôΔdåÃÃÍ0Ú
ê$
0 áÊcôò¯Δ`|ÃÃÌÚˇ¸
ê

0˝
ÜfcôôòΔ`˛Ãÿ
ê
0 
fcôôòΔ`˛ÃÌÌ
ê

0˝

fcôôòΔd˛Ãÿ
ê
0 
Üc·èò¯f8|Ã|ÌÌ
ê

0¸xˆÿ
ê
0 ÚåÌÌ
ê

0xÿ
ê
0 ›Ì
ê    

0Δ
ê
0 Ô?ÚˇÚˇ¸
ê

0Ì¿Ú˝0Ú
ê
0 ÔÄÚ Ú

ê

0¸xÙ
Ò˝@ÒÄ
ê
0 
ÜÙ
Ò@ÒÄ
ê:

0˝
˝f˚
x`>c@˛˝@¿˛|`f¿˝Ä
ê<    
0 y˝f˚
ƒ`0˛
@˛@`˛f``¿˝Ä
ê=

0˝    ¸á<|f<ff¸
¿x0>gòÒGåÃ˝@g√«¿ff|f8¯xÿÄ
ê>
0 ¸áûFffFff¸
¿Ã`0fcôòLÃÃ@˛f`˝f    dÃÇÄ
ê=

0˝    ¸Öˆ>ff>ff¸
‹Ã`<fcôòLÃÃ˝@˛f
`|˛f    pÃÿÄ
ê;    
0 ¸ÑÊ˚f¸
ø`0fcôò˛Ã@fgÊ``˛f    8ø¿Ä
ê9

0˝yF˚f¸
ÿ`0fcôò˛Ã
˝@ff``˛f    ÿ¿Ä
ê;    
0 
˚f¸
Ã`0fcôòÃû@ff&``˛f    LÿÄ
ê=

0˝    
Ü>f>>f>¸
xx0>>aòÒòGè˝@«√Δ``>|f8Ãx¿Ä
ê$
0 ˛x˙¸
Ò@ÙÄ
ê

0ÙF¸
Ò˝@ÙÄ
ê
0 ˆ<¸
Ò@ÒÄ
ê

0ÌÄÚ˝ Ú

ê
0 Ô¿Ú0Ú
ê

0Ì?Úˇ˝Úˇ¸
ê
0 ›Ì
ê    

0Δ
ê
0 ›Ì
ê    

0Δ
ê
0 ›Ì
ê    

0Δ
ê
0 ›Ì
ê    

0Δ
ê
0 ›Ì
ê

0ÿU@
ê.

0 @ í ˝ Ä

8áp||<Ç˝Ì
ê)    
0@ ÄǸ1Ä

D
à¢à"ΔË
ê/#
0 Aú«pÉ∑fpÄ*ô«2@
KåDà¢à(DD"™˝Ì
ê+
0@I( ‰í)H˛$•)
@
JR8áûàH8<íË
ê/
0 A…Ê Ñí)H˛ •):@J^DÄÇà|
 Ç˝Ì
ê+
0BI
 Ñí)H˛ •)J@JPDÅàD ÇË
ê/#
0 yƒŒÛë&HÄ ô'9¬:L8@ÜpDN8 Ç˝Ì
ê

0B¸@Á˚ˇ˛
ê
0 Û

ѸÄÛˆ˙ˇÄ
ê

0œ?˙ˇ¿
ê
0 ›ˆ|˚‡
ê

0ÿ˚ˇ¿q˚ˇ¯‡
ê:
0 @A‡˛ Ä

8áp||<Ç˝0˚0ˆ˚
ê7
0@A˛˛1Ä

D
à¢à"Δ˙ ˚‰˚p
ê:#
0 Aé·Õ@*ô«2@
KåDà¢à(DD"™˝@˚Ë˚
p
ê7
0@PA‰•$§§˛$•)
@
JR8áûàH8<í˙@˚Ë˚
p
ê?
0 AÃAG°‰ß§˛ •):@J^DÄÇà|
 Ç˝@˝`Ë1Ä
p
ê<
0BBA$%D$˛ •)J@JPDÅàD Ç˙
@1˝`Ë33
p
ê@#
0 y‹!ƒC@ ô'9¬:L8@ÜpDN8 Ç˝@0><`Ë36
p
ê#

0B¸@@0#32f`Ë3<
p
ê)
0 Û

ѸÄÛ@030f`Ë38
p
ê

0ÿ@0330~`Ë3<
p
ê 
0 ›@0330``Ë36
p
ê

0ÿ@1332b`Ë33
p
ê 
0 ›@3<`Ë1Ä
p
ê

0ÿ@˚Ë˚
p
ê
0 ›@˚Ë˚
p
ê

0ÿ@˚Ë˚
p
ê
0 › ˚‰˚p
ê

0ÿ0˚0ˆ˚
ê
0*›™®˚ˇ¿q˚ˇ¯‡
ê

0œ|˚‡
ê

0œ?˙ˇ¿
ê

0œ˙ˇÄ
ê

0œ˚ˇ˛
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê    

0Δ
ê

?≈ˇ
ê

?≈ˇ
ê
ƒ

ƒ

ƒˇ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡5˘
> ˛Ä
Ä»˛˛à˝
@˛"`IJ
!˛

˝˚8|@‡ ˝@˛˛˝˝  Ä˝!˛

˝˚>:@à
¡ a‰Kú@

ƒO]è.8√ã
Ê!√¿‚ DLq`"xx„á
f<p¸>$@Ñ
B "$L"@
Äë$Hë"`àë0ëDLë˛"$@â DD!ê"DâÅô"Dà¸>:@Ñ
C‡<"$H"á¡@ëHê @àë ëDHê""$@â@*Ñ!"DàÒÅ"Dà¸>$xѯÒB "$H>

@ü
ƒHé @àü ëDHé˛"$@âÄ*Ñ!"DâÅ"D¯¸>$@ÑB "$H 
@ê$HÅ @àê ëDHÅ˛"$@â@!"Dâ
"Dĸ>$@ÑB "$»"
@ë$»ë"@àë ëDHë˛"$@â !&DâÅ"Dà¸>:@à
B !„H¿
Äé
√O@è Càé
‚!√¿‚ xx«
<p¸|A‡˛ ̯@˘@Ù¯
 Ì˘
@˘@Ù¯

¿‰
ÄΡ¡¡¡Ì
˛
`flÌ
å˛
 flÔá
Tqb#Ñ" ‡ÔHà
$âí$D" ‡Ôà
y#ƒ" ‡Ôèà
â$D" ‡ÓH
â$D" ‡ÔHà
âdD" ‡Ôá
é
y£ƒ!‡‡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡√
ˇ¡¡√
ˇ√
ˇ¡
¯ Ç»
Ä˛Δ»ÄÛa≈Ä™8∞·„ãÄŒÅ"&@íD…$LÕÒ"$@Ç<àÚ$HÕÅ"$@ÇDâ'»ÕÅ"$@ÇDâ$ÕÅ"$@ÇDâ$HÕ¯Ò!ƒ@Ç<àÒ„àÕ˜ ï
 ï

¿Ã¡¡¡¡)ƒ
  ÇÄ

˝0Ä@¸Í&ƒ
˛ Δ˛

˝
˙È.*§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`Ï.*§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âêÏ.*îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚âÏ.*
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"âÏ.*åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"âÏ.
åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"âÏ.*ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àqÏÒ
¸
ŸÒ¸
Ÿ¡¡¡¡¡
Ä˝ÄœÄ
˝Äœ(xá
‚Ãxâ√ãÄa¿—(DààÅ
2DàÑLí —DDààÅ
"DàÑH–DDàèÅ
"Dàồ
ˇ˛Dàà

"DàÑ–ÇDààÅ    "DòÑH ”
ˇÇxá‚"xhcà¿—@ĸ@˛
—@ĸ@˛ Œˇ∫@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-46    )BUsing the Edition Manager4^*¿
¯
.°dONLNd\lhÄ(elThe ,
Courier°dONLNd\Äh¯)SectionOptionsDialog°dONLNd\¯h
$)x function rR`°dONLNd#\
$h
^),eturns in the R`°dONLNd1\
^h
Ç):actionR`°dONLNd7\
Çh
Ì)$ parameter the code for .
°dONLNdOiluè(rlone of fif†°dONLNdXiêu
‚)$Mve user actions. The function dismisses the publisher and subscriber options °dONLNd•vlÇ
%(l,dialog boxes after the user clicks a button.,Zapf Dingbats°dONLNd“ålìq*
n
.°dONLNd‘âxï∏)Action code is °dONLNd„â∏ï‹)@'read'°dONLNdÈâ‹ï
ó)$+ for a click of the Get Edition Now button..
°dONLNd
ûl•q(§l
n
.°dONLNd
õxß∏)Action code is °dONLNd
&õ∏ß‹)@'writ'°dONLNd
,õ‹ß
ù)$, for a click of the Send Edition Now button..
°dONLNd
Y∞l∑q(∂l
n
.°dONLNd
[≠xπ∏)Action code is °dONLNd
j≠∏π‹)@'goto'°dONLNd
p≠‹π
ë)$* for a click of the Open Publisher button..
°dONLNd
õ¬l…q(»l
n
.°dONLNd
ùøxÀ∏)Action code is °dONLNd
¨ø∏À‹)@'cncl'°dONLNd
≤ø‹À
Ù)$A for a click of the Cancel Publisher or Cancel Subscriber button..
°dONLNd
Ù‘l€q(⁄l
n
.°dONLNd
ˆ—x›∏)Action code is °dONLNd—∏›ƒ)@' °dONLNd—ƒ› )
 °dONLNd— ›–)
 °dONLNd    —–›÷)
 °dONLNd
—÷›‹)
'°dONLNd—‹›
ï)+ ($20202020) for a click of the OK button. .
°dONLNd7‚lÓö(ÎlListing 2-8 @°dONLNdB‚õÓ
t)// shows an example of how your application can r'°dONLNdq‚
tÓ
Î)Ÿespond to the action codes °dONLNdåÔl˚o(¯l
rE°dONLNdçÔp˚õ)
eceived frU`°dONLNdóÔõ˚
)+om the section options rP°dONLNdØÔ
˚
)jeply rÿ@°dONLNdµÔ
˚
0)ecorL†°dONLNdπÔ
1˚
7)
dh`°dONLNd∫Ô
7˚
<). :¿°dONLNdºÔ
<˚
B)
Y˚@°dONLNdΩÔ
A˚
v)ou can use sÑ@°dONLNd…Ô
w˚
†)6
everal difC °dONLNd”Ô
°˚
≠)*fer%†°dONLNd÷Ô
≠˚
Ë)ent techniqueÙ@°dONLNd„Ô
Ë˚
Ó);s °dONLNd¸l
∫(
lfor this purpose; t1†°dONLNd¯¸ª

G)O his listing shows one technique.


+*
3
¯4
,*
3
¯"
,*_

ˇ·ˇ‚7^
    °dONLNd
!l
,ò(
)lListing 2-8°dONLNd&
!∞
,
)DResponding to action codes
.°dONLNdB
;l
G
§(
Dl4PROCEDURE DoOptionsDialog(theSection: SectionHandle)°dONLNdv
;
§
G
™(
D
§
;°dONLNdx
Il
Ur(
Rl
V°dONLNdy
Ir
U~)AR°dONLNd}
W~
c¢+reply:°dONLNdâ
WÍ
c
8)lSectionOption°dONLNdñ
W
8
c
>)N
s°dONLNdó
W
>
c
b)Reply;°dONLNdü
e~
qÿ(
n~theEditionInfo:°dONLNd¥
eÍ
q
V)lEditionInfoRecord;°dONLNd»
s~
®(
|~action:°dONLNd’
sÍ

)lResType;°dONLNdfl
Å~
ç¢(
ä~sodErr°dONLNdÂ
Å¢
ç“)$, geiErr°dONLNdÌ
Å“
çÿ)0
:°dONLNdÙ
ÅÍ
ç
)OSErr°dONLNd˘
Å

ç
)
;°dONLNd¸
è~
õÿ(
ò~gpiErr, gpsErr:°dONLNd
èÍ
õ
)lOSErr°dONLNd
è

õ
)
;°dONLNd
´l
∑r(
¥l
B°dONLNd
´r
∑ä)EGIN°dONLNd 
π~
≈
&+reply.sectionH := theSection°dONLNd<
π
&
≈
,)®
;°dONLNd?
«~
”
&(
–~{display options dialog box}°dONLNd]
’~
·
\*%sodErr := SectionOptionsDialog(reply)°dONLNdÇ
’
\
·
b)fi
;°dONLNdÖ
„~
Ôê(
Ï~{de°dONLNdà
„ê
Ô
∂)1termine what the user did and handle appropriatel°dONLNdπ
„
∂
Ô
¬(
Ï
∂y}°dONLNdΩ
Ò~
˝¸(
˙~IF reply.canceled THE°dONLNd“
Ò¸
˝
)~
N°dONLNd€
Ò

˝
&){use°dONLNdfl
Ò
&
˝
n)r selected t°dONLNdÎ
Ò
n
˝
‘)Hhe Cancel button}°dONLNdˇ
ˇêñ(ê
E°dONLNd
ˇñ
)XIT(DoOptionsDialog)°dONLNd
ˇ

)x
;°dONLNd~Ñ(~
I°dONLNdѸ)F reply.changed THEN°dONLNd/ê'¢+{th°dONLNd2¢'
∂).e section record has changed; make note of thi°dONLNd`
∂'
¬($
∂s}°dONLNde)ê5ú(2êMy°dONLNdg)ú5
P)SectionHasChanged(theSection);°dONLNdà7êC¢(@ê{if°dONLNdã7¢C) you customiz°dONLNdò7C¸)Ne,°dONLNdö7¸C
ò) you may want to do some }°dONLNd∑EêQ
(Nê{ post-processing no°dONLNdÀE
Q
)xw}°dONLNdœS~_¸(\~{get the action code}°dONLNdÊa~mÑ*
a°dONLNdÁaÑm
)ction := reply.action°dONLNd¸a
m
)~
;°dONLNdˇo~{Ñ(x~
I°dONLNdoÑ{
)F (action = 'read') THEN°dONLNd}~âú(Ü~BEGIN°dONLNd"}¥âΔ)6{us°dONLNd%}Δâ
å)!er selected Get Edition Now butto°dONLNdF}
åâ
ò)Δn}°dONLNdKãêó
&(îêDoReadEdition(theSection)°dONLNddã
&ó
,)ñ
;°dONLNdhôê•ñ(¢ê
E°dONLNdiôñ•
)XIT(DoOptionsDialog);°dONLNdÄß~≥ê(∞~END°dONLNdÉßê≥ñ)
;ˇ3™@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-47
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\úh¢(eú
I°dONLNd
\¢h
2)F (action = 'writ') THEN°dONLNdjúv∫(súBEGIN°dONLNd#j“v‰)6{us°dONLNd&j‰v
∞)"er selected Send Edition Now butto°dONLNdHj
∞v
º)Ãn}°dONLNdMxÆÑ
P(ÅÆDoWriteEdition(theSection);°dONLNdkÜÆí
2*EXIT(DoOptionsDialog);°dONLNdÉîú†Æ(ùúEND°dONLNdÜîƆ¥)
;°dONLNdâ¢úÆ¢(´ú
I°dONLNd䢢Æ
2)F (action = 'goto') THEN°dONLNd§∞úº¥(πúBEGI°dONLNd®∞¥º∫)
N°dONLNd¨∞“º‰){us°dONLNdØ∞‰º
§) er selected Open Publisher butto°dONLNdœ∞
§º
∞)¿n}°dONLNd‘æÆ 
Ê(«Æ4geiErr := GetEditionInfo(theSection, theEditionInfo)°dONLNd
æ
Ê 
Ï(«
Ê
;°dONLNd
ÃÆÿ¥(’Æ
I°dONLNd
Ã¥ÿ
8)F geiErr <> noErr THEN°dONLNd
#Ã
8ÿ
>)Ñ
 °dONLNd
(⁄¿ÊΔ(„¿
M°dONLNd
)⁄ΔÊ
>)yErrHandler(geiErr);°dONLNd
>⁄
>Ê
»)x{handle error and exit}°dONLNd
XËÆÙ¥(ÒÆ
g°dONLNd
YË¥Ù
˛)7psErr := GotoPublisherSection(theEditionInfo.container)°dONLNd
êË
˛Ù(Ò
˛
;°dONLNd
îˆÆ
¥(ˇÆ
I°dONLNd


)F gpsErr <> noErr°dONLNd
¶ˆ


8)f THEN°dONLNd
Ø
¿
Δ(
¿
M°dONLNd
∞
Δ

>)yErrHandler(gpsErr);°dONLNd
≈

>

»)x{handle error and exit}°dONLNd
fl
Æ

2(
ÆEXIT(DoOptionsDialog);°dONLNd
˜
 ú
,Æ(
)úEND°dONLNd
˙
 Æ
,¥)
;°dONLNd
˝
.ú
:¢(
7ú
I°dONLNd
˛
.¢
:
2)F (action = 'cncl') THEN°dONLNd
<ú
H∫(
EúBEGIN°dONLNd
<∫
H¿)
 °dONLNd
<¿
H“){Us°dONLNd"
<“
H
∞)%er selected Cancel Publisher or Cance°dONLNdG
<
∞
H)fil Subscriber }°dONLNdX
JÆ
V¿(
SÆ{ b°dONLNd[
J¿
V‰)utton.°dONLNda
J‰
VÍ)$
 °dONLNdb
JÍ
V
å)Call the UnRegisterSection °dONLNd}
J
å
V)¢function and dispose }°dONLNdñ
XÆ
d¿(
aÆ{ o°dONLNdô
X¿
d
V)f the section record and °dONLNd≤
X
V
d
™)ñalias record.}°dONLNd√
fÆ
r¥(
oÆ
E°dONLNdƒ
f¥
r
2)XIT(DoOptionsDialog);°dONLNd€
tú
Ä¥(
}úEND;°dONLNd‡
Çä
éú(
ãäEND°dONLNd„
Çú
é¢)
;.
°dONLNdÂ
öä
¶
B(
£ä*The following sections describe the featurY°dONLNd
ö
B
¶
˝)∏+es of the publisher and subscriber options °dONLNd:
ßä
≥ƒ(
∞ädialog boxes.


—H
ÿ4
“H
ÿ 
ӊ
”

ˇ·ˇ‚7^°dONLNdI
Ċ
“
ô*1Publishing a New Edition While Saving or Manuallyˇˇˇˇˇˇ‘@(
Œ
2
°dONLNd|
ÿä
‰(
·äZBy default, your application should write publisher data to an edition each time the user °dONLNd÷
Âä
Ò
Ñ*8saves the document and the contents of the publisher dif]°dONLNd
Â
Ñ
Ò
ô)˙fer fr°dONLNd
Â
ö
Ò)om the latest edition. In the °dONLNd2
Úä
˛(
˚äWpublisher options dialog box, the user can choose to write new data to an edition each °dONLNdâ
ˇä
Ä*7time the document is saved (by clicking On Save) or onl    ¿°dONLNd¿
ˇ
Å
¶)˜y upon t+`°dONLNd»
ˇ
¶
Δ)%he user °dONLNdœ
ˇ
«
Œ)!’s`°dONLNd—
ˇ
Œ
Ï) specifiˆÄ°dONLNdŸ
ˇ
Ï
Ú)c °dONLNd€äç(ä
rE°dONLNd‹éß)equesµÄ°dONLNd·ß∞)t (À¿°dONLNd‰∞
)    by clicking Manually).°dONLNd˚ä*('äSWhen the update mode is set to manual, a user must click the Send Edition Now butto    ¿°dONLNdN*('n °dONLNdP+ä7å(4ä
ih`°dONLNdQ+ç7)Vn the publisher options dialog box to write publisher data to an edition. When a user .°dONLNdß8äD†(Aäclick°dONLNd¨8†D⁄)s this button,°dONLNd∫8⁄D
6): the section options rR`°dONLNd–8
6D
Q)\eply r$¿°dONLNd÷8
QD
c)ecor˜ °dONLNd⁄8
bD
◊)d contains the action code ˜ °dONLNdı8
◊D
˚)u'writ'˜ °dONLNd˚8
˚D)$. In .
°dONLNdEäQı(Näthis case, you should wrîÄ°dONLNdEıQ
R)kite out the new editioÖ@°dONLNd.E
SQ
[)^n.÷†°dONLNd0E
[Q
g) Wô@°dONLNd2E
gQ)(riting to an edition manually is useful °dONLNdZRä^
R([ä*when a user tends to save a document numer”¿°dONLNdÑR
R^
ù)»ous times while röÄ°dONLNdïR
û^
…)Levising it.°dONLNd°däp(mäWEach time the user saves the document, check the update mode of the publisher section. °dONLNd¯qä}ç*
IfiÄ°dONLNd˘qç}£)f the ¿°dONLNdˇq§}
b)-publisher section sends its data to an editioí`°dONLNd,q
b}
Î)æn when the document is saved,¨Ä°dONLNdIq
Î})â chec®°dONLNdNq
}    )k °dONLNdP~ääí(áä
w◊°dONLNdQ~íä
ü)>hether the publisher data has changed since it was last writte °dONLNdè~
†ä
´(á
†n t™‡°dONLNdí~
´ä
ˇ)o the edition. If so, °dONLNd®ãäóú(îäwritÙ`°dONLNd¨ãúó›)e the publisherÖ°dONLNdªãfló
)C’s data to ta†°dONLNd«ã
ó
Q).he new edition.ˇ¶@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-48    )BUsing the Edition Manager4^*¿
¯
°dONLNd\lh
#(el)In addition, you may also support a Stop Y`°dONLNd)\
#h
∫)∑All Editions menu command to pr؇°dONLNdH\
∫h
‹)óovide a °dONLNdPilu
](rl5method for temporarily suspending all update activity`°dONLNdÖi
\u
k). Seà¿°dONLNdâi
ku
r)e “`°dONLNdãi
ru
á)“Intr    †°dONLNdêi
àu
)oduction to Publishers, °dONLNd®vlÇ
8(l-Subscribers, and Editions” beginning on page È`°dONLNd’v
8Ç
E)Ã2-4=@°dONLNdÿv
FÇ
K) f °dONLNd⁄v
LÇ
ø)or additional information.

†*ß
¯4°*ß
¯ ¢l¢
¯

ˇ·ˇ‚7^°dONLNdˆìl°Ù(ùlSubscribing to an Edition ‡¿°dONLNd
ìÛ°
{)áAutomatically or Manuallyˇˇˇˇˇˇ‘@)˛
2
°dONLNd
+ßl≥
Î(∞lWBy default, your application should subscribe to an edition each time new edition data °dONLNd
Ç¥l¿
Ã*Qbecomes available. In the subscriber options dialog box, the user can choose to rt°dONLNd
Ӵ
ÿ
Û(Ω
Ãead new °dONLNd
€¡lÕâ( ldata frw°dONLNd
‚¡âÕ
d)4om an edition as the data is available (by clicking µ@°dONLNd¡
dÕ
ı)€ Automatically) or only upon the °dONLNd6Œl⁄(◊luser=¿°dONLNd:ŒÄ⁄•)    ’s specifi0 °dONLNdDŒ¶⁄∞)&c rÂ`°dONLNdGŒ∞⁄
5)
equest (by clicking Manually).°dONLNdf‡lÏ
Ï(ÈlTWhen the update mode is set to manual, the user must click the Get Edition Now buttoù¿°dONLNd∫‡
ÏÏ
Ù(È
Ïn °dONLNdºÌl˘n(ˆl
ih`°dONLNdΩÌo˘
)(n the subscriber options dialog box to rÈ°dONLNdÂÌ
˘
fi)¨-eceive new editions. When a user clicks this .°dONLNd˙l
Á(
lbutton, the section options rR`°dONLNd/˙Á

){eply r$¿°dONLNd5˙


)ecor˜ °dONLNd9˙


à)d contains the action code ,
Courier˜ °dONLNdT˙
à

¨)u'read'˜ °dONLNdZ˙
¨

È)$. In this case, .
°dONLNdj
l
§(
lyou should rfl‡°dONLNdv
§
®)8
e©Ä°dONLNdw
©


)ad in the new editioº`°dONLNdã




    )Xn.¿°dONLNdç




)     Seó °dONLNdê



)e ‡¿°dONLNdí



Î),“Opening an Edition Container to Read Data” °dONLNdæ
l
 ¿(
lbeginning on page V °dONLNd–
¡
 ”)U2-41™°dONLNd‘
”
 ÿ) f}‡°dONLNd÷
Ÿ
 
B)or detailed information.°dONLNdÔ
&l
2
{(
/l<When the update mode is set to automatic, your application rx °dONLNd+
&
{
2
‡(
/
{eceives a Section Read °dONLNdB
3l
?
W(
<l5event each time a new edition becomes available. In râ`°dONLNdw
3
W
?
∑)Îesponse, you should r?Ä°dONLNdå
3
∏
?
)aead the new .°dONLNdò
@l
Lˇ(
Il edition data beginning with the °dONLNd∏
@ˇ
L
)ìOpe°dONLNdª
@

L
)nE°dONLNdΩ
@

L
A)dition°dONLNd√
@
A
L
j)$
 function..
°dONLNdŒ
Rl
^r(
[l
Y@Ä°dONLNdœ
Rr
^‰)our application does not rL¿°dONLNdÈ
R‰
^
∑)r1eceive Section Read events for subscribers that r›`°dONLNd
R
∑
^
Í)”eceive new °dONLNd%
_l
kº(
hleditions manuallym°dONLNd6
_ª
kΩ)O
.°dONLNd8
ql
}r(
zl
Y@Ä°dONLNd9
qr
}Ì)ou may also support a Stop I`°dONLNdT
qÌ
}
Ñ){All Editions menu command to prü‡°dONLNds
q
Ñ
}
⁄)óovide a method for °dONLNdÜ
~l
ä
)(
ál*temporarily suspending all update activityÄ¿°dONLNd∞
~
(
ä
7)º. Seä °dONLNd¥
~
7
ä
>)e ”¿°dONLNd∂
~
>
ä
S)“Intr°dONLNdª
~
T
ä
Ù)%oduction to Publishers, Subscribers, °dONLNd‡
ãl
ó
(
îl and Editions” beginning on page ¿°dONLNd
ã


ó
)ï2-4e†°dONLNd
ã

ó
) f9Ä°dONLNd
ã

ó
Ñ)or additional information÷‡°dONLNd
ã
Ñ
ó
Ü)p
.


µ*
º
¯4
∂*
º
¯ 
∑l
∑
¯

ˇ·ˇ‚7^°dONLNd!
®l
∂·(
≤lCanceling Sections W⁄°dONLNd5
®·
∂
7)uithin Documentsˇˇˇˇˇˇ‘@(
≤
Ò
2
°dONLNdF
ºl
»
¿(
≈lOThe option of canceling publishers and subscribers is available to the user thr
¿°dONLNdï
º
¡
»
Í(
≈
¡    ough the °dONLNdû
…l
’
o(
“l:Cancel Publisher and Cancel Subscriber buttons in the corr†°dONLNdÿ
…
p
’
„(
“
pesponding options dialog °dONLNdÒ
÷l
‚Δ(
fllboxes. When the use‡°dONLNd
÷«
‚
C)[r clicks one of these buttons,… °dONLNd"
÷
C
‚
Î)|( the action code of the section options .°dONLNdJ
„l
Ôp(
Ïl
rR`°dONLNdK
„p
Ôã)eply r$¿°dONLNdQ
„ã
Ôù)ecor˜ °dONLNdU
„ú
Ô®)d i˜ °dONLNdX
„®
Ô¨)
s˜ °dONLNdY
„¨
ÔÆ)
 ˜ °dONLNdZ
„Æ
Ô¥)
'˜ °dONLNd[
„¥
Ô“)cncl'˜ °dONLNd`
„“
Ô‚). Se˜ °dONLNdd
„‚
ÔÈ)e ˜ °dONLNdf
„È
Ô
{) “Relocating an Edition” on page ˜ °dONLNdÜ
„
{
Ô
é)í2-60˜ °dONLNdä
„
é
Ô
î) f˜ °dONLNdå
„
î
Ô
”)or additional .
°dONLNdö
l
¸
(
˘l#information on canceling a section.°dONLNdæl
ÿ*TWhen a user cancels a section (either a publisher or subscriber) and then saves the °dONLNdl
œ*Mdocument, or when a user closes an untitled document (which contains newly crÀ†°dONLNd_
œ
È(
œeated °dONLNdel(◊(%lsections) without saving7†°dONLNd}ÿ(‡)l it‚`°dONLNdć(
!), you must unrÊ °dONLNdé
!(
i)Aegister each corrÄ°dONLNdü
j(
¿)Iesponding section rm@°dONLNd≤
¿(
“)Vecor·†°dONLNd∂
“(
Ó)d and .°dONLNdº)l5ä(2lalias rR`°dONLNd√)ä5ú)ecor$¿°dONLNd«)ú5œ)d using the $¿°dONLNd”)œ5
5)3UnRegisterSection$¿°dONLNd‰)
55
‡)f( function. In addition, you should also °dONLNd    6lB¬(?ldelete the section rR`°dONLNd     6¬B‘)Vecor$¿°dONLNd    $6‘B
)d and alias r˜ °dONLNd    16
B
)8ecor…Ä°dONLNd    56
B
Q)d using the …Ä°dONLNd    A6
QB
u)3Dispos…Ä°dONLNd    G6
uB
{)$
e…Ä°dONLNd    H6
{B
ü)Handle…Ä°dONLNd    N6
üB
´)$ prõ‡°dONLNd    Q6
´B
»)ocedurn@°dONLNd    W6
»B
›)e. Sen@°dONLNd    \6
›B
‰)e .
°dONLNd    ^ClOŸ(LlInside Macintosh: Memory.—°dONLNd    vCŸOfl)m f—°dONLNd    xCflO
t)!or additional information on the —°dONLNd    ôC
tO
ò)ïDispos—°dONLNd    üC
òO
û)$
e—°dONLNd    †C
ûO
¬)Handle—°dONLNd    ¶C
¬O
Œ)$ pr£`°dONLNd    ©C
ŒO
Î)oceduru¿°dONLNd    ØC
ÎO
Û)e..
°dONLNd    ≤Ula
Á(^lTWhen a user cancels a publisher section and then saves the document, or when a user °dONLNd
bln
Y*4closes an untitled document (which contains newly cr¿°dONLNd
:b
Yn
Í)Ì eated publishers) without savingRÄ°dONLNd
Zb
În
Ì)í
 °dONLNd
[ol{r(xlit™¿°dONLNd
]or{˘), you must also delete any corrÕ °dONLNd
|o˘{
‰)á6esponding edition containers (in addition to deleting °dONLNd
≤|làë(Öl    section r≠Ä°dONLNd
ª|ëà£)%ecor!‡°dONLNd
ø|§àfi)ds and alias r∫Ä°dONLNd
Õ|fià):ecor.‡°dONLNd
—|Òà

)ds).ˇ4h@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-49
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh
((eä$Do not delete an edition container fil`°dONLNd%\
)h
[)üle, section rK‡°dONLNd2\
[h
m)2ecor¿@°dONLNd6\
mh
û)d, or alias r‡°dONLNdC\
üh
±)2ecorã@°dONLNdG\
±h)d until the user saves °dONLNd^iäu
â(rä7the document; the user may decide to undo changes befor%†°dONLNdïi
äu
(r
äe saving the document.°dONLNd¨{äáê(Ñä
Tµ¿°dONLNd≠{èáÿ)o locate the appr,°dONLNdæ{Ÿá
û)J.opriate edition container to be deleted (befor5@°dONLNdÏ{
ûá
⁄)≈e you use the ,
Courier.°dONLNd˙àäî(ëäUnRegisterSection°dONLNd
àî
A)f function), use the °dONLNd
à
Aî
ï)QGetEditionInfo°dONLNd
-à
ïî
æ)T
 function.°dONLNd
8üä´
(®äerr := GetEditionInf°dONLNd
Lü
´
)xo(°dONLNd
Nü
´
ò)sectionH, editionInfo);°dONLNd
f∑ä√û(¿äThe °dONLNd
j∑û√‡)editionInfo°dONLNd
u∑‡√
*)B parameter is a rR`°dONLNd
Ü∑
*√
<)Jecor$¿°dONLNd
ä∑
<√
~)d of data type $¿°dONLNd
ô∑
~√
‰)BEditionInfoRecord$¿°dONLNd
™∑
‰√
Á)f
.°dONLNd
¨Œä⁄
 (◊äTYPE EditionInfoRecord = °dONLNd
«‹úË¿+RECORD°dONLNd
–Íƈÿ+crDate:°dONLNd
€Íˆˆ
2)H
TimeStamp;°dONLNd
ÏÍ
tˆ
)~{date edition container }°dONLNd¯
t

»*{ was created}°dONLNd$
Æ
ÿ(
ÆmdDate:°dONLNd/
ˆ

2)H
TimeStamp;°dONLNd@

t

Ú)~{date of last change}°dONLNdX
Æ
 Í(
Æ
fdCreator:°dONLNdf
ˆ
 
 )HOSType;°dONLNdt

t
 
»)~{file creator}°dONLNdÖ
"Æ
.ÿ(
+ÆfdType:°dONLNdê
"ˆ
.
 )HOSType;°dONLNdû
"
t
.
∂)~{file type}°dONLNd¨
0Æ
<Í(
9Æ
container:°dONLNd∫
0ˆ
<
t)HEditionContainerSpec;°dONLNd÷
0
t
<
¬)~{the edition}°dONLNdÂ
>ú
J¥(
GúEND;°dONLNdÍ
Vä
bû(
_äThe °dONLNdÓ
Vû
bÚ)GetEditionInfo°dONLNd¸
VÚ
b
)T function rR`°dONLNd
V

b
˛),4eturns the edition container as part of the edition .
°dONLNd;
cä
o¡(
läinformation.ˇˇGN.°dONLNdH
uä
Åù*The ˇ˝’Í«N°dONLNdL
uù
Å¡)crDateˇˇGN«N°dONLNdR
u¡
Å…)$ fiú°dONLNdU
u 
Å
)    eld contains the cr∂Ê°dONLNdh
u

Å
°)O eation date of the edition. The ˇ˝’Íb∫°dONLNdà
u
¢
Å
Δ)âmdDateˇˇGNb∫°dONLNdé
u
Δ
Å
Œ)$ fi™°dONLNdë
u
Œ
Å)eld contains the .
°dONLNd¢
Çä
éß(
ãämodifi⁄`°dONLNd®
Çß
é
)cation date of the edition..°dONLNdƒ
îä
†û(
ùäThe °dONLNd»
îû
†¬)fdType°dONLNdŒ
î¬
†È)$     and the °dONLNd◊
îÈ
†
)'    fdCreator°dONLNd‡
î

†
()6 fi°dONLNd„
î
(
†
G)    elds arR`°dONLNdÍ
î
G
†
í)e the type and cr$¿°dONLNd˚
î
í
†
Û)Keator of the edition fi$¿°dONLNd
î
Û
†)ale. The ˇˇiL°dONLNd
°ä
≠¿(
™ä    containerˇˇÕƒ°dONLNd#
°¿
≠≈)6 fD°dONLNd%
°Δ
≠
0)ield includes a volume r'¥°dONLNd=
°
0
≠
B)jefer˙°dONLNdA
°
A
≠
u)ence number
x°dONLNdL
°
v
≠
à)5, dir™ú°dONLNdQ
°
à
≠
∫)ectory ID, f§°dONLNd]
°
ª
≠)3ilename, script, and .
°dONLNdr
Æä
∫
(
∑äpart number for the edition..°dONLNdè
¿ä
Ãê*
Tï°dONLNdê
¿è
Ãö)o rg`°dONLNdì
¿ö
Ã
)emove the edition container™°dONLNdÆ
¿

Ã
>)}
, use the ™°dONLNd∏
¿
>
Ã
⁄)'DeleteEditionContainerFile™°dONLNd“
¿
⁄
Ã)ú
 function.°dONLNd›
׊
„
J(
‡ä err := DeleteEditionContainerFil°dONLNd˝
◊
J
„
V)¿e(°dONLNdˇ
◊
V
„
§)editionFile);

H    4H     ä

ˇ·ˇ‚7^.
°dONLNd
ıä˙(
ˇäLocating a Publisher Q@°dONLNd#
ı˙
m)pThrough a Subscriberˇˇˇˇˇˇ‘@(
ˇ
2
°dONLNd9    ä
(ä"The user can locate a publisher frù°dONLNd[    

˝)í2om a subscriber within a document by clicking the °dONLNdçä"
î(ä<Open Publisher button in the subscriber options dialog box. dONLNd…
î"
”(
îAs a shortcut, ≠`°dONLNdÿ
”"
)?Apple °dONLNdfi#ä/
Ñ(,ä:suggests that you also allow the user to locate a publishe´¿°dONLNd#
Ñ/
ú)˙r by sÚ °dONLNd#
ú/
¨)elecfi°dONLNd"#
≠/
Δ)ting aÈ@°dONLNd(#
Δ/
Ú)
 subscribeÄ°dONLNd2#
Û/
¸)-r iiÄ°dONLNd5#
¸/)    n a °dONLNd90ä<÷(9ädocument and prÓ@°dONLNdH0÷<fl)LesÙ‡°dONLNdJ0fl<˚)    sing O÷†°dONLNdP0¸<
Q)ption–double-click..°dONLNddBäN
(KäWhen the action code of the °dONLNdÄB
N
})ÅSectionOptionsReply°dONLNdìB
}N
É)r rR`°dONLNdïB
ÉN
ï)ecor$¿°dONLNdôB
ïN
ß)d is $¿°dONLNdûB
ßN
À)'goto'$¿°dONLNd§B
ÀN
Ú)$
, use the °dONLNdÆOä[
(XäGoToPublisherSection°dONLNd¬O
[
+)x
 function.°dONLNdÕfär
&(oäerr := GoToPublisherSectio°dONLNdÁf
&r
2)ún(°dONLNdÈf
2r
n)
container)°dONLNdÛf
nr
t)<
;ˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-50    )BUsing the Edition Manager4^*¿
¯
.°dONLNd\lhÄ(elThe ,
Courier°dONLNd\Äh¯)GoToPublisherSection°dONLNd\¯h
e)x function locates the corrR`°dONLNd2\
eh
±)mect document by r$¿°dONLNdC\
±h
Î)Lesolving the .
°dONLNdPilu
Ã(rlSalias in the edition, and it launches the document’s application if necessary (the °dONLNd£vlÇè*Edition ëÄ°dONLNd´vèÇ
Â)#GManager sends an Open Documents event). The Edition Manager then sends °dONLNdÚÉlè|(ålthe ›`°dONLNdˆÉ|è
)$publishing application a Section Scr≠`°dONLNd
É
è
œ)û*oll event. If the document containing the °dONLNd
Dêlúo(ôl
rE°dONLNd
Eêpú
ù)Dequested publisher is located on the same computer as its subscriberdÄ°dONLNd
âê
ùú
·(ô
ù, the document °dONLNd
òùl©®(¶lopens and scr/°dONLNd
•ù©©
B)=%olls to the location of the publisherú‡°dONLNd
 ù
A©
–)ò!. If the document containing the °dONLNd
Ιl∂o(≥l
rE°dONLNd
Ï™p∂
)'equested publisher is located on a shar?°dONLNd™
∂
p)´ed volume (using fi:‡°dONLNd&™
q∂
‰)Vle sharing), the document °dONLNd@∑l√®(¿lopens and scr/°dONLNdM∑©√
Ì)=Nolls to the location of the publisher only if the user has privileges to open °dONLNdõƒl–≤(Õlthe document fr0@°dONLNd™ƒ≥–Ò)Gom the Finder∫†°dONLNd∑ƒ–Ú)=
..°dONLNdπ÷l‚s(fll
Yï°dONLNd∫÷r‚™)ou need to prg`°dONLNd«÷™‚ÿ)8
ovide the g`°dONLNd—÷ÿ‚
P).GoToPublisherSectiong`°dONLNdÂ÷
P‚
)x$ function with the edition container™°dONLNd    ÷
Ô‚
Ù)ü. °dONLNd„lÔr(Ïl
Tï°dONLNd„qÔË)o accomplish this, use the ï°dONLNd'„ËÔ
<)wGetEditionInfoï°dONLNd5„
<Ô
ï)T function. See the prg`°dONLNdJ„
ïÔ
ÿ)Yevious section, °dONLNdZl¸“(˘l“Canceling Sections WÛ`°dONLNdo—¸
#)eithin Documents,”Û`°dONLNdÄ
#¸
ä)R for information on the Û`°dONLNdò
ä¸
fi)gGetEditionInfoÛ`°dONLNd¶
fi¸
‡)T
 .
°dONLNdß˝l
    ì(
l    function.


.*
5
¯4
/*
5
¯ 
0l
0
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd≤
l
.
v*$'Renaming a Document Containing Sectionsˇˇˇˇˇˇ€r(
*

2
°dONLNd€
5l
Añ(
>lIf a user rw¿°dONLNdÊ
5ñ
A
†)*:enames a document that contains sections by choosing Save ≠¿°dONLNd 
5
†
A
µ(
>
†As frJ‡°dONLNd%
5
∂
A
È)om the File °dONLNd1
Bl
N
„(
KlWmenu, or if a user pastes a portion of a document that contains a section into another .°dONLNdà
Ol
[Ω*document, use the °dONLNdö
OΩ
[
)QAssociateSection°dONLNd™
O

[
F)`
 function.°dONLNdµ
al
më(
jlUse the °dONLNdΩ
aë
mÒ)%AssociateSection°dONLNdÕ
aÒ
m
v)` function to update the alias rR`°dONLNdÏ
a
v
m
à)Öecor$¿°dONLNd
a
à
m
ß)d of a r˜ °dONLNd¯
a
¶
m
≈)egister…Ä°dONLNdˇ
a
≈
m
Ù)ed section.°dONLNd
xl
Ñ
∂(
Ål7err := AssociateSection (sectionH, newSectionDocument);°dONLNdC
êl
úÄ*The °dONLNdG
êÄ
ú‡)AssociateSection°dONLNdW
ê‡
ú
c)` function internally calls the °dONLNdv
ê
c
ú
•)ÉUpdateAlias°dONLNdÅ
ê
•
ú
‰)B function. It is .
°dONLNdí
ùl
©Ä(
¶lalso ö‡°dONLNdó
ùÄ
©˛)possible to update the alias r«Ä°dONLNdµ
ù˛
©
)~ecor;‡°dONLNdπ
ù

©
E)d using the „†°dONLNd≈
ù
D
©
´)3Alias Manager (see the L °dONLNd‹
ù
¨
©
œ)hchapter °dONLNd‰
™l
∂q(
≥l
“°dONLNdÂ
™q
∂ä)Alias ’°dONLNdÎ
™ä
∂±)Managerg°dONLNdÚ
™≤
∂ƒ)(” in  ¿°dONLNd˜
™≈
∂
")Inside Macintosh: Files砡dONLNd
™
"
∂
')] fªÄ°dONLNd
™
(
∂
û)or additional information).


€*
‚
¯4
‹*
‚
¯ 
›l
›
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd-
Ãl
€
{(
◊l+Displaying Publisher and Subscriber Bordersˇˇˇˇˇˇ€r(
◊

2
°dONLNdZ
‚l
Ó
ô(
ÎlAEach publisher and subscriber within a document should have a borË°dONLNdõ
‚
ô
Ó
„(
Î
ôder that appears °dONLNd¨
Ôl
˚
H(
¯l4when a user selects the contents of these sections. ÇÄ°dONLNd‡
Ô
H
˚
N)‹
YC°dONLNd·
Ô
N
˚
„)!ou should display a publisher borw‡°dONLNd
Ô
„
˚
Ù)ïder °dONLNd
¸lÑ(las thr¿°dONLNd
¸Ö¯)ee pixels wide with 50 per3¿°dONLNd&
¸¯
î)s$cent gray lines and a subscriber borÇ °dONLNdJ
¸
î
æ)ú
der as thro‡°dONLNdT
¸
æ
Ê)*
ee pixels °dONLNd^    l∂(lwide with 75 per†°dONLNdn    ∑
†)K8cent gray lines. Separate the contents of the section fr≥`°dONLNd¶    
†
–)È
om the ború`°dONLNd∞    
–
·)0der °dONLNd¥l"
(l'itself with one pixel of white space. T´@°dONLNd€
"
)£o cr÷°dONLNdfl
"
Y)eate your borl °dONLNdÏ
Z"
ÿ);ders, you should use patternæ@°dONLNd
ÿ"
Á)~s, nÆ°dONLNd
Á"
Ú)ot °dONLNd#l/(,lcolors. Depending on the user›‡°dONLNd,#Ò/
–)Ö3’s monitor type, colors may not be distinguishable.°dONLNd`5lA¨(>lIn general, bor¿¿°dONLNdo5¨A
æ)@>ders for publishers and subscribers should behave like the bor'†°dONLNd≠5
øA
fl(>
øders of .°dONLNdµBlNê(Kl'PICT'°dONLNdªBêN‡)$ graphics in a worR`°dONLNdÕB‡NÙ)Pd-pr$¿°dONLNd—BÙN
I)ocessing document. Δ`°dONLNd‰B
HN
P)T
A9¿°dONLNdÂB
PN
`) bor °dONLNdÈB
`N
‚)der should appear when the .
°dONLNd    Ol[Ÿ(Xluser clicks the content arw°dONLNd    OŸ[
≈)m5ea of a publisher or a subscriber and disappear when °dONLNd    T\lh
(el&the user clicks outside the content ar °dONLNd    z\
h
O)°ea of a section. Ï°dONLNd    ã\
Oh
U)B
Y¨Ä°dONLNd    å\
Uh
›)ou can also make all publisher °dONLNd    ¨iluæ(rland subscriber bor« °dONLNd    æiæu
≤)R5ders appear or disappear by implementing an optional °dONLNd    ÙvlÇ£(l
Show/Hide °dONLNd    ˛v§Ç≥)8Borb@°dONLNd

v≥Ç
)ders menu command. ˇD@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-51
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh¢(eäFigurR¿°dONLNd\¢hª)e 2-17@°dONLNd\ªh
â)+ displays the Edition Manager Show/Hide BorK °dONLNd6\
äh)œders menu command in the °dONLNdOiäu∫(rä
Edit menu.

óH®4òH®"òH]

ˇ·ˇ‚7^
    °dONLNd[çäò∫*#Figure 2-17°dONLNdgçÃò
ö)B-Edit menu with Show/Hide Borders menu command
°dONLNdñ
Yä
e
ñ(
bä:Depending on your application, you may choose to include r"†°dONLNd–
Y
ó
e
(
b
óesize handles or similar °dONLNdÈ
fä
rÙ(
oäcomponents in your boró`°dONLNdˇ
fÙ
r
)jders. Seµ¿°dONLNd

f

r
)"e ˇ`°dONLNd
    
f

r
•)“Object-Oriented Graphics BorVÄ°dONLNd
&
f
¶
r
Ê)âders” on page ç@°dONLNd
4
f
Ê
r
¯)@2-56· °dONLNd
8
f
¯
r
˝) fµ°dONLNd
:
f
˛
r    )or °dONLNd
=
sä
Œ(
|äan example of r⁄ °dONLNd
L
sŒ

)Desize handles.°dONLNd
[
Öä
ë
f(
éä2Whenever a user selects a portion of a publisher oà °dONLNd
ç
Ö
f
ë
˙)‹$r sets the insertion point within a °dONLNd
±
íä
ûê(
õä
pÇ °dONLNd
≤
íê
û¥)ublisherÓ‡°dONLNd
∫
í≥
û
/)#, you should display the bor‰°dONLNd
÷
í
/
û
g)|der as 50 per    ¿°dONLNd
„
í
h
û
ê)9    cent grayÃÄ°dONLNd
Ï
í
è
û
î)'. n °dONLNd
Ó
í
î
û
õ)
A®¿°dONLNd
Ô
í
õ
û) user can copy the contents °dONLNd
üä
´
˙(
®äWof a publisher or subscriber without copying the section itself by selecting the data, °dONLNdb
¨ä
∏
v*6copying, and then pasting the data in a new location. n¿°dONLNdò
¨
v
∏
})Ï
A©`°dONLNdô
¨
}
∏)$ user can cut and paste a selection °dONLNdΩ
πä
≈“(
¬äthat contains an ¿°dONLNdŒ
π”
≈Ê)Ientir[†°dONLNd”
πÊ
≈È)
e?@°dONLNd‘
πÍ
≈
R) publisher or subscriber. °dONLNdÏ
π
R
≈
)h$, but you should discourage users frÈ¿°dONLNd
π

≈)ûom °dONLNd
Δä
“
1(
œä%making multiple copies of a publisher]Ä°dONLNd8
Δ
1
“
@)ß. Sef‡°dONLNd<
Δ
@
“
G)e ∞Ä°dONLNd>
Δ
G
“),“Duplicating Publishers and Subscribers” on °dONLNdj
ӊ
fl°(
‹äpage Z‡°dONLNdo
Ӣ
fl¥)2-58Æ¿°dONLNds
Ӵ
flπ) fdž°dONLNdu
”∫
fl
#)or detailed information.°dONLNdé
Âä
ÒÍ(
ÓäWhen the user modifi§Ä°dONLNd¢
ÂÍ
Ò
')`es a publisher°dONLNd∞
Â
'
Ò
¢)=, your application should gr2Ä°dONLNdÃ
Â
¢
Ò
¯){ow or shrink its bor⁄‡°dONLNd‡
Â
¯
Ò)Vder to °dONLNdÁ
Úä
˛
^(
˚ä-accommodate the new dimension of the section.°dONLNdäê*
Y@Ä°dONLNdê
F)(ou should display only one publisher borƒ@°dONLNd>
F)∂0der within a document at a time. If a cursor is °dONLNdnä
Ç(ä:inserted within a publisher that is contained within a lar‚@°dONLNd®
Ç
º)¯ger publisherÄ°dONLNdµ
Ω
ˆ);, you should °dONLNd¬ä*Ù('ädisplay only the smaller7 °dONLNd⁄Ù*
Y)j, internal publisher boró†°dONLNdÚ
Y*
g)eder≤@°dONLNdı
g*)+. If it is absolutely necessary to display °dONLNd +ä7«(4äall section bor˚`°dONLNd/+«7
≠)=3ders within a document at the same time, you can crú†°dONLNdb+
Æ7
)Áeate a Show/Hide °dONLNds8äDô(AäBor÷@°dONLNdv8ôDfi)ders menu item)¿°dONLNdÑ8flD‰)F. °dONLNdáJäVê(Sä
Y@Ä°dONLNdàJêVÍ)ou do not need to prW°dONLNdúJÍV)Z@ovide support for publishers contained within other publishers. °dONLNd‹Wäcì(`äIf ≤`°dONLNdflWìc
,)    !you do not, you should dim the Cr°dONLNdW
-c)ö4eate Publisher menu command (to indicate that it is °dONLNd4däp
@(mä*not selectable) when a user attempts to cr÷¿°dONLNd^d
@p)∂-eate a publisher within an existing publisher»†°dONLNdãdp)ƒ
.

ßà
AòÄ:
õ
–HH



\*4

ˇˇˇˇˇˇ

õ
–´/
∂
]
˝ˇ¸fi
˝ˇ¸fi
˝ˇ¸fi
˝ˇ¸fi¯?3ü¸fi˘ˇ?ü¸fi˘¯3¸fi˘Û3ü¸fi¯s3ü¸fi˘Û3ü¸fi˘Û3ü¸fi˘Û3ü¸fi¯83œ¸fi
˝ˇ¸fi
˝ˇ¸fi
˝ˇ¸fi
˝ˇ¸fi
˝ˇ¸fi
ÔˇÏ
ÔÏ
ÔÏ
ÔÏÄ
Ę1¯ÏÄ
Ę    HÏüè˜    HÏ˛ôį0Ï˛ôį
@`Ï˛ôį¿Ï˛ôį    IÄÏ˛ôį    IÄÏèè˜1¯Ï
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
Ô™∏Ï
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏˆ1òÏÄˆ    IòÏûˆ    IòÏåˆÒòÏåˆ
@ÏåˆÒòÏåˆ    IòÏôåˆ    IòÏ܈1òÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏÙ0ÏÄı    IàÏį    IÄÏôôįÒÄÏôôį
AÄÏôôįÒÄÏôôį    IÄÏ˛ôį    IàÏį0Ï˛
ÄıÏ˛ÄıÏ˝ÙÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ˜1òÏĘ    IòÏè<x¯    IòÏëôïÒòÏúï
AòÏ鸯ÒòÏ`    IòÏ샯    IêÏéx¯1‡Ï
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ    0Òò˚0Ï    0
ôò˚    IòÏ    1·«Åôò˚    IòÏ˛3#
ôò˚ÒòÏ˛3
˘ò˚
A¯Ï    ?3Û
ôò˚ÒòÏ    03
ôò˚    IòÏ    13#
ôò˚    IòÏ    1·¡Åôò˚1òÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
Ô™∏Ï
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ˛0Ä0¸ÏÄ0Ä0¸Ï<<xôüé>6˛ÏfF1ò˝ô338˛Ïf>1òôôú330˛Ï~f1¯ôôé3?0˛Ï`f1Äôôá300˛Ïòbf1àôôì310ÿÏ<>üé30ÿÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ00‡˙Ï0˛0
Ä˙Ï3>8€>
áÄ˚Ï332d„33
å¿˚Ï338`√33
å¿˚Ï33`√3?
å¿˚Ï33`√30
å¿˚Ï33&d√31
åÃøÏ>8√>
áåøÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ00Ä0˝Ï0˛0¿¸Ï3>8€>6œè1„·¿Ï332d„338ÃΔ˛3 Ï338`√330ÃΔ˛3ÄÏ33`√3?0ÃΔ331¿Ï33`√300ÃΔ330‡Ï33&d√310ÃΔ332ffÏ>8√>0èÉ1„1ΔfÏˆ˚Ïˆ˚Ï
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ0˛>˘Ï0˛3˘Ï>3036|xŸ¿¸Ï˛30338ÃÄ ¸Ï˛30>30ÃÃ√ĸÏ˛30330ø¡¿¸Ï˛30330ÿ¿‡¸Ï˛3 330ì`¸Ï3?¿>0|x¡¿¸Ï
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
Ô™∏Ï
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ
ÔÏ0˛30˛˝Ï0˛100˛˝Ï>3003>>6|˝Ï˛3
00˝3#8Ã˝Ï˛3
00˝30Ã˝Ï˛3
00¸3
0Ã˝Ï˛3
00¸3
0Ã˝Ï˛3
 1¸3
0Ã˝Ï3?¿3>>0|˝Ï˘0¯Ï˘0¯Ï
ÔÏ
ÔÏ
Ôˇ¯Ï
Ôˇ¯Ï««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««fi
Î-    >xx!¯‚˝8¸¯˚! 
!| Ù
+ DÑ`¸D0Ä˙!! !B Ù
;9 BÄ Dπ¿ÑÄÛòqb DLq` ,8àÇ!0Ò¿B8π„ãúòqb 8qf,√ã;9 BÄ "D¬ Ådâí DD!ê 2DàÑ! |D¬$L"dâí Dâô3$Lë;9<B|x¯  ¬"DÇ |ÒDâ *Ñ!"DU? BDÇ$H Dâ @â"#»ë;9 B  "DɇÅD˘ *Ñ!
"DU!‡BDÇ'»D˘ @â"$Hë;9 B @"DÇ  ÅDÅ !
"D"!BDÇ$DÅ @â"$Hë;9 DÑ @"LÇ @ ÅDâ`!!"D"! BDÇ$H"Dâ`Dâ"$Hë;9>xx @4Å¿¸ ¯ÒDq†"8"!Ò¿|8Å„àDq†8q"#»è˜“˜"“˜“«««««««««««««««««««««««««««««
¯ ÇŒ
Ä˛ΔŒÄÛa≈Ä™8∞·„ãÄ‘Å"&@íD…$L”Ò"$@Ç<àÚ$H”Å"$@ÇDâ'»”Å"$@ÇDâ$”Å"$@ÇDâ$H”¯Ò!ƒ@Ç<àÒ„à”˜ “¯
 “¯

¿“««««)ƒ
  ÇÄ

˝0Ä@¸&ƒ
˛ Δ˛

˝
˙Ô.*§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`Ú.*§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âêÚ.*îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚âÚ.*
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"âÚ.*åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"âÚ.
åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"âÚ.*ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àqÚÒ
¸
flÒ¸
fl«««««
Ä˝Ä’Ä
˝Ä’(xá
‚Ãxâ√ãÄa¿◊(DààÅ
2DàÑLí ◊DDààÅ
"DàÑH÷DDàèÅ
"Dàá»÷˛Dàà

"DàÑ÷ÇDààÅ    "DòÑH ◊Çxá‚"xhcà¿◊@ĸ@˛◊@ĸ@˛ ‘ˇ2@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-52    )BUsing the Edition Manager4^*¿
¯
°dONLNd\lhÑ(elFigurR¿°dONLNd\Ñhù)e 2-18@°dONLNd\ùh“) shows the r*Ä°dONLNd\”h
 )6ecommended bor` °dONLNd%\
 h
È)M,der behavior for publishers. The top window °dONLNdQiluÒ(rlshows a publisher with its bor¡ °dONLNdoiÒu
Ÿ)Ö0ders displayed. The middle window shows how the °dONLNdüvlÇz(lborB °dONLNd¢v{Ç
Ó)Sders look when a user selects some of the contents of a section. The bottom window °dONLNdıÉlè¿(ålshows how the borU@°dONLNd
É¿è
Ú)TEders look when a user selects data within a document that includes a °dONLNd
Kêlú∫(ôlpublisher section.

æ*œ
¯4ø*œ
¯"ø*]

ˇ·ˇ‚7^
    °dONLNd
_¥løú*#Figure 2-18°dONLNd
k¥ÆøÙ)BPublisher borders

Œjv
¯òÄ,L
THH



\*î

ˇˇˇˇˇˇ
L
T—*
~
˘·ˇˇ
˘·ˇ
˘·ˇ
˘·ˇ˘Ô˛¸ˇ¸Ò˝ˇ˛ˇÔÿˇ ˘˚˛
ò˛˙Ç ˇ$˘Ë¸ˇ¸˛
IJ˝ˇ˛Ç/ÿˇ ˘˚áçü6pò„„3˙Ç ˇ$˘Ë¸ˇ¸ÃŒ338»ôì3#˛3
˝ˇ˛Ç/ÿˇ˘˚ÃÃ330‡ô√3˛3˙Ç ˇ$˘Ë¸ˇ
¸ÃÃ3?0pò„˛3?3˝ˇ˛˛/ÿˇ ˘˚    ÃÃ3008òs˛3
03˙Ä ˇ#˘Ë¸ˇ    ¸ÃÃ310òô˝313˝ˇ˛Ä/ÿˇ ˘˚áå0pò„„˙Ä ˇ˘Ô˛¸ˇ¸¯˛˝ˇ˛ˇÔÿˇ˘#ˆˇ˘Ìˆˇ
˘·ˇ
˘·ˇ¯ˇ˘„ˇ˘„ˇ˘„ˇ˘„$ˇ˘„Bˇ˘„Åˇ˘„    òˇ˘„√ÿˇ˘„Bˇ˘„Bˇ˘„Bˇ˘„~ˇ˘„ˇ˘„ˇ˘„ˇ¯ˇ˘„ˇ¯ˇ˘„8ˇ˘„8ˇ˘„8ˇ˘„8ˇ˘„8ˇ ˘    xÒ„p˛
˛0˜8ˇ˘    Õõ30˛
¸˜8ˇ#˘¡É
«1«
«èú|˛q„ûqÛÄ˙8ˇ#˘yÅ„mõ3mÉf€6p€1∂ÃŸΔ¿˙8ˇ#˘Ä3õ3Á
Ê€>`€1≥ßÉÄ˙8ˇ#˘Ä3õ3
Éf€0`€1∂ßĿ˙8ˇ#˘Õõ3mõ3mÉf€6`€1∂ßܿ˙8ˇ#˘
“[I´m4õm´Le´6 qõl€)*˙™8ˇ˘ÂU8ˇ˘
™ˇ¯ˇ˘Êàòˇ˘Ê
"8ˇ˘Êàòˇ%˘‡ ¸Ç$qƒ @
"8ˇ#˘ê˙Ç$"ä$ @àòˇ'˘!âëf1¡åÁŒcá0w Ç8ÀpgqÉådÄ
"8ˇ'˘!äJ)JRî•$îÇH$§Ń%, îÇJBBïàòˇ'˘!ã (yÇîΩÙÇH$ºÄ$%( îÇK¬NÜ
"8ˇ'˘!í)@BRî°$ÑÇH$†"ä$%( îÇJRïàòˇ'˘!·Ñ&3Ååîò¬cÅ0òqƒ8»dÅIÉédÄ
"8ˇ˘ ¯àòˇ˘ ¯
"8ˇ˘Êàòˇ˘Ê
"8ˇ˘Êàòˇ#˘
ÑÄê ˙˛
"8ˇ!˘ĸ ˙˛àòˇ'˘!g„c7π∏vI‹8»ò;å≥8ÀK≥å∞
"8ˇ'˘!íîÑêîѧêIJ$%$Rƒ•,    JJR¿àòˇ'˘!íóÑìîѧêIIà$Â<^Ñ•Ë    JJ^Ä
"8ˇ'˘!íîîîѧêIHH%" PÑ•    JJPÄàòˇ'˘!bììîɧàI;Ñ$‚
LÉ8»    :KåÄ
"8ˇ˘ ˙àòˇ˘ ˙
"8ˇ˘Êàòˇ˘Ê
"8ˇ˘Êàòˇ&˘
ÑÄ
Ä
  IJ ˝L
"8ˇ%˘˝Ä
  ˛˛ ˝Dàòˇ'˘!geª7Ã≥á2√∏¿ÊEò«`Çe§ÀYåÂ"
"8ˇ'˘!íñ$îÑíƒK
%!)(•(êTñ(%,bRE%àòˇ'˘#íÙ$îúíÉJ
%·/(°ÊêTî0!(C–E"
"8ˇ'˘!íÑ$î§íÄÇJ
%
(•
ê(î(%(BE%àòˇ'˘!bd$îúLá2§¿ÊòŒ`(d$»Aå$‚
"8ˇ˘Ê%àòˇ˘Ê¬
"8ˇ˘Êàòˇ˘Ê
"8ˇ˘Êàòˇ%˘˝

˝@Äé8Ä ÄÑ
"8ˇ%˘˝

˝@ÄQDÄ ˛àòˇ'˘#g9ÉñdLÁ3±é`Ê„@É9∏7ú¿
"8ˇ'˘§BX˛í
HRêIîÉê8ѧ§†• àòˇ'˘#t§BPÚûí    :I“IóÄPÑ$§ò•‡
"8ˇ'˘!î§BPÅí    JJRÄIîQDѧ§Ñ•àòˇ'˘#tú    Éêaë:IŒ`&ìé8É$∏∏ú¿
"8ˇ˘˛˙¯ ¸àòˇ˘˛˙¯ ¸
"8ˇ˘Êàòˇ˘Ê
"8ˇ˘Êàòˇ˘˚Ì
"8ˇ˘˚Ìàòˇ˘ëí∞c;9.eÄÔ
"8ˇ˘
íR¿î§•$ñÓˇ¯ˇ˘
íRÄѧ•$ÙÓˇ˘
íRÄ$ÑÓˇ˘qéÄc$∏‚dÔ~ˇ˘˝ ÏBˇ˘`˝ ÏBˇ˘ÊBˇ˘
™√ÿˇ˘ÂU    òˇ˘
™Åˇ˘„Bˇ˘„$ˇ˘„ˇ˘„ˇ˘„ˇ
˘·ˇ¯ˇ˘?ˇ‰ËDˇ˘ 01Èˇ˘`0$ËD    ¸ˇ˘†01È    ˇ˘>0$ËD|âÿˇ˘01È@IXˇ˘0$ËD@)Xˇ˘01È@)Xˇ˘0$ËD@I¸XU˘>01È|à@X
™˘†0$ËD@XU˘`01È@Xˇ˘ 0$ËDÿˇ˘?ˇÒÈˇ
˘·ˇ¯ˇ
˘·ˇ¯ˇ◊
c◊
◊
t◊
î◊
s’
˘·ˇ‡ˇ
˘·0ˇ
˘·0ˇ
˘·0ˇ˘˚ˇø˛ˇ¯Ô?˛ˇ˝ˇfl∞ˇ"˘Ä˙0000
Ä¿˝
@0ˇ'˘˙ø˛ˇ¯˛00
Ä¿?˛ˇ˝_∞e%˘Ä˝<|x‡>1Û„1Û„«á¿˝
@0ñ$˘˙ø˛ˇ¯ôôåff1ê˚31åÿ?˛ˇ˝_∞Ù"˘Ä˝ôåff1¿˚31åÿ˝
@0Ñ$˘˙ø˛ˇ¯ôå~f0‡˚31èÿ?˛ˇ˝¸_∞d"˘Ä˝ôå`f0p˚31å¿˝
@0ˇ$˘˙ø˛ˇ¯ôôåbf10˚31åL¿?˛ˇ˝_∞ˇ%˘Ä˝Ü<f‡31Û31Û0«á¿˝
@0ˇ˘˚ˇø˛ˇ¯˜00˝?˛ˇ˝ˇfl∞ˇ˘Ò00ˆ0ˇ˘Ò
‡
‡ˆ0ˇ
˘·0ˇ
˘·ˇ
Ã˘„0˘„0˘„00˘„H0˘„Ñ0ˇ˘„0ˇ˘„
0ˇ˘„á∞ˇ˘„Ñ0ˇ˘„Ñ0 ˘„Ñ0 ˘„¸0Ê˘„0)˘„0/˘„ˇ(˘„ˇÊ˘„pˇ˘„pˇ˘„pˇ˘„pˇ˘„pˇ˘    <x¿˝¿¿˜pˇ˘    3fÿ˝
¿¿˝˜pˇ#˘0`¿¿q«åq¿q„¡Á?úxÁú|‡˙pˇ#˘`x¿€fÀ`Ÿ∂¿Õú6Ãm≥6q∞˙pˇ#˘`¿¡ÊÃ˘¿y∂¿œò6ÃlÛ6`‡˙pˇ#˘`¿√fÿ`Ÿ∂¿Ã6Ãm≥6`0˙pˇ#˘3fÿ€fÀ`Ÿ∂¿Õò6Ãm≥6a∞˙pˇ#˘¥ñ“j€M&€j”jÕ≤úfΔ[6 J˙™òpˇ˘ÂUXpˇ˘™üˇˇ˘Ê
Q0U˘Áˇ¸îDp
™˘Áˇ˝Q0U%˘Gˇ˜¸ˇ˛ˇflˆˇ¯„顡˜ˇˇoˇ˛ˇ¸îDpˇ#˘[˙ˇ˛ˇflˆˇ˜]vˇˇ˜ˇˇoˇ˛ˇ˝Q0ˇ'˘!]õ¶sèúΔ9Ãg3‚9˜fl~ÒÕ#Ê>#üÊfl¸îDpˇ'˘!]mu≠kZ÷∂⁄flmˆ÷¯fl鈥˜⁄flmooZø˝Q0ˇ'˘!]u·ü{Z–æ¬flmˆ–ˇ_ˆˆµ˜⁄flml^¸îDpˇ'˘#[~ıØÔkZ◊∂fiflmˆ◊˜]vˆµ˜⁄flmkZø˝Q0ˇ'˘#Gûˆsú⁄Ÿœg≥˙Ÿ¯„éÒÕ˚Êfl≠üffl¸îDp"˘Òˇ˜¯ˇ˝Q0à˘Òˇ˜¯ˇ¸îDp"˘Áˇ˝Q0à˘Áˇ¸îDp"˘Áˇ˝Q0à#˘ûflˇˇ˚ˇˇ€ˇˇ˝˜ˇˇ˚˙ˇˇˇ¸îDp"!˘~fl¸ˇ˚ˇˇ˝˜ˇˇ˚˙ˇˇˇ˝Q0à'˘#f<G>'2>—ë‚màÒÕŸÒ¯”1Õ<m”ˇ¸îDp"'˘#[~⁄fi€⁄fi÷€Ì≠}ˆˆ∂˚k{N÷¥˝≠mkOˇ˝Q0à'˘#[~⁄€fi÷€Ì≠ùˆΔ∞˚h{^÷Ö˝≠mh_ˇ¸îDp"'˘#[~⁄˛⁄⁄fi÷€Ì≠̈∑w˚k˚^÷Ω˝≠mkflˇ˝Q0à'˘#g[>€fl›Ì±ˆ«y˝l¯fl1Õ˝±mflˇ¸îDp"˘Òˇ˚ˇ˜˙ˇ˝Q0à˘Òˇ˚ˇ˜˙ˇ¸îDpˇ˘Áˇ˝Q0ˇ˘Áˇ¸îDpˇ˘Áˇ˝Q0ˇ&˘ûˇˇ˚ˇflˇˇüˇ∑ˇ˜ˇflˇ˛˛ˇ˜˝ˇϸîDpˇ%˘~˝ˇflˇˇˇ∑ˇ˜˛ˇ˛˛ˇ˜˝ˇÓ˝Q0ˇ'˘!f<fë29å”3OœΔnôŒ<gflfñ˘Õ)úΔ¥îDpˇ'˘![~⁄v⁄fi€Nˇm?∂∑µµ÷µ˛€Í⁄uˆ¥ÁknµQ0ˇ'˘#[~¬ˆ⁄ÿ€_?m∂á¥5◊Ü~€Í⁄Û˜µÔÓ¥îDpˇ'˘![~fiˆ⁄÷€_flm∂øµ˚÷øæ€ı⁄ıˆµÔ{nµQ0ˇ'˘!gfˆ⁄ÿÏfi?s÷œΔ{ŸÃgıʈ˘ÕÔúˆƒîDpˇ˘ÁˇıQ0ˇ˘ÁˇÃîDpˇ˘ˡÄ
Q0ˇ˘ˡÄîDpˇ˘ˡÄ
Q0ˇ%˘˛˚¸ˇ
ø˛ˇÔ˛flˇqfl˜fl˚ˇfiˇÄîDpˇ%˘˛˚¸ˇ
ø˛ˇÔ˛fl˛ÎÆfl˜˛ˇ˛ˇÄ
Q0ˇ'˘#f8ÒüfÏΔ>3úgΔ|G>˚Ôfl1ëÚ8òœÄîDpˇ'˘!z÷˚oi€[[}ΩmÎ[Ìæ⁄flÒfi÷÷˙◊÷∑Ä
Q0ˇ'˘#b÷˚ok√X[}±mãCÌæ⁄βfiˆ÷˙Ÿ÷áÄîDpˇ'˘!Z÷˚okflª€}≠mk_Ìæ⁄˛ÎÆfi÷÷˙fi÷øÄ
Q0ˇ'˘#bÿ˝üÁº€æ1mågˆ[?qfl6—˙—ÿœÄîDpˇ˘˛ˇ˙ˇ˘ˇ˜˝ˇÄ
Q0ˇ˘˛ˇ˚ˇ¸¯ˇ˜˝ˇÄîDpˇ˘Ê
Q0ˇ˘ÂîDpˇ˘Ê
Q0ˇ˘˚
ÏîDpˇ˘˚
Ì
Q0ˇ˘$d¨ŒŒKô`ÓîDpˇ˘$î∞%))I%ÄÔ
_ˇˇ˘
$î†!))I=Ìê0ˇ˘
$î†%))I!Ó
P0ˇ˘c†….8ôÓê¸0ˇ˘˝Ï
PÑ0ˇ˘˝ÎêÑ0ˇ˘Ê
PÑ0ˇ˘™óá∞ˇ˘ÂUR
0ˇ˘™ë0ˇ˘„Ñ0ˇ˘„H0ˇ˘„00ˇ˘„0ˇ˘„0ˇ
˘·ˇˇ˘ˇ˘È0ˇ˘ÈDH0ˇ˘    È¯0ˇ˘(ÈDH
0ˇ˘Oå    È˘∞ˇ˘ÄåÈDHÄí∞ˇ˘å    ÈÄR∞ˇ˘åÈDHÄR∞ˇ˘Äå    ÈÄì¯∞U˘OåÈDH˘Ä∞
™˘(    È
Ä∞U˘ÈDHÄ∞ˇ˘    Èˇ∞ˇ˘ˇ¸ÈDH0ˇ
˘·ˇˇ
˘·ˇˇ◊
Á◊
z◊
b◊
Z◊
„
˘·ˇ‡ˇ
˘·0ˇ
˘·0ˇ
˘·0ˇ'˘˚ˇø˛ˇÄ0¿Ã¿`0˛ˇ˝ˇfl∞ˇ#˘Ä˚0¿¿¿`0˝
@0ˇ'˘˙ø˛ˇüé>6å|¯Ã|¯Ò·˛ˇ˝_∞ˇ!˘Ä˝˝ô338˚Ãc30˝
@0Ê$˘˙ø˛ˇ
˛ôú330˚Ãc30˛ˇ˝_∞Z"˘Ä˝˛ôé3?0˚ÃcÛ0˝
@0B$˘˙ø˛ˇ
˛ôá300˚Ãc0˛ˇ˝¸_∞^"˘Ä˝˛ôì310˚Ãc0˝
@0Ê'˘˙ø˛ˇüé30Ã|ÃÃ|Ã1·˛ˇ˝_∞ˇ˘Ä˝¯˘
@0ˇ ˘˚ˇø˛ˇ
¯åå˝˛ˇ˝ˇfl∞ˇ˘xxˆ0ˇ
˘·0ˇ
˘·0ˇ
˘·ˇˇ˘„0    L˘„0;˘„00x˘„H0{˘„Ñ0|˘„0ˇ˘„
0ˇ˘„á∞ˇ˘„Ñ0ˇ˘„Ñ0ˇ˘„Ñ0˜˘„¸0˜˘„0Δ˘„0µ˘„ˇ¥˘„ˇµ˘„pΔ˘„pˇ˘„pˇ˘Áˇ˛pˇ˘Áˇ˛pˇ ˘    a√á?ˇ˘„˝ˇ??ˇˇÛˇ¸¯ˇ˛pˇ˘    Lô3?ˇ˘Û˝ˇ
??˝ˇ¸¯ˇ˛pˇ$˘Oü??é8sé?é>‡¿cácÉ˚ˇ˛pˇ$˘aüá?$ô3$ü&I?2c…3íL…éO˚ˇ˛pˇ$˘|üÛ?>3?ÜI?0g…3ì…ü˚ˇ˛pˇ$˘|üÛ?<ô3?ü&I?3Á…3íL…üœ˚ˇ˛pˇ$˘Lô3?$ô3$ü&I?2g…3íL…ûO˚ˇ˛pˇ#˘˚i-ï$≤Ÿ$ï,Êï2Mcô9§…5µ˙UXpˇ˘*Ê™∏pˇ˘’ÊU_ˇˇ˘Áˇ˛±0ˇ˘Áˇ˛TDpU˘Áˇ˛±0
™%˘Gˇ˜¸ˇ˛ˇflˆˇ¯„顡˜ˇˇoˇ˛ˇ˛TDpU#˘[˙ˇ˛ˇflˆˇ˜]vˇˇ˜ˇˇoˇ˛ˇ˛±0ˇ'˘!]õ¶sèúΔ9Ãg3‚9˜fl~ÒÕ#Ê>#üÊfl˛TDpˇ'˘!]mu≠kZ÷∂⁄flmˆ÷¯fl鈥˜⁄flmooZø˛±0ˇ'˘!]u·ü{Z–æ¬flmˆ–ˇ_ˆˆµ˜⁄flml^˛TDpˇ'˘![~ıØÔkZ◊∂fiflmˆ◊˜]vˆµ˜⁄flmkZø˛±0ˇ'˘#Gûˆsú⁄Ÿœg≥˙Ÿ¯„éÒÕ˚Êfl≠üffl˛TDpˇ˘Òˇ˜¯ˇ˛±0à˘Òˇ˜¯ˇ˛TDp"˘Áˇ˛±0à˘Áˇ˛TDp"˘Áˇ˛±0à#˘ûflˇˇ˚ˇˇ€ˇˇ˝˜ˇˇ˚˙ˇˇˇ˛TDp"!˘~fl¸ˇ˚ˇˇ˝˜ˇˇ˚˙ˇˇˇ˛±0à'˘#f<G>'2>—ë‚màÒÕŸÒ¯”1Õ<m”ˇ˛TDp"'˘#[~⁄fi€⁄fi÷€Ì≠}ˆˆ∂˚k{N÷¥˝≠mkOˇ˛±0à'˘#[~⁄€fi÷€Ì≠ùˆΔ∞˚h{^÷Ö˝≠mh_ˇ˛TDp"'˘#[~⁄˛⁄⁄fi÷€Ì≠̈∑w˚k˚^÷Ω˝≠mkflˇ˛±0à'˘#g[>€fl›Ì±ˆ«y˝l¯fl1Õ˝±mflˇ˛TDp"˘Òˇ˚ˇ˜˙ˇ˛±0à˘Òˇ˚ˇ˜˙ˇ˛TDp"˘Áˇ˛±0ˇ˘Áˇ˛TDpˇ˘Áˇ˛±0ˇ&˘ûˇˇ˚ˇflˇˇüˇ∑ˇ˜ˇflˇ˛˛ˇ˜˝ˇÏ˛TDpˇ%˘~˝ˇflˇˇˇ∑ˇ˜˛ˇ˛˛ˇ˜˝ˇÓ˛±0ˇ'˘!f<fë29å”3OœΔnôŒ<gflfñ˘Õ)úΔ∂TDpˇ'˘![~⁄v⁄fi€Nˇm?∂∑µµ÷µ˛€Í⁄uˆ¥Ákn∂±0ˇ'˘#[~¬ˆ⁄ÿ€_?m∂á¥5◊Ü~€Í⁄Û˜µÔÓ∂TDpˇ'˘![~fiˆ⁄÷€_flm∂øµ˚÷øæ€ı⁄ıˆµÔ{n∂±0ˇ'˘!gfˆ⁄ÿÏfi?s÷œΔ{ŸÃgıʈ˘ÕÔúˆΔTDpˇ˘Áˇˆ±0ˇ˘ÁˇŒTDpˇ˘Áˇ˛±0ˇ˘Áˇ˛TDpˇ˘Áˇ˛±0ˇ%˘˛˚¸ˇ
ø˛ˇÔ˛flˇqfl˜fl˚ˇfiˇˇ˛TDpˇ%˘˛˚¸ˇ
ø˛ˇÔ˛fl˛ÎÆfl˜˛ˇ˛ˇˇ˛±0ˇ'˘#f8ÒüfÏΔ>3úgΔ|G>˚Ôfl1ëÚ8òœˇ˛TDpˇ'˘!z÷˚oi€[[}ΩmÎ[Ìæ⁄flÒfi÷÷˙◊÷∑ˇ˛±0ˇ'˘#b÷˚ok√X[}±mãCÌæ⁄βfiˆ÷˙Ÿ÷ᡲTDpˇ'˘!Z÷˚okflª€}≠mk_Ìæ⁄˛ÎÆfi÷÷˙fi÷øˇ˛±0ˇ'˘#bÿ˝üÁº€æ1mågˆ[?qfl6—˙—ÿœˇ˛TDpˇ˘˛ˇ˙ˇ˘ˇ˜¸ˇ˛±0ˇ˘˛ˇ˚ˇ¸¯ˇ˜¸ˇ˛TDpˇ˘˙ˇ˛Ó±0ˇ˘˙ˇ˛ÓTDpˇ˘˙ˇ˛Ó±0ˇ˘¸ˇ˛ˇ˛ÓTDpˇ˘¸ˇ˛ˇ˛Ó±0ˇ˘[õSÁ11¥fûÓTDpˇ˘[kO⁄÷÷∂⁄~Óøˇˇ˘[k_fi÷÷∂¬˛ÓP0ˇ˘[k_⁄÷÷∂fi˛Ó∞0ˇ˘cú_Á6—«f˙ÓP¸0ˇ˘{˝ˇ˜ˇˇ˛Ó∞Ñ0ˇ˘g˝ˇ˜ˇˇ˛ÓPÑ0ˇ˘Â∞Ñ0ˇ˘™Wá∞ˇ˘ÂU2
0ˇ˘™—0ˇ˘„Ñ0ˇ˘„H0ˇ˘„00ˇ˘„0ˇ˘„0ˇ
˘·ˇˇ˘ˇ˘È0ˇ˘ÈDH0ˇ˘    È¯0ˇ˘(ÈDH
0ˇ˘Oå    È˘∞ˇ˘ÄåÈDHÄí∞ˇ˘å    ÈÄR∞ˇ˘åÈDHÄR∞ˇ˘Äå    ÈÄì¯∞
™˘OåÈDH˘Ä∞U˘(    È
Ä∞
™˘ÈDHÄ∞ˇ˘    Èˇ∞ˇ˘ˇ¸ÈDH0ˇ
˘·ˇˇ
˘·ˇˇ◊
Á◊
z◊
b◊
Z◊
„◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
Ê◊
Z◊
B◊
^◊
Ê◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
    L◊
;◊
x◊
{◊
|◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
˜◊
˜◊
Δ◊
µ◊
¥◊
µ◊
Δ◊
ˇ◊
ˇ’’’’’’’’’’’’’◊
U◊

™◊
U’’’’’◊
ˇ◊
à◊
"◊
à◊
"◊
à◊
"◊
à◊
"◊
à◊
"◊
à◊
"◊
à$    ˘‡
‡É¿ƒ˝8 
ˆ
"#Å
Ñ ¸Da
ˆ
ˇ(!ÅÑ <âsÄÑ!
    ¬0‚√ãÉ√ãû8π¿˘
ˇ%!ÅÉ¿DâÑ@ 
    "$L$L"D¬ ˜$ Ò    Ò„‡Ñ ÑDâ@¯!
Ò"$H$H"DLj%!ÅÑ Dâ¿!

"‚'»$H"|Å¿˜%!ÅÑ Dâ !

"$$H"@Ä ˜%!ÅÑ Dô@@!

2"$H$H"DÇ ˜%!˘‡
‡É¿<iĸ 
”¬‚#à√à8Å¿˜˜‡˜D‡˜8‡’’’ ¯‡
GăÄ<
ć
D@ƒÄBć
Ñ#ħq¿@8pá‡
Ñ$@§àÄ@Dààч
Ñ$@îàÄ<@xàч
Ñ$@îàÄ@àèч
Ñ$@åàÄ@àà‡DD@åàÄBD˛à‡
GÉÄÑp`<8xᇠ¯‡’’’’’’’’’’’’’’’’’’’’’’
¯ Ç‹
Ä˛Δ‹ÄÛa≈Ä™8∞·„ãÄ‚Å"&@íD…$L·Ò"$@Ç<àÚ$H·Å"$@ÇDâ'»·Å"$@ÇDâ$·Å"$@ÇDâ$H·¯Ò!ƒ@Ç<àÒ„à·˜ ‡¯
 ‡¯

¿‡’’’’)ƒ
  ÇÄ

˝0Ä@¸˛&ƒ
˛ Δ˛

˝
˙˝-+§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`-+§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âê-+îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚â-+
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"â-+åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"â-
åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"â-+ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àqÒ
¸
ÌÒ¸
Ì’’’’’
Ä˝Ä„Ä
˝Ä„(xá
‚Ãxâ√ãÄa¿Â(DààÅ
2DàÑLí ÂDDààÅ
"DàÑH‰DDàèÅ
"Dàỉ˛Dàà

"DàщÇDààÅ    "DòÑH ÂÇxá‚"xhcà¬Â@ĸ@˛‚@ĸ@˛ ‚ˇQ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-53
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh¢(eäFigurR¿°dONLNd\¢hª)e 2-19@°dONLNd\ªh) shows the r*Ä°dONLNd\Òh
>)6ecommended bor` °dONLNd%\
>h
)M-der behavior for subscribers. The top window °dONLNdRiäu
(räshows a subscriber with its bor,¿°dONLNdqi
u
˚)â0ders displayed. The middle window shows how the °dONLNd°väÇò(äborB °dONLNd§vôÇ)Qders look when a user selects the contents of a section. The bottom window shows °dONLNdıÉäèø(åähow the borΩ`°dONLNd
Éøè
Ò)5Eders look when a user selects data within a document that includes a °dONLNd
Eêäú€(ôäsubscriber section.

æHœ4øHœ"øH]

ˇ·ˇ‚7^
    °dONLNd
Z¥äø∫*#Figure 2-19°dONLNd
f¥Ãø
)BSubscriber borders
°dONLNd
zkäw
m(tä8If a user tries to select only a portion of a subscriber8°dONLNd
≤k
mw
ˆ)„ , you should highlight the entir»‡°dONLNd
“k
ˆw
˝)âe °dONLNd
‘xäÑ˙(Åäcontents of the subscriberï °dONLNd
Óx˙Ñˇ)p. 6¿°dONLNd
xˇÑ
)
Aq`°dONLNd
Òx
Ñ
p) user cannot edit the dat@°dONLNd
x
qÑ
{)ka ip†°dONLNdx
{Ñ
∏)
n a subscriberÄ°dONLNdx
∏Ñ
«)=. Se%‡°dONLNdx
«Ñ
Œ)e oÄ°dONLNd!x
ŒÑ)“Modifying a °dONLNd.ÖäëÂ(éäSubscriber” on page <`°dONLNdBÖÊë¯)\2-59ê@°dONLNdFÖ¯ë˝) fd °dONLNdHÖ˛ë
g)or detailed information.°dONLNdaóä£
˛(†äWIf a user cancels a section using the publisher or subscriber options dialog box, your °dONLNd∏§ä∞*Yapplication should leave the contents of the section within the document, but you should °dONLNd±äΩ•*be surZ`°dONLNd±•Ωª)e to r†‡°dONLNd±ªΩ˙)emove the bor√`°dONLNd*±˙Ω
)?ders frq@°dONLNd1±
Ω
√))om this data, as it is no longer considerßÄ°dONLNdZ±
√Ω
˘)¨ed a section.

ŒàSòÄ,>
UHH



\*4

ˇˇˇˇˇˇ
>
U—o
ƒ
˛„ˇ¯
˛„¯
˛„¯
˛„¯˛˜ˇ˛ˇ¿Ò˛ˇ˛ˇÔÿ¯!˛
¸
IJÃ
Ä
ĸÇ ¯%˛Ù
˛ˇ¿
IJ¿
Ä
IJˇ˛Ç/ÿ¯!˛
¸√ΔœèÃqÒèèĸÇ ¯%˛Ù
˛ˇ¿fgôúdÃ…ôë˛ô
IJˇ˛Ç/ÿ¯!˛
¸ffôòp÷ôè˛ôĸÇ ¯%˛Ù
˛ˇ
¿ffüò8Ãq˛ôüôIJˇ˛˛/ÿ¯!˛
¸    ffòÃ9˛ôòĸÄ ¯$˛Ù
˛ˇ    ¿ffòòLÃ˝ôòôIJˇ˛Ä/ÿ¯!˛
¸
√Δè8ÃqÒ˛è
ĸÄ ¯˛˜ˇ˛ˇ¿¯
Ä
IJˇ˛ˇÔÿ¯˛Ò
Äį¯˛Ó˜¯
˛„¯
˛„ˇ¯¯˛Â¯˛Â¯˛Â¯˛Â$¯˛ÂB¯˛Âů˛Â    ò¯˛Â√ÿ¯˛ÂB¯˛ÂB¯˛ÂB¯˛Â~¯˛Â¯˛Â¯˛Âˇ¯¯˛Âˇ¯¯˛Â8¯˛@
Äqƒ`Äı8¯˛@Ä"ä$ ˝Äı8¯˛ß8ò ÇŒ&eª7Ã≥Ę8¯˛
˛§Ń$))ñ$îÑ탈8¯˛
Ù§ºÄ$ È/Ù$îúíɈ8¯ ˛
§†"ä$%)(Ñ$î§íÄĢÓ8¯ ˛
8òqƒÓ&d$îúLá˛˙ª∫8¯˛ ˘Ó8¯˛ †˚
8¯˛Ì‡˚8¯˛Ì
†Ä
8¯˛Ì
‡¸‡8¯%˛˛Ä ˛@
      
†á<
8¯%˛˛Ä ˛@˛      
‡
ˇ‡ˇ¯¯%˛
ñ`„,Ë&YÅÃã1éΔpgs¿†8
àò¯%˛Xêê±%AbBRQJP    !  • ‡œ
"8¯%˛
–ì°%GC¬^QCÃ    ' r#° †
3Ò‡
àò¯%˛PÄî°"âBP!J    ) í$• ‡ºp˛8
"8¯%˛
–`솂áAÅÃ!1ú'qô †ˇ·¸„ˇäàò¯˛Ì
·œÅ˚
Č
"8¯˛Ì
£{√Jàò˙
ˇ˛Ì
‚'º˛
Œ
"8¯˛Ì
¶ˇá¸Íàò¯˛Ì
Ó;ˇ¯ˇ¿Ó
"8¯'˛
qƒ`
Ù˝

˛
¨aˇ˛`Íàò˙
ˇ$˛
"ä$ D˝

˛
Ó!ˇˇ¡¸Œ
"8¯(˛ò ÇŒ&Gf…;á8¿¶¿ˇˇw0 àò˙
ˇ%˛
$Ń$))D•â    )A§% „Ä=ˇ˛†Ó
"8¯(˛
$Ä$ È/DΩ    )1º% †ˇˇÉ˘Íàò˙
ˇ%˛
$$"ä$%)(D°    )    †% ‡ˇˇ˘ˇÓ
"8¯(˛òqƒÓ& Dô    'pá$¿†ˇˇn àò˙
ˇ˛Ì
‡ˇˇ
"8¯˛Ì†˛˜˝O
àò˙
ˇ˛Ì‡˛˝fl
"8¯˛Ì†˛ˇø
àò˙
ˇ˛Ì‡˝˛
"8¯#˛˝H
@˛†˝>?
àò¯˛˝H
˛˚‡¸
"8¯&˛±ñ`Ó3Ɇò9ñÏ‹g2ŒÅƸ

àò˙
ˇ#˛JXêI
A$XíRK
@@‡¸
"8¯#˛JPI:A$–íRrJ
A¿†¸
àò¯#˛JPÄIJA
$íRíJ
B@‡¸
"8¯"˛Iê`):@ä    êíRq2
A¿†˚
àò¯˛Ì˘Ó
"8¯˛Ì˙ª∫àò¯˛Ì˘Ó
"8¯˛Âàò¯˛Â
"8¯˛
«@Îàò¯˛(¢@Í
"8¯˛ Aúf‡Ïàò¯˛
»BRêÏ
"8¯˛(BrêÏàò¯˛(¢BRíêÏ
"8¯˛
«AíríÏàò¯˛Â
"8¯˛Âàò¯˛Âˇ¯¯˛Â¯˛Â¯˛Â~¯˛ÂB˙
›˛ÂB˙
w˛ÂB˙
›˛Â√ÿ˘
˛Â    ò˘
˛ÂÅ˘
˛ÂB˘
˛Â$˘
˛Â˘
˛Â˘
˛Â˘
˛„ˇ¯˙

˛ˇÚÎ"$˙

˛Îàå˙
Ò˛0Î"$    ¸˙
ô˛PÎàå    ˘È˛üÎ"$|âÿ˘9˛    
Îàå@IX˘}˛

Î"$@)X˙

›˛

Îàå@)X˙

˛    
Î"$@I¸X˙
˛üÎàå|à@X˙
˛PÎ"$@X˙
˛0Îàå@X˙
=˛Î"$ÿ˙
˝˛ˇ¯Îàå˙
Ÿ˛„ˇ¯˙
·˛„ˇ¯˙

·◊
·◊
·◊
¡◊
·◊
!˛„ˇ˙

A˛„˙

a˛„˙

°˛„˙

·˛˜ˇˇˇ¯Ôˇˇ˛ˇÔÿ˘
#˛
˙0000
Ä¿˝Ç ˙
›(˛Ù
ˇˇ¯˛00
Ä¿ˇˇ˛Ç/ÿ˙
w&˛
˝<|x‡>1Û„1Û„«á¿˝Ç ˙
›"˛Ù
ˇˇ¯ôôåff1ê˚3
1åÿˇˇ˛Ç/ÿ¯ ˛
˝ôåff1¿˚31åÿ˝Ç ¯"˛Ù
ˇˇ¯ôå~f0‡˚3
1èÿˇˇ˛˛/ÿ¯ ˛
˝ôå`f0p˚31å¿˝Ä ¯"˛Ù
ˇˇ¯ôôåbf10˚3
1åL¿ˇˇ˛Ä/ÿ¯#˛
˝Ü<f‡31Û31Û0«á¿˝Ä ¯˛˜ˇˇˇ¯˜00˝ˇˇ˛ˇÔÿ¯˛Ú00˜¯˛Ú
‡
‡˜¯
˛„¯
˛„ˇ¯¯˛Â¯˛Â¯˛Â¯˛Â$¯˛ÂB¯˛Âů˛Â    ò¯˛Â√ÿ¯˛ÂB¯˛ÂB¯˛ÂB¯˛Â~¯˛Â¯˛Â¯˛Âˇ¯¯˛Âˇ¯˙
ˇ˛Â8˙
IJ@
Äqƒ`Äı8˙

IJ@Ä"ä$ ˝Äı8˙
Ä!˛ß8ò ÇŒ&eª7Ã≥Ę8˙

Ä ˛
˛§Ń$))ñ$îÑ탈8˙
è ˛
Ù§ºÄ$ È/Ù$îúíɈ8˙

à#˛
§†"ä$%)(Ñ$î§íÄĢÓ8˙
à#˛
8òqƒÓ&d$îúLá˛˙ª∫8˙

à˛ ˘Ó8˙
à˛ †˚
8˙

è˛ÌÔ˚ˇÓ8˙
IJÌ
Øˇˇ‡ˇˇÍ8˙

IJÌ
Ôˇ¯ˇˇÓ8˙
Ä(˛˛Ä ˛@
      
Øˇ˙x√ˇˇÍ8˙

Ä(˛˛Ä ˛@˛      
Ôˇ˛ˇÓˇ¯˙
ˇ(˛
ñ`„,Ë&YÅÃã1éΔpgs¿Øˇ˜ˇÒ«ˇÍàò˙
ˇ%˛Xêê±%AbBRQJP    !  • ÔˇÁˇ‡0ˇÓ
"8¯%˛
–ì°%GC¬^QCà    ' r#° Ø˛ˇÃÍàò¯%˛PÄî°"âBP!J    ) í$• Ô¯Cˇè
«Ó
"8¯%˛
–`솂áAÅÃ!1ú'qô Øjàò¯˛Ì
Ó0~˛„.
"8¯˛Ì
¨ÑÄ<ˇ¯™àò˙
ˇ˛Ì
ÌÿC‡
ˇ˛.
"8¯˛Ì
©xˇ¸
àò¯˛Ì
·ƒ?Ò
"8¯'˛
qƒ`
Ù˝

˛
£û
¯ü˜
àò˙
ˇ$˛
"ä$ D˝

˛
·fi>Á.
"8¯(˛ò ÇŒ&Gf…;á8¿©?àœ*àò˙
ˇ%˛
$Ń$))D•â    )A§% Ϭ
‡_
"8¯(˛
$Ä$ È/DΩ    )1º% Øˇ|
àò˙
ˇ%˛
$$"ä$%)(D°    )    †% Ôˇ¸
"8¯(˛òqƒÓ& Dô    'pá$¿Øˇˇ·ë*àò˙
ˇ˛Ì
Ôˇˇ¯ÄÓ
"8¯˛ÌØ˛ˇ∞Íàò˙
ˇ˛ÌÔ˛ˇÄ Ó
"8¯˛ÌØ˛ˇ@Íàò˙
ˇ˛ÌÔ˝ˇÄ
Ó
"8¯#˛˝H
@˛Ø˝ˇ¡¿Íàò¯˛˝H
˛˚Ô¸ˇÊÓ
"8¯&˛±ñ`Ó3Ɇò9ñÏ‹g2ŒÅÄظˇıÍàò˙
ˇ#˛JXêI
A$XíRK
@@Ô¸ˇÙÓ
"8¯#˛JPI:A$–íRrJ
A¿Ø¸ˇÚÍàò¯#˛JPÄIJA
$íRíJ
B@Ô¸ˇÓ
"8¯"˛Iê`):@ä    êíRq2
A¿†˚
àò¯˛Ì˘Ó
"8¯˛Ì˙ª∫àò¯˛Ì˘Ó
"8¯˛Âàò¯˛Â
"8¯˛
«@Îàò¯˛(¢@Í
"8¯˛ Aúf‡Ïàò¯˛
»BRêÏ
"8¯˛(BrêÏàò¯˛(¢BRíêÏ
"8¯˛
«AíríÏàò¯˛Â
"8¯˛Âàò¯˛Âˇ¯¯˛Â¯˛Â¯˛Â~¯˛ÂB˙
›˛ÂB˙
w˛ÂB˙
›˛Â√ÿ˘
˛Â    ò˙
˝˛ÂÅ˙
˝˛ÂB˙
˝˛Â$˙
˝˛Â˙
˝˛Â˙
˝˛Â˙
˝˛„ˇ¯˙
˝˛ˇÚÎ"$˘˝˛Îàå˘˛0Î"$    ¸˙
e˛PÎàå    ˙
˛üÎ"$|âÿ˙
≈˛    
Îàå@IX˙
Å˛

Î"$@)X˙
!˛

Îàå@)X˙
·˛    
Î"$@I¸X˙
²üÎàå|à@X˙

²PÎ"$@X˙
·˛0Îàå@X˘¡˛Î"$ÿ˘
˛ˇ¯Îàå˙
%˛„ˇ¯˘˛„ˇ¯˙
◊
÷÷=÷◊
›˛„ˇ˙
Ω˛„˙
ù˛„˙
]˛„˙
˛˜ˇˇˇÔˇˇ˛ˇÔÿ˘
%˛
¸˛3˛¿¿¿˝Ç ˙
›(˛Ù
ˇˇ˛˛¿ˇˇ˛Ç/ÿ˙
w&˛
˝„3·√ç≥·„`¯«œå«œè˝Ç ˙
›"˛Ù
ˇˇÒì33&N˛3Ä˚à    Δ33ˇˇ˛Ç/ÿ¯!˛
˛
√33Ü˛3˚ÃΔ33˝Ç ¯"˛Ù
ˇˇ„31Δ33Û˚à    Δ?3ˇˇ˛˛/ÿ¯ ˛
˝s30Ê33˚ÃΔ03˝Ä ¯"˛Ù
ˇˇÒ332fL33˚à    Δ13ˇˇ˛Ä/ÿ¯#˛
˝·Û·√å3·„ëÃëÃ√˝Ä ¯˛˜ˇˇˇˆ¿¿˛ˇˇ˛ˇÔÿ¯˛Ò¿¿¯¯˛ÒÄį¯
˛„¯
˛„ˇ¯¯˛Â¯˛Â¯˛Â¯˛Â$¯˛ÂB¯˛Âů˛Â    ò¯˛Â√ÿ¯˛
ÊˇËB¯˛
ÊˇËB¯˛
ÊˇËB¯˛
ÊˇË~¯˛
ÊˇË¯˛
ÊˇË¯˛
ÊˇÔˇ¯¯˛
ÊˇÔˇ¯˙
ˇ˛
ÊˇÏ8˙
IJflˇ?Ò«ˇ˚œ˝ˇˇ˜ˇøıˇÏ8˙

IJflˇøÓ∫Ìˇ˚Ô˝˝ˇøıˇÏ8˙
Ä#˛¨c≥Ôæ˝ÛòϯÕ"ds¶?ˇˇ˘àÏ8˙

Ä$˛
˛≠ÒøÌÎk}¥ÌµΩ∂ù˛ˇ¢˙"Ï8˙
è#˛≠°˛øÌÔãh}Ö̵±∂æˇˇ˘àÏ8˙

à%˛u≠ØÓ∫ÌÌkk˝Ω̵≠∂øøˇˇØ˚ˇ˙Ï8˙
à%˛tc≥Ò«ÛàÏ˛Õ̵±Ÿºˇˇè˚ˇ¯Ï8˙

à˛˝Ôˇ
Øˇˇ?ˇˇ˙Ï8˙
à˛˝Ôˇ
èˇ¸
èˇˇ¯Ï8˙

è˛
Óˇ
Øˇ˝<aˇˇ˙Ï8˙
IJ
Óˇ
èˇ¯ˇ¯Ï8˙

IJ
Óˇ
Øˇ˚ˇ¯„ˇ˙Ï8˙
Ä(˛ˇˇøˇÔ˛ˇflˇˇ˚Ô˛ÔˇèˇÛˇ¯Ï8˙

Ä(˛ˇˇøˇÔ˛ˇfl˛ˇ˚Ô˛ÔˇØˇˇÊ˙Ôˇ¯˙
ˇ(˛4œéiãÏ”?∫g8Ò«ÃFsè¸!ˇ«Ä„¯Ëàò˙
ˇ%˛”∑∑ßm_Nfi÷◊Z◊˚ooˆÔ≠oد
é:Í"8¯%˛á∂/m\^–◊^˚loΔÓ/oè??ÒòËàò¯%˛◊øµØnª^˛◊ÔZ˛˚ko∂Ì≠oÆB¿¸ZÍ"8¯%˛œ∂/éº_?Ôg1˝lw«v3oéÏ!ˇˇËàò¯˛
Óˇ
¨¯<
ˇ˛
Í"8¯˛
Óˇ
à‚įàËàò˙
ˇ˛
Óˇ
©œ¸O˚äÍ"8¯˛
Óˇ
àÔ
ÛòËàò¯˛
Óˇ
¨üăgöÍ"8¯&˛ˇÒ«ˇ˚œˇ¸ˇ}˛ˇ
é?·/àËàò˙
ˇ#˛ˇÓ∫Ìˇ˚Ôˇ›¸ˇ}˛ˇ
Øˇ¯>
Í"8¯(˛3ÛÔæ˝ÛòÏˇ‹sL¯õb<s„üèˇ˛Ëàò˙
ˇ%˛m˝ÒøÌÎk›≠;{k_}≠ÌoØˇˇÄHöÍ"8¯(˛mÒ˛øÌÔãh›°x{kg}°Ìoèˇˇ¸@xËàò˙
ˇ%˛mÌÓ∫ÌÌkkˇ›Ø{˚k{}ØÌoØ˛ˇÑ
XzÍ"8¯(˛≥ÒÒ«ÛàÏÔ›≥|˚lGºsÌüè˛ˇ¿
xËàò˙
ˇ˛
ÓˇØ˛ˇ¯ zÍ"8¯˛
Óˇè˝ˇ¿¯Ëàò˙
ˇ˛
ÓˇØ˝ˇ‡‡zÍ"8¯˛
Óˇè¸ˇÛxËàò˙
ˇ˛
ÓˇØ¸ˇ˙˙Í"8¯#˛
˛ˇ€ˇˇˇ˜ˇˇfl˛ˇˇ˚˛ˇè¸ˇ˙xËàò¯ ˛
˛ˇ€ˇˇˇ˜˛ˇ˛˚ˇØ¸ˇ˘zÍ"8¯&˛'4œàÊ>/≥„4âëÃfòÚ??ˇè¸ˇ¯xËàò˙
ˇ"˛⁄”∑€zflumˆ”∂÷ˆ⁄w˙flflˇØ˚ˇ˙Í"8¯ ˛⁄◊á€bflumˆ∂÷Δ⁄˘˙flˇ˘àËàò¯!˛⁄◊ø€Zflz̈˜∂÷∂⁄˛˙fiflˇ¢˙"Í"8¯ ˛€7œÎbfl∫Û˚7∂÷«fÒ˙flˇ˘àËàò¯˛
ÊˇÍ"8¯˛
ÊˇËàò¯˛
ÊˇÍ"8¯˛
ÊˇËàò¯˛
ÊˇÍ"8˙
ˇ˛qfl˜˛ÎˇËàò˙
ˇ˛ÎÆfl˜ÍˇÍ"8˙
ˇ˛˚Ôfl1ÃèÏˇËàò˙
ˇ˛Òfi÷ˆ∑ÏˇÍ"8˙
ˇ˛βfiˆΔ∑ÏˇËàò˙
ˇ˛ÎÆfi÷∂∑ÏˇÍ"8˙
ˇ˛qfl6Δ∂ÏˇËàò˙
ˇ˛
ÊˇÍ"8˙
ˇ˛
ÊˇËàò˙
ˇ˛
ÊˇÔˇ¯˙
ˇ˛
ÊˇË˙

˛
ÊˇË˙
D˛
ÊˇË~˙

˛
ÊˇËB˙
ˇ˛
ÊˇËB˙
ˇ˛ÂB˙
ˇ˛Â√ÿ˙
ˇ˛Â    ò˙
ˇ˛ÂÅ˙
ˇ˛ÂB˙
ˇ˛Â$˙
ˇ˛Â˙

ˇ˛Â˙
˛Â˘˛„ˇ¯˙
3˛ˇÚÎ"$˙
ã˛Îàå˙
„˛0Î"$    ¸˙
¡˛PÎàå    ˙
˛üÎ"$|âÿ˙
q˛    
Îàå@IX˙
s˛

Î"$@)X˙
Û˛

Îàå@)X˙
Ò˛    
Î"$@I¸X˘a˛üÎàå|à@X˘
˛PÎ"$@X˙

˛0Îàå@X˘˛Î"$ÿ˙
˛ˇ¯Îàå˙
˛„ˇ¯˙
˛„ˇ¯˘◊
◊
o◊
_◊
O◊
/◊
◊
ˇ◊

◊
D◊

◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ◊
ˇ’’’’’’’’’◊
ˇ◊
Ä◊

Ä◊
Ä◊

Ä◊
è◊

à◊
à◊

à◊
à◊

è◊
Ä◊

Ä◊
Ä◊

Ä◊
ˇ◊
ˇ’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’"    ˘‡
‡É¿ƒ˝8 ˛"ı!Å
Ñ ¸Da
˛ı&"ÅÑ <âsÄÑ!

√ác√ãÉ√ãû8π¿¯&"ÅÑ DâÑ@!

$Hò"$L$L"D¬ ¯%!Ò    Ò„‡Ñ ÑDâ@¯!Ò$"$H$H"Dǘ&"ÅɇDâ¿ ¯    #à"'»$H"|Å¿¯&"ÅÄ Dâ       H"$$H"@Ä ¯&"ÅÄ@Dô@@ 
    2$Hê"$H$H"DÇ ¯&"˘‡
‡ÉÄ<iĸ ‡”√á#√à√à8Å¿¯˜‡˜D‡˜8‡’’’ ¯‡
GăÄ<
ć
D@ƒÄBć
Ñ#ħq¿@8pá‡
Ñ$@§àÄ@Dààч
Ñ$@îàÄ<@xàч
Ñ$@îàÄ@àèч
Ñ$@åàÄ@àà‡DD@åàÄBD˛à‡
GÉÄÑp`<8xᇠ¯‡’’’’’’’’’’’’’’’’’’’’’’’
|ÑA‹
@˛c‹@yé0‚¿UXpÒ≈¿‚@àÑ I"dâ&·xàÑ ADy$·@àÑ A"D≷@àÑ A"Dâ·@àÑ A"Dâ$·|xÉ‚ ADxÒƒ·    ˜‚

s
¯

‚

Ñ    ˜‡‚

◊

◊

◊

◊

)b˛ÄA@ÄÄ˝@ x¸
˛&b˛Äc˛ÄÄ˝˛Ñ˙
˝-+R8àÄã0Ò¿U8≈é8∞ã8π«è√áa≈ÄÄqf,ƒKp„å8∞-+RDàÄåë I"DFD"D»åàD¬$HàDHà"&@Äâô3$LàâD»-+JDUàê A@DD"@àààDʼnHàDà"$@Äâ"$HàÄÒDà-+J|Uàé‡A"@DD"8ààà|Ç$HàDà"$@Äâ"$HàÅDà-+F@"àÅA"@DD"ààà@Ç$HàDà"$@Äâ"$HàÅDà-
FD"àë A"˛D"DàààDÇ$HàDHà"$@Ñâ"$»àâDà-+B8"àéÒ¿A8DC8àÄàÜ8ÅÁèCáÜ!ƒ@xq"#Hàpƒ8àÄ˝
ÌÒ
¸
Ì’’’’’¿x˝@„@Ñ˝@„<xCÄÄqf<D·≈¿∞‡Â"DD@Äâô"DB&…Â""DD@Äâ"DB$â‰""DG¿Äâ"DC‰â‰"DDÄâ"DBâ‰A"DD@Ñâ"LB$âÂA<xCÄxq<41ƒà‡Â @¸ ˛
 @¸ ˛‚ˇ(é@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-54    )BUsing the Edition Manager4^*¿
¯
°dONLNd\lhó(el    GenerallyºÄ°dONLNd    \ñh
¶)*=, the appearance and function of publisher and subscriber borù¿°dONLNdF\
¶h
È(e
¶ders should be °dONLNdUilu£(rlthe same acrm@°dONLNdai£uø)7oss dif °dONLNdhi¿uÃ)ferȆ°dONLNdkiÀu
)ent applications:‡°dONLNd{i
u
")G. Th-°dONLNdi
#u
°)e following sections entitled °Ä°dONLNdùi
°u
¨)~“T◊@°dONLNdüi
´u
 )
ext Bor‚ °dONLNd¶i
 u
‰)ders,”w °dONLNd¨i
Âu
Á)
 °dONLNd≠vlÇÄ(l“Spr܇°dONLNd±vÄÇ∏)eadsheet Bor&Ä°dONLNdΩvπÇ”)9ders,”ªÄ°dONLNd√v”Ç’)
 ;Ä°dONLNdƒv÷Ç
^)“Object-Oriented Graphics Bor톰dONLNd·v
^Ç
x)àders,”'†°dONLNdÁv
yÇ
Ü) any°dONLNdÍv
ÜÇ
é)d ¿°dONLNdÏv
èÇ
Ú)    “Bitmapped Graphics °dONLNd
Élè{(ålBor÷@°dONLNd
É{èì)ders”Î@°dONLNd
Éìè¿) describe sÁ °dONLNd
É¡è

).pecialized featurm†°dONLNd
$É
è
§)J#es for publisher and subscriber bor#†°dONLNd
GÉ
•è
≈)öders in °dONLNd
Oêlú}(ôlworÄ°dONLNd
Rê~úç)d-pÉ@°dONLNd
Uêçúê)
rH@°dONLNd
Vêëú…)ocessing, spr憰dONLNd
cê…ú
_)8"eadsheet, or graphics applicationsŒ‡°dONLNd
Öê
_ú
d)ñ. 

∫*¡
¯4ª*¡
¯ ºlº
¯

ˇ·ˇ‚7^°dONLNd
â≠lªs(∑l
T°dONLNd
ä≠rªØ)ext Bordersˇˇˇˇˇˇ‘@(∑
Ò
2
°dONLNd
ó¡lÕâ( lIn wor¡`°dONLNd
ù¡âÕú)d-pr¯ °dONLNd
°¡úÕ
›)Eocessing documents, a publisher may contain other publishers. Howeverfl`°dONLNd
Ê¡
›Õ
Ù( 
›, one °dONLNd
ÏŒl⁄ (◊lpublisher should not D†°dONLNd
ŒÀ⁄Ë)_overlap≥†°dONLNdŒË⁄
9) another publisher9`°dONLNdŒ
9⁄
>)Q. ¿°dONLNdŒ
>⁄
D)
YÃ@°dONLNdŒ
C⁄
Í)%ou should display only one publisher °dONLNdB€lÁz(‰lborB °dONLNdE€{Á
˜)Yder at a time. If an insertion point is placed within a publisher that is encompassed by °dONLNdûËlÙú(Òlanother larƒ@°dONLNd©ËúÙ÷)0ger publisher˛Ä°dONLNd∂Ë÷Ù
›):<, you should display only the smaller internal publisher borÓ`°dONLNdÚË
›Ù
Î(Ò
›der    °dONLNdıË
ÏÙ
Ó)
.°dONLNd˜˙l

a(
l8In exceptional cases, it may be necessary to display mor‡°dONLNd/˙
b

 )ˆe than one publisher or °dONLNdG
l
´(
lsubscriber borZ°dONLNdU
´

Â)?Hder at a time. For example, a publisher may consist of a paragraph that °dONLNdù
l
 
Ó(
lXincludes a marker for a footnote. The data contained within the footnote should also be °dONLNdı
!l
-ë*consider‡°dONLNd˝
!í
-˘)&ed part of the publisher9°dONLNd
!˘
-
œ)g0. When a user selects the paragraph, you should °dONLNdE
.l
:Ï(
7lsimultaneously display a bort@°dONLNda
.Ï
:
)Äder arë@°dONLNdg
.

:
W)ound the footnote.°dONLNdz
@l
Lé(
IlThe bor}‡°dONLNdÅ
@é
L
Ù)"Rder of a publisher that contains text should be located between characters within °dONLNd”
Ml
Y
}(
Vl=the text. The insertion point, when placed on such a boundaryP°dONLNd
M
}
Y
Ê(
V
}, should gravitate towar¿°dONLNd(
M
Á
Y
Ô)jd °dONLNd*
Zl
f¶(
clthe publisherL@°dONLNd7
Z¶
f˛):. That is, a click in frπ °dONLNdO
Z˛
f
ê)X$ont (to the left) of a publisher borˇ`°dONLNds
Z
ê
f
Ï)íder should place the °dONLNdà
gl
s‚(
plcursor inside the publisher‡°dONLNd£
g‚
s
…)v5, so that subsequent typing goes inside the publisher1°dONLNdÿ
g
…
s
ı)Á. Clicking °dONLNd„
tl
Ä
"(
}l,at the end (to the right) of a publisher borI °dONLNd
t
#
Ä
fl)∑,der should also place the cursor inside the °dONLNd;
Ål
çñ(
äl    publisherÓ‡°dONLNdD
Åï
çó))
.°dONLNdF
ìl
üÊ(
úlWhenever two separate borp‡°dONLNd_
ìÊ
ü
)zders ar ‡°dONLNdf
ì

ü
,)    e adjacení@°dONLNdo
ì
-
ü
2))t,T†°dONLNdq
ì
3
ü
Ï)) the boundary click should go in between °dONLNdö
†l
¨¬(
©lthem. This is also tr™ °dONLNdØ
†¬
¨Ù)Vue for a bory°dONLNdª
†ı
¨
˜)3<der that is next to other nontextual aspects of a document, .°dONLNd˜
≠l
πé(
∂lsuch as ,
Courier°dONLNdˇ
≠é
π≤)"'PICT'°dONLNd
≠≤
π

)$ graphics or page brR`°dONLNd
≠


π
")Xeaks..
°dONLNd
øl
À©(
»lWhen a user r1¿°dONLNd,
ø™
À
)>emoves information frΔ°dONLNdA
ø

À
∑)b(om a publisher that contains text data, W@°dONLNdi
ø
∏
À
Ï)¨you should °dONLNdt
Ãl
ÿo(
’l
rE°dONLNdu
Ãp
ÿà)esize }†°dONLNd{
Ãà
ÿß)the borù °dONLNdÇ
Ãß
ÿ±)deÇÄ°dONLNdÑ
̲
ÿÊ)r so that it b0 °dONLNdí
ÃÁ
ÿ
)5ecome} °dONLNdó
Ã

ÿ
)
s∫ °dONLNdò
Ã

ÿ
&) smalleÂÄ°dONLNdü
Ã
&
ÿ
))
r¿°dONLNd†
Ã
*
ÿ
,)
.ö¿°dONLNd°
Ã
,
ÿ
”)% When a user adds information to the °dONLNdΔ
Ÿl
Âñ(
‚l    publisherÓ‡°dONLNdœ
Ÿï
Âö)), Ó‡°dONLNd—
Ÿö
ÂÂ)you should enlar“ °dONLNd·
ŸÂ
Âı)Kge tÌ@°dONLNdÂ
Ÿı
Â
)he bor `°dONLNdÎ
Ÿ

Â
)deØ¿°dONLNdÌ
Ÿ

Â
¶)r to accommodate the new text.;‡°dONLNd
Ÿ
ß
Â
Ê)ã The insertion °dONLNd
Êl
Ú™(
Ôlpoint should rG‡°dONLNd(
Ê´
Ú
")?emain within the publisherx`°dONLNdB
Ê
"
Ú
')w. °dONLNdE
¯lÊ(
lIf a user highlights the entir¿°dONLNdc
¯Ê
Ω)z1e contents of a publisher and then chooses Cut fræ`°dONLNdî
¯
Ω
Û)◊om the Edit °dONLNd†l
9(l-menu, you should not delete the publisher borâ`°dONLNdÕ
9
Í)Õ&der within the document. The user may °dONLNdÛl
B(l2intend to delete the existing publisher data and rJ‡°dONLNd    %
C
ˆ)◊)eplace it with new data, or the user may °dONLNd    Nl+–((lwant to move the entirƒ °dONLNd    d–+
ä)d,e publisher and its data to a new location. V†°dONLNd    ê
ã+
£)ªFigur)`°dONLNd    ï
£+
º)e 2-20Δ‡°dONLNd    õ
º+
›) shows °dONLNd    £,l8ï(5lthis state.

Z*k
¯4[*k
¯"[*]

ˇ·ˇ‚7^
    °dONLNd    ∞Pl[ú*#Figure 2-20°dONLNd    ºPÆ[¥)B
A0°dONLNd    ΩP¥[
7)  publisher with contents removed

jj¶
¯òÄ0Ò
wHH



\*î

ˇˇˇˇˇˇ
Ò
wng_
fi%
¸Ä@˝Ä˜˚    Ä`¿˝
ġ" Ä˝Ä˜ ¯ @˝
ġ1/ ∞‡8≈Œ8ë]√ãŃK1f]p"\8yá 8Cá‚√àà‡8∞‡1/ …Fë"`ÑL$L…ô"a" "`Dààô" "DDHÅ$Hâ…1/ âDë@ÑHHâA" "@Dààë  <DH
$EQâ1/ âDë"@á»
ƒHâ"A" "@|ààë" DG«‚$EP‡â1- âD
ë"@Ñ$Hâ"A" "@@ààë" DDÄ$B âˇ1/ âDì"@ÑH$»â"A" &@Dààë" "DDHÅ$B!â1/ à‡Dç@cà
√Hâ@ @8xá <Cá‚#Ç ‡à‡¯Äˆ˙ԯĘ

˙àÔ
χ˙pÔ————$aÄ Ä˚˙@įBIJ@ÄÇ ˙ ˙@ÙB˛
˛@Ä1/q«qàé,8p‡p"\D@‚Á±ã≈Œ\‚ÃG
á·\Xq¿1/àÇ" àë2Dâ" "`"D@Cà»åë&"a2BàÅ"`dàÄ1àÇ  àë"DÅ" "@"*ÄB˛àë$"@Ú"Bà

@DxÄ1¯Ç  Ö"|p‡" "@>*ÄB˛àë$"A"Bá

"@DàÄ1ÄÇ  Ö"@" "@ B˛àë$"A"BÄÅ
"@DàÄ1àÇ" Ç"Dâ" &@"B˛àë$"A"BàÅ"@DàÄ1pÇÇ"8p‡ @2˛àèƒ@Ú"@AÄá·@Dx`
Á
¯*Ò"¯TÒ˛¯"€¯D€¯"€¯D€"˚

"˛
ĸ
 ˝0˝Ä ¯˚

D˛
Ĉ˝Ä¯*&àé√áá"·«é"\‡8∞‡.qfbΔ,<·¿xq√ãa¬¯*&àë$Hë
≈$D"a…0âô"#"2Dë DàÑLà""¯*U$Hë
£
‰D"Aâ â˛"DDàÑHà!‚¯)U'œë
≈$D"Aâ ˘˝"DÒ¿Dàá»à""¯)"$
£$D"Aâ Å˝"Dë DàÑà""¯)"$Hë
≈$D&Aâ â˝"Dë DàÑHà""¯+"#á«"·ÁÉ@‡à‡ q˛"<·¿xpcàÜ!‚ ˘¯DÛ¸@Ú¯"ÛD¸@Ú
¯DÒ8ϯ"€¯D€¯"€¯D€¯*€¯T€—————————————————————————————————————————————————————————————————————————————————————————————————————,    ˘‡
‡
¡Äƒ˝8p`  a ˛IJ@˙
*Å"@¸Dàê    ˝
IJ@˙
1/Å$ <âsÄÑ
    P<#,8∏"&8∞X·≈éŒ,√àé1/Å$ DâÑ@    Pë"!2D¿""»"dB&D"3$Hë"1/Ò    Ò„‡D ÑDâ@¯àë"!"DÄBà"DB$D "$Hë"1/ÅÑ Dâ¿!àë"!"|ÄBà"DC‰D"$E"1/Å
 Dâ A
¸ë"!
"@ÄÇà"DBD"$E"1/Å@Dô@@Äê
ì"!"DÄÇà"DB$D""$B"1/˘‡
‡·Ä<iĸ
¯`
<!"8ÄÇàD1ƒC"#Ç
˜˜Á
˜D˜Á˜8‹——— ¯‹
GăÄ<
Ä‹
D@ƒÄBÄ‹
Ñ#ħq¿@8pá‹
Ñ$@§àÄ@DààÑ‹
Ñ$@îàÄ<@xàÑ‹
Ñ$@îàÄ@àèÑ‹
Ñ$@åàÄ@àà‹DD@åàÄBD˛à‹
GÉÄÑp`<8xá‹ ¯‹—————————————————————
¯ Çÿ
IJΔÿÄÛa≈Ä™8∞·„ãÄfiÅ"&@íD…$L›Ò"$@Ç<àÚ$H›Å"$@ÇDâ'»›Å"$@ÇDâ$›Å"$@ÇDâ$H›¯Ò!ƒ@Ç<àÒ„à›˜ ‹¯
 ‹¯

¿‹————)ƒ
  ÇÄ

˝0Ä@¸˙&ƒ
˛ Δ˛

˝
˙˘.*§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`¸.*§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âê¸.*îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚â¸.*
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"â¸.*åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"â¸.
åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"â¸.*ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àq¸Ò
¸
ÈÒ¸
È—————
Ä˝ÄflÄ
˝Äfl(xá
‚Ãxâ√ãÄa¿·(DààÅ
2DàÑLí ·DDààÅ
"DàÑH‡DDàèÅ
"Dàệ˛Dàà

"DàчÇDààÅ    "DòÑH ·Çxá‚"xhcଷ@ĸ@˛fi@ĸ@˛ fiˇI4@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-55
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähê(eä
Y@Ä°dONLNd
\êh
ã)9ou should leave the cursor inside the small publisher borL†°dONLNd:\
ãh)˚der for further typing. If the °dONLNdYiäu
ı(räVuser inserts the cursor in a new location (instead of typing data inside the existing °dONLNdØväÇò*borB °dONLNd≤vôÇÍ)der), you need to r˜°dONLNd≈vÍÇ
t)Qemove the empty publisher bor∑°dONLNd‚v
uÇ
ç)ãder fr'‡°dONLNdËv
éÇ)om the document to allow the °dONLNd
Éäè
(åäuser to move the publisher=‡°dONLNd
É
è
")v    . This ef≈@°dONLNd
(É
"è
Ø)""fectively deletes the publisher frh°dONLNd
JÉ
∞è)éom the document. If °dONLNd
^êäú
:(ôä*the user pastes the publisher that is curr°dONLNd
àê
;ú
⁄)±%ently held in the scrap, you should rß°dONLNd
≠ê
⁄ú
Í)üe-cr˘¿°dONLNd
±ê
Íú)    eate its °dONLNd
∫ùä©ò(¶äborB °dONLNd
Ωùô©ß)der\¿°dONLNd
¿ùß©
P)*. If the user cuts or copies other data frfl °dONLNd
Íù
P©
∑)©om the document befor†°dONLNd
ˇù
∏©
Ú)he pasting the °dONLNd™ä∂Ω(≥äpublisher frE °dONLNd™æ∂
j)4'om the scrap, the publisher should be rΩ°dONLNd@™
j∂
ó)¨    emoved frÙ†°dONLNdI™
ó∂
“)-om the scrap.

‘H€4’H€ ÷ä÷

ˇ·ˇ‚7^°dONLNdX«ä’˚(—äSpreadsheet Bordersˇˇˇˇˇˇ‘@(—
2
°dONLNdm€äÁô(‰äBor÷@°dONLNdp€ôÁ∑)ders ar0@°dONLNdw€∏Á‡)ound spr °dONLNd€‡Á)(Beadsheet data or other data in arrays should look and behave very °dONLNd¡ËäÙ⁄(Òämuch like text bor`°dONLNd”Ë⁄ÙÚ)Pders. î`°dONLNdŸËÚÙ

)Figurg °dONLNdfiË

Ù
#)e 2-21†°dONLNd‰Ë
$Ù
|) shows a typical borÛ@°dONLNd¯Ë
{Ù
¡)Wder within a spr\@°dONLNdË
¬Ù
Î)G    eadsheet °dONLNdıä

π(˛ä    document.


#H
44
$H
4"
$H]

ˇ·ˇ‚7^
    °dONLNd
ä
$∫*#Figure 2-21°dONLNd(
Ã
$“)B
A0°dONLNd)
“
$
î)/ publisher border within a spreadsheet document
°dONLNdZ
°ä
≠’(
™äNote that the borΔ°dONLNdk
°’
≠)KGder goes below the column headers (A, B, C, D) and to the right of the °dONLNd≤
Æä
∫ç(
∑ä
rE°dONLNd≥
Æé
∫
–)Kow labels (1, 2, 3, 4)—it should not overlap these cell boundaries. The bor›`°dONLNd˛
Æ
–
∫
¸(
∑
–der at the °dONLNd    
ªä
«fl(
ƒäbottom and the borX°dONLNd
ªfl
«)UGder on the right side can be placed within the adjacent cells (outside °dONLNdb
Ȋ
‘
=(
—ä,of the cells that constitute the publisher).°dONLNdè
ڊ
Êπ*
Unlike borÑ@°dONLNdô
⁄π
Ê‚)/    ders in w™°dONLNd¢
⁄‚
ÊÎ))or‰Ä°dONLNd§
⁄Î
Ê˛)    d-pr@°dONLNd®
⁄ˇ
Ê
p)ocessing applications, bor√Ä°dONLNd¬
⁄
p
Ê
ü)qders in sprñ`°dONLNdÕ
⁄
ü
Ê
)/eadsheet documents (or °dONLNd‰
Áä
Û
—(
äLother documents with array data) can overlap. That is, a user can select a r@°dONLNd0
Á
“
Û(

“ow of cells to °dONLNd?
Ùä
Í(
˝äObe a publisher and an overlapping column of those cells to be another publisherÛ‡°dONLNdé
Ù
È
Ó(
˝
È. Δ@°dONLNdê
Ù
Ó
Ù)
YÜ¿°dONLNdë
Ù
Ù
)ou °dONLNdî
ä¸(
äshould never display morU‡°dONLNd¨
¸
g)re than one publisher borÄ°dONLNdƒ

h)l%der at a time. When a user selects a °dONLNdÈäò(äsprÑ °dONLNdÏò
")!eadsheet cell that is part of mor⠡dONLNd
"
|)äe than one publisherê¿°dONLNd!
|
ˇ)Z, you should display only the °dONLNd?ä'ò($äborB °dONLNdBô')Vder of the publisher that was last edited. (This can be accomplished by comparing the °dONLNdò(ä4ß(1ämodifi⁄`°dONLNdû(ß4
.) cation dates of the publishers.)°dONLNdø:äF
o(Cä8If it is absolutely necessary to display all section born@°dONLNd˜:
oF)Â#ders within a document at the same °dONLNdGäS–(Pätime, you can crÀ°dONLNd*G–S
2)Feate a Show/Hide BorLJ°dONLNd>G
3S
˙)c,ders command in the Edit menu to toggle all °dONLNdjTä`ò(]äborB °dONLNdmTô`ÿ)ders on and of¶‡°dONLNd{Tÿ`›)?f.°dONLNd~fär
&(oä#When data is added to or deleted fr¿°dONLNd°f
'r
≈)ù%om a publisher that consists of a spr∑°dONLNdΔf
≈r)ûeadsheet cell or °dONLNd◊säª(|äother arrayû °dONLNd‚s∫˜)0, you should r˛°dONLNds˜
!)=esize its b¶°dONLNd˚s
"
+)+or‡Ä°dONLNd˝s
+
5)    de≈‡°dONLNdˇs
6
?)r tz‡°dONLNds
@
˛)
*o accommodate the addition or deletion of °dONLNd,Ääå¢(âädata. ¿°dONLNd2Ä¢å©)
A∫`°dONLNd3Ä©å
ì)4 publisher should behave like a named range in a spró °dONLNdgÄ
ìå
)Íeadsheet. For example, if a °dONLNdÉçäôø(ñäuser cuts a rº °dONLNdêçøô
Ã)5=ow within a publisher that consists of a named range in a sprflÄ°dONLNdÕç
Ãô(ñ
Ãeadsheet, you °dONLNd€öä¶
L(£ä,should shrink the publisher data and its borW¿°dONLNd    ö
L¶
o)¬der corrM °dONLNd    ö
o¶
¶)#espondingly] °dONLNd    ö
•¶
ß)6
.


3H
âòÄ@
S
ıHH



\*4

ˇˇˇˇˇˇ

S
ı
6Iâ>œˇ¯ÙÄ¯Ä˘˘¯@˘ÙÄ¯Ä˘˘¯@˘Ù1Ä˝0˝Ä˛˝˛

‡˛˝x˝@˛
¿˛Ù1Ä˝0˝Ä˛
IJ˛
0˛˝l˝@˛˝Ù0Ä˝x˝Ä˛
IJ˛˝˝f˝@˛˝Ù0Ä˝x˝Ä˛˝˛˝˝f˝@˛
IJÙ0Ä˝Ã˝Ä˛
IJ˛˝˝f˝@˛˝Ù0Ä˝¸˝Ä˛
IJ˛˝˝f˝@˛˝Ù1Ä˝Ã˝Ä˛
IJ˛
0˛˝l˝@˛˝Ù1Ä˝Ã˝Ä˛˝˛

‡˛˝x˝@˛
¿˛ÙÄ¯Ä˘˘¯@˘ÙÄ¯Ä˘˘¯@˘Ùœˇ¯ÙÄ‹™‡˘ÙÄÊUW¯UP˘Ù!Ä¯Ä˘‡ ˚ ĸ`˘Ù!Ä¯Ä˘ ˚1ĸP˘Ù)įÅ1ƒò≤@˛8≤LY *ò≥¸`˘Ù)įÅI$§¬@˛…$¬Ra $§ƒí¸P˘Ù)įÅ9$úÇ@˛$ÇNA  úѸ`˘Ù)įëI$§Ç@˛$ÇRA  §Ñ¸P˘Ù)įëI$§Ç@˛    $ÇRA  §Ñí¸`˘Ù)įé9#úÅ¿˛8ÅŒ@‡ úɸP˘Ù"Ä¯Ä˝@˛¸ ¯`˘Ù#Ä¯Ä˛

IJ¸¿¯P˘Ù˛ˇ˛˙"DDƒ˘DT˘DF¯Dd˘DHÙÄ¯Ä˘˘¯P˘ÙÄ¯Ä˘˘¯`˘Ù+ÄÄÄ˙Ä˝@#á˝|p¬˛
«¿é|P˘Ù+Ä¿@˙Ä˝¿dHë˝à2"˛ Aë@`˘Ù+Ä¿s˚Ä˝@§Hë˝àR"˝ Bë
@P˘Ù,Ä
ÄîĸĽA#àë˝pí"˝@Ñëx`˘Ù+Äì˚Ä˝B$Gë˝â‚˝Äàè"P˘Ù-ÄêĸĽCÙ@ë˝â¯"˛

¡?`˘Ù-ÄRîĸĽ@$A˝àB˛
ÇDP˘Ù,Ä¿ås˚Ä˝@#Ü˝pDz·å8`˘ÙÄ˚Ģ˘¯P˘ÙÄ`˚Ģ˘¯`˘Ù˛ˇ
˝H¸àâë¯Q˘ÙÄ¯Ä˘˘ˇ˛¯`˘ÙÄ¯Ä˘˘ˇ˛¯P˘Ù0    Ä¿Ä ˛Ä˝@¿G
˛ˇ˚„˚fi˛„Äé8`˘Ù/    Ä
Ä@ ˛Ä˝¡»É˛ˇÛ›ÛÓÔû˝DAë"DP˘Ù/Ä,Δ$Œ`Ä˝B
HÖ˛ˇ˚›ÎfiÔ^˝ÑBë"D`˘Ù0ÄÄâ1))$êÄ˝C¬Hⲡ˚„€èfi˛
ƒDé"DP˘Ù/Ä¿I!(1‰`Ä˝B$G벡˚›ªˆÌfi˝$HëD`˘Ù/Ä¿I!(1Ä˝B'‡üü˛ˇ˚›ÅˆÏ˝$O—DP˘Ù0Ä¿I!))$êÄ˝B A
˛ˇ˚›˚vÔfi˛$@ëD`˘Ù0ÄÄé Δ$¬`Ä˝A¿F
˛ˇ˚„˚èfi˛
√Äé8P˘ÙÄ˙Ģ˘ˇ˛¯`˘ÙÄ˙Ģ˘ˇ˛¯P˘Ù˛ˇ˛˙"DDƒ˘DT˘DF¯Dd˘DHÙÄ¯Ä˘˘¯P˘ÙÄ¯Ä˘˘¯`˘Ù+Ä¿Ç˝Ä˝Á«¸|qÒ¬¸é8P˘Ù)Ä
¿D˝Ä¸@Hë¸@à""˚ë"D`˘Ù*    Ä¿Iés9IJĸÄHë¸@àB"˚ë"DP˘Ù,    Ä¿®íîí@˛Ä˝
¿á¸xp‚"¸
"D`˘Ù+    Ä¿®íóëIJĸ àë¸à‚¸
"DP˘Ù+    ć
íî@˛Ä¸!ë¸à"¸
"D`˘Ù,    Ä¿
íîí@˛Ä˝!ë¸DâB¸"DP˘Ù,    Ä¿
és    IJĽ
¡¸8p·Ç¸8`˘ÙIJ¸Ä˘˘¯P˘ÙIJ`¸Ä˘˘¯`˘Ù
ÿˇ—˘ÙÄ‹™‡˘ÙÄ‹U@˘ÙÄ¿¯Ä˘˘¯@˘ÙÄ¯Ä˘˘¯@˘ÙÄ¯Ä˘˘¯@˘ÙÄÄ¯Ä˘˘¯@˘ÙÄ¿¯Ä˘˘¯@˘ÙÄ¿¯Ä˘˘¯@˘ÙÄ¿¯Ä˘˘¯@˘ÙÄÄ¯Ä˘˘¯@˘ÙÄ¯Ä˘˘¯@˘ÙÄ¯Ä˘˘¯@˘Ù˛ˇ¸¯Dƒ˘DT˘DFÔDHÙ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡9˛

Û¿¿Åà˝p‡@@@¬@@@˛B˙ĸ
 7˛    
  C¸à
¿@@@@@@˛
˘ĸ
 @˛<
AyÁ
@†"xFXqpxqs«D«1`è8pÒ≈á8éD≥,p@˛<
AâÄ@†"DB"dâÄDâÑHòDBê"HòDâ&Hëë"DÃë2 @˛<
‚„«¿ÅâÄ @
"DB DâDâHê®BêDyHëë Dàë" @˛<
 

âÄ @@
"DBD˘DâOê®B"àê|âƒOüë Dàü" @˛<
 
â@Ä@¯"DBDÅDâH
B"Hê@â$Hë Dàê" @˛<
  
â2ÄÄ
@&DB"DâDâHê
B"HêDâ$Hëë"Làë" @˛<
Û¿¿¡x“
¯@xBDqxq«
Aëè8xÒƒGé4àé"Û˜ÌÛà˜ÌÛp–¡¡¡
˝@¯ –˝
è
à
x–˝
àÄ
à
Ñ
–˛
G
H„ÄÄp·–˛
HÅIÄâ–˛
HÅ)xÄÒ–˛
HÅ)Å–˛
HÅÅ–˝
ààÅÑâ–˝
è
‡¿xpÒ–
˝@¯ –¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡˛‡D ÄÃ˛@ Ã˛Ãqᮂ√áé.—˛D àôI$Hë0—˛ƒD àëÚ#»ë —˛D àë    $Hü —˛D àë    $Hê —˛D àë    $Hë —˛„ƒáÚ#«é —ÛÄ–Ù
Ä–Ùœ¡¡¡¡,˛ÄÄ @˝¬A¿¸@ Ó)˛˛Ä˛ @˝@@ ˙Ì1˛+ëƒDXqáé®·Δ,p·≈ÄX·≈Œ<xF8„,ã1f"X√áa≈Ä1˛+í$DdààëI"2!&@dB&"DB"DA2L…ô"dDHà"&@1˛+R"®DÄàëÚ"!@DB$"DB <A"Hâ"DDà"$@1˛+S‚®Dpàü    "!ƒ@DC‰"DB DA"Hâ"DDà"$@1˛+2
Dàê    "!$@DB"DB DA"Hâ"DDà"$@1˛+2!Dààë    ""!$@DB$"DB"DA"$Hâ&DDHà"$@1˛+¡DpáéÒ¬"·ƒDD1ƒ<xB<1"√àâDCáÜ!ƒ@̸
 @›̸
 @›¡¡¡¡¡˝@¿˛˛@”˝@ ˛˛@”˝°„¬ã1‚'.Eá‘˝°""L…"0FHÄ’˛
""Hâ" DH‘˛
">Hâ" DH‘˛˘" Hâ" DH‘˛    ""$Hâb DHÄ’˛    „¬√àâ·°é @DG’˝

¸
˝@“˝

¸
˝Ä“ˇ-‚@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-56    )BUsing the Edition Manager4^*¿
¯
°dONLNd\lh
#(el*When a user cuts a publisher and its entirÔ`°dONLNd*\
#h
á)∑e contents within a spr›‡°dONLNdA\
áh
Ú)deadsheet document, the °dONLNdXiluÄ(rlentir
¿°dONLNd]iÅu

)e section should be held in th    ‡°dONLNd{i
u
#)Åe scrap.uÄ°dONLNdÉi
#u
«)!$ Do not leave an empty publisher bor`°dONLNdßi
»u
Ï)•    der in a °dONLNd∞vlÇz(lsprÑ °dONLNd≥vzÇ∂)eadsheet (as r£`°dONLNd¡v∂Ç
%)<ecommended for text bor°dONLNdÿv
&Ç
Ì)p0ders). If a user attempts to paste a copy of an °dONLNd
Élèª(ålexisting publisher¿°dONLNd
ɪè
µ)O9, you should warn the user by displaying an alert box (se¯`°dONLNd
SÉ
µè
º)˙e °dONLNd
Uêlú
L(ôl1“Duplicating Publishers and Subscribers” on page Í°dONLNd
Üê
Lú
^)‡2-58=‡°dONLNd
äê
_ú
b)
)ë¿°dONLNd
ãê
bú
d)
.

∫*¡
¯4ª*¡
¯ ºlº
¯

ˇ·ˇ‚7^°dONLNd
é≠lª
!(∑l Object-Oriented Graphics Bordersˇˇˇˇˇˇ‘@(∑
Ò
2
°dONLNd
∞¡lÕ
t( l<In an object-oriented drawing application, the publisher borÈ`°dONLNd
Ï¡
tÕ
¨( 
tder should fi]@°dONLNd
˘¡
≠Õ
Œ)9    t just arA‡°dONLNd¡
ŒÕ
Á)!ound °dONLNdŒl⁄¬(◊lthe selected objects.°dONLNd‡lÏr*
Y@Ä°dONLNd‡rÏõ)    ou can pr≈‡°dONLNd'‡õÏ∫))ovide rÙ`°dONLNd.‡∫Ï
Â)Eesize handles that appear with all drawing objects to allow the user °dONLNdsÌl˘w(ˆlto ∑‡°dONLNdvÌw˘z)
r|‡°dONLNdwÌ{˘≤)esize the bor’°dONLNdÑÌ≤˘
)7der of a publishere@°dONLNdñÌ
˘
)N. e@°dONLNdòÌ
˘
)Figur8°dONLNdùÌ
˘
6)e 2-22’Ä°dONLNd£Ì
6˘
ö) shows a publisher bor€¿°dONLNdπÌ
ö˘
Δ)d
der with rÀ‡°dONLNd√Ì
Δ˘
fi),esize °dONLNd…˙l
ë(
lhandles.


(*
9
¯4
)*
9
¯"
)*]

ˇ·ˇ‚7^
    °dONLNd”
l
)ú*#Figure 2-22°dONLNdfl
Æ
)¥)B
A0°dONLNd‡
¥
)
F)% publisher border with resize handles
°dONLNd!l-s(*l
AG@°dONLNd!t-y)
n†°dONLNd    !z-|)
 ò†°dONLNd
!|-‚)application can make p@°dONLNd !„-
)gublisher bor¨@°dONLNd,!
-
-)5ders A@°dONLNd1!
.-
O)appear Å¿°dONLNd8!
O-
R)!
tƒ °dONLNd9!
R-
])o ffi°dONLNd<!
]-
ü)loat over the arx†°dONLNdL!
†-
“)Cea the user °dONLNdX.l:í(7lpublisheπ†°dONLNd`.í:ò)&s.v†°dONLNdb.ô:Ω) The borÙÄ°dONLNdj.Ω:
&)$der acts like a clipping r∏¿°dONLNdÑ.
':
æ)j ectangle—anything within the bor1°dONLNd§.
ø:
–)òder °dONLNd®;lGœ(Dlbecomes the publisher›‡°dONLNdΩ;ŒG”)b. ›‡°dONLNdø;”GÎ)Figur∞†°dONLNdƒ;ÎG
)e 2-23N °dONLNd ;
G
ı)6 shows a publisher that contains clipped graphics and °dONLNdHlT
(Ql&its subscriber in another application.°dONLNd'Zlfs*
A∫†°dONLNd(Zsf•) user can cr±‡°dONLNd4Z•f
ó)27eate publishers and subscribers that overlap each otherfi¿°dONLNdkZ
óf
Δ)Ú. Thus, bor◊ °dONLNdvZ
Δf
Ò)/    ders may °dONLNdgls
ï(plDoverlap and it may no longer be possible to turn on a particular bor§ °dONLNd√g
ïs
Á(p
ïder when the user °dONLNd’tlÄÿ(}lclicks within a publisher˘ °dONLNdÓt◊Ä
i)k . Drawing applications should pr°dONLNdt
jÄ
⁄)ìovide a menu command, °dONLNd$Ålçá(älShow ›†°dONLNd)Åáçñ)Bor3‡°dONLNd,Åóç
)ders, that toggles to Hide Borë`°dONLNdJÅ
ç
Î)Å.ders. This command should allow users to turn °dONLNdxélö¯(ól all publisher and subscriber borƒ °dONLNdòé¯ö
0)åders on or of£‡°dONLNd•é
0ö
5)8f.


8j    
¯òÄ2
î
èHH



\*î

ˇˇˇˇˇˇ

î
è
<=œ
Ã
¸
fiˇ¯˘
¸
fi˘
¸
fi˘
¸
fi˘¸
~ˇÔ˚ˇÛ˘ˇ˜Ï˘¸
Ä ˙˛
ÄˆA˘"¸
~Ä/˚ˇÄ
Ä
à˛˘ˇAÏ˘ ¸
Ä ˙ÒÒè
Å≥««Δ8p¯A˘!¸
~Ä/˚ˇ˝ôÅѲfd»˘ˇAÏ˘¸
Ä ˙
˝ôÅπÉÊff`‡¯A˘!¸
~Ä/˚ˇ
˝ôüÅôܲf`p˘ˇÏ˘¸
Ä ˙
˝ôò
ôܲf
`8¯@˘!¸
~Ä/˚ˇ
    ˝ôòÅôܲfdò˘ˇ@Ï˘ ¸
Ä ˙ôôÒèÒÉÁΔf8p¯@˘ ¸
~ˇÔ˚ˇ˛

Ä˝˝˘ˇ˜Ï˘¸
Ù

Ä˝Ú˘
¸
fi˘
¸
fi˘
¸
fiˇ¸˘¸
‡˘¸
‡˘¸
‡˘¸
‡˘¸
‡!˘¸
‡@å˘¸
‡ÄL˘¸
‡·Ï˘¸
‡!˘¸
‡!˘¸
‡!˘¸
‡?˘¸
‡˘¸
‡˘¸
‡ˇ¸˘¸
‡˘¸
‡˘¸
‡˘¸
‡˘¸
‡˘¸
‡˘¸
‡˘¸
¸xͲ˘¸
¸}ÍU^˛˘¸
¸zÍ™æ˛˘¸
¸}ÍU^˛˘¸
¸(Ͳ˘¸
¸¯Ù˛˘¸
¸(¯
>ı˛˘¸
¸˚?ˇÛˇÄ¿˜˛˘¸
¸(˚ˇÊ~Å¿˜˛˘¸
¸˚ˇflˆ¡¿˜˛˘¸
¸(˚˛˛˜Û¿˜˛˘"¸
¸¸o¯
„˜ùÄ˙˛˘!¸
¸(¸|˘8˛˘"¸
¸˝| ˘8˛˘"¸
¸(˝¯¿?ˇ˘h˛˘"¸
¸˝¿‡
˙˘X˛˘"¸
¸(˝
˘˲˘"¸
¸˝|(è˘‹˛˘$¸
¸(˝x@˛å˚
¨˛˘$¸
¸˛‡˝¯˚
V˛˘%¸
¸(˛¿`˛ġ¿˚
™˛˘&¸
¸˛
@í¿¸
W˛˘&¸
¸(˛

¿˛¸¸
´˛˘&¸
¸˛
~˛W¸
U˛˘'¸
¸(˛
x˛0Ä
´Ä˝
´Ä˛˘'¸
¸˛
p˛ U‡˝
’¿˛˘&¸
¸(
‡˛`™∞¸ͯ˛˘&¸
¸‡@‡˛UP¸’_ˇ˛˘&¸
¸(Ä¿™∏¸™™´˛˘%¸
¸˝¿U\¸’UV˛˘(¸
¸(ć™Æˇ™™Æ˛˘(¸
¸éˇˇUW◊
’Ux˛˘(¸
¸(@
™´ÄÆ
™´‡˛˘'¸
¸˝UU‡TW˛˛˘'¸
¸(˝@™™ø˙¨º˛˘&¸
¸8˝
˝UXp˛˘&¸
¸(`˝ì˝™∑z‡˛˘'¸
¸p2Ò€˝U_
’@˛˘&¸
¸(pˇˇ‡ˇ¸™™¿˛˘&¸
¸–˝˝UW’UIJ˘$¸
¸(‡
ÓÄ˝˚™´Ä˛˘!¸
¸¿~¸˙U˛˛˘#¸
¸(¿¸˚™´˛˛˘#¸
¸
¿`8¸
˚UV˛˛˘#¸
¸(
Å`_
‡¸
˚™Æ˛˛˘#¸
¸
@ü¿˚’¸UT˛˛˘ ¸
¸(
@:˙˚™¨˛˛˘"¸
¸C€¸˙’¸UX˛˛˘!¸
¸(¬Å˙
˚™∞˛˛˘"¸
¸
ÇÅÄ˚
˚U`˛˛˘"¸
¸(
ÇÄ¿˚
˚™¿˛˛˘"¸
¸ÇÄ@˚
˚U¿˛˛˘$¸
¸(À√¸˚

´˝™
´Ä˛˛˘#¸
¸Ó√Ñ˙
◊ı˛UV˝˛˘$¸
¸(˚Ä˚
™>˛™º˝˛˘$¸
¸!¸Ä˚
÷˛Up˝˛˘$¸
¸(6√‡?Ä˚Í
Í™™‡˝˛˘#¸
¸gN˙VuU_¿˝˛˘"¸
¸(OL
Ï˙j™¯¸˛˘"¸
¸Nx˙6
ˇ¿¸˛˘¸
¸(
‹p˜:¯˛˘¸
¸
¯¿˜¯˛˘¸
¸(pĘ¯˛˘¸
¸`Ę¯˛˘¸
¸(·ÄÌ˛˘¸
¸«Ï˛˘¸
¸(    ΔÏ˛˘¸
¸åÏ˛˘¸
¸(7ˆ¯˛˘¸
¸/¯>¯˛˘¸
¸(*8¯˜?¯˛˘¸
¸hp¯Áü¯˛˘¸
¸(˛`¯ˇŒ¯˛˘¸
¸ò¿¯ˇÊ¯˛˘ ¸
¸(∫¿˝Ä˝ˇ`¯˛˘"¸
¸∏IJÁ˛?ˇ`¯˛˘"¸
¸)±Ä˛ˇ‡˛~¿¯˛˘!¸
¸
k˝ˇ¿˛~ˇ‹¯˛˘!¸
¸
*c˝ˇ¿
»ˇ‹¯˛˘"¸
¸Êx˛?ˇ¿Ãˇ‹¯˛˘"¸
¸*o˛˛ˇÃˇˇ‹¯˛˘!¸
¸/˛ˇ‹ˇˇ˜˛˘!¸
¸)Ø˚˛ˇ˛ˇˇ˜˛˘"¸
¸ûÕ˛ˇ˛ˇ<¯˛˘"¸
¸
(ç˝Äˇˇ¯˛ˇø¯˛˘ ¸
¸
À¸Äˇˇ˛˝ˇ¯˛˘!¸
¸    («›Ä
ˇˇ¸˝ˇ˛¯˛˘!¸
¸    ã˝ˇˇ¸˝ˇ˛¯˛˘!¸
¸    (˚˘
ˇˇ¸˝ˇ¸¯˛˘!¸
¸    >cˇˇ˛¡˝ˇ¯˛˘¸
¸    (?Œˇˇ˛ÿ˝ˇ˜˛˘!¸
¸L˛ˇ˝˛ˇ¸˜˛˘!¸
¸(¯˛ˇ˝˛ˇ¸˜˛˘!¸
¸@˛ˇ˝˛ˇ¸˜˛˘¸
¸(˝˙ˇ¸˜˛˘¸
¸˝˙ˇ¯˜˛˘¸
¸(˝˙ˇ¯˜˛˘¸
¸˝˙ˇ¯˜˛˘¸
¸(˝
˙ˇ¯˜˛˘¸
¸˝
˙ˇ¯˜˛˘¸
¸(˝
˙ˇ¯˜˛˘¸
¸˝
˙ˇ¯˜˛˘¸
¸(˝
˙ˇ¯˜˛˘¸
¸˝
˙ˇ¯˜˛˘¸
¸(˝
˙ˇ¯˜˛˘¸
¸¸˙ˇ¯˜˛˘¸
¸(¸?˛ˇ¸ˇ¯˜˛˘¸
¸¸ˇÒ¯ˇ¯ˇ¯˜˛˘¸
¸(¸ˇˇ¯ˇ¯˜˛˘¸
¸¸ˇ¯˜˛˘¸
¸(¸ˇ¯¯˜˛˘¸
¸¸?ˇ¯˜˛˘¸
¸(¸?ˇ¯˜˛˘¸
¸¸?ˇ˜˛˘¸
¸(¸?ˇ˜˛˘¸
¸¸?ˇ??˜˛˘¸
¸(¸?ˇ?‡˜˛˘¸
¸¸?ˇ˜˛˘¸
¸(¸?ˇ¯˜˛˘¸
¸¸?ˇ˛¯¸˜˛˘¸
¸(¸ˇˇ¯ˇ˜˛˘¸
¸¸ˇˇÄ¯ˇ˜˛˘ ¸
¸(¸ˇˇÄˇ√ˇÄ¯˛˘¸
¸¯
ˇ@ˆ˛˘¸
¸(Ͳ˘¸
¸Í˛˘¸
¸zÍ™æ˛˘¸
¸}ÍU^˛˘¸
¸zÍ™æ˛˘¸
¸xͲ˘¸
‡ˇ¸˙
¸
‡˘¸
‡˘¸
‡?˘¸
‡!˙
¸
‡!˘¸
‡!˙
¸
‡·Ï˘¸
‡ÄL˙
¸
‡@å˘¸
‡!˙
¸
‡˘¸
‡˙
¸
‡˘¸
‡˙

¸
fiˇ¸˘¸
‡˘¸
‡˘¸
‡˛˙
¸
‡Ç˘¸
‡ÉÏ˘¸
‡Ç,˘¸
‡Ç,˘¸
‡Ç,˘¸
‡˛,˘¸
‡ ,˘¸
‡ ,˘¸
‡ ,˘¸
‡?Ï˘¸
‡˘
¸
fiˇ¸˘˚fiˇ¸˘œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœ2    ˘‡
‡
¡¿ƒ˝8pp  a   ˛
!˛ .Å" ¸Dàà      ˛

˚ 31Å$ <âsÄÑ
    P<#,8∏<8π„ãÇ"cã
sᯇ,8∞Ò31Å  DâÑ@Pë"!2D¿"D¬$L"!ÅÑHà    2D…"31Ò    Ò„‡@@ÑDâ@¯àë"!"DÄ"DÇ$H
T!ÅH"<â 31ÅÄÄDâ¿  àë"!"|Ä"DÇ'»
T!Å«!"Dâ31Å

Dâ @@
¸ë"!
"@Ä"DÇ$à!ÅàA"Dâ31ÅDô@@ÄÄ
ì"!"DÄ"DÇ$Hà!ÅHàÅ"Dâ"31˘‡
‡Á‡<iĸ
˘¯
<!"8Ä<8Å„àà »Åᯇ"<àÒ
˜˜Â
˜D˜Â˜8⁄œœœ ¯⁄
GăÄ<
Ä⁄
D@ƒÄBÄ⁄
Ñ#ħq¿@8pá⁄
Ñ$@§àÄ@DààÑ⁄
Ñ$@îàÄ<@xàÑ⁄
Ñ$@îàÄ@àèÑ⁄
Ñ$@åàÄ@àà⁄DD@åàÄBD˛à⁄
GÉÄÑp`<8xá⁄ ¯⁄œœœœœœœœœœœœœœœœœœœœœœœ–
œœœ>B Ä◊ ˛
1Ä◊ <«q`*é,8x‚‡‹ DBâê$ë2Dâ€<DBâ è"<†DBâ ë"DâÚ€ DBâ ë"D†DBâ ë"Dâ€><Aàq è"<x‚€˜⁄˜à⁄˜p€
–
œœœ)1˛@ Ä @@˝ <¸ǯ&1˛@1Ä@@˝˛B˘Ä¯.*)D@Eáx‡*éb«XEé\„«Ña√é0‚¿@8≥b%å8qΔX˙.*)"D@FHàâ$ë"#""dFD"a$D"$D @DÃôí&DDàÇ"d˙.*%"*ÄDHâ è "" DDD"@Ú$D"ƒ @Dàë$D@xÇ"D˙.*%>*ÄDGâ ë ""DDD>A$D"D @Dàë$D@àÇ"D˙.*# D@àâ ë ""DDD A$D"D @Dàë$D@àÇ"D˙.
#"DHàâ ë˛""DDD"A$D"$D BDàëdDDàÇ"D˙.*!DGx‡ è"!éD@DC@Û«Ñ!√√‚ <8àë§D8xbD˙@˝
ÁÄ˝
Áœœœœœ`<˝ › B˝ ›
<!¿@8≥"p‚‡Xpfl
"" @DÃë"!dàfl"" @Dàë"!DÄfl"#‡@Dàë"!ÚDÄfl?ë""@Dàë"!DÄfl ë"" BDàë&!Dàfl û<!¿<8àû‚Dp@‡ ¸˛‹ ¸˛‹ˇM™@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-57
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHw4gHw"hH]

ˇ·ˇ‚7^    °dONLNd\äg∫(däFigure 2-23°dONLNd\Ãg“)B
A0°dONLNd\“g
å)/ publisher and subscriber with clipped graphics

H4H ä

ˇ·ˇ‚7^°dONLNd@
ˇä
$(    äBitmapped Graphics Bordersˇˇˇˇˇˇ‘@(    
2
°dONLNd\äï(äCr\°dONLNd^ï…)eating a bors°dONLNdj…„)4der arê°dONLNdp„)Bound bitmapped graphics in applications is similar to doing so in °dONLNd≤ ä,
T()ä-object-oriented drawing applications. The borW@°dONLNdfl 
T,
ì) der appears arÒ¿°dONLNdÌ 
ì,
Ï)?ound the selected arŒÄ°dONLNd

 
Ï,)Yea. The °dONLNd
    -ä9π(6äuser can cr˜@°dONLNd
-π9
Â)/Beate overlapping publishers and subscribers in bitmapped graphics °dONLNd
V:äFƒ(Cäapplications. F@°dONLNd
d:≈FÀ);
Y¿°dONLNd
e:ÀF
)ou need to pr¿°dONLNd
r:
F
o);ovide a Show/Hide BorŒÄ°dONLNd
á:
oF)i$ders command to allow users to turn °dONLNd
´GäS¶(Päall bor퇰dONLNd
≤G¶SÂ)ders on and of˜†°dONLNd
¿GÂSÍ)?f.

wà
ÁòÄ8
øHH



\*4

ˇˇˇˇˇˇ

øzà
⁄
ÛÊˇ˛Ù
ÛÊÙ
ÛÊÙ
ÛÊÙÛ˚ˇøˇˇˇˇfl˝˚ÙÛIJxÄ¿˚DÙ"Û
˙øˇˇƒ˛¿˛ˇˇ–E˚Ù!ÛIJ
¿Ÿ˛„    8Ãœå«˝DÙ!Û˙øˇˇ¿‚˛32d˝Ã    ôôúˇˇ–E˚Ù!ÛIJ‹¡Û330påÃÃŒôò˝DÙ"Û˙øˇˇÃ√˛308Ãëüòˇˇfl≈˚Ù!ÛIJ
Ã√˛3    0ÃÃ√ôò˝Ù"Û˙øˇˇÃ√˛32LÃÃ…ôòòˇˇ–˚Ù!ÛIJx¡Û„38œå«è˝ÙÛ˚ˇøˇˇ˛Ùˇˇfl˝˚ÙÛ˘ÔÙ
ÛÊÙ
ÛÊÙÛ¡ÙÛË
ÙÛË
ÙÛË
ÙÛË
ÉÙÛË
CÙÛË
#ÙÛ
*Ò™†˙
 ÙÛUP˙
x{ÙÛ
*Ò™†˙
CÙÛ
PÒP˙
CÙÛ
 ¯<˚ ˙
CÙÛ
P¯
|¸P˙
√ÙÛ
 ˚ˇÁˇ
IJ ˙
ÙÛ
P˚ˇÃ˝IJP˙
ÙÛ
 ¸
ˇ‡
øÌÉIJ ˙
ˇˇÙÛ
P¸
¸˝ÔÁIJP˙
ˇˇÙÛ
 ¸fl«Ô;˝ ˝¿
ÄÙÛ
P¸¯>"˝P˛
¿
ÄÙ Û
 ˝¯@<"˝ ˛
¿
ÄÙ Û
P˝ˇÄ˛˝P˛@
ÄÙ Û
 ˝Ä¿Ù˝ ˛¿
ÄÙ Û
P˝˝P˛@
ÄÙ Û
 ˝¯P˝ ˛‡
ÄÙ!Û
P˝IJ‡P˛`
ÄÙ!Û
 ˛¿>˝?∞ ˛
∞
ÄÙ"Û
P˛Ä¿

ˇÄÿP˛P
ÄÙ"Û
 ˛Ä
$Æ ˛
∏
ÄÙ"Û
P˛Ä3¸◊‡P˛X
ÄÙ"Û
 ˛
¸˛<7‡j∏ ˛
®
ÄÙ"Û
P˛
˛
`?˛U\P˛\
ÄÙ"Û
 ˛
‡0˛
@>˛jØ ˛Æ
ˇˇÙ"ÛP¿ ˛
¿<˛uUÄP˛W¿
Ù"Û ¿Ä¡¸˛*™Ä ˛™ˇ¯
DGÙ"ÛPҲ5U¿P˛UUX
Ù!Û ˝Ҳ*™‡ ˛™™∞
DGÙ"ÛP
¿˛uUpP¯UUp
Ù"Û $
ˇ˛j™∏ ∏™´¿
DGÙ"ÛP<Ä4UU\PupU_
Ù!Û 0˝j™Ø ͆ø
DGÙ!ÛP0˝>Ä6uUUˇ’`u‡
Ù!Û p˝8>*™™⁄™¿ÎÄ
DGÙ!ÛP¿˝ ?&5UU%U∏◊˛
Ù"Û ‡d?„∂*™™⁄™¯™˛
DGÙ"ÛP‡
ˇˇ¡˛5UU%US˝V˛
Ù Û     
†‡¸*™™⁄™æ™¨˛
DGÙÛP
¿‹˚5UU%˛U\˛
ÙÛ 
ĸ>˚™™⁄˛™®˛
DGÙÛP
Ä<0˚UU%˛UX˛
ÙÛ Ä¿˛p˚
™™⁄˛™∞˛
DGÙÛP¿æ¿˚UU%˛Up˛
ÙÛ ġ?Ä˚™™⁄˛™†˛
DGÙÛPÄt˛˙UU%˛U`˛
ÙÛ á∑¯˙™™⁄˛™¿˛
DGÙÛPÖ˘UU%˛UIJ
ÙÛ ˘
™™⁄™™´˝
DGÙÛP
Ä˙UU%UUV˝
ÙÛ Ä˙
™™⁄™™Æ˝
DGÙÛPóá¯˙]U%UU\˝
ÙÛ ›á˙ø™⁄™™∞˝
DGÙÛPˇˆ?˙Qı%UU‡˝
ÙÛ C¯˙∞:˙™´Ä˝
DGÙÛPmá¿˙P%UW¸
ÙÛ Œú˙∞Ú™˛¸
DGÙÛPûòÿ˙P›W¿¸
ÙÛ ú8˙
∞/˛˚
DGÙÛP∏‡˜
–P˙
ÙÛ ÒĈ∞ ˙
DGÙÛP·ıP˙
ÙÛ ¡ı` ˙
DGÙÛP√ÛP˙
ÙÛ éÛ ˙
DGÙÛPåÛP˙
ÙÛ 3Û ˙
DGÙÛPnˆP˙
ÙÛ ^0¯| ˙
DGÙÛPTp¯Ó~P˙
ÙÛ –‡¯œ> ˙
DGÙÛQ¸¿¯ˇúP˙
ÙÛ!1įˇÃ ˙
DGÙÛQuIJ
¸?˛¿P˙
ÙÛ!q˝œ‡˛˛¿ ˙
DGÙÛSc˝ˇ¿˛¸ˇÄP˙
ÙÛ&÷˝?ˇÄ˛˝ˇ∏ ˙
DGÙÛTΔ˝;ˇÄêˇˇ∏P˙
ÙÛ%Ã˛ˇÄòˇˇ∏ ˙
DGÙÛTfl¸˛ˇˇ‡ôˇˇ∏P˙
ÙÛ&^˛ˇˇ‡πˇ˛˛ ˙
DGÙÛS_ˆ˛ˇˇ‡˝ˇ˛˛P˙
ÙÛ!=ö˛ˇˇ‡ˇˇ˛x ˙
DGÙÛ
Q˚
ˇˇ˝ˇ~P˙
ÙÛ
!ó˘
ˇˇ¸˝ˇ˛ ˙
DGÙÛ
Qèªˇˇ¯
˝ˇ¸P˙
ÙÛ
!˙ˇˇ¯
˝ˇ¸ ˙
DGÙÛ
Q˜Úˇˇ¯
˝ˇ¯P˙
ÙÛ
 |Δˇˇ˝É˝ˇ‡ ˙
DGÙÛ
Púˇˇ˝±˛ˇ˛˛P˙
ÙÛ 0ò˛ˇ˚˛ˇ¯˛ ˙
DGÙÛP?˛ˇ˚˛ˇ¯˛P˙
ÙÛ Ä˛ˇ˚˛ˇ¯˛ ˙
DGÙÛ
P˝˙ˇ¯˛P˙
ÙÛ
 ˝˙ˇ˛ ˙
DGÙÛ
P˝˙ˇ˛P˙
ÙÛ
*Ò™†˙
DGÙÛUP˙
ÙÛ
*Ò™†˙
DGÙÛ¸˙ˇˆ
ÙÛ¸˙ˇˆ
DGÙÛ¸˙ˇˆ
ÙÛ¸˙ˇˆ
DGÙÛ¸˙ˇˆ
ÙÛ¸
˙ˇˆ
DGÙÛ˚ˇˇ˛ˇ˘ˇˆ
ÙÛ˚ˇˇ„ÒˇÒˇˆ
DGÙÛ˚ˇˇ‡
ˇÒˇˆ
ÙÛ˚ˇˇ‡ˇ‡ˇˆ
DGÙÛ˚ˇˇ‡ˇˇˆ
ÙÛ˚ˇ‡ˇ‡ˇˆ
DGÙÛ˚ˇ‡ˇ‡ˇˆ
ÙÛ˚ˇ‡ˇ‡ˇ‡ˆ
DGÙÛ˚ˇ‡ˇ‡ˇ‡ˆ
ÙÛ˚ˇ‡‡‡ˆ
DGÙÛ˚ˇ‡?‡¿ˆ
ÙÛ˚ˇ‡?‡?‡ˆ
DGÙÛ˚ˇ‡‡ˆ
ÙÛ˚ˇ¸¯ˆ
DGÙÛ˚?ˇ˛˛ˆ
ÙÛ˚?ˇˇ˛ˆ
ˇˇÙÛ˚ˇˇˇáˇˆ
ÙÛ˜˛Äı
ÙÛË
√ÙÛË
CÙÛË
CÙÛË
CÙÛË
x{ÙÛË
 ÙÛË
#ÙÛË
CÙÛË
ÉÙÛË
ÙÛË
ÙÛË
ÙÛ¡ÙÛˇ˘DÄ
ÙÛDDEÄÅÙÛ    DÄ¡?ÉÙÛ(DDEÄ° ÉÙÛOå    Dèë ˚ÙÛÄåDDEà     ãÙÛå    Dà ãÙÛåDDEà ãÙÛÄå    Dà    ?ãÙÛOåDDEèëÙÛ(    DÄ°ÙÛDDEÄ¡ÙÛ    DÄÅ˚ÙÛˇ¸DDEÄ
ÙÛ¡ÙÛ¡Ù………………………Û‰ˇı
ÛÄÂı
ÛÄÂı
ÛÄÂıÛø˜ˇˇ˛Ò
˛ˇ˛ˇÔÿı ÛÄ@˛¿p
ÄÄ˚Ç ı#Û
ø@ˇˇ˛ ˛»
Ä
Ä
˛ˇ˛Ç/ÿı"ÛÄ@˛œ·¿¡ô·ΔŸÒ∞˝Ç ı#Ûø@ˇˇ˛˛ô
ì ·ôôì'ôô¡˛ˇ˛Ç/ÿı"ÛÄ@˛Ê˛ô
ÉÄqôô√ôôÄ˝Ç ı#Ûø@ˇˇ˛f˛ô
Å¿9ôò„ô˘Å˛ˇ˛˛/ÿı"ÛÄ@˛f˛ô
ćôòsôÅÄ˝Ä ı#Ûø@ˇˇ˛f˛ô
í`˛ô3&ôâÅ˛ˇ˛Ä/ÿı"ÛÄ@˛Δüò·¿p˘·ΔÒÄ˝Ä ıÛø˜ˇˇ˛˛ı
˛ˇ˛ˇÔÿıÛĢÓı
ÛÄÂı
ÛÄÂıÛ‰ˇ¯ıÛÄÁıÛÄÁıÛÄÁıÛÄÁ$ıÛÄÁBıÛÄÁÅıÛÄÁ    òıÛÄÁ√ÿıÛÄÁBıÛÄÁBıÛÄÁBıÛÄÁ~ıÛÄÁıÛÄÁıÛÄÁˇ¯ıÛÄÁˇ¯ıÛÄÁ8ıÛÄÁ8ıÛÄÁ8ıÛÄÁ8ıÛÄÁ8ıÛÄÁ8ıÛÄ˝w˝8ıÛÄ˝›˝8ıÛÄ˝w˝8ıÛÄ˝Ò˝8ıÛÄ˝Ò˝8ıÛÄ˝¯

‡¸˝8ıÛÄ˝¯‡`˝˝8ıÛÄ˝˙3ˇˇ?¯˛˝8ıÛÄ˝˙ˇ˛`7˲˝ˇ¯ıÛÄ˝˚ˇˇl˛˝àòıÛÄ˝˚‡?Ô<˛˝
"8ıÛÄ˝¸ˇÄ?yÿ˛˝àòıÛÄ˝¸¿0!Ò˛˝
"8ıÛÄ˝¸'¿@
·˛˝àòıÛÄ˝¸ˇÄg¸ˇ˛˝
"8ıÛÄ˝¸¸~†p˛˝àòıÛÄ˝¸‡`p˛˝
"8ı ÛÄ˝˝¿ć8˛˝àòıÛÄ˝˝Ä˝8¿˝
"8ı ÛÄ˝˝>
˛
ˇÄÄ˝àòı ÛÄ˝˝
|˛¸¿˝
"8ı ÛÄ˝˝
p˛0     p˝àòı ÛÄ˝˝
˛aü‡ø˝
"8ı!ÛÄ˝˛‡
·øU¿˝àòı!ÛÄ˝˛ÄÄ
¯™‡˝
"8ı!ÛÄ˝˛
Ä
Ux˝àòı!ÛÄ˝˛

˛
‡™¨˝
"8ı!ÛÄ˝˛
>˛>‡
UT˝àòı!ÛÄ˝˛¯ <˛
™Æ˝
"8ı ÛÄ˝˛˝
<˛
UW˝àòı!ÛÄ˝˛ x˛™´á˝
"8ı!ÛÄ˝˛‡
 ‡?ˇUU≈˝àòı!ÛÄ˝
‡
† ™™Á˝
"8ı ÛÄ˝
Ä˝0 UUu˝àòı!ÛÄ˝
IJ    
Ù
∞™™ß˝
"8ı ÛÄ˝IJ
¿
˛U˝àòı ÛÄ˝˝    

˘0
™™ß˝
"8ı ÛÄ˝Ä!ˇ∞
˛U˝àòı!ÛĽġ˛
™™ß˝
"8ıÛÄ˝¿?¸
˛U˝àòıÛÄ˝‡x¸
™™ß˝
"8ıÛÄ˝Á‡
˚’UU˝àòıÛÄ˝Ň
Ä˚͙߽
"8ıÛÄ˝Ä˚˛U˝àòıÛÄ˝˙j™ß˝
"8ıÛÄ˝4˘¸˙5UU˝àòıÛÄ˝4ß˙*™ß˝
"8ıÛÄ˝0t=ø¿˙5UU˝àòıÛÄ˝pl(˘j™ß˝
"8ıÛÄ˝`®(˘˛U˝àòıÛÄ˝`®(˘j™ß˝
"8ıÛÄ˝‡h(˘˛U˝àòıÛÄ˝¿,º?¿˙jÍß˝
"8ıÛÄ˝Ä.Ï8@˙5˝U˝àòıÛÄ˝Ä7ˇ±¯˙*èß˝
"8ıÛÄ˝Ç¿ÿ˙5Å’˝àòıÛÄ˝l>s¯˙:Äw˝
"8ıÛÄ˝t‡0`˙Ä˝àòıÛÄ˝Ù¿¿˙Ä˝
"8ıÛÄ˝ÁÄ
¿˙Ä˝àòıÛÄ˝«ˆÄ˝
"8ıÛÄ˝åˆÄ˝àòıÛÄ˝'ˆÄ˝
"8ıÛÄ˝&ˆ˝àòıÛÄ˝ŒÙ˝
"8ıÛÄ˝åpÙ˝àòıÛÄ˝ú`Ù˝
"8ıÛÄ˝
ò¿Ù˝àòıÛÄ˝pĈ@˝
"8ıÛÄ˝Òį@s‡˝àòıÛÄ˝£Ä¯ˇs˝
"8ıÛÄ˝á˜˛y˝àòıÛÄ˝ʘˇ¸‡˝
"8ıÛÄ˝    å˜ˇ˛`˝àòıÛÄ˝¨˝˝
ˇˆ˝
"8ı ÛÄ˝à˝
>˛ˇˆ˝àòı ÛÄ˝˝
˛˛Á¸˝
"8ı!ÛÄ˝6∞˛
ˇ¸˛Ô˝¿˝àòı!ÛÄ˝&0˛
fl¸᡽¿˝
"8ı!ÛÄ˝.gġ¸<«ˇ˝¿˝àòı!ÛÄ˝&ˇ‡ˇˇ¸œˇ˝¿˝
"8ı!ÛÄ˝2 ˇˇ˝œˇ˝àòı!ÛÄ˝ˇ∞ˇˇˇÔˇ˝
"8ı!ÛÄ˝
    Ï–ˇˇ˛ˇÛ¿˝àòı!ÛÄ˝
flÿˇˇÄ˛ˇ˚˝
"8ı ÛÄ˝
ø»ˇˇ‡˝ˇ˝àòı ÛÄ˝
}ÿˇˇ¿˝ˇ‡˝
"8ı ÛÄ˝
ø–?ˇˇ¿˝ˇ‡˝àòı ÛÄ˝
øêˇˇ¿˝ˇ¿˝
"8ı ÛÄ˝
Ê0?ˇˇÏ˝ˇ˝àòı!ÛÄ˝
¸‡?ˇˇÌè˛ˇ˝
"8ı!ÛÄ˝
Ñ¿˛ˇfl˛ˇ¿˝àòı!ÛÄ˝
ˇÄ?˛ˇfl˛ˇ¿˝
"8ı!ÛÄ˝˛˛ˇfl˛ˇ¿˝àòıÛÄ˝¸˙ˇ¿˝
"8ıÛÄ˝¸˙ˇÄ˝àòıÛÄ˝¸?˙ˇÄ˝
"8ıÛÄ˝Ò˝àòıÛÄ˝w˝
"8ıÛÄ˝›˝àòıÛÄ˝w˝
"8ıÛÄÁàòıÛÄÁ
"8ıÛÄÁàòıÛÄÁˇ¯ıÛÄÁıÛÄÁıÛÄÁ~ıÛÄÁBıÛÄÁBıÛÄÁBıÛÄÁ√ÿıÛÄÁ    òıÛÄÁÅıÛÄÁBıÛÄÁ$ıÛÄÁıÛÄÁıÛÄÁıÛ‰ˇ¯ıÛÄ
ˇˇÏ"$ıÛÅ
Ä
ÏàåıÛÉ
Ä
Ï"$    ¸ıÛÖ
Ä
Ïàå    ıÛâÒÄ
Ï"$|âÿıÛêÄ
Ïàå@IXıÛ†Ä
Ï"$@)XıÛ†Ä
Ïàå@)XıÛêÄ
Ï"$@I¸XıÛâÒÄ
Ïàå|à@XıÛÖ
Ä
Ï"$@XıÛÉ
Ä
Ïàå@XıÛÅ
Ä
Ï"$ÿıÛÄ
ˇˇÏàåıÛ‰ˇ¯ı
Û¡¯ı…………………………………………………………………………………………………………………………………………………………………………Ù

¿ÿ8    >xxq¯> ˛ è¿0Ä˝  ˛Ä0IJ

5 DÑà ˝ @Ä˝ ˛ ˝Ä˛˛
˛97 BÄ
  a‰Kú A(àûá\,<<8qv<8∏"&8∞è<ó8Òc97 BÄ` "$L"@C(Hëàô"`2Dë"DâÇ"D¿""»àë"DòDâë"97<B|x¯<"$H"á¿ÄÄDHëà"@"D"@Å"DÄBààë"Dê<â 97 B  "$H>

@DHëá>@"D"8Å"|ÄBààë>DêDâ97 B@ "$H @˛HëÄë @"Dë"Å"@ÄÇààë DêDâ97 DÑÅ "$»"‡ÄÇIëàë"@"Dì"Dâ"DÄÇààë"DêDâ"97>xx
¯‡ !„H«ÇÜûá@"<<8q<8ÄÇàè<ê<Ò˜ ˘Ë
˛ÄIJ¯
 ˘ËÄIJ¯

¿€˚…………… ¯‘
GăÄ<
Ä‘
D@ƒÄBÄ‘
Ñ#ħq¿@8pá‘
Ñ$@§àÄ@DààÑ‘
Ñ$@îàÄ<@xàÑ‘
Ñ$@îàÄ@àèÑ‘
Ñ$@åàÄ@àà‘DD@åàÄBD˛à‘
GÉÄÑp`<8xá‘ ¯‘………………………………………………………………………
¯ Ç–
Ä˛Δ–ÄÛa≈Ä™8∞·„ãÄ÷Å"&@íD…$L’Ò"$@Ç<àÚ$H’Å"$@ÇDâ'»’Å"$@ÇDâ$’Å"$@ÇDâ$H’¯Ò!ƒ@Ç<àÒ„à’˜ ‘¯
 ‘¯

¿‘…………)ƒ
  ÇÄ

˝0Ä@¸Ú&ƒ
˛ Δ˛

˝
˙Ò.*§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`Ù.*§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âêÙ.*îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚âÙ.*
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"âÙ.*åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"âÙ.
åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"âÙ.*ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àqÙÒ
¸
·Ò¸
·……………
Ä˝Ä◊Ä
˝Ä◊(xá
‚Ãxâ√ãÄa¿Ÿ(DààÅ
2DàÑLí ⁄
DDààÅ
"DàÑHÿDDàèÅ
"Dàá»ÿ˛Dàà

"DàÑÿÇDààÅ    "DòÑH ŸÇxá‚"xhcà¿Ÿ@ĸ@˛
Ÿ@ĸ@˛ ÷ˇ3º@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-58    )BUsing the Edition Manager4^*¿
¯

j*p
¯4j*p
¯ klk
¯

ˇ·ˇ‚7^°dONLNd\lj
<(fl&Duplicating Publishers and Subscribersˇˇˇˇˇˇ‘@(f
Ò
2
°dONLNd(pl|
S(yl4Whenever a user clicks a publisher or subscriber borц°dONLNd\p
S|
a)Áderü@°dONLNd_p
a|
Ù)!, you should change the contents °dONLNdÄ}lâ˚(Ül$of the section to a selected state. uÄ°dONLNd§}˚â

)è
Y6°dONLNd•}

â
Ñ)ou should discourage users fr`°dONLNd¬}
Ñâ
·)Éom making multiple °dONLNd’älñ
fl(ìlScopies of a publisher and pasting them in the same or other documents, because the °dONLNd
(ól£
    *$contents of the edition would be difÕ`°dONLNd
Ló
    £
)ù
fi⁄ °dONLNd
Nó
£
u)cult or impossible to pr3`°dONLNd
fó
v£
Û)gedict. Multiple copies of the °dONLNd
ѧl∞
)(≠l*same publisher also contain the same contrKÄ°dONLNd
Ƨ
*∞
})æol block value. See @†°dONLNd
¤
~∞
é)T“Cr†°dONLNd
Ť
é∞
Ù)eating and Registering °dONLNd
‹±lΩ¿(∫la Section” on page °dONLNd
Ô±¡Ω”)U2-74`‡°dONLNd
Û±”Ω
g)" for detailed information on contr;Ä°dONLNd±
gΩ
ê)î
ol blocks.°dONLNd √lœ‚(ÃlWhen a user attempts to cr˝¿°dONLNd:√‚œ
t)v#eate a copy of a publisher that alr√Ä°dONLNd]√
uœ
fl)ìeady exists, you should °dONLNdu–l‹
6(Ÿl.display an alert box such as the one shown in /Ä°dONLNd£–
7‹
O)ÀFigur@°dONLNd®–
O‹
h)e 2-24ü¿°dONLNdÆ–
h‹
j)
.

˛*

¯4ˇ*

¯"ˇ*]

ˇ·ˇ‚7^
    °dONLNd±Ùlˇú(¸lFigure 2-24°dONLNdΩÙÆˇ
B)B&Creating multiple publishers alert box
°dONLNdÂ
íl
û
›(
õlRWhen a user attempts to save a document that contains multiple copies of the same °dONLNd7
ül
´ñ*    publisherÓ‡°dONLNd@
üï
´
d))0, display an alert box such as the one shown in û`°dONLNdp
ü
e
´
})–Figurq °dONLNdu
ü
}
´
ñ)e 2-25†°dONLNd{
ü
ó
´
ô)
.


Õ*
fi
¯4
Œ*
fi
¯"
Œ*]

ˇ·ˇ‚7^
    °dONLNd~
√l
Μ(
ÀlFigure 2-25°dONLNdä
î
Œ
;)B$Saving multiple publishers alert box
°dONLNd∞flrÿ(olIf a user decides to ignorN`°dONLNd fŸr
…)m9e your alert box, your application should still save the °dONLNdsl
Z(|l5document, but you should continue to display this err◊°dONLNd8s
Z
ç)Óor message ØÄ°dONLNdCs
é
∑)4
every time†`°dONLNdMs
∏
‡)*
 the user °dONLNdWÄlå»(âlsaves this document.


j
z
¯òÄ2
F
ÉHH



\*4

ˇˇˇˇˇˇ

F
É
l
‰
h?”ˇ ” ”'”ˇê'”ˇê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê&˝

Ä⁄
ê+&˝
¿˝
˝Ä˛`˝c˛¯¿Ã
Ä˚Δ¸
ê'&˝
¿˝
1Ģc˛ÿ¿
Ä˚Δ¸
ê1&˝
`˝1Ò≥¿cÄx¯xÛ·„`ÃïÃqÒ∞<|<|è
Á√¿˛
ê/&˝
`˝1ôôΔ`f@åÃÃc33Ä˝Ã…ôô¿˝fÄΔf`˛
ê0&˝
0˝1ôôÜ`g|ÃÃc33¯˛Ã·ôôÄ˝fÄΔf`˛
ê1&˝
0˝1ô˘á‡cIJÃc3Û¿˛Ãqô˘Äff~fÄΔg‡˛
ê0&˝
˝1ôÅÜa¿˛Ãc3¿˛Ã9ôÅÄff`fÄΔf˝
ê1&˝
ò˝1ôâÜ d¿˛Ãc3¿˛ÃôôâÄffbfÄΔf ˛
ê1&˝
3Ã˝1òÒÉ¿cÄ|Ãx31„¿|¯ÃqòÒÄ<|<f
èfc¿˛
ê&˝
3ÃÊ`ˆ
ê&˝
cΔÊ`ˆ
ê&˝
cΔ⁄
ê&˝
√√⁄
ê&˝
√√⁄
ê&˛
É¡Ä€
ê$&˛
É¡Ä˛|Δ0˚`ÿÚ
ê$&˛¿¿˛`˛
$˚2`ÿÚ
ê'&˛¿¿˛`|œ1„‡6x¯Ãx€00<c√ÄHÚ
ê'&˛¿`˛`ÃΔ3306åÃÃå„08Fff@êÚ
ê%&˛
Ä`˛xÃΔ330|ÃÃ|√0>fg
ê$&˛
Ä0˛`ÃΔ330¸Ã√0fg„ÄÒ
ê$&˛0˛`ÃΔ330¸Ã√0ff
¿Ò
ê$&˛˛`ÃΔ330¸Ã√0&ff$ÃÒ
ê&&˛
IJ||√1„0x|Ã||¡>c√åÒ
ê&˛0¿Ò0Ï
ê&˛0¿Ú
0Ï
ê&˛`
ÄÚ

‡Ï
ê&˛`€
ê&˛¿€
ê&˛˝ˇ€
ê&˛ˇˇ˛€
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê%&˜0p1IJ`¸

å˚Ä¿¸
ê!&˜0¿1į

å˚¿¸
ê,&˜&1‡yÒ≥¿cġáçûœáèÄx¯xÃœå«èÒ
ê+&˜0¿1ôôΔ`f@ÃÃŒ3
å»Ã¿˛Ã˝ÃôôúÅò
ê,&˜0¿1ôôÜ`g˛Ã3
å«Ã¿˛ÃåÃÃŒôòĢò
ê,&˜0¿1ô˘á‡cIJÃ?
åÃÿÃøÃëüòÅôò
ê,&˜0¿1ôÅÜa¿˛Ã0
åÃÿÃÿÃÃ√ôòÅôò
ê,&˜0¿1ôâÜ d¿˛Ã1
åÃÿÃÃÃÃ…ôòòÅôò
ê,&˜&0¿òÒÉ¿cÄëåëÿxÃxœå«è
è˘ò
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê'&˜|Δ0
å¯å`˝0¸Δ¸
ê'&˜`˛    
å¿˝0¸Δ¸
ê*&˜`|œ1„‡œáÄ¿˘ûc«¬8<|x‡6x¯O¸
ê*&˜`ÃΔ330
åÿ¡ôåffddôôåff1ê#8ÃÃܸ
ê*&˜xÃΔ330
åÿÒôåff`pôåff1¿0Ãø
ê*&˜`ÃΔ330
圿¡ôåff`8ôå~f0‡30¸Ã¸
ê*&˜`ÃΔ330
åáôåff`ôå`f0p30¿Ã¸
ê*&˜`ÃΔ˛3
åÃ@¡ôåff`Lôôåbf1030ƒÃ¸
ê*&˜||√1„3ëį˘ÜcΔ`8Ü<f‡0xø
ê&Ú
‰
ê&Ú‰
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê&ÙÄ¿¿Á
ê&Ù¿¿Á
ê&˜    |l˘é<x¯«ÄË
ê&˜
fq˛ôåÃÿË
ê&˜    faôôò|ÃÿË
ê&˜    fa˘ôòÃÃœ¿Ë
ê&˜faÅôò˛ÃÁ
ê&˜faâôô˛ÃLË
ê&˜    |`˘é|¯«åË
ê&˜`fl
ê&˜`fl
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê&›˚ˇ¯
ê&›˚ˇ˛
ê&›˘ˇ
ê&fi

˚Ä
ê&fi

«˚ˇ„Ä
ê&fi
ÿ˚¿
ê&fi
ê˚    ¿
ê&fi
†˚¿
ê&fi
†˚¿
ê&fi†<c¿
ê&fi†ff¿
ê&fi†fl¿
ê&fi†fx¿
ê&fi†fp¿
ê&fi†fx¿
ê&fi†fl¿
ê&fi†ff¿
ê&fi†<c¿
ê&fi
†˚¿
ê&fi
†˚¿
ê&fi
†˚¿
ê&fi
ê˚    ¿
ê&fi
ÿ˚¿
ê&fi

«˚ˇ„Ä
ê&fi

˚Ä
ê&›˘ˇ
ê&›˚ˇ˛
ê&›˚ˇ¯
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê    &‘
ê'”ˇê'”ˇê ” ”?”ˇˇœœœœœœ—
ˇœœ—
ˇ—
ˇœœœœœœœœœœœœœœœœœœœ—

—
Ä—
Ä—
Ä—
Ä—
Ä—
œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœœ—
—
ú—
ò—
ò—
—
ò—
œœœœœœœ/    |‡à˝    p‡
‡@˝    a¿˝
IJ.@à

0¸à
0¸    !@˝
į31@Ñ
PyÁ
PÁ8≈áÅf"#åxCÄÒ¬0‚√ãúÑ8ªÄ‚,Ã31@Ñ
êâÄêëFHÅô"!DD@â"$L"DD¡â,Ã31xѯÒ!âÄ!èDHÅ"!DD@â"$H ƒDÅâ\Ã31@ÑBâÄ BëDHÅ"!DG¿â"‚'»D|ÅâÄÃ31@Ñɯâ@ɯDHÅ"!DDâ"$D@ÅâDÃ31@à

â2ÄÄ
ëDHÅ&!DD@â2"$H"DDÅâ8Ã31|x“
¯
‚DGÅ ƒxCÄ”¬‚#àƒ8Ä¿‚ ˜ÛÄ˝@ÄÒ˜àÙ
Ä˝@ÄÒ
˜pÙËœœœœœœœœœœœœœœœœœœœœœœ
¯ Ç÷
IJΔ÷ÄÛa≈Ä™8∞·„ãÄfi
ˇÅ"&@íD…$L›
ˇÒ"$@Ç<àÚ$H›
ˇÅ"$@ÇDâ'»€Å"$@ÇDâ$›
ˇÅ"$@ÇDâ$H€¯Ò!ƒ@Ç<àÒ„à€˜ ⁄¯
 ⁄¯

¿⁄œœœœ)ƒ
  ÇÄ

˝0Ä@¸¯&ƒ
˛ Δ˛

˝
˙˜.*§q
a„Ä™8qã8q`
8qsèá8√ã
‚ÃYàñ0·«q`˙.*§â
""$@íDàåàDâê
âÑHëàëDLÅ
2fHô"âê˙.*îà™
 "$@Ç<ÄààDÅ
â»ëàDHÅ
"DHë
‚â˙.*
"'¿ÇDÄààDq
˘HëàDHÅ
"DHë"â˙.*åÄD
"$ÇDÄààD    
ÅHëàDHÅ
"DHë"â˙.
åàD
""$@ÇD˛àDâ
âHëàëDHÅ    "DIë"â˙.*ÑpD
!„ÄÇ<pàÜ8q
qœáCàÄ‚"DFë··àq˙Ò
¸
È
ˇÒ¸
Á—
ˇ—
ˇ—
ˇœœ
Ä˝Ä›Ä
˝Ä›(xá
‚Ãxâ√ãÄa¿fl(DààÅ
2DàÑLí flDDààÅ
"DàÑHfiDDàèÅ
"Dàá»fi˛Dàà

"Dàч
ˇÇDààÅ    "DòÑH ·
ˇÇxá‚"xhcà¿fl@ĸ@˛
fl@ĸ@˛ fi
ˇ


›hN
¯òÄ2
F
ÉHH



\*4

ˇˇˇˇˇˇ

F
É
‡k¥
g“ˇ¿Ä”@Ä”@    ü‘ˇ˛@    ü‘ˇ˛@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@#ò˝¸
£0¸¸
a@˛`ı@#ò˝¸
£0¸¸
a@˛`˛ı@*ò˝¸£1·„`x¯|û>6Ò@8x¯Ò„>ôò¯@+ò˝
Ä˝323IJÃ˛38`dÃÃb332ôò¯@+ò˝
Ä˝
„1Û˛Ã˛30``ÃÃaÛ38ôò¯@*ò˝
0¿¸√Û3¸ÃÃ?330``ÃÃc33ôò¯@*ò˝
0¿¸√3¿ÃÃ0330``ÃÃc33ôò¯@*ò˝
``¸√3ƒÃÃ1330`dÃÃc33&ëò¯@*ò˝
f`¸¡·ÛxÃ|>008xÃ1Û3
ü‡¯@ò˝
œ0Û0È@ò˝
œ0Û0È@ò˛
è⁄@ò˛
è⁄@ò˛⁄@ò˛⁄@ò˛⁄@/ò˛˛

Åò˝¿1Ä1åÉ˚
`@/ò˛˛
ò
ÅÄ˝¿1Ä
Ä    ˚
Ä`@3ò˛˛'
ôôÒò„·„g
„¿y3Ãx¯É>36Ã· @2ò˛
Ä
˝ô"ì33åÄΔ`1ôò31åÃÃÉ#33#8Ãôôí@@3ò˛
Ä
Ò˛ô"√33Δ`1ôò31åÃÃ330Ãôô¿@1ò˛¿
Åôôò„3ÛΔ`1ô¯31åÃø30Ãôô¯‡@1ò˛¿
Åôôòs3ÄΔ`1ôÄ31åÃø30Ã
ôôÄp@1ò˛``
Å˛ô33    ÄΔ`1ôà31åÃø30à    ôôâ0@3ò˛-``
ĢÒò„1„c¿ò0ÃxÃ30|ò‡@ò˛¿0„˙@ò˛¿0„å˙@ò
Ä„x˙@ò
Ä€@ò˛€@ò˛ˇ¸€@ò
˛ˇ¯€@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@%ò˜¡¿Δ˛

ĸ
0˚>03`¸@ ò˜√Δ˜
0˚300`¸@,ò˜&«ÅÁ√Δœ
é˛6x>>
„·‡33>3|<l<«¿@+ò˜√ΔfgÅô338Ã3#3330˝32ffpff`@,ò˜√ΔffÅú330Ã33330>˛38ff`fÊ`@,ò˜√ΔgÊÅé330¸˛3330˛3f~`ff`@,ò˜√Δf
á330¿˛3330˛3f``ff`@,ò˜√Δf&Åì330ƒ˛3330˛3&fb`ff`@,ò˜&√fcΔ
é30x33
„1‡0>3f<`<Ê`@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@)ò¯
3¿0‡f1Ä˝0¿˝
¸@)ò¯
Ä0˛    0`0˝0¿˝
¸@+ò¯
ÅÛ<«èÄ>Êyè‡<|xÒÒ„ÄxŸ„·<¸@+ò¯
É3Ãÿ33f1ôôëê2ff1ôòΔ@å„32¸@+ò¯
„3Ãÿ33Δf1ôôÅ¿0ff1ôò«|√30¸@+ò¯
É3Ãÿ3?f1ôôć0ff1˘ò√ÄÃ√Û0¸@+ò¯
É3Ãÿ30f1ôôÄp0ff1Åò¡¿Ã√0¸@+ò¯
É3˛Ã31f1ôôÅ02ff1âòƒ¿Ã√0¸@+ò¯
ÒÛ«åÃ3„Êèć<fÒòcÄ|¡„0¸@òÚ‰@òÚ‰@    ò‘@    ò‘@    ò‘@    ò‘@òÙf`Ê@òÙ``Ê@ò¯    
Ò≥√Ê8Ò„„Á@ò¯
ôΔffdb˛3Á@ò¯    
ôÜff`aÛ33Á@ò¯    
ôáÊf`c33?Á@ò¯    
ôÜf`c330Á@ò¯

ôÜ&fdc3310Ë@ò¯

ÒÉ√Ê81Û„0Ë@ò¯

Äfl@ò¯

Äfl@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@ò›˚ˇ‡@òfi
˙ˇ¯@òfi˙ˇ¸@òfi
¿˚@òfi
˚ˇé@òfi
`˚o@òfi
@˚'@òfi
Ä˚@òfi
Ä˚@òfiÄÒå@òfiÄ
ôò@òfiÄ
ô∞@òfiÄ
ô‡@òfiÄ
ô¿@òfiÄ
ô‡@òfiÄ
ô∞@òfiÄ
ôò@òfiÄÒå@òfi
Ä˚@òfi
Ä˚@òfi
Ä˚@òfi
@˚'@òfi
`˚o@òfi
˚ˇé@òfi
¿˚>@òfi˙ˇ¸@òfi
˙ˇ¯@ò›˚ˇ‡@    ò‘@    ò‘@    ò‘@    ò‘@    ò‘@ˇ    ò‘@    ò‘@    ò‘@ˇ    ü‘ˇ˛@ˇ    ü‘ˇ˛@Ä”@Ä”@“ˇ¿ˇœœœœœœœœœœœœœœ—
—
ò—
ò—
ò—
ò—
ò–œœœœœœœœœ—
—
#—
—
3—
3—
3—
œœœœœœœœœœœœœœœœœœœœœ—
—
—
—
2—
8—
—
—
&—
œœœœœœœœ–x–å–|–ÖÖÖ|œœœœœœœœœœ0
<<8¸¯Ä˛    ?@˝    a¿˝
IJ,    "BDÄÄ˝Ä !˙    !@˝
IJ31!@ÑÄÅáë.pÄ!  D≈áÅf"#åxCÄÒ¬0‚√ãúÑ8ªÄ‚ 31!@¯Äàë0àÄ
> "DFHÅô"!DD@â"$L"DD¡â 31!><|àë à

DDHÅ"!DD@â"$H ƒDÅâ@31!Äàë ¯

"(DHÅ"!DG¿â"‚'»D|ÅâÄ31! Äàë Ä

"(DHÅ"!DDâ"$D@Åâ@31"B@ÑÄàì à!!"DHÅ&!DD@â2"$H"DDÅâ 31<<¸xÄáç pÄ?DGÅ ƒxCÄ”¬‚#àƒ8Ä¿‚ ˆÄÙÄ˝@ÄÒ˜
Äı
Ä˝@ÄÒ
˜ÙËœœœœœœœ–
–––––––––––>B Äÿ ˛
1Äÿ <«q`*é,8x‚‡› DBâê$ë2Dâ‹<DBâ è"<â‹ DBâ ë"DâÚ‹ DBâ ë"Dâ‹ DBâ ë"Dâ‹><Aàq è"<x‚‹˜€˜à€˜p€––
œœ)1˛@ Ä @@˝ <¸ǯ&1˛@1Ä@@˝˛B˘Ä¯.*)D@Eáx‡*éb«XEé\„«Ña√é0‚¿@8≥b%å8qΔX˙.*)"D@FHàâ$ë"#""dFD"a$D"$D @DÃôí&DDàÇ"d˙.*%"*ÄDHâ è "" DDD"@Ú$D"ƒ @Dàë$D@xÇ"D˙.*%>*ÄDGâ ë ""DDD>A$D"D @Dàë$D@àÇ"D˙.*# D@àâ ë ""DDD A$D"D @Dàë$D@àÇ"D˙1
#"DHàâ ë˛""DDD"A$D"$D BDàëdDDàÇ"D¸
ˇ1*!DGx‡ è"!éD@DC@Û«Ñ!√√‚ <8àë§D8xbD¸
ˇ@˝
ÁÄ˝
Á—
ˇœœœœ`<˝ › B˝ ›
<!¿@8≥"p‚‡Xpfl
"" @DÃë"!dàfl"" @Dàë"!DÄfl"#‡@Dàë"!ÚDÄfl?ë""@Dàë"!DÄfl ë"" BDàë&!Dàfl û<!¿<8àû‚Dpfl ¸˛˛@‡ ¸˛‹ˇ:†@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-59
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähë(eä
A∫†°dONLNd
\ëh
â)8 user can modify the contents of any duplicate publisher©@°dONLNd9\
âh)¯", but the contents of the edition °dONLNd[iäu
c(rä2will be whichever publisher was the last to write..°dONLNdé{äá
ø*FWhen a user chooses to copy and paste or duplicate a section, use the ,
Courier°dONLNd‘{
øá
˚(Ñ
ø
HandToHand°dONLNdfi{
˚á
˝)<
 .
°dONLNdflàäîÂ(ëäfunction (described i• °dONLNdÙàÂîÌ)[n ˆÄ°dONLNdˆàÌî
Z)Inside Macintosh: MemoryGÄ°dONLNd
à
[î
^)n
)õ`°dONLNd
à
^î
Õ) to duplicate the section r– °dONLNd
*à
Õî
fl)oecorDÄ°dONLNd
.à
‡î)d and alias .°dONLNd
:ïä°é(ûä
rR`°dONLNd
;ïé°†)ecor$¿°dONLNd
?¶)
d$¿°dONLNd
@ﶰ∫). Set$¿°dONLNd
Eï∫°Œ) the $¿°dONLNd
JÏ)alias$¿°dONLNd
OïÏ°ı) fi$¿°dONLNd
Rïı°
g)    eld of the cloned section r˜ °dONLNd
mï
f°
x)qecor…Ä°dONLNd
qï
x°
è)d to t…Ä°dONLNd
wï
è°
π)he handl…Ä°dONLNd
ï
π°
œ)*e of t…Ä°dONLNd
Öï
ϡ
¸)
he cloned .
°dONLNd
è¢äƆ(´äalias ¿°dONLNd
Ƨ)
r“¿°dONLNd
ñ¢§Æ∂)ecorG °dONLNd
ö¢∑Æ
e)'d and generate a unique section identifi,@°dONLNd
¢
fÆ)Ø'cation number for it. In addition, you °dONLNd
ÈØäª
H(∏ä-should also place the section data, section rü‡°dONLNdØ
Hª
Z)æecor@°dONLNdØ
[ª
î)d, and alias rÔ‡°dONLNd(Ø
ìª
•)8ecord@°dONLNd,Ø
¶ª
‰)d in the scrap..°dONLNd<¡äÕØ( äUse the °dONLNdD¡ØÕ
    )%RegisterSection°dONLNdS¡
    Õ
Z)Z function (describe°dONLNdf¡
ZÕ
m)Qd in °dONLNdk¡
mÕ) “Opening and Closing a Document .
°dONLNdãŒä⁄
(◊äContaining Sections” on page χ°dONLNd®Œ
⁄
!)Ö2-22@¿°dONLNd¨Œ
"⁄
%)
)dONLNd≠Œ
%⁄
6) to rÄ°dONLNd≤Œ
7⁄
’)&egister the cloned section’s section r
¿°dONLNdÿŒ
’⁄
Á)ûecor °dONLNd‹Œ
Á⁄
Ô)d.°dONLNdfl‡äÏë(Èä
A∫†°dONLNd‡‡ëÏÊ) user can select the ≈@°dONLNdı‡ÊÏ
)Ucontents‘†°dONLNd˝‡
Ï
∏)") of a publisher without selecting the bor∞°dONLNd&‡
∏Ï)∞der and copy just °dONLNd8Ìä˘
˝(ˆäWthe data to a new location. In this case, the user has simply copied data (and not the °dONLNdè˙ä
Â*publisher). Do not crÒ`°dONLNd§˙Â

)[
eate a borâ °dONLNdÆ˙


Ø)+&der for this data in the new location.


+H
24
,H
2 
-ä
-

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd÷
ä
+
(
'äModifying a Subscriberˇˇˇˇˇˇ€r(
'
2
°dONLNdÓ
2ä
>
W(
;ä0When the user selects data or clicks the data ar6Ä°dONLNd
2
X
>
§)Œea of a subscriber$°dONLNd0
2
§
>)L, you should highlight °dONLNdG
?ä
KØ(
Hä    the entirh °dONLNdP
?Ø
K
<)%!e contents of the subscriber usin °dONLNdq
?
=
K
S)ég invq@°dONLNdv
?
S
K
Ä)
erse videoù†°dONLNdÄ
?
Ä
K
Ö)-. ?@°dONLNdÇ
?
Ö
K)Although you shouldn’t allow a °dONLNd°
Lä
X
F(
Uä,user to edit the information in a subscriberı`°dONLNdÕ
L
E
X
U)ª, yo˙°dONLNd—
L
U
X
f)u caÒ`°dONLNd’
L
g
X
Î)n allow a user to make global °dONLNdÛ
Yä
e—(
bäadornments to s∏Ä°dONLNd
Y—
e
)Gubscribers. P`°dONLNd
Y

e
;)3In other worW@°dONLNd
Y
;
e
˙)7.ds, users can change the font, size, or other °dONLNdH
fä
rÊ(
oächaracteristics of the G@°dONLNd_
fÁ
r˙)]entirã °dONLNdd
f˙
r˝)
en¿°dONLNde
f˛
r
.) subscriber…@°dONLNdp
f
-
r
7)/. FX`°dONLNds
f
8
r
˙)-or example, a user might select a subscriber °dONLNd†
sä

=(
|ä(within a document and change all text frÄ`°dONLNd»
s
=

¥)≥om plain to bold. However3‡°dONLNd·
s
¥

Ì)w, you should °dONLNdÓ
Ää
å›(
âädiscourage users frO†°dONLNd

Äfi
å
‡)T8om modifying the individual elements contained within a °dONLNd9
çä
ô
j(
ñä2subscriber—for example, by editing a sentence or r⁄`°dONLNdk
ç
j
ô
Á)‡otating an individual graphi@°dONLNdá
ç
Ë
ô
Ù)~c oj°dONLNdä
ç
Ù
ô
)bject.°dONLNdë
üä
´
°(
®ä>Remember that each time a new edition arrives for a subscriber@°dONLNdœ
ü
°
´
÷(
®
°, any modifiT °dONLNd€
ü
÷
´)5cations that °dONLNdË
¨ä
∏—(
µäthe user has intr≠@°dONLNd˘
¨—
∏˝)G    oduced ar‡@°dONLNd
¨˝
∏
W),e overwritten. Globa⁄@°dONLNd
¨
X
∏
ì)[l changes to a£@°dONLNd$
¨
î
∏
¿)<
 subscribe»Ä°dONLNd.
¨
¿
∏
œ),r ar °dONLNd2
¨
–
∏
‡)e m¿°dONLNd5
¨
‡
∏)uch easier °dONLNd@
πä
≈Ù(
¬äfor your application to rn °dONLNdY
πÙ
≈
)j    egenerate* °dONLNdb
π

≈
!)+
.


”H
·4
‘H
·
    °dONLNdd
“ä
›ù(
ڊNote

ˇ·ˇ‚7^
°dONLNdi
flä
Î
«*FAlthough adornments should be global and never partial, you may still °dONLNdØ
Îä
˜
ô*Aneed to give users the ability to select portions of a subscriber,Ä°dONLNd
Î
ô
˜
≠(
Ù
ô, for °dONLNdˆ
˜ä
j(ä1instance, when performing spell checking and searÑ¿°dONLNd'
˜
j
è)‡ch-and-r @°dONLNd/
˜
ê
Æ)&eplace °dONLNd6äª(äoperations.,Zapf Dingbats‚Ä°dONLNdB¿Δ)6
u
°dONLNdEä 
q(ä7If you do allow a user to edit a subscriber section, pr|Ä°dONLNd|
q 
ô)Á    ovide an °dONLNdÜ!ä-
(*äQenable/disable editing option within the subscriber options dialog box using the .°dONLNd◊.ä:
*SectionOptionsExpDialog°dONLNdÓ.
:
d)ä function, describe°dONLNd    
.
d:
p)Pd i°dONLNd    .
p:
w)n °dONLNd    .
w:
˜)“Customizing Dialog Boxes”°dONLNd     .
˜:
˘)Ä
 .
°dONLNd    !;äG
(Däbeginning on the next page.9Ä°dONLNd    <;
G
){ WπÄ°dONLNd    >;
G
√))hen you allow a user to edit a subscriberq¿°dONLNd    g;
√G
¸)≤, you should °dONLNd    tHäTÛ(Qächange the subscriber fr˘‡°dONLNd    åHÛT
å)i$om a selected state to editable data °dONLNd    ∞H
çT
è)ö
.°dONLNd    ≤Zäfê(cä
Bõ¿°dONLNd    ≥Zêf
˚)Tecause a user can modify a publisher just like any other portion of a document, its °dONLNd
gäs
¸(päSsubscriber may change in size as well as content. For example, a user may modify a °dONLNd
ZtäÄ
r*3publisher by adding two additional columns to a spr?¿°dONLNd
çt
sÄ
ú)È    eadsheet.ˇp@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-60    )BUsing the Edition Manager4^*¿
¯

k*r
¯4l*r
¯ mlm
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\lkÌ(glRelocating an Editionˇˇˇˇˇˇ€r(g

2
°dONLNdrl~•({lIn the Finder¿°dONLNd$r§~
:)8", users cannot move an edition acrx`°dONLNdFr
;~
|)óoss volumes. TÄ°dONLNdTr
|~
á)Ao ræ°dONLNdWr
á~
Ÿ)elocate an edition, °dONLNdklã|(àlthe ›`°dONLNdo|ã∞)user must fiE°dONLNd{±ã
})52rst select its publisher and cancel the section (rÊ°dONLNd≠
}ã
∏)Ãemember to r‚°dONLNdπ
∏ã
Ë);
emove the °dONLNd√ålòz(ïlborB °dONLNdΔå{òÊ)der). The user needs to rd`°dONLNdflåÊò
Ÿ)k7epublish and then select a new volume location for the °dONLNd
ôl•ê(¢l    edition. a°dONLNd
ôê•
)$As a convenience for the userw@°dONLNd
<ô
•
N)Å, you should r◊ °dONLNd
Jô
N•
ı)=)etain the selection of all the publisher °dONLNd
s¶l≤
f(Øl<data after the user cancels the section to make it easy to ró °dONLNd
ض
f≤
¿)˙epublish the section.

◊*fi
¯4ÿ*fi
¯ ŸlŸ
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd
Δ»l◊
(”lCustomizing Dialog Boxesˇˇˇˇˇˇ€r(”

2
°dONLNd
‡filÍ
”(ÁlPThe expandable dialog box functions allow you to add items to the bottom of the °dONLNd0Îl˜ä*dialog Ò °dONLNd7Îä˜
Î)Pboxes, apply alternate mapping of events to item hits, apply alternate meanings °dONLNdá¯l
w(

lto ∑‡°dONLNdä¯w

ó)Dthe item hits, and choose the location of the dialog boxes. See the »‡°dONLNdŒ¯
ó

∫(


óchapter °dONLNd÷
l
q(
l
“°dONLNd◊
q
ë)Dialog 톰dONLNdfi
ë
∏) Manager$†°dONLNdÂ
π
æ)(
”$†°dONLNdÊ
æ
À) in fi`°dONLNdÍ
À

I)Inside Macintosh: Macintosh T0‡°dONLNd

I

ç)~oolbox Essentialsı‡°dONLNd

ç

î)D au‡°dONLNd

ï

≥)nd the @`°dONLNd!

¥

◊)chapter °dONLNd)
l
q(
l
“°dONLNd*
q
ì)Standar¥@°dONLNd1
ì
“)"d File Package[@°dONLNd?
”
Â)@” in °dONLNdD
Ê

C)Inside Macintosh: Files€‡°dONLNd[

C

ª)] for additional information.°dONLNdx
$l
0
?(
-l/The expandable versions of these dialog boxes rrÄ°dONLNdß
$
?
0
V)”equirâ¿°dONLNd¨
$
V
0
c)e fi‡ °dONLNd∞
$
c
0
Í)ve additional parameters. Use .°dONLNdŒ
1l
=~(
:lthe ,
Courier°dONLNd“
1~
=¸)NewPublisherExpDialog°dONLNdÁ
1¸
=
ƒ)~- function to expand the publisher dialog box.°dONLNd
Hl
T
Ï(
Ql@err := NewPublisherExpDialog (reply, where, expansionDITLresID, °dONLNd`
V
 
b
Ï+¥"dlgHook, filterProc, yourDataPtr);°dONLNdÉ
nl
zë(
wlUse the °dONLNdã
në
z
)%NewSubscriberExpDialog°dONLNd°
n

z
›)Ñ. function to expand the subscriber dialog box.°dONLNd–
Öl
ë
Ï(
él@err := NewSubscriberExpDialog (reply, where, expansionDITLresID,°dONLNd
ì
 
ü
&+¥
 °dONLNd
ì
&
ü
Ú)"dlgHook, filterProc, yourDataPtr);ˇˇË∫°dONLNd?
´l
∑ê(
¥lUse the ˇˇ∫.Qt°dONLNdG
´ë
∑
)%SectionOptionsExpDialogˇˇË∫Qt°dONLNd^
´

∑
¯)ä2 function to expand the publisher options and the .
°dONLNdê
∏l
ƒ˘(
¡l subscriber options dialog boxes..°dONLNd±
œl
€
Ú*Aerr := SectionOptionsExpDialog (reply, where, expansionDITLresID,°dONLNd˝
›
 
È
&+¥
 °dONLNd˛
›
&
È
,)
 °dONLNdˇ
›
,
È
¯)"dlgHook, filterProc, yourDataPtr);°dONLNd"
ıl
Ä(
˛lThe °dONLNd&
ıÄ
û)reply°dONLNd+
ıû

) parameter is a pointer to a °dONLNdH
ı


Ä)|NewPublisherReplyd@°dONLNdY
ı


Ñ)e, d@°dONLNd[
ı
Ñ

)NewSubscriberReplyHÄ°dONLNdm
ı
Ô

Ù)k, °dONLNdolw(lor °dONLNdrwÈ)SectionOptionsReply°dONLNdÖÈÔ)r rR`°dONLNdáÔ

)ecor$¿°dONLNdã


)d, r˜ °dONLNdè

D)espectively€`°dONLNdö
C
F)4
.ˇˇ˙(°dONLNdúl s(l
Yï°dONLNdùr 
£)Fou can automatically center the dialog box by passing (–1, –1) in the ˇˇÓxI°dONLNd„
§ 
¬(
§whereˇˇ˙(I°dONLNdË
¬ 
Û)
 parameterÖ–°dONLNdÚ
Û 
˜)1. °dONLNdı&l2Ä(/lThe °dONLNd˘&Ä2Ï)expansionDITLresID°dONLNd&Ï2
9)l parameter shoul°dONLNd&
92
i)Md contain 0°dONLNd&&
i2
í)0
 or a vali°dONLNd0&
í2
û))d i°dONLNd3&
û2
«)
tem list (°dONLNd=&
«2
Î))'DITL'°dONLNdC&
Î2
Ò)$) .
°dONLNdE3l?o(<l
rE°dONLNdF3p?à)esourç@°dONLNdK3à?ı)ce ID. This integer is the é@°dONLNdf3ı?¯)m
rS@°dONLNdg3˘?
)esourõÄ°dONLNdl3
?
)ce U`°dONLNdo3
?
5)ID of :Ä°dONLNdu3
6?
F)an it@°dONLNdy3
F?
´)tem list whose items ar@°dONLNdê3
¨?
Ì)fe appended to °dONLNdû@lLÃ(Ilthe end of the standarÏ`°dONLNd¥@ÃL◊)`d ipÄ°dONLNd∑@ÿL
|)'tem list. The dialog items keep their rÙ¿°dONLNdfi@
|L
)§elative positions, but they °dONLNd˙MlYt(VlarE°dONLNd¸MuY∫)    e moved as a grt‡°dONLNdM∫Y
V)E#oup to the bottom of the dialog box뇰dONLNd.M
VY
Ù)ú#. See the chapter “Dialog Manager” °dONLNdQZlfw(clin π¿°dONLNdTZwfı)Inside Macintosh: Macintosh T@°dONLNdqZıf
9)~oolbox Essentials—@°dONLNdÇZ
9f
>)D f• °dONLNdÑZ
?f
∑)or additional information o8°dONLNdüZ
∏f
√)yn iq¿°dONLNd¢Z
√f
Í)
tem lists..°dONLNd≠llxÄ(ulThe °dONLNd±lÄxº)
filterProc°dONLNdªlºx
fl)<> parameter should be a pointer to an expandable modal-dialog fi°dONLNd˙l
flx
Ú(u
fllter ˇˇ§Ã°dONLNdˇylÖú(Çlfunction or ˇ˛Ód…ò°dONLNd    yúÖÆ)0NILˇˇ§Ã…ò°dONLNd    yÆÖ≤). °dONLNd    y≥Ö
?)An expandable modal-dialog fi˛h°dONLNd    -y
?Ö
˜)å+lter function is similar to a modal-dialog .
°dONLNd    XÜlír(èl
fiå¿°dONLNd    ZÜrí◊)lter function or event fiD °dONLNd    sÜÿí
 )f6lter function except that an expandable modal-dialog fi°dONLNd    ™Ü
Àí
‹)Ûlter .°dONLNd    Øìlü
/(úl+function accepts two extra parameters. The °dONLNd    ⁄ì
/ü
q)√ModalDialog°dONLNd    Âì
qü
})B prR`°dONLNd    Ëì
}ü
ö)ocedur$¿°dONLNd    Óì
öü
À)e calls the .
°dONLNd    ˙†l¨Â(©lexpandable modal-dialog fi:Ä°dONLNd
†Ê¨
<)zlter function you prdž°dONLNd
(†
<¨
¢)Vovide in this parameter≤†°dONLNd
?†
¢¨
ß)f. ˇ@:@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äUsing the Edition Manager

, (‡2-61
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähì(eäPrN†°dONLNd\îhΔ)
oviding a fiƒ °dONLNd\Δh
[)2"lter function enables you to map r)¿°dONLNd0\
\h)ñ(eal events (such as a mouse-down event) °dONLNdXiäu
Ò(räSto an item hit (such as clicking the Cancel button). For instance, you may want to °dONLNd´vädž*map ÷ °dONLNdØv†Çß)a V °dONLNd±v®ÇÀ)keyboar °dONLNd∏vÃÇ
Í)$Ad equivalent to an item hit. See the chapter “Dialog Manager” in °dONLNd˘Éäè§(åäInside qÄ°dONLNd
É•è
)Macintosh: Macintosh T“Ä°dONLNd
É
è
K)boolbox Essentials.óÄ°dONLNd
'É
Lè
≥)E for information on the ,
CourieróÄ°dONLNd
?É
≥è
ı)gModalDialogóÄ°dONLNd
JÉ
ıè
˜)B
 .
°dONLNd
Kêäúì(ôäprG °dONLNd
Mêîú≤)
ocedurfi`°dONLNd
Sê≤úπ)e..°dONLNd
V¢äÆû(´äThe °dONLNd
Z¢ûÆ»)dlgHook°dONLNd
a¢»Æ
))* parameter should be °dONLNd
v¢
)Æ
©)aa pointer to an expandable d°dONLNd
í¢
©Æ
‘)Ä    ialog hoo°dONLNd
õ¢
‘Æ)+k function °dONLNd
¶Øäªè(∏ä
o°dONLNd
ßØèªï)r °dONLNd
©Øïªß)NIL°dONLNd
¨Øߪ¨). !†°dONLNd
Æبª
À)?An expandable dialog hook function is similar to a dialog hook .
°dONLNd
̺仱(≈ä    function @°dONLNd
ˆº≤»–)(except ˛‡°dONLNd
˝º–»
Â)>that an expandable dialog hook function accepts an additional .°dONLNd;…ä’∫(“ä    parameter¬†°dONLNdD…π’“)/. The ¬†°dONLNdJ…“’
V)NewSubscriberExpDialog¬†°dONLNd`…
V’
[)Ñ, ¬†°dONLNdb…
[’
Ÿ)NewPublisherExpDialog¬†°dONLNdw…
Ÿ’
Ò)~, and °dONLNd}÷ä‚
(fläSectionOptionsExpDialog°dONLNdî÷
‚)ä5 functions call your expandable dialog hook function ˇˇt:°dONLNd…„äÔÈ(Ïäafter each call to the ˇ˛\Æ≈"°dONLNd‡„ÈÔ
+)_ModalDialogˇˇt:≈"°dONLNd΄
+Ô
6)B prº°dONLNdÓ„
7Ô
T)ocedurfi°dONLNdÙ„
SÔ
b)e. TRV°dONLNd¯„
cÔ
j)
hRV°dONLNd˘„
jÔ
p)e Δê°dONLNd˚„
pÔ
†)
dialog hoo: °dONLNd„
°Ô
Ú)1k function should tóx°dONLNd„
ÚÔ
˛)Qakóx°dONLNd„
˛Ô)e t≤°dONLNd„    Ô)he °dONLNd 丆(˘äapprR`°dONLNd$†¸
)opriate action, such as fiR`°dONLNd>
¸
M)nlling in a checR`°dONLNdM
M¸
X)?kbR`°dONLNdO
X¸
{)ox. The R`°dONLNdW
{¸
∑)#
itemOffsetR`°dONLNda
∑¸)< parameter to the .
°dONLNds˝ä
    ì(
äprG °dONLNdu˝î
    ≤)
ocedurfi`°dONLNd{˝≤
    
2)e is the number of items in th∑`°dONLNdô˝
3
    
=)Åe iÈ`°dONLNdú˝
=
    
w)
tem list befor˘ °dONLNd™˝
w
    
˘):e the expansion dialog items. õ°dONLNd»˝
˙
    )É
Y[Ä°dONLNd…˝
    )ou °dONLNdÃ

ä

(
äneed to subtract the item of- °dONLNdË




)yfset frb‡°dONLNdÔ




ë)om the item hit to get the r√†°dONLNd


ë
)uelative item number in the °dONLNd&
ä
#
(
 äexpansion dialog item list. Th-¿°dONLNdD


#
Õ)É*e expandable dialog hook function should r±Ä°dONLNdn

Õ
#
ˇ)¿eturn as its °dONLNd{
$ä
0µ(
-ä
function r”@°dONLNdÖ
$µ
0œ)+esult tŒ °dONLNdå
$–
0
>)he absolute item number °dONLNd£
$
>
0
C)n. °dONLNd¶
6ä
B
©(
?ä?When the Edition Manager displays subsidiary dialog boxes in frà °dONLNdÂ
6
©
B(
?
©ont of another dialog °dONLNd˚
Cä
OÕ(
Läbox on the user¿°dONLNd

Cœ
OÂ)E’s scr˛@°dONLNd
C‰
O
    )een, youn†°dONLNd
C


O
{)&r dialog hook and event fie°dONLNd2
C
|
O
Ω)rlter functions s‘@°dONLNdB
C
Ω
O)Ahould check the .°dONLNdR
Pä
\Æ(
YärefCon°dONLNdX
PÆ
\¥)$ fPÄ°dONLNdZ
P¥
\Ê)ield in the PÄ°dONLNdf
PÊ
\
.)2WindowRecordPÄ°dONLNdr
P
.
\
k)H data type (fr"‡°dONLNdÄ
P
k
\
å)=om the "‡°dONLNdá
P
å
\
∞)!window"‡°dONLNdç
P
∞
\
∂)$ fÛ`°dONLNdè
P
µ
\
Á)ield in the °dONLNdõ
]ä
i“(
fäDialogRecord°dONLNdß
]“
i
t)H#) to determine which window is currR`°dONLNd 
]
t
i
∏)¢ently in the for$¿°dONLNd⁄
]
∏
i
Δ)Degr˜ °dONLNd›
]
≈
i)ound. The main °dONLNdÏ
jä
v‹(
sädialog box for the °dONLNdˇ
j‹
v
Z)RNewPublisherExpDialog°dONLNd
j
Z
v
Å)~     and the °dONLNd
j
Å
v)'NewSubscriberExpDialog°dONLNd3
j
v)Ñ
 .
°dONLNd4
wä
É
B(
Ää*functions contains the following constant:.°dONLNd_
éä
ö®*CONST°dONLNdg
é¿
ö
,)6sfMainDialogRefCon°dONLNdÄ
é
>
ö
t)~    = 'stdf';°dONLNdç
é
Ü
ö
˛)H{new publisher and }°dONLNd∞
ú
Ü
®
Ï*{ new subscriber}°dONLNd¬
¥ä
¿
    (
ΩäThe main dialog box for the °dONLNdfi
¥
    
¿
ì)SectionOptionsExpDialog°dONLNdı
¥
ì
¿
Ù)ä function contains the .
°dONLNd
¡ä
Õfi(
 äfollowing constant:.°dONLNd 
ÿä
‰®*CONST°dONLNd(
ÿ¿
‰
>)6emOptionsDialogRefCon°dONLNdE
ÿ
P
‰
Ü)ê    = 'optn';°dONLNdR
ÿ
ò
‰
¯)H{options dialog}ˇˇÀî.
°dONLNdc
ä
¸î(
˘äSeâ`°dONLNde
î
¸õ)
e ûî°dONLNdg
õ
¸
é)3“Summary of the Edition Manager” beginning on page ¿†°dONLNdö

è
¸
¶)Ù2-106Ä°dONLNdü

ß
¸
¨) f≥Ù°dONLNd°

¨
¸)or additional constants. .°dONLNdªäû(äThe °dONLNdøû‡)yourDataPtr°dONLNd ‡
")B parameter is rR`°dONLNdŸ
"
Ï)B0eserved for your use. It is passed back to your R`°dONLNd    
Ï) dialog ˇˇΔé°dONLNdä≠(ähook anFé°dONLNdÆ‘)$    d event f§*°dONLNd ‘Â)&ilte§*°dONLNd$Â
)r function.j∏°dONLNd/

”)-, This parameter does not have to be of type ˇˇS™,D°dONLNd[
‘
Ê)¬PtrˇˇΔé,D°dONLNd^
Ê)—it can be ˇˇ¯¿°dONLNdiä(
é(%ä;any 32-bit quantity that you want. In Pascal, you can pass ˇˇÍ@0@°dONLNd§
è(
—(%
èyourDataPtrˇˇ¯¿0@°dONLNdØ
—(
“)B
 )°dONLNd∞
”(
·)in rÙ °dONLNd¥
·(
)egister éÄ°dONLNdº(
)!
AéÄ°dONLNdΩ
()6 ,á@°dONLNd¿()

 .
°dONLNd¡)ä5î(2äanQ`°dONLNd√)ï5∏)d declar °dONLNdÀ)∏5
e)#%e your dialog hook and modal-dialog fiÅ@°dONLNdÒ)
f5
Ü)Æ    lter as l熰dONLNd˙)
Ü5)  ocal functions without the last °dONLNd    6äB∑(?ä    parameterS†°dONLNd    #6∑B
5)-. The stack frame is set up pr±°dONLNd    A6
5B
˜)~.operly for these functions to access their par# °dONLNd    o6
¯B)√ent °dONLNd    sCäO
(Lä"local variables. See the chapter “! °dONLNd    ïC
O
;)èStandarU`°dONLNd    úC
;O
z)"d File Package¸`°dONLNd    ™C
zO
å)?” in ∂ °dONLNd    ØC
çO
Ì)Inside Macintosh: Files ˝°dONLNd    «C
ÌO
)`
fP‡°dONLNd    »C
ÒO
¸)or °dONLNd    ÀPä\Á(Yädetailed information..°dONLNd    ·bän≠*For the °dONLNd    Èb≠n
+)#NewPublisherExpDialog°dONLNd    ˛b
+n
@)~ and °dONLNd
b
@n
ƒ)NewSubscriberExpDialog°dONLNd
b
ƒn)Ñ functions, all the °dONLNd
-oä{
(xäpseudo-items for the StandarR`°dONLNd
Io
{
})Ñd File Package—such as R`°dONLNd
`o
}{
◊)osfHookFirstCallR`°dONLNd
oo
◊{
Ó)Z(–1), °dONLNd
u|äà‰(ÖäsfHookNullEvent°dONLNd
Ñ|‰à
)Z(100), °dONLNd
ã|
à
f)sfHookRebuildList°dONLNd
ú|
fà
ï)f(101), and °dONLNd
ß|
ïà
È)/sfHookLastCall°dONLNd
µ|
Èà)T    (–2)—can °dONLNd
æâäïfi(íäbe used, as well as °dONLNd
“âfiï
P)TemHookRedrawPreview°dONLNd
Ââ
Pï
j)r(150).ˇJÇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-62    )B Subscribing to Non-Edition Files4^*¿
¯
.°dONLNd\lhè(elFor the ,
Courier°dONLNd\èh
)#SectionOptionsExpDialog°dONLNd\
h
–)ä) function, the only valid pseudo-items arR`°dONLNdH\
–h
◊)∑e °dONLNdJiluΔ(rlsfHookFirstCall°dONLNdYiΔu›)Z(–1), °dONLNd_i›u
7)sfHookNullEvent°dONLNdni
7u
S)Z(100), °dONLNdui
Su
ß)sfHookLastCall°dONLNdÉi
ßu
æ)T(–2), °dONLNdâvlÇfi(lemHookRedrawPreview°dONLNdúvfiÇ˙)r(150), °dONLNd£v˙Ç
l)emHookCancelSection°dONLNd∂v
lÇ
à)r(160), °dONLNdΩÉlèfi(ålemHookGoToPublisher°dONLNd–Éfiè˙)r(161), °dONLNd◊É˙è
l)emHookGetEditionNow°dONLNdÍÉ
lè
à)r(162), °dONLNdÒêlú‰(ôlemHookSendEditionNow°dONLNd
ê‰ú
)x(162), °dONLNd
ê
ú
Ñ)emHookManualUpdateMode°dONLNd
"ê
Ñú
≥)Ñ(163), and °dONLNd
-ùl©‰(¶lemHookAutoUpdateMode°dONLNd
Aù‰©
t)x(164). See the chapter “StandarR`°dONLNd
`ù
t©
…)êd File Package” in .
°dONLNd
s™l∂Ü(≥lInside qÄ°dONLNd
z™á∂Ã)Macintosh: Files Δ‡°dONLNd
ã™Ã∂
^)E for information on pseudo-items.

Ω*ÿ
¯4æ*ÿ
¯

Ë*
¯4È*
¯ Í*Í
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNd
≠’*Ëu(„*
SubscribinWT°dONLNd
∑’vËë)Lg toǸ°dONLNd
ª’ëË
) Non-Edition FilesˇˇˇˇˇˇV˛(„

2
°dONLNd
œ˘l
„(
lUsing the Edition ManagerꆰdONLNd
ˢ„

5)w, a subscriber can rØ °dONLNd
¸˘
5

j)Read data dirª¿°dONLNd˘
j

à)5ectly frH`°dONLNd˘
â

)om another document, .°dONLNd%
l
±(
lsuch as an entirR`°dONLNd5
±
∏)Ee R`°dONLNd7
∏
‹)'PICT'R`°dONLNd=
‹
Â)$ fiR`°dONLNd@
Â

Δ)    5le, instead of subscribing to an edition. This featur$¿°dONLNdu

Δ

Ê)·    e is for .
°dONLNd~
l

O(
l3advanced applications that can set up bottleneck pr\@°dONLNd±

O

m)„ocedurÛÄ°dONLNd∑

m

ã)es for r{ °dONLNdø

å

Ø)eading. ©`°dONLNd«

Ø

«)#Figur| °dONLNdÃ

«

‡)e 2-26†°dONLNd“

·

„)
 .°dONLNd”
 l
,
 (
)l(shows a document that is subscribing dirR`°dONLNd˚
 
 
,
L)¥ectly to a R`°dONLNd
 
L
,
p),'PICT'R`°dONLNd
 
p
,
y)$ fiR`°dONLNd
 
y
,
Ö)    le.R`°dONLNd
 
Ö
,
á)
 


N*
_
¯4
O*
_
¯"
O*]

ˇ·ˇ‚7^
    .
°dONLNd
Dl
Oú(
LlFigure 2-26.°dONLNd!
DÆ
O
)BSubscribing directly to a °dONLNd;
D

O
/)c'PICT'°dONLNdA
D
/
O
6) fi°dONLNdD
D
6
O
=)le
.
°dONLNdHHlT
€(QlTFor each application, the Edition Manager keeps a pointer to a bottleneck function. °dONLNdúUla*The ª¿°dONLNd†Ua
î)>Edition Manager never opens or closes an edition container diro†°dONLNdfiU
ïa
©(^
ïectlyG†°dONLNd„U
©a
„). Instead, the .°dONLNdÚblnı(klEdition Manager calls the currR`°dONLNdbın
F)âent edition openerï°dONLNd"b
En
^)P. The ï°dONLNd(b
^n
∏)InitEditionPackï°dONLNd7b
∏n
‡)Z
 function .
°dONLNdAol{™(xl(described on ı`°dONLNdOo™{¡)>page –@°dONLNdTo¬{‘)2-74$ °dONLNdXo’{
)) sets up the curr†°dONLNdjo
{
ô)Jent system opener function.


_j0
¯4
^`
_aòB@
@

_a
übøø    
◊ˇ˛Ï
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏòB@Ä
@Ä

üa
flb
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏòBÄ¿
Ä¿

flab
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏòB¿

¿

a_b
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏ
÷ˇÏøøøøøøøøøøøøøøøøøø˛ÁÄ8»˛"@»˛   »˛Ñ  p»˛Ñ  à»˛FAàà»˛(ÄBê»˛fl¸<`»øøøø"˛
Ê˛`Ä !Ä¿˛
x„øê-fl"˛
 ˛ê$ Ä@@˛
$DTêSfl!˛˝@Ä@@DÄDàD Bfl#˛Üv¥ ‡4qÕ£qº8ËFÁë«@Hê
Ó‡#˛ç¢ò–     JRΔK–i±©DêàÑÄpêö4‡#˛    %‡C(â Ñä(êâ!–HPêàÄAî8‡#˛…aê% J¥ß    ¥¨`æBåa    ¿Åà
&@‡#˛œ†·‡x¿.|GGH‡[¡ÃàAÅ√é
<8‡˝
 ˆ

˝@˚
fi˝
 ˆ

˝Ä˚fi˝

¿ı‡˛˙fiø˛‡ÿ00…˛ @`…˛Ñ†…˛
Çû7<£^4qhÕ˛
ç4hî$äI¶∞Õ˛
$P®Hîâ' Õ˛
7»ë,$I÷ú»@Õ˛
ÀxÓH5Δ§i«@ÕòB

@


@
_aübˆ
 È
 È

¿Ãø$˛0Ä0
¿˝å:˝„˛
˝IJ

Ä˝D‹#˛ ( 
Ä
@Ñ˚@„(˛"!dÇxÊQ(”‹„¨
=ƒ”^yç„s¡Ì6õOçÊs¿Â(˛"¶§Ç)-¶ÖI$ôI¥
ödâ%RFâA
”iE2RLâ@Â(˛"«-Pä'í(ä$(úHëF"E
ÅíJä$"I
ÄÂ(˛"H6ZR¯    y¶“)H- â“K$Áâ¡)4ú´LÁì¿Â(˛"G$ìùgq¶<ëŒHáIܨ≤;é‰Ä·…$ó“sú‰ÄÂIJ
 Ä÷Ï
 Ä÷Ï
q¿÷ø˛
Ü8
Ä`
Ü◊˛ID˚ ˛â˝◊˝ëd
˛@

"0◊˛X<q˚údôD◊Ö
BPx„˜8B<Ÿ˝éàã)$$∂ö
"öBê%RHi≠Ÿ˝Ñà#
Q-(ú%"E¯F¢ âŒ"Ÿ˝àê%⁄H6K‡uØ    H J)¥êæ$Ÿ˛0`XÁíp$uúA©0 ±œ$‡YŒXŸ˚@˚@¸Ä¸@Ÿ˚@ıĸ@Ÿ˚‡ˆ

¿¸‡Ÿøøøøøøøøøøøøø˝Ä@
–¸Œ˛
Ä¿ ¸Œ˛ÄÄ Œ˛è<Ñiº◊@Δœ˛Ñíö∂íR5ÄIœ˛»£§¢¢9"êœ˛I%†—I•,B"”œ˛ˆYIYÙ:tå@–˝
@˝@Õ˝
@˝@ ˝
8‡˝‡ ø˛
¿ÄÄÕ˛    
 Ä@Ã˛    @¿!Ã˛By„<@7C»œ˛M(¶LÄ@IçHœ˛ éQD$¿@â(œ˛@YiòÄFû0œ˛Ñ>íNË8j œÚ œÚ@œÛ

ÄœøòB
@
Ä

@
Ä
üaflb˛
§¸
À˛

l¸
$$À˛H ÄÀ˛I£˝Œ–0À˛H§¶$ë`À˛ëB$D°@À˛⁄YHO"Ä$À˛ìÓH5ÄÒxÀøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB
Ä
¿

Ä
¿
flabøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB
¿
‡

¿
‡
a?bøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB@
@

_a
üb
øø    
◊32Ï’
Ï’Ï
¡’
Ï
¡’Ï’
Ï’Ï
¡’
ÏÚˇ—˛Å˛ˇÄ¯
ÁÏ˛ÄÙ

@Ë
Ï˛ÄÙ
ÁÏÄÙ
—˛ÄÙ
Á
ÏÄÙ
—˛ÄÙ
ÁÏ˛ÄÙ

Ë
Ï˛Ä˘˝
ÁÏĢ˝
—˛Ä˘
˛
Á
ÏĢ
˛
—˛Ä˘
˛
ÁÏ˛Ä˘
˛
È
Ï˛Ä˘¿
ÁÏĢ<‡
—˛ÄÄ˝|‡
Á
Ïĸ|‡
—˛Ä>˚|Ä
ˇˇÈÏ˛ÄÄ<˚ÄÈ
Ï˛ÄÄ|˘ÄÈÏÄÄ‹˘Ä”˛ÄÄò˘ÄÈ
ÏÄÅ∏˘˛”˛ÄÉ8ıÈÏ˛ÄÇ8˚

Ä˝È
Ï˛ÄÜ0˚

¿˝ÈÏÄ1åp˚
@
Ä”˛Ä!àp˚

¿È
ÏÄ!ÿp˛    
¿”˛Ä!‡˚
ÈÏ˛Äa‡˚ÙÈ
Ï˛ÄA‡‡p|ÈÏÄA¿‡ê    x”˛Ä¡¡¿
@˛È
ÏġŇÅ $˛˛”˛ÉÒ¯
¿8˛˛ÈÏ˛Ä˜
˛È
Ï˛Ä˜
˛ÈÏĘ
h˛”˛Ä˜
¯˛È
ÏĘ
˛”˛Ä˜8˝ÈÏ˛Ä¯
0x˝ı¯ˇ
Ï˛Ä¯0¸ı˘
Ïįp¸ı˘
È˛Ä˙¿¿¸ı˘

ÏĢ
ܸı˘
È˛Ä¯¸ı˘
Ï˛Ä˙¸¸ı˘

ÏòB@Ä
@Ä

üa
flb
˛Ä˚
î ˛ı˘
ÏÄ˚
(`˛ı˘
È˛Ä˚l˛ı˘

ÏÄ˚»IJı˘
ˇ¿Î˛Ä˜
IJı˜
¿Ï˛ÄÚı˜
¿
Ï˛ÄÚı˜
¿ÏÄÚı˜¿Î˛Ä˘˙USı˜
¿
ÏĢL˚Ã
À ˆ˜¿Î˛Ä˘˘38ˆ˚@˛
¿Ï˛Ä˘
P˛¿ˆ˚`˛
¿
Ï"˛Ä˘
0˛‡3ˆ˛¿p˛
¿Ï"Ģ@ˆ˛¿8˛¿Î"˛Ä˘PXˆ˛¿
<˛
¿
Ï"Ģ@ÄHˆ˛Ä
¿˛¿Î"˛Ä˘0‡j3ˆć˛
¿Ï"˛Ä˘P
0*ˆÄÄ¿
Ï"˛Ä˘0
ò/3ˆ\Ä¿Ï!Ģ@˛å-ˆ˝fÄ¿Î#˛Ä˚
PcÑ-ˆ˝£¿¿
Ï#Ä˚
@ÒÜ!ˆ˝8·
@¿Î$˛Ä˚
$0¬#3ˆ˛¸aà¿¿Ï$˛Ä˚
uÑPB"ˆ˛0òÄ¿
Ï(˛Ä˚&ö0?¸c¯3Ç˙
åêÄ¿Ï(Ä˚$ú@pÅF˙
üˇê˛¿Î*˛Ä˚I Px·ÃKô∑çĸº
ೃÏ)Ä˚I@xπÄ?ã ~f_˚>8¢¿¿Î'˛Ä˘0ÃÄ|3 v&Q˚˛†¿¿Ï&˛Ä˘P
Ü<;ôÁè˚˝ì`¿
Ï ˛Ä˘0ˇ√3ˆ¸¡Ä¿Ï"Ģ@`

ãˆ˛
ˇ‡¿Ä¿Î"˛Ä˘Pp
Ä”ˆ@‡¿
Ï"Ģ@p?ÉÄÄ~Kˆ@ ¿Î"˛Ä˘0@3>É√sˆ¡‡`?∞¿Ï"˛Ä˘P@`Ç
ìˆœ8 ‡–¿
Ï"˛Ä˘1¿¿ Ûˆ
ò Äx¿Ï$Ģ
A¿Ä ˛0¯pé8¿Î$˛Ä˘
P p¯p¿ª¿
Ï%Ģ
@ò0
ãfl˘ˇ
˛˛Ç
¿¿Î%˛Ä˘
09¯–≥
Ģf
`¿Ï$˛Ä˘    P1˘ò[”¯å~4 ¿
Ï#˛Ä˘    0ˇlÛ„˜"˛d7‡¿Ï%Ģ
@ˇ»t
Ģ
ˇƒö0¿Î&˛Ä˙PˇÃ‹fl˘ˇ˛

ˇÊû¿
Ï%Ä˙@ˇƒåp¯
ˇÚ∂¿Î%˛Ä˙0ˇÑ30¯ˇ‚‚¿Ï%˛Ä¸<nñPˇˆ˛ˇ‚Ä¿
Ï%˛Ä¸ì0ˇ3ˆ˛ˇ¬˛
¿Ï%ĸ#@?ˇÑˆ˛ˇ¬˛¿Î%˛Ä¸%<*P
ˇˇÑˆ˛ˇ¬˛
¿
Ï%ĸX‘$@ˇˇ‰ˆ˛ˇˇ‚˛¿Î%˛Ä¸@0ˇˇ¸3ˆ
ˇˇ˙˛
¿Ï%˛Ä¸@Pˇˇ˛ˆ˛ˇ˛
¿
Ï%˛Ä¸‡0˛ˇ3ˆ˛ˇÑ˛
¿Ï"Ģ
@˛ˇˆ˛ˇƒ˛¿Î"˛Ä˘
P?˛ˇˆ˛ˇƒ˛
¿
Ï!Ģ@˝ˇˆ˛ˇƒ˛¿Î"˛Ä˘0˛ˇ˛3ˆ˛ˇΔ˛
¿Ï"˛Ä˘P˛ˇ˛ˆ˛ˇÇ˛
¿
Ï!˛Ä˘3˝ˇà3ˆ˛ˇÇ˛
¿Ï ĢG˝ˇÃˆ˝ˇ‚˛¿Î ˛Ä˘_˝ˇƒˆ˝ˇ‚˛
¿
Ï ĢO˝ˇƒˆ˝ˇ‚˛¿ÎòBÄ¿
Ä¿

flab
 ˛Ä˘?˝ˇƒ3ˆ˝ˇ„˛
¿Ï ˛Ä˘_˝ˇΔˆ˝ˇ·˛
¿
Ï ˛Ä˘0˝ˇÇ3ˆ˝ˇ·˛
¿Ï"Ģ
@s˛ˇˆ?˛ˇ·˛¿Î"˛Ä˘Pc¯áˆ9˛ˇ¡Ä¿
Ï"Ģ@c¯
á
Ĉ9¸cÄ¿¿Î"˛Ä˘0c¯
Ä3ˆ9¸AÄ`¿Ï"˛Ä˘Pg¯
ˆ9¸AIJ
¿
Ï"˛Ä˘0g∏
3ˆ9¸¡Ä˛
¿Ï"Ģ@¯
ˆ9¸ÅIJ¿Î"˛Ä˘P∞0ˆ?¸ÅIJ
¿
ÏĢ@˚ıÏÅIJ¿Î˛Ä˘˘3ı˜
¿Ï˛Ä˘˙USı˜
¿
Ï˛Ä˘˘3ı˜
¿ÏĈˇÄı˜¿Î˛ÄˆˇÄı˜
¿
ÏĈˇÄı˜¿Î˛ÄˆˇÄı˜
¿Ï˛ÄÚı˜
¿
Ï˛ÄÚı˜
¿ÏÄÚı˜¿Î˛ÄÚı˜
¿
ÏIJ
 D˝ı˜¿Î ˛Ä˛
˚€˚ˇÌˇ¿˛ı¯¿Ï!˛Ä˛˚€ÒøÕˇ¿˛ı˘ˇ
¿
Ï˛Ä˚@¿˛ı˜ˇ
¿ÏÄÚı˜ˇ¿Î˛Ä˝Ω@Ñ
˝È
ÏÄ˝4∑oˇœfiP˝”#˛Ä˝5ßoˇœfi–˝Ù @
˛Ï˛Ä˚¿˚ÙĆ
˛
Ï˛ÄÚÙºÊ0Cùh<Ã`Ï$Ä
†ää†
˛Ù    &ôy≤GT˛Í%˛Äfløflº˛Îfiˇ?∏Ù:ôi"[T–
Ï$Äfløflº˛Îfiˇ?∏Ù    .ñ0”èTÓ`ͲÄÚ˚Ï˛ÄÚ˚
Ï˛ÄFÅ
r˛˚ÏÄ
˛ˇ{ÔfiÔüøÁ/ˇÄ”˛Ä
˛ˇ{ÔfiÔóø«ˇÄÈ
ÏĘ@˝”˛ÄÚÈÏ˛Ä˛#îCâ˝È
Ï˛Ä˛:˝Î€}Àœø¯˛ÈÏIJ;˝Ô⁄}flÀø¯˛”˛ÄÚÈ
ÏÄÚ”˛Ä˝‡
Ä`˝ÈÏ˛Ä˝vˇoΩˇüÔ˝È
Ï˛Ä˝vˇoΩˇüÔ˝ÈÏĘ˝”˛ÄÚÈ
ÏÄ˚@˚”˛Ä˚π¿˚ÈÏ˛Ä˚ª¿˚È
Ï˛Ä˚
˘ÈÏÄÚ”˛ÄÚÈ
ÏÄÚ”˛ÄÚÈÏ˛ÄÚÈ
Ï˛ÄÚÈÏˇ”òB¿

¿

a_b
˛ÒˇÈ
Ï
¡’Ï’
Ï’Ï
¡’
Ï
¡’Ï’
Ï’Ï
¡
÷UÏ
÷ÃÏøøøøøøøøøøøøøøøøøø˛ÁÄ8»˛"@»˛   »˛Ñ  p»˛Ñ  à»˛FAàà»˛(ÄBê»˛fl¸<`»øøøø"˛
Ê˛`Ä !Ä¿˛
x„øê-fl"˛
 ˛ê$ Ä@@˛
$DTêSfl!˛˝@Ä@@DÄDàD Bfl#˛Üv¥ ‡4qÕ£qº8ËFÁë«@Hê
Ó‡#˛ç¢ò–     JRΔK–i±©DêàÑÄpêö4‡#˛    %‡C(â Ñä(êâ!–HPêàÄAî8‡#˛…aê% J¥ß    ¥¨`æBåa    ¿Åà
&@‡#˛œ†·‡x¿.|GGH‡[¡ÃàAÅ√é
<8‡˝
 ˆ

˝@˚
fi˝
 ˆ

˝Ä˚fi˝

¿ı‡˛˙fiø˛‡ÿ00…˛ @`…˛Ñ†…˛
Çû7<£^4qhÕ˛
ç4hî$äI¶∞Õ˛
$P®Hîâ' Õ˛
7»ë,$I÷ú»@Õ˛
ÀxÓH5Δ§i«@ÕòB

@


@
_aüb
ˆ
 È
 È

¿Ãø$˛0Ä0
¿˝å:˝„˛
˝IJ

Ä˝D‹#˛ ( 
Ä
@Ñ˚@„(˛"!dÇxÊQ(”‹„¨
=ƒ”^yç„s¡Ì6õOçÊs¿Â(˛"¶§Ç)-¶ÖI$ôI¥
ödâ%RFâA
”iE2RLâ@Â(˛"«-Pä'í(ä$(úHëF"E
ÅíJä$"I
ÄÂ(˛"H6ZR¯    y¶“)H- â“K$Áâ¡)4ú´LÁì¿Â(˛"G$ìùgq¶<ëŒHáIܨ≤;é‰Ä·…$ó“sú‰ÄÂIJ
 Ä÷Ï
 Ä÷Ï
q¿÷ø˛
Ü8
Ä`
Ü◊˛ID˚ ˛â˝◊˝ëd
˛@

"0◊˛X<q˚údôD◊Ö
BPx„˜8B<Ÿ˝éàã)$$∂ö
"öBê%RHi≠Ÿ˝Ñà#
Q-(ú%"E¯F¢ âŒ"Ÿ˝àê%⁄H6K‡uØ    H J)¥êæ$Ÿ˛0`XÁíp$uúA©0 ±œ$‡YŒXŸ˚@˚@¸Ä¸@Ÿ˚@ıĸ@Ÿ˚‡ˆ

¿¸‡Ÿøøøøøøøøøøøøø˝Ä@
–¸Œ˛
Ä¿ ¸Œ˛ÄÄ Œ˛è<Ñiº◊@Δœ˛Ñíö∂íR5ÄIœ˛»£§¢¢9"êœ˛I%†—I•,B"”œ˛ˆYIYÙ:tå@–˝
@˝@Õ˝
@˝@ ˝
8‡˝‡ ø˛
¿ÄÄÕ˛    
 Ä@Ã˛    @¿!Ã˛By„<@7C»œ˛M(¶LÄ@IçHœ˛ éQD$¿@â(œ˛@YiòÄFû0œ˛Ñ>íNË8j œÚ œÚ@œÛ

ÄœøòB
@
Ä

@
Ä
üaflb
˛
§¸
À˛

l¸
$$À˛H ÄÀ˛I£˝Œ–0À˛H§¶$ë`À˛ëB$D°@À˛⁄YHO"Ä$À˛ìÓH5ÄÒxÀøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB
Ä
¿

Ä
¿
flab
øøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB
¿
‡

¿
‡
a?b
øøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB@
@
?abøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB@Ä
@Ä
aøbøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòBÄ¿
Ä¿
øaˇbøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB¿

¿

ˇa?bøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB

@


@
?abøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB
@
Ä

@
Ä
aøbøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB
Ä
¿

Ä
¿
øaˇbøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB
¿
‡

¿
‡
ˇabøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB@
@
?ab
øøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB@Ä
@Ä
aøb
øøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòBÄ¿
Ä¿
øaˇb
øøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB¿

¿

ˇa?b
øøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB

@


@
?ab
øøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB
@
Ä

@
Ä
aøb
øøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB
Ä
¿

Ä
¿
øaˇb
øøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøòB
¿
‡

¿
‡
ˇab
øøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøøˇ6¶@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡ä Subscribing to Non-Edition Files

, (‡2-63
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähê(eä
Tµ¿°dONLNd
\èh)o override the standarRÄ°dONLNd\Òh
M)bd opener function, crĆ°dONLNd,\
Mh)\*eate an opener function that contains the °dONLNdViäuÎ(räfollowing parameters:,
Courier.°dONLNdlÄäå
™*0FUNCTION MyOpener (selector: EditionOpenerVerb; °dONLNd£éˆö¸+l
 °dONLNd§é¸ö
Ï)(VAR PB: EditionOpenerParamBlock): OSErr;.
°dONLNdÕ¶ä≤ê(Øä
Y@Ä°dONLNdŒ¶ê≤
_),our opener needs to know which formats the fil¿°dONLNd˚¶
_≤
Í)œ le contains and how the data is °dONLNd
≥äø”(ºäsupposed to be rÆ`°dONLNd
+≥”ø
)Iead or written. ˇˇ÷™.°dONLNd
<≈ä—
ê(Œä<The opener function is passed an edition opener verb in the ˇˇÉ˛πN°dONLNd
x≈
ê—
¿(Œ
êselectorˇˇ÷™πN°dONLNd
Ä≈
¿—
Ò)0
 parameter“ò°dONLNd
ä≈
Ò—)1, which .
°dONLNd
í“äfi©(€äidentifiV†°dONLNd
ö“™fi
å) 3es the action the opener function should perform. TU@°dONLNd
Õ“
çfi
¯)„he opener can allocate a °dONLNd
ÊfläÎ
g(Ëä2handle or pointer to contain information such as fi~†°dONLNdfl
hÎ
v)file ru†°dONLNdfl
vÎ
Ü)efer!¿°dONLNd!fl
áÎ)ence numbers. This value is .°dONLNd=Ï䯣(ıäpasse°dONLNdBÏ£¯Ø)d t°dONLNdEÏد—)o the I/°dONLNdMÏ—¯fl)"O rR`°dONLNdPÏfl¯
)outines in the R`°dONLNd_Ï
¯
N)?ioRefNumR`°dONLNdgÏ
N¯
W)0 fiR`°dONLNdjÏ
W¯)    *eld of the edition opener parameter block.°dONLNdï˛ä

û(
äThe °dONLNdô˛û

¬)eoOpen°dONLNdü˛¬

◊)$ and °dONLNd§˛◊


)    eoOpenNew°dONLNd≠˛



ï)6 edition opener verbs (describe°dONLNdÃ˛
ï


®)àd in °dONLNd—˛
®

)“Calling an Edition .
°dONLNdÂ
ä
ÿ(
äOpener” on page ◊°dONLNdı
ÿ
Í)N2-64*‡°dONLNd˘
Î
Ó)
)~¿°dONLNd˙
Ó
Ù) r√¿°dONLNd¸
Ù

Ω)0eturn a pointer to a function to do the actual r†°dONLNd,

æ
) eading and writing.°dONLNd@
ä
)
(
&äThe following sections describe,Zapf Dingbats°dONLNd`
3ä
:è*
n
°dONLNdb
0ñ
<Í)how to get the curr}@°dONLNdu
0Í
<
6)Tent edition openev@°dONLNdÜ
0
7
<
=)Mr °dONLNdâ
Eä
Lè(
Kä
n
°dONLNdã
Bñ
N
0)!how to set your own edition opene÷†°dONLNd¨
B
0
N
6)ör °dONLNdØ
Wä
^è(
]ä
n
°dONLNd±
Tñ
`
)how to call an edition openeÉ¿°dONLNdÕ
T

`
)}r °dONLNd–
iä
pè(
oä
n
°dONLNd“
fñ
r
)the edition opener parameters


ñH
ù4
óH
ù 
òä
ò

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdÒ
áä
ñ
](
íä"Getting the Current Edition Openerˇˇˇˇˇˇ€r(
í
2
.°dONLNd
ùä
©
(
¶äWhen you want to get the currR`°dONLNd2
ù

©
^)áent edition openeR`°dONLNdC
ù
^
©
b)M
rï°dONLNdD
ù
a
©
d)
,ï°dONLNdE
ù
d
©
à)     use the ï°dONLNdN
ù
à
©)$GetEditionOpenerProcï°dONLNdb
ù
©)x
 .
°dONLNdc
™ä
∂±(
≥ä    function..°dONLNdm
¡ä
Õ
&*err := GetEditionOpenerPro°dONLNdá
¡
&
Õ
2)úc(°dONLNdâ
¡
2
Õ
b)opener);°dONLNdí
Ÿä
Âû(
‚äThe °dONLNdñ
Ÿû
¬)opener°dONLNdú
Ÿ¬
Â˙)$ parameter rR`°dONLNd®
Ÿ˙
Â
)8eturnR`°dONLNd≠
Ÿ

Â
%)s a pR`°dONLNd≤
Ÿ
%
Â
p)ointer to the curr$¿°dONLNdƒ
Ÿ
p
Â
Ω)Kent edition opene$¿°dONLNd’
Ÿ
Ω
Â
¡)M
rg`°dONLNd÷
Ÿ
¿
Â
√)
.g`°dONLNd◊
Ÿ
√
Â
≈)
     °dONLNdÿ
Ÿ
≈
Â
Õ)
A|`°dONLNdŸ
Ÿ
Ã
Â
‹) difN¿°dONLNd›
Ÿ
‹
Â
È)fer! °dONLNd‡
Ÿ
È
Â
˘)ent .
°dONLNd‰
Êä
Úú(
ÔäcurrØ°dONLNdË
Êú
Ú
)Uent opener is kept for each application. One application’s opener is never called by °dONLNd=
Ûä
ˇ‚(
¸äanother application.

$H+4%H+ &ä&

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdSä$
&*$Setting an Edition Openerˇˇˇˇˇˇ€r( 
2
.°dONLNdn+ä7ë(4ä
Yï°dONLNdo+ê7∑)    ou can prg`°dONLNdx+∑7
:)'ovide your own edition openeg`°dONLNdî+
:7
>)É
r™°dONLNdï+
=7
@)
.™°dONLNdñ+
@7
H) Tø°dONLNdò+
G7
ã)o do so, use the ø°dONLNd©+
ã7)DSetEditionOpenerProcø°dONLNdΩ+7)x
 .
°dONLNdæ8äD±(Aä    function..°dONLNd»Oä[
t*'err := SetEditionOpenerProc(@MyOpener);°dONLNdgäsû*The °dONLNdÙhûs•)
@
°dONLNdıg•s’)MyOpener°dONLNd˝g’s
ò)0, parameter is a pointer to the edition opene°dONLNd)g
òs
»)√r function t°dONLNd5g
»s
˜)0
hat you arR`°dONLNd?g
˜s
˛)/e .
°dONLNdAtäÄì(}äprG °dONLNdCtîÄ
    )
oviding. If you set the curr√`°dONLNd_t
    Ä
^)uent opener to be a rΩ¿°dONLNdst
^Ä
Í)Uoutine in your own code, be sur˚†°dONLNdít
ÍÄ)å
e to call .°dONLNdúÅäçú(ääthe °dONLNd†Åúç
)GetEditionOpenerProc°dONLNd¥Å
ç
C)x function fi°dONLNd¿Å
Cç
…)/rst so that you can save the prR`°dONLNdflÅ
…ç)Üevious openerï°dONLNdÏÅç)<. If .
°dONLNdÒéäö
¡(óäHyour opener is passed a selector that it does not understand, use the pr¿°dONLNd9é
¬ö(ó
¬evious opener °dONLNdGõäßì(§äprG °dONLNdIõîß
)
Yovided by the Edition Manager to handle it. See the next section for a list of selectors.ˇ⁄@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-64    )B Subscribing to Non-Edition Files4^*¿
¯

k*r
¯4l*r
¯ mlm
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\lk
(glCalling an Edition OpeneˆP°dONLNd\
k
)ó
rˇˇˇˇˇˇ€r)Ì
2
.°dONLNdrl~s({l
Yï°dONLNdrr~†)ou use the ,
Courierï°dONLNd'r†~
).CallEditionOpenerProcï°dONLNd<r
~
≥)~# function to call an edition opener◊†°dONLNd_r
≤~
—)î. Since .
°dONLNdglã|(àlthe ›`°dONLNdk|ã
T)/Edition Manager is a package that may move, a r∏ °dONLNdö
Tã
œ)ÿeal pointer cannot be safely °dONLNd∑ålòo(ïl
rE°dONLNd∏åpòï)eturned ÅÄ°dONLNd¿åïò§)%for ΩÄ°dONLNdƒå§ò’)the standarL`°dONLNdœå÷ò
+)2d opener and I/O r2¿°dONLNd·å
+ò
 )U#outines. The system opener and the °dONLNd
ôl•(¢lI/O I†°dONLNd
    ôÄ•É)
r†°dONLNd

ôÑ•¶)outines °dONLNd
ôß•Ø)#ar”°dONLNd
ôØ•∂)e †°dONLNd
ô∑•∫)
r·†°dONLNd
ô∫•
q)+eturned as a value that is not a valid addrNÄ°dONLNd
Bô
r•
û)∏ess to a prë °dONLNd
Mô
û•
º),ocedur(`°dONLNd
Sô
Ω•
⁄)e. The .°dONLNd
Z¶l≤Í(ØlCallEditionOpenerProc°dONLNd
o¶Í≤ˇ)~ and °dONLNd
t¶ˇ≤
_)CallFormatIOProc°dONLNd
Ѷ
_≤
—)` functions check for these .
°dONLNd
ü≥løã(ºlvalues ú`°dONLNd
¶≥ãø
)and call the system openers.°dONLNd
√≈l—r(Œl
Y@Ä°dONLNd
ƒ≈r—
C)/ou should never assume that a value for a systeo °dONLNd
Û≈
C—
r)—
m opener i˙`°dONLNd
˝≈
r—
Ü)/s a fiD °dONLNd≈
á—
¡)xed constant..°dONLNd‹lË
™(Âl5err := CallEditionOpenerProc (selector, PB, routine);°dONLNdGÙl
è*Set the °dONLNdOÙè
ø)#selector°dONLNdWÙø

„)0B parameter to one of the edition opener verbs. The edition opener .
°dONLNdô

l
ß(

lverbs include,Zapf Dingbats°dONLNdß
l
q*
n
.°dONLNd©
x
 Ã)eoCanSubscribe.
°dONLNd∏
)l
0q(
/l
n
.°dONLNd∫
&x
2ú)eoOpen.
°dONLNd¡
;l
Bq(
Al
n
.°dONLNd√
8x
D¢)eoClose.
°dONLNdÀ
Ml
Tq(
Sl
n
.°dONLNdÕ
Jx
VÆ)    eoOpenNew.
°dONLNd◊
_l
fq(
el
n
.°dONLNdŸ
\x
h¥)
eoCloseNew°dONLNd‰
ml
yÄ(
vlThe °dONLNdË
mÄ
yå)PB°dONLNdÍ
må
y›) parameter of the °dONLNd¸
m›
y
[)QCallEditionOpenerProc°dONLNd
m
[
y
›)~ function is an edition opener .
°dONLNd0
zl
Ü∂(
Élparameter block..°dONLNdA
ël
ù
&*TYPE EditionOpenerParamBlock = °dONLNdb
ü~
´¢+RECORD°dONLNdk
≠ê
πÆ+info:°dONLNdu
≠Í
π
V)ZEditionInfoRecord;°dONLNdé
≠
h
π
Ú)~{edition container to }°dONLNd¥
ª
h
«
⁄*{ be subscribed to}°dONLNd 
…ê
’Δ(
“ê    sectionH:°dONLNdÿ
…Í
’
>)ZSectionHandle;°dONLNdÌ
…
h
’
¬)~{publisher or }°dONLNd
◊
h
„
º*{ subscriber }°dONLNd(
Â
h
Ò
‘*{ requesting open}°dONLNd=
Ûê
ˇΔ(
¸ê    document:°dONLNdK
ÛÍ
ˇ
&)Z
FSSpecPtr;°dONLNd\
Û
h
ˇ
Œ)~{document passed}°dONLNdp
êÃ(
ê
fdCreator:°dONLNd
Í
)ZOSType;°dONLNdç

h
Ê)~{Finder creator type}°dONLNd•êΔ(ê    ioRefNum:°dONLNd≥Í
)ZLongInt;°dONLNd¬
h
‘)~{reference number}°dONLNd◊ê)∫(&êioProc:°dONLNd„Í)
J)ZFormatIOProcPtr;°dONLNd˙
h)
‘)~{routine to read }°dONLNd+
h7
§*
{ formats}°dONLNd(9êE¿(Bêsuccess:°dONLNd59ÍE
)ZBoolean;°dONLNdD9
hE
Ê)~{reading or writing }°dONLNdhG
hS
Œ*{ was successful}°dONLNd|Uêaÿ(^êformatsMask:°dONLNdçUÍa
,)ZSignedByte;°dONLNdüU
ha
Ï)~{formats required to }°dONLNdƒc
ho
∞*{ subscribe}°dONLNd“q~}ñ(z~END;ˇ7@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡ä Subscribing to Non-Edition Files

, (‡2-65
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿.°dONLNd\ähû(eäThe ,
Courier°dONLNd\ûh»)routine°dONLNd\»h
)* parameter of the °dONLNd\
h
ó)QCallEditionOpenerProc°dONLNd2\
óh)~ function is a pointer to an .
°dONLNdOiäuÙ(räedition opener function.°dONLNdh{äá
* The following list shows which fi2`°dONLNdâ{
á
„)ì-elds of the edition opener parameter block ar≠°dONLNd∂{
„á)Δ
e used by °dONLNd¿àäîı(ëäthe edition opener verbs¿°dONLNdÿàˆî¯)l
:
    °dONLNd⁄°H¨}(©HOpener verb^@°dONLNdÁ°Œ¨‚)ÜField°dONLNdÌ°
%¨
V)WDescription°dONLNd˘°
£¨
Õ)~
Called by 
°dONLNdˇˇ)+
 
.°dONLNd
ØHªú(∏HeoCanSubscribe,    Symbol.
°dONLNd
Ø∞∫π)h
Æ.^@°dONLNd
!ØŒªÊ)info.
°dONLNd
&Ø
%ª
)WEdition container to °dONLNd
;∫
%Δ
Y*subscribe to] °dONLNd
G∫
ZΔ
\)5
..°dONLNd
IØ
£ª(∏
£NewSubscriberDialo°dONLNd
[∫
£Δ
©*
g°dONLNd
\∫
©Δ)function for a subscriber.
°dONLNd
x ∞’π(”∞
Æ.^@°dONLNd
z Œ÷
)formatsMask.
°dONLNd
Ü 
%÷
O)W    Formats r†°dONLNd
è 
P÷
g)+equir&‡°dONLNd
î 
g÷
)ed to °dONLNd
ö’
%·
Q(fi
%
subscribe.°dONLNd
®Â∞π(Ó∞
¨^@°dONLNd
™ÂŒÒ
)Return value.°dONLNd
∑Â
%Ò
-)W
AÛ`°dONLNd
∏Â
,Ò
.)
 Û`°dONLNd
πÂ
.Ò
L)noErrÛ`°dONLNd
æÂ
LÒ
d) code .
°dONLNd
ƒ
%¸
p(˘
%indicates that an °dONLNd
÷˚
%

Ñ*edition container can °dONLNd
Ï

%

q*be subscribed to. ο°dONLNd
˛

q

x)L
A&`°dONLNd
ˇ

y

{)
 .°dONLNd

%

[(

%    noTypeErr°dONLNd    

[

s)6 code .
°dONLNd

%
(
p(
%
%indicates that an °dONLNd!
'
%
3
r*edition container °dONLNd3
2
%
>
Ñ*cannot be subscribed °dONLNdH
=
%
I
0*to..°dONLNdN
MH
Yl(
VHeoOpen.
°dONLNdU
M∞
Xπ)h
Æ.^@°dONLNdW
MŒ
YÊ)info.
°dONLNd\
M
%
Y
)WEdition container to °dONLNdq
X
%
d
P*
open for r†°dONLNd{
X
Q
d
q),eading..°dONLNdÉ
M
£
Y
Â(
V
£OpenEdition°dONLNdé
M
Â
Y
˙)B and °dONLNdì
X
£
d(
a
£GetStandardFormats°dONLNd•
X
d)l
 .
°dONLNd¶
c
£
o(
l
£functions for a subscriber°dONLNd√
h∞
sπ(
q∞
Æ.^@°dONLNd≈
hŒ
t˛)sectionH.
°dONLNdŒ
h
%
t
w)WSubscriber section °dONLNd·
s
%

(*
rE°dONLNd‚
s
)

z)equesting open or .°dONLNdÙ
~
%
ä
7(
á
%NIL°dONLNd˜
~
7
ä
:)
..
°dONLNd
é∞
ôπ(
ó∞
¨.^@°dONLNd
éŒ
ö˛)ioRefNum.
°dONLNd
é
%
ö
<)WRefer⁄ °dONLNd
é
<
ö
á)ence number for °dONLNd"
ô
%
•
<(
¢
%use bï`°dONLNd'
ô
<
•
G)y I°dONLNd*
ô
H
•
\)/O r3 °dONLNd.
ô
\
•
})outine. °dONLNd6
§
%
∞
m(
≠
%Not the same as .°dONLNdF
Ø
%
ª
s*EditionRefNum°dONLNdS
Ø
s
ª
v)N
..
°dONLNd^
ø∞
 π(
»∞
¨.^@°dONLNd`
øŒ
ÀÚ)ioProc.
°dONLNdg
ø
%
À
<)WI/O r†°dONLNdl
ø
=
À
É)outine to call to °dONLNd~
 
%
÷
((
”
%
rE°dONLNd
 
)
÷
_)ead formats.°dONLNdè
⁄∞
Âπ(
„∞
¨^@°dONLNdë
⁄Œ
Ê
)Return value.°dONLNdû
⁄
%
Ê
-)W
AÛ`°dONLNdü
⁄
,
Ê
.)
 Û`°dONLNd†
⁄
.
Ê
L)noErrÛ`°dONLNd•
⁄
L
Ê
o)     code or .
°dONLNdÆ
Â
%
Ò
9(
Ó
%apprI@°dONLNd≤
Â
:
Ò
h)opriate err© °dONLNdΩ
Â
h
Ò
ã).or code..°dONLNd»
ıH
r(
˛HeoClose.
°dONLNd–
ı∞π)h
Æ.^@°dONLNd“
ıŒ
Ê)info.
°dONLNd◊
ı
%

å)WEdition container to be °dONLNdÔ
%
V*closed for rÒÄ°dONLNd˚
V
v)1eading..°dONLNd
ı
£

Î(
˛
£CloseEdition°dONLNd
ı
Î
)H and °dONLNd
£(    
£GetStandardFormats°dONLNd&)l
 .
°dONLNd'
£(
£functions for a subscriber°dONLNdJ∞π(∞
Æ.^@°dONLNdLŒ˛)sectionH.
°dONLNdU
%
w)WSubscriber section .°dONLNdh
%'
)*
rR`°dONLNdi
)'
x)equesting close or R`°dONLNd|
x'
ä)ONILR`°dONLNd
ä'
ç)
..
°dONLNdä+∞6π(4∞
Æ.^@°dONLNdå+Œ7˛)ioRefNum.
°dONLNdï+
%7
,)W
VÕ °dONLNdñ+
+7
D)alue rÀ@°dONLNdú+
D7
v)eturned by .°dONLNdß6
%B
I(?
%eoOpen°dONLNd≠6
IB
L)$
..
°dONLNd≤F∞Qπ(O∞
Æ.^@°dONLNd¥FŒRÚ)ioProc.
°dONLNdªF
%R
,)W
VÕ °dONLNdºF
+R
D)alue rÀ@°dONLNd¬F
DR
v)eturned by .°dONLNdÕQ
%]
I(Z
%eoOpen°dONLNd”Q
I]
L)$
..
°dONLNdÿa∞lπ(j∞
Æ.^@°dONLNd⁄aŒm¯)success.
°dONLNd‚a
%m
Ñ)WSuccess value passed .°dONLNd˜l
%x
B*to the °dONLNd˛l
Bx
ä)CloseEdition°dONLNd
l
äx
å)H
 .
°dONLNdw
%É
L(Ä
%    function.°dONLNdá∞íπ(ê∞
¨^@°dONLNd áŒì
)Return value.°dONLNd-á
%ì
-)W
AÛ`°dONLNd.á
,ì
.)
 Û`°dONLNd/á
.ì
L)noErrÛ`°dONLNd4á
Lì
o)     code or .
°dONLNd=í
%û
9(õ
%apprI@°dONLNdAí
:û
h)opriate err© °dONLNdLí
hû
ã).or code.X°dONLNd\°
ı™+ç    continuedˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-66    )B Subscribing to Non-Edition Files4^*¿
¯
°dONLNdà2l>z(;lAs @°dONLNdã2{>©)Listing 2-9§Ä°dONLNdñ2©>‚). demonstrate¢¿°dONLNd¢2„>
):s, you iS‡°dONLNd™2
>
≠) &nstall your own edition opener functio‹¿°dONLNd–2
≠>
»)™n by fi—†°dONLNd◊2
…>
ˆ)rst saving °dONLNd‚?lKé(Hlthe curr`°dONLNdÍ?èK
b)#.ent opener and then installing your own opener’°dONLNd?
aK
◊)“. The listing also shows an .°dONLNd4LlX≠(Uledition opener¬†°dONLNdBL¨X√)@, the ,
Courier¬†°dONLNdHL√X
)MyEditionOpener¬†°dONLNdWL
X
t)Z function. When it rï°dONLNdkL
tX
©)Weceives the °dONLNdwYle¿(bleoCanSubscribe°dONLNdÖY¿e
)T opener verb, the °dONLNdóY
e
g)MMyEditionOpener°dONLNd¶Y
ge
Õ)Z function calls another °dONLNdæflr∏(olapplication-defi°dONLNdŒf∏rŒ)Lned rR`°dONLNd”fŒrÔ)outine, R`°dONLNd€fÔr
C)!MyCanSubscribeR`°dONLNdÈf
Cr
⁄)T!. The Edition Manager sends your .
°dONLNd
sl
M(|l7edition opener this verb to help it build the list of fiÄ°dONLNdBs
N
®)‚les displayed by the .°dONLNdWÄlå∫(âlNewSubscriber°dONLNddÄ∫å˘)N function. The °dONLNdsĢå
M)?MyCanSubscribe°dONLNdÅÄ
Må
y)T function rR`°dONLNdåÄ
yå
ñ),eturns R`°dONLNdìÄ
ñå
¥)noErrR`°dONLNdòÄ
¥å
€) if it can .
°dONLNd£çlôπ(ñlsubscribe to the fiG@°dONLNd∂ç∫ô
Œ)NCle; otherwise, it calls the original edition opener to handle the r†°dONLNd˘ç
Ι
Ì(ñ
Œequest..°dONLNdv*Ç`(*    eoOpenNew,    Symbol.
°dONLNd
víÅõ)h
Æ.^@°dONLNdv∞Ç»)info.
°dONLNdv
Ç
a)WEdition container to °dONLNd&Å
ç
R*open for writing..°dONLNd8v
ÖÇ
Ÿ(
ÖOpenNewEdition°dONLNdFv
ŸÇ
€)T
 .
°dONLNdGÅ
Öç
Ì(ä
Öfunction for a publisher°dONLNdbëíúõ(öí
Æ.^@°dONLNddë∞ù‡)sectionH.
°dONLNdmë
ù
U)WPublisher section °dONLNdú
®

*
rE°dONLNdÄú
®
\)equesting open or .°dONLNdíß
≥
(∞
NIL°dONLNdïß
≥
)
..
°dONLNd†∑í¬õ(¿í
Æ.^@°dONLNd¢∑∞√‡)document.
°dONLNd´∑
√
Z)WDocument pointer °dONLNdº¬
Œ
L*passed into the .°dONLNdÃÕ
Ÿ
[*OpenNewEdition°dONLNd⁄Õ
[Ÿ
])T
 .
°dONLNd€ÿ
‰
.(·
    function.°dONLNdÓËíÛõ(Òí
Æ.^@°dONLNdË∞ÙÊ)    fdCreator°dONLNd˙Ë
Ù
)WThe °dONLNd˛Ë
Ù
Q)    fdCreator°dONLNd
Ë
QÙ
S)6
 .
°dONLNd
Û
ˇ
L(¸
passed into the .°dONLNd
˛



[*OpenNewEdition°dONLNd
&˛
[


])T
 .
°dONLNd
'
    


.(

    function.°dONLNd
:
í
$õ(
"í
¨.^@°dONLNd
<
∞
%‡)ioRefNum.
°dONLNd
E


%
)WRefer⁄ °dONLNd
J


%
i)ence number for °dONLNd
Z
$

0
(
-
use bï`°dONLNd
_
$

0
))y I°dONLNd
b
$
*
0
>)/O r3 °dONLNd
f
$
>
0
_)outine. °dONLNd
n
/

;
O(
8
Not the same as .°dONLNd
~
:

F
U*EditionRefNum°dONLNd
ã
:
U
F
X)N
..
°dONLNd
ú
Jí
Uõ(
Sí
¨.^@°dONLNd
û
J∞
V‘)ioProc.
°dONLNd
•
J

V
)WI/O r†°dONLNd
™
J

V
e)outine to call to °dONLNd
º
U

a
E(
^
write formats.°dONLNd
Œ
eí
põ(
ní
¨^@°dONLNd
–
e∞
qÈ)Return value.°dONLNd
›
e

q
)W
AÛ`°dONLNd
fi
e

q
)
 Û`°dONLNd
fl
e

q
.)noErrÛ`°dONLNd
‰
e
.
q
Q)     code or .
°dONLNd
Ì
p

|
(
y
apprI@°dONLNd
Ò
p

|
J)opriate err© °dONLNd
¸
p
J
|
m).or code..°dONLNd
Ä*
åf(
â*
eoCloseNew.
°dONLNd
Äí
ãõ)h
Æ.^@°dONLNd
Ä∞
å»)info.
°dONLNd
Ä

å
n)WEdition container to be °dONLNd1
ã

ó
_*closed after writing..°dONLNdG
Ä
Ö
å
Õ(
â
ÖCloseEdition°dONLNdS
Ä
Õ
å
œ)H
 .
°dONLNdT
ã
Ö
ó
Ì(
î
Öfunction for a publisher°dONLNdu
õí
¶õ(
§í
Æ.^@°dONLNdw
õ∞
߇)sectionH.
°dONLNdÄ
õ

ß
U)WPublisher section .°dONLNdí
¶

≤
*
rR`°dONLNdì
¶

≤
Z)equesting close or R`°dONLNd¶
¶
Z
≤
l)ONILR`°dONLNd©
¶
l
≤
o)
..
°dONLNd¥
∂í
¡õ(
øí
Æ.^@°dONLNd∂
∂∞
¬‡)ioRefNum.
°dONLNdø
∂

¬
)W
VÕ °dONLNd¿
∂

¬
&)alue rÀ@°dONLNdΔ
∂
&
¬
X)eturned by .°dONLNd—
¡

Õ
=(
 
    eoOpenNewï°dONLNd⁄
¡
<
Õ
?)5
..
°dONLNdfl
—í
‹õ(
ڒ
Æ.^@°dONLNd·
—∞
›‘)ioProc.
°dONLNdË
—

›
)W
VÕ °dONLNdÈ
—

›
&)alue rÀ@°dONLNdÔ
—
&
›
X)eturned by .°dONLNd˙
‹

Ë
=(
Â
    eoOpenNewï°dONLNd
‹
<
Ë
?)5
..
°dONLNd
Ïí
˜õ(
ıí
Æ.^@°dONLNd

Ï∞
¯⁄)success.
°dONLNd
Ï

¯
f)WSuccess value passed .°dONLNd'
˜

$*to the °dONLNd.
˜
$
l)CloseEdition°dONLNd:
˜
l
n)H
 .
°dONLNd;

.(
    function.°dONLNdNíõ(í
¨^@°dONLNdP∞È)Return value.°dONLNd]

)W
AÛ`°dONLNd^

)
 Û`°dONLNd_

.)noErrÛ`°dONLNdd
.
Q)     code or .
°dONLNdm
)
(&
apprI@°dONLNdq
)
J)opriate err© °dONLNd|
J)
m).or code.
    °dONLNdˇˇ(p*Opener verb^@°dONLNdˇˇ)ÜField°dONLNdˇˇ)WDescription°dONLNdˇˇ)~
Called by 
°dONLNdˇˇ)+ (continued)ˇ*@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡ä Subscribing to Non-Edition Files

, (‡2-67
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHn4gHn"hH_

ˇ·ˇ‚7^    °dONLNd\äg∂(däListing 2-9°dONLNd\Œg
i)D&Using your own edition opener function,
Courier
.°dONLNd5väÇú(äVAR°dONLNd:Ñúê
Ä+&gOriginalOpener: EditionOpenerProcPtr;°dONLNdaÑ
Äê
Ê)‰{global variable}°dONLNdt†ä¨ê(©ä
P°dONLNdu†ê¨Δ)    ROCEDURE °dONLNd~†Δ¨“)6My°dONLNdĆ“¨
2)InstallMyOpener;°dONLNdëÆä∫®(∑äBEGIN°dONLNdòºú»
¬+1FailOSErr(GetEditionOpenerProc(gOriginalOpener));°dONLNdÀ ú÷
»*2FailOSErr(SetEditionOpenerProc(@MyEditionOpener));°dONLNd˛ÿä‰Æ(·äEND; {°dONLNd
ÿƉ∫)$My°dONLNd
ÿ∫‰
)InstallMyOpener°dONLNd
ÿ
‰
)Z
}°dONLNd
Ùä

‘(˝ä7FUNCTION MyEditionOpener (selector: EditionOpenerVerb; °dONLNd
X



‡+ê!  VAR PB: EditionOpenerParamBlock°dONLNd
y

‡

Ï)Δ) °dONLNd
Ö

,

8(

,: °dONLNd
á

8

b)OSErr; °dONLNd
è
ä
*®(
'äBEGIN°dONLNd
ñ
,ú
8ÿ+
WITH PB DO°dONLNd
¢
:ú
F∫*BEGIN°dONLNd
™
HÆ
T
+CASE selector OF°dONLNd
æ
V¿
b
+eoCanSubscribe:°dONLNd
“
d“
p
∂+&MyEditionOpener := MyCanSubscribe(PB);°dONLNd
¸
r¿
~Í(
{¿eoOpen:°dONLNd
Ä“
å
∞+%MyEditionOpener := MyEditionOpen(PB);°dONLNd1
é¿
ö(
ó¿eoClose:°dONLNd>
ú“
®
∂+&MyEditionOpener := MyEditionClose(PB);°dONLNdh
™¿
∂(
≥¿OTHERWIS°dONLNdp
™
∂ˆ)0
E°dONLNdv
∏“
ƒ
û(
¡“"{call the original edition opener}°dONLNdù
Δ“
“
,*MyEditionOpener°dONLNd¨
Δ
,
“
2)Z
 °dONLNd≥
‘‰
‡Í(
›‰
:°dONLNd¥
‘Í
‡
n)= CallEditionOpenerPro°dONLNd 
‘
n
‡
z)Ñc(°dONLNdÃ
‘
z
‡
¬)selector, PB°dONLNdÿ
‘
¬
‡
»)H
,°dONLNdÁ
‚
t
Ó
z(
Î
t
g°dONLNdË
‚
z
Ó
⁄)OriginalOpener);°dONLNd˚
Æ
¸Ã(
˘ÆEND; °dONLNd
Ã
¸
)    {of CASE}°dONLNd
˛ú
∫(úEND; °dONLNd
˛∫
)    {of WITH}°dONLNdä
(äEND; {MyEditionOpener°dONLNd/

)~
}°dONLNd2(ä4(1äAFUNCTION MyCanSubscribe (VAR PB: EditionOpenerParamBlock): OSErr;°dONLNdt6äB®*BEGIN°dONLNd{DúP+?{check file type to see if it is a file you can emulate as an }°dONLNdºRú^ÿ*
{ edition}°dONLNd»`úl
§*,IF PB.info.fdType = {for example}'PICT' THEN°dONLNd˜nÆz
8+MyCanSubscribe := noErr°dONLNd|úà
⁄(Öú5ELSE {otherwise, let the saved edition opener decide}°dONLNdIä¿ñ
+$7MyCanSubscribe := CallEditionOpenerProc(eoCanSubscribe,°dONLNdâò
§
2+Z    °dONLNdîò
ò§)~PB, gOriginalOpener);°dONLNd™¶ä≤
(ØäEND; {MyCanSubscribe}ˇÄ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-68    )B Subscribing to Non-Edition Files4^*¿
¯

k*r
¯4l*r
¯ mlm
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\lk
 (glOpening and Closing Editionsˇˇˇˇˇˇ€r(g

2
°dONLNdrl~
ï({lBEach time the Edition Manager opens or closes an edition container3°dONLNd`r
ï~
€({
ï, it calls the currh °dONLNdsr
€~
Î)Fent °dONLNdwlãπ(àledition opener prU`°dONLNdàπã◊)Mocedurφ°dONLNdé◊ã
√)5e and passes it an opener verb and a parameter block.°dONLNdƒëlùr(öl
Y@Ä°dONLNd≈ërùÿ)our opener must be car_†°dONLNd€ëÿù
Õ)f4eful when closing documents since a document may alrv °dONLNd
ë
Õù
‰)ıeady °dONLNd
ûl™
C(ßl/have been opened by another application. Be surxÄ°dONLNd
Cû
C™
–)◊e to use the Open/Deny modes °dONLNd
`´l∑
d(¥l8whenever possible. Do not close a document if it was alrˆ@°dONLNd
ò´
d∑
«)¯eady open when your °dONLNd
¨∏lƒÃ(¡lapplication opened it.

È*
¯4Í*
¯ ÎlÎ
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd
ƒ⁄lÈ∑*$Listing Files $°dONLNd
“⁄∏È
Q)LThat Can Be Subscribed ˙Ü°dONLNd
È⁄
PÈ
X)ò
T÷¥°dONLNd
Í⁄
WÈ
^)
oˇˇˇˇˇˇ€r)ô
2
.°dONLNd
Ìl¸Ä(˘lThe ,
Courier°dONLNd
ÒĸÚ)NewSubscriberDialog°dONLNdÚ¸
D)r function calls the °dONLNd
D¸
Ò)R'edition opener function and passes the ˇˇeò°dONLNd?˝l
    r(
l
e°dONLNd@˝r
    ¿)oCanSubscribeˇˇÃà°dONLNdM˝¿
    ˜)N opener verb Âò°dONLNdZ˝˜
    
)7in the ˇˇeò~®°dONLNda˝

    
D)selectorˇˇÃà~®°dONLNdi˝
D
    
w)0 parameter ∏°dONLNdt˝
x
    
Œ)4to build the list of fʇ°dONLNdä˝
Œ
    
˜)V
iles that .
°dONLNdî

l
Á(
lcan be subscribed to. The pr†°dONLNd∞

Ë

˜)|?eview in the subscriber dialog box is generated by calling the .°dONLNdÔ
l
#ÿ(
 lGetStandardFormats°dONLNd

ÿ
#
5)l function (described i°dONLNd

5
#
<)]n °dONLNd

<
#
Ã)“Edition Container Formats” on °dONLNd8
$l
0Ñ(
-lpage °dONLNd=
$Ñ
0ú)2-101°dONLNdB
$ú
0†)
)°dONLNdC
$†
0
#), which calls the format I/O °dONLNd`
$
#
0
-)ÉprR`°dONLNdb
$
-
0
J)
ocedur$¿°dONLNdh
$
J
0
|)e with the $¿°dONLNds
$
|
0
ñ)2verbs $¿°dONLNdy
$
ñ
0
∫)eoOpen$¿°dONLNd
$
∫
0
ø)$, °dONLNdÅ
1l
=Æ(
:lioHasFormat°dONLNdå
1Æ
=≥)B, °dONLNdé
1≥
=◊)ioRead°dONLNdî
1◊
=
)$, and then °dONLNdü
1

=
0)/eoClose°dONLNd¶
1
0
=
@)*. Se°dONLNd™
1
@
=
G)e °dONLNd¨
1
G
=
⁄)“Calling a Format I/O Function”°dONLNdÀ
1
⁄
=
Ë)ì on .
°dONLNdœ
>l
Jô(
Glthis page fg‡°dONLNd⁄
>ö
J
`).,or detailed information on format I/O verbs.


o*
v
¯4
p*
v
¯ 
ql
q
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd
`l
oÓ(
klReading From and WΩ¸°dONLNd
`Ó
o
;)Çriting to Filesˇˇˇˇˇˇ€r(
k

2
°dONLNd+
vl
Çú(
l
The I/O prLÄ°dONLNd5
vù
Ǫ)1ocedur„¿°dONLNd;
vª
Ç◊)e is a r¿°dONLNdC
vÿ
Ç
4)outine that actually r‡°dONLNdY
v
4
Ç
›)\(eads and writes the data. It too has an °dONLNdÅ
Él
è
1(
ål.interface of a selector and a parameter block.°dONLNd∞
ïl
°r*
Tµ¿°dONLNd±
ïq
°“)o override the standarRÄ°dONLNd«
ï”
°fl)bd r≥@°dONLNd 
ïfl
°
m) eading and writing functions, crå`°dONLNdÍ
ï
m
°
‰)éeate an I/O function. Note °dONLNd
¢l
Æ‘(
´lthat you also need to pr¸ °dONLNd
¢‘
Æ
ì)h*ovide your own opener function to call you„†°dONLNdG
¢
î
Æ
ó)¿
r÷@°dONLNdH
¢
ò
Æ
‚) I/O function. Se7Ä°dONLNdY
¢
„
Æ
Í)Ke °dONLNd[
Øl
ª
(
∏l$“Calling an Edition Opener” on page ÍÄ°dONLNd
Ø

ª
$)¶2-64>`°dONLNdÉ
Ø
%
ª
')
..°dONLNdÖ
»l
‘
V(
—l'FUNCTION MyIO (selector: FormatIOVerb; °dONLNd≤
÷Δ
‚
b+ZVAR PB: FormatIOParamBlock°dONLNdÃ
÷
b
‚
n)ú):°dONLNdŒ
÷
n
‚
ò) OSErr;

*
¯4    *
¯ 
l

¯

ˇ·ˇ‚7^ˇˇ‹..
ˇ◊°dONLNd◊
˘l
(lCalling a Format I/O Functionˇˇˇˇˇˇ€r(

2
°dONLNdˆlr(l
Tµ¿°dONLNd˜q
N)1o indicate to the Edition Manager which format I/∞†°dONLNd(
O
Ñ)fiO function t› °dONLNd4
Ñ
¡)5o use, use the .°dONLNdCl(Ã(%lCallFormatIOProc°dONLNdSÃ(ı)`
 function.°dONLNd^3l?
å(<l0err := CallFormatIOProc (selector, PB, routine);ˇ0˙@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡ä Subscribing to Non-Edition Files

, (‡2-69
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿.°dONLNd\äh≠(eäSet the ,
Courier°dONLNd\≠h›)#selector°dONLNd\›h
˝)0@ parameter to one of the format I/O verbs. The format I/O verbs .
°dONLNdPiäu≠(räinclude ,Zapf Dingbats°dONLNdYäÜè*
n
.°dONLNd[|ñàÿ)ioHasFormat.
°dONLNdgëäòè(óä
n
.°dONLNdiéñöfi)ioReadFormat.
°dONLNdv£ä™è(©ä
n
.°dONLNdx†ñ¨ÿ)ioNewFormat.
°dONLNdѵäºè(ªä
n
.°dONLNdÜ≤ñæ‰)ioWriteFormatˇˇ’T°dONLNdî√äœù(ÃäThe ˇˇ¸UT°dONLNdò√ûœ™)PBˇˇ’TUT°dONLNdö√™œ˙) parameter of the ˇˇ¸™§°dONLNd¨√˙œ
Z)PCallFormatIOProcˇˇ’T™§°dONLNdº√
Zœ)`* function contains a format I/O parameter .
°dONLNdʖ䋧(Ÿäblock..°dONLNdÌÁäÛ
&*TYPE FormatIOParamBlock = °dONLNd
    ıú

¿+RECORD°dONLNd

Æ
‰+    ioRefNum:°dONLNd
 



8)ZLongInt;°dONLNd
-

b

Œ)Z{reference number}°dONLNd
B
Æ
ÿ(
Æformat:°dONLNd
N



J)ZFormatType;°dONLNd
^

b

‡)Z{edition format type}°dONLNd
v
Æ
+(
(ÆformatIndex°dONLNd
Ç

+ˆ)B
:°dONLNd
á


+
8)LongInt;°dONLNd
î

b
+)Z{opener-specific enumeration }°dONLNd
ø
-
b
9
∞*{ of formats}°dONLNd
œ
;Æ
Gÿ(
DÆoffset:°dONLNd
€
;

G
8)ZLongInt;°dONLNd
Ë
;
b
G
⁄)Z{offset into format}°dONLNd
ˇ
IÆ
Ufi(
RÆbuffPtr:°dONLNd
I

U
 )ZPtr;°dONLNd
I
b
U
Œ)Z{data starts here}°dONLNd*
WÆ
cfi(
`ÆbuffLen:°dONLNd7
W

c
8)ZLongInt;°dONLNdD
W
b
c
¬)Z{length of data}°dONLNdV
eú
q¥(
núEND;°dONLNd[
}ä
âû(
ÜäThe °dONLNd_
}û
â»)routine°dONLNdf
}»
â
)* parameter of the °dONLNdx
}

â
y)QCallFormatIOProc°dONLNdà
}
y
â)`" function is a pointer to a format.
°dONLNd´
ää
ñ≈(
ìäI/O function..°dONLNdπ
úä
®
#* The following list shows which fi°dONLNd⁄
ú
#
®
C)ôelds of °dONLNd‚
ú
C
®
Ø) FormatIOParamBlock°dONLNdÙ
ú
Ø
®
ª)l arR`°dONLNd˜
ú
ª
®
˜)e used by the .
°dONLNd
©ä
µ™(
≤äformat “`°dONLNd
©™
µ—) I/O verbÜ °dONLNd
©“
µÿ)(s:
    °dONLNd
¬H
Õ|(
 HFormat I/O vˇ–°dONLNd#
¬|
͊)4erb校dONLNd(
¬Õ
Õ˘)Q    Parameter{ °dONLNd2
¬
$
Õ
U)WDescription{ °dONLNd>
¬
•
Õ
œ)Å
Called by ¸ °dONLNdˇˇ)*
 
.°dONLNdU
–H
‹ä(
ŸHioHasFormat,    Symbol.
{ °dONLNda
–Ø
€∏)g
Æ.ʆ°dONLNdc
–Õ
‹˝)ioRefNum.
{ °dONLNdl
–
$
‹
;)WI/O r    ¿°dONLNdq
–
<
‹
L)eferµ‡°dONLNdu
–
L
‹
á)ence number { °dONLNdÅ
€
$
Á
'(
‰
$
r@ °dONLNdÇ
€
(
Á
y)eturned by opener$‡°dONLNdì
€
y
Á
{)Q
..{ °dONLNdï
–
•
‹(
Ÿ
•EditionHasFormat{ °dONLNd•
–
‹
)`, { °dONLNdß
€
•
Á(
‰
•GetStandardFormats{ °dONLNdπ
€
Á)l, { °dONLNdª
Ê
•
Ú
∏(
Ô
•and { °dONLNdø
Ê
∏
Ú
˙)ReadEdition{ °dONLNd 
Ê
˙
Ú
¸)B
 .
{ °dONLNdÀ
Ò
•
˝
Œ(
˙
•    functions{ °dONLNd◊
ÎØ
ˆ∏(
ÙØ
Æ.ʆ°dONLNdŸ
ÎÕ
˜Ò)format.
{ °dONLNd‡
Î
$
˜
Ñ)WCheck for this format.{ °dONLNd˙
˚Ø∏(Ø
¨.ʆ°dONLNd¸
˚Õ
)formatIndex.
{ °dONLNd
˚
$
[)WAn optional { °dONLNd
$
z*enumeration of the { °dONLNd'
$
m*supplied format.{ °dONLNd;!Ø,∏(*Ø
¨.ʆ°dONLNd=!Õ-˜)buffLen.
{ °dONLNdE!
$-
P)WIf found, r0 °dONLNdP!
Q-
{)-
eturn the { °dONLNdZ,
$8
ä(5
$length size or –1 if size { °dONLNdt7
$C
Z*is unknown.{ °dONLNdÉGØR∏(PØ
¨ʆ°dONLNdÖGÕS
)Return value.{ °dONLNdíG
$S
,)W
AÓÄ°dONLNdìG
+S
-)
 ÓÄ°dONLNdîG
-S
K)noErrÓÄ°dONLNdôG
KS
X) or { °dONLNdùR
$^
Z([
$    noTypeErr{ °dONLNd¶R
Z^
s)6 code..
” °dONLNd¥a
˝j+£    continuedˇÇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-70    )B Subscribing to Non-Edition Files4^*¿
¯
°dONLNd@lLÏ(IlThe marks for each format ar≠ °dONLNd1@ÏL
q)Äe kept by the Edition ManagerÓ@°dONLNdN@
qL
≤)Ö. The format I/Í °dONLNd]@
≥L
‰)BO function °dONLNdhMlYq(Vl
oıÄ°dONLNdiMqYŸ)nly needs to be able to rª`°dONLNdÇM⁄Y
j)i!ead or write, beginning at any ofπ‡°dONLNd£M
jY
‚)êfset. If you know that your °dONLNdøZlf≈(clapplication always r`°dONLNd”ZΔf˛)Zeads an entirÖ‡°dONLNd‡Z˛f
[)8e format sequentially“†°dONLNdıZ
Zf
õ)\, you can ignor£`°dONLNdZ
úf
º)Be the ofÊ °dONLNdZ
ºf
–) fset. ,
Courier.°dONLNdv*Çr(*ioReadFormat,    Symbol.
{ °dONLNdvëÅö)g
Æ.ʆ°dONLNdvØÇfl)ioRefNum.
{ °dONLNdv
Ç
)WI/O r    ¿°dONLNdv
Ç
.)eferµ‡°dONLNd!v
.Ç
i)ence number { °dONLNd-Å
ç
    (ä

r@ °dONLNd.Å

ç
[)eturned by opener$‡°dONLNd?Å
[ç
])Q
..{ °dONLNdAv
áÇ
…(
áReadEdition{ °dONLNdLv
…Ç
fi)B and { °dONLNdQÅ
áç
Û(ä
áGetStandardFormats{ °dONLNdcÅ
Ûç
ı)l
 .
{ °dONLNddå
áò
∞(ï
á    functions{ °dONLNdpëëúö(öë
Æ.ʆ°dONLNdrëØù”)format.
{ °dONLNdyë
ù
K)WGet this format.{ °dONLNdç°ë¨ö(™ë
Æ.ʆ°dONLNdè°Ø≠Ò)formatIndex.
{ °dONLNdõ°
≠
)W
V»@°dONLNdú°
≠
%)alue rΔ`°dONLNd¢°
%≠
W)eturned by .{ °dONLNd≠¨
∏
H(µ
ioHasFormat{ °dONLNd∏¨
H∏
K)B
..
{ °dONLNdΩºë«ö(≈ë
Æ.ʆ°dONLNdøºØ»”)offset.
{ °dONLNdΔº
»
n)WRead format beginning { °dONLNd‹«
”
*frî°dONLNdfi«
”
9)
om this of≤`°dONLNdË«
9”
K),fset.{ °dONLNdÒ◊ë‚ö(‡ë
Æ.ʆ°dONLNdÛ◊Ø„Ÿ)buffPtr.
{ °dONLNd˚◊
„
k)WPut data beginning her¿¿°dONLNd
◊
k„
r)ee.{ °dONLNd
ÁëÚõ(ë
´.ʆ°dONLNd
ÁØÛŸ)buffLen.
{ °dONLNd
!Á
Û
7)WSpecify buf˜@°dONLNd
,Á
7Û
o)1fer length to { °dONLNd
:Ú
˛
    (˚

r@ °dONLNd
;Ú

˛
6)
ead, and rW†°dONLNd
EÚ
6˛
m),eturn actual { °dONLNd
R˝

    
.(

amount r$Ä°dONLNd
Z˝
/
    
R))eceived.{ °dONLNd
f
ë
ö(
ë
¨ʆ°dONLNd
h
Ø
Ë)Return value.{ °dONLNd
u



)W
AÓÄ°dONLNd
v



)
 ÓÄ°dONLNd
w



-)noErrÓÄ°dONLNd
|

-

S)
 code, or .
{ °dONLNd
Ü


$
(
!
apprD`°dONLNd
ä


$
I)opriate err§@°dONLNd
ï

I
$
l).or code..°dONLNd
†
(*
4l(
1*ioNewFormat.
{ °dONLNd
¨
(ë
3ö)g
Æ.ʆ°dONLNd
Æ
(Ø
4fl)ioRefNum.
{ °dONLNd
∑
(

4
)WI/O r    ¿°dONLNd
º
(

4
.)eferµ‡°dONLNd
¿
(
.
4
i)ence number { °dONLNd
Ã
3

?
    (
<

r@ °dONLNd
Õ
3


?
[)eturned by opener$‡°dONLNd
fi
3
[
?
])Q
..{ °dONLNd
‡
(
á
4
ˇ(
1
áSetEditionFormatMark{ °dONLNd
Ù
3
á
?
ç*
a{ °dONLNd
ı
3
ç
?
ö)nd { °dONLNd
¯
3
ö
?
‚)WriteEdition{ °dONLNd
3
‚
?
‰)H
 .
{ °dONLNd
>
á
J
∞(
G
á    functions{ °dONLNd
Cë
Nö(
Lë
Æ.ʆ°dONLNd
CØ
O”)format.
{ °dONLNd
C

O
)WCrW °dONLNd
C

O
X)eate this format.{ °dONLNd1
Së
^ö(
\ë
¨.ʆ°dONLNd3
SØ
_Ò)formatIndex.
{ °dONLNd?
S

_
=)WAn optional { °dONLNdK
^

j
\*enumeration of the { °dONLNd^
i

u
O*supplied format.{ °dONLNdr
yë
Ñö(
Çë
¨ʆ°dONLNdt
yØ
ÖË)Return value.{ °dONLNdÅ
y

Ö
)W
AÓÄ°dONLNdÇ
y

Ö
)
 ÓÄ°dONLNdÉ
y

Ö
-)noErrÓÄ°dONLNdà
y
-
Ö
S)
 code, or .
{ °dONLNdí
Ñ

ê
(
ç
apprD`°dONLNdñ
Ñ

ê
I)opriate err§@°dONLNd°
Ñ
I
ê
l).or code..°dONLNd¨
î*
†x(
ù*ioWriteFormat.
{ °dONLNd∫
îë
üö)g
Æ.ʆ°dONLNdº
îØ
†fl)ioRefNum.
{ °dONLNd≈
î

†
)WI/O r    ¿°dONLNd 
î

†
.)eferµ‡°dONLNdŒ
î
.
†
i)ence number { °dONLNd⁄
ü

´
    (
®

r@ °dONLNd€
ü


´
[)eturned by opener$‡°dONLNdÏ
ü
[
´
])Q
..{ °dONLNdÓ
î
á
†
œ(
ù
áWriteEdition{ °dONLNd˙
î
œ
†
ı)H     function.
{ °dONLNd
Øë
∫ö(
∏ë
Æ.ʆ°dONLNd
ØØ
ª”)format.
{ °dONLNd
Ø

ª
K)WGet this format.{ °dONLNd#
øë
 ö(
ȑ
Æ.ʆ°dONLNd%
øØ
ÀÒ)formatIndex.
{ °dONLNd1
ø

À
)W
V»@°dONLNd2
ø

À
%)alue rΔ`°dONLNd8
ø
%
À
W)eturned by .{ °dONLNdC
 

÷
H(
”
ioNewFormat{ °dONLNdN
 
H
÷
K)B
..
{ °dONLNdS
ڑ
Âö(
„ë
Æ.ʆ°dONLNdU
گ
Ê”)offset.
{ °dONLNd\
⁄

Ê
)W
WΩ¿°dONLNd]
⁄

Ê
o)    rite format beginning { °dONLNds
Â

Ò
(
Ó
frî°dONLNdu
Â

Ò
9)
om this of≤`°dONLNd
Â
9
Ò
K),fset.{ °dONLNdà
ıëö(
˛ë
Æ.ʆ°dONLNdä
ıØ
Ÿ)buffPtr.
{ °dONLNdí
ı


k)WGet data beginning her¿°dONLNd®
ı
l

s)fe.{ °dONLNdÆëõ(ë
´.ʆ°dONLNd∞ØŸ)buffLen.
{ °dONLNd∏

7)WSpecify buf˜@°dONLNd√
7
o)1fer length to { °dONLNd—

(
write.{ °dONLNd€ ë+ö()ë
¨ʆ°dONLNd› Ø,Ë)Return value.{ °dONLNdÍ 
,
)W
AÓÄ°dONLNdÎ 
,
)
 ÓÄ°dONLNdÏ 
,
-)noErrÓÄ°dONLNdÒ 
-,
P)     code or .
{ °dONLNd˙+
7
(4
apprD`°dONLNd˛+
7
I)opriate err§@°dONLNd    +
I7
i).or codeWÄ°dONLNd+
j7
l)!
.
    °dONLNdˇˇ(p*Format I/O vˇ–°dONLNdˇˇ)4erbʆ°dONLNdˇˇ)Q    Parameter{ °dONLNdˇˇ)WDescription{ °dONLNdˇˇ)Å
Called by ¸ °dONLNdˇˇ)* (continued)ˇ8Ä@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-71
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

^Hx4^Hx

àHê4âHê äHä

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNduHàÏ(ÉHEdition Manager Refer?z°dONLNduÏà
)§enceˇˇˇˇˇˇV˛(É
2
°dONLNdô䕸(¢äThis section describes the Y@°dONLNd6ô˝•
)sdata strï`°dONLNd>ô
•
5)!uctur@°dONLNdCô
6•
T)es and °dONLNdJô
U•
X)
r‘°dONLNdKô
X•
t)outine`°dONLNdQô
u•
ò)    s that arnÄ°dONLNdZô
ò•
ª)#e specifi&@°dONLNdcô
º•
fi)$    c to the °dONLNdl¶ä≤≠(ØäEdition ëÄ°dONLNdt¶≠≤‘)#Managerf °dONLNd{¶‘≤
)'. The “Data StrÇ@°dONLNdä¶
≤
,)Auctur °dONLNdè¶
-≤
Ë),es” section describes the edition container °dONLNdª≥äøç(ºä
rE°dONLNdº≥éø†)ecorπ`°dONLNd¿≥†ø®)d U °dONLNd¬≥©øÚ)    and the section rM °dONLNd”≥Úø
)Iecor¡Ä°dONLNd◊≥
ø)8d. The “Edition Manager Routines” section describes the °dONLNd
¿äÃç(…ä
rE°dONLNd
¿éÃ
€)Joutines your application can use to implement publish and subscribe featur— °dONLNd
Z¿
€Ã
Ò(…
€es in °dONLNd
`Õ䟰(÷äyour ˛`°dONLNd
eÕ°Ÿ’)application.


H
4
H
 
H


ˇ·ˇ‚7^°dONLNd
sıH
z(

HData Str∫ °dONLNd
{ız
õ)2uctur®¿°dONLNd
Äıõ
ß)!esˇˇˇˇˇˇ(


2
°dONLNd
Ñ
ä

N(
ä.This section describes the edition container rÕ °dONLNd
≤

N

`)ƒecorAÄ°dONLNd
∂

a

≤)d and the section r’@°dONLNd
…

≤

ƒ)QecorI†°dONLNd
Õ

≈

·)d. See ∏`°dONLNd
‘

·

¯)page ì@°dONLNd
Ÿ

˘
)2-91Á °dONLNd
›

)
 °dONLNd
fi
ä
&
:(
#ä)for a description of the new subscriber rì°dONLNd

:
&
S)∞eply r@°dONLNd

T
&
f)ecor膰dONLNd

f
&
q)d, ´`°dONLNd

q
&
à)page Ü@°dONLNd

â
&
õ)2-93⁄ °dONLNd

õ
&) for a description of the °dONLNd7
'ä
3–(
0änew publisher rc@°dONLNdF
'–
3È)Feply rÎÄ°dONLNdL
'È
3˚)ecor_‡°dONLNdP
'¸
3
)d, {†°dONLNdS
'

3
)page VÄ°dONLNdX
'

3
1)2-95™`°dONLNd\
'
1
3
„)+ for a description of the section options r¬@°dONLNdá
'
„
3
ı)≤ecor6†°dONLNdã
'
ˆ
3)d, and °dONLNdí
4ä
@°(
=äpage Z‡°dONLNdó
4¢
@¥)2-99Æ¿°dONLNdõ
4¥
@
V)( for a description of the edition info rz`°dONLNd√
4
W
@
i)£ecorÓ¿°dONLNd«
4
i
@
¸)"d. For information on the edition °dONLNdÈ
Aä
M
ö(
Jä;opener parameter block and format I/O parameter block, see °dONLNd$
A
õ
M
≤(
J
õpage Ó‡°dONLNd)
A
≤
M
…)2-103B¿°dONLNd.
A
 
M
fl) and /‡°dONLNd3
A
‡
M
˜)page 
¿°dONLNd8
A
¯
M)2-104^†°dONLNd=
A
M), °dONLNd?
Nä
Zç(
Wä
rE°dONLNd@
Né
Zø)espectively~°dONLNdK
Næ
Z¿)0
.


~H
Ü4
H
Ü 
ÅH
Å

ˇ·ˇ‚7^°dONLNdN
qH
fl(
{HThe Edition Container Recor∫@°dONLNdi
qfl
Ê)ó
dˇˇˇˇˇˇ(
{
2
°dONLNdl
Üä
íÎ(
èäAn edition container rÄ°dONLNdÇ
ÜÏ
í˛)becorć°dONLNdÜ
ܲ
í
&)    d identifiÛ@°dONLNdê
Ü
&
í
U)(es a specifih°dONLNdú
Ü
V
í
Ñ)0c edition fi$`°dONLNd®
Ü
Ö
í
˚)/le. Many Edition Manager °dONLNd¡
ìä
üç(
úä
rE°dONLNd¬
ìé
ü¥)    outines r    `°dONLNdÀ
ìµ
üÃ)'equir †°dONLNd–
ìÃ
ü
2)e an edition container r/Ä°dONLNdË
ì
2
ü
D)fecor£‡°dONLNdÏ
ì
D
ü
ç)d as a parameterP@°dONLNd¸
ì
ç
ü
•)I. The ,
Courier.°dONLNd
†ä
¨
(
©äEditionContainerSpec°dONLNd
†

¨
B)x data type defPÄ°dONLNd$
†
B
¨
∂)@ines an edition container r"‡°dONLNd?
†
∂
¨
»)tecorı@°dONLNdC
†
«
¨
–)d.°dONLNdF
∑ä
√
2(
¿äTYPE EditionContainerSpec = °dONLNdd
≈ú
—¿+RECORD°dONLNdm
Ӯ
flfi+theFile:°dONLNd{
”

fl
D)lFSSpec;°dONLNdá
”
t
fl)Z{file containing edition }°dONLNdØ
·
t
Ì
û*{ data}°dONLNdπ
ÔÆ
˚
(
¯ÆtheFileScript:°dONLNdÕ
Ô

˚
\)lScriptCode;°dONLNd›
Ô
t
˚
)Z{script code of filename}°dONLNd˘
˝Æ    fi(ÆthePart:°dONLNd
˝
    
J)lLongInt;°dONLNd
˝
t    
¯)Z{which part of file, }°dONLNd8
t
˛*{ always kPartsNotUsed}°dONLNdRÆ%ˆ("ÆthePartName:°dONLNdd
%
>)lStr31;°dONLNdo
t%
∞)Z
{reserved}°dONLNd|'Æ3
(0ÆthePartScript:°dONLNdê'
3
\)lScriptCode;°dONLNd†'
t3
∞)Z
{reserved}°dONLNd¨5úA¥(>úEND;

NH]4OH]
    .
°dONLNd±NäY÷(VäField descriptions

ˇ·ˇ‚7^
.°dONLNdƒ[äg¥*theFile.
°dONLNdÃ[ÊgÌ)\
A∫†°dONLNdÕ[Ìgı) fiG`°dONLNd–[ˆg
)        le specifiÁÄ°dONLNd⁄[
g
@)&    ciation rˆ¿°dONLNd„[
@g
R)$ecork °dONLNdÁ[
Sg
è)d that identifi≥†°dONLNdˆ[
èg
)<es the name and location of °dONLNdgÊs
(pÊthe edition fi©Ä°dONLNd g
s
c)8le. Specify the fiå¿°dONLNd2g
ds
∫)Fle using the standarZ†°dONLNdFg
ªs
)Wd conventions for °dONLNdXsÊÏ(|Ê
fiå¿°dONLNdZsÏ
)    le specifi,‡°dONLNdds

4)'cation rS¿°dONLNdls
4
F)!ecor» °dONLNdps
F
‡)$ds as described in the chapter “IntrI@°dONLNdîs
·)õoduction to °dONLNd†Êã
E(àÊFile Management” in 4°dONLNd¥
Fã
£)`Inside Macintosh: Files˙‡°dONLNdÀ
£ã
•)]
..°dONLNdŒéäöÿ(óätheFileScript.
°dONLNd‹éÊöÌ)\
A∫†°dONLNd›éÌö
U) script code that identifi@°dONLNd˜é
Vö
˝)i'es the script in which the name of the °dONLNdöʶ
ù(£Ê)document is to be displayed in the FinderÉ@°dONLNdGö
ù¶
¢)∑. $‡°dONLNdIö
¢¶
©)
A_Ä°dONLNdJö
©¶
È) script code of .°dONLNdZ¶Ê≤
:(ØÊsmSystemScript°dONLNdh¶
:≤
@)T rR`°dONLNdj¶
@≤
O)epr$¿°dONLNdm¶
O≤
‡)!esents the default system script.ˇÄ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-72    )BEdition Manager Reference4^*¿
¯,
Courier
.°dONLNd\lhñ(elthePart°dONLNd\»h–)\
AÛ`°dONLNd    \œh
e)" value that must always be set to Û`°dONLNd+\
eh
≥)ñkPartsNotUsedÛ`°dONLNd8\
≥h
Î)N in System 7.°dONLNdFklwÆ(tlthePartName.
°dONLNdRk»wÛ)\    Reserved..°dONLNd\zlÜ∫(ÉlthePartScript.
°dONLNdjz»ÜÛ)\    Reserved.

©*±
¯4™*±
¯ ¨*¨
˛

ˇ·ˇ‚7^°dONLNduú*™à(¶*The Section Recor@°dONLNdÜúâ™ê)_
dˇˇˇˇˇˇ(¶
Ú
2
°dONLNdâ±lΩs(∫l
A∫†°dONLNdä±sΩö)
 section rh °dONLNdî±õΩ≠)(ecor‹Ä°dONLNdò±≠Ω’)    d identifiN‡°dONLNd¢±÷Ω
))es a specifi√†°dONLNdƱ
Ω
…)//c publisher or subscriber section. It contains °dONLNd›æl 
Ü(«lBinformation to identify the section as a publisher or a subscriber‡°dONLNd
æ
Ü 
’(«
Ü, a time stamp to r¨†°dONLNd
2æ
’ 
Á)Oecor!°dONLNd
6æ
Ë 
)d °dONLNd
8Àl◊´(‘lthe last modifiÄ°dONLNd
GÀ¨◊
])@)cation of the section, and unique identifiˇ °dONLNd
qÀ
]◊
‡)±cation for each section. Many °dONLNd
èÿl‰Ω(·lEdition Manager rhÄ°dONLNd
†ÿΩ‰„)Q    outines r,‡°dONLNd
©ÿ‰‰˚)'equirD °dONLNd
Æÿ˚‰
b)e a handle to a section r㠡dONLNd
«ÿ
b‰
t)gecorX°dONLNd
Àÿ
u‰
æ)d as a parameter`°dONLNd
€ÿ
æ‰
÷)I. The .°dONLNd
·ÂlÒ∫(ÓlSectionRecord°dONLNd
ÓÂ∫Ò˙)N data type defPÄ°dONLNd
¸Â˙Ò
;)@ines a section r"‡°dONLNdÂ
;Ò
M)Aecorı@°dONLNdÂ
LÒ
U)d.°dONLNd¸l
Í(
lTYPE SectionRecord = °dONLNd*

~
¢+RECORD°dONLNd3
ê
$¿+version:°dONLNd@
Í
$
,)ZSignedByte;°dONLNdP

D
$
™)Z{always 1 in 7.0}°dONLNdd
&ê
2Æ(
/êkind:°dONLNdn
&Í
2
2)ZSectionType;°dONLNd
&
D
2
⁄)Z{publisher or subscriber}°dONLNdõ
4ê
@Æ(
=êmode:°dONLNd•
4Í
@
,)ZUpdateMode;°dONLNdµ
4
D
@
¬)Z{automatic or manual}°dONLNdÕ
Bê
N∫(
KêmdDate:°dONLNdŸ
BÍ
N
&)Z
TimeStamp;°dONLNdË
B
D
N
⁄)Z{last change in document}°dONLNd
Pê
\Ã(
Yê
sectionID:°dONLNd
PÍ
\
)ZLongInt;°dONLNd 
P
D
\
‘)Z{application-specific, }°dONLNdE
^
D
j
»*{ unique per document}°dONLNd^
lê
x∫(
uêrefCon:°dONLNdj
lÍ
x
)ZLongInt;°dONLNdw
l
D
x
»)Z{application-specific}°dONLNdê
zê
Ü¥(
Éêalias:°dONLNdõ
zÍ
Ü
2)ZAliasHandle;°dONLNd¨
z
D
Ü
‘)Z{handle to alias record}°dONLNd»
ñê
¢
Ê(
üê9{The following fields are private and are set up by the }°dONLNd
§ê
∞
⁄*7{ RegisterSection function. Do not modify the private }°dONLNd>
≤ê
æÃ*
{ fields.}°dONLNdK
¿ê
ÿ*subPart:°dONLNdX
¿Í
Ã
)ZLongInt;°dONLNde
¿
D
Ã
z)Z    {private}°dONLNdq
ΐ
⁄ÿ(
◊ênextSection:°dONLNdÇ
ŒÍ
⁄
>)ZSectionHandle;°dONLNdï
Œ
D
⁄
Ê)Z{private, do not use as a }°dONLNdΩ
‹
D
Ë
ò*{ linked list}°dONLNdŒ
Íê
ˆfi(
ÛêcontrolBlock:°dONLNd‡
ÍÍ
ˆ
)ZHandle;°dONLNdÏ
Í
D
ˆ
Ú)Z{may be used for comparison }°dONLNd
¯
D
n*{ only}°dONLNd ê∫(êrefNum:°dONLNd,Í
>)ZEditionRefNum;°dONLNd?
D
z)Z    {private}°dONLNdIl Ñ(lEND;

-*<
¯4.*<
¯
    .
°dONLNdN-l8∏*Field descriptions

ˇ·ˇ‚7^
.°dONLNda:lFñ*version.
°dONLNdi:»F
g)\&Indicates the version of the section rm†°dONLNdè:
gF
y)üecor‚°dONLNdì:
yF
ñ)d, curr,¿°dONLNdö:
óF
¡)
ently $01..°dONLNd¶IlUÑ(Rlkind.
°dONLNd´I»U⁄)\Defi†°dONLNdØI€U
Î)@nes the section type as either publisher or subscriber with the .°dONLNdÔU»a

(^»stPublisher°dONLNd˙U

a
)B or °dONLNd˛U
a
_)stSubscriber°dONLNd
U
_a
â)H
 constant.°dONLNddlpÑ(mlmode.
°dONLNdd»p
*)\Indicates if editions arj‡°dONLNd2d
*p
Œ)b#e updated automatically or manuallyg‡°dONLNdUd
Õp
œ)£
.ˇ6¿@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-73
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\ähÆ(eämdDate.
°dONLNd\Êh
r)\Indicates which version (modifiº†°dONLNd&\
rh)å'cation date) of the section’s contents ˇˇ‚™.°dONLNdMhÊt
∂(qÊ/is contained within the publisher or subscriberú°dONLNd|h
∂t
Œ)–. The ˇˇß˛◊°dONLNdÇh
Œt
Ú)mdDateˇˇ‚™◊°dONLNdàh
Út
˙)$ fi∫ö°dONLNdãh
˚t)    eld is .
°dONLNdítÊÄ
>(}Êset to 0 when you cr@°dONLNd¶t
?Ä)Y-eate a new subscriber section and to the curr˛†°dONLNd”tÄ)√ent °dONLNd◊ÄÊå
3(âÊtime when you crÿ°dONLNdÁÄ
3å
é)Meate a new publisherÉ@°dONLNd˚Ä
éå
Æ)[. Be surÒ¿°dONLNd
Ä
Æå
˙) e to update this fiÍ °dONLNd
Ä
˚å)Meld °dONLNd
åÊò
|(ïÊ!each time publisher data is modifi›¿°dONLNd
<å
|ò
‰)ñed. The section’s modifiΔ°dONLNd
Tå
Âò)ication °dONLNd
[òʧ
&(°Êdate is comparN°dONLNd
iò
'§
ñ)Aed to the edition’s modifif†°dONLNd
Éò
ñ§)ocation date to determine °dONLNd
ú§Ê∞
˝(≠Ê?whether the section and the edition contain the same data. The °dONLNd
€∞ʺ
$*section modifiB‡°dONLNd
È∞
%º
Î)?.cation date is displayed in the publisher and °dONLNdºÊ»
á(≈Ê%subscriber options dialog boxes. See .†°dONLNd<º
à»
Ù)¢“Closing an Edition” on °dONLNdT»Ê‘˝(—Êpage Z‡°dONLNdY»˛‘
)2-28Æ¿°dONLNd]»
‘
) for detailed information..°dONLNdx◊ä„¿(‡ä    sectionID.
°dONLNdÇ◊Ê„Ô)\PrN†°dONLNdÑ◊„
˛)
;ovides a unique number for each section within a document. °dONLNdø„ÊÔÌ(ÏÊ
A∫†°dONLNd¿„ÌÔÔ)
 :†°dONLNd¡„Ô
ì)%simple way to implement this is to crs†°dONLNdÊ„
ìÔ
¯)£eate a counter for each °dONLNd˛ÔÊ˚
ˇ(¯Ê>document that is saved to disk with the document. The counter °dONLNd<˚Ê

ê*)should start at 1. The section ID is currö@°dONLNde˚
ê

Í)™ently used as a tie br†°dONLNd{˚
Î
)[    eaker in .°dONLNdÑ
Ê
¯(
Êthe °dONLNdà
¯

p)GoToPublisherSection°dONLNdú

p

«)x function when therR`°dONLNdØ

«

ÿ)We ar$¿°dONLNd≥

ÿ
    )e multiple .
°dONLNdæ
Ê
(
ÊDpublishers to the same edition in a single document. The section ID °dONLNd
Ê
+
X*should not be 0 or –1. See $¿°dONLNd

Y
+)s)“Duplicating Publishers and Subscribers” °dONLNdF
+Ê
7
(
4Êon page !¿°dONLNdN
+

7
)&2-58u†°dONLNdR
+

7
Õ)( for information on multiple publishers..°dONLNd{
:ä
FÆ(
CärefCon.
°dONLNdÇ
:Ê
F˝)\Refer⁄ °dONLNdá
:˝
F
Δ).ence constant available for application-specififi¿°dONLNd∂
:
Δ
F
fi)…c use..°dONLNdΩ
Iä
U®(
Räalias.
°dONLNd√
IÊ
U
n)\ Contains a handle to the alias rÔÄ°dONLNd„
I
n
U
Ä)àecorc‡°dONLNdÁ
I
Å
U)"d for a particular section within °dONLNd    
UÊ
a
(
^Êa document..°dONLNd
fä
rÍ(
oäWhenever the user crR`°dONLNd)
fÍ
r
q)`eates a publisher or subscriberï°dONLNdH
f
p
r
õ)Ü, call the ï°dONLNdS
f
õ
r
◊)+
NewSectionï°dONLNd]
f
◊
r
ˇ)<
 function .
°dONLNdg
sä
»(
|ä(described on ı`°dONLNdu
s»
fl)>page –@°dONLNdz
s‡
Ú)2-75$ °dONLNd~
sÛ

)) to cre °dONLNdÖ
s


M)eate a section rh@°dONLNdï
s
M

_)Aecor‹†°dONLNdô
s
_

ï)d and alias r8@°dONLNd¶
s
ñ

®)7ecor¨†°dONLNd™
s
®

∞)d.


´H
≥4
¨H
≥ 
ÆH
Æ

ˇ·ˇ‚7^°dONLNdÆ
õH
´≥(
ßHEdition Manager ~Ä°dONLNdæ
õ¥
´Í)lRoutinesˇˇˇˇˇˇ(
ß
2
°dONLNd»
≥ä
ø
(
ºäThis section describes the r@°dONLNd‰
≥


ø
Q)woutines you use to,Zapf Dingbats°dONLNd˜
…ä
–è(
ϊ
n
°dONLNd˘
Δñ
“
)initialize the Edition Manager°dONLNd
ۊ
‚è(
·ä
n
°dONLNd
ÿñ
‰û)crµ@°dONLNd
ÿû
‰…)
eate and r=°dONLNd&
ÿ 
‰
),egister a section°dONLNd8
Ìä
Ùè(
Ûä
n
°dONLNd:
Íñ
ˆû)crµ@°dONLNd<
Íû
ˆ
;)$eate and delete an edition container°dONLNda
ˇäè(ä
n
°dONLNdc
¸ñ
)set and locate a format mark°dONLNdÄäè(ä
n
°dONLNdÇñô)
rE°dONLNdÉöÏ)ead in edition data°dONLNdó#ä*è()ä
n
°dONLNdô ñ,ˆ)write out edition data°dONLNd∞5ä<è(;ä
n
°dONLNd≤2ñ>¯)close an edition after r}°dONLNd 2¯>
E)beading or writing°dONLNd‹GäNè(Mä
n
°dONLNdfiDñP)display dialog boxes°dONLNdÛYä`è(_ä
n
°dONLNdıVñb
")!locate a publisher and edition frK¿°dONLNdV
#b
h)çom a subscriber°dONLNd&kärè(qä
n
°dONLNd(hñtô)
rE°dONLNd)höt
)ead and write non-edition fi¿°dONLNdEh
t
)|leø¿°dONLNdGh
t
!)
s°dONLNdIyäÖ
s(Çä4Result codes appear at the end of each function wherÄ°dONLNd}y
tÖ
˝)Í!e applicable. In addition to the °dONLNdûÜäí¶(èäspecifiÓ °dONLNd•ܶí∞)c r£`°dONLNd®ܱí
.)esult codes listed, you may rM`°dONLNd≈Ü
/í
Y)~
eceive err™`°dONLNdœÜ
Yí
µ)*ors generated by the Û`°dONLNd‰Ü
µí
ı)\Alias Manager°dONLNdÒÜ
ˆí
˚)A, °dONLNdÛìäüú(úäFile )Ä°dONLNd¯ìùüƒ)Manager˛ °dONLNdˇì√ü
+)&, and Memory Manager °dONLNdì
+ü
-)h
.ˇh@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-74    )BEdition Manager Reference4^*¿
¯

j*q
¯4j*q
¯ l*l
˛

ˇ·ˇ‚7^°dONLNd\*j‘(f* Initializing the Edition Managerˇˇˇˇˇˇ(f
Ú
2
.°dONLNd"ql}s(zl
Yï°dONLNd#qr}†)ou use the ,
Courierï°dONLNd.q†}˙).InitEditionPackï°dONLNd=q˙}
∫)Z+ function to initialize the Edition Manager◊†°dONLNdhq
π}
◊)ø. Note .
°dONLNdo~lä(álthat V °dONLNdt~Ää´)    you shoulU@°dONLNd}~¨äπ),d ca@°dONLNdÄ~πä
)all this function ˘`°dONLNdí~
ä
)Gonly 7¿°dONLNdó~
ä
.)once.

∫*√
¯4ª*¬
¯ º*º
˛

ˇ·ˇ‚7^
°dONLNdû≠*ªÄ(∑*InitEditionPackˇˇˇˇˇˇ(∑
Ú
2
.°dONLNdØÃlÿÖ(’lBeforR`°dONLNd¥ÃÖÿ¿)e calling the R`°dONLNd¬Ã¿ÿ
);InitEditionPackR`°dONLNd—Ã
ÿ
^)Z function, be sur$¿°dONLNd‚Ã
^ÿ
‹)De to determine whether the °dONLNd˝ŸlÂ
o(‚l9Edition Manager is available on your system by using the °dONLNd
6Ÿ
oÂ
ô(‚
oGestalt°dONLNd
=Ÿ
ôÂ
Ï)* function with the °dONLNd
PÊlÚÍ(ÔlgestaltEditionMgrAttr°dONLNd
eÊÍÚ)~ (°dONLNd
gÊÚ
)'edtn'°dONLNd
mÊ
Ú
=)$
) selector¬†°dONLNd
wÊ
<Ú
?)(
.°dONLNd
yˇl
ˆ(
lFUNCTION InitEditionPac°dONLNd
êˇˆ

)äk:°dONLNd
íˇ


,) OSErr;
.
°dONLNd
ö
'*
0c(
.*DESCRIPTION
.°dONLNd
¶
4l
@Ä+BThe °dONLNd
™
4Ä
@⁄)InitEditionPack°dONLNd
π
4⁄
@
)Z function rR`°dONLNd
ƒ
4

@
=),eturns an err$¿°dONLNd
—
4
=
@
‰)7&or if the package could not be loaded .
°dONLNd
˜
Al
MÁ(
Jlinto the system heap and prâÄ°dONLNd
AÁ
M
2){operly initialized7‡°dONLNd$
A
3
M
8)L. 
°dONLNd'
h*
qD(
o*RESULëÄ°dONLNd,
hD
qh)T CODES


∞*
∏
¯4
∞*
∑
¯ 
≤*
≤
˛

ˇ·ˇ‚7^°dONLNdo
¢*
∞7(
¨*Crà°dONLNdq
¢7
∞‡) eating and Registering a Sectionˇˇˇˇˇˇ(
¨
Ú
2
.°dONLNdì
∑l
√s(
¿l
Yï°dONLNdî
∑r
√†)ou use the ï°dONLNdü
∑†
√‹).
NewSectionï°dONLNd©
∑‹
√
)< function to crg`°dONLNd∏
∑

√
Δ);(eate a new section (either publisher or .
°dONLNd‡
ƒl
–Õ(
Õlsubscriber) and alias r´†°dONLNd˜
ƒÕ
–fl)aecor °dONLNd˚
ƒ‡
–
)d (which is a rÃ`°dONLNd

ƒ

–
.)>eferxÄ°dONLNd
ƒ
/
–
µ) ence to the edition container fr*`°dONLNd.
ƒ
∂
–
◊)áom the °dONLNd5
—l
›
j(
⁄l9document containing the publisher or subscriber section)..°dONLNdo
„l
ÔÄ*The °dONLNds
„Ä
Ôº)
NewSection°dONLNd}
„º
ÔË)< function rR`°dONLNdà
„Ë
Ô
/),egisters a sectioR`°dONLNdô
„
/
Ô
`)Gn much as tR`°dONLNd§
„
`
Ô
n)1he R`°dONLNdß
„
n
Ô
»)RegisterSectionR`°dONLNd∂
„
»
Ô
)Z
 function ˇˇÿú°dONLNd¿
l
¸
~(
˘l=informs the Edition Manager about a section (except that the ˇˇâ‘ˆ°dONLNd˝

~
¸
∫(
˘
~
NewSectionˇˇÿúˆ°dONLNd

∫
¸
˜)< function does .
°dONLNd
˝l    Ä(lnot rN@°dONLNd
˝Å    ‘)esolve an alias to fiΔ`°dONLNd0
˝‘    
C)Snd the edition container).°dONLNdKl
Ì(lVWhen a section needs to be disposed of because the document containing the section is °dONLNd°l(á*being ö °dONLNdßá(ì)cloh@°dONLNd™î(´)sed oÄ °dONLNdØ´(±)r Ú¿°dONLNd±±(÷)because B°dONLNdπ◊(
ƒ)&8the user has canceled the section, you need to call the .°dONLNdÒ)l5“(2lUnRegisterSection°dONLNd)“5
)f function beforR`°dONLNd)
5
Ñ)?e disposing of the section.°dONLNd-;lGö(Dl
Using the °dONLNd7;öG
).IsRegisteredSection°dONLNdJ;
G
Í)r2 function, your application must verify that each .
°dONLNd|HlTä(Qlevent r@°dONLNdÉHãT”)eceived is for a r0 °dONLNdïH”T)Hegister@°dONLNdúHT
Ù);ed section. This is necessary because your application may .°dONLNd◊Ula∂(^lhave just called °dONLNdËU∂a
)JUnRegisterSection°dONLNd˘U
a
ã)f while the event was alrR`°dONLNdU
ãa
Û)oeady being held in the .
°dONLNd(bln§(klevent queue.°dONLNd5tlÄ
÷*QIf a user saves a document that contains sections under another name (using Save ´°dONLNdÜt
ր
Û(}
÷As) or °dONLNdçÅlç
Á(älVpastes a portion of a document that contains a section into another document, use the .°dONLNd„élöÃ*AssociateSection°dONLNdÛéÃö
y)`) function to update the section’s alias rR`°dONLNdé
yö
ã)≠ecor$¿°dONLNd é
ãö
ñ)d. °dONLNd3
ul
Åä(
~lnoErr.
°dONLNd9
uÀ
Å–)_
0°dONLNd;
u‰
Å
)No errE†°dONLNdA
u


Å

)or.°dONLNdE
Äl
å®(
âl
memFullErr.
°dONLNdP
ĺ
å–)P–108°dONLNdU
ĉ
å
M)(Could not load packageˇ=∏@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-75
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

jHr4jHr lHl

ˇ·ˇ‚7^°dONLNd\Hjä(fH
NewSectionˇˇˇˇˇˇ(f
2
.°dONLNd{äáØ(ÑäUse the ,
Courier°dONLNd{ØáÎ)%
NewSection°dONLNd{Îá
&)< function to crR`°dONLNd-{
&á
});eate a new section r$¿°dONLNdA{
}á
è)Wecor˜ °dONLNdE{
éá
«)d and alias r…Ä°dONLNdR{
«á
Ÿ)9ecorõ‡°dONLNdV{
Ÿá)d for a new .
°dONLNdbàäî(ëäpublisher or subscriberÓ‡°dONLNdyàÔîÒ)e
..°dONLNd{°ä≠
»(™ä5FUNCTION NewSection (container: EditionContainerSpec;°dONLNd∏Ø
ª
∞+~sectionDocument: FSSpecPtr; °dONLNd‹Ω
…
Ï*&kind: SectionType; sectionID: LongInt;°dONLNd

À
◊
û*initialMode: UpdateMode; °dONLNd
+Ÿ
Â
™*VAR sectionH: SectionHandle°dONLNd
FŸ
™Â
∂)¢):°dONLNd
HŸ
∂Â
‡) OSErr;°dONLNd
PÒä˝¿(˙ä    container.
°dONLNd
ZÒÃ˝◊)BThr °dONLNd
\Òÿ˝‰)e eÖ`°dONLNd
_Ò‰˝
¢),dition you want to publish or subscribe to. .°dONLNd
å

ä
‰(

äsectionDocument.
°dONLNd
ú
Ã
◊+BThr °dONLNd
û
ÿ
‰)e vb°dONLNd
°
Â

)olume r©†°dONLNd
®



)"eferU¿°dONLNd
¨



Q)ence number›†°dONLNd
∑

P

a)8, dir¶¿°dONLNd
º

b

©)ectory ID, and fi/‡°dONLNd
Õ

™

Ë)Hlename of the .°dONLNd
€
Ã
%
v(
"Ã&document that contains a section. The °dONLNd


v
%
–)™sectionDocument°dONLNd

–
%)Z parameter °dONLNd
%Ã
1›(
.Ãcan °dONLNd
%›
1È)be °dONLNd"
%È
1˚)NIL!†°dONLNd%
%˚
1
.) if your currÙ°dONLNd2
%
-
1
Â)2*ent document has never been saved. If so, .
°dONLNd\
1Ã
=Á(
:Ãwhen √`°dONLNda
1Á
=˜)the  ¿°dONLNde
1¯
=
)user fi≠‡°dONLNdl
1

=
å)nally saves the document, r•`°dONLNdá
1
å
=
Â)yemember to call the .°dONLNdõ
=Ã
I
,(
FÃAssociateSection°dONLNd´
=
,
I
M)` functio°dONLNd≥
=
M
I
h)!n for e°dONLNd∫
=
h
I
ı)!ach section to update its alias rR`°dONLNd€
=
ı
I)çecor$¿°dONLNdfl
=
I)d.°dONLNd‚
Mä
Y¢(
Väkind.
°dONLNdÁ
MÃ
Y◊)BThr °dONLNdÈ
Mÿ
Y‚)e t˛ °dONLNdÏ
M‚
Y
¥)
1ype of section (publisher or subscriber) being cr.@°dONLNd
M
µ
Y
—)”eated. .°dONLNd%
]ä
i¿(
fä    sectionID°dONLNd/
]Ã
i‘)B
AÛ`°dONLNd0
]”
i
ª)4 unique number for a section within a document. The Û`°dONLNdd
]
ª
i
˜)Ë
NewSectionÛ`°dONLNdn
]
˜
i
˘)<
 °dONLNdo
iÃ
u
7(
rÃfunction initializes the °dONLNdà
i
7
u
m)k    sectionID°dONLNdë
i
m
u
v)6 fi°dONLNdî
i
v
u
›)    eld of the new section rR`°dONLNd¨
i
›
u
Ô)gecor$¿°dONLNd∞
i
Ô
u)d with .
°dONLNd∑
uÃ
ů(
~Ã
the specifiKÄ°dONLNd¬
u˘
Å)-=ed value. Do not use 0 or –1 for an ID number; these numbers °dONLNdˇ
ÅÃ
ç‘(
äÃarE°dONLNd

Å’
ç‡)    e rS†°dONLNd
Ň
ç)Eeserved. If your application copies a section, you need to specify a °dONLNdI
çÃ
ô
v(
ñÃ&unique number for the copied section. .°dONLNdp
ùä
©Ã(
¶äinitialMode.
°dONLNd|
©Ã
µ◊+BThr °dONLNd~
©ÿ
µÂ)e u¬‡°dONLNdÅ
©Â
µ
Í)>pdate mode for the section. For publishers this is either the .°dONLNdø
µÃ
¡
(
æà    pumOnSave°dONLNd»
µ

¡
)6 or °dONLNdÃ
µ

¡
E)    pumManual°dONLNd’
µ
E
¡
Ÿ)6% constant, and for subscribers it is °dONLNd˙
¡Ã
ÕÎ(
 Ãeither °dONLNd

¡Î
Õ
3)sumAutomatic°dONLNd
¡
3
Õ
@)H or °dONLNd
¡
@
Õ
v)    sumManual°dONLNd
¡
v
Õ
{)6. !†°dONLNd
¡
{
Õ
É)
Aï°dONLNd
¡
Ç
Õ
∫) subscriber crg`°dONLNd+
¡
∫
Õ
Ô)8eated with °dONLNd6
ÕÃ
Ÿ
(
÷ÃsumAutomatic°dONLNdB
Õ

Ÿ
x)H mode automatically rR`°dONLNdW
Õ
x
Ÿ)deceives a Section Read event. Tg`°dONLNdv
Õ
Ÿ
)ão ˇˇß°dONLNdx
ŸÃ
Â÷(
‚ÃprR`°dONLNdz
Ÿ÷
Â
“)
:event this initial Section Read event, you should set the ˇ˛ı*ÿÏ°dONLNd¥
Ÿ
“
Â)¸initialModeˇˇßÿÏ°dONLNdø
Ÿ
Â)B
 °dONLNd¿
ÂÃ
Ò
    (
ÓÃparameter to °dONLNdÕ
Â
    
Ò
?)=    sumManual°dONLNd÷
Â
?
Ò
â)6 and then, when °dONLNdÊ
Â
â
Ò
≈)J
NewSection°dONLNd
Â
≈
Ò
À)< rR`°dONLNdÚ
Â
À
Ò)eturns, set the °dONLNd
ÒÃ
˝‰(
˙Ãmode°dONLNd
Ò‰
˝Í) fPÄ°dONLNd
ÒÍ
˝
A)ield of the section r"‡°dONLNd
Ò
A
˝
S)Wecorı@°dONLNd!
Ò
R
˝
e)d to ı@°dONLNd&
Ò
e
˝
≠)sumAutomaticı@°dONLNd2
Ò
≠
˝
∞)H
.°dONLNd4
ä∫(
äsectionH°dONLNd=
Ç)BThe °dONLNdA
‡
)
NewSection°dONLNdK


H)< function rR`°dONLNdV

H
t),
eturns a hR`°dONLNd`

t
¸),andle to the allocated section °dONLNdÖ(Ã
rR`°dONLNdÄ–‚)ecor$¿°dONLNdÑ‚Ë)
d$¿°dONLNdÖË
:) in this parameterg`°dONLNdó
9
<)Q
.g`°dONLNdò
<
b)
 If an err9¿°dONLNd¢
b
å)&or occurs, 9¿°dONLNd≠
å
»)*
NewSection9¿°dONLNd∑
»
Œ)< r °dONLNdπ
Œ
Î)eturns  °dONLNd¿
Î
˝)NIL≠¿°dONLNd√
¸    ) in .
°dONLNd«Ã%
("Ãthis parameter¿°dONLNd’
%
)@
.
°dONLNd◊?HHÅ(FHDESCRIPTION
.°dONLNd„LäXû+BThe °dONLNdÁLûX⁄)
NewSection°dONLNdÒL⁄X
ñ)<+ function allocates two handles in the currR`°dONLNdL
ñX)ºent zone: one handle for the .
°dONLNd9YäeØ(bä    section r≠Ä°dONLNdBYØe¡)%ecor!‡°dONLNdFY¬e
])$d and another handle for the alias rû@°dONLNdjY
]e
o)õecor†°dONLNdnY
pe
√)d. Note that you ar•†°dONLNdÅY
√e
Œ)Se r¥@°dONLNdÑY
Œe)esponsible for °dONLNdìfärô(oäunrÄ°dONLNdñförı)egistering handles cr≈‡°dONLNd´fır
x)[eated by the Edition ManagerÄ°dONLNd«f
xr
z)É
..°dONLNd…xäÑë(Åä
Yï°dONLNd xêÑ‹)our application rg`°dONLNd€x‹Ñ
)Leceives the g`°dONLNdÁx
Ñ
â)5multiplePublisherWrng`°dONLNd˚x
âÑ
è)x r9¿°dONLNd˝x
èÑ
€)esult code if ther °dONLNdx
ۄ
Ï)Le is .
°dONLNdÖäëÆ(éäanother ‡°dONLNdÖØë≤)%
r€‡°dONLNdÖ≤ëœ)egister+°dONLNd$Ö–ë
c)"ed publisher to the same edition. >@°dONLNdFÖ
cë
i)ì
Y˛¿°dONLNdGÖ
hë
≤)our application rȇ°dONLNdXÖ
≤ë
‰)Jeceives the .°dONLNddíäûˆ(õänotThePublisherWrn°dONLNdvíˆû¸)l rR`°dONLNdxí¸û)>esult code if another publisher (to the same edition) was the °dONLNd∂üä´
<(®ä*last section to write to the edition. The °dONLNd‡ü
<´
¥)≤multiplePublisherWrn°dONLNdÙü
¥´
∫)x rR`°dONLNdˆü
∫´)esult code takes °dONLNd    ¨ä∏Ÿ(µäpriority over the °dONLNd    ¨Ÿ∏
E)OnotThePublisherWrn°dONLNd    +¨
E∏
K)l rR`°dONLNd    -¨
K∏
w)
esult codeR`°dONLNd    7¨
w∏
z),
.ˇT@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-76    )BEdition Manager Reference4^*¿
¯
°dONLNd\*eD(c*RESULëÄ°dONLNd\Deh)T CODES°dONLNd
Δ*œQ(Õ*SEE ALSO
°dONLNd
‘l‡
$+B*For information on the edition container r ¿°dONLNd
;‘
$‡
6)∏ecor? °dONLNd
?‘
7‡
R)d, see ´ °dONLNd
F‘
R‡
i)page Ü°dONLNd
K‘
j‡
|)2-71Ÿ‡°dONLNd
O‘
|‡
Á). For information on the °dONLNd
h·lÌë(Íl    section r≠Ä°dONLNd
q·ëÌ£)%ecor!‡°dONLNd
u·§Ìø)d, see 燰dONLNd
|·øÌ
)“The Section RecorW@°dONLNd
é·
Ì
u)Td” beginning on page … °dONLNd
£·
uÌ
á)b2-72°dONLNd
ß·
àÌ
È). For information on fi£@°dONLNd
æ·
ÈÌ
Û)ale °dONLNd
¡Ól˙à(˜lspecifiÓ °dONLNd
»Óà˙©)cation r°dONLNd
–Ó™˙º)"ecorâ`°dONLNd
‘Óº˙€)ds, see 2`°dONLNd
‹Ó‹˙
9) Inside Macintosh: Files˘@°dONLNd
ÛÓ
9˙
O)]. See L@°dONLNd
˘Ó
P˙
¶)Listing 2-4 on page @°dONLNdÓ
ß˙
Ø)W2-b °dONLNdÓ
Ø˙
π)33b °dONLNdÓ
π˙
ÿ)
 for an .°dONLNd˚l
¿(
lexample that uses ,
Courier°dONLNd+˚¿
¸)T
NewSection°dONLNd5˚¸

)< to crR`°dONLNd;˚


p)eate a publisher and R`°dONLNdP˚
p

Δ)_Listing 2-6 on page R`°dONLNdd˚
Δ

œ)V2-R`°dONLNdf˚
œ

Ÿ)    40R`°dONLNdh˚
Ÿ

Í)
 for °dONLNdm
l
y(
lan °dONLNdp
y
¡)example that crR`°dONLNd
¡

*)Heates a subscriber using R`°dONLNdò

*

f)i
NewSectionR`°dONLNd¢

f

i)<
.


D*
M
¯4
E*
L
¯ 
F*
F
˛

ˇ·ˇ‚7^
.
°dONLNd•
7*
E2(
A*
R)¿°dONLNd¶
73
EÄ)    egisterSectionˇˇˇˇˇˇ(
A
Ú
2
°dONLNd∂
Vl
b
M(
_l1When opening a document that contains sections, r2¿°dONLNdÁ
V
N
b
—)‚egister each section using the .°dONLNd
cl
oΔ(
llRegisterSection°dONLNd
cΔ
oÒ)Z function. °dONLNd!
|l
à
ò(
Öl2FUNCTION RegisterSection (sectionDocument: FSSpec;°dONLNd\
ä¸
ñ
+ê
 °dONLNd]
ä

ñ
)
 °dONLNd^
ä

ñ
û)sectionH: SectionHandle; °dONLNdÄ
ò¸
§
(
°¸
 °dONLNdÅ
ò

§
)
 °dONLNdÇ
ò

§
∞)VAR aliasWasUpdated: Boolean°dONLNdû
ò
∞
§
º)®):°dONLNd†
ò
º
§
Ê) OSErr;°dONLNd®
∞l
ºΔ(
πlsectionDocument.
°dONLNd∏
ºÆ
»π+BThr °dONLNd∫
º∫
»Δ)e vb°dONLNdΩ
º«
»È)olume r©†°dONLNdƒ
ºÈ
»˘)"eferU¿°dONLNd»
º˙
»
3)ence number›†°dONLNd”
º
2
»
C)8, dir¶¿°dONLNdÿ
º
D
»
ã)ectory ID, and fi/‡°dONLNdÈ
º
å
»
 )Hlename of the °dONLNd˜
Ȯ
‘
C(
—Æ"document that contains a section. .°dONLNd
ÿl
‰ñ(
·lsection°dONLNd!
ÿñ
‰ú)*
H.
°dONLNd#
ÿÆ
‰µ)
A∫†°dONLNd$
ÿµ
‰Ω) h°dONLNd&
ÿæ
‰
)    andle to the section ṙ°dONLNd<
ÿ

‰
+)[ecorb@°dONLNd@
ÿ
,
‰
á)d for a given section..°dONLNdW
Ël
ÙΔ(
ÒlaliasWasUpdated°dONLNdg
ÙÆ∂+B
AÛ`°dONLNdh
Ùµ
) Boolean value that r≈¿°dONLNd}
Ù

2)`eturns ≈¿°dONLNdÑ
Ù
2
J)TRUE≈¿°dONLNdà
Ù
J
Ú)( if the alias for the edition container .
°dONLNd∞Æ
‚(    ÆEsubscribed to was out of date and was updated. This may occur if the °dONLNdıÆ’*    edition fiL °dONLNdˇ÷
á)('le was moved to a new location or was rí°dONLNd&
á
¨)±enamed.
°dONLNd.2*;c(9*DESCRIPTION
ˇˇ—.°dONLNd:?lK+BThe ˇˇs0Q°dONLNd>?ÄK⁄)RegisterSectionˇˇ—Q°dONLNdM?⁄K
P)Z function adds the section r8¿°dONLNdi?
PK
b)vecor °dONLNdm?
bK
“)d to the Edition Manager¿°dONLNdÖ?
”K
¯)q’s list of .
°dONLNdêLlXo(Ul
rE°dONLNdëLpXç)egisterî °dONLNdòLçX
7))ed sections and tries to allocate a contri°dONLNd¡L
7X
^)™
ol block. Õ`°dONLNdÀL
^X
®)'After calling the .°dONLNd›YleΔ(blRegisterSection°dONLNdÏYΔe
)Z function, the °dONLNd˚Y
e
K)=controlBlock°dONLNdY
Ke
Q)H fPÄ°dONLNd    Y
Qe
®)ield of the section r"‡°dONLNdY
®e
∫)Wecorı@°dONLNd"Y
πe
Ë)d contains °dONLNd-flrã(oleither °dONLNd4fãrù)NIL!†°dONLNd7fùr‰) or a valid contrÙ°dONLNdHf„r
    )F    ol block.°dONLNdRxlѱ(ÅlFor a subscriber¬†°dONLNdbx∞Ñ«)D, the ¬†°dONLNdhx«Ñ
)controlBlock¬†°dONLNdtx
Ñ
)H fi¬†°dONLNdwx
Ñ
P)    eld contains ¬†°dONLNdÑx
PÑ
b)8NILd@°dONLNdáx
bÑ
Ä) if the d@°dONLNdèx
ÄÑ
⁄)RegisterSectiond@°dONLNdûx
ڄ
‹)Z
 .
°dONLNdüÖlë
®(élIfunction could not locate the edition container being subscribed to. The .°dONLNdËílûΔ*RegisterSection°dONLNd˜íΔû
    )Z function then rR`°dONLNdí
    û
W)Ceturns either the R`°dONLNdí
Wû
œ)NcontainerNotFoundWrnR`°dONLNd-í
Ϟ
Ó)x or the °dONLNd5ül´Δ(®luserCanceledErr°dONLNdDüΔ´Ã)Z rR`°dONLNdFüô
B)esult code. For a publisherï°dONLNdaü
A´
b)u    , if the ï°dONLNdjü
b´
º)!RegisterSectionï°dONLNdyü
º´
‰)Z
 function .
°dONLNdɨl∏”(µlcould not locate its corrŸÄ°dONLNdú¨”∏
O)gesponding edition container@°dONLNd∑¨
O∏
π)|, the Edition Manager cr5`°dONLNdœ¨
∫∏
fl)k    eates an .°dONLNdjlvä(slnoErr.
xÄ°dONLNdj
v
)ü
0xÄ°dONLNdj
$v
@)No err> °dONLNdj
Av
J)or.°dONLNdulÅ“(~leditionMgrInitErr.
xÄ°dONLNd0u¸Å
)ê–450xÄ°dONLNd5u
$Å
ã)(Manager not initialized.°dONLNdNÄlå∫(âlbadSectionErr.
xÄ°dONLNd\ĸå
)ê–451xÄ°dONLNdaÄ
$å
ç)(Not a valid section type.°dONLNd{ãló∫(îlbadSubPartErr.
xÄ°dONLNdâã¸ó
)ê–454xÄ°dONLNdéã
$ó
ò)(Bad edition container spec.°dONLNd™ñl¢‰(ülmultiplePublisherWrn.
xÄ°dONLNdøñ¸¢
)ê–460xÄ°dONLNdƒñ
$¢
2)(AlrÌ °dONLNd«ñ
2¢
Ö)eady is a publisher.°dONLNd‹°l≠ÿ(™lnotThePublisherWrn.
xÄ°dONLNdÔ°¸≠
)ê–463xÄ°dONLNdÙ°
$≠
r)(Not the publisherˇ;f@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-77
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh
£(eäBedition container in the last place the edition was located and crõ °dONLNdB\
£h
Ÿ(e
£eates a contrl@°dONLNdO\
⁄h)7ol block for .°dONLNd\iäu≥(räit. If the ,
Courier°dONLNdgi≥u
))RegisterSection°dONLNdvi
u
±)Z& function could not locate a publisher=`°dONLNdúi
≤u
Ã)•’s corr¿°dONLNd£i
Ãu
˚)
esponding °dONLNd≠väÇ
*(ä%edition container or its volume, the °dONLNd“v
*Ç
r)†controlBlock°dONLNdfiv
rÇ
{)H fi°dONLNd·v
{Ç
≥)    eld contains °dONLNdÓv
≥Ç
≈)8NIL°dONLNdÒv
ł
 ). R`°dONLNdÛv
 Ç
—)
Yg`°dONLNdÙv
–Ç
˝)
ou should .
°dONLNd˛Éäè©(åänever r¬Ä°dONLNd
É©èµ)e-r•°dONLNd
ɵè
')egister a section that is alr≥ °dONLNd
%É
'è
B)ready rl†°dONLNd
+É
Cè
`)egisterª¿°dONLNd
2É
`è
m)ed.°dONLNd
6ïä°˝(ûäNote that you can compart¿°dONLNd
Nï˝°
)se contr|‡°dONLNd
Uï
°);ol blocks for individual sections. If two sections contain °dONLNd
ê¢äÆ (´äthe same contrˆÄ°dONLNd
û¢ Æ
˛)@Hol block value, these sections publish or subscribe to the same edition .°dONLNd
ÊØ䪔(∏ä(unless the contrR`°dONLNd
˜Ø”ª
)Iol block is R`°dONLNdØ
ª
)/NILR`°dONLNdØ
ª)8). The Edition Manager keeps track of how many sections .
°dONLNd>ºä»í(≈äarE°dONLNd@ºì»û)    e rS†°dONLNdCºû»Æ)eferˇ¿°dONLNdGºÆ»Ï)encing a contr`°dONLNdUºÌ»
›)?6ol block to know when it can be deallocated. The contrx‡°dONLNdãº
›»)    ol block °dONLNdî…ä’
F(“ä)maintains a count of how many sections arM¿°dONLNdΩ…
G’
R)Ωe r\`°dONLNd¿…
R’
b)eferÄ°dONLNdƒ…
c’
Ò)!encing it. Each time you use the .°dONLNdÂ÷ä‚(fläUnRegisterSection°dONLNdˆ÷‚
C)f function, the contrR`°dONLNd
÷
C‚
å)Sol block subtractR`°dONLNd÷
å‚
ù)Is 1 fR`°dONLNd ÷
ù‚
°)
r$¿°dONLNd!÷
°‚
Ô)om the number of .
°dONLNd2„äÔ
9(Ïä'sections. When the number of sections rÄ°dONLNdY„
:Ô
ä)∞eaches 0, the contr¡@°dONLNdl„
äÔ
Ó)Pol block is deallocated..°dONLNdÖıä

ë(˛ä
Yï°dONLNdÜıê

‹)our application rg`°dONLNdóı‹


)Leceives the g`°dONLNd£ı



â)5multiplePublisherWrng`°dONLNd∑ı
â


è)x r9¿°dONLNdπı
è


€)esult code if ther °dONLNdÀı
€


Ï)Le is .
°dONLNd–
ä
Æ(
äanother ‡°dONLNdÿ
Ø
≤)%
r€‡°dONLNdŸ
≤
œ)egister+°dONLNd‡
–

c)"ed publisher to the same edition. >@°dONLNd

c

i)ì
Y˛¿°dONLNd

h

≤)our application rȇ°dONLNd

≤

‰)Jeceives the .°dONLNd 
ä
ˆ(
änotThePublisherWrn°dONLNd2
ˆ
¸)l rR`°dONLNd4
¸

˝):esult code if another publisher (to the same edition) was °dONLNdn
ä
(ú(
%äthe °dONLNdr
ú
(
N)*last section to write to the edition. The °dONLNdú

N
(
Δ)≤multiplePublisherWrn°dONLNd∞

Δ
(
Ã)x rR`°dONLNd≤

Ã
(
˙)esult code °dONLNdΩ
)ä
5•(
2ätakes °dONLNd√
)•
5Ù)priority over the °dONLNd’
)Ù
5
`)OnotThePublisherWrn°dONLNdÁ
)
`
5
f)l rR`°dONLNdÈ
)
f
5
í)
esult codeR`°dONLNdÛ
)
í
5
ï),
.
.
°dONLNdı
OH
Xb(
VHRESULëÄ°dONLNd˙
Ob
XÅ)T CODEÂÄ°dONLNd
OÅ
XÖ)
S°dONLNd6
ƒH
Õo(
ÀHSEE ALSO
°dONLNd?
“ä
fi
+B For information on the section rÑ`°dONLNd_
“

fi
()åecor¯¿°dONLNdc
“
(
fi
C)d, see d¿°dONLNdj
“
D
fi
ó)“The Section Recor. °dONLNd|
“
ò
fi
‚)Td” beginning on °dONLNdå
flä
ΰ(
Ëäpage Z‡°dONLNdë
ߢ
Î¥)2-72Æ¿°dONLNdï
ߴ
Îπ). Æ¿°dONLNdó
flπ
Î
)For information on fi5°dONLNd¨
fl

Î
<)]    le specifi’ °dONLNd∂
fl
<
Î
])&cation r¸°dONLNdæ
fl
]
Î
o)!ecorp`°dONLNd¬
fl
p
Î
è)ds, see `°dONLNd 
fl
ê
Î
Ì) Inside Macintosh: Files‡@°dONLNd·
fl
Ì
Î
Ú)]. .°dONLNd„
Ïä
¯õ(
ıäFor °dONLNdÁ
Ïõ
¯
à)4additional information and an example of the use of °dONLNd
Ï
à
¯
‚)ÌRegisterSection°dONLNd*
Ï
‚
¯
˜)Z, see .
°dONLNd0
˘ä
›(äG“Opening and Closing a Document Containing Sections” beginning on page ¶Ä°dONLNdw
˘
›
Ô(
›2-22˙`°dONLNd{
˘
Ô
Ò)
.

5H>46H= 7H7

ˇ·ˇ‚7^
°dONLNd~(H6Q(2H
U’Ä°dONLNd(Q6Æ)    nRegisterSectionˇˇˇˇˇˇ(2
2
°dONLNdëGäS(PäVWhen a section needs to be disposed of because the document containing the section is °dONLNdÁTä`•*being ö °dONLNdÌT•`±)cloh@°dONLNdT≤`…)sed oÄ °dONLNdıT…`œ)r Ú¿°dONLNd˜Tœ`Ù)because B°dONLNdˇTı`
‚)&8the user has canceled the section, you need to call the .°dONLNd7aäm(jäUnRegisterSection°dONLNdHam
/)f function beforR`°dONLNdWa
/m
¢)?e disposing of the section.°dONLNdszäÜ
º(Éä3FUNCTION UnRegisterSection (sectionH: SectionHandle°dONLNd¶z
ºÜ
»(É
º):°dONLNd®z
Ȇ
Ú) OSErr;°dONLNd∞íäû¥(õäsection°dONLNd∑í¥û∫)*
H.
°dONLNdπíÃû”)
A∫†°dONLNd∫í”û€) h°dONLNdºí‹û
8)    andle to the section ṙ°dONLNd“í
7û
I)[ecorb@°dONLNd÷í
Jû
•)d for a given section..°dONLNd

]ä
i®(
fänoErr.
°dONLNd
]
%
i
*)õ
0°dONLNd    
]
>
i
Z)No errE†°dONLNd
]
[
i
d)or.°dONLNd
hä
t‰(
qäuserCanceledErr.
°dONLNd#
h

t
*)å–128°dONLNd(
h
>
t
U)(User ¿Ä°dONLNd-
h
U
t
})    clicked C}@°dONLNd6
h
~
t
í))anceàÄ°dONLNd:
h
í
t
®)l in dF`°dONLNd@
h
©
t
—)    ialog box.°dONLNdK
sä
(
|äeditionMgrInitErr.
°dONLNd]
s


*)å–450°dONLNdb
s
>

•)(Manager not initialized.°dONLNd{
~ä
äÿ(
áäbadSectionErr.
°dONLNdâ
~

ä
*)å–451°dONLNdé
~
>
ä
ü)(Not valid section type.°dONLNd¶
âä
ï
(
íämultiplePublisherWrn.
°dONLNdª
â

ï
*)å–460°dONLNd¿
â
>
ï
L)(AlrÙ†°dONLNd√
â
L
ï
ü)eady is a publisher.°dONLNdÿ
îä
†
(
ùäcontainerNotFoundWrn.
°dONLNdÌ
î

†
*)å–461°dONLNdÚ
î
>
†
Ä)(Alias was not r∑@°dONLNd

î
Ä
†
°)Besolved.°dONLNd

üä
´ˆ(
®änotThePublisherWrn.
°dONLNd
ü

´
*)å–463°dONLNd"
ü
>
´
å)(Not the publisherˇÚ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-78    )BEdition Manager Reference4^*¿
¯
°dONLNd\*ec(c*DESCRIPTION
ˇˇ˜.°dONLNdjlv+BThe ,
CourierˇˇÂ<w°dONLNdjÄvÊ)UnRegisterSectionˇˇ˜w°dONLNd!jÊv
)f function r7ú°dONLNd,j
v
o),emoves the section frÔ8°dONLNdAj
ov
€)]om the Edition Managerë‘°dONLNdWj
›v
˜)n’s list .
°dONLNd_wlÉ{(Älof ré`°dONLNdcw{Éò)egister›Ä°dONLNdjwòÉÕ)ed sections. :¿°dONLNdwwŒÉ‘)6
Y˚@°dONLNdxw”É
n)$ou can then dispose of the section r˚‡°dONLNdúw
nÉ
Ä)õecorp@°dONLNd†w
ÅÉ
∑)d and alias rÀ‡°dONLNd≠w
∑É
…)6ecor@@°dONLNd±w
 É
È)d with °dONLNd∏Ñlêç(çlstandar±Ä°dONLNdøÑçê
)!d Memory Manager and ResourL¿°dONLNd⁄Ñ
ê
í)éce Manager calls. Once unrõ@°dONLNdÙÑ
íê
Ø)wegisterÍ`°dONLNd˚Ñ
Øê
Á)ed, a section °dONLNd
    ëlùò(öl
does not rf °dONLNd
ëòù
),eceive any events and cannot r©†°dONLNd
1ë
ù
€)á)ead or write any data. Depending on your °dONLNd
Zûl™í(ßlClipboar,°dONLNd
bûì™ø)'
d strategyH@°dONLNd
lûæ™
 )+, you may want to unrw@°dONLNd
Åû
 ™
Ã)b)egister sections that have been cut into °dONLNd
™´l∑|(¥lthe ›`°dONLNd
Æ´|∑¢)Clipboarâ`°dONLNd
∂´£∑´)'d.
°dONLNd
π—*⁄D(ÿ*RESULëÄ°dONLNd
æ—D⁄h)T CODES


;*
D
¯4
<*
C
¯ 
=*
=
˛

ˇ·ˇ‚7^°dONLNdU
.*
<ó(
8*IsRegisteredSectionˇˇˇˇˇˇ(
8
Ú
2
.°dONLNdj
Ml
Yä(
VlUpon rR`°dONLNdp
Mä
Y
v)6eceiving a section event, your application must call tR`°dONLNd¶
M
v
Y
Ñ)Ïhe R`°dONLNd©
M
Ñ
Y
ˆ)IsRegisteredSectionR`°dONLNdº
M
ˆ
Y
¯)r
 .
°dONLNdΩ
Zl
fã(
clfunctioº‡°dONLNdƒ
Zã
f§)n to vÏ`°dONLNd 
Z§
f…)    erify tha¿°dONLNd”
Z 
f‰)&t the eÒ °dONLNd⁄
Z‰
f˝)vent rπ¿°dONLNd‡
Z˛
f
F)eceived is for a r◊†°dONLNdÚ
Z
F
f
c)Hegister&¿°dONLNd˘
Z
d
f
ê)
ed sectiont†°dONLNd
Z
ê
f
ï),. G°dONLNd
Z
ï
f
õ)
YÄ°dONLNd
Z
õ
f
”)ou must call .°dONLNd
gl
sfi(
plIsRegisteredSection°dONLNd&
gfi
s˜)r beforR`°dONLNd,
g˜
s
s)e handling a section event bR`°dONLNdH
g
s
s
ˆ)|ecause your application may °dONLNdd
tl
Ä∂(
}lhave just called °dONLNdu
t∂
Ä
)JUnRegisterSection°dONLNdÜ
t

Ä
ã)f while the event was alrR`°dONLNdû
t
ã
Ä
Û)oeady being held in the .
°dONLNdµ
Ål
ç§(
älevent queue..°dONLNd¬
öl
¶
™*5FUNCTION IsRegisteredSection (sectionH: SectionHandle°dONLNd˜
ö
™
¶
∂(
£
™):°dONLNd˘
ö
∂
¶
‡) OSErr;°dONLNd

≤l
æñ(
ªlsection°dONLNd
≤ñ
æú)*
H.
°dONLNd

≤Æ
æµ)
A∫†°dONLNd
≤µ
æΩ) h°dONLNd
≤æ
æ
)    andle to the section ṙ°dONLNd#
≤

æ
+)[ecorb@°dONLNd'
≤
,
æ
ä)d for a given section. 
°dONLNd?
ÿ*
·c(
fl*DESCRIPTION
.°dONLNdK
Âl
Òy+BTh°dONLNdM
Ây
ÒÄ)e °dONLNdO
ÂÄ
ÒÚ)IsRegisteredSection°dONLNdb
ÂÚ
Ò
)r
 function °dONLNdl
Â

Ò
)(
rR`°dONLNdm
Â

Ò
G)
eturns a r$¿°dONLNdw
Â
G
Ò
è))esult code (not a$¿°dONLNdà
Â
è
Ò
∂)H Boolean$¿°dONLNdê
Â
∂
Ò
ÿ)' value) ˇˇöê°dONLNdò
Úl
˛
(
˚l#indicating whether the section is rW0°dONLNdª
Ú

˛
%)öegister)ê°dONLNd¬
Ú
%
˛
4)ed. e¿°dONLNdΔ
Ú
4
˛
<)
AŸ °dONLNd«
Ú
;
˛
<)
 ˇ˛œ∞s∞°dONLNd»
Ú
=
˛
C)
ns∞°dONLNd…
Ú
C
˛
[)oErrˇˇöês∞°dONLNdÕ
Ú
[
˛
`) r‡†°dONLNdœ
Ú
`
˛
˜)$esult code indicates that a section .
°dONLNdÛ
ˇly(lis rÍ`°dONLNd˜
ˇyñ)egister9Ä°dONLNd˛
ˇó§)ed.
°dONLNd&*/D(-*RESULëÄ°dONLNd&D/h)T CODES°dONLNdNd*mQ(k*SEE ALSO
.°dONLNdWql}Î+BFor an example of the use of °dONLNdtqÎ}
])IsRegisteredSection°dONLNdáq
]}
r)r, see °dONLNdçq
r}
»)Listing 2-1 on page °dONLNd°q
»}
—)V2-°dONLNd£q
—}
€)    14°dONLNd•q
€}
fi)

.°dONLNd
≈fllÎä(ËlnoErr.
°dONLNd
Àfl
Î
)≠
0°dONLNd
Õfl
2Î
N)No errE†°dONLNd
”fl
OÎ
X)or.°dONLNd
◊Ílˆñ(ÛlfBsyErr.
°dONLNd
flÍ
ˆ
)£–47°dONLNd
„Í
2ˆ
Ç)#Section doing I/O.°dONLNd
ˆıl

“(˛leditionMgrInitErr.
°dONLNdı




)û–450°dONLNdı
2


ô)(Manager not initialized.°dONLNd&
l
ˆ(
    lnotRegisteredSectionErr.
°dONLNd>




)û–452°dONLNdC

2

I)(Not rÀ¿°dONLNdH

I

f)egister‡°dONLNdO

g

q)ed.°dONLNd3l?ä(<lnoErr.
w`°dONLNd3
"?
')∂
0w`°dONLNd3
;?
W)No err=°dONLNd3
X?
a)or.°dONLNd >lJˆ(GlnotRegisteredSectionErr.
w`°dONLNd8>
J
')ß–452w`°dONLNd=>
;J
R)(Not r√ °dONLNdB>
RJ
o)egister@°dONLNdI>
pJ
z)edˇ0*@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-79
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

jHr4jHr lHl

ˇ·ˇ‚7^°dONLNd\HjQ(fH
A’Ä°dONLNd
\Qj§)    ssociateSectionˇˇˇˇˇˇ(f
2
°dONLNd{äá
Ù(ÑäQIf a user saves a document that contains sections under another name (using Save ´°dONLNdc{
Ùá(Ñ
ÙAs) or °dONLNdjàäî(ëäVpastes a portion of a document that contains a section into another document, use the ,
Courier.°dONLNd¿ïä°Í*AssociateSection°dONLNd–ïÍ°
ó)`) function to update the section’s alias rR`°dONLNd˘ï
ó°
©)≠ecor$¿°dONLNd˝ï
©°
≤)d.°dONLNd
Æä∫
º(∑ä3FUNCTION AssociateSection (sectionH: SectionHandle;°dONLNd
=º
,»
⁄+¢newSectionDocument: FSSpecPtr°dONLNd
Zº
⁄»
Ê)Æ):°dONLNd
\º
Ê») OSErr;°dONLNd
d‘䇥(›äsection°dONLNd
k‘¥‡∫)*
H.
°dONLNd
m‘Ç”)
A∫†°dONLNd
n‘”‡€) h°dONLNd
p‘‹‡
8)    andle to the section ṙ°dONLNd
Ü‘
7‡
I)[ecorb@°dONLNd
ä‘
J‡
®)d for a given section. .°dONLNd
¢‰äˆ(ÌänewSectionDocument.
°dONLNd
µø◊+BThr °dONLNd
∑ÿ¸‰)e vb°dONLNd
∫¸
)olume r©†°dONLNd
¡
¸
)"eferU¿°dONLNd
≈
¸
Q)ence number›†°dONLNd
–
P¸
a)8, dir¶¿°dONLNd
’
b¸
©)ectory ID, and fi/‡°dONLNd
Ê
™¸
˝)Hlename of the new °dONLNd
¯¸Ã
˝(
Ã
document. 
°dONLNd
"H
+Å(
)HDESCRIPTION
.°dONLNd
/ä
;û+BThe °dONLNd
/û
;˛)AssociateSection°dONLNd#
/˛
;
>)` function calls °dONLNd3
/
>
;
Ä)@UpdateAlias°dONLNd>
/
Ä
;
Ê)B on the section’s alias rR`°dONLNdW
/
Ê
;
¯)fecor$¿°dONLNd[
/
¯
;
˛)
d$¿°dONLNd\
/
˛
;). 
.
°dONLNd_
VH
_b(
]HRESULëÄ°dONLNdd
Vb
_Å)T CODEÂÄ°dONLNdj
VÅ
_Ö)
S°dONLNdû
îH
ùo(
õHSEE ALSO
.°dONLNdß
°ä
≠Ò+BFor information on the °dONLNdæ
°Ò
≠
3)gUpdateAlias°dONLNd…
°
3
≠
)B. function, see the chapter “Alias Manager” in .
°dONLNd˜
Æä
∫Á(
∑äInside Macintosh: FilesF‡°dONLNd
ÆË
∫Í)^
.


flH
Á4
flH
Ê 
·H
·

ˇ·ˇ‚7^°dONLNd
—H
flP(
€H
C°dONLNd
—Q
flU)    
rà°dONLNd
—U
fl
/)(eating and Deleting an Edition Containerˇˇˇˇˇˇ(
€
2
°dONLNd=
Êä
Ú›(
ÔäEach time a user cr€`°dONLNdP
Ê›
Ú)SCeates a new publisher section within a document to an edition that .°dONLNdì
Ûä
ˇæ(
¸ädoes not alrR`°dONLNdü
Ûæ
ˇ
&)4eady exist, you use the R`°dONLNd∑
Û
&
ˇ
¬)hCreateEditionContainerFileR`°dONLNd—
Û
¬
ˇ
˝)ú function to cr$¿°dONLNd‡
Û
˝
ˇ);eate .
°dONLNdÂä

(    äan empty edition container4 °dONLNdˇ


)w
..°dONLNd
äê(ä
Tï°dONLNdèö)o rg`°dONLNdö
)emove the edition container™°dONLNd 

>)}
, use the ™°dONLNd*
>
⁄)'DeleteEditionContainerFile™°dONLNdD
⁄)ú
 function.

OHW4OHW QHQ

ˇ·ˇ‚7^
.
°dONLNdPAHOfl(KHCreateEditionContainerFileˇˇˇˇˇˇ(K
2
.°dONLNdlaämë(jä
Yï°dONLNdmaêmæ)ou use the ï°dONLNdxaæm
Z).CreateEditionContainerFileï°dONLNdía
Zm
ï)ú function to crg`°dONLNd°a
ïm
˙);eate an empty edition .
°dONLNd∑näz≥(wä    container2 °dONLNd¿n≥zµ))
..°dONLNd¬áäì
b(êä$FUNCTION CreateEditionContainerFile °dONLNdÓï
°
˛+~)(editionFile: FSSpec; fdCreator: OSType; °dONLNd£
Ø
*
 °dONLNd £
Ø
‘)!editionFileNameScript: ScriptCode°dONLNdA£
‘Ø
‡)Δ):°dONLNdC£
‡Ø
) OSErr;°dONLNdk
cä
o®(
länoErr.
}°dONLNdq
c·
oÊ)W
0}°dONLNds
c˙
o
)No errB†°dONLNdy
c

o
 )or.°dONLNd}
nä
z∫(
wäparamErr.
}°dONLNdÜ
n◊
zÊ)M–50}°dONLNdä
n˙
z
I)#Invalid parameterˇà@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-80    )BEdition Manager Reference4^*¿
¯,
Courier
.°dONLNd\lhÆ(eleditionFile.
°dONLNdhÆtπ+BThr °dONLNdh∫tΔ)e vb°dONLNdh«tÈ)olume r©†°dONLNdhÈt˘)"eferU¿°dONLNdh˙t
3)ence number›†°dONLNd'h
2t
C)8, dir¶¿°dONLNd,h
Dt
ã)ectory ID, and fi/‡°dONLNd=h
åt
Ô)Hlename for the edition °dONLNdTtÆÄ˝(}Æcontainer being cr懰dONLNdft˝Ä
)Oeated. .°dONLNdnÑlê¢(çl    fdCreator.
°dONLNdxÑÆêπ)BThr °dONLNdzÑ∫ê≈)e c,°dONLNd}ÑΔê…)
rÒ°dONLNd~Ñ…ê
9)eator type for the edition..°dONLNdöîl†Í(ùleditionFileNameScript.
°dONLNd∞†Æ¨π+BThr °dONLNd≤†∫¨≈)e s¯¿°dONLNdµ†≈¨˝)cript of the fiº°dONLNdƒ†˛¨
#)9lename. ݡdONLNd̠
#¨
,)%(YÒ`°dONLNdŒ†
,¨
ê)    ou can get this value fr| °dONLNdʆ
ë¨
•)eom tà°dONLNd͆
•¨
≤)he .°dONLNd̨Æ∏¸(µÆtheFileScript°dONLNd˙¨¸∏
)N fPÄ°dONLNd¸¨
∏
)ield oPÄ°dONLNd
¨
∏
4)f an ePÄ°dONLNd
¨
4∏
ô)dition container specif!°dONLNd
¨
ô∏
ø)e    ication rÛ`°dONLNd
(¨
æ∏
–)%ecor≈¿°dONLNd
,¨
–∏
›)d.)
.
°dONLNd
0—*⁄c(ÿ*DESCRIPTION
.°dONLNd
<fllÎÄ+BThe °dONLNd
@flÄÎ
)CreateEditionContainerFile°dONLNd
Zfl
Î
L)ú function crR`°dONLNd
ffl
LÎ
Ë)0"eates an empty edition container fiR`°dONLNd
âfl
ËÎ
Û)úle .
°dONLNd
åÏl¯
g(ıl;(it does not contain any formats). This function sets the fi¨†°dONLNd
»Ï
g¯
œ)˚le type of the edition to ˇˇÅ≤.°dONLNd
‚˘l
ê(
l'edtu'ˇˇ’Ê°dONLNd
ˢê
î)$. ˜Ü°dONLNd
͢î

˜)OAs soon as you write data to the edition, the Edition Manager updates the type °dONLNd9
l
{(
l(to °dONLNd=
{
ü)'edtp'°dONLNdC
ü
›)$ for graphics, °dONLNdR
›


)>'edtt'°dONLNdX




4)$ for text, or °dONLNdf

4

X)3'edts'°dONLNdl

X

„)$! for sound). If your application ˇˇwv°dONLNdç
l
†(
lwrites both ˇ˛fbnÏ°dONLNdô
°
≈)5'TEXT'ˇˇwvnÏ°dONLNdü
≈
ÿ)$ and ˇ˛fb]ÿ°dONLNd§
Ÿ
˝)'PICT'ˇˇwv]ÿ°dONLNd™
˝

Ì)$7 formats to the edition, the Edition Manager sets the fit°dONLNd‚

Ó

¯)Òle .
°dONLNdÂ
 l
,
(
)l#type to the type that was written fi`°dONLNd    
 

,
‹)ô2rst. If your application has a bundle, you should °dONLNd;
-l
9Ô(
6ldesignate an icon for the apprJ¿°dONLNdY
-
9
†)Ñ)opriate edition types that you can write.$Ä°dONLNdÇ
-
°
9
£)±
 
°dONLNdÑ
S*
\D(
Z*RESULëÄ°dONLNdâ
SD
\h)T CODES°dONLNdx
”*
‹Q(
⁄*SEE ALSO
°dONLNdÅ
·l
Ì»+BFor information on fi@°dONLNdñ
·…
ÌÔ)]    le specifi¶`°dONLNd†
·Ô
Ì
)&cation rÕ@°dONLNd®
·

Ì
")!ecorA†°dONLNd¨
·
#
Ì
B)ds, see ͆°dONLNd¥
·
B
Ì
ü)Inside Macintosh: Files±Ä°dONLNdÀ
·
†
Ì
˜)^. For an example of .°dONLNdfl
Ól
˙ô(
˜lthe use of °dONLNdÍ
Óô
˙
5)-CreateEditionContainerFile°dONLNd
Ó
5
˙
J)ú, see °dONLNd

Ó
J
˙
†)Listing 2-4 on page °dONLNd
Ó
†
˙
©)V2-°dONLNd 
Ó
©
˙
≥)    33°dONLNd"
Ó
≥
˙
∂)

.

**3
¯4+*2
¯ ,*,
˛

ˇ·ˇ‚7^
.
°dONLNd%*+3('*
D~@°dONLNd&4+¡)
eleteEditionContainerFileˇˇˇˇˇˇ('
Ú
2
°dONLNdA<lH
(ElXIf a user cancels a publisher section within a document or closes a document containing °dONLNdôIlUô*
a newly cr¿°dONLNd£IöU
c).-eated publisher without saving, you need to rɆ°dONLNd–I
cU
fi)…emove the edition containerUÄ°dONLNdÎI
fiU
„){. .°dONLNdÓ[lgr(dl
Tï°dONLNdÔ[qgæ)o locate the apprg`°dONLNd[æg
í)M1opriate edition container to be deleted, use the g`°dONLNd1[
íg
Ê)‘GetEditionInfog`°dONLNd?[
Êg
Ë)T
 °dONLNd@hltï(ql
function. R`°dONLNdJhïtú))
Yg`°dONLNdKhõt…)ou use the g`°dONLNdVh…t
/).UnRegisterSectiong`°dONLNdgh
/t
µ)f  function (only after using the °dONLNdáulÅ¿(~lGetEditionInfo°dONLNdïu¿Å
)T function) to unrR`°dONLNd¶u
Å
])Eegister the section r$¿°dONLNdªu
]Å
o)Xecor˜ °dONLNdøu
nÅ
ß)d and alias r…Ä°dONLNdÃu
ßÅ
π)9ecorõ‡°dONLNd–u
πÅ
fi)    d of the .
°dONLNdŸÇlé⁄(ãlpublisher being canceled膰dONLNdÒÇ⁄éfl)n. .°dONLNdê
al
mä(
jlnoErr.
°dONLNdñ
aı
m˙)â
0°dONLNdò
a

m
*)No errE†°dONLNdû
a
+
m
4)or.°dONLNd¢
ll
x¢(
ul    dskFulErr.
°dONLNd¨
lÎ
x˙)–34°dONLNd∞
l

x
=)#Disk is full.°dONLNdæ
wl
Éê(
ÄlnsvErr.
°dONLNd≈
wÎ
É˙)–35°dONLNd…
w

É
V)#No such volume.°dONLNdŸ
Çl
éä(
ãlioErr.
°dONLNdfl
ÇÎ
é˙)–36°dONLNd„
Ç

é
.)#I/O err ‡°dONLNdÍ
Ç
.
é
7) or.°dONLNdÓ
çl
ôú(
ñlbdNamErr.
°dONLNd˜
çÎ
ô˙)–37°dONLNd˚
ç

ô
')#Bad fiD@°dONLNd

ç
(
ô
H)lename.°dONLNd    
òl
§ê(
°lfnfErr.
°dONLNd
òÎ
§˙)–43°dONLNd
ò

§
L)#File not found.°dONLNd$
£l
Øú(
¨ldirNFErr.
°dONLNd-
£Ê
Ø˙)z–120°dONLNd2
£

Ø
)(DirꠡdONLNd5
£

Ø
e)ectory not found.°dONLNdG
Æl
∫“(
∑leditionMgrInitErr.
°dONLNdY
ÆÊ
∫˙)z–450°dONLNd^
Æ

∫
u)(Manager not initializedˇ4º@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-81
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿.°dONLNd\ähê(eä
Tï°dONLNd
\èhö)o rg`°dONLNd\öh
)emove the edition container™°dONLNd\
h
>)}
, use the ,
Courier™°dONLNd)\
>h
⁄)'DeleteEditionContainerFile™°dONLNdC\
⁄h)ú function. °dONLNdOuäÅ(~äAFUNCTION DeleteEditionContainerFile (editionFile: FSSpec): OSErr;°dONLNdëçäôÃ*editionFile.
°dONLNdùôÕ◊+BThr °dONLNdüôÿ•‰)e vb°dONLNd¢ô•
)olume r©†°dONLNd©ô
•
)"eferU¿°dONLNd≠ô
•
Q)ence number›†°dONLNd∏ô
P•
a)8, dir¶¿°dONLNdΩô
b•
©)ectory ID, and fi/‡°dONLNdŒô
™•)Hlename for the edition °dONLNd•ñ
6(ÆÃcontainer being deleted.
°dONLNd˛ H”Å(—HDESCRIPTION
.°dONLNd

ÿä‰
+BIf the user cancels a publisher¬†°dONLNd
)ÿ
‰
W)Ö, do not call the ¬†°dONLNd
;ÿ
W‰
Û)HDeleteEditionContainerFile¬†°dONLNd
Uÿ
Û‰
ı)ú
 .
°dONLNd
VÂäÒ(ÓäUfunction until the user saves the document. This allows the user to undo changes and °dONLNd
´Úä˛ç*
rE°dONLNd
¨Úé˛
^)0evert to the last saved version of the document..°dONLNd
›
ä
û(
äThe °dONLNd
·
û

:)DeleteEditionContainerFile°dONLNd
˚

:

[)ú functio°dONLNd

[

h)!n d°dONLNd

h

Ê)eletes the edition container °dONLNd#

Ê

¸)~only °dONLNd(

¸
)if .
°dONLNd+
ä
õ(
äther"`°dONLNd/
ú
æ)    e is no rù@°dONLNd8
æ
€)"egisterÏ`°dONLNd?
€

)ed publisher¿†°dONLNdK



)7. ì°dONLNdM



)
YSÄ°dONLNdN



^)ou need to unr%‡°dONLNd\

^

…)Aegister a publisher befor.Ä°dONLNdu

…
)ke you can delete °dONLNdÜ
ä
*®(
'äits corr °dONLNdé
©
*
%)esponding edition container™‡°dONLNd©

$
*
&){
..°dONLNd´
0ä
<ë(
9ä
Yï°dONLNd¨
0ê
<fl)ou should use the ï°dONLNdæ
0fl
<
{)ODeleteEditionContainerFileï°dONLNdÿ
0
{
<
ÿ)ú function even if therg`°dONLNdÓ
0
ÿ
<
È)]e ar9¿°dONLNdÚ
0
È
<
)e .
°dONLNdÙ
=ä
I
ò(
Fä@subscribers to the edition. When a subscriber section tries to r7 °dONLNd4
=
ô
I
€(
F
ôead in data, it r§ °dONLNdE
=
€
I
˝)Beceives °dONLNdM
Jä
Vó(
Säan —`°dONLNdP
Jó
V£)errR†°dONLNdS
J§
V
e).or if the edition container has been deleted. 
°dONLNdÇ
pH
yb(
wHRESULëÄ°dONLNdá
pb
yÜ)T CODES°dONLNd[
ÂH
Óo(
ÏHSEE ALSO
.°dONLNdd
Ûä
ˇú+BSee °dONLNdh
Ûú
ˇ¥)page °dONLNdm
Û¥
ˇ«)2-98°dONLNdq
Û«
ˇ
X)! for detailed information on the °dONLNdí
Û
X
ˇ
¨)ëGetEditionInfo°dONLNd†
Û
¨
ˇ
È)T function. See °dONLNdØ
Û
È
ˇ
)=page °dONLNd¥
Û

ˇ)2-77°dONLNd∏
Û
ˇ)
 °dONLNdπäÔ(    äfor information on the °dONLNd–Ô
U)eUnRegisterSection°dONLNd·
U
‹)f function. For information on fi°dONLNd

‹
Á)ále .
°dONLNdä¶(äspecifiÓ °dONLNd¶«)cation r°dONLNd»⁄)"ecorâ`°dONLNd⁄˘)ds, see 2`°dONLNd˙
W) Inside Macintosh: Files˘@°dONLNd6
W
\)]. 

=HE4>HE @H@

ˇ·ˇ‚7^°dONLNd:0H>|(:H
Setting an}@°dONLNdD0}>°)5d Getti°dONLNdK0¢>

)%ng a Format Markˇˇˇˇˇˇ(:
2
.°dONLNd]EäQØ(NäUse the °dONLNdeEØQ
')%SetEditionFormatMark°dONLNdyE
'Q
å)x function to set the currR`°dONLNdíE
åQ
Ó)eent mark for a section °dONLNd©Rä^´([äformat °dONLNd∞R´^∂)!an°dONLNd≤R∂^¬)d t°dONLNdµR¬^–)he °dONLNd∏R–^
*)GetEditionForma°dONLNd«R
*^
6)ZtM°dONLNd…R
6^
H)ark°dONLNdÃR
H^
t) function t°dONLNd◊R
t^
è),o get t°dONLNdfiR
è^
Æ)he currR`°dONLNdÂR
Æ^
–)ent marR`°dONLNdÏR
–^
‹)"k fR`°dONLNdÔR
‹^
Ô)or a .
°dONLNdÙ_äk⁄(häparticular format. .°dONLNdé
~ä
ä®(
áänoErr.
°dONLNdî
~

ä
)â
0°dONLNdñ
~
,
ä
H)No errE†°dONLNdú
~
I
ä
R)or.°dONLNd†
âä
ïÆ(
íänsvErr.
°dONLNdß
â
    
ï
)–35°dONLNd´
â
,
ï
t)#No such volume.°dONLNdª
îä
†®(
ùäioErr.
°dONLNd¡
î
    
†
)–36°dONLNd≈
î
,
†
L)#I/O err ‡°dONLNdÃ
î
L
†
U) or.°dONLNd–
üä
´∫(
®äbdNamErr.
°dONLNdŸ
ü
    
´
)–37°dONLNd›
ü
,
´
E)#Bad fiD@°dONLNd„
ü
F
´
f)lename.°dONLNdÎ
™ä
∂Æ(
≥äfnfErr.
°dONLNdÚ
™
    
∂
)–43°dONLNd˜
™
,
∂
j)#File not found.°dONLNd
µä
¡∫(
æädirNFErr.
°dONLNd
µ

¡
)z–120°dONLNd
µ
,
¡
:)(DirꠡdONLNd
µ
:
¡
É)ectory not found.°dONLNd*
¿ä
Ã(
…äeditionMgrInitErr.
°dONLNd<
¿

Ã
)z–450°dONLNdA
¿
,
Ã
ì)(Manager not initializedˇä@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-82    )BEdition Manager Reference4^*¿
¯

j*r
¯4j*r
¯ l*l
˛

ˇ·ˇ‚7^
°dONLNd\*j®(f*SetEditionFormatMarkˇˇˇˇˇˇ(f
Ú
2
°dONLNd{lás(Ñl
A∫†°dONLNd{sá
<)/ format mark indicates the next position of a rZ@°dONLNdF{
=á
«) !ead or write operation. Initiallyí`°dONLNdg{
Δá
Ï)â    , a mark °dONLNdpàlîß(ëldefaults to 0. ņ°dONLNdàßîƒ);After r‡`°dONLNdÜàƒî
Ï)Feading or writing data, the format mark is set past the last position °dONLNdÃïl°©(ûlwritten to or r6¿°dONLNd€ï™°√)>ead frµ°dONLNd·ï√°”)om.~Ä°dONLNd‰ï‘°‹) T4@°dONLNdÊï‹°
)o set the curr °dONLNdÙï
°
µ)9%ent mark for a given format, use the ,
Courier.°dONLNd
¢lƉ(´lSetEditionFormatMark°dONLNd
-¢‰Æ
)x
 function.°dONLNd
8ªl«
Œ(ƒl;FUNCTION SetEditionFormatMark (whichEdition: EditionRefNum;°dONLNd
~…
 ’
&+¥
 °dONLNd
…
&’
∂)whichFormat: FormatType;°dONLNd
¢◊
 „
&(‡
 
 °dONLNd
£◊
&„
í)setMarkTo: LongInt°dONLNd
µ◊
í„
û)l):°dONLNd
∑◊
û„
») OSErr;°dONLNd
øÔl˚¥(¯lwhichEdition.
°dONLNd
Ã˚Æ
π+BThr °dONLNd
Œ˚∫
≈)e rÄ¿°dONLNd
—˚≈
’)efer,‡°dONLNd
’˚÷

U)ence number for the edition. .°dONLNd
Û
l
Æ(
lwhichFormat.
°dONLNd
ˇ
Æ
#π+BThr °dONLNd

∫
#ƒ)e f†°dONLNd
≈
#
9)ormat type for the edition..°dONLNd 
'l
3¢(
0l    setMarkTo.
°dONLNd*
'Æ
3π)BThr °dONLNd,
'∫
3Δ)e o1@°dONLNd/
'«
3 )
fWÄ°dONLNd0
' 
3
)fset for the next rX¿°dONLNdC
'

3
å)Kead or write for this format+¿°dONLNd_
'
ç
3
è)x
.
°dONLNda
M*
Vc(
T*DESCRIPTION
.°dONLNdm
Zl
fÄ+BThe °dONLNdq
ZÄ
f¯)SetEditionFormatMark°dONLNdÖ
Z¯
f
V)x function sets the currR`°dONLNdú
Z
V
f
ø)^ent mark for the specifiR`°dONLNd¥
Z
ø
f
Ì)i
ed format °dONLNdæ
gl
sö(
pl
type accorR`°dONLNd»
gö
s
).ding to the value of the R`°dONLNd·
g

s
<)l    setMarkToR`°dONLNdÍ
g
<
s
n)6
 parameterï°dONLNdÙ
g
m
s
p)1
.
.
°dONLNdˆ
é*
óD(
ï*RESULëÄ°dONLNd˚
éD
óh)T CODES


¯*
¯4
¯*
¯ 
˙*
˙
˛

ˇ·ˇ‚7^°dONLNd¢
Í*
¯´(
Ù*GetEditionFormatMarkˇˇˇˇˇˇ(
Ù
Ú
2
.°dONLNd∏
lë(lUse the °dONLNd¿
ëÎ)%GetEditionForma°dONLNdœ
Θ)ZtM°dONLNd—
˜
    )ark°dONLNd‘

    
5) function t°dONLNdfl

5
P),o get t°dONLNdÊ

P
o)he currR`°dONLNdÌ

o
ë)ent marR`°dONLNdÙ

ë
ù)"k fR`°dONLNd˜

ù
·)or a particular .
°dONLNdl#å( lformat..°dONLNd0l<
Œ*;FUNCTION GetEditionFormatMark (whichEdition: EditionRefNum;°dONLNdU>
 J
&+¥
 °dONLNdV>
&J
º)whichFormat: FormatType; °dONLNdzL
 X
&(U
 
 °dONLNd{L
&X
∂)VAR currentMark: LongInt°dONLNdìL
∂X
¬)ê):°dONLNdïL
¬X
Ï) OSErr;°dONLNdùdlp¥(mlwhichEdition.
°dONLNd™pÆ|π+BThr °dONLNd¨p∫|≈)e rÄ¿°dONLNdØp≈|’)efer,‡°dONLNd≥p÷|
U)ence number for the edition. .°dONLNd—ÄlåÆ(âlwhichFormat.
°dONLNd›åÆòπ+BThr °dONLNdflå∫òƒ)e f†°dONLNd‚å≈ò)    ormat typ·¿°dONLNdÎåò
x)+e whose mark you want to get..°dONLNd    úl®Æ(•lcurrentMark°dONLNd®Æ¥ª+BTh°dONLNd®ª¥¬)e °dONLNd®¬¥
:)GetEditionFormatMark°dONLNd-®
:¥
f)x function rR`°dONLNd8®
f¥
ù),eturns the mR`°dONLNdD®
ù¥
–)7ark for the .
°dONLNdP¥Æ¿ (ΩÆspecifiÓ °dONLNdW¥ ¿⁄)ed fß`°dONLNd[¥€¿ı)ormat%‡°dONLNd`¥ˆ¿
D) in this parameterl`°dONLNdr¥
C¿
H)M. .°dONLNd
õl
ßä(
§lnoErr.
°dONLNd
õı
ß˙)â
0°dONLNd

õ

ß
*)No errE†°dONLNd
õ
+
ß
4)or.°dONLNd
¶l
≤ú(
ØlrfNumErr.
°dONLNd
¶Î
≤˙)–51°dONLNd!
¶

≤
G)#Bad edition rª‡°dONLNd.
¶
G
≤
W)9eferh°dONLNd2
¶
X
≤
ë)ence number.°dONLNd?
±l
Ω¢(
∫l    noTypeErr.
°dONLNdI
±Ê
Ω˙)z–102°dONLNdN
±

Ω
ß)( Unknown format (subscriber only).°dONLNdp
ºl
»“(
≈leditionMgrInitErr.
°dONLNdÇ
ºÊ
»˙)z–450°dONLNdá
º

»
u)(Manager not initializedˇ40@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-83
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\HeÅ(cHDESCRIPTION
ˇˇ÷™.°dONLNdjäv
b+B1If the edition does not support the format specifi5P°dONLNd>j
cv
å)Ÿ
ed in the ,
CourierˇˇÉ˛πN°dONLNdHj
åv
Œ))whichFormatˇˇ÷™πN°dONLNdSj
Œv
ˇ)B
 parameter“ò°dONLNd]j
ˇv)1, you °dONLNdcwäÉé(Ää
rR`°dONLNddwéɵ)    eceive a R`°dONLNdmwµÉÎ)'    noTypeErrR`°dONLNdvwÎÉÒ)6 r$¿°dONLNdxwÒÉ
 )esult code.
.
°dONLNdÑùH¶b(§HRESULëÄ°dONLNdâùb¶Ü)T CODES

˚H
4¸H
 ˛H˛

ˇ·ˇ‚7^°dONLNd
ÓH¸«(¯HReading in Edition Dataˇˇˇˇˇˇ(¯
2
.°dONLNd
7
ä
ê(
ä
Tï°dONLNd
8
è
“)o initiate the rg`°dONLNd
H
“

)Ceading of data fr9¿°dONLNd
Y



œ)L*om an edition (for a subscriber), use the 9¿°dONLNd
É

œ
)±OpenEdition9¿°dONLNd
é

)B
 .
°dONLNd
è
ä
±(
ä    function..°dONLNd
ô
"ä
.Ø*Use the °dONLNd
°
"Ø
.
)%EditionHasFormat°dONLNd
±
"

.)`8 function to learn in which formats the edition data is .
°dONLNd
È
/ä
;¥(
8ä
available..°dONLNd
Ù
Aä
MØ*Use the °dONLNd
¸
AØ
MÒ)%ReadEdition°dONLNd
AÒ
M
()B function to rR`°dONLNd
A
(
M
[)7ead data fr$¿°dONLNd 
A
[
M
fi)3om an edition. This function r˜ °dONLNd>
A
›
M
¸)Çeads fr…Ä°dONLNdE
A
¸
M)om .
°dONLNdH
Nä
Z¨(
Wäthe curr`°dONLNdP
N≠
Z
)#ent mark for the specifiG°dONLNdh
N

Z
@)f
ed format.


äH
ì4
ãH
í 
åH
å

ˇ·ˇ‚7^
°dONLNdt
}H
ãè(
áHOpenEditionˇˇˇˇˇˇ(
á
2
.°dONLNdÅ
úä
®ê(
•ä
Tï°dONLNdÇ
úè
®“)o initiate the rg`°dONLNdí
ú“
®
)Ceading of data fr9¿°dONLNd£
ú

®
œ)L*om an edition (for a subscriber), use the 9¿°dONLNdÕ
ú
œ
®)±OpenEdition9¿°dONLNdÿ
ú
®)B
 .
°dONLNdŸ
©ä
µ±(
≤ä    function..°dONLNd„
Š
Œ
‘*7FUNCTION OpenEdition (subscriberSectionH: SectionHandle°dONLNd
¬
‘
Œ
‡(
À
‘; °dONLNd$
–

‹
(
Ÿ

 °dONLNd%
–

‹
&)VAR °dONLNd)
–
&
‹
§)refNum: EditionRefNum°dONLNd>
–
§
‹
∞)~):°dONLNd@
–
∞
‹
⁄) OSErr;°dONLNdH
Ëä
Ùˆ(
ÒäsubscriberSectionH.
°dONLNd[
ÙÔ+B
A∫†°dONLNd\
Ù”€) h°dONLNd^
Ù‹
8)    andle to the section ṙ°dONLNdt
Ù
7
I)[ecorb@°dONLNdx
Ù
J
®)d for a given section. .°dONLNdêäÆ(ärefNum°dONLNdóÇ)BThe °dONLNdõ‡
")OpenEdition°dONLNd¶
"
N)B function rR`°dONLNd±
N
o),eturns tR`°dONLNdπ
o
Å)!he r$¿°dONLNdΩ
Å
ì)efer˜ °dONLNd¡
í)ence number for the edition˜ °dONLNd‹)y
 .
°dONLNd›Ã
(Ãin this parameterFÄ°dONLNdÓ

)K
.
°dONLNd6H?Å(=HDESCRIPTION
.°dONLNd¸CäOû+BThe °dONLNdCûO‡)OpenEdition°dONLNdC‡O
f)B  function opens an edition for rR`°dONLNd+C
fO
û)Üeading and r$¿°dONLNd7C
ûO
«)8
eturns a r˜ °dONLNdAC
ΔO
ÿ)(efer…Ä°dONLNdEC
ÿO
Ì)ence .
°dONLNdJPä\
A(Yä)number that your application can use to r»°dONLNdsP
A\)∑.efer to this edition in other Edition Manager .°dONLNd°]äié(fä
rR`°dONLNd¢]éi≥)    outines. R`°dONLNd´]≥i
_)%'Multiple subscribers can each call the R`°dONLNd“]
_i
°)¨OpenEditionR`°dONLNd›]
°i)B function simultaneously .
°dONLNdˆjävπ(sä(each call r °dONLNdjπvÎ)/eturns a dif#†°dONLNdjÏv¯)3fer °dONLNdj¯v
)ent r(Ä°dONLNdj
v
)efer‘†°dONLNdj
v
r)ence number) and r‡°dONLNd,j
sv
¢)Wead data fr|@°dONLNd7j
¢v)/om a single edition. If a °dONLNdQwäɲ(Ääpublisher (located on a difg@°dONLNdlw˛É

)tferI¿°dONLNdow

É
˝)7ent machine) is writing to an edition when you use the .°dONLNd¶ÑäêÃ(çäOpenEdition°dONLNd±ÑÃê
)B function, you rR`°dONLNd¡Ñ
ê
9)A
eceive an R`°dONLNdÀÑ
9ê
u),
flLckedErrR`°dONLNd’Ñ
uê
{)< r$¿°dONLNd◊Ñ
{ê
ß)
esult code$¿°dONLNd·Ñ
ßê
™),
.°dONLNdê´ä∑®(¥änoErr.
°dONLNdñ´
∑
)â
0°dONLNdò´
,∑
H)No errE†°dONLNdû´
I∑
R)or.°dONLNd¢∂ä¬∫(øärfNumErr.
°dONLNd´∂
    ¬
)–51°dONLNdØ∂
,¬
e)#Bad edition rª‡°dONLNdº∂
e¬
u)9eferh°dONLNd¿∂
v¬
Ø)ence number.°dONLNdÕ¡äÕ¿( ä    noTypeErr.
°dONLNd◊¡
Õ
)z–102°dONLNd‹¡
,Õ
x)(Unknown format.°dONLNdÏÃäÿ(’äeditionMgrInitErr.
°dONLNd˛Ã
ÿ
)z–450°dONLNd
Ã
,ÿ
ì)(Manager not initializedˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-84    )BEdition Manager Reference4^*¿
¯
°dONLNd\*eD(c*RESULëÄ°dONLNd\Deh)T CODES°dONLNd∏ª*ƒQ(¬*SEE ALSO
.°dONLNd¡…l’Î+BFor an example of the use of ,
Courier°dONLNdfi…Î’
-)OpenEdition°dONLNdÈ…
-’
B)B, see °dONLNdÔ…
B’
r)Listing 2-7°dONLNd˙…
r’
Ä)0 on °dONLNd˛…
Ä’
ò)page °dONLNd
…
ò’
´)2-42°dONLNd
…
´’
Æ)
.


*

¯4
*

¯ 
*

˛

ˇ·ˇ‚7^
.
°dONLNd

¯*
1(
*
E‘Ä°dONLNd
¯1
é)ditionHasFormatˇˇˇˇˇˇ(

Ú
2
.°dONLNd

l
#ë(
 lUse the °dONLNd
$
ë
#Ò)%EditionHasFormat°dONLNd
4
Ò
#
Â)`8 function to learn in which formats the edition data is .
°dONLNd
l
$l
0ñ(
-l
available..°dONLNd
w
=l
I
∂*7FUNCTION EditionHasFormat (whichEdition: EditionRefNum;°dONLNd
∏
K

W
V+¢whichFormat:°dONLNd
ƒ
K
V
W
\)H
 °dONLNd
≈
K
\
W
§)FormatType; °dONLNd
€
Y

e
Ü(
b
VAR formatSize: Size°dONLNd
Ô
Y
Ü
e
í)x):°dONLNd
Ò
Y
í
e
º) OSErr;°dONLNd
˘
ql
}¥(
zlwhichEdition.
°dONLNd
}Æ
âπ+BThr °dONLNd
}∫
â≈)e rÄ¿°dONLNd
}≈
â’)efer,‡°dONLNd
}÷
â
U)ence number for the edition. .°dONLNd-
çl
ôÆ(
ñlwhichFormat°dONLNd9
ôÆ
•ª+BTh°dONLNd;
ôª
•Δ)e f°dONLNd>
ôΔ
•
-)ormat type that you arR`°dONLNdT
ô
-
•
8)ge r$¿°dONLNdW
ô
8
•
ä)equesting. For the $¿°dONLNdj
ô
ä
•
Ã)RwhichFormat$¿°dONLNdu
ô
Ã
•
Œ)B
 .
°dONLNdv
•Æ
±€(
ÆÆ    parameterS†°dONLNd
•€
±
Ö)-&, you should decide which formats to rÄ°dONLNd•
•
Ö
±
ı)™ead in the same way that °dONLNdæ
±Æ
Ω‚(
∫Æ
you do whe°dONLNd»
±„
ΩÔ)5n r%`°dONLNdÀ
±Ô
Ω
,)eading data fr †°dONLNdŸ
±
,
Ω
g)=om the scrap.Ä°dONLNdÊ
±
h
Ω
j)<
 e‡°dONLNdÁ
±
j
Ω
p)
Y&`°dONLNdË
±
p
Ω
Ù)"ou can also get a list of all the °dONLNd

ΩÆ
…
+(
ΔÆavailable formats and their r™Ä°dONLNd'
Ω
+
…
ä)}espective lengths by rF¿°dONLNd=
Ω
ã
…
º)`eading the .°dONLNdH
…Æ
’
(
“ÆkFormatListFormat°dONLNdY
…

’
)f (°dONLNd[
…

’
>)'fmts'°dONLNda
…
>
’
h)$
) format. °dONLNdl
Ÿl
®(
‚l
formatSize°dONLNdw
ÂÆ
Òª+BTh°dONLNdy
ª
Ò¬)e °dONLNd{
¬
Ò
")EditionHasFormat°dONLNdã
Â
"
Ò
N)` function rR`°dONLNdñ
Â
N
Ò
Å),eturns the fR`°dONLNd¢
Â
Å
Ò
º)3ormat lengthR`°dONLNdÆ
Â
º
Ò
fi);     in this .
°dONLNd∑
ÒÆ
˝€(
˙Æ    parameterS†°dONLNd¿
Ò€
˝›)-
.
°dONLNd¬* c(*DESCRIPTION
.°dONLNdŒ$l0å+BIf the rR`°dONLNd÷$å0
) equested format is availableR`°dONLNdÚ$
0
#)Ç, theR`°dONLNd˜$
#0
%)
 R`°dONLNd¯$
%0
Ö)EditionHasFormatR`°dONLNd$
Ö0
ã)` fR`°dONLNd
$
ã0
±)    unction r$¿°dONLNd$
±0
Œ)&eturns $¿°dONLNd$
Œ0
Ï)noErrg`°dONLNd$
Î0
), °dONLNd!1l=ë(:land the °dONLNd)1ë=Õ)%
formatSize°dONLNd31Õ=
)< parameter rR`°dONLNd?1
=
∏)8)eturns the size of the data in the specifiR`°dONLNdi1
∏=
Ò)≥ed format or °dONLNdv>lJ‰(GlkFormatLengthUnknown°dONLNdä>‰J
7)x (–1), which signifPÄ°dONLNdù>
7J
π)Sies that the size is unknown. "‡°dONLNdª>
πJ
¿)Ç
Y7‡°dONLNdº>
øJ
Ï)
ou should .
°dONLNdΔKlW}(Tlther"`°dONLNd K~Wè)eforz`°dONLNdŒKèWŒ)e continue to rƒ‡°dONLNd›KŒW
:)?ead the format until therË°dONLNdˆK
:W
j)le is no mor¨`°dONLNd
K
kW
Ö)1e dataT °dONLNdK
ÜW
à)
..°dONLNdjlvä(slnoErr.
y†°dONLNdj
v
)î
0y†°dONLNdj
v
5)No err?@°dONLNdj
6v
?)or.°dONLNdulÅê(~lfnfErr.
y†°dONLNd%uˆÅ
)ä–43y†°dONLNd)u
Å
W)#File not found.°dONLNd9Älå®(âl
flLckedErr.
y†°dONLNdDĈå
)ä–45y†°dONLNdHÄ
å
†)#Publisher writing to an edition.°dONLNdiãlóñ(îlpermErr.
y†°dONLNdqãˆó
)ä–54y†°dONLNduã
ó
a)#Not a subscriber.°dONLNdáñl¢“(üleditionMgrInitErr.
y†°dONLNdôñÒ¢
)Ö–450y†°dONLNdûñ
¢
Ä)(Manager not initializedˇ3B@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-85
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

^Hk4^Hk    °dONLNd]ähù(eäNote

ˇ·ˇ‚7^
°dONLNd
iäu£*The TˆÄ°dONLNdi¢u
î):ranslation Manager (if it is available) attempts implicit °dONLNdIuäź(~ätranslation ù`°dONLNdUuºÅ
)2under certain cirî °dONLNdfu
Å
ø)I*cumstances. For instance, it does so when °dONLNdêÅäç
(ääyour application attempts to rV°dONLNdÆÅ
ç
')Ñead fr‘@°dONLNd¥Å
'ç
¬)$om an edition a format type that is °dONLNdÿçäô
'(ñä'not in the edition. In this case, the T◊¿°dONLNdˇç
&ô
≥)úranslation Manager attempts to °dONLNd
ôä•

(¢ätranslate the data into the rá@°dONLNd
;ô

•
q)wequested format. For mor˜†°dONLNd
Sô
q•
≤)pe information, °dONLNd
b•ä±ö(Æäsee –@°dONLNd
f•ö±Ÿ)the chapter “T*¿°dONLNd
t•Ÿ±
B)?ranslation Manager” in QÄ°dONLNd
ã•
B±
å)iInside Macintosh: °dONLNd
ù±äΩõ(∫äMorÄ°dONLNd
†±úΩ¢)e z °dONLNd
¢±¢Ωœ)
Macintosh ꠡdONLNd
¨±œΩ’)-
TꠡdONLNd
≠±‘ΩÌ)oolbox£†°dONLNd
≥±ÓΩ)
.,Zapf Dingbats#†°dONLNd
µ¥ˆº¸)
u
°dONLNd
∏÷HflM(›H
RG°dONLNd
π÷Nflb)ESULëÄ°dONLNd
Ω÷bflÜ)T CODES°dONLNdW
*H
3o(
1HSEE ALSO
.°dONLNd`
8ä
D
    +BFor an example of the use of ,
Courier°dONLNd}
8
    
D
i)EditionHasFormat°dONLNdç
8
i
D
~)`, see °dONLNdì
8
~
D
Æ)Listing 2-7°dONLNdû
8
Æ
D
È)0 beginning on .
°dONLNd¨
Eä
Q°(
Näpage Z‡°dONLNd±
E¢
Q¥)2-42Æ¿°dONLNdµ
E¥
Q
3). For information about the T¿ °dONLNd“
E
3
Q
‚)$ranslation Manager and Scrap Manager†°dONLNdˆ
E
‚
Q
˜)Ø, see °dONLNd¸
Rä
^§(
[äInside qÄ°dONLNd
R•
^Ê)Macintosh: Mor¯Ä°dONLNd
RÊ
^
)Ae Macintosh TÆ°dONLNd
R

^
8)9oolboxÖ†°dONLNd$
R
9
^
;)
.


éH
ó4
èH
ñ 
êH
ê

ˇ·ˇ‚7^
°dONLNd'
ÅH
èP(
ãH
R)¿°dONLNd(
ÅQ
èå)
eadEditionˇˇˇˇˇˇ(
ã
2
.°dONLNd4
†ä
¨Ø(
©äUse the °dONLNd<
†Ø
¨Ò)%ReadEdition°dONLNdG
†Ò
¨
()B function to rR`°dONLNdU
†
(
¨
[)7ead data fr$¿°dONLNd`
†
[
¨
fi)3om an edition. This function r˜ °dONLNd~
†
›
¨
¸)Çeads fr…Ä°dONLNdÖ
†
¸
¨)om .
°dONLNdà
≠ä
π¨(
∂äthe curr`°dONLNdê
≠≠
π
)#ent mark for the specifiG°dONLNd®
≠

π
@)f
ed format..°dONLNd≥
Δä
“
º(
œä3FUNCTION ReadEdition (whichEdition: EditionRefNum; °dONLNdÓ
‘

‡
+~
 °dONLNdÔ
‘

‡)+whichFormat: FormatType; buffPtr: UNIV Ptr;°dONLNd"
‚

Ó
(
Î

 °dONLNd#
‚

Ó
t)VAR buffLen: Size°dONLNd4
‚
t
Ó
Ä)f):°dONLNd6
‚
Ä
Ó
™) OSErr;°dONLNd>
˙ä“(äwhichEdition.
°dONLNdKÃ◊+BThr °dONLNdMÿ„)e rÄ¿°dONLNdP„Û)efer,‡°dONLNdTÙ
s)ence number for the edition. .°dONLNdrä"Ã(äwhichFormat.
°dONLNd~"Ã.◊+BThr °dONLNdÄ"ÿ.‚)e f†°dONLNdÉ"„.
e)ormat type that you want to rt‡°dONLNd†"
e.
y)Çead. .°dONLNd¶2ä>Æ(;äbuffPt°dONLNd¨2Æ>¥)$
r.
°dONLNdÆ2Ã>”)
A∫†°dONLNdØ2”>€) p<¿°dONLNd±2‹>
#)    ointer to the buf4‡°dONLNd¬2
#>
û)Gfer into which you want to r¸`°dONLNdfi2
û>
÷){ead the data..°dONLNdÏBäNÆ(KäbuffLe°dONLNdÚBÆN¥)$
n.
°dONLNdÙBÃN
y)&The number of bytes that you want to rû¿°dONLNdB
yN
æ)≠ead into the buf °dONLNd*B
øN
À)FferZ‡°dONLNd-B
 N
’). T{†°dONLNd0B
’N
‚)he .°dONLNd3NÃZ
(WÃReadEdition°dONLNd>N
Z
:)B function rR`°dONLNdIN
:Z
[),eturns tR`°dONLNdQN
[Z
i)!he R`°dONLNdTN
iZ
à)actual R`°dONLNd[N
àZ
…)number of byteR`°dONLNdiN
…Z
”)As r$¿°dONLNdlN
”Z)
ead in the °dONLNdwZÃfˆ(cÃbuffLen°dONLNd~Zˆf
()*
 parameter¬†°dONLNdàZ
'f
*)1
.¬†°dONLNdâZ
*f
,)
 °dONLNd
ƒ‰ä®(ÌänoErr.
°dONLNd
 ‰

)â
0°dONLNd
É
,
H)No errE†°dONLNd
“‰
I
R)or.°dONLNd
÷Ôä˚∫(¯ärfNumErr.
°dONLNd
flÔ
    ˚
)–51°dONLNd
„Ô
,˚
e)#Bad edition rª‡°dONLNd
Ô
e˚
u)9eferh°dONLNd
ÙÔ
v˚
Ø)ence number.°dONLNd
˙ä
¿(
ä    noTypeErr.
°dONLNd˙


)z–102°dONLNd˙
,

á)(Format not available.°dONLNd&
ä
(
äeditionMgrInitErr.
°dONLNd8



)z–450°dONLNd=

,

ì)(Manager not initializedˇd@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-86    )BEdition Manager Reference4^*¿
¯
°dONLNd\*ec(c*DESCRIPTION
.°dONLNdjlvÄ+BThe ,
Courier°dONLNdjÄv¬)ReadEdition°dONLNdj¬vÓ)B function rR`°dONLNd&jÓv
%),eads data fr$¿°dONLNd2j
%v
≠)7om the edition into the specifi$¿°dONLNdQj
≠v
»)àed buf˜ °dONLNdWj
«v
‘)fer9¿°dONLNdZj
‘v
Ÿ). ˇˇn¯°dONLNd\wlÉÆ(ÄlReadEditionˇˇœ®°dONLNdgwÆÉ≥)B r"°dONLNdiw¥ÉÌ)eturns in the ˇˇn¯ë°dONLNdwwÌÉ
)9buffLenˇˇœ®ë°dONLNd~w
É
ø)*& parameter the total number of bytes r¯°dONLNd§w
¿É
¯)©ead into the °dONLNd±Ñlêz(çlbufR`°dONLNd¥Ñzêá)ferï°dONLNd∑ÑÜêß)    . If the ï°dONLNd¿Ñßê—)!buffLenï°dONLNd«Ñ—ê
    )* parameter rg`°dONLNd”Ñ
    ê
·)8/eturns a value smaller than the value you have °dONLNd
ëlùä(ölspecifi°dONLNd
    ëäùÆ)ed, therR`°dONLNd
ëÆù
&)$e is no additional data to r$¿°dONLNd
-ë
&ù
a)xead, and the $¿°dONLNd
:ë
aù
£);ReadEdition$¿°dONLNd
Eë
£ù
œ)B function r˜ °dONLNd
Pë
Ν
Û)+    eturns a °dONLNd
Yûl™ä(ßlnoErr°dONLNd
^ûä™ê) rR`°dONLNd
`ûê™ˇ)esult code. If you use the R`°dONLNd
{ûˇ™
A)oReadEditionR`°dONLNd
Üû
A™
∏)B function after all data is r$¿°dONLNd
£û
∏™
Î)wead in, the °dONLNd
Ø´l∑Æ(¥lReadEdition°dONLNd
∫´Æ∑⁄)B function rR`°dONLNd
≈´⁄∑
),
eturns an R`°dONLNd
ϫ
∑
()*eofErrR`°dONLNd
’´
(∑
.)$ r$¿°dONLNd
◊´
.∑
])esult code..
°dONLNd
„Ωl…r(Δl
Y@Ä°dONLNd
‰Ωr…ï)ou can r√¿°dONLNd
ÏΩï…ƒ)#ead data fr  °dONLNd
˜Ω≈…
ˆ)0Dom an edition while a publisher on the same machine is writing data °dONLNd; l÷
(”l)to the same edition. The data that you ar°dONLNdd 
÷
))≤e r˛†°dONLNdg 
)÷
ı)1eading is the old edition (not the data that the °dONLNdò◊l„
(‡l)publisher is writing). If the publisher fi+Ä°dONLNd¬◊
„
Ü)¨nishes writing data beforu@°dONLNd€◊
Ü„
©)ne you ar†°dONLNd„◊
™„
æ)$e thr2°dONLNdË◊
æ„
◊)ough .°dONLNd̉lp(Ìl
rR`°dONLNdÓ‰p
)!eading the old edition data, the R`°dONLNd‰

F)îReadEditionR`°dONLNd‰
F
r)B function r$¿°dONLNd%‰
r
ú),
eturns an $¿°dONLNd/‰
ú
Ã)*abortErr$¿°dONLNd7‰
Ã
“)0 r˜ °dONLNd9‰
—
È)esult °dONLNd?Òl˝°(˙lcode. If the °dONLNdLÒ°˝„)5ReadEdition°dONLNdWÒ„˝
)B function rR`°dONLNdbÒ
˝
9),
eturns an R`°dONLNdlÒ
9˝
i)*abortErrR`°dONLNdtÒ
i˝
o)0 r$¿°dONLNdvÒ
o˝
Ë)esult code, you should stop °dONLNdí˛l

ô(
ltrying to rR`°dONLNdù˛ô

˘)-ead data and use the R`°dONLNd≤˛˘


A)`CloseEditionR`°dONLNdæ˛
A


î)H function with the R`°dONLNd—˛
î


–)S
successfulR`°dONLNd€˛
–


“)<
 °dONLNd‹
l
∏(
lparameter set to °dONLNdÌ
∏
÷)LFALSE°dONLNdÚ
÷
Ÿ)
.°dONLNdÛ
Ÿ
€)
 


%*
3
¯4
&*
3
¯
    .
°dONLNdı
$l
/(
,lNote

ˇ·ˇ‚7^
°dONLNd˙
1l
=Ö*The TˆÄ°dONLNdˇ
1Ñ
=
v):ranslation Manager (if it is available) attempts implicit °dONLNd9
=l
Iû(
Fltranslation ù`°dONLNdE
=û
IÁ)2under certain cirî °dONLNdV
=Á
I
°)I*cumstances. For instance, it does so when °dONLNdÄ
Il
U(
Rlyour application attempts to rV°dONLNdû
I
U
    )Ñead fr‘@°dONLNd§
I
    
U
§)$om an edition a format type that is °dONLNd»
Ul
a
    (
^l'not in the edition. In this case, the T◊¿°dONLNdÔ
U

a
ï)úranslation Manager attempts to °dONLNd
al
m„(
jltranslate the data into the rá@°dONLNd+
a„
m
S)wequested format. For mor˜†°dONLNdC
a
S
m
î)pe information, °dONLNdR
ml
y|(
vlsee –@°dONLNdV
m|
yª)the chapter “T*¿°dONLNdd
mª
y
$)?ranslation Manager” in QÄ°dONLNd{
m
$
y
n)iInside Macintosh: °dONLNdç
yl
Ö}(
ÇlMorÄ°dONLNdê
y~
ÖÑ)e z °dONLNdí
yÑ
Ö±)
Macintosh ͆°dONLNdú
y±
Ö∑)-
T͆°dONLNdù
y∂
Öœ)oolbox£†°dONLNd£
y–
Ö“)
.,Zapf Dingbats#†°dONLNd•
|ÿ
Ñfi)
u
q†°dONLNd¶
yfi
Ö‡)
 
°dONLNd©
û*
ßD(
•*RESULëÄ°dONLNdÆ
ûD
ßh)T CODES°dONLNd”*'Q(%*SEE ALSO
.°dONLNd‹,l8Î+BFor an example of the use of °dONLNd˘,Î8
-)ReadEdition°dONLNd,
-8
B)B, see °dONLNd
,
B8
r)Listing 2-7°dONLNd,
r8
≠)0 beginning on °dONLNd#,
≠8
≈);page °dONLNd(,
≈8
ÿ)2-42°dONLNd,,
ÿ8
›). 

\*d
¯4]*d
¯ _*_
˛

ˇ·ˇ‚7^.
°dONLNd0O*]6(Y*
Wú¿°dONLNd1O5]≠)riting out Edition Dataˇˇˇˇˇˇ(Y
Ú
2
°dONLNdJdlpr(ml
Tµ¿°dONLNdKdqpˆ)!o initiate the writing of data frfl °dONLNdldˆp
û)Ö'om a publisher to its edition containerf°dONLNdìd
ûp
ƒ)®
, use the .°dONLNdùql}¿(zlOpenNewEdition°dONLNd´q¿}ı)T function. (Tï°dONLNd∏qÙ}
)4o crg`°dONLNdºq
}
s)eate an edition container™°dONLNd’q
r}
ô)o
, use the °dONLNdfl~lä
(álCreateEditionContainerFile°dONLNd˘~
ä
x)ú function, as described on °dONLNd~
xä
ê)ppage °dONLNd~
êä
£)2-79°dONLNd~
£ä
™).)°dONLNd êlúë(ôlUse the °dONLNd(êëúŸ)%WriteEdition°dONLNd4êŸú
{)H& function to write data to an edition.°dONLNdµ
¨l
∏ä(
µlnoErr.
°dONLNdª
¨ı
∏˙)â
0°dONLNdΩ
¨

∏
*)No errE†°dONLNd√
¨
+
∏
4)or.°dONLNd«
∑l
√ú(
¿labortErr.
°dONLNd–
∑Î
√˙)–27°dONLNd‘
∑

√
´)##Publisher has written a new edition.°dONLNd˘
¬l
Ί(
ÀlioErr.
°dONLNdˇ
¬Î
Œ˙)–36°dONLNd
¬

Œ
.)#I/O err ‡°dONLNd

¬
.
Œ
7) or.°dONLNd
Õl
Ÿú(
÷lfnOpnErr.
°dONLNd
ÕÎ
Ÿ˙)–38°dONLNd
Õ

Ÿ
G)#File not open.°dONLNd*
ÿl
‰ê(
·leofErr.
°dONLNd1
ÿÎ
‰˙)–39°dONLNd5
ÿ

‰
0)#No mor“‡°dONLNd;
ÿ
0
‰
ä)"e data of that format.°dONLNdR
„l
Ôú(
ÏlrfNumErr.
°dONLNd[
„Î
Ô˙)–51°dONLNd_
„

Ô
G)#Bad edition rª‡°dONLNdl
„
G
Ô
W)9eferh°dONLNdp
„
X
Ô
ë)ence number.°dONLNd}
Ól
˙¢(
˜l    noTypeErr.
°dONLNdá
ÓÊ
˙˙)z–102°dONLNdå
Ó

˙
i)(Format not available.°dONLNd¢
˘l“(leditionMgrInitErr.
°dONLNd¥
˘Ê˙)z–450°dONLNdπ
˘

u)(Manager not initializedˇ7Ê@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-87
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

jHr4jHr lHl

ˇ·ˇ‚7^°dONLNd\Hj©(fHOpenNewEditionˇˇˇˇˇˇ(f
2
°dONLNd{äáê(Ñä
Tµ¿°dONLNd{èá
)!o initiate the writing of data frfl °dONLNd2{
á
º)Ö'om a publisher to its edition containerf°dONLNdY{
ºá
‚)®
, use the ,
Courier.°dONLNdcàäîfi(ëäOpenNewEdition°dONLNdqàfiî
)T
 function.°dONLNd|°ä≠
Ê(™ä:FUNCTION OpenNewEdition (publisherSectionH: SectionHandle;°dONLNdøØ
ª
\+ê fdCreator:°dONLNd Ø
\ª
b)B
 °dONLNdÀØ
bª
å)OSType;°dONLNd€Ω
…
˛(Δ
& publisherSectionDocument: FSSpecPtr; °dONLNd

À
◊
∂* VAR refNum: EditionRefNum°dONLNd
$À
∂◊
¬)ú):°dONLNd
&À
¬◊
Ï) OSErr;°dONLNd
.„äÔ(ÏäpublisherSectionH.
°dONLNd
@ÔÃ˚◊+BThr °dONLNd
BÔÿ˚Â)e pΩ‡°dONLNd
EÔÂ˚
≠)1ublisher section that is writing to the edition. .°dONLNd
wˇä
¿(
ä    fdCreator.
°dONLNd
ÅˇÃ
◊)BThr °dONLNd
ɡÿ
‰)e FJ‡°dONLNd
ܡÂ

)inder cr뇰dONLNd
éˇ


û)"#eator type of the new edition icon..°dONLNd
≤
ä

(
äpublisherSectionDocument.
°dONLNd
À
Ã
'◊+BThr °dONLNd
Õ
ÿ
'Â)e d◊Ä°dONLNd
–
Â
'
É)#ocument that contains the publisher`°dONLNd
Û

Ñ
'
˚)ü. This parameter is used to °dONLNd
'Ã
3‘(
0Ãcrµ@°dONLNd
'‘
3
)eate an alias fr‡°dONLNd!
'

3
ú)@om the edition to the publisherh°dONLNd@
'
ù
3
)â’s document. If you pass .°dONLNdY
3Ã
?fi(
<ÃNIL!†°dONLNd\
3fi
?Ô) for !†°dONLNda
3Ô
?
)publisherSectionDocument!†°dONLNdy
3

?
˝)ê, an alias is not made in the .
°dONLNdó
?Ã
KÛ(
HÃ    edition fiL °dONLNd°
?Ù
K˛)(le..°dONLNd•
Oä
[Æ(
XärefNum°dONLNd¨
OÃ
[‡)BThe °dONLNd∞
O‡
[
4)OpenNewEdition°dONLNdæ
O
4
[
`)T function rR`°dONLNd…
O
`
[
ì),eturns the r$¿°dONLNd’
O
ì
[
•)3efer˜ °dONLNdŸ
O
§
[
€)ence number .
°dONLNdÂ
[Ã
g€(
dÃfor º°dONLNdÈ
[€
gÎ)the `°dONLNdÌ
[Ï
g
Y)edition in this parameterü@°dONLNd
[
X
g
])l. q†°dONLNd
[
]
g
c)
Y2 °dONLNd    
[
c
g
©)ou specify this rq@°dONLNd
[
©
g
π)Fefer`°dONLNd
[
∫
g
–)ence .°dONLNd#
gÃ
sÓ(
pÃnumber °dONLNd*
gÓ
s˙)"as °dONLNd-
g˙
s
)a °dONLNd/
g

s
ó)"parameter for subsequent calls to °dONLNdQ
g
ó
s
fl)ïWriteEdition°dONLNd]
g
fl
s
‰)H, °dONLNd_
sÃ

D(
|ÃSetEditionFormatMark°dONLNds
s
D

\)x, and °dONLNdy
s
\

§)CloseEdition°dONLNdÖ
s
§

Ù)H to specify which .
°dONLNdó
Ã
ã(
àÃMpublisher is writing its data to an edition. If the edition cannot be opened °dONLNd‰
ãÃ
ó
5*for writing because ther͇°dONLNd¸
ã
5
ó)i5e is another publisher writing to it, or because the °dONLNd1
óÃ
£“(
†Ã
fiå¿°dONLNd3
ó“
£
Ä)(le system does not allow writing, an errˆ °dONLNd[
ó
Ä
£
ô)Æor is rH†°dONLNdb
ó
ö
£
“)eturned and .°dONLNdn
£Ã
Ø
 (
¨ÃOpenNewEdition°dONLNd|
£
 
Ø
5)T sets °dONLNdÇ
£
5
Ø
Y)refNum°dONLNdà
£
Y
Ø
f)$ to °dONLNdå
£
f
Ø
x)NIL°dONLNdè
£
x
Ø
}). 
.
°dONLNdí
…H
“Å(
–HDESCRIPTION
.°dONLNdû
֊
‚û+BThe °dONLNd¢
÷û
‚Ú)OpenNewEdition°dONLNd∞
÷Ú
‚
)T
 function °dONLNd∫
÷

‚
’)(+opens an edition for writing. The function °dONLNdÂ
÷
’
‚
Ÿ)ª
rR`°dONLNdÊ
÷
Ÿ
‚)
eturns an ˇˇW≤°dONLNd
„ä
Ô¿(
Ïä    flLckdErrˇˇ«Ê°dONLNd˘
„¿
Ô≈)6 rF°dONLNd˚
„Δ
Ô
)esult code if therDX°dONLNd
„

Ô
µ)K&e is a subscriber on another machine ré°dONLNd3
„
µ
Ô
ı)§eading data fr.°dONLNdA
„
ı
Ô)@om the ˇˇ˜|°dONLNdH
ä
¸‹(
˘äsame edition. The ˇˇÊtft°dONLNdZ
›
¸
1)SOpenNewEditionˇˇ˜|ft°dONLNdh

1
¸
\)T function r'ðdONLNds

]
¸
Å),    eturns a ˇˇÊtƒ°dONLNd|

Ç
¸
¨)%permErrˇˇ˜|ƒ°dONLNdÉ

¨
¸
±)* r‡†°dONLNdÖ

±
¸
¸)esult code if therôt°dONLNdó

˝
¸)Le is a .
°dONLNdû
˝ä    ç(ä
rE°dONLNdü
˝é    ´)egisterî °dONLNd¶
˝´    
Ä)0ed publisher to that edition on another machine.°dONLNd◊ä
!(ä The Edition Manager allows two rç`°dONLNd˜
!
>)óegister‹Ä°dONLNd˛
>
ô)ed publishers that arΔ@°dONLNd
ô
‡)[e located on the ™°dONLNd$
·
Ù)Hsame®¿°dONLNd(
ı
˜)
 °dONLNd)ä((%äXmachine to write to the same edition. Note that multiple publishers cannot write to the °dONLNdÅ)ä5*Vsame edition simultaneously—only one publisher can write to an edition at a given time@°dONLNd◊)5(2
.
°dONLNdŸPHYb(WHRESULëÄ°dONLNdfiPbYÜ)T CODES
.°dONLNdÂ]äi®+(noErr.
°dONLNdÎ]
i
)â
0°dONLNdÌ]
,i
H)No errE†°dONLNdÛ]
Ii
R)or.°dONLNd˜hät®(qäioErr.
°dONLNd˝h
    t
)–36°dONLNd
h
,t
L)#I/O err ‡°dONLNdh
Lt
U) or.°dONLNdsä¿(|ä    flLckdErr.
°dONLNds
    
)–45°dONLNds
,
º)#!Edition in use by another section.°dONLNd=~ää¥(áäpermErr.
°dONLNdE~
    ä
)–54°dONLNdI~
,ä
P)#Register} °dONLNdQ~
Pä
‚)$ed publisher on another machine.°dONLNdrâäï¿(íä    wrPermErr.
°dONLNd|â
    ï
)–61°dONLNdÄâ
,ï
q)#Not a publisher.°dONLNdëîä†(ùäeditionMgrInitErr.
°dONLNd£î
†
)z–450°dONLNd®î
,†
ì)(Manager not initializedˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-88    )BEdition Manager Reference4^*¿
¯
°dONLNd\*eQ(c*SEE ALSO
.°dONLNd    jlvÎ+BFor an example of the use of ,
Courier°dONLNd&jÎv
?)OpenNewEdition°dONLNd4j
?v
T)T, see °dONLNd:j
Tv
Ñ)Listing 2-5°dONLNdEj
Ñv
ø)0 beginning on .
°dONLNdTwlÉÉ(Älpage Z‡°dONLNdYwÑÉñ)2-36Æ¿°dONLNd]wñÉõ). 

≥*º
¯4¥*ª
¯ µ*µ
˛

ˇ·ˇ‚7^
°dONLNda¶*¥6(∞*
Wú¿°dONLNdb¶5¥p)riteEditionˇˇˇˇˇˇ(∞
Ú
2
.°dONLNdo≈l—ë(ŒlUse the °dONLNdw≈ë—Ÿ)%WriteEdition°dONLNdÉ≈Ÿ—
ÿ)H< function to write data to an edition. This function begins .
°dONLNdø“lfiº(€lwriting at the curr°dONLNd““Ωfi
#)Qent mark for the specifiF†°dONLNdÍ“
#fi
P)f
ed format..°dONLNdıÎl˜
§(Ùl4FUNCTION WriteEdition (whichEdition: EditionRefNum; °dONLNd
1˘Í
+~
 °dONLNd
2˘
ˆ)
 °dONLNd
3˘ˆ

å)whichFormat: FormatType; °dONLNd
T
Í
(
Í
 °dONLNd
U

ˆ)
 °dONLNd
V
ˆ

∂) buffPtr: UNIV Ptr; buffLen: Size°dONLNd
v

∂

¬)¿):°dONLNd
x

¬

Ï) OSErr;°dONLNd
Ä
l
+¥(
(lwhichEdition.
°dONLNd
ç
+Æ
7π+BThr °dONLNd
è
+∫
7≈)e rÄ¿°dONLNd
í
+≈
7’)efer,‡°dONLNd
ñ
+÷
7
U)ence number for the edition. .°dONLNd
¥
;l
GÆ(
DlwhichFormat.
°dONLNd
¿
GÆ
S
_+B(The format type that you want to write. .°dONLNd
È
Wl
cê(
`lbuffPt°dONLNd
Ô
Wê
cñ)$
r.
°dONLNd
Ò
WÆ
cµ)
A∫†°dONLNd
Ú
Wµ
cΩ) p<¿°dONLNd
Ù
Wæ
c
)    ointer to the buf4‡°dONLNd
W

c
)GfeR`°dONLNd
W

c
û)#r containing the data to write to tÏ¿°dONLNd*
W
û
c
œ)ëhe edition. .°dONLNd7
gl
sñ(
plbuffLen.
°dONLNd?
gÆ
sπ)BThr °dONLNdA
g∫
s«)e nç °dONLNdD
g«
s
n)%umber of bytes that you want to write¿°dONLNdi
g
o
s
±)® to the edition. 
°dONLNd{
ç*
ñc(
î*DESCRIPTION
.°dONLNdá
öl
¶Ä+BThe °dONLNdã
öÄ
¶»)WriteEdition°dONLNdó
ö»
¶
?)H function writes the specifi°dONLNd≥
ö
?
¶
‡)w&ed number of bytes to the edition. If °dONLNdŸ
ßl
≥~(
∞lthe °dONLNd›
ß~
≥◊)data cannot be entirR`°dONLNdÒ
ß◊
≥
a)Y ely written to the edition, the R`°dONLNd
ß
a
≥
©)äWriteEditionR`°dONLNd
ß
©
≥
’)H function r$¿°dONLNd(
ß
’
≥
Ú),eturns .
°dONLNd/
¥l
¿Ü(
Ωlan errR†°dONLNd5
¥Ü
¿è)or˝`°dONLNd7
¥é
¿ê)
.
°dONLNd9
€*
‰D(
‚*RESULëÄ°dONLNd>
€D
‰h)T CODES°dONLNd‰:*CQ(A*SEE ALSO
°dONLNdÌGlS
G+B3For an example that writes data to an edition, see  °dONLNd G
HS
v)‹Listing 2-5´`°dONLNd+G
vS
µ). beginning on &†°dONLNd9G
∂S
Õ)@page 
Ä°dONLNd>G
ŒS
‡)2-36U`°dONLNdBG
‡S
Â). 

x*Ä
¯4x*
¯ z*z
˛

ˇ·ˇ‚7^°dONLNdFj*xè(t*Closing an Edition ÂÄ°dONLNdYjèx˜)eAfter Reading or W@°dONLNdkj˜x
)hritingˇˇˇˇˇˇ)˚
2
.°dONLNdslãé(àlAfter fi°dONLNd{éã∂)"    nishing rR`°dONLNdÑ∂ãfl)(    eading fr$¿°dONLNdçflã
}))%om or writing to an edition, use the $¿°dONLNd≤
}ã
≈)ûCloseEdition$¿°dONLNdæ
ŋ
¯)H function to .
°dONLNdÀålò∂(ïlclose the edition..°dONLNdE
Ël
Ùä(
ÒlnoErr.
y†°dONLNdK
Ë˝
Ù
)ë
0y†°dONLNdM
Ë

Ù
2)No err?@°dONLNdS
Ë
3
Ù
<)or.°dONLNdW
Ûl
ˇ¢(
¸l    dskFulErr.
y†°dONLNda
ÛÛ
ˇ
)á–34y†°dONLNde
Û

ˇ
E)#Disk is full.°dONLNds
˛l
ä(lioErr.
y†°dONLNdy
˛Û

)á–36y†°dONLNd}
˛


6)#I/O errƒÄ°dONLNdÑ
˛
6

?) or.°dONLNdà    lú(lrfNumErr.
y†°dONLNdë    Û
)á–51y†°dONLNdï    

O)#Bad edition rµÄ°dONLNd¢    
O
_)9efera†°dONLNd¶    
`
ô)ence number.°dONLNd≥l “(leditionMgrInitErr.
y†°dONLNd≈Ó 
)Ç–450y†°dONLNd 
 
})(Manager not initializedˇ8V@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-89
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

jHr4jHr lHl

ˇ·ˇ‚7^°dONLNd\Hjè(fHCloseEditionˇˇˇˇˇˇ(f
2
.°dONLNd{äáØ(ÑäUse the ,
Courier°dONLNd{Øá˜)%CloseEdition°dONLNd"{˜á
§)H) function to close an edition after you fi°dONLNdL{
§á
æ)≠nish rR`°dONLNdR{
æá
Á)    eading fr$¿°dONLNd[{
Áá
))om or .
°dONLNdaàäî¡(ëäwriting to it..°dONLNdp°ä≠
¬*4FUNCTION CloseEdition (whichEdition: EditionRefNum; °dONLNd¨Ø
ª
+~
 °dONLNd≠Ø
ª
)
 °dONLNdÆØ
ª
Ä)successful: Boolea°dONLNd¿Ø
Ī
í)ln):°dONLNd√Ø
íª
º) OSErr;°dONLNdÀ«ä”“(–äwhichEdition.
°dONLNdÿ”Ãfl◊+BThr °dONLNd⁄”ÿfl„)e rÄ¿°dONLNd›”„flÛ)efer,‡°dONLNd·”Ùfl
s)ence number for the edition. .°dONLNdˇ„äÔ¿(Ïä    successfu°dONLNd
„¿ÔΔ)6
lˇˇòj°dONLNd

ÔÃ˚‘+
AÛ`°dONLNd
Ô”˚

) value that iºû°dONLNd
Ô
˚
È)81ndicates whether your application was successful O°dONLNd
IÔ
Í˚
Ó)fl
(ˇ˛…>O°dONLNd
JÔ
Ó˚)TRUEˇˇòjO°dONLNd
NÔ˚)) or °dONLNd
S˚Ã

(
Ãunsuccessful (°dONLNd
a˚


%);FALSE°dONLNd
f˚
%

/)) i°dONLNd
i˚
/

:)
n rR`°dONLNd
l˚
:

c)    eading fr$¿°dONLNd
u˚
c

˙))"om or writing data to the edition.
.
°dONLNd
ò
!H
*Å(
(HDESCRIPTION
°dONLNd
§
.ä
:
+B When a subscriber successfully fi¥ °dONLNd
≈
.

:
>)ínishes r«‡°dONLNd
Õ
.
>
:
{)"eading data frm °dONLNd
€
.
|
:
—)>om the edition, the .°dONLNd
Ô
;ä
G“(
DäCloseEdition°dONLNd
˚
;“
G
B)H function takes the modifPÄ°dONLNd
;
B
G
ø)pication date of the edition f!°dONLNd1
;
ø
G)}ile that you have ˇˇú∏°dONLNdC
Hä
Té(
Qä
rR`°dONLNdD
Hé
TÌ)ead and puts it in the ˇ˛÷(˛∞°dONLNd[
HÌ
T
)_mdDateˇˇú∏˛∞°dONLNda
H

T
)$ fiõh°dONLNdd
H

T
r)    eld of the subscriber.°dONLNdy
H
t
T
°)Z’s section r:¿°dONLNdÖ
H
°
T
≥)-ecor °dONLNdâ
H
≥
T)d. This indicates that .
°dONLNd†
Uä
a
(
^äQthe data contained in the edition and the subscriber section within the document °dONLNdÒ
bä
ní*arE°dONLNdÛ
bì
nö)    e 醰dONLNdı
bö
n™)the Ï°dONLNd˘
b™
n√)same.°dONLNdˇ
tä
Ä
2(
}ä&When a subscriber is unsuccessful in r¨Ä°dONLNd%
t
2
Ä
o)®eading data frQ¿°dONLNd3
t
p
Ä
Í)>om an edition (because therqÄ°dONLNdN
t
Í
Ä)z    e is not .°dONLNdW
Åä
ç–(
ääenough memoryd@°dONLNdd
Ŝ
ç
)E, or you didn’t fid@°dONLNdv
Å

ç
ä)Gnd a format that you can r6†°dONLNdê
Å
ä
ç
≈)tead), set the 6†°dONLNdû
Å
≈
ç
);
successful6†°dONLNd®
Å

ç)<
 °dONLNd©
éä
ö«(
óäparameter to °dONLNd∂
é«
öÂ)=FALSE°dONLNdª
éÂ
ö˛). The °dONLNd¡
é˛
ö
F)CloseEdition°dONLNdÕ
é
F
ö)H0 function then closes the edition, but does not °dONLNd˝
õä
ß´(
§äset the °dONLNd
õ´
ßœ)!mdDate°dONLNd
õœ
ßÿ)$ fi°dONLNd
õÿ
ß    )    Eeld. This implies that the subscriber is not updated with the latest .
°dONLNdS
®ä
¥´(
±äedition..°dONLNd\
∫ä
Δ
*When a publisher successfully fi°dONLNd|
∫

Δ
«)í'nishes writing data to an edition, the °dONLNd£
∫
«
Δ)´CloseEdition°dONLNdØ
∫
Δ)H
 .
°dONLNd∞
«ä
”
(
–äWfunction makes the data that the publisher has written to the edition available to any .°dONLNd
‘ä
‡
*subscribers and sets the corrR`°dONLNd$
‘

‡
^){esponding edition fiR`°dONLNd8
‘
^
‡
é)Y
le’s modifiR`°dONLNdC
‘
é
‡
«)0cation date (R`°dONLNdP
‘
«
‡
˝)9    ioFlMdDatR`°dONLNdY
‘
˝
‡)6) to °dONLNd^
·ä
Ìú(
Íäthe °dONLNdb
·ú
Ì¿)mdDate°dONLNdh
·¿
Ì…)$ fi°dONLNdk
·…
Ì
#)    eld of the publisher=`°dONLNd
·
$
Ì
R)[’s section r¿°dONLNdã
·
R
Ì
d).ecor‚ °dONLNdè
·
c
Ì    )$d. The Edition Manager then sends a .
°dONLNd≥
Óä
˙
(
˜äSection Read event to all currÉÄ°dONLNd—
Ó

˙
ÿ)Å.ent subscribers set to automatic update mode. f °dONLNdˇ
Ó
ÿ
˙)ÕAt this point, °dONLNd
˚ä†(äthe fiÍ °dONLNd
˚†
)le type of the edition fi¨@°dONLNd-
˚

f)dle is set based on the fi߆°dONLNdF
˚
g)c$rst known format that the publisher °dONLNdjäñ(äwrú°dONLNdlñ¶)ote..°dONLNdqä&
∂(#äDWhen a publisher is unsuccessful in writing data to an edition, the °dONLNdµ
∂&
˛(#
∂CloseEdition°dONLNd¡
˛&)H
 .
°dONLNd¬'ä3Ã(0äfunction discarц°dONLNd—'Ã3)BLds what the publisher has written to the edition. The data contained in the °dONLNd4ä@ˆ(=äedition prior to writing r>¿°dONLNd74˜@
Δ)m,emains unchanged, and Section Read events arn °dONLNdc4
Δ@
˛)œe not sent to °dONLNdqAäMª(JäsubscribersT‡°dONLNd|AºM¡)2. 
°dONLNdhHqb(oHRESULëÄ°dONLNdÑhbqÜ)T CODES
.°dONLNdãuäÅ®+(noErr.
y†°dONLNdëu
Å
)è
0y†°dONLNdìu
2Å
N)No err?@°dONLNdôu
OÅ
X)or.°dONLNdùÄäå®(âäioErr.
y†°dONLNd£Ä
å
)Ö–36y†°dONLNdßÄ
2å
R)#I/O errƒÄ°dONLNdÆÄ
Rå
[) or.°dONLNd≤ãäó∫(îäfnOpnErr.
y†°dONLNdªã
ó
)Ö–38y†°dONLNdøã
2ó
k)#File not open.°dONLNdŒñä¢∫(üärfNumErr.
y†°dONLNd◊ñ
¢
)Ö–51y†°dONLNd€ñ
2¢
k)#Bad edition rµÄ°dONLNdËñ
k¢
{)9efera†°dONLNdÏñ
|¢
µ)ence number.°dONLNd˘°ä≠(™äeditionMgrInitErr.
y†°dONLNd°

≠
)Ä–450y†°dONLNd°
2≠
ô)(Manager not initializedˇX@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-90    )BEdition Manager Reference4^*¿
¯
°dONLNd\*eQ(c*SEE ALSO
.°dONLNd    jlvÎ+BFor an example of the use of ,
Courier°dONLNd&jÎv
3)CloseEdition°dONLNd2j
3v
H)H, see °dONLNd8j
Hv
x)Listing 2-5°dONLNdCj
xv
≥)0 beginning on .
°dONLNdRwlÉÉ(Älpage Z‡°dONLNdWwÑÉñ)2-36Æ¿°dONLNd[wñÉõ). 

ß*Ø
¯4®*Ø
¯ ™*™
˛

ˇ·ˇ‚7^°dONLNd_ö*®¨(§*Displaying Dialog Boxesˇˇˇˇˇˇ(§
Ú
2
°dONLNdxØlª
(∏l The Edition Manager supports thrg‡°dONLNdòØ
ª
u)óee dialog boxes: publisheráÄ°dONLNd≤Ø
uª
ß)r, subscriberb°dONLNdæØ
ߪ
„)2, and options °dONLNdúl»®(≈ldialog boxes. Ô‡°dONLNd⁄º®»Æ)<
Y∞`°dONLNd€ºÆ»
”)Bour application can display simple dialog boxes that appear center¿°dONLNd
º
‘»
Ô(≈
‘ed on °dONLNd
#…l’è(“lthe userõ °dONLNd
+…ê’¶)$’s scr놰dONLNd
1…¶’
l),een, or you can customize your dialog boxes..°dONLNd
^€lÁë(‰lUse the °dONLNd
f€ëÁ
3)%GetLastEditionContainerUsed°dONLNd
Å€
3Á
⁄)¢( function to get the default edition to .
°dONLNd
©ËlÙå(Òldisplay°dONLNd
∞ËåÙé) 
..°dONLNd
≤˙l
ë(
lUse the °dONLNd
∫˙ë

)%NewSubscriberDialog°dONLNd
Õ˙


Î)r6 function to display the subscriber dialog box on the °dONLNd
l
~(
luser=`°dONLNd

î)’s scr¿°dONLNd
î
⁄)een and use the ¿°dONLNd
⁄

F)FNewPublisherDialog¿°dONLNd/

F

fl)l# function to display the publisher .
°dONLNdR
l
 Œ(
ldialog box on the userx‡°dONLNdh
œ
 Â)c’s scro`°dONLNdn
Â
 
L)een. Unlike the Standarß¿°dONLNdÖ

L
 
g)gd File Ì°dONLNdå

g
 
ç)Package Œ¿°dONLNdî

é
 
ë)'
rì¿°dONLNdï

í
 
«)outines, the .°dONLNd¢
!l
-ÿ(
*lNewPublisherDialog°dONLNd¥
!ÿ
-ˇ)l     and the °dONLNdΩ
!ˇ
-
q)'NewSubscriberDialog°dONLNd–
!
q
-
◊)r functions allow you to .
°dONLNdË
.l
:‚(
7lspecify the initial volume rƒ‡°dONLNd
.‚
:Ú)veferq°dONLNd
.Û
:
O)ence number and dirlÄ°dONLNd
.
O
:
¨)\ectory ID so that ther¶¿°dONLNd1
.
¨
:
‰)]e can be one °dONLNd>
;l
G
=(
Dl3default location for editions for all applications..°dONLNdr
Ml
Ys*
Yï°dONLNds
Mr
Y†)ou use the ï°dONLNd~
M†
Y
).SectionOptionsDialogï°dONLNdí
M

Y
Á)x/ function to display the publisher options and .
°dONLNd¡
Zl
f
+(
cl+subscriber options dialog boxes on the user=†°dONLNdÏ
Z
,
f
B)¿’s scr4 °dONLNdÚ
Z
B
f
S)een..°dONLNd˜
ll
xÄ(
ulThe °dONLNd˚
lÄ
x
)NewSubscriberExpDialog°dONLNd
l

x
    )Ñ, °dONLNd
l
    
x
á)NewPublisherExpDialog°dONLNd(
l
á
x
ü)~, and °dONLNd.
yl
Öˆ(
ÇlSectionOptionsExpDialog°dONLNdE
yˆ
Ö
,)ä functions arR`°dONLNdR
y
,
Ö
˜)6.e the same as the simple dialog functions but .
°dONLNdÄ
Ül
íâ(
èlhave fiN°dONLNdá
Üä
í˚)ve additional parameters.


¬*
À
¯4
√*
 
¯ 
ƒ*
ƒ
˛

ˇ·ˇ‚7^
°dONLNd¢
µ*
√œ(
ø*GetLastEditionContainerUsedˇˇˇˇˇˇ(
ø
Ú
2
.°dONLNdø
‘l
‡ë(
›lUse the °dONLNd«
‘ë
‡
3)%GetLastEditionContainerUsed°dONLNd‚
‘
3
‡
⁄)¢( function to get the default edition to .
°dONLNd

·l
Ìå(
Íldisplay°dONLNd
·å
Ì
ì) ?. This function allows a user to easily subscribe to the data r`°dONLNdP
·
ì
Ì
„(
Í
ìecently published.ˇÄ°dONLNdb
·
„
Ì
Â)P
 .°dONLNdd
˙l
J(l%FUNCTION GetLastEditionContainerUsed °dONLNdêÿ
∞+l$(VAR container: EditionContainerSpec°dONLNd¥
∞
º)ÿ):°dONLNd∂
º
Ê) OSErr;°dONLNdæ l,¢()l    container°dONLNd» Æ, )BIf the °dONLNdœ  ,
T)GetLastEditionContainer°dONLNdÊ 
T,
l)äUsed°dONLNdÍ 
l,
‹) function locates the last °dONLNd,Æ8
E(5Æ"edition for which a section was crR`°dONLNd',
E8
v)óeated, the R`°dONLNd2,
v8
¨)1    containerR`°dONLNd;,
¨8
‡)6 parameter .
°dONLNdF8ÆD

(AÆcontains its volume r≈‡°dONLNd[8

D
)\eferr°dONLNd_8
D
T)ence number˘‡°dONLNdj8
SD
d)8, dir√°dONLNdo8
eD
ô)ectory ID, fifl°dONLNd|8
ôD
Ë)4lename, and part, .°dONLNdéDÆP≈(MÆand rR`°dONLNdìD≈PÍ)    eturns a R`°dONLNdúDÍP
)%noErrR`°dONLNd°D
P
) r$¿°dONLNd£D
P
ñ) esult code. (The last edition cr˜ °dONLNd√D
ïP
Ì)áeated is associated .
°dONLNd◊PÆ\
Ò(YÆKwith the last time that your application or another application located on .°dONLNd"\Æh
**the same machine used the °dONLNd<\
*h
f)|
NewSection°dONLNdF\
fh
ï)< function.) 
.
°dONLNdSÇ*ãc(â*DESCRIPTION
.°dONLNd_èlõ
+B)If the last edition used is missing, the °dONLNdàè
õ
∫)¨GetLastEditionContainerUsed°dONLNd£è
∫õ
‚)¢
 function °dONLNd≠úl®p(•l
rR`°dONLNdÆúp®ö)
eturns an R`°dONLNd∏úö®æ)*fnfErrR`°dONLNdæú殃)$ r$¿°dONLNd¿úƒ®
)esult code, but still r˜ °dONLNd◊ú
®
^)Zeturns the corr…Ä°dONLNdÊú
^®
î)@ect volume rõ‡°dONLNdÚú
î®
¶)6efern@°dONLNdˆú
¶®
)ence number and °dONLNd©lµz(≤ldirR`°dONLNd    ©zµ
!)&ectory ID that you should use for the R`°dONLNd/©
!µ
ì)ßNewSubscriberDialogR`°dONLNdB©
ìµ
º)r
 function.ˇ6z@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-91
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿.°dONLNd\ähÚ(eäPass the information frR`°dONLNd\Úh
)hom the ,
CourierR`°dONLNd\
h
µ)!GetLastEditionContainerUsedR`°dONLNd9\
µh
˙)¢ function to the °dONLNdJiäu¸(räNewSubscriberDialog°dONLNd]i¸u
%)r
 function.
.
°dONLNdhèHòb(ñHRESULëÄ°dONLNdmèbòÜ)T CODES°dONLNdflÿH·o(flHSEE ALSO
.°dONLNdËÊäÚ
    +BFor an example of the use of °dONLNd
Ê
    Ú
´)GetLastEditionContainerUsed°dONLNd
 Ê
´Ú
¿)¢, see °dONLNd
&Ê
¿Ú
)Listing 2-6°dONLNd
1Ê
Ú
Ú)0
 .
°dONLNd
2ÛäˇΔ(¸äbeginning on {@°dONLNd
?Û«ˇfi)=page V °dONLNd
DÛflˇÒ)2-40™°dONLNd
HÛÒˇ
∞).. For a description of the edition container r@°dONLNd
vÛ
±ˇ
√)¿ecor놰dONLNd
zÛ
√ˇ
fi)d, see ˝†°dONLNd
ÅÛ
fiˇ
ı)page ÿÄ°dONLNd
ÜÛ
ˆˇ)2-71,`°dONLNd
äÛ    ˇ). .°dONLNd
å
ä
û(
    äThe °dONLNd
ê
û

)NewSubscriberDialog°dONLNd
£



Ö)r function is described next.


<H
E4
=H
D 
>H
>

ˇ·ˇ‚7^
.
°dONLNd
¡
/H
=¬(
9HNewSubscriberDialogˇˇˇˇˇˇ(
9
2
°dONLNd
÷
Nä
Z
,(
Wä#When a user chooses the Subscribe T °dONLNd
˘
N
,
Z)¢1o menu command, your application should call the .°dONLNd*
[ä
g¸(
däNewSubscriberDialog°dONLNd=
[¸
g)rB function to allow the user to choose an edition to subscribe to. °dONLNdÄ
tä
Ä
8(
}äFUNCTION NewSubscriberDialog °dONLNd•
Ç

é
º+~(VAR reply: NewSubscriberReply°dONLNd√
Ç
º
é
»)¥):°dONLNd≈
Ç
»
é
Ú) OSErr;°dONLNdÕ
öä
¶®(
£äreply.
°dONLNd”
öÃ
¶◊)BThr °dONLNd’
öÿ
¶Â)e nç °dONLNdÿ
öÂ
¶
()ew subscriber r
†°dONLNdÁ
ö
)
¶
B)Deply r퇰dONLNdÌ
ö
B
¶
T)ecor@°dONLNdÒ
ö
U
¶
])d.£°dONLNdÛ
ö
]
¶
_)
 ı`°dONLNdÙ
ö
_
¶
e)
Yµ‡°dONLNdı
ö
e
¶
˙)$ou specify a location to use as the .°dONLNd
¶Ã
≤
\(
ØÃ!default edition container in the °dONLNd:
¶
\
≤
í)ê    container°dONLNdC
¶
í
≤
õ)6 fi°dONLNdF
¶
õ
≤
–)    eld of this rR`°dONLNdS
¶
–
≤
‚)5ecor$¿°dONLNdW
¶
‚
≤
Ì)d. ˜ °dONLNdZ
¶
Ï
≤
Û)

Y °dONLNd[
¶
Û
≤)ou also °dONLNdc
≤Ã
æ
(
ªÃspecify in the °dONLNdr
≤

æ
N)@formatsMask°dONLNd}
≤
N
æ
W)B fi°dONLNdÄ
≤
W
æ
Á)    eld which edition format types °dONLNdü
æÃ
 
>(
«ÃNewSubscriberDialog°dONLNd≤
æ
>
 
Ö)r should displayd@°dONLNd¡
æ
Ñ
 
ù)F. The d@°dONLNd«
æ
ù
 )NewSubscriberDialogd@°dONLNd⁄
æ
 )r
 .
°dONLNd€
 Ã
÷˜(
”Ã
function r”@°dONLNdÂ
 ˜
÷
£)+&eturns information concerning the user;¿°dONLNd
 
•
÷
Ë)Æ’s choice in the .°dONLNd
÷Ã
‚¸(
flÃcanceled°dONLNd$
÷¸
‚
)0 and °dONLNd)
÷

‚
G)    container°dONLNd2
÷
G
‚
M)6 fPÄ°dONLNd4
÷
M
‚
ä)ields of this r"‡°dONLNdC
÷
ä
‚
ú)=ecorı@°dONLNdG
÷
õ
‚
§)d.°dONLNdJ
Ïä
¯
&(
ıäTYPE NewSubscriberReply = °dONLNdf
˙ú¿+RECORD°dONLNdoƉ+    canceled:°dONLNd}

8)ZBoolean;°dONLNdå
Ü
Ê)~{user canceled }°dONLNd´
Ü"
‘*{ dialog box}°dONLNdª$Æ0ˆ(-ÆformatsMask:°dONLNdÃ$
0
J)ZSignedByte;°dONLNdfi$
Ü0
Ú)~{formats required}°dONLNdÛ2Æ>Í(;Æ
container:°dONLNd2
>
Ü)ZEditionContainerSpec;°dONLNd2
Ü>
Ú)~{edition selected}°dONLNd2@úL¥(IúEND;

ZHi4ZHh
    .
°dONLNd7Yäd÷(aäField descriptions

ˇ·ˇ‚7^
.°dONLNdJfär¥*cancele°dONLNdQf¥r∫)*
d°dONLNdSfÊrÛ)2Th°dONLNdUfÛr˙)e °dONLNdWf˙r
l)NewSubscriberDialog°dONLNdjf
lr
ò)r function rR`°dONLNduf
òr
µ),eturns R`°dONLNd|f
µr
‹)    in this fiR`°dONLNdÜf
‹r)'eld a value .
°dONLNdírÊ~
({Ê=that indicates whether the user canceled the dialog box. The .°dONLNdœ~Êä
*
function rR`°dONLNdŸ~
ä
-)*eturns R`°dONLNd‡~
-ä
E)TRUER`°dONLNd‰~
Eä
V) in tR`°dONLNdÈ~
Vä
d)he R`°dONLNdÏ~
dä
î)canceledR`°dONLNdÙ~
îä
ù)0 fiR`°dONLNd˜~
ùä
¶)    elR`°dONLNd˘~
¶ä
º)    d if tR`°dONLNdˇ~
ºä)he user canceled °dONLNdäÊñ
f(ìÊthe dialog box. Otherwise, t°dONLNd,ä
fñ
û)Ähe function rR`°dONLNd9ä
ûñ
ª)8eturns R`°dONLNd@ä
ªñ
Ÿ)FALSER`°dONLNdEä
Ÿñ
ˇ)
 in this f"‡°dONLNdOä
ˇñ)&iel"‡°dONLNdRäñ)d °dONLNdTñÊ¢˝(üÊand rR`°dONLNdYñ˝¢
))eturns in tR`°dONLNddñ
)¢
7),he R`°dONLNdgñ
7¢
m)    containerR`°dONLNdpñ
m¢
v)6 fiR`°dONLNdsñ
v¢
)    elR`°dONLNduñ
¢
ã)    d tR`°dONLNdxñ
㢠   )he edition container for the .
°dONLNdï¢ÊÆ
)(´Ênew subscriberÃÄ°dONLNd£¢
(Æ
*)B
..°dONLNdtùä©®(¶änoErr.
y†°dONLNdzù
©
 )ë
0y†°dONLNd|ù
4©
P)No err?@°dONLNdÇù
Q©
Z)or.°dONLNdÜ®ä¥Æ(±äfnfErr.
y†°dONLNdç®
¥
 )á–43y†°dONLNdë®
4¥
Æ)#Edition container not found.°dONLNdÆ≥äø(ºäeditionMgrInitErr.
y†°dONLNd¿≥
ø
 )Ç–450y†°dONLNd≈≥
4ø
õ)(Manager not initializedˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-92    )BEdition Manager Reference4^*¿
¯,
Courier
.°dONLNd\lhÆ(elformatsMaskˇˇ«°dONLNd\»h€)\The ˇˇUTG°dONLNd\‹h
)formatsMaskˇˇ«G°dONLNd\
h
&)B fi8°dONLNd\
'h
¯)    /eld indicates which edition format type (text, .
°dONLNdMh»t
È(q»Bgraphics, and sound) to display within the subscriber dialog box. .°dONLNdèt»Äœ*
Yï°dONLNdêtŒÄ
)ou can set the ï°dONLNdüt
Ä
N)>formatsMaskï°dONLNd™t
NÄ
W)B fiï°dONLNd≠t
WÄ
·)     eld to the following constants: °dONLNdÕÄ»å
"(â»kTEXTformatMask°dONLNd‹Ä
"å
6)Z (1), °dONLNd‚Ä
6å
ê)kPICTformatMask°dONLNdÒÄ
êå
Ø)Z     (2), or °dONLNd˙å»ò
(ï»ksndFormatMask°dONLNd
å
ò
6)T (4). Tï°dONLNd
å
5ò
Ë)(o support a combination of formats, add °dONLNd
7ò»§
,(°»the constants together¬†°dONLNd
Mò
+§
u)c. For example, a ¬†°dONLNd
^ò
u§
∑)JformatsMask¬†°dONLNd
iò
∑§
ı)B of 3 displays .
°dONLNd
x§»∞
◊(≠»?both graphics and text edition format types in the subscriber  z‡°dONLNd
∑§
ÿ∞
⁄(≠
ÿ
 °dONLNd
∏∞»º˘(π»dialog box..°dONLNd
ƒølÀ¢(»l    container.
°dONLNd
Œø»À
Ú)\FThe edition container of the last edition published or subscribed to. °dONLNdÀ»◊Œ*
Y@Ä°dONLNdÀŒ◊Â)ou pr@°dONLNdÀÊ◊
ü)*ovide in this parameter the location and fi†°dONLNdEÀ
ü◊
Í)πlename to use as °dONLNdV◊»„
Ë(‡»Fthe default edition to subscribe to. If the user clicks the Subscribe .°dONLNdú„»ÔÈ*button, °dONLNd§„ÈÔ
[)!NewSubscriberDialog°dONLNd∑„
[Ô
a)r rR`°dONLNdπ„
aÔ
~)eturns R`°dONLNd¿„
~Ô
ú)FALSER`°dONLNd≈„
úÔ
≠) in tR`°dONLNd „
≠Ô
ª)he R`°dONLNdÕ„
ªÔ
Î)canceledR`°dONLNd’„
ÎÔ
Ì)0
 .
°dONLNd÷Ô»˚Œ(¯»
fiå¿°dONLNdÿÔŒ˚’)el>¿°dONLNd⁄Ô÷˚ı)d and r†°dONLNd·Ôˆ˚
) eturns t„ °dONLNdÈÔ
˚
$)!he ˛ °dONLNdÏÔ
$˚
I)    selected Œ¿°dONLNdıÔ
J˚
Ã)&edition container for the new .°dONLNd˚»
(
»    subscribe°dONLNd˚

)(    r in the °dONLNd%˚


I)#    container°dONLNd.˚
I

R)6 fi°dONLNd1˚
R

f)    eld. 
.
°dONLNd8
 *
)c(
'*DESCRIPTION
.°dONLNdD
.l
:Ä+BThe °dONLNdH
.Ä
:Ú)NewSubscriberDialog°dONLNd[
.Ú
:
Â)r8 function displays the subscriber dialog box on the user=`°dONLNdì
.
Ê
:
Ô)Ù’s °dONLNdñ
;l
Gx(
DlscrR`°dONLNdô
;x
G†)    een. The R`°dONLNd¢
;†
G
)(NewSubscriberDialogR`°dONLNdµ
;

G
¢)r! function (which is based on the R`°dONLNd÷
;
¢
G
)êCustomGetFileR`°dONLNd„
;

G
Ú)N
 .
°dONLNd‰
Hl
Tu(
QlprG °dONLNdÊ
Hv
Tî)
ocedurfi`°dONLNdÏ
Hî
T
/)#e described in the chapter “Standar`°dONLNd
H
0
T
Ç)úd File Package” in q °dONLNd"
H
Ç
T
fl)RInside Macintosh: Files8°dONLNd9
H
‡
T
Â)^) °dONLNd;
Ul
aÿ(
^lswitches to the volume rä °dONLNdS
Uÿ
aË)lefer6@°dONLNdW
UÈ
a
E)ence number and dir1¿°dONLNdj
U
E
a
π)\ectory ID and selects the fi¿Ä°dONLNdÜ
U
π
a
˜)tlename of the ˇˇhÙ.°dONLNdî
bl
nˇ(
kl!edition container that you specifi#–°dONLNd∂
b

n
()î
ed in the ˇ˛:‹^¨°dONLNd¿
b
(
n
^)(    containerˇˇhÙ^¨°dONLNd…
b
^
n
f)6 fi«†°dONLNdÃ
b
f
n
í)eld of the ˇ˛:‹|°dONLNd◊
b
ì
n
±)-replyˇˇhÙ|°dONLNd‹
b
±
n
‚)
 parameterÆ°dONLNdÊ
b
·
n
˜)0. Use °dONLNdÏ
ol
{~(
xlthe °dONLNd
o~
{
 )GetLastEditionContainerUsed°dONLNd
o
 
{
ı)¢3 function to get the edition container of the last ˇˇ›‹°dONLNd>
|l
à
à(
ÖlAedition that was either published or subscribed to, then set the ˇˇôît°dONLNd
|
â
à
ø(
Ö
â    containerˇˇ›‹t°dONLNdà
|
ø
à
«)6 fiÊP°dONLNdã
|
«
à
˜)eld to this .
°dONLNdó
âl
ï∑(
íledition containerÒÄ°dONLNd®
â∂
ï
∂)J<. This allows the user to publish and then easily subscribe..°dONLNdÂ
õl
ß
>(
§l0Note that if an edition does not contain either °dONLNd
õ
>
ß
b)“'PICT'°dONLNd
õ
b
ß
g)$, °dONLNd
õ
g
ß
ã)'TEXT'°dONLNd#
õ
ã
ß
õ)$, or °dONLNd(
õ
õ
ß
ø)'snd '°dONLNd.
õ
ø
ß
Ó)$ data, the °dONLNd9
®l
¥fi(
±lNewSubscriberDialog°dONLNdL
®fi
¥
w)r% function does not list the edition fPÄ°dONLNdq
®
w
¥
Â)ôile in the new subscriber .
°dONLNdã
µl
¡
H(
æl3dialog box (unless you install an opener that can rŇ°dONLNdæ
µ
H
¡
œ)‹ ecognize the edition’s data in r¡†°dONLNdfi
µ
œ
¡
Ù)áesponse .°dONLNdÊ
¬l
Ή(
Àlto the °dONLNdÌ
‰
Œ›)eoCanSubscribe°dONLNd˚
¬›
Œ˙)T verb).
.
°dONLNd
Ë*
ÒD(
Ô*RESULëÄ°dONLNd
ËD
Òh)T CODES°dONLNdõ1*:Q(8*SEE ALSO
°dONLNd§?lK
c+B:For an illustration of the new subscriber dialog box, see Ñ@°dONLNdfi?
cK
{)˜FigurW°dONLNd„?
{K
º)e 2-12 on page @°dONLNdÚ?
ΩK
≈)B2-j °dONLNdÙ?
≈K
œ)37j °dONLNdˆ?
œK
Ú)
    . For an .°dONLNdˇLlXÕ(Ulexample of the use of °dONLNdLÕX
?)aNewSubscriberDialog°dONLNd(L
?X
T)r, see °dONLNd.L
TX
Ñ)Listing 2-6°dONLNd9L
ÑX
ø)0 beginning on °dONLNdGL
øX
◊);page °dONLNdLL
◊X
Í)2-40°dONLNdPL
ÍX
Ô). .
°dONLNdRYle
&(bl,For a description of the edition container rÛ@°dONLNd~Y
&e
8)∫ecorg†°dONLNdÇY
9e
T)d, see ”†°dONLNdâY
Te
k)page ÆÄ°dONLNdéY
le
~)2-71`°dONLNdíY
e
⁄). For information on °dONLNdßflrΔ(oledition openers, see õÄ°dONLNdºfΔr
∑)Z5“Subscribing to Non-Edition Files” beginning on page 2`°dONLNdÒf
∏r
 )Ú2-62Ü@°dONLNdıf
 r
œ). .°dONLNd
ˆlä(
ˇlnoErr.
°dONLNd
ˆı˙)â
0°dONLNd
ˆ

*)No errE†°dONLNd
ˆ
+
4)or.°dONLNd!
l“(
leditionMgrInitErr.
°dONLNd3
Ê˙)z–450°dONLNd8


=)(    Manager nc`°dONLNdA

>
u)0ot initialized@°dONLNdO

v
Î)8 or could not load package.°dONLNdkl∫(lbadSubPartErr.
°dONLNdyÊ˙)z–454°dONLNd~

Ç)(Bad edition container specˇ9ÿ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-93
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

jHr4jHr lHl

ˇ·ˇ‚7^°dONLNd\HjQ(fH
N~@°dONLNd
\Rjº)
ewPublisherDialogˇˇˇˇˇˇ(f
2
°dONLNd{äá
π(ÑäCWhen a user selects a portion of a document and then chooses the Cr9¿°dONLNdW{
∫á
˚(Ñ
∫eate Publisher .°dONLNdfàäî
g(ëä/menu command, your application should call the ,
Courier°dONLNdïà
gî
”)›NewPublisherDialog°dONLNdßà
Ӕ)l function to .
°dONLNd¥ïä°(ûäVallow the user to choose a name and location of the edition to which your application °dONLNd

¢äÆ˝*writes the publisher data. µ °dONLNd
%¢˝Æ
)s
Yu†°dONLNd
&¢
Æ
e)our application specifi    ‡°dONLNd
=¢
fÆ)c%es a location and name to use as the °dONLNd
bØäªÎ(∏ädefault edition and pr^¿°dONLNd
xØΪ
)aovides a prL`°dONLNd
ÉØ
ª
≤)1#eview of the publisher data to the .°dONLNd
¶ºä»ˆ(≈äNewPublisherDialog°dONLNd
∏ºˆ»
!)l function. °dONLNd
ƒ’ä·
2(fiäFUNCTION NewPublisherDialog °dONLNd
Á„ˆÔ
§+l(VAR reply: NewPublisherReply°dONLNd„
§Ô
∞)Æ):°dONLNd„
∞Ô
⁄) OSErr;°dONLNd˚ä
¢(
ärepl°dONLNd˚¢
®)
y.
°dONLNd˚Ã
”)*
A∫†°dONLNd˚”
€) n°dONLNd˚‹

)    ew publisher r‡°dONLNd%˚


5)@eply r¶ °dONLNd+˚
5

G)ecorÄ°dONLNd/˚
H

N)
d6@°dONLNd0˚
N

S). †°dONLNd2˚
S

Y)
Y… °dONLNd3˚
X
),ou specify a location to use as the default .°dONLNd_
Ã

8(
Ãedition container in the °dONLNdx

8

n)l    container°dONLNdÅ

n

w)6 fi°dONLNdÑ

w

¨)    eld of this rR`°dONLNdë

¨

æ)5ecor$¿°dONLNdï

æ

…)d. ˜ °dONLNdò

»

œ)

Y °dONLNdô

œ
)ou also specify °dONLNd©
Ã

!(
Ãinformation in the °dONLNdº

!

K)UusePart°dONLNd√

K

P)*, °dONLNd≈

P

z)previewï°dONLNdÃ

y

ë)), and ï°dONLNd“

ë

fl)previewFormatï°dONLNdfl

fl

Ë)N fiï°dONLNd‚

Ë
)
elds. The °dONLNdÏ
Ã
+
8(
(ÃNewPublisherDialog°dONLNd˛

8
+
d)l function rR`°dONLNd    

d
+
˚),"eturns information concerning the °dONLNd+
+Ã
7fi(
4Ãuser=`°dONLNd/
+fl
7
$)’s choice in the =`°dONLNd@
+
$
7
T)Ecanceled=`°dONLNdH
+
T
7
Y)0, =`°dONLNdJ
+
Y
7
è)    replacing=`°dONLNdS
+
è
7
ß)6, and =`°dONLNdY
+
ß
7
›)    container=`°dONLNdb
+
›
7
Ê)6 fi=`°dONLNde
+
Ê
7)    elds of .
°dONLNdm
7Ã
C‚(
@Ãthis r˛ °dONLNds
7‚
CÙ)ecorrÄ°dONLNdw
7ı
C˝)d..°dONLNdz
Mä
Y
 (
VäTYPE NewPublisherReply = °dONLNdï
[ú
g¿+RECORD°dONLNdû
iÆ
u‰+    canceled:°dONLNd¨
i

u
8)ZBoolean;°dONLNdπ
i
b
u
˛)Z{user canceled dialog box}°dONLNd◊
wÆ
ÉÍ(
ÄÆ
replacing:°dONLNdÊ
w

É
8)ZBoolean;°dONLNdÛ
w
b
É
Ï)Z{user chose existing } °dONLNd
Ö
b
ë
˛*{ filename for an edition}°dONLNd4
ìÆ
üfi(
úÆusePart:°dONLNdA
ì

ü
8)ZBoolean;°dONLNdN
ì
b
ü)Z{always false in version 7.0}°dONLNdn
°Æ
≠fi(
™Æpreview:°dONLNd{
°

≠
2)ZHandle;°dONLNdá
°
b
≠
)Z{handle to 'prvw', 'PICT', }°dONLNd∞
Ø
b
ª
˛*{ 'TEXT', or 'snd ' data} °dONLNdÕ
ΩÆ
…
(
ΔÆpreviewFormat:°dONLNd‡
Ω

…
J)ZFormatType;°dONLNd
Ω
b
…
»)Z{type of preview}°dONLNd
ÀÆ
◊Í(
‘Æ
container:°dONLNd
À

◊
Ü)ZEditionContainerSpec;°dONLNd5
Ÿ
b
Â
¬+Z{edition chosen}°dONLNdG
Áú
Û¥(
úEND;


H4
H
    .
°dONLNdLä÷(äField descriptions

ˇ·ˇ‚7^
.°dONLNd_ä¥*cancele°dONLNdf¥∫)*
d°dONLNdhÊ˙)2The °dONLNdl˙
f)NewPublisherDialog°dONLNd~
f
í)l function rR`°dONLNdâ
í
÷),eturns in this fiR`°dONLNdö
÷)Deld a value .
°dONLNd¶Ê%
("Ê=that indicates whether the user canceled the dialog box. The .°dONLNd„%Ê1
*
function rR`°dONLNdÌ%
1
-)*eturns R`°dONLNdÙ%
-1
E)TRUER`°dONLNd¯%
E1
d) in the R`°dONLNd%
d1
î)canceledR`°dONLNd%
î1
ù)0 fiR`°dONLNd%
ù1)    eld if the user canceled °dONLNd$1Ê=
j(:Êthe dialog box. The function rR`°dONLNdB1
j=
á)Ñeturns R`°dONLNdI1
á=
•)FALSER`°dONLNdN1
•=
Œ)
 in this fiR`°dONLNdY1
Œ=))eld if the user °dONLNdi=ÊI
u(FÊ clicked the Publish button and rR`°dONLNdâ=
uI
Ø)èeturns in the R`°dONLNdó=
ØI
Â):    containerR`°dONLNd†=
ÂI
Ó)6 fiR`°dONLNd£=
ÓI)    eld the .
°dONLNd´IÊU
í(RÊ'edition container for the new publisher© °dONLNd“I
íU
î)¨
..°dONLNd’Xäd∫(aäreplacin°dONLNd›X∫d¿)0
g°dONLNdflXÊd˙),The °dONLNd„X˙d
f)NewPublisherDialog°dONLNdıX
fd
í)l function rR`°dONLNdX
íd
Ø),eturns R`°dONLNdX
Ød
«)TRUER`°dONLNdX
«d
Ê) in the ˇ˛„$°dONLNddÊp
(mÊ    replacingˇˇ°°dONLNdd
p
!)6 fÒå°dONLNdd
!p
µ)$ield if the user chose an existing f)`°dONLNdBd
∂p
‰)ï
ilename frúðdONLNdLd
‰p).om the list .
°dONLNdXpÊ|
j(yÊof available editions and confi'`°dONLNdwp
k|
õ)Örmed this r—Ä°dONLNdÇp
õ|)0eplacement. If the value of .°dONLNdû|Êà¯(ÖÊthe °dONLNd¢|¯à
.)    replacing°dONLNd´|
.à
7)6 fi°dONLNdÆ|
7à
R)    eld is °dONLNdµ|
Rà
j)TRUE°dONLNdπ|
jà
≤), do not call the °dONLNdÀàÊî
Ç(ëÊCreateEditionContainerFile°dONLNdÂà
Çî)ú  function. If the value of this °dONLNdîʆÌ(ùÊ
fi°dONLNdî̆
#)eld and the °dONLNdî
#†
S)6canceled°dONLNdî
S†
\)0 fi°dONLNdî
\†
w)    eld is °dONLNd%î
w†
ï)FALSE°dONLNd*î
ï†
—), you can call °dONLNd9†Ê¨
Ç(©ÊCreateEditionContainerFile°dONLNdS†
Ǩ
ó)ú to crR`°dONLNdY†
ó¨
Ï)eate a new edition .
°dONLNdl¨Ê∏
(µÊ    container2 °dONLNdu¨
∏
))
.ˇÇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-94    )BEdition Manager Reference4^*¿
¯,
Courier
.°dONLNd\lhê(elusePar°dONLNd\êhñ)$
t°dONLNd\»h–)8
AÛ`°dONLNd    \œh
A) value that must be set to Û`°dONLNd$\
Ah
G)r
FÛ`°dONLNd%\
Gh
_)ALSEÛ`°dONLNd)\
_h
x) befor≈¿°dONLNd/\
xh
≥)e calling the °dONLNd=h»t
4(q»NewPublisherDialog°dONLNdOh
4t
])l
 function.°dONLNdZwlÉê(Älprevie°dONLNd`wêÉñ)$
w°dONLNdbw»É–)8
AÛ`°dONLNdcwœÉÿ) hÛ`°dONLNdewÿɡ)        andle to Û`°dONLNdnwˇÉ
#)''prvw'Û`°dONLNdtw
#É
()$, Û`°dONLNdvw
(É
L)'PICT'Û`°dONLNd|w
LÉ
Q)$, Û`°dONLNd~w
QÉ
u)'TEXT'Û`°dONLNdÑw
uÉ
Ö)$, or Û`°dONLNdâw
ÖÉ
©)'snd 'Û`°dONLNdèw
©É
Δ)$ data. Û`°dONLNdñw
ΔÉ
⁄)The °dONLNdöÉ»è
4(å»NewPublisherDialog°dONLNd¨É
4è
⁄)l& function displays this data in the prR`°dONLNd“É
ڏ
¯)¶eview .
°dONLNdÿè»õ–(ò»arE°dONLNd⁄è—õ
*)    ea of the dialog box..°dONLNdûl™¥(ßlpreviewForma°dONLNd¸û¥™∫)H
t.
°dONLNd˛û»™œ)
A∫†°dONLNdˇûœ™
) value that iÿÄ°dONLNd
û
™
#)4ndicate*@°dONLNd
û
$™
()!
sg@°dONLNd
û
(™
∞) which type of data the handle L@°dONLNd
3û
±™
Ã)âin the .°dONLNd
:™»∂Ú(≥»preview°dONLNd
A™Ú∂¯)* fPÄ°dONLNd
C™¯∂
)ield PÄ°dONLNd
H™
∂
)
r"‡°dONLNd
I™
∂
#)eferı@°dONLNd
M™
"∂
<)ences.°dONLNd
Tπl≈ú(¬lcontaine°dONLNd
\πú≈¢)0
r.
°dONLNd
^π»≈
)),An edition container rÄ°dONLNd
tπ
*≈
<)becorć°dONLNd
xπ
<≈
t)d that specifi`‡°dONLNd
Üπ
u≈
É)9es t)‡°dONLNd
äπ
Ñ≈
π)he volume r2¿°dONLNd
ïπ
π≈
…)5eferfi‡°dONLNd
ôπ
…≈
fl)ence °dONLNd
û≈»—Í(Œ»number≥°dONLNd
§≈Í—˚)", dir| °dONLNd
©≈¸—
C)ectory ID, and fi@°dONLNd
∫≈
D—
_)Hlenam\†°dONLNd
ø≈
_—
í)e to use as tk@°dONLNd
Ã≈
í—
ü)3he Ü@°dONLNd
œ≈
ü—
¿)default q`°dONLNd
◊≈
¡—
‚)"edition 0¿°dONLNd
fl≈
„—
Ó)"to ˇˇË†.°dONLNd
‚—»›
8(⁄»publish the data to. The ˇˇπ‡ °dONLNd
˚—
9›
•)qNewPublisherDialogˇˇË† °dONLNd—
•›
–)l function rÆ¿°dONLNd—
–›
˜)+
eturns in .
°dONLNd"›»È‡(Ê»this fiE‡°dONLNd)›·È
R)eld the edition container t‚@°dONLNdD›
RÈ
∞)qhat the user selected. 
°dONLNd\
*
c(
    *DESCRIPTION
.°dONLNdh
l
Ä+BThe °dONLNdl
Ä
Ï)NewPublisherDialog°dONLNd~
Ï

œ)l3 function displays the new publisher dialog box on °dONLNd±
l
)~(
&lthe °dONLNdµ
~
)ê)user=`°dONLNdπ
ë
)¶)’s scr¿°dONLNdø
¶
)¿)een. T¿°dONLNd≈
¿
)Œ)he ¿°dONLNd»
Œ
)
:)NewPublisherDialog¿°dONLNd⁄

:
)
 )l! function (which is based on the °dONLNd˚
*l
6∫(
3lCustomPutFile°dONLNd
*∫
6Δ)N prR`°dONLNd
*Δ
6„)ocedur$¿°dONLNd
*„
6
4)e described in the $¿°dONLNd$
*
4
6
_)Q    chapter “$¿°dONLNd-
*
_
6
Ñ)+Standar˜ °dONLNd4
*
É
6
¡)$d File Packag˜ °dONLNdA
*
¡
6
ÿ)>e” in .
°dONLNdG
7l
CÜ(
@lInside qÄ°dONLNdN
7á
C…)Macintosh: FilesF‡°dONLNd^
7 
CÕ)C
)ö¿°dONLNd_
7Õ
C
;) switches to the volume r$‡°dONLNdx
7
<
C
L)oefer—°dONLNd|
7
L
C
®)ence number and dirÃÄ°dONLNdè
7
®
C
…)\ectory IÄ°dONLNdó
7
 
C
‘)"D °dONLNdô
Dl
Pà(
MlspecifiÓ °dONLNd†
Dà
P˛)ed by the edition containerπ °dONLNdª
D˛
P
)v, sˆ °dONLNdæ
D

P
)    ets th“‡°dONLNdƒ
D

P
+)e eÊ °dONLNd«
D
+
P
4)diÍ@°dONLNd…
D
4
P
x)    table text item th°dONLNd⁄
D
y
P
ó)Eo the fi«†°dONLNd‚
D
ó
P
≤)lenam°dONLNdÁ
D
≥
P
÷)e specifi÷¿°dONLNd
D
÷
P
)#ed by °dONLNdˆ
Ql
]o(
Zl
t¬`°dONLNd˜
Qo
]√)he edition containe†°dONLNd

Qƒ
]«)U
rN‡°dONLNd
Q«
]
), and displays a prz‡°dONLNd
Q

]
)Q1eview of the publisher data in the new publisher .°dONLNdO
^l
j¥(
gldialog box. The °dONLNd_
^¥
j
 )HNewPublisherDialog°dONLNdq
^
 
j
Ò)l1 function handles all user interaction until the .
°dONLNd¢
kl
w
(
tl)user clicks the Cancel or Publish button..°dONLNdÃ
}l
âs*
Yï°dONLNdÕ
}r
â
)!ou should deallocate the handle rg`°dONLNdÓ
}

â
)ôefer9¿°dONLNdÚ
}

â
W)enced by the 9¿°dONLNdˇ
}
W
â
Å):preview9¿°dONLNd
}
Å
â
ä)* fi9¿°dONLNd    
}
ä
â
Æ)        eld to fr °dONLNd
}
Æ
â
Î)$ee up memory`°dONLNd
}
È
â
Ï);
.
.
°dONLNd 
£*
¨D(
™*RESULëÄ°dONLNd%
£D
¨h)T CODES°dONLNd∏
Ï*
ıQ(
Û*SEE ALSO
°dONLNd¡
˙l
_+B9For an illustration of the new publisher dialog box, see †°dONLNd˙
˙
`
x)ÙFigurÎ`°dONLNdˇ
˙
w
ã)e 2-1¸@°dONLNd
˙
ã
∏)
1 on page °dONLNd
˙
π
¡).2-q‡°dONLNd
˙
¡
À)29q‡°dONLNd
˙
À
Ó)
    . For an .°dONLNdlÕ(lexample of the use of °dONLNd1Õ
9)aNewPublisherDialog°dONLNdC
9
N)l, see °dONLNdI
N
~)Listing 2-4°dONLNdT
~
π)0 beginning on °dONLNdb
π
—);page °dONLNdg
—
‰)2-33°dONLNdk
‰
È). .
°dONLNdml 
&(l,For a description of the edition container rÛ@°dONLNdô
& 
8)∫ecorg†°dONLNdù
9 
T)d, see ”†°dONLNd§
T 
k)page ÆÄ°dONLNd©
l 
~)2-71`°dONLNd≠
 
Ñ). 

P*Y
¯4Q*X
¯ R*R
˛

ˇ·ˇ‚7^
°dONLNd±C*Q1(M*
S‘Ä°dONLNd≤C1Q§)ectionOptionsDialogˇˇˇˇˇˇ(M
Ú
2
.°dONLNd«blnë(klUse the °dONLNdœbën
    )%SectionOptionsDialog°dONLNd„b
    n
ÿ)x/ function to display the publisher options and .
°dONLNdol{
+(xl+subscriber options dialog boxes on the user=†°dONLNd=o
,{
B)¿’s scr4 °dONLNdCo
B{
S)een..°dONLNdHàlî
&(ëlFUNCTION SectionOptionsDialog  °dONLNdoñÍ¢
§+~(VAR reply: SectionOptionsReply°dONLNdéñ
§¢
∞)∫):°dONLNdêñ
∞¢
⁄) OSErr;°dONLNd,
±l
Ωä(
∫lnoErr.
°dONLNd2
±ı
Ω˙)â
0°dONLNd4
±

Ω
*)No errE†°dONLNd:
±
+
Ω
4)or.°dONLNd>
ºl
»“(
≈leditionMgrInitErr.
°dONLNdP
ºÊ
»˙)z–450°dONLNdU
º

»
=)(    Manager nc`°dONLNd^
º
>
»
u)0ot initialized@°dONLNdl
º
v
»
Î)8 or could not load package.°dONLNdà
«l
”∫(
–lbadSubPartErr.
°dONLNdñ
«Ê
”˙)z–454°dONLNdõ
«

”
Ç)(Bad edition container specˇ;ä@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-95
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\äh®(eäreply°dONLNd\Ãh‡)BThe °dONLNd
\‡h˛)reply°dONLNd\˛h
©)' parameter contains a section options rR`°dONLNd6\
©h
ƒ)´eply r$¿°dONLNd<\
ƒh
÷)ecor˜ °dONLNd@\
’h
fi)d.˜ °dONLNdB\
fih
‡)    
 …Ä°dONLNdC\
‡h
Á)
YfiÄ°dONLNdD\
Êh)ou specify .
°dONLNdOhÃt
:(qÃa handle to the publishero`°dONLNdhh
;t
~)o’s or subscriber1°dONLNdxh
t
≠)D’s section r‚¿°dONLNdÑh
≠t
ø).ecorW °dONLNdàh
¿t
‰)    d in the .°dONLNdëtÃĸ(}ÃsectionH°dONLNdôt¸Ä
)0 fPÄ°dONLNdõt
Ä
;)ield of this r"‡°dONLNd©t
;Ä
M)9ecorı@°dONLNd≠t
LÄ
k)d. The ı@°dONLNd¥t
kÄ
„)SectionOptionsDialogı@°dONLNd»t
„Ä)x
 function °dONLNd“ÄÃå–(âÃ
rR`°dONLNd”Ä–å
y)&eturns information concerning the user¿°dONLNd˘Ä
zå
¬)™’s actions in the ¿°dONLNd
Ä
Œ
Ú)Hcanceled¿°dONLNd
Ä
Úå
˜)0, °dONLNd
åÃòˆ(ïÃchanged°dONLNd
åˆò
)*, and °dONLNd
"å
ò
2)action°dONLNd
(å
2ò
8)$ fPÄ°dONLNd
*å
8ò
R)ields.°dONLNd
1¢äÆ
,(´äTYPE SectionOptionsReply = °dONLNd
N∞úº¿+RECORD°dONLNd
WæÆ ‰+    canceled:°dONLNd
dæˆ 
&)HBoolean;°dONLNd
ræ
b 
˛)l{user canceled dialog box}°dONLNd
èÃÆÿfi(’Æchanged:°dONLNd
õÈÿ
&)HBoolean;°dONLNd
©Ã
bÿ
)l{changed the section record}°dONLNd
»⁄Æʉ(„Æ    sectionH:°dONLNd
’⁄ˆÊ
J)HSectionHandle;°dONLNd
È⁄
bÊ
˛)l{handle to the specified }°dONLNdË
bÙ
»*{ section record}°dONLNd$ˆÆ
ÿ(ˇÆaction:°dONLNd/ˆˆ

&)HResType;°dONLNd=ˆ
b

∂)l{action codes}°dONLNdM
ú
¥(
úEND;


H
,4
H
,
    .
°dONLNdR
ä
(÷(
%äField descriptions

ˇ·ˇ‚7^
.°dONLNde
*ä
6∫*canceledˇˇË†°dONLNdn
*Ê
6˘)\The ˇˇπ‡h†°dONLNdr
*˙
6
r)SectionOptionsDialogˇˇË†h†°dONLNdÜ
*
r
6
ù)x function r@°dONLNdë
*
û
6
·),eturns in this fiΔ °dONLNd¢
*
·
6)Celd a value .
°dONLNdÆ
6Ê
B
(
?Ê=that indicates whether the user canceled the dialog box. The .°dONLNdÎ
BÊ
N
*
function rR`°dONLNdı
B

N
-)*eturns R`°dONLNd¸
B
-
N
E)TRUER`°dONLNd
B
E
N
d) in the R`°dONLNd
B
d
N
î)canceledR`°dONLNd
B
î
N
ù)0 fiR`°dONLNd
B
ù
N)    eld if the user canceled °dONLNd,
NÊ
Z
û(
WÊ)the dialog box. Otherwise, the function rR`°dONLNdU
N
û
Z
ª)∏eturns R`°dONLNd\
N
ª
Z
Ÿ)FALSER`°dONLNda
N
Ÿ
Z)
 in this fiR`°dONLNdl
N
Z))eld. °dONLNds
]ä
i¥(
fächangedˇˇË†°dONLNd{
]Ê
i˘)\The ˇˇπ‡h†°dONLNd
]˙
i
r)SectionOptionsDialogˇˇË†h†°dONLNdì
]
r
i
ù)x function r@°dONLNdû
]
û
i
∫),eturns ˇˇπ‡Ù‡°dONLNd•
]
∫
i
“)TRUEˇˇË†Ù‡°dONLNd©
]
“
i
˙)
 in this fiÆ¿°dONLNd¥
]
˚
i))eld if .
°dONLNdª
iÊ
uÈ(
rÊ
t¬`°dONLNdº
iÈ
u
i)he user changed the section r °dONLNdŸ
i
i
u
{)ÄecordÄ°dONLNd›
i
|
u) d. For example, the update mode .°dONLNd˝
uÊ
Å
?(
~Êmay have changed.°dONLNd
u
?
Å
≥)Y Otherwise, the function rR`°dONLNd(
u
≥
Å
–)teturns R`°dONLNd/
u
–
Å
Ó)FALSER`°dONLNd4
u
Ó
Å)     in this .
°dONLNd=
ÅÊ
çÏ(
äÊ
fiå¿°dONLNd?
ÅÏ
ç˛)eld. .°dONLNdE
êä
ú¥(
ôäsection°dONLNdL
ê¥
ú∫)*
H.
°dONLNdN
êÊ
úÌ)2
A∫†°dONLNdO
êÌ
úı) h°dONLNdQ
êˆ
ú
R)    andle to the section ṙ°dONLNdg
ê
Q
ú
c)[ecorb@°dONLNdk
ê
d
ú
˘)$d for the section the user selected..°dONLNdê
üä
´Æ(
®äaction°dONLNdó
üÊ
´˙)\The °dONLNdõ
ü˙
´
r)SectionOptionsDialog°dONLNdØ
ü
r
´
û)x function rR`°dONLNd∫
ü
û
´
‚),eturns in this fiR`°dONLNdÀ
ü
‚
´)Deld the °dONLNd”
´Ê
∑
.(
¥Êcode for one of fi°dONLNdÂ
´
.
∑
®)Hve user actions: action code °dONLNd
´
®
∑
Ã)z'read'°dONLNd
´
Ã
∑
Ò)$
 for user °dONLNd
∑Ê
√
–(
¿Ê5selection of the Get Edition Now button, action code °dONLNdG
∑
–
√
Ù)Í'writ'°dONLNdM
∑
Ù
√)$ for °dONLNdR
√Ê
œ
Í(
ÃÊ;user selection of the Send Edition Now button, action code °dONLNdç
√
Í
œ(
Ã
Í'goto'°dONLNdì
√
œ)$
 °dONLNdî
œÊ
€
Î(
ÿÊ<for user selection of the Open Publisher button, action code°dONLNd–
œ
Î
€
Ò(
ÿ
Î
 °dONLNd—
€Ê
Á

(
‰Ê'cncl'°dONLNd◊
€


Á
Ò)$6 for user selection of the Cancel Publisher or Cancel °dONLNd
ÁÊ
Û
v(
Ê"Subscriber button, or action code °dONLNd/
Á
v
Û
Ç)ê' °dONLNd1
Á
Ç
Û
à)
 °dONLNd2
Á
à
Û
é)
 °dONLNd3
Á
é
Û
î)
 °dONLNd4
Á
î
Û
†)' °dONLNd6
Á
†
Û
˚)($20202020) for user .
°dONLNdK
ÛÊ
ˇ
\(
¸Êselection of the OK button.
°dONLNdgH!Å(HDESCRIPTION
ˇˇÍˆ.°dONLNds&ä2ù+BThe ˇˇ¿‚jˆ°dONLNdw&û2
)SectionOptionsDialogˇˇÍˆjˆ°dONLNdã&
2
è)x function displays the apprÈ.°dONLNd¶&
è2)yopriate options dialog box for .
°dONLNd≈3ä?∂(<ä
the specifiKÄ°dONLNd–3∑?È)-ed section rfi`°dONLNd‹3È?˚)2ecorR¿°dONLNd‡3¸?)=d. The function displays information about the subscriber or °dONLNd@äL¥(Iä    publisherÓ‡°dONLNd&@≥L
I))%, such as its latest edition and curr蠡dONLNdK@
IL)ñ-ent update mode setting, and allows the user .°dONLNdxMäY
(Vä to perform various actions. The °dONLNdòM
Y
ê)éSectionOptionsDialog°dONLNd¨M
êY)x function handles all user .
°dONLNd«Zäf
Å(cä;interaction until the user selects a button. The function ru@°dONLNdZ
Åf
¬)˜eturns the user$Ä°dONLNdZ
ƒf)C’s action in the .°dONLNd"gäsÆ(päaction°dONLNd(gÆs¥)$ fPÄ°dONLNd*g¥sÊ)ield of the PÄ°dONLNd6gÊs
)2replyPÄ°dONLNd;g
s
˘)5 parameter; your application should then perform the .
°dONLNdptäÄõ(}äcorr`°dONLNdttúÄÌ)esponding action. 
°dONLNdáöH£b(°HRESULëÄ°dONLNdåöb£Ü)T CODES
.°dONLNdì®ä¥®+(noErr.
|@°dONLNdô®¥ı)f
0|@°dONLNdõ®
    ¥
%)No errA‡°dONLNd°®
&¥
/)or.°dONLNd•≥äøΔ(ºä
memFullErr.
|@°dONLNd∞≥·øı)W–108|@°dONLNdµ≥
    ø
@)(Memory fullˇ&@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-96    )BEdition Manager Reference4^*¿
¯
°dONLNd\*eQ(c*SEE ALSO
°dONLNd    jlv
Y+B9For illustrations of the section options dialog box, see Ù¿°dONLNdBj
Yv
q)ÌFigur«Ä°dONLNdGj
qv
ä)e 2-13e°dONLNdMj
ãv
ö) thrΩ¿°dONLNdQj
öv
≥)ough ‡°dONLNdVj
¥v
Ã)Figur̆°dONLNd[j
Àv
‰)e 2-16ã °dONLNdaj
Âv
Á)
 .°dONLNdbwlÉ•(Älbeginning on °dONLNdow•ÉΩ)9page °dONLNdtwΩÉ–)2-43°dONLNdxw–É
T). For an example of the use of ,
Courier°dONLNdów
TÉ
Ã)ÑSectionOptionsDialog°dONLNd´w
ÃÉ
·)x, see .
°dONLNd±Ñlêö(çlListing 2-8 @°dONLNdºÑõê⁄)/ beginning on õÄ°dONLNd Ñ⁄êÒ)?page v`°dONLNdœÑÚê
)2-46 @°dONLNd”Ñ
ê
ó)$. For a description of the section r˜ °dONLNd˜Ñ
óê
©)ìecorkÄ°dONLNd˚Ñ
™ê
≈)d, see ◊Ä°dONLNd
Ñ
Ő
‹)page ≤`°dONLNd
Ñ
ݐ
Ô)2-72@°dONLNd
Ñ
ê
ı). 

¿*…
¯4¡*»
¯ ¬*¬
˛

ˇ·ˇ‚7^
°dONLNd
≥*¡3(Ω*
N~@°dONLNd
≥4¡
›)
EewSubscriberExpDialog, NewPublisherExpDialog, SectionOptionsExpDialogˇˇˇˇˇˇ(Ω
Ú
2
.°dONLNd
W“lfiÄ(€lThe °dONLNd
[“Äfi
)NewSubscriberExpDialog°dONLNd
q“
fi
    )Ñ, °dONLNd
s“
    fi
á)NewPublisherExpDialog°dONLNd
à“
áfi
ü)~, and °dONLNd
éfllΈ(ËlSectionOptionsExpDialog°dONLNd
•flˆÎ
,)ä functions arR`°dONLNd
≤fl
,Î
˜)6.e the same as the simple dialog functions but .
°dONLNd
‡Ïl¯â(ılhave fiN°dONLNd
ÁÏä¯
Ò)Pve additional parameters. These additional parameters allow you to add items to °dONLNd7˘l

„(
lVthe bottom of the dialog boxes, apply alternate mapping of events to item hits, apply °dONLNdç
l

…*Qalternate meanings to the item hits, and choose the location of the dialog boxes..°dONLNdfl
l
+
,* FUNCTION NewSubscriberExpDialog °dONLNd
-Δ
9
‘+Z-(VAR reply: NewSubscriberReply; where: Point;°dONLNd8
;Δ
GÃ*
 °dONLNd9
;Ã
G
z)expansionDITLresID: Integer; °dONLNd\
IΔ
UÃ(
RΔ
 °dONLNd]
IÃ
U
t)dlgHook: ExpDlgHookProcPtr; °dONLNd
WΔ
cÃ(
`Δ
 °dONLNdÄ
WÃ
c
û)#filterProc: ExpModalFilterProcPtr; °dONLNd©
eΔ
qÃ(
nΔ
 °dONLNd™
eÃ
q
Ä)yourDataPtr: UNIV Ptr): OSErr;°dONLNd…
l
ã
 (
àlFUNCTION NewPublisherExpDialog°dONLNdÁ

 
ã
&)¥
 °dONLNdÓ
çΔ
ôÃ(
ñΔ
(°dONLNdÔ
çÃ
ô
§)$VAR reply: NewPublisherReply; where:°dONLNd
ç
§
ô
Œ)ÿ Point;°dONLNd 
õΔ
ßÃ(
§Δ
 °dONLNd!
õÃ
ß“)
e°dONLNd"
õ“
ß
t)xpansionDITLresID: Integer;°dONLNd=
õ
t
ß
z)¢
 °dONLNdD
©Δ
µÃ(
≤Δ
 °dONLNdE
©Ã
µ“)
d°dONLNdF
©“
µ
n)lgHook: ExpDlgHookProcPtr;°dONLNd`
©
n
µ
t)ú
 °dONLNdg
∑Δ
√Ã(
¿Δ
 °dONLNdh
∑Ã
√“)
f°dONLNdi
∑“
√
)    ilterProc°dONLNdr
∑

√
)6: E°dONLNdu
∑

√
ò)xpModalFilterProcPtr;°dONLNdä
∑
ò
√
û)~
 °dONLNdë
≈Δ
—Ã(
ŒΔ
 °dONLNdí
≈Ã
—“)
y°dONLNdì
≈“
—
J)ourDataPtr: UNIV Ptr°dONLNdß
≈
J
—
V)x):°dONLNd©
≈
V
—
Ä) OSErr;°dONLNd±
fll
Î
,(
Ël FUNCTION SectionOptionsExpDialog°dONLNd—
fl
,
Î
2)¿
 °dONLNdÿ
ÌΔ
˘Ã(
ˆΔ
(°dONLNdŸ
ÌÃ
˘
∞)&VAR reply: SectionOptionsReply; where:°dONLNdˇ
Ì
∞
˘
⁄)‰ Point;°dONLNd
˚ΔÃ(Δ
 °dONLNd
˚Ó)
e°dONLNd
˚“
t)xpansionDITLresID: Integer;°dONLNd)
˚
t
z)¢
 °dONLNd0    ΔÃ(Δ
 °dONLNd1    Ó)
d°dONLNd2    “
n)lgHook: ExpDlgHookProcPtr;°dONLNdL    
n
t)ú
 °dONLNdSΔ#Ã( Δ
 °dONLNdTÃ#“)
f°dONLNdU“#
ò)!ilterProc: ExpModalFilterProcPtr;°dONLNdv
ò#
û)Δ
 °dONLNd}%Δ1Ã(.Δ
 °dONLNd~%Ã1“)
y°dONLNd%“1
J)ourDataPtr: UNIV Ptr°dONLNdì%
J1
V)x):°dONLNdï%
V1
Ä) OSErr;°dONLNdù=lIÑ(Flrepl°dONLNd°=ÑIä)
y.
°dONLNd£=ÆIµ)*
A∫†°dONLNd§=µIΩ) n°dONLNd¶=æI

)    ew subscriber râÄ°dONLNdµ=

I
)Ceply±°dONLNdπ=
I
^), new publisher rî@°dONLNd =
^I
q)Keplyª¿°dONLNdŒ=
pI
z), o1@°dONLNd—=
{I
Ö)r s‡‡°dONLNd‘=
ÖI
≈)
ection options °dONLNd„IÆU±(RÆ
rE°dONLNd‰I≤U«)eply @°dONLNdÈI»UÀ)
rÕ@°dONLNdÍIÀU›)ecorA†°dONLNdÓIfiUÈ)d. /¿°dONLNdÒIÈUÔ)
Y@°dONLNdÚIÓU
v)ou specify information in the fiêÄ°dONLNdI
wU
≠)âelds of this r‚¿°dONLNd I
≠U
ø)6ecorW °dONLNd$I
¿U
»)d °dONLNd&UÆa¿(^Æjust ›@°dONLNd+U¿aÀ)as ö@°dONLNd.UÃa
+)you do in the the corr… °dONLNdDU
+a
b)_esponding fi
 °dONLNdPU
ca
Ü)8    elds of r£@°dONLNdYU
Üa
ò)#ecor†°dONLNd]U
ôa
À)ds used by .°dONLNdhaÆm
 (jÆNewSubscriberDialog°dONLNd{a
 m
%)r, °dONLNd}a
%m
ë)NewPublisherDialog°dONLNdèa
ëm
©)l, and °dONLNdïmÆy
&(vÆSectionOptionsDialog°dONLNd©m
&y
))x
.°dONLNd´}lâä(Ülwhere.
°dONLNd±}Æâµ)B
A∫†°dONLNd≤}µâ

) point that specifir†°dONLNd≈}
â
e)Mes a location on the scrœÄ°dONLNd›}
eâ
ç)ceen wherk °dONLNdÂ}
éâ
Ù))e the function displays °dONLNd˝âÆïÒ(íÆthe dialog box. F†°dONLNdâÚï¯)D
Y °dONLNdâ¯ï
Á)6ou can automatically center the dialog box by passing .°dONLNdDïÆ°≤(ûÆ
(°dONLNdFï≤°Ó)–1, –1) in the °dONLNdUïÓ°
)<where°dONLNdZï
°
>)
 parameter¬†°dONLNddï
=°
B)1. ˇ?Ç@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-97
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\ähˆ(eäexpansionDITLresID°dONLNdhÃt‘+B
AÛ`°dONLNdh”t

) value of 0Û`°dONLNdh

t
*).
 or a valiÛ`°dONLNd)h
*t
6))d iÛ`°dONLNd,h
6t
_)
tem list (Û`°dONLNd6h
_t
É))'DITL'Û`°dONLNd<h
Ét
ç)$) r≈¿°dONLNd?h
çt
§)
esourò °dONLNdDh
§t)ce ID. This integer is .
°dONLNd[tÃÄ‹(}Ãthe ›`°dONLNd_t‹Ä
É)'ID of a dialog item list whose items ar;°dONLNdÜt
ÑÄ)®e appended to the end of the °dONLNd£ÄÃåÌ(âÃstandar±Ä°dONLNd™ÄÌå
ª)!1d dialog item list. The dialog items keep their r+°dONLNd€Ä
ºå    )œelative positions, °dONLNdÓåÃò¸(ïÃbut they ardž°dONLNd˘å¸ò
A)0e moved as a gr≤Ä°dONLNd
å
Aò
›)E#oup to the bottom of the dialog boxœÄ°dONLNd
+å
›ò
fl)ú
..°dONLNd
-úä®Æ(•ädlgHoo°dONLNd
3úÆ®¥)$
k°dONLNd
5úî‘)
AÛ`°dONLNd
6ú”®
´)0 pointer to an expandable dialog hook function oÛ`°dONLNd
fú
´®
±)ÿr Û`°dONLNd
hú
±®
√)NILÛ`°dONLNd
kú
è
»). ï°dONLNd
mú
»®)An expandable .
°dONLNd
{®Ã¥(±ÃIdialog hook function is similar to a dialog hook function except that an °dONLNd
ƒ¥Ã¿
Ì*?expandable dialog hook function accepts an additional parameter∞Ä°dONLNd¥
Ì¿
Ú(Ω
Ì. .°dONLNd¿ÃÓ(…Ã
T°dONLNd¿“Ç)he °dONLNd    ¿‡Ã
d)NewSubscriberExpDialog°dONLNd¿
dÃ
i)Ñ, °dONLNd!¿
iÃ
Á)NewPublisherExpDialog°dONLNd6¿
ÁÃ
ˇ)~, and °dONLNd<ÃÃÿ
V(’ÃSectionOptionsExpDialog°dONLNdSÃ
Vÿ
Ü)ä functions c°dONLNd_Ã
Üÿ
ê)0al°dONLNdaÃ
êÿ)
l your expandable dialog °dONLNdzÿÉ
(·Ãhook function a°dONLNdâÿ
‰
T)Efter each call t°dONLNdôÿ
T‰
f)Co th°dONLNdùÿ
f‰
m)e °dONLNdüÿ
m‰
Ø)ModalDialog°dONLNd™ÿ
؉
ª)B prR`°dONLNd≠ÿ
ª‰
ÿ)ocedur$¿°dONLNd≥ÿ
ÿ‰
›)
e$¿°dONLNd¥ÿ
›‰
Ë). T$¿°dONLNd∑ÿ
ˉ
ˆ)he .
°dONLNd∫‰Ã

(ÌÃexpandable  °dONLNd≈‰

1)6
dialog hooH†°dONLNdœ‰
1
Ñ)/k function should t7Ä°dONLNd‚‰
Ö
è)TakΔ†°dONLNd‰‰
è
ô)
e tR†°dONLNdÁ‰
ö
º)he appr6‡°dONLNdÓ‰
º)"opriate action, such .°dONLNdøfl(˘Ãas fi°dONLNdfl¸
)lling in a chec°dONLNd
¸
))?kb°dONLNd
)¸
L)ox. The °dONLNd!
L¸
à)#
itemOffset°dONLNd+
à¸
“)< parameter to th°dONLNd;
“¸)Je expandable .
°dONLNdH¸Ã

-(
Ãdialog hook function i3@°dONLNd^¸
.

§)bs the number of items in th⁄@°dONLNdy¸
§

Æ)ve i@°dONLNd|¸
Ø

È)tem list befor°dONLNdä¸
È
):e your °dONLNdë
Ã

7(
Ãexpansion dialog items. z‡°dONLNd©

7

=)k
Y;`°dONLNd™

=

√)ou need to subtract the item of °dONLNd…

√

‹)Üfset fr‡°dONLNd–

›
)om the item °dONLNd‹
Ã
 

(
Ãhit to get the rqÄ°dONLNdÏ



 
®)>#elative item number in the expansioÓ†°dONLNd

®
 
≥)ûn i(`°dONLNd

¥
 
‘)tem listÿÄ°dONLNd

‘
 
Ï) . The °dONLNd 
 Ã
,
Ö(
)Ã(expandable dialog hook function should r∫ °dONLNdH
 
Ö
,
„)πeturn as its function r    @°dONLNd_
 
‰
,)_
esult the °dONLNdi
,Ã
8
,(
5Ãabsolute item number±°dONLNd}
,
,
8
1)`. .°dONLNdÄ
<ä
H¿(
Eä    filterPro°dONLNdâ
<¿
HΔ)6
c°dONLNdã
HÃ
T‘+
AÛ`°dONLNdå
H”
T
è)( pointer to an expandable modal-dialog fiÛ`°dONLNdµ
H
è
T
Õ)ºlter function oÛ`°dONLNdƒ
H
Õ
T
”)>r Û`°dONLNdΔ
H
”
T
Â)NILÛ`°dONLNd…
H
Â
T
Í). ï°dONLNdÀ
H
Í
T
˘)An .
°dONLNdŒ
TÃ
`
E(
]Ãexpandable modal-dialog fi:Ä°dONLNdË
T
F
`
˙)z+lter function is similar to a modal-dialog °dONLNd
`Ã
l“(
iÃ
fiå¿°dONLNd
`“
l„)lter Û¿°dONLNd
`„
l
7)function or event fiD °dONLNd.
`
8
l
Ê)U(lter function except that an expandable °dONLNdV
lÃ
x
(
uÃmodal-dialog fiü`°dONLNde
l

x
Œ)D,lter function accepts two extra parameters. D`°dONLNdë
l
œ
x
’)ø
Te °dONLNdí
l
’
x
‚)he .°dONLNdï
xÃ
Ñ“(
ÅÃ
M°dONLNdñ
x“
Ñ
)
odalDialog°dONLNd†
x

Ñ
)< prR`°dONLNd£
x

Ñ
7)ocedur$¿°dONLNd©
x
7
Ñ
<)
e$¿°dONLNd™
x
<
Ñ
‰)$ calls the expandable modal-dialog fı@°dONLNdŒ
x
„
Ñ
˙)ßilter .
°dONLNd‘
ÑÃ
ê
(
çÃfunction you pra °dONLNd„
Ñ

ê
w)Eovide in this parameterë °dONLNd˙
Ñ
w
ê
|)f. 2¿°dONLNd¸
Ñ
|
ê
ˇ)An expandable modal-dialog °dONLNd
êÃ
ú“(
ôÃ
fiå¿°dONLNd
ê“
úÊ)lter fG†°dONLNd
êÁ
ú
c)unction allows you to map rª°dONLNd:
ê
c
ú
˚)|!eal events (such as a mouse-down °dONLNd[
úÃ
®(
•ÃLevent) to an item hit (such as clicking a Cancel button). For instance, you °dONLNdß
®Ã
¥
G*may want to map a keyboar‡°dONLNd¿
®
H
¥
ø)|d equivalent to an item hit..°dONLNd›
∏ä
ƒÃ(
¡äyourDataPtr.
°dONLNdÈ
ƒÃ
–◊+BRe˜†°dONLNdÎ
ƒ◊
–
¬)6served for your use. It is passed back to your hook anΔÄ°dONLNd!
ƒ
√
–
È)Ï    d event fS‡°dONLNd*
ƒ
Í
–
˛)'ilter .°dONLNd0
–Ã
‹
∑(
ŸÃ5function. This parameter does not have to be of type °dONLNde
–
∑
‹
…)ÎPtr°dONLNdh
–
…
‹)—it can be any °dONLNdw
‹Ã
Ë
Ä(
ÂÃ(32-bit quantity that you want. In Pascal°dONLNdü
‹
Ä
Ë
æ)¥, you can pass °dONLNdÆ
‹
æ
Ë)>yourDataPtr°dONLNdπ
‹
Ë)B in .
°dONLNdΩ
ËÃ
ٜ(
ÒÃ
rE°dONLNdæ
Ë–
ÙÔ)egister „`°dONLNdΔ
ËÔ
Ù
/)A6, and declar¿°dONLNd‘
Ë
0
Ù
∫)Ae your dialog hook and event fifÄ°dONLNdÛ
Ë
∫
Ù
⁄)ä    lter as lr‡°dONLNd¸
Ë
⁄
Ù
Ó) ocal °dONLNd

ÙÃ
m(
˝Ã$functions without the last parameterˆ °dONLNd%
Ù
l
Í)†. The stack frame is set up prSÄ°dONLNdC
Ù
Î
)operly °dONLNdJÃ
o(    Ã'for these functions to access their parΔ¿°dONLNdq
o
æ)£ent local variablesRÄ°dONLNdÑ
ø
¡)P
.
°dONLNdÜ%H.Å(,HDESCRIPTION
.°dONLNdí3ä?û+BThe °dONLNdñ3û?
)NewPublisherExpDialog°dONLNd´3
?
!)~, °dONLNd≠3
!?
•)NewSubscriberExpDialog°dONLNd√3
•?
Ω)Ñ, and °dONLNd…@äL
(IäSectionOptionsExpDialog°dONLNd‡@
L
é)ä functions display the apprR`°dONLNd˚@
éL    )zopriate dialog box, handle °dONLNd    MäY
o(Vä4user interaction, and call any functions you have prR`°dONLNd    JM
oY
Æ)Âovided in the R`°dONLNd    XM
ÆY
ÿ)?dlgHookR`°dONLNd    _M
ÿY
Ì)* and °dONLNd    dZäfΔ(cä
filterProc°dONLNd    nZΔfˇ)< parameters.°dONLNd    {läx≠(uäFor the °dONLNd    Él≠x
+)#NewPublisherExpDialog°dONLNd    òl
+x
@)~ and °dONLNd    ùl
@x
ƒ)NewSubscriberExpDialog°dONLNd    ≥l
ƒx)Ñ functions, all °dONLNd    √yäÖú(Çäthe °dONLNd    «yúÖ
 )pseudo-items for the StandarR`°dONLNd    „y
 Ö
á)Ñd File Package such as R`°dONLNd    ˙y
áÖ
’)ghookFirstCallR`°dONLNd
y
’Ö
Ï)N(–1), °dONLNd
Üäíÿ(èähookNullEvent°dONLNd
ÜÿíÙ)N(100), °dONLNd
!ÜÙí
N)hookRebuildList°dONLNd
0Ü
Ní
})Z(101), and °dONLNd
;Ü
}í
≈)/hookLastCall°dONLNd
GÜ
≈í)H(–2) can be used, °dONLNd
Yìäüπ(úäas well as °dONLNd
dìπü
)/hookRedrawPreview°dONLNd
uì
ü
9)f(150).ˇ™@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-98    )BEdition Manager Reference4^*¿
¯
.°dONLNd\lhè(elFor the ,
Courier°dONLNd\èh
)#SectionOptionsExpDialog°dONLNd\
h
–)ä) function, the only valid pseudo-items arR`°dONLNdH\
–h
◊)∑e °dONLNdJilu∫(rlhookFirstCall°dONLNdWi∫u—)N(–1), °dONLNd]i—u
)hookNullEvent°dONLNdji
u
;)N(100), °dONLNdqi
;u
É)hookLastCall°dONLNd}i
Éu
ö)H(–2), °dONLNdÉvlÇfi(lemHookRedrawPreview°dONLNdñvfiÇ˙)r(150), °dONLNdùv˙Ç
l)emHookCancelSection°dONLNd∞v
lÇ
à)r(160), °dONLNd∑Élèfi(ålemHookGoToPublisher°dONLNd Éfiè˙)r(161), °dONLNd—É˙è
l)emHookGetEditionNow°dONLNd‰É
lè
à)r(162), °dONLNdÎêlú‰(ôlemHookSendEditionNow°dONLNdˇê‰ú
)x(162), °dONLNd
ê
ú
Ñ)emHookManualUpdateMode°dONLNd
ê
Ñú
≥)Ñ(163), and °dONLNd
'ùl©‰(¶lemHookAutoUpdateMode°dONLNd
;ù‰©˛)x(164)..
°dONLNd
BØlªÄ(∏lIf yo∑°dONLNd
GØĪí)u pr@°dONLNd
KØ쪘)ovide an expandable dw°dONLNd
`ؘª
‘)d3ialog hook function, it must contain the following °dONLNd
ìºl»ô(≈l    parameter°dONLNd
úºö»†).s:.°dONLNd
ü’l·
⁄(fil=FUNCTION MyExpDlgHook (itemOffset: Integer; itemHit: Integer;°dONLNd
„¸Ô
Ä+êtheDialog: DialogPtr; °dONLNdÒÍ˝(˙Í
 °dONLNdÒ¸˝
\)yourDataPtr: Ptr°dONLNdÒ
\˝
h)`):°dONLNdÒ
h˝
û)     Integer;.
°dONLNd!
    l
Ä(
lIf yo∑°dONLNd&
    Ä
í)u pr@°dONLNd*
    ì

2)"ovide an expandable modal-dialog fí@°dONLNdL
    
2

e)üilter functioÄ°dONLNdY
    
f

n)4n,o‡°dONLNd[
    
n

Ú) it must contain the following °dONLNdz
l
"†(
lparameters..°dONLNdÜ
/l
;
í*1FUNCTION MyExpModalFilter (theDialog: DialogPtr; °dONLNd¡
=

I
∞+¢VAR theEvent: EventRecord; °dONLNdÊ
K

W
å*itemOffset: Integer; °dONLNd
Y

e
í*VAR itemHit: Integer; °dONLNd%
g

s
n*yourDataPtr: Ptr°dONLNd5
g
n
s
z)`):°dONLNd7
g
z
s
™) Boolean°dONLNd?
g
™
s
∞)0
;
.
°dONLNdA
é*
óQ(
ï*SEE ALSO
°dONLNdJ
úl
®
+B$See the chapter “Dialog Manager” in Q °dONLNdn
ú

®
è)•Inside Macintosh: Macintosh T£†°dONLNdã
ú
é
®
“)}oolbox Essentialsh†°dONLNdú
ú
”
®
‰)E for °dONLNd°
©l
µ
z(
≤l>additional information on item lists. See the chapter “Standar¯†°dONLNdfl
©
z
µ
Ã(
≤
zd File Package” in °dONLNdÚ
∂l
†(
ølInside qÄ°dONLNd˘
∂á
¬Ã)Macintosh: Files Δ‡°dONLNd

∂Ã
¬
Ø)E1for information on dialog hook and modal-dialog fiŒ@°dONLNd<
∂
Ø
¬
Ï)„lter functions.


Ê*
Ó
¯4
Á*
Ó
¯ 
È*
È
˛

ˇ·ˇ‚7^°dONLNdM
Ÿ*
ÁÊ(
„*#Locating a Publisher and Edition Fr˝Ä°dONLNdp
ŸÊ
Á
;)ºom a Subscriberˇˇˇˇˇˇ(
„
Ú
2
.°dONLNdÅ
Ól
˙Ä(
˜lThe °dONLNdÖ
ÓÄ
˙‘)GetEditionInfo°dONLNdì
Ó‘
˙
)T function rR`°dONLNdû
Ó

˙
Û),9eturns information about a section’s edition such as its .
°dONLNd◊
˚l√(llocation, last modifi
‡°dONLNdÏ
˚ƒ

)Xcation date, cr¿¿°dONLNd˚
˚


)=eatorwÄ°dONLNd
˚

E), and type..°dONLNdl
O(l5Once you locate a section’s edition, you can use the °dONLNdA
O
«)„GoToPublisherSection°dONLNdU
«
Ô)x
 function .
°dONLNd_l&}(#lto fiƒ†°dONLNdd}&
7)(nd the document containing the publisherÄ°dONLNdå
7&
9)∫
.

V*_
¯4W*^
¯ X*X
˛

ˇ·ˇ‚7^
°dONLNdèI*W}(S*GetEditionInfoˇˇˇˇˇˇ(S
Ú
2
.°dONLNdühltë(qlUse the °dONLNdßhëtÂ)%GetEditionInfo°dONLNdµhÂt
€)T9 function to obtain information about a section’s edition°dONLNdÓh
€t
fi)ˆ
,°dONLNdÔh
fit
ˆ) such .
°dONLNdıulÅ‹(~las its location, last modifi¶†°dONLNdu‹Å
)pcation date, creÄ°dONLNd u
Å
0)>eator@°dONLNd%u
0Å
^), and type..°dONLNd1élöˆ(ólFUNCTION GetEditionInfo°dONLNdPúÍ®
Ü+~(sectionH: SectionHandle; °dONLNdr™Í∂*
 °dONLNds™∂
º)"VAR editionInfo: EditionInfoRecord°dONLNdï™
º∂
»)Ã):°dONLNdó™
»∂
Ú) OSErr;ˇ7@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡2-99
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\äh¥(eäsection°dONLNd\¥h∫)*
H.
°dONLNd    \Ãh”)
A∫†°dONLNd
\”h€) h°dONLNd\‹h
8)    andle to the section ṙ°dONLNd"\
7h
I)[ecorb@°dONLNd&\
Jh
®)d for a given section. .°dONLNd>läxÃ(uäeditionInfo°dONLNdJxÃÑŸ+BAn°dONLNdLxŸÑ
:) edition information rR`°dONLNdbx
:Ñ
L)aecor$¿°dONLNdfx
LÑ
k)d. The $¿°dONLNdmx
kÑ
ø)GetEditionInfo$¿°dONLNd{x
øÑ
Î)T function r˜ °dONLNdÜx
ÍÑ)+eturns .
°dONLNdçÑÃê
∫(çÃ7the public information contained in the section’s contrE†°dONLNdƒÑ
ªê
‡)Ô    ol block.
°dONLNdŒ©H≤Å(∞HDESCRIPTION
°dONLNd⁄∑ä√„+BThe Edition Managel†°dONLNdÏ∑‰√Ô)Zr e®‡°dONLNdÔ∑Ô√
)nsurÉ`°dONLNdÛ∑
√
)
eM°dONLNdÙ∑
√
)
sä°dONLNdı∑
√
¶)$ that the existing edition name corr¨ °dONLNd
∑
¶√)öesponds to the FinderH°dONLNd
.∑√)a’s .°dONLNd
1ƒä–
(Õäexisting edition name. If the °dONLNd
Oƒ
–
6)Çcontrol°dONLNd
Vƒ
6–
<)*
B°dONLNd
Wƒ
<–
T)lock°dONLNd
[ƒ
T–
]) fi°dONLNd
^ƒ
]–
∞)    eld of the section rR`°dONLNd
rƒ
∞–
¬)Secor$¿°dONLNd
vƒ
¬–
‘)d is $¿°dONLNd
{ƒ
‘–
Ó)set to $¿°dONLNd
ǃ
Ó–
˙)NI$¿°dONLNd
у
˙–)
LΔ`°dONLNd
Öƒ
ˇ–) oΔ`°dONLNd
ზ)r °dONLNd
â—ä›
#(⁄ä#the edition cannot be located, the °dONLNd
¨—
#›
w)ôGetEditionInfo°dONLNd
∫—
w›
£)T function rR`°dONLNd
≈—
£›
Õ),
eturns an R`°dONLNd
œ—
Õ›
Ò)*fnfErrR`°dONLNd
’—
Ò›
Û)$
 .
°dONLNd
÷fiäÍç(Áä
rE°dONLNd
◊fiéÍ•)esult ˝Ä°dONLNd
›fi•Íπ)code»†°dONLNd
·fi∫ͺ)
..°dONLNd
„ä¸û(˘äThe °dONLNd
Áû¸Ú)GetEditionInfo°dONLNd
ıÚ¸
)T function rR`°dONLNd
¸),9eturns information about the section’s edition in a data °dONLNd9˝ä
    ñ(
ästrl°dONLNd<˝ñ
    ¨)uctur>`°dONLNdA˝¨
    ’)
e of type >`°dONLNdK˝’
    
;))EditionInfoRecord>`°dONLNd\˝
;
    
>)f
.°dONLNd^
ä
 
 (
äTYPE EditionInfoRecord = °dONLNdy
"ú
.¿+RECORD°dONLNdÇ
0Æ
<ÿ+crDate:°dONLNdç
0ˆ
<
2)H
TimeStamp;°dONLNdû
0
t
<
)~{date edition container }°dONLNd≈
>
t
J
»*{ was created}°dONLNd÷
LÆ
Xÿ(
UÆmdDate:°dONLNd·
Lˆ
X
2)H
TimeStamp;°dONLNdÚ
L
t
X
Ú)~{date of last change}°dONLNd

ZÆ
fÍ(
cÆ
fdCreator:°dONLNd
Zˆ
f
 )HOSType;°dONLNd&
Z
t
f
»)~{file creator}°dONLNd7
hÆ
tÿ(
qÆfdType:°dONLNdB
hˆ
t
 )HOSType;°dONLNdP
h
t
t
∂)~{file type}°dONLNd^
vÆ
ÇÍ(
Æ
container:°dONLNdl
vˆ
Ç
t)HEditionContainerSpec;°dONLNdà
v
t
Ç
¬)~{the edition}°dONLNdó
Ñú
ê¥(
çúEND;


ùH
¨4
ûH
¨
    .
°dONLNdú
ùä
®÷(
•äField descriptions

ˇ·ˇ‚7^
.°dONLNdØ
™ä
∂Æ*crDate.
°dONLNd∂
™Ê
∂Ò)\Thr °dONLNd∏
™Ú
∂˝)e c,°dONLNdª
™˛
∂

)
rÒ°dONLNdº
™


∂
t)eation date of the edition. .°dONLNd⁄
πä
Ů(
ŠmdDate.
°dONLNd·
πÊ
≈Ò)\Thr °dONLNd„
πÚ
≈
)e mè¿°dONLNdÊ
π

≈
)odifi °dONLNdÎ
π

≈
á)cation date of the edition..°dONLNd
Ȋ
‘¿(
—ä    fdCreator.
°dONLNd
»Ê
‘Ï)\
T†¿°dONLNd
»Ï
‘˝)he c,°dONLNd
»˛
‘

)
rÒ°dONLNd
»


‘
)eatorÄ°dONLNd
»

‘
)r oZ†°dONLNd
»
 
‘
])f the edition fiX°dONLNd.
»
^
‘
j)>le. .°dONLNd3
׊
„Æ(
‡äfdType.
°dONLNd:
◊Ê
„Ò)\Thr °dONLNd<
◊Ú
„ˇ)e fi»Ä°dONLNd@
◊ˇ
„
)le type ¿°dONLNdH
◊
 
„
c)!of the edition fi䆰dONLNdY
◊
c
„
o)Cle. .°dONLNd^
Êä
Ú∫(
Ôäcontaine°dONLNdf
Ê∫
Ú¿)0
r.
°dONLNdh
ÊÊ
Ú
G),An edition container rÄ°dONLNd~
Ê
H
Ú
Z)becorć°dONLNdÇ
Ê
Z
Ú
ü)d, which specifi› °dONLNdí
Ê
ü
Ú
¿)Ees the vg`°dONLNdö
Ê
¡
Ú
„)"olume rØ°dONLNd°
Ê
„
Ú
Û)"efer[ °dONLNd•
Ê
Ù
Ú
)ence °dONLNd™
ÚÊ
˛
(
˚Ênumber≥°dONLNd∞
Ú

˛
)", dir| °dONLNdµ
Ú

˛
N)ectory ID, fiò °dONLNd¬
Ú
N
˛
˛)4(lename, script, and part number for the °dONLNdÍ
˛Ê

(Êedition.
°dONLNdÛ#H,b(*HRESULëÄ°dONLNd¯#b,Ü)T CODES°dONLNdklHuo(sHSEE ALSO
.°dONLNdtzäÜ
    +BFor an example of the use of °dONLNdëz
    Ü
])GetEditionInfo°dONLNdüz
]Ü
r)T, see °dONLNd•z
rÜ
¢)Listing 2-8°dONLNd∞z
¢Ü
›)0 beginning on °dONLNdæz
݆
ı);page °dONLNd√z
ıÜ)2-46°dONLNd«zÜ). .
°dONLNd…áäì
)(êä&For another use of this function, see |‡°dONLNdÔá
*ì
é)†“Canceling Sections Wl°dONLNdá
éì)dithin Documents” beginning °dONLNdîä†Ø(ùäon page !¿°dONLNd'î∞†¬)&2-48u†°dONLNd+
Å).. For a description of the edition container rˇ°dONLNdYî
ņ
ì)øecor]@°dONLNd]î
î†
Ø)d, see …@°dONLNddî
؆
Δ)page § °dONLNdiî
Ǡ
Ÿ)2-71¯°dONLNdmî
٠
fi). .°dONLNdˇ1ä=®(:änoErr.
°dONLNd1
=
)â
0°dONLNd1
,=
H)No errE†°dONLNd1
I=
R)or.°dONLNd<äHÆ(EäfnfErr.
°dONLNd<
    H
)–43°dONLNd<
,H
C)#Not rÀ¿°dONLNd!<
CH
`)egister‡°dONLNd(<
aH
Ä)ed or fiu °dONLNd0<
ÄH
©)le moved.°dONLNd:GäS(PäeditionMgrInitErr.
°dONLNdLG
S
)z–450°dONLNdQG
,S
ì)(Manager not initializedˇ,@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-100    )BEdition Manager Reference4^*¿
¯

j*r
¯4j*r
¯ l*l
˛

ˇ·ˇ‚7^
°dONLNd\*j3(f*
G~@°dONLNd
\4jB)
oT÷Ä°dONLNd\Aj•)oPublisherSectionˇˇˇˇˇˇ(f
Ú
2
°dONLNd{lá
Æ(ÑlJWhen the user wants to locate the publisher for a particular subscriber (bÆ¿°dONLNd`{
Æá
€(Ñ
Æy clicking .°dONLNdkàlît(ël
O°dONLNdlàtîÜ)pen °dONLNdpàÜî
e)3Publisher in the subscriber options dialog box), th°dONLNd£à
eî
l)fle ,
Courier°dONLNd•à
lî
‰)SectionOptionsDialog°dONLNdπà
‰î
Ê)x
 °dONLNd∫ïl°ñ(ûl
function rR`°dONLNdƒïñ°À)*eturns the aR`°dONLNd–ïÀ°˘)5ction code R`°dONLNd€ï˘°
).'gotoR`°dONLNd‡ï
°
)
'R`°dONLNd·ï
°
<) in the R`°dONLNdÈï
<°
`)actionR`°dONLNdÔï
`°
i)$ fiR`°dONLNdÚï
i°
fl)    eld of the section options r$¿°dONLNd
ï
fl°
ˆ)veply .
°dONLNd
¢lÆo(´l
rE°dONLNd
¢pÆÇ)ecorπ`°dONLNd
¢ÇÆ¡)d. When you r@°dONLNd
%¢¬Æ
Ë)@Aeceive this action code, you should open the document containing °dONLNd
fØlª|(∏lthe ›`°dONLNd
jØ|ª¶)    publisherL@°dONLNd
sضª´)*. .°dONLNd
v¡lÕê( l    First, us°dONLNd
¡êÕ©)$e the °dONLNd
Ö¡©Õ˝)GetEditionInfo°dONLNd
ì¡˝Õ
7)T function to fi°dONLNd
¢¡
7Õ
£):nd the edition container¬†°dONLNd
∫¡
¢Õ
≈)k. Then u¬†°dONLNd
¬¡
≈Õ
‚)#se the °dONLNd
…Œl⁄‰(◊lGoToPublisherSection°dONLNd
›Œ‰⁄
€)x7 function to open the document containing the publisher¬†°dONLNdŒ
⁄⁄
›)ˆ
.°dONLNdÁlÛr(l
F°dONLNdÁrÛ
 )UNCTION GoToPublisherSection °dONLNd=ı¸


º+ä (container: EditionContainerSpec°dONLNd]ı
º


»)¿):°dONLNd_ı
»


Ú) OSErr;°dONLNdg
l
ú(
lcontaine°dONLNdo
ú
¢)0
r.
°dONLNdq
Æ

)An edition container rÄ°dONLNdá



")becorć°dONLNdã

"

g)d, which specifi› °dONLNdõ

g

x)Ees v
°dONLNdü

y

õ)olume rQ†°dONLNd¶

õ

´)"efer˝¿°dONLNd™

´

‰)ence numberÖ†°dONLNdµ

‰

È)9, °dONLNd∑
Æ
%∫(
"ÆdirI °dONLNd∫
ª
%
)ectory ID, and fi“@°dONLNdÀ


%
")GlenameÛ@°dONLNd—

"
%
m)  of the subscribero@°dONLNd„

o
%
ö)M’s edition.≤‡°dONLNdÓ

ö
%
ú)+
 @°dONLNdÔ

ù
%
£)
Y≈¿°dONLNd

¢
%
fi)ou obtain the .°dONLNd˛
%Æ
1
>(
.Æ!edition container by calling the °dONLNd
%
>
1
í)êGetEditionInfo°dONLNd-
%
í
1
Ω)T function. 
.
°dONLNd9
K*
Tc(
R*DESCRIPTION
.°dONLNdE
Xl
dÄ+BThe °dONLNdI
XÄ
d¯)GoToPublisherSection°dONLNd]
X¯
d
$)x function rR`°dONLNdh
X
$
d
≈),%esolves the alias in the edition to fiR`°dONLNdé
X
≈
d
“)°nd .
°dONLNdë
el
q|(
nlthe ›`°dONLNdï
e|
q
)!document containing its publisherÍ °dONLNd∂
e

q
◊)ó0. In general, this function internally uses the .°dONLNdÊ
rl
~ÿ(
{lGetStandardFormats°dONLNd¯
rÿ
~
Ë)l> function to get the alias to the publisher document and then .
°dONLNd6
l
ão(
àl
rE°dONLNd7
p
ã
3)/esolves the alias. It next sends the Finder an ä`°dONLNdf

3
ã
)√(Apple event to open the document (which °dONLNdé
ål
ò
á(
ïlDlaunches its application if necessary) and, after the publisher is rº °dONLNd“
å
á
ò
§(
ï
áegister@°dONLNdŸ
å
•
ò
ÿ)ed, sends a °dONLNdÂ
ôl
•ú(
¢lSection Scr`@°dONLNd
ôú
•

)0oll event to the publisher˜‡°dONLNd

ô
    
•
)m
..°dONLNd
´l
∑Ê(
¥lAs an optimization, if therR`°dONLNd'
´Ê
∑
)ze is a r$¿°dONLNd/
´

∑
")egister˜ °dONLNd6
´
!
∑
Z)ed publisher9¿°dONLNdB
´
Z
∑
q)9, the 9¿°dONLNdH
´
q
∑
È)GoToPublisherSection9¿°dONLNd\
´
È
∑
Î)x
 .
°dONLNd]
∏l
ƒ
(
¡l#function simply sends a Section Scr@°dONLNdÄ
∏

ƒ
v)úoll event to the publisher©‡°dONLNdö
∏
u
ƒ
z)m. °dONLNdù
 l
÷
;(
”l1If the edition does not contain an alias and ther °dONLNdŒ
 
<
÷
L)–e ar ¿°dONLNd“
 
L
÷
e)e no rˆ@°dONLNdÿ
 
d
÷
Å)egisterE`°dONLNdfl
 
Ç
÷
È)ed publishers, then the .°dONLNd˜
◊l
„‰(
‡lGoToPublisherSection°dONLNd
◊‰
„
Ò)x< function sends an Open Documents event to open the edition .
°dONLNdG
‰l
è(
Ìl    to the crJÄ°dONLNdP
‰ê
‚)$eating application.°dONLNdd
ˆl
#(
ˇl,If the edition container is not an edition fiä¿°dONLNdë
ˆ
#
¢)∑le (as is the case when you ar[`°dONLNdØ
ˆ
£
≈)Äe using .°dONLNd∑l
(l)bottlenecks to subscribe to non-edition fi°dONLNd·

F)≤
les), the °dONLNdÎ
F
æ)(GoToPublisherSection°dONLNdˇ
æ
Ê)x
 function .
°dONLNd    l≈(lsends the Finder an "°dONLNd≈
;)YApple event to open that fiö °dONLNd8
;
G)vle. 
°dONLNd=7*@D(>*RESULëÄ°dONLNdB7D@h)T CODES
.°dONLNdIDlPä+(noErr.
°dONLNdODıP˙)â
0°dONLNdQD
P
*)No errE†°dONLNdWD
+P
4)or.°dONLNd[Ol[ê(XlfnfErr.
°dONLNdbOÎ[˙)–43°dONLNdfO
[
L)#File not found.°dONLNdvZlf“(cleditionMgrInitErr.
°dONLNdàZÊf˙)z–450°dONLNdçZ
f
u)(Manager not initialized.°dONLNd¶elq∫(nlbadSubPartErr.
°dONLNd¥eÊq˙)z–454°dONLNdπe
q
{)(Invalid edition containerˇ8h@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡
ˇ2-101
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\Heo(cHSEE ALSO
°dONLNd    jäv
ª+BIFor illustrations of the section options dialog box for subscribers, see Ö†°dONLNdRj
ªv
”(s
ªFigurX`°dONLNdWj
”v
Ï)e 2-15ı‡°dONLNd]j
Ïv
¸) on °dONLNdawäÉ°(Ääpage Z‡°dONLNdfw¢É¥)2-44Æ¿°dONLNdjw¥É…) and õ‡°dONLNdow É‚)Figurn†°dONLNdtw‚É˚)e 2-16 °dONLNdzw¸É
) on S°dONLNd~w
É
#)page -‡°dONLNdÉw
$É
6)2-45Å¿°dONLNdáw
6É
ê). For an example of rS °dONLNdúw
ëÉ)[esponding to the action code ,
Courier.°dONLNdπÑäêÆ(çä'goto'°dONLNdøÑÆê√)$, see °dONLNd≈Ñ√êÛ)Listing 2-8°dONLNd–ÑÛê
.)0 beginning on °dONLNdfiÑ
.ê
F);page °dONLNd„Ñ
Fê
Y)2-46°dONLNdÁÑ
Yê
Ï)#. For a description of the edition .
°dONLNd

ëäùπ(öäcontainer r4Ä°dONLNd
ë∫ùÃ)0ecor®‡°dONLNd
ëÃùÁ)d, see ‡°dONLNd
 ëËùˇ)page Ô¿°dONLNd
%ëˇù
)2-71C†°dONLNd
)ë
ù
)
.

¡H…4¬H… ƒHƒ

ˇ·ˇ‚7^°dONLNd
,¥H¬’(æHEdition Container Formatsˇˇˇˇˇˇ(æ
2
.°dONLNd
G…ä’
(“äThe Edition Manager calls the °dONLNd
e…
’
Ç)åGetStandardFormats°dONLNd
w…
Ç’)l# function to get the alias used in °dONLNd
ö÷ä‚ú(fläthe °dONLNd
û÷ú‚
)GoToPublisherSection°dONLNd
≤÷
‚
Ü)x function and to get the prR`°dONLNd
Õ÷
Ü‚)review shown in the subscriber .
°dONLNd
΄äÔΩ(Ïädialog box. È@°dONLNd
˜„ΩÔ√)3
Y©¿°dONLNd
¯„√Ô⁄)ou prmÄ°dONLNd
˝„€Ô
ñ),obably do not need to call this function dir°dONLNd)„
óÔ
´)ºectlyÊ°dONLNd.„
™Ô
¨)
.


H
(4
 H
' 
!H
!

ˇ·ˇ‚7^
°dONLNd1
H
 π(
HGetStandardFormatsˇˇˇˇˇˇ(

2
.°dONLNdE
1ä
=ë(
:ä
Yï°dONLNdF
1ê
=¶)ou prg`°dONLNdK
1¶
=
,)obably do not need to call the g`°dONLNdj
1
,
=
ò)ÜGetStandardFormatsg`°dONLNd|
1
ò
=
Œ)l function dir9¿°dONLNdâ
1
Œ
=)6ectly because .
°dONLNdó
>ä
J
7(
Gä(the Edition Manager calls this function..°dONLNd¿
Wä
c
2*FUNCTION GetStandardFormats °dONLNd‚
e‰
q
∞+Z"(container: EditionContainerSpec; °dONLNd

s‰
Í*
 °dONLNd
sÍ

û)VAR previewFormat: FormatType;°dONLNd/
ʼn
çÍ(
ä‰
 °dONLNd0
ÅÍ
ç
∞)!preview, publisherAlias, formats:°dONLNdQ
Å
∞
ç
∂)Δ
 °dONLNdR
Å
∂
ç
⁄)Handle°dONLNdX
Å
⁄
ç
Ê)$):°dONLNdZ
Å
Ê
ç) OSErr;°dONLNdb
ôä
•∫(
¢äcontaine°dONLNdj
ô∫
•¿)0
r.
°dONLNdl
ôÃ
•
-)An edition container rÄ°dONLNdÇ
ô
.
•
@)becorć°dONLNdÜ
ô
@
•
x)d that specifi`‡°dONLNdî
ô
y
•
ô)9es the eÄ°dONLNdú
ô
ö
•
fl)!dition volume rÚ °dONLNd´
ô
fi
•
Ó)Deferû@°dONLNdØ
ô
Ô
•)ence °dONLNd¥
•Ã
±Ó(
ÆÃnumber≥°dONLNd∫
•Ó
±ˇ)", dir| °dONLNdø
•

±
4)ectory ID, fiò °dONLNdÃ
•
4
±
Å)4lename, and part..°dONLNdfi
µä
¡ÿ(
æäpreviewFormat°dONLNdÏ
¡Ã
Õ‡+BThe °dONLNd
¡‡
Õ
L)GetStandardFormats°dONLNd
¡
L
Õ
x)l function rR`°dONLNd
¡
x
Õ),"eturns in this parameter a handle .
°dONLNd/
ÕÃ
ŸÍ(
÷Ãto the f9†°dONLNd7
ÕÎ
Ÿ
)irst format f`°dONLNdC
Õ

Ÿ
;)1of the r“ °dONLNdK
Õ
;
Ÿ
æ)equested format type that it fiÁ†°dONLNdj
Õ
æ
Ÿ)Énds in the edition.Ë@°dONLNd}
Õ
Ÿ)P
 .°dONLNd
݊
È¥(
Êäpreview°dONLNdá
›Ã
È‘)B
AÛ`°dONLNdà
›”
È
$) format type. The Û`°dONLNdö
›
$
È
ê)QGetStandardFormatsÛ`°dONLNd¨
›
ê
È)l  function looks for a format of .
°dONLNdÃ
ÈÃ
ı
(
ÚÃthe type specifih¿°dONLNd‹
È

ı
Å)Ced in this parameter and r °dONLNdˆ
È
Ç
ı
˛)seturns in this parameter the °dONLNd
ıÃ

$(
˛Ãformat type of the fi£ °dONLNd(
ı
$

t)Xrst format that it fiu °dONLNd=
ı
u

Î)Qnds. The function tries to fiQ‡°dONLNdZ
ı
Ï
)wnd one .°dONLNda
Ã
(
Ãof four formats: °dONLNdr


7)G'prvw'°dONLNdx

7
<)$, °dONLNdz

<
`)'PICT'°dONLNdÄ

`
e)$, °dONLNdÇ

e
â)'TEXT'°dONLNdà

â
ô)$, or °dONLNdç

ô
Ω)'snd '°dONLNdì

Ω
¬)$. °dONLNdñäfi(äpublisherAlias°dONLNd•Ã)‡+BThe °dONLNd©‡)
4)publisherAlias°dONLNd∑
4)
l)T parameter rR`°dONLNd√
l)
∂)8eads the format °dONLNd”)Ã5
\(2ÃkPublisherDocAliasFormat°dONLNdÎ)
\5
b)ê (°dONLNdÌ)
b5
Ü)'alis'°dONLNdÛ)
Ü5
ç)$).°dONLNdˆ9äE¥(BäformatsˇˇÂ¥°dONLNd˛9ÃEfl)BThe ˇˇ±e¥°dONLNd9‡E

)formatsˇˇÂ¥e¥°dONLNd    9

E
A)* parameter r|°dONLNd9
BE
Æ)8eads the virtual format ˇˇ±öL°dONLNd-9
ÆE)lkFormatListFormatˇˇÂ¥öL°dONLNd>9E)f
 °dONLNd?EÃQ–(NÃ
(°dONLNd@E–QÙ)'fmts'°dONLNdFEÙQ˝)$). 
.
°dONLNdJkHtÅ(rHDESCRIPTION
.°dONLNdVxäÑë+B
Yï°dONLNdWxêÑ
º)Bou should pass in valid handles for the formats that you want and ï°dONLNdôx
ºÑ
Œ(Å
ºNIL6†°dONLNdúx
΄) for the formats .
°dONLNd≠Öäë
((éä#that you don’t want. The handles arg °dONLNd–Ö
(ë
3)ûe ru¿°dONLNd”Ö
3ë
¥) esized to the size of the data. .°dONLNdÙóä£é(†ä
I°dONLNdıóé£Δ)f one of the rR`°dONLNdóΔ£
])8"equested formats cannot be found, R`°dONLNd%ó
]£
…)óGetStandardFormatsR`°dONLNd7ó
…£
œ)l r$¿°dONLNd9ó
ϣ
Ù)    eturns a °dONLNdB§ä∞¿(≠ä    noTypeErr°dONLNdK§¿∞Δ)6 rR`°dONLNdM§Δ∞˜)esult code. ˇ“@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-102    )BEdition Manager Reference4^*¿
¯
°dONLNd\*eD(c*RESULëÄ°dONLNd\Deh)T CODES

Ø*∑
¯4∞*∑
¯ ≤*≤
˛

ˇ·ˇ‚7^°dONLNd|¢*∞|(¨*Reading and W(°dONLNdâ¢|∞˙)Rriting Non-Edition Filesˇˇˇˇˇˇ(¨
Ú
2
°dONLNd£∑l√
ï(¿lBThe Edition Manager never opens or closes an edition container diro†°dONLNdÂ∑
ï√
‚(¿
ïectly—it calls the °dONLNd¯ƒl–~(ÕlcurrØ°dONLNd¸ƒ~–Œ)ent edition opener›@°dONLNd
ƒŒ–›)P. Seʆ°dONLNd
ƒ›–‰)e 0@°dONLNd
ƒÂ–
÷)5“Subscribing to Non-Edition Files” beginning on page « °dONLNd
Iƒ
÷–
Ë)Ò2-62°dONLNd
Mƒ
È–
Î)
 °dONLNd
N—l›o(⁄l
f”‡°dONLNd
O—o›‚)or additional information.°dONLNd
j„lÔr(Ïl
Tµ¿°dONLNd
k„qÔ“)o override the standarRÄ°dONLNd
Å„”Ô
!)bd opener functionK`°dONLNd
í„
"Ô
+)O, cª†°dONLNd
ï„
+Ô
.)    
rĆ°dONLNd
ñ„
/Ô
Â)*eate an opener function that contains the °dONLNd
¿l¸Δ(˘lfollowing parameter@Ä°dONLNd
”«¸Õ)[s:,
Courier.°dONLNd
÷
    l

Ü(
l/FUNCTION MyOpener (selector: EditionOpenerVerb;°dONLNd
ÿ
#
ò+l  VAR PB: EditionOpenerParamBlock°dONLNd,

ò
#
§)¿):°dONLNd.

§
#
Œ) OSErr;°dONLNd6
/l
;
Y(
8l3When this function is called by the Edition Manager¬†°dONLNdi
/
X
;
o)Ï, the ¬†°dONLNdo
/
o
;
ü)selector¬†°dONLNdw
/
ü
;
˜)0 parameter is set to °dONLNdå
<l
H˚(
El!one of the edition opener verbs (°dONLNd≠
<˚
H
)èeoOpen°dONLNd≥
<

H
$)$, °dONLNdµ
<
$
H
N)eoClose°dONLNdº
<
N
H
S)*, °dONLNdæ
<
S
H
â)    eoOpenNewï°dONLNd«
<
à
H
ç)5, ï°dONLNd…
<
ç
H
…)
eoCloseNew™°dONLNd”
<
»
H
Õ);, °dONLNd’
Il
U¿(
RleoCanSubscribe°dONLNd„
I¿
U›)T). The °dONLNdÍ
I›
UÈ)PB°dONLNdÏ
IÈ
U
‡)6 parameter contains an edition opener parameter block .
°dONLNd"
Vl
bo(
_l
rE°dONLNd#
Vp
bÇ)ecorπ`°dONLNd'
VÇ
bä)d..°dONLNd*
hl
të(
qlUse the °dONLNd2
hë
t
    )%GetEditionOpenerProc°dONLNdF
h
    
t
})x function to locate the currR`°dONLNdb
h
}
t
 )tent edition openeR`°dONLNds
h
 
t
÷)Mr aR`°dONLNdv
h
÷
t
Û)nd use °dONLNd}
ul
Å~(
~lthe °dONLNdÅ
u~
ň)SetEditionOpenerProc°dONLNdï
uˆ
Å
3)x function to prR`°dONLNd§
u
3
Å
∂)=ovide your own edition openeR`°dONLNd¿
u
∂
Å
∫)É
rï°dONLNd¡
u
π
Å
º)
.ï°dONLNd¬
u
º
Å
æ)
 °dONLNdƒ
ál
ìë(
êlUse the °dONLNdÃ
áë
ì
)%CallEditionOpenerProc°dONLNd·
á

ì
†)~" function to call an edition opene°dONLNd
á
†
ì
¨)ër a°dONLNd
á
¨
ì
€)nd use the °dONLNd
îl
†Ã(
ùlCallFormatIOProc°dONLNd!
îÃ
†
@)` function to call a format I°dONLNd=
î
@
†
v)t/O function.


–*
Ÿ
¯4
—*
ÿ
¯ 
“*
“
˛

ˇ·ˇ‚7^
.
°dONLNdK
√*
—ß(
Õ*GetEditionOpenerProcˇˇˇˇˇˇ(
Õ
Ú
2
.°dONLNda
‚l
Óë(
ÎlUse the °dONLNdi
‚ë
Ó
    )%GetEditionOpenerProc°dONLNd}
‚
    
Ó
})x function to locate the currR`°dONLNdô
‚
}
Ó
 )tent edition openeR`°dONLNd™
‚
 
Ó
Œ)M
rï°dONLNd´
‚
Õ
Ó
–)
.°dONLNd≠
˚l
(lFUNCTION GetEditionOpenerProc°dONLNd“    Í
∞+~!(VAR opener: EditionOpenerProcPtr°dONLNdÛ    
∞
º)Δ):°dONLNdı    
º
Ê) OSErr;°dONLNd˝!l-ê(*lopener°dONLNd!Æ-ª)BTh°dONLNd!ª-¿)
e°dONLNd!¿-¬)
 °dONLNd!¬-
:)GetEditionOpenerProc°dONLNd!
:-
f)x function rR`°dONLNd'!
f-
}),eturnR`°dONLNd,!
}-
ë)s a pR`°dONLNd1!
ë-
‹)ointer to the curr$¿°dONLNdC!
‹-
Ï)Kent .
°dONLNdG-Æ9Í(6Æedition opene†°dONLNdT-Î9
d)=r function in this parameter„°dONLNdp-
c9
e)x
.

i*q
¯4i*q
¯ k*k
˛

ˇ·ˇ‚7^
°dONLNds[*i•(e*SetEditionOpenerProcˇˇˇˇˇˇ(e
Ú
2
.°dONLNdâ{láë(ÑlUse the °dONLNdë{ëá
    )%SetEditionOpenerProc°dONLNd•{
    á
F)x function to prR`°dONLNd¥{
Fá
…)=ovide your own edition openeR`°dONLNd–{
…á
Õ)É
rï°dONLNd—{
Ãá
œ)
.°dONLNd”îl†
 (ùlFUNCTION SetEditionOpenerProc °dONLNd˘¢ÍÆ
ò+~(opener: EditionOpenerProcPtr°dONLNd¢
òÆ
§)Æ):°dONLNd¢
§Æ
Œ) OSErr;°dONLNdjlvä(slnoErr.
°dONLNdjıv˙)â
0°dONLNdj
v
*)No errE†°dONLNdj
+v
4)or.°dONLNdulÅ¢(~l    noTypeErr.
°dONLNd(uÊÅ˙)z–102°dONLNd-u
Å
à)(Edition container not found.°dONLNdJÄlå“(âleditionMgrInitErr.
°dONLNd\ÄÊå˙)z–450°dONLNdaÄ
å
u)(Manager not initializedˇ/≤@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡
ˇ2-103
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\äh®(eäopene°dONLNd\®hÆ)
r.
°dONLNd\Ãh”)$
A∫†°dONLNd\”h€) p<¿°dONLNd
\‹h
P)    ointer to the edition openeÄ°dONLNd%\
Qh
Ç)ur function t^¿°dONLNd1\
Çh
Ø)1
hat you arC@°dONLNd;\
Øh
¿)-e prT°dONLNd?\
¿h
‰)oviding.

óH†4òHü ôHô

ˇ·ˇ‚7^
°dONLNdIäHò»(îHCallEditionOpenerProcˇˇˇˇˇˇ(î
2
.°dONLNd`©äµØ(≤äUse the °dONLNdh©Øµ
-)%CallEditionOpenerProc°dONLNd}©
-µ
æ)~" function to call an edition opene°dONLNdü©
æµ
¬)ë
r¬†°dONLNd†©
¡µ
ƒ)
.°dONLNd¢¬äŒ
D(ÀäFUNCTION CallEditionOpenerProc °dONLNd…–
‹
º+~(selector: EditionOpenerVerb; °dONLNdÔfi
Í
Œ*! VAR PB: EditionOpenerParamBlock;°dONLNd
Ï
¯
º* routine: EditionOpenerProcPtr°dONLNd
6Ï
º¯
»)¥):°dONLNd
8Ï
»¯
Ú) OSErr;°dONLNd
@
ä
∫(
äselector°dONLNd
I
Ã

g)B!An edition opener verb. When the °dONLNd
j

g

Â)õCallEditionOpenerProc°dONLNd


Â
)~
 function ˇˇ≤°dONLNd
â
Ã

^(
à is called by the Edition Manager=°dONLNd
©

^

t)í, the ˇˇH°H°dONLNd
Ø

t

§)selectorˇˇ≤°H°dONLNd
∑

§
)0 parameter is set to one of °dONLNd
”
Ã
(
?(
%Ãthe edition opener verbs (°dONLNd
Ì

?
(
c)seoOpen°dONLNd
Û

c
(
h)$, °dONLNd
ı

h
(
í)eoClose°dONLNd
¸

í
(
ó)*, °dONLNd
˛

ó
(
Õ)    eoOpenNewï°dONLNd

Ã
(
—)5, ï°dONLNd    

—
()
eoCloseNew™°dONLNd

();, °dONLNd
(Ã
4
 (
1ÃeoCanSubscribe°dONLNd#
(
 
4
))T). °dONLNd'
8ä
Dê(
Aä
P°dONLNd(
8ê
Dñ)
B.
°dONLNd*
8Ã
DŸ)<An†°dONLNd,
8⁄
D
a) edition opener parameter bloc†°dONLNdJ
8
b
D
j)àk.¿°dONLNdL
8
j
D
l)
 .°dONLNdN
Hä
TÆ(
Qäroutin°dONLNdT
HÆ
T¥)$
e.
°dONLNdV
HÃ
T”)
A∫†°dONLNdW
H”
T€) p<¿°dONLNdY
H‹
T
M)    ointer to an edition openeÄ°dONLNds
H
N
T
|)rr function.
°dONLNd
nH
wÅ(
uHDESCRIPTION
°dONLNdã
{ä
á+BXThe Edition Manager calls an edition opener function whenever it needs to open or close °dONLNd„
àä
î*Wan edition. The Edition Manager passes an edition opener parameter block as one of the °dONLNd:
ïä
°
ˇ*Sparameters to an edition opener function. The edition opener parameter block is defiÀ °dONLNdé
ï
ˇ
°(
û
ˇned °dONLNdí
¢ä
Ƶ(
´äby this str-‡°dONLNdù
¢∂
ÆÕ),uctur≥¿°dONLNd¢
¢Õ
Æ‘)e:.°dONLNd•
πä
≈
D(
¬äTYPE EditionOpenerParamBlock = °dONLNdΔ
«ú
”¿+RECORD°dONLNdœ
’Æ
·Ã+info:°dONLNdŸ
’

·
t)ZEditionInfoRecord;°dONLNdÚ
’
Ü
·)~{edition container to }°dONLNd
„
Ü
Ô
¯*{ be subscribed to}°dONLNd.
ÒÆ
˝‰(
˙Æ    sectionH:°dONLNd<
Ò

˝
\)ZSectionHandle;°dONLNdQ
Ò
Ü
˝
‡)~{publisher or }°dONLNdo
ˇ
Ü
⁄*{ subscriber }°dONLNdå
Ü
Ú*{ requesting open}°dONLNd°Æ'‰($Æ    document:°dONLNdØ
'
D)Z
FSSpecPtr;°dONLNd¿
Ü'
Ï)~{document passed}°dONLNd‘)Æ5Í(2Æ
fdCreator:°dONLNd„)
5
2)ZOSType;°dONLNdÒ)
Ü5)~{Finder creator type}°dONLNd    7ÆC‰(@Æ    ioRefNum:°dONLNd7
C
8)ZLongInt;°dONLNd&7
ÜC
Ú)~{reference number}°dONLNd;EÆQÿ(NÆioProc:°dONLNdGE
Q
h)ZFormatIOProcPtr;°dONLNd^E
ÜQ
Ú)~{routine to read }°dONLNdS
Ü_
¬*
{ formats}°dONLNdåaÆmfi(jÆsuccess:°dONLNdôa
m
8)ZBoolean;°dONLNd®a
Üm)~{reading or writing }°dONLNdÃo
Ü{
Ï*{ was successful}°dONLNd‡}Æâˆ(ÜÆformatsMask:°dONLNdÒ}
â
J)ZSignedByte;°dONLNd}
Üâ
)~{formats required to }°dONLNd(ã
Üó
Œ*{ subscribe}°dONLNd6ôú•¥(¢úEND;ˇÿ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-104    )BEdition Manager Reference4^*¿
¯
°dONLNd\lhr(el
Tµ¿°dONLNd
\qh“)o override the standarRÄ°dONLNd\”hfl)bd r≥@°dONLNd\flh
°)+eading and writing functions, you should cr'@°dONLNdE\
¢h
◊)√eate an I/O °dONLNdQilu
@(rl0function that contains the following parameters.,
Courier.°dONLNdÇÇlé
V*'FUNCTION MyIO (selector: FormatIOVerb; °dONLNdØêΔú
b+ZVAR PB: FormatIOParamBlock°dONLNd…ê
bú
n)ú):°dONLNdÀê
nú
ò) OSErr;°dONLNd”®l¥è(±lSet the °dONLNd€®è¥ø)#selector°dONLNd„®ø¥
~)0+ parameter to one of the format I/O verbs (°dONLNd
®
~¥
¿)øioHasFormat°dONLNd
®
¿¥
≈)B, ˇ˛ˇ˛°dONLNd
µl¡¥(ælioReadFormatˇˇ™™°dONLNd
'µ¥¡∏)H, ˇ˛ˇ˛*™°dONLNd
)µπ¡˚)ioNewFormatˇˇ™™*™°dONLNd
4µ˚¡ˇ)B, ˇ˛ˇ˛’T°dONLNd
6µˇ¡
M)ioWriteFormatˇˇ™™’T°dONLNd
Cµ
M¡
i)N). The ˇ˛ˇ˛*®°dONLNd
Jµ
j¡
v)PBˇˇ™™*®°dONLNd
Lµ
v¡
¯) parameter contains a format .
°dONLNd
i¬lŒŒ(ÀlI/O parameter block rÑÄ°dONLNd
~¬ŒŒ‡)becor¯‡°dONLNd
Ǭ‡ŒÊ)
d†°dONLNd
ɬÁŒÈ)
.
°dONLNd
ÖË*ÒQ(Ô*SEE ALSO
°dONLNd
éˆl
}+BSee ”°dONLNd
íˆ}

R).“Calling an Edition Opener” beginning on page q‡°dONLNd
¿ˆ
S

e)÷2-64≈¿°dONLNd
ƒˆ
e

›) for additional information.


2*
;
¯4
3*
:
¯ 
4*
4
˛

ˇ·ˇ‚7^
°dONLNd
‚
%*
32(
/*
C)¿°dONLNd
„
%3
3é)    allFormatIOProcˇˇˇˇˇˇ(
/
Ú
2
.°dONLNd
Ù
Dl
Pë(
MlUse the °dONLNd
¸
Dë
PÒ)%CallFormatIOProc°dONLNd
DÒ
P
e)` function to call a format I°dONLNd(
D
e
P
õ)t/O function.°dONLNd5
]l
i
û(
fl3FUNCTION CallFormatIOProc (selector: FormatIOVerb; °dONLNdr
k

w
∞+¢VAR PB:FormatIOParamBlock; °dONLNdó
y

Ö
û*routine: FormatIOProcPtr°dONLNdØ
y
û
Ö
™)ê):°dONLNd±
y
™
Ö
‘) OSErr;°dONLNdπ
ël
ùñ(
ölselecto°dONLNd¿
ëñ
ùú)*
r°dONLNd¬
ëÆ
ù∂)
AÛ`°dONLNd√
ëµ
ùª) fÛ`°dONLNd≈
ëª
ù˙)ormat I/O verÛ`°dONLNd“
ë˙
ù
)?b (Û`°dONLNd’
ë

ù
G)ioHasFormatÛ`°dONLNd‡
ë
G
ù
L)B, Û`°dONLNd‚
ë
L
ù
î)ioReadFormatÛ`°dONLNdÓ
ë
î
ù
ô)H, Û`°dONLNd
ë
ô
ù
€)ioNewFormatÛ`°dONLNd˚
ë
€
ù
‡)B, °dONLNd˝
ùÆ
©¸(
¶ÆioWriteFormat°dONLNd

ù¸
©
)N). °dONLNd
≠l
πr(
∂l
P°dONLNd
≠r
πx)
B.
°dONLNd
≠Æ
πµ)<
A∫†°dONLNd
≠µ
π∫) féÄ°dONLNd
≠ª
π
:)ormat I/O parameter block rëÄ°dONLNd/
≠
:
π
L)ecor‡°dONLNd3
≠
M
π
U)d..°dONLNd6
Ωl
…ê(
Δlroutin°dONLNd<
Ωê
…ñ)$
e.
°dONLNd>
ΩÆ
…µ)
A∫†°dONLNd?
Ωµ
…Ω) p<¿°dONLNdA
Ωæ
…
)    ointer to a format I/b†°dONLNdV
Ω

…
K)YO function. 
°dONLNdc
„*
Ïc(
Í*DESCRIPTION
°dONLNdo
l
¸
®+BFThe Edition Manager calls a format I/O function whenever it needs to r\°dONLNdµ

®
¸
¡(
˘
®ead fr⁄@°dONLNdª

¡
¸
˜)om or write °dONLNd«
˝l    
Ë(lUto an edition. The Edition Manager passes a format I/O parameter block as one of the °dONLNd
lÒ*parameters to a format I/O pri°dONLNd9
Ò
)Öocedur@°dONLNd?


Δ)(e. The format I/O parameter block is defi/°dONLNdh

Δ
Ê)∂ned by °dONLNdol#ä( lthis stró °dONLNdwä#°)uctur°dONLNd|¢#©)e:.°dONLNd.l:
(7lTYPE FormatIOParamBlock = °dONLNdõ<~H¢+RECORD°dONLNd§JêVΔ+    ioRefNum:°dONLNd≤JÍV
)ZLongInt;°dONLNdøJ
DV
∞)Z{reference number}°dONLNd‘Xêd∫(aêformat:°dONLNd‡XÍd
,)ZFormatType;°dONLNdX
Dd
¬)Z{edition format type}°dONLNdfêrÿ(oêformatIndex:°dONLNdfÍr
)ZLongInt;ˇ˝ˇ¸°dONLNd&f
Dr
˜)Z{opener-specific enumeration } °dONLNdRt
DÄ
í*{ of formats}°dONLNdbÇêé∫(ãêoffset:°dONLNdnÇÍé
)ZLongInt;°dONLNd{Ç
Dé
º)Z{offset into format}°dONLNdíêêú¿(ôêbuffPtr:°dONLNdüêÍú
)ZPtr;°dONLNd®ê
Dú
∞)Z{data starts here}°dONLNdΩûꙿ(ßêbuffLen:°dONLNd ûÍ™
)ZLongInt;°dONLNd◊û
D™
§)Z{length of data}°dONLNdȨ~∏ê(µ~END°dONLNdϨê∏ñ)
;ˇ%¬@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äEdition Manager Reference

, (‡
ˇ2-105
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\Heo(cHSEE ALSO
°dONLNd    jävõ+BSee ”°dONLNdjõv
Ñ)2“Calling a Format I/O Function” beginning on page ˙Ä°dONLNd?j
Ñv
ñ)È2-68N`°dONLNdCj
óv) for additional information.

¢H™4£H™ •H•

ˇ·ˇ‚7^°dONLNdaíH¢∞(ûHApplication-Defi߇°dONLNdqí∞¢

)hned Routinesˇˇˇˇˇˇ(û
2
°dONLNd™ä∂ê(≥ä
Y@Ä°dONLNdÄ™ê∂Ò)our application can prÔ`°dONLNdñ™Ò∂
Â)a7ovide an edition opener function, format I/O function, °dONLNdÕ∑ä√
Æ(¿ä>expandable dialog hook function, and expandable modal-dialog fi熰dONLNd
∑
Æ√(¿
Ælter function. For the °dONLNd
#ĊЍ(͊
rE°dONLNd
$ƒé–
…)Houtine declarations of the edition opener and format I/O functions, see @@°dONLNd
lƒ
 –    (Õ
 “Reading and °dONLNd
yъݔ(ڊ
W¬†°dONLNd
z—ì›
X)    ,riting Non-Edition Files” beginning on page `†°dONLNd
¶—
Y›
p)Δ2-102¥Ä°dONLNd
´—
p›
ö). For the rN °dONLNd
∂—
õ›)+outine declarations of the °dONLNd
—fiäÍ
É(Áä4expandable dialog hook and expandable modal-dialog fi`°dONLNdfi
ÑÍ
‰)˙lter functions, see the .°dONLNdÎä˜ (Ùädescription of ,
Courier°dONLNd-Î ˜
N)@NewSubscriberExpDialog°dONLNdCÎ
N˜
S)Ñ, °dONLNdEÎ
S˜
—)NewPublisherExpDialog°dONLNdZÎ
—˜
È)~, and °dONLNd`¯ä

(

äSectionOptionsExpDialog°dONLNdw¯


O)ä beginning on °dONLNdÖ¯
O

g);page °dONLNdä¯
g

z)2-96°dONLNdé¯
z

). ˇR@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-106    )BSummary of the Edition Manager4^*¿
¯

^*x
¯4^*x
¯

à*ê
¯4â*ê
¯ ä*ä
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNdu*à
(É*Summary of the Edition ManagerˇˇˇˇˇˇV˛(É

2

¡*»
¯4¡*»
¯ ¬*¬
¯

ˇ·ˇ‚7^°dONLNd!≤*¡ì(Ω*Pascal Summaryˇˇˇˇˇˇ∑†(Ω

2

È*Ô
¯4Í*Ó
¯ Î*Î
¯

ˇ·ˇ‚7^°dONLNd2fi*È[(Ê*    Constantsˇˇˇˇˇˇa‡(Ê
Ú
2,
Courier
.°dONLNd=˘*
H(
*CONST°dONLNdF
<
ú+{resource types}°dONLNdX
<
!Ñ*rSectionType°dONLNdn

!
&)¥    = 'sect';°dONLNd{

8
!
º)H{resource type for a }°dONLNd°
#
8
/
n*    { section°dONLNd™
#
n
/
t)6
}°dONLNd≠
1<
=ñ(
:<{section types}°dONLNdæ
?<
KÑ*stSubscriber°dONLNd‘
?
K
)¥= $01;°dONLNdfi
?
8
K
Œ)H{subscriber section type}°dONLNd˘
M<
Y~(
V<stPublisher°dONLNd

M
Y
)¥= $0A;°dONLNd

M
8
Y
¬)H{publisher section type°dONLNd
/
M
¬
Y
Œ)ä} °dONLNd
3
[<
gê(
d<{update modes}°dONLNd
C
i<
uÑ*sumAutomatic°dONLNd
Y
i
u
)¥= 0;°dONLNd
a
i
8
u
⁄)H{subscriber receives new } °dONLNd
å
w
8
É
Œ*{ editions automatically}°dONLNd
ß
Ö<
ër(
é<    sumManual°dONLNd
∫
Ö
ë
)¥= 1;°dONLNd
¬
Ö
8
ë
⁄)H{subscriber receives new } °dONLNd
Ì
ì
8
ü
∞*{ editions manually}°dONLNd
°<
≠r(
™<    pumOnSave°dONLNd
°
≠
)¥= 0;°dONLNd
°
8
≠
¬)H{publisher sends new } °dONLNdE
Ø
8
ª
™*{ editions on save}°dONLNdZ
Ω<
…r(
Δ<    pumManual°dONLNdm
Ω
…
)¥= 1;°dONLNdu
Ω
8
…
⁄)H{publisher does not send } °dONLNd†
À
8
◊
⁄*{ new editions until user }°dONLNdÀ
Ÿ
8
Â
n*    { request°dONLNd‘
Ÿ
n
Â
t)6
}°dONLNd◊
Á<
ÛB(
<
{°dONLNdÿ
ÁB
Û
)!edition container subpart number}°dONLNd˚
ı<
ä(
˛<kPartsNotUsed°dONLNd
ı

)¥= 0;°dONLNd
ı
8

⁄)H{edition is the whole file}°dONLNd7<®(<kPartNumberUnknown°dONLNdS
)¥= -1;°dONLNd\
8
Œ)H{not used in version 7.0}°dONLNdu
Œ
‘)ñ
 °dONLNdy<+B((<
{°dONLNdzB+ê)preview size}°dONLNdâ-<9ä(6<kPreviewWidth°dONLNd†-9
)¥= 120;°dONLNd™-
89
ò)H{preview width} °dONLNdº;<Gê(D<kPreviewHeight°dONLNd‘;G
)¥= 120;°dONLNdfi;
8G
í)H{preview height°dONLNdÌ;
íG
ò)Z
}°dONLNdÒW<c¢(`<{special formats}°dONLNde<qÃ*kPublisherDocAliasFormat°dONLNd&eq
&)¥    = 'alis';°dONLNd3e
8q
Œ)H{alias record from the } °dONLNd\s
8
»*{ edition to publisher} °dONLNdvÅ<çê(ä<kPreviewFormat°dONLNdéÅç
&)¥    = 'prvw';°dONLNdõÅ
8ç
Œ)H{'PICT' thumbnail sketch}°dONLNd∂è<õ¢(ò<kFormatListFormat°dONLNd—èõ
&)¥    = 'fmts';°dONLNdfiè
8õ
»)H{list of all available }°dONLNdù
8©
Œ*{ formats and their sizes°dONLNdù
Ω
‘)ñ
}ˇ/®@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äSummary of the Edition Manager

, (‡
ˇ2-107
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\Zhÿ(eZ{bits for formatMask}°dONLNdjZv¥*kPICTformatMask°dONLNd0j
v
&)¥= 1;°dONLNd8j
Vv
º)H{graphics format}°dONLNdKxZÑ¥(ÅZkTEXTformatMask°dONLNddx
Ñ
&)¥= 2;°dONLNdlx
VÑ
§)H{text format}°dONLNd{ÜZíÆ(èZksndFormatMask°dONLNdìÜ
í
&)¥= 4;°dONLNdõÜ
Ví
™)H{sound format}°dONLNd¨¢ZÆ
(´Z {Finder types for edition files}°dONLNdŒ∞Zº“*kPICTEditionFileType°dONLNdÏ∞
º
D)¥    = 'edtp';°dONLNd˘∞
Vº
»)H{contains 'PICT', }°dONLNd
æZ “(«ZkTEXTEditionFileType°dONLNd
,æ
 
D)¥    = 'edtt';°dONLNd
9æ
V 
∞)H{ 'TEXT', and }°dONLNd
JÃZÿÃ(’ZksndEditionFileType°dONLNd
gÃ
ÿ
D)¥    = 'edts';°dONLNd
tÃ
Vÿ
Œ)H{ 'snd ' file types}°dONLNd
ä⁄Zʉ(„ZkUnknownEditionFileType°dONLNd
´⁄
Ê
D)¥    = 'edtu';°dONLNd
∏⁄
VÊ
¬)H{unknown file type°dONLNd
 ⁄
¬Ê
»)l
}°dONLNd
ÕËZÙ`(ÒZ
{°dONLNd
ŒË`Ù¥)miscellaneous}°dONLNd
fiˆZ
“(ˇZkFormatLengthUnknown°dONLNd
¸ˆ


D)¥    = -1;    °dONLNd    ˆ
V

Ú)H{length of format unknown}°dONLNd&
Z

∂(
Z:{message IDs for Apple events sent by the Edition Manager}°dONLNdb
 Z
,“*sectionEventMsgClass°dONLNdÄ
 

,
D)¥    = 'sect';°dONLNdç
 
V
,
¯)H{Apple events sent by the }°dONLNd∏
.
V
:
¬*{ Edition Manager}°dONLNdÃ
<Z
H∫(
EZsectionReadMsgID°dONLNdÊ
<

H
D)¥    = 'read';°dONLNdÛ
<
V
H
‘)H{Section Read events}°dONLNd

JZ
V¿(
SZsectionWriteMsgID°dONLNd%
J

V
D)¥    = 'writ';°dONLNd2
J
V
V
⁄)H{Section Write events}°dONLNdJ
XZ
dΔ(
aZsectionScrollMsgID°dONLNdf
X

d
D)¥    = 'scrl';°dONLNds
X
V
d
‡)H{Section Scroll events}°dONLNdå
fZ
rΔ(
oZsectionCancelMsgID°dONLNd®
f

r
D)¥    = 'cncl';°dONLNdµ
f
V
r
‡)H{Section Cancel events}°dONLNdœ
ÇZ
é
å(
ãZ3{refCon field when displaying stacked dialog boxes}°dONLNd
êZ
úΔ*sfMainDialogRefCon°dONLNd 
ê

ú
D)¥    = 'stdf';°dONLNd-
ê
V
ú
Œ)H{new publisher and }°dONLNdQ
û
V
™
º*{ new subscriber}°dONLNdd
¨Z
∏‰(
µZsfNewFolderDialogRefCon°dONLNdÖ
¨

∏
D)¥    = 'nfdr';°dONLNdí
¨
V
∏
û)H{new folder}°dONLNd†
∫Z
Δÿ(
√ZsfReplaceDialogRefCon°dONLNdø
∫

Δ
D)¥    = 'rplc';°dONLNdÃ
∫
V
Δ
∂)H{replace dialog}°dONLNdfi
»Z
‘fi(
—ZsfStatWarnDialogRefCon°dONLNd˛
»

‘
D)¥    = 'stat';°dONLNd
»
V
‘
∂)H{warning dialog}°dONLNd
÷Z
‚Ã(
flZsfErrorDialogRefCon°dONLNd:
÷

‚
D)¥    = 'err ';°dONLNdG
÷
V
‚
™)H{error dialog}°dONLNdW
‰Z
ÿ(
ÌZemOptionsDialogRefCon°dONLNdv
‰


D)¥    = 'optn';°dONLNdÉ
‰
V

∂)H{options dialog}°dONLNdï
ÚZ
˛¸(
˚ZemCancelSectionDialogRefCon°dONLNd∫
Ú

˛
D)¥    = 'cncl';°dONLNd«
Ú
V
˛
∂)H{cancel section}°dONLNdŸZÍ(    ZemGotoPubErrDialogRefCon°dONLNd˚

D)¥    = 'gerr';°dONLNd
V
¬)H{locate publisher}°dONLNdZ(
&(%Z"{pseudo-item hits for dialogHooks}°dONLNdA*Z6Ã*emHookRedrawPreview°dONLNd^*
6
2)¥= 150;°dONLNdh*
V6
⁄)H{for NewPublisher or }°dONLNdé8
VD
Ê*{ NewSubscriber dialogs}°dONLNd®FZRÃ(OZemHookCancelSection°dONLNd≈F
R
2)¥= 160;°dONLNdœF
VR
¯)H{for SectionOptions dialog}°dONLNdÏTZ`Ã(]ZemHookGoToPublisher°dONLNd    T
`
2)¥= 161;°dONLNdT
V`
¯)H{for SectionOptions dialog}°dONLNd0bZnÃ(kZemHookGetEditionNow°dONLNdMb
n
2)¥= 162;°dONLNdWb
Vn
¯)H{for SectionOptions dialog}°dONLNdtpZ|“(yZemHookSendEditionNow°dONLNdíp
|
2)¥= 162;°dONLNdúp
V|
¯)H{for SectionOptions dialog}°dONLNdπ~Zäfi(áZemHookManualUpdateMode°dONLNdŸ~
ä
2)¥= 163;°dONLNd„~
Vä
¯)H{for SectionOptions dialog}°dONLNdåZò“(ïZemHookAutoUpdateMode°dONLNdå
ò
2)¥= 164;°dONLNd(å
Vò
¯)H{for SectionOptions dialog}ˇ–@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-108    )BSummary of the Edition Manager4^*¿
¯

h*n
¯4i*m
¯ j*j
¯

ˇ·ˇ‚7^°dONLNd]*hD(e*Data òp°dONLNd]DhJ)
Tµ‡°dONLNd]Jha)ypesˇˇˇˇˇˇa‡(e
Ú
2,
Courier
.°dONLNdx*Ñ~(Å*TYPE TimeStamp°dONLNd%xÑ
,)Δ
= LongInt;°dONLNd4x
JÑ
¬)Z{seconds since 1904}°dONLNdJÜ<íê(è<EditionRefNum °dONLNdbÜí
,)¥
= Handle; °dONLNdqÜ
Jí
⁄)Z{for use in Edition I/O}°dONLNdãî<†~(ù<UpdateMode °dONLNd†î†
,)¥
= Integer;°dONLNdØî
J†
™)Z{sumAutomatic, }°dONLNd–¢
JÆ
§*{ sumManual, } °dONLNd∞
Jº
‘*{ pumOnSave, pumManual}°dONLNd
    æ< Ñ(«<SectionType °dONLNd
æ 
>)¥= SignedByte;°dONLNd
1æ
J 
∂)Z{stSubscriber or }°dONLNd
TÃ
Jÿ
§*{ stPublisher} °dONLNd
e⁄<Ê~(„<FormatType °dONLNd
z⁄Ê
§)¥= PACKED ARRAY[1..4] OF CHAR; °dONLNd
©Ë
JÙ
Ï+Z{similar to ResType used } °dONLNd
’ˆ
J

‘*{ by the Scrap Manager}°dONLNd
Ô
<
ä(
<SectionHandle°dONLNd


D)¥= ^SectionPtr;°dONLNd
 <
,x(
)<
SectionPtr°dONLNd*
 
,
V)¥= ^SectionRecord;°dONLNd=
.<
:ê(
7<SectionRecord °dONLNdU
.
:¸)¥= °dONLNdY
<<
H`(
E<RECORD°dONLNdb
JN
V~+version:°dONLNds
J
V
2)¢SignedByte;°dONLNdÉ
J
J
V
‡)Z{always 1 in version 7.0}°dONLNdü
XN
dl(
aNkind:°dONLNd≠
X
d
8)¢SectionType;°dONLNdæ
X
J
d
‡)Z{publisher or subscriber}°dONLNd⁄
fN
rl(
oNmode:°dONLNdË
f
r
2)¢UpdateMode;°dONLNd¯
f
J
r
»)Z{automatic or manual}°dONLNd
tN
Äx(
}NmdDate:°dONLNd 
t
Ä
,)¢
TimeStamp;°dONLNd/
t
J
Ä
⁄)Z{last change to section}°dONLNdJ
ÇN
éä(
ãN
sectionID:°dONLNd]
Ç
é
 )¢LongInt;°dONLNdj
Ç
J
é
⁄)Z{application-specific, }°dONLNdì
ê
J
ú
Œ*{ unique per document}°dONLNd¨
ûN
™x(
ßNrefCon:°dONLNdº
û
™
 )¢LongInt;°dONLNd…
û
J
™
Œ)Z{application-specific}°dONLNd‚
¨N
∏r(
µNalias:°dONLNdÒ
¨
∏
8)¢AliasHandle;°dONLNd
¨
J
∏
⁄)Z{handle to alias record}°dONLNd
»N
‘
§(
—N9{The following fields are private and are set up by the }°dONLNdZ
÷N
‚ˆ*{ RegisterSection function.}°dONLNdz
ÚN
˛~*subPart:°dONLNdã
Ú
˛
 )¢LongInt;°dONLNdò
Ú
J
˛
Ä)Z    {private}°dONLNd§Nñ(    NnextSection:°dONLNdπ
D)¢SectionHandle;°dONLNdÃ
J
Ä)Z    {private}°dONLNdÿNú(NcontrolBlock:°dONLNdÓ
)¢Handle;°dONLNd˙
J
Ä)Z    {private}°dONLNdN(x(%NrefNum:°dONLNd(
D)¢EditionRefNum;°dONLNd)
J(
Ä)Z    {private}°dONLNd4*<6T(3<END;°dONLNd:C<O
V*/EditionContainerSpecPtr =^EditionContainerSpec;°dONLNdkQ<]¥*EditionContainerSpec°dONLNdQ¥]¿)x =°dONLNdÉ_<k`(h<RECORD°dONLNdåmNy~+theFile:°dONLNdùmy
)¢FSSpec;°dONLNd©m
Jy
Ï)Z{file containing edition } °dONLNd’{
Já
t*{ data}°dONLNdflâNï®(íNtheFileScript: °dONLNd˜âï
2)¢ScriptCode;°dONLNdâ
Jï
‡)Z{script code of filename}°dONLNd#óN£~(†NthePart:°dONLNd4ó£
 )¢LongInt;°dONLNdAó
J£
‘)Z{which part of file, } °dONLNdi•
J±
‘*{ always kPartsNotUsed}ˇ*∂@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äSummary of the Edition Manager

, (‡
ˇ2-109
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\lh¥(elthePartName:°dONLNd\
h
2)¢Str31;°dONLNd \
hh
§)Z
{reserved}°dONLNd-jlvΔ(slthePartScript: °dONLNdEj
v
J)¢
ScriptCode°dONLNdOj
Jv
P)<
;°dONLNdUj
hv
§)
{reserved}°dONLNdaxZÑr(ÅZEND;°dONLNdgëZù
 *!FormatsAvailable = ARRAY[0..0] OF°dONLNdäüZ´~*RECORD°dONLNdì≠lπú+theType:°dONLNd§≠
π
P)¢FormatType;°dONLNd¥≠
hπ
Ê)Z{format type for an }°dONLNd⁄ª
h«
§*
{ edition}°dONLNdÁ…l’®(“l
theLength:°dONLNd˙…
’
>)¢LongInt;°dONLNd
…
h’
)Z{length of edition format }°dONLNd
3◊
h„
í*{ type}°dONLNd
<ÂZÒr(ÓZEND;°dONLNd
B˛Z

“*EditionInfoRecord = °dONLNd
X
Z
~*RECORD°dONLNd
a
l
&ñ+crDate:°dONLNd
q


&
J)¢
TimeStamp;°dONLNd
Ä

h
&
˛)Z{date edition container }°dONLNd
™
(
h
4
º*{ was created}°dONLNd
ª
6l
Bñ(
?lmdDate:°dONLNd
À
6

B
J)¢
TimeStamp;°dONLNd
⁄
6
h
B
Ê)Z{date of last change}°dONLNd
Ú
Dl
P®(
Ml
fdCreator:°dONLNd
D

P
8)¢OSType;°dONLNd
D
h
P
º)Z{file creator}°dONLNd"
Rl
^ñ(
[lfdType:°dONLNd2
R

^
8)¢OSType;°dONLNd>
R
h
^
™)Z{file type}°dONLNdL
`l
l®(
il
container:°dONLNd_
`

l
å)¢EditionContainerSpec;°dONLNdÖ
n
h
z
∂+Z{the edition}°dONLNdî
|Z
àr(
ÖZEND;°dONLNdö
ïZ
°“*NewPublisherReply = °dONLNd∞
£Z
Ø~*RECORD°dONLNdπ
±l
Ω¢+    canceled:°dONLNd»
±ÿ
Ω
)lBoolean;°dONLNd◊
±
V
Ω
¯)~{user canceled dialog box} °dONLNdı
øl
À®(
»l
replacing:°dONLNd
øÿ
À
)lBoolean;°dONLNd
ø
V
À
‡)~{user chose existing } °dONLNd;
Õ
V
Ÿ
Ú*{ filename for an edition}°dONLNdX
€l
Áú(
‰lusePart:°dONLNdf
€ÿ
Á
)lBoolean;°dONLNdu
€
V
Á)~{always FALSE in version 7.0}°dONLNdï
Èl
ıú(
Úlpreview:°dONLNd£
Èÿ
ı
)lHandle;°dONLNd±
È
V
ı
¯)~{handle to 'prvw', 'PICT',}°dONLNd‹
˜
V
Ï*{ 'TEXT', or 'snd ' data}°dONLNd¯l¿(lpreviewFormat:°dONLNdÿ
)lFormatType;°dONLNd
V
º)~{type of preview}°dONLNd2l®(l
container:°dONLNdBÿ
V)lEditionContainerSpec;°dONLNdg!
V-
∂+~{edition chosen}°dONLNdy/Z;r(8ZEND;°dONLNdHZT“*NewSubscriberReply =°dONLNdïVZb~*RECORD°dONLNdûdlp¢+    canceled:°dONLNd≠dÿp
)lBoolean;°dONLNdºd
Vp
Ú)~{user canceled dialog box}°dONLNdŸrl~¥({lformatsMask:°dONLNdÎrÿ~
)lSignedByte;°dONLNd˝r
V~
¬)~{formats required}°dONLNdÄlåÆ(âlcontainer: °dONLNd#Äÿå
V)lEditionContainerSpec;°dONLNdHé
Vö
¬+~{edition selected}°dONLNd\úZ®r(•ZEND;ˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-110    )BSummary of the Edition Manager4^*¿
¯,
Courier
.°dONLNd\<h∫(e<SectionOptionsReply =°dONLNdj<v`*RECORD°dONLNd xNÑÑ+    canceled:°dONLNd/x∫ÑÍ)lBoolean;°dONLNd>x
8Ñ
‘)~{user canceled dialog box}°dONLNd[ÜNíÑ(èN    changed: °dONLNdjÜ∫íÍ)lBoolean;°dONLNdyÜ
8í
º)~{changed the section }°dONLNdüî
8†
n*    { record}°dONLNd´¢NÆÑ(´N    sectionH:°dONLNd∫¢∫Æ
)lSectionHandle;°dONLNdœ¢
8Æ
‘)~{handle to the specified }°dONLNd˘∞
8º
û*{ section record}°dONLNd
æN x(«Naction:°dONLNd
æ∫ Í)lResType;°dONLNd
)æ
8 
å)~{action codes}°dONLNd
9Ã<ÿT(’<END;°dONLNd
?Â<Ò¢*EditionOpenerVerb°dONLNd
Q¢Ò
ò)f)= (eoOpen, eoClose, eoOpenNew, eoCloseNew°dONLNd
zÂ
òÒ
û)ˆ
,°dONLNd
ÑÛ∫ˇ
 (¸∫eoCanSubscribe); °dONLNd
ó

<
ÿ(

<EditionOpenerParamBlock = °dONLNd
≥
<
`*RECORD°dONLNd
º
N
)l+info:°dONLNd
«
∫
)
&)lEditionInfoRecord;°dONLNd
‡

8
)
¬)~{edition container to }°dONLNd
+
8
7
™*{ be subscribed to}°dONLNd
9N
EÑ(
BN    sectionH:°dONLNd,
9∫
E
)lSectionHandle;°dONLNdA
9
8
E
»)~{publisher or subscriber°dONLNdY
9
»
E
Œ)ê
 °dONLNdZ
9
Œ
E
‘)
}°dONLNdk
G
8
S
§(
P
8{ requesting open}°dONLNdÄ
UN
aÑ(
^N    document:°dONLNdè
U∫
aˆ)l
FSSpecPtr;°dONLNd†
U
8
a
û)~{document passed}°dONLNd¥
cN
oä(
lN
fdCreator:°dONLNdƒ
c∫
o‰)lOSType;°dONLNd“
c
8
o
∂)~{Finder creator type}°dONLNdÍ
qN
}Ñ(
zN    ioRefNum:°dONLNd˘
q∫
}Í)lLongInt;°dONLNd
q
8
}
§)~{reference number}°dONLNd
N
ãx(
àNioProc:°dONLNd*
∫
ã
)lFormatIOProcPtr;°dONLNdA

8
ã
Œ)~{routine to read formats}°dONLNd]
çN
ô~(
ñNsuccess:°dONLNdk
ç∫
ôÍ)lBoolean;°dONLNdz
ç
8
ô
Œ)~{reading or writing was }°dONLNd£
õ
8
ß
Ü*{ successful}°dONLNd≥
©N
µñ(
≤NformatsMask:°dONLNd≈
©∫
µ¸)lSignedByte;°dONLNd◊
©
8
µ
º)~{formats required to }°dONLNd˝
∑
8
√
Ä*{ subscribe}°dONLNd
≈<
—T(
Œ<END;°dONLNd
fi<
ÍÑ*FormatIOVerb°dONLNd
ބ
Íä)H
 °dONLNd
fiä
Í
Ä))= (ioHasFormat, ioReadFormat, ioNewFormat°dONLNdH
fi
Ä
Í
í)ˆ, i°dONLNdK
fi
í
Í
Ê)oWriteFormat);°dONLNd[
Ï<
¯∫(
ı<FormatIOParamBlock = °dONLNdr
˙<`*RECORD°dONLNd{NÑ+    ioRefNum:°dONLNdä∫Í)lLongInt;°dONLNdô
8
§)~{reference number}°dONLNdÆN"x(Nformat:°dONLNdª∫"¸)lFormatType;°dONLNdÕ
8"
∂)~{edition format type}°dONLNdÂ$N0ñ(-NformatIndex:°dONLNd˜$∫0Í)lLongInt;°dONLNd$
80
Ï)~{opener-specific enumeration }°dONLNd42
8>
Ü*{ of formats}°dONLNdD@NLx(INoffset:°dONLNdQ@∫LÍ)lLongInt;°dONLNd`@
8L
∞)~{offset into format}°dONLNdwNNZ~(WNbuffPtr:°dONLNdÖN∫Z“)lPtr;°dONLNdêN
8Z
§)~{data starts here}°dONLNd•\Nh~(eNbuffLen:°dONLNd≥\∫hÍ)lLongInt;°dONLNd¬\
8h
ò)~{length of data}°dONLNd”j*vB(s*END;ˇ*æ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äSummary of the Edition Manager

, (‡
ˇ2-111
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

hHn4iHm jHj

ˇ·ˇ‚7^°dONLNd]HhΔ(eHEdition Manager Routinesˇˇˇˇˇˇa‡(e
2
°dONLNd~HäÍ(áH Initializing the Edition Manager,
Courier
.°dONLNd;ëHùfi*FUNCTION InitEditionPack °dONLNdUëÚù
")™: OSErr;
.
°dONLNd^ØHªˆ(∏H"Creating and Registering a Section
.°dONLNdÅ¡HÕ∫*FUNCTION NewSection°dONLNdï¡ÚÕ
æ)™"(container: EditionContainerSpec; °dONLNd∑Œ¯⁄+/sectionDocument: FSSpecPtr; kind: SectionType; °dONLNdÊ€¯Á*-sectionID: LongInt; initialMode: UpdateMode; °dONLNd
˯Ù
ö*VAR sectionH: SectionHandle°dONLNd
.Ë
öÙ
¶)¢):°dONLNd
0Ë
¶Ù
–) OSErr;°dONLNd
8¯H
ÿ(

HFUNCTION RegisterSection°dONLNd
Q¯Ú

à)™(sectionDocument: FSSpec;°dONLNd
j¯
à

é)ñ
 °dONLNd
l
¯
˛(
¯
s°dONLNd
m
˛

à)ectionH: SectionHandle;°dONLNd
Ñ

à

é)ä
 °dONLNd
Ü
¯
˛(
¯
V°dONLNd
á
˛

†)AR aliasWasUpdated: Boolean°dONLNd
¢

†

¶)¢
)°dONLNd
§
¯
+

(
(¯: O°dONLNd
ß



+
()SErr;°dONLNd
≠
/H
;‰(
8HFUNCTION UnRegisterSection°dONLNd
»
/Ú
;
Ç)™(sectionH: SectionHandle°dONLNd
‡
/
Ç
;
é)ê):°dONLNd
‚
/
é
;
∏) OSErr;°dONLNd
Í
?H
K(
HHFUNCTION IsRegisteredSection°dONLNd
LÚ
X
∏+™!(sectionH: SectionHandle): OSErr;°dONLNd)
\H
hfi(
eHFUNCTION AssociateSection°dONLNdC
\Ú
h
é)™(sectionH: SectionHandle; °dONLNd^
i¯
u
¶+newSectionDocument: FSSpecPtr°dONLNd{
i
¶
u
≤)Æ):°dONLNd}
i
≤
u
‹) OSErr;
.
°dONLNdÖ
áH
ì
#(
êH*Creating and Deleting an Edition Container
.°dONLNd∞
öH
¶
*#FUNCTION CreateEditionContainerFile°dONLNd‘
ßÚ
≥
Ë+™)(editionFile: FSSpec; fdCreator: OSType; °dONLNd˝
¥¯
¿
æ+!editionFileNameScript: ScriptCode°dONLNd
¥
æ
¿
 )Δ):°dONLNd 
¥
 
¿
Ù) OSErr;°dONLNd(
ƒH
–
(
ÕH#FUNCTION DeleteEditionContainerFile°dONLNdL
—Ú
›
j+™(editionFile: FSSpec°dONLNd`
—
j
›
v)x):°dONLNdb
—
v
›
†) OSErr;
.
°dONLNdj
ÔH
˚{(
¯H
Setting anÉ¿°dONLNdt
Ô{
˚ö)3d Gett˘ °dONLNdz
Ôö
˚˜)ing a Format Mark
.°dONLNdå
Hˆ(
HFUNCTION SetEditionFormatMark°dONLNd™Ú
¶+™(whichEdition: EditionRefNum; °dONLNd…¯'
é+whichFormat: FormatType; °dONLNd„(¯4
d*setMarkTo: LongInt°dONLNdı(
d4
p)l):°dONLNd˜(
p4
ö) OSErr;°dONLNdˇ8HDˆ(AHFUNCTION GetEditionFormatMark°dONLNdEÚQ
¶+™(whichEdition: EditionRefNum; °dONLNd<R¯^
é+whichFormat: FormatType; °dONLNdV_¯k
à*VAR currentMark: LongInt°dONLNdn_
àk
î)ê):°dONLNdp_
îk
ƒ) OSErr; ˇÊ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-112    )BSummary of the Edition Manager4^*¿
¯
°dONLNd\*h£(e*Reading in Edition Data,
Courier
.°dONLNdo*{¢*FUNCTION OpenEdition°dONLNd-o‘{
¶)™#(subscriberSectionH: SectionHandle;°dONLNdPo
¶{
¨)“
 °dONLNdR|⁄à‡(Ö⁄
V°dONLNdS|‡à
p)AR refNum: EditionRefNum°dONLNdk|
pà
|)ê):°dONLNdm|
|à
¶) OSErr;°dONLNduå*ò¿(ï*FUNCTION EditionHasFormat°dONLNdèå‘ò
à)™(whichEdition: EditionRefNum; °dONLNdÆô⁄•
p+whichFormat: FormatType; °dONLNd»¶⁄≤
R*VAR formatSize: Size°dONLNd‹¶
R≤
^)x):°dONLNdfi¶
^≤
é) OSErr; °dONLNdÁ∂*¬¢(ø*FUNCTION ReadEdition°dONLNd¸∂‘¬
à)™(whichEdition: EditionRefNum; °dONLNd
√⁄œ
‚+,whichFormat: FormatType; buffPtr: UNIV Ptr; °dONLNd
G–⁄‹
@*VAR buffLen: Size°dONLNd
X–
@‹
L)f):°dONLNd
Z–
L‹
v) OSErr;
.
°dONLNd
bÓ*˙5(˜*
WØ∞°dONLNd
cÓ4˙•)
riting out Edition Data
.°dONLNd
{
*
¥(
    *FUNCTION OpenNewEdition°dONLNd
ì
‘

¶)™#(publisherSectionH: SectionHandle; °dONLNd
∑
⁄

L+fdCreator: OSType; °dONLNd
À
⁄
&
∏*%publisherSectionDocument: FSSpecPtr; °dONLNd
Ò
'⁄
3
p*VAR refNum: EditionRefNum°dONLNd

'
p
3
|)ñ):°dONLNd
'
|
3
¶) OSErr;°dONLNd
7*
C®(
@*FUNCTION WriteEdition°dONLNd*
7‘
C
à)™(whichEdition: EditionRefNum; °dONLNdI
D⁄
P
‚+,whichFormat: FormatType; buffPtr: UNIV Ptr; °dONLNdu
Q⁄
]
(*buffLen: Size°dONLNdÇ
Q
(
]
4)N):°dONLNdÑ
Q
4
]
^) OSErr;
.
°dONLNdå
o*
{Ï(
x*%Closing an Edition After Reading or Wûê°dONLNd±
oÏ
{
)¬riting
.°dONLNd∏
Ç*
é®(
ã*FUNCTION CloseEdition°dONLNdŒ
Ç‘
é
à)™(whichEdition: EditionRefNum; °dONLNdÌ
è⁄
õ
L+successful: Boolean°dONLNd
è
L
õ
X)r):°dONLNd
è
X
õ
Ç) OSErr;
.
°dONLNd

≠*
πß(
∂*Displaying Dialog Boxes
.°dONLNd"
ø*
À
*$FUNCTION GetLastEditionContainerUsed°dONLNdG
Ñ
ÿ
¨+™$(VAR container: EditionContainerSpec°dONLNdk
Ã
¨
ÿ
∏)ÿ):°dONLNdm
Ã
∏
ÿ
‚) OSErr;°dONLNdu
‹*
Ë“(
Â*FUNCTION NewSubscriberDialog°dONLNdí
È‘
ı
à+™(VAR reply: NewSubscriberReply°dONLNd∞
È
à
ı
î)¥):°dONLNd≤
È
î
ı
æ) OSErr;°dONLNd∫
˘*Ã(*FUNCTION NewPublisherDialog°dONLNd÷
˘‘
Ç)™(VAR reply: NewPublisherReply°dONLNdÛ
˘
Ç
é)Æ):°dONLNdı
˘
é
∏) OSErr;°dONLNd˝    *ÿ(*FUNCTION SectionOptionsDialog°dONLNd‘"
é+™(VAR reply: SectionOptionsReply°dONLNd:
é"
ö)∫):°dONLNd<
ö"
ƒ) OSErr;°dONLNdD&*2‰(/*FUNCTION NewSubscriberExpDialog°dONLNdd3‘?
Ë+™.(VAR reply: NewSubscriberReply; where: Point; °dONLNdí@⁄L
à+expansionDITLresID: Integer; °dONLNd∞M⁄Y
Ç*dlgHook: ExpDlgHookProcPtr; °dONLNdÕZ⁄f
¨*#filterProc: ExpModalFilterProcPtr; °dONLNdg⁄s
X*yourDataPtr: UNIV Ptr°dONLNdg
Xs
d)~):°dONLNdg
ds
é) OSErr;ˇ,:@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äSummary of the Edition Manager

, (‡
ˇ2-113
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\Hh¸(eHFUNCTION NewPublisherExpDialog°dONLNdiÚu+™-(VAR reply: NewPublisherReply; where: Point; °dONLNdLv¯Ç
¶+expansionDITLresID: Integer; °dONLNdjɯè
†*dlgHook: ExpDlgHookProcPtr; °dONLNdáê¯ú
 *#filterProc: ExpModalFilterProcPtr; °dONLNd™ù¯©
v*yourDataPtr: UNIV Ptr°dONLNdøù
v©
Ç)~):°dONLNd¡ù
Ç©
¨) OSErr;°dONLNd…≠Hπ
(∂H FUNCTION SectionOptionsExpDialog°dONLNdÍ∫ÚΔ+™/(VAR reply: SectionOptionsReply; where: Point; °dONLNd
«¯”
¶+expansionDITLresID: Integer; °dONLNd
7‘¯‡
†*dlgHook: ExpDlgHookProcPtr; °dONLNd
T·¯Ì
 *#filterProc: ExpModalFilterProcPtr; °dONLNd
wÓ¯˙
v*yourDataPtr: UNIV Ptr°dONLNd
åÓ
v˙
Ç)~):°dONLNd
éÓ
Ç˙
¨) OSErr;
.
°dONLNd
ñ
H

K(
H2Locating a Publisher and Edition From a Subscriber
.°dONLNd
…
H
*“*FUNCTION GetEditionInfo°dONLNd
·
Ú
*
é)™(sectionH: SectionHandle; °dONLNd
¸
+¯
7
ƒ+"VAR editionInfo: EditionInfoRecord°dONLNd
+
ƒ
7
–)Ã):°dONLNd 
+
–
7
˙) OSErr;°dONLNd(
;H
Gˆ(
DHFUNCTION GoToPublisherSection°dONLNdF
HÚ
T
≤+™ (container: EditionContainerSpec°dONLNdf
H
≤
T
æ)¿):°dONLNdh
H
æ
T
Ë) OSErr;
.
°dONLNdp
fH
rÕ(
oHEdition Container Formats
.°dONLNdä
yH
ÖÍ*FUNCTION GetStandardFormats°dONLNd¶
yÚ
Ö
æ)™"(container: EditionContainerSpec; °dONLNd…
ܯ
í
≤+VAR previewFormat: FormatType; °dONLNdÈ
ì¯
ü
é*preview, publisherAlias, °dONLNd
†¯
¨
R*formats: Handle°dONLNd
†
R
¨
^)Z):°dONLNd
†
^
¨
à) OSErr;
.
°dONLNd
æH
 ï(
«HReading and WI∞°dONLNd)
æï
 ¸)Mriting Non-Edition fiä∞°dONLNd>
æ¸
 

)gles
.°dONLNdB
–H
‹ˆ(
ŸHFUNCTION GetEditionOpenerProc°dONLNd`
›Ú
È
∏+™!(VAR opener: EditionOpenerProcPtr°dONLNdÅ
›
∏
È
ƒ)Δ):°dONLNdÉ
›
ƒ
È
Ó) OSErr;°dONLNdã
ÌH
˘ˆ(
ˆHFUNCTION SetEditionOpenerProc°dONLNd©
˙Ú
†+™(opener: EditionOpenerProcPtr°dONLNdΔ
˙
†
¨)Æ):°dONLNd»
˙
¨
÷) OSErr;°dONLNd–
H¸(HFUNCTION CallEditionOpenerProc°dONLNdÔÚ#
¶+™(selector: EditionOpenerVerb; °dONLNd$¯0
æ+!VAR PB: EditionOpenerParamBlock; °dONLNd01¯=
¶*routine: EditionOpenerProcPtr°dONLNdM1
¶=
≤)Æ):°dONLNdO1
≤=
‹) OSErr;°dONLNdWAHMfi(JHFUNCTION CallFormatIOProc°dONLNdqAÚM
à)™(selector: FormatIOVerb; °dONLNdãN¯Z
†+VAR PB: FormatIOParamBlock; °dONLNd®[¯g
à*routine: FormatIOProcPtr°dONLNd¿[
àg
î)ê):°dONLNd¬[
îg
æ) OSErr;

äHè4äHè ãHã

ˇ·ˇ‚7^.
°dONLNdÀHäï(áHApplication-Defiâ°°dONLNd€ïä’)Mned Routinesˇˇˇˇˇˇa‡(á
2
.°dONLNdÈïH°Δ(ûHFUNCTION MyExpDlgHook°dONLNdˇïÚ°
‚)™((itemOffset: Integer; itemHit: Integer; °dONLNd(¢¯Æ
|+theDialog: DialogPtr; °dONLNd?دª
X*yourDataPtr: Ptr°dONLNdOØ
Xª
d)`):°dONLNdQØ
dª
ö)     Integer;ˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-114    )BSummary of the Edition Manager4^*¿
¯,
Courier
.°dONLNd\*h¿(e*FUNCTION MyExpModalFilter°dONLNd\‘h
^)™(theDialog: DialogPtr; °dONLNd2i⁄u
|+VAR theEvent: EventRecord; °dONLNdNv⁄Ç
‹*+itemOffset: Integer; VAR itemHit: Integer; °dONLNdyÉ⁄è
:*yourDataPtr: Ptr°dONLNdâÉ
:è
F)`):°dONLNdãÉ
Fè
|)     Boolean;°dONLNdïì*üê(ú*FUNCTION MyOpener°dONLNdßì‘ü
à)™(selector: EditionOpenerVerb; °dONLNdΔ†⁄¨
 +(VAR PB: EditionOpenerParamBlock): OSErr;°dONLNdÔ∞*ºx(π*FUNCTION MyIO°dONLNd˝∞‘º
j)™(selector: FormatIOVerb; °dONLNd
Ω⁄…
v+VAR PB: FormatIOParamBlock°dONLNd
1Ω
v…
Ç)ú):°dONLNd
3Ω
Ç…
¨) OSErr;

˙*


¯4˙*


¯ ˚*˚
¯

ˇ·ˇ‚7^.
°dONLNd
<Î*˙s(ˆ*    C Summaryˇˇˇˇˇˇ∑†(ˆ

2


"*
(
¯4
#*
'
¯ 
$*
$
¯

ˇ·ˇ‚7^°dONLNd
H
*
"[(
*    Constantsˇˇˇˇˇˇa‡(

Ú
2
.°dONLNd
S
2*
>H(
;*CONST°dONLNd
[
@*
LN*enum {°dONLNd
c
N<
Z®+/*resource types*/°dONLNd
w
\<
hÆ*#define rSectionTyp°dONLNd
ä
\Æ
h¥)r
e°dONLNd
ï
\
h¸)B '°dONLNd
ó
\¸
h
)sect'°dONLNd
†
\
8
h
»)</*resource type for a */°dONLNd
»
j
8
v
Ä*/* section*/°dONLNd
◊
Ü<
í¢(
è</*section types*/°dONLNd
Í
î<
†Ñ*stSubscriber°dONLNd
î
†
)¥= 0x01,°dONLNd
î
8
†
⁄)H/*subscriber section type*/°dONLNd(
¢<
Æ~(
´<stPublisher°dONLNd=
¢
Æ
)¥= 0x0A,°dONLNdH
¢
8
Æ
⁄)H/*publisher section type*/ °dONLNdf
æ<
 ú(
«</*update modes*/°dONLNdx
Ã<
ÿÑ*sumAutomatic°dONLNdé
Ã
ÿ
)¥= 0,°dONLNdñ
Ã
8
ÿ
Ê)H/*subscriber receives new */ °dONLNd√
⁄
8
Ê
⁄*/* editions automatically*/°dONLNd‡
Ë<
Ùr(
Ò<    sumManual°dONLNdÛ
Ë
Ù
)¥= 1,°dONLNd˚
Ë
8
Ù
Ê)H/*subscriber receives new */ °dONLNd(
ˆ
8
º*/* editions manually*/°dONLNd@<r(<    pumOnSave°dONLNdS
)¥= 0,°dONLNd[
8
Œ)H/*publisher sends new */ °dONLNdÑ
8
∂*/* editions on save*/°dONLNdõ <,r()<    pumManual°dONLNdÆ ,
)¥= 1,°dONLNd∂ 
8,
Ê)H/*publisher does not send */ °dONLNd„.
8:
Ê*/* new editions until user */°dONLNd<
8H
Ä*/* request*/°dONLNdU<a
(^<$/*edition container subpart number*/°dONLNdDc<oä*kPartsNotUsed°dONLNd[co
)¥= 0,°dONLNdcc
8o
Ê)H/*edition is the whole file*/°dONLNdÇq<}®(z<kPartNumberUnknown°dONLNdûq}
)¥= -1,°dONLNdßq
8}
‡)H/*not used in version 7.0*/ °dONLNdΔç<ôú(ñ</*preview size*/°dONLNdÿõ<ßä*kPreviewWidth°dONLNdÔõß
)¥= 120,°dONLNd˘õ
8ß
§)H/*preview width*/ °dONLNd©<µê(≤<kPreviewHeight°dONLNd%©µ
)¥= 120,°dONLNd/©
8µ
§)H/*preview height*/ˇ3.@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äSummary of the Edition Manager

, (‡
ˇ2-115
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\ZhÃ(eZ/*special formats*/°dONLNdjZv
*#define kPublisherDocAliasForma°dONLNd4j
v
)∫
t°dONLNd?j
v
&) '°dONLNdAj
&v
D)alis'°dONLNdJj
Vv
¯)0/*alias record from the */ °dONLNdux
VÑ
Ú*/* edition to publisher*/ °dONLNdëÜZíÿ(èZ#define kPreviewForma°dONLNd¶Üÿífi)~
t°dONLNd≤Ü
 í
&)H
'°dONLNd≥Ü
&í
>)prvw°dONLNd∑Ü
>í
D)
'°dONLNdªÜ
Ví
\)
/°dONLNdºÜ
\í
¯)*'PICT' thumbnail sketch*/°dONLNdÿîZ†Í(ùZ#define kFormatListForma°dONLNdî͆)ê
t°dONLNd˚î
†
)$
 °dONLNd˝î
 †
&)
'°dONLNd˛î
&†
>)fmts°dONLNd
î
>†
D)
'°dONLNd
î
V†
\)
/°dONLNd
î
\†
Ú)*list of all available */°dONLNd
0¢
VÆ
˛(´
V/* formats and their sizes*/°dONLNd
OæZ ‰(«Z/*bits for formatMask*/°dONLNd
hÃZÿ¥*kPICTformatMask°dONLNd
ÅÃ
ÿ
&)¥= 1,°dONLNd
âÃ
Vÿ
»)H/*graphics format*/°dONLNd
û⁄ZÊ¥(„ZkTEXTformatMask°dONLNd
∑⁄
Ê
&)¥= 2,°dONLNd
ø⁄
VÊ
∞)H/*text format*/°dONLNd
–ËZÙÆ(ÒZksndFormatMask°dONLNd
ËË
Ù
&)¥= 4,°dONLNd
Ë
VÙ
∂)H/*sound format*/°dONLNd
Z

&(
Z"/*Finder types for edition files*/°dONLNd'
Z
¸*#define kPICTEditionFileTyp°dONLNdB
¸

)¢
e°dONLNdM



)
 °dONLNdO

 

&)
'°dONLNdP

&

>)edtp°dONLNdT

>

D)
'°dONLNdX

V

\)
/°dONLNdY

\

‘)*contains 'PICT', */°dONLNdo
 Z
,¸(
)Z#define kTEXTEditionFileTyp°dONLNdä
 ¸
,
)¢
e°dONLNdï
 

,
)
 °dONLNdó
 
 
,
&)
'°dONLNdò
 
&
,
>)edtt°dONLNdú
 
>
,
D)
'°dONLNd†
 
V
,
\)
/°dONLNd°
 
\
,
º)* 'TEXT', and */°dONLNd≥
.Z
:ˆ(
7Z#define ksndEditionFileTyp°dONLNdÕ
.ˆ
:¸)ú
e°dONLNdÿ
.

:
)
 °dONLNd⁄
.
 
:
&)
'°dONLNd€
.
&
:
>)edts°dONLNdfl
.
>
:
D)
'°dONLNd„
.
V
:
\)
/°dONLNd‰
.
\
:
⁄)* 'snd ' file types*/°dONLNd˚
<Z
H
(
EZ#define kUnknownEditionFileTyp°dONLNd
<

H
)¥
e°dONLNd$
<

H
)
 °dONLNd&
<
 
H
&)
'°dONLNd'
<
&
H
>)edtu°dONLNd+
<
>
H
D)
'°dONLNd/
<
V
H
\)
/°dONLNd0
<
\
H
‘)*unknown file type*/°dONLNdG
XZ
d
2(
aZ$/*pseudo-item hits for dialogHooks*/°dONLNdm
fZ
rÃ*emHookRedrawPreview°dONLNdä
f

r
2)¥= 150,°dONLNdî
f
V
r
Ê)H/*for NewPublisher or */°dONLNdº
t
V
Ä
Ú*/* NewSubscriber dialogs*/°dONLNdÿ
ÇZ
éÃ(
ãZemHookCancelSection°dONLNdı
Ç

é
2)¥= 160,°dONLNdˇ
Ç
V
é)H/*for SectionOptions dialog*/°dONLNd
êZ
úÃ(
ôZemHookGoToPublisher°dONLNd;
ê

ú
2)¥= 161,°dONLNdE
ê
V
ú)H/*for SectionOptions dialog*/°dONLNdd
ûZ
™Ã(
ßZemHookGetEditionNow°dONLNdÅ
û

™
2)¥= 162,°dONLNdã
û
V
™)H/*for SectionOptions dialog*/°dONLNd™
¨Z
∏“(
µZemHookSendEditionNow°dONLNd»
¨

∏
2)¥= 162,°dONLNd“
¨
V
∏)H/*for SectionOptions dialog*/°dONLNdÒ
∫Z
Δfi(
√ZemHookManualUpdateMode°dONLNd
∫

Δ
2)¥= 163,°dONLNd
∫
V
Δ)H/*for SectionOptions dialog*/°dONLNd:
»Z
‘“(
—ZemHookAutoUpdateMode°dONLNdX
»

‘
&)¥= 16°dONLNd\
»
&
‘
,)
4°dONLNda
»
V
‘
\)0
/°dONLNdb
»
\
‘)*for SectionOptions dialog*/°dONLNd
÷H
‚N(
flH
}°dONLNdÄ
÷N
‚T)
;°dONLNdÉ
‰Z
Í+/*edition opener verbs*/°dONLNdú
ÚH
˛
º(
˚H>enum {eoOpen, eoClose, eoOpenNew, eoCloseNew, eoCanSubscribe};°dONLNd‹Hf*enum °dONLNd·fl)
{°dONLNd‰Z(`(%Z
/°dONLNdÂ`(
í)3*refCon field when displaying stacked dialog boxes*°dONLNd
í(
ò(%
í
/°dONLNd*Z6
(3Z#define emOptionsDialogRefCo°dONLNd7*
6
)®
n°dONLNdD*
26
>)0 '°dONLNdF*
>6
\)optn'°dONLNdO*
z6
Ê)</*options dialog*/°dONLNdc8ZD
&(AZ"#define emCancelSectionDialogRefCo°dONLNdÖ8
&D
,)Ã
n°dONLNdí8
2D
>) '°dONLNdî8
>D
\)cncl'°dONLNdù8
zD
Ê)</*cancel section*/°dONLNd±FZR
(OZ#define emGotoPubErrDialogRefCo°dONLNd–F
R
)∫
n°dONLNd›F
2R
>) '°dONLNdflF
>R
\)gerr'°dONLNdËF
zR
Ú)</*locate publisher*/°dONLNdˇbZn“(kZkFormatLengthUnknown°dONLNdb
n
,)¥= -1 °dONLNd&b
Vn
˛)H/*length of format unknown*/°dONLNdCpH|N(yH
}°dONLNdDpN|T)
;°dONLNdG~Zä
ò+5/*refCon field when displaying stacked dialog boxes*/°dONLNd~åZòˆ*#define sfMainDialogRefCon°dONLNd¢å
ò
8)¥ 'stdf'°dONLNd≠å
Vò
Œ)H{new publisher and }°dONLNd—ö
V¶
º*{ new subscriber}°dONLNd‰®Z¥
(±Z#define sfNewFolderDialogRefCon°dONLNd®
¥
8)∫'nfdr'°dONLNd®
V¥
û)B{new folder}ˇ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-116    )BSummary of the Edition Manager4^*¿
¯,
Courier
.°dONLNd\<hÍ(e<#define sfReplaceDialogRefCon°dONLNd'\h
)¥ 'rplc'°dONLNd2\
8h
ò)H{replace dialog}°dONLNdDj<v(s<#define sfStatWarnDialogRefCon°dONLNdcjv
)¥ 'stat'°dONLNdwj
8v
ò)H{warning dialog}°dONLNdâx<Ñfi(Å<#define sfErrorDialogRefCon°dONLNdÆxÑ
)¥ 'err '°dONLNdπx
8Ñ
å)H{error dialog}°dONLNd î<†
§(ù<</*message IDs for Apple events sent by the Edition Manager*/°dONLNd
¢<Æl*#define °dONLNd
¢lÆfi)0sectionEventMsgClas°dONLNd
#¢fiƉ)r
s°dONLNd
.¢Ƹ) '°dONLNd
0¢¸Æ
)sect°dONLNd
4¢
Æ
)
'°dONLNd
9¢
8Æ
>)$
/°dONLNd
:¢
>Æ
Ê)*Apple events sent by the */°dONLNd
f∞
8º
™(π
8/* Edition Manager*°dONLNd
y∞
™º
∞)r
/°dONLNd
|æ< r(«<    #define s°dONLNd
Öær Δ)6ectionReadMsgI°dONLNd
ìæΔ Ã)T
D°dONLNd
ûæ ¸)* '°dONLNd
†æ¸ 
)read°dONLNd
§æ
 
)
'°dONLNd
©æ
8 
>)$
/°dONLNd
™æ
> 
¬)*Section Read events*/°dONLNd
¬Ã<ÿr(’<    #define s°dONLNd
ÀÃrÿÃ)6ectionWriteMsgI°dONLNd
⁄ÃÃÿ“)Z
D°dONLNd
ÂÃÿ¸)$ '°dONLNd
Áøÿ
)writ°dONLNd
ÎÃ
ÿ
)
'°dONLNd
Ã
8ÿ
>)$
/°dONLNd
ÒÃ
>ÿ
»)*Section Write events*/°dONLNd
⁄<Êl(„<#define °dONLNd⁄lÊ“)0sectionScrollMsgI°dONLNd#⁄“Êÿ)f
D°dONLNd.⁄ʸ) '°dONLNd0⁄¸Ê
)scrl°dONLNd4⁄
Ê
)
'°dONLNd9⁄
8Ê
>)$
/°dONLNd:⁄
>Ê
Œ)*Section Scroll events*/°dONLNdTË<Ùl(Ò<#define °dONLNd\ËlÙ“)0sectionCancelMsgI°dONLNdmË“Ùÿ)f
D°dONLNdxËÙ¸) '°dONLNdz˸Ù
)cncl°dONLNd~Ë
Ù
)
'°dONLNdÉË
8Ù
>)$
/°dONLNdÑË
>Ù
Œ)*Section Cancel events*/


*

¯4
*

¯ 
*

¯

ˇ·ˇ‚7^.
°dONLNdû
*
D(
*Data òp°dONLNd£
D
J)
Tµ‡°dONLNd§
J
[)yper °dONLNdß
\
a)
sˇˇˇˇˇˇa‡(

Ú
2
.°dONLNd™
'*
30(
0*
t°dONLNd´
'0
3Í)ypedef unsigned long TimeStamp;°dONLNdŸ
'
8
3
∂(
0
8/*seconds since 1904*°dONLNdÓ
'
∂
3
º)~
/°dONLNd
5*
A0(
>*
t°dONLNdÒ
50
Aÿ)ypedef Handle EditionRefNum;°dONLNdˇˇ)®
`°dONLNd
5
8
A
º)`/*used in Edition I/O*°dONLNd3
5
º
A
¬)Ñ
/°dONLNd5
C*
O0(
L*
t°dONLNd6
C0
O¿)ypedef short UpdateMode;°dONLNd]
C
8
O
D(
L
8/*°dONLNd_
C
D
O
í)update mode: °dONLNdl
C
í
O
Ú)NsumAutomatic, */°dONLNdå
Q
8
]
û(
Z
8/* sumManual, */ °dONLNd≠
_
8
k
Œ*/* pumOnSave, pumManual*/°dONLNd«
m*
y¿(
v*typedef char SectionType;°dONLNdÔ
m
8
y
⁄(
v
8/*one byte, stSubscriber */°dONLNd
{
8
á
∞*/* or stPublisher*/ °dONLNd/
â*
ï(
í*!typedef unsigned long FormatType;°dONLNd_
â
8
ï
º(
í
8/*similar to ResType*/°dONLNdw
•*
±Æ(
Æ*struct SectionRecord {°dONLNdè
≥<
øÆ+SignedByte version;°dONLNd∞
≥
8
ø
Ï)¸/*always 1x01 in version 7.0*/°dONLNd–
¡<
Õ¢(
 <SectionType kind;°dONLNdÔ
¡
8
Õ
™)¸/*stPublisher or */°dONLNd
œ
8
€
û*/* stSubscriber*/°dONLNd%
›<
Èú(
Ê<UpdateMode mode;°dONLNdC
›
8
È
¬)¸/*automatic or manual*/°dONLNd\
Î<
˜¢(
Ù<TimeStamp mdDate;°dONLNd{
Î
8
˜
‘)¸/*last change to section*/°dONLNdó
˘<ñ(<long sectionID;°dONLNd¥
˘
8
‘)¸/*application-specific, */°dONLNdfi
8
»*/* unique per document*/°dONLNd¯<!Ñ(<long refCon;°dONLNd
8!
»)¸/*application-specific*/°dONLNd,#</®(,<AliasHandle alias;°dONLNdL#
8/
‘)¸/*handle to alias record*/°dONLNdh1<=ä(:<long subPart;°dONLNdÉ1
8=
>)¸
/°dONLNdÑ1
>=
z)
*private*/°dONLNdê?<KB(H<
s°dONLNdë?BK
)"truct SectionRecord **nextSection;°dONLNd¡?
8K
>)ˆ
/°dONLNd¬?
>K
z)
*private*/°dONLNdŒM<YB(V<
H°dONLNdœMBY¥)andle controlBlock;°dONLNdM
8Y
z)ˆ/*private*/°dONLNd˝[<g∫(d<EditionRefNum refNum;°dONLNd [
8g
z)¸/*private*/°dONLNd,i*u6(r*};°dONLNd0Ö*ë
,*+typedef struct SectionRecord SectionRecord;°dONLNd\ì*ü
\*3typedef SectionRecord *SectionPtr, **SectionHandle;ˇ*‡@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äSummary of the Edition Manager

, (‡
ˇ2-117
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\Hhˆ(eHstruct EditionContainerSpec {°dONLNdjZv¥+FSSpec theFile;°dONLNd<j
Vv
‘)¸/*file containing */ °dONLNdax
VÑ
º*/* edition data*/°dONLNdtÜZíˆ(èZScriptCode theFileScript; °dONLNdúÜ
Ví
¯)¸/*script code of filename*/°dONLNdπîZ†®(ùZlong thePart;°dONLNd‘î
V†
Ï)¸/*which part of file, */ °dONLNd˝¢
VÆ
Ï*/* always kPartsNotUsed*/°dONLNd
∞ZºΔ(πZStr31 thePartName;°dONLNd
8∞
Vº
\)¸
/°dONLNd
9∞
\º
ò)
*reserved*°dONLNd
C∞
òº
û)<
/°dONLNd
FæZ ˆ(«ZScriptCode thePartScript; °dONLNd
næ
V 
\)¸
/°dONLNd
oæ
\ 
ò)
*reserved*°dONLNd
yæ
ò 
û)<
/°dONLNd
{ÃHÿT(’H};°dONLNd
ËHÙ
û*9typedef struct EditionContainerSpec EditionContainerSpec;°dONLNd
πˆH

å*6typedef EditionContainerSpec *EditionContainerSpecPtr;°dONLNd
Ò
H
‰*struct EditionInfoRecord {°dONLNd
 Z
,¿+TimeStamp crDate;°dONLNd+
 
D
,
Ê)Í/*date edition container */°dONLNdU
.
D
:
§*/* was created*/°dONLNdg
<Z
H¿(
EZTimeStamp mdDate;°dONLNdÖ
<
D
H
Œ)Í/*date of last change*/°dONLNdû
JZ
V¿(
SZOSType fdCreator;°dONLNdº
J
D
V
§)Í/*file creator*/°dONLNdŒ
XZ
dÆ(
aZOSType fdType;°dONLNdÈ
X
D
d
í)Í/*file type*/°dONLNd¯
fZ
r
(
oZEditionContainerSpec container;°dONLNd$
f
D
r
û)Í/*the edition*/°dONLNd4
tH
ÄT(
}H};°dONLNd8
êH
ú
z*3typedef struct EditionInfoRecord EditionInfoRecord;°dONLNdm
¨H
∏‰*struct NewPublisherReply {°dONLNdâ
∫Z
Δ¿+Boolean canceled;°dONLNdß
∫
D
Δ
Ú)Í/*user canceled dialog box*/ °dONLNdΔ
»Z
‘Δ(
—ZBoolean replacing;°dONLNdÂ
»
D
‘
⁄)Í/*user chose existing */ °dONLNd
÷
D
‚
Ï*/* filename for an edition*/°dONLNd+
‰Z
∫(
ÌZBoolean usePart;°dONLNdH
‰
D

Ú)Í/*always FALSE in version */ °dONLNdt
Ú
D
˛
t*/* 7.0*/°dONLNd~Z¥(    ZHandle preview;°dONLNdö
D
Ú)Í/*handle to 'prvw', 'PICT',*/°dONLNdΔ
D
Ê*/* 'TEXT', or 'snd ' data*/°dONLNd„Z((%ZFormatType previewFormat;°dONLNd    
D(
∂)Í/*type of preview*/°dONLNd*Z6
(3ZEditionContainerSpec container;°dONLNdJ*
D6
∞)Í/*edition chosen*/°dONLNd]8HDT(AH};°dONLNd`FHR
z*3typedef struct NewPublisherReply NewPublisherReply;°dONLNdïbHnÍ*struct NewSubscriberReply {°dONLNd≤pZ|¿+Boolean canceled;°dONLNd–p
D|
Ï)Í/*user canceled dialog box*/°dONLNdÓ~Zäˆ(áZunsigned char formatsMask;°dONLNd~
Dä
º)Í/*formats required*/°dONLNd+åZò
(ïZ EditionContainerSpec container; °dONLNdXå
Dò
º)Í/*edition selected*/°dONLNdmöH¶T(£H};°dONLNdp®H¥
Ü*5typedef struct NewSubscriberReply NewSubscriberReply;ˇà@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-118    )BSummary of the Edition Manager4^*¿
¯,
Courier
.°dONLNd\*h“(e*struct SectionOptionsReply {°dONLNdj<v¢+Boolean canceled;°dONLNd<j
&v
Œ)Í/*user canceled dialog box*/°dONLNdZx<Ñ¢(Å<Boolean changed; °dONLNdxx
&Ñ
∂)Í/*changed the section */°dONLNdüÜ
&í
h*/* record*/°dONLNd¨î<†Δ(ù<SectionHandle sectionH;°dONLNd–î
&†
Œ)Í/*handle to the specified */°dONLNd˚¢
&Æ
ò*/* section record*/°dONLNd
∞<ºñ(π<ResType action;°dONLNd
,∞
&º
Ü)Í/*action codes*/°dONLNd
=æ* 6(«*};°dONLNd
A⁄*Ê
t*7typedef struct SectionOptionsReply SectionOptionsReply;°dONLNd
zˆ*

Œ*Ftypedef pascal Boolean (*ExpModalFilterProcPtr) (DialogPtr theDialog, °dONLNd
Õ



+ÿ
E°dONLNd
Œ



Ú)'ventRecord *theEvent, short itemOffset,°dONLNd
ı

Ú

¯)Í
 °dONLNd



(


s°dONLNd



») hort *itemHit, Ptr yourDataPtr);°dONLNd&
.*
:
Ê(
7*Jtypedef pascal short (*ExpDlgHookProcPtr) (short itemOffset, short itemHit°dONLNdp
.
Ê
:
Ï(
7
Ê
,°dONLNdy
<®
HÆ(
E®
 °dONLNdÄ
<

H
Ú)l%DialogPtr theDialog, Ptr yourDataPtr)°dONLNd•
<
Ú
H
¯)fi
;°dONLNd®
X*
d0(
a*
t°dONLNd©
X0
d
)'ypedef unsigned char EditionOpenerVerb;°dONLNd”
t*
ÄÍ(
}* struct EditionOpenerParamBlock {°dONLNdı
Ç<
éΔ+EditionInfoRecord info;°dONLNd
Ç
&
é
º)Í/*edition container to */°dONLNdA
ê
&
ú
§*/* be subscribed to*/°dONLNdX
û<
™Δ(
ß<SectionHandle sectionH;°dONLNd|
û
&
™
Œ)Í/*publisher or subscriber */°dONLNdß
¨
&
∏
û*/* requesting open*/°dONLNdΩ
∫<
ΔÆ(
√<FSSpecPtr document;°dONLNd›
∫
&
Δ
ò)Í/*document passed*/°dONLNdÚ
»<
‘¢(
—<OSType fdCreator;°dONLNd
»
&
‘
∞)Í/*Finder creator type*/°dONLNd)
÷<
‚ê(
fl<long ioRefNum;°dONLNdD
÷
&
‚
û)Í/*reference number*/°dONLNdZ
‰<
Δ(
Ì<FormatIOProcPtr ioProc;°dONLNd~
‰
&

»)Í/*routine to read formats*/°dONLNdõ
Ú<
˛ú(
˚<Boolean success;°dONLNd∏
Ú
&
˛
»)Í/*reading or writing was */°dONLNd‚
&
Ä*/* successful*/°dONLNdÛ<ÿ(<unsigned char formatsMask;°dONLNd
&
∂)Í/*formats required to */°dONLNdA
&(
z*/* subscribe*/°dONLNdP**60(3*
}°dONLNdQ*066)
;°dONLNdS8*D
§(A*?typedef struct EditionOpenerParamBlock EditionOpenerParamBlock;°dONLNdîT*`
⁄*Htypedef pascal short (*EditionOpenerProcPtr) (EditionOpenerVerb selector°dONLNd‹T
⁄`
‡(]
⁄
,°dONLNdÌb
8n
>(k
8
F°dONLNdÓb
>n
¬)ormatIOParamBlock *PB)°dONLNdb
¬n
»)Ñ
;°dONLNd~*ä
ò(á*=enum {ioHasFormat, ioReadFormat, ioNewFormat, ioWriteFormat};°dONLNdEå*ò¸*#typedef unsigned char FormatIOVerb;ˇ(P@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äSummary of the Edition Manager

, (‡
ˇ2-119
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd\HhÍ(eHstruct FormatIOParamBlock {°dONLNdjZvÆ+long ioRefNum;°dONLNd8j
Dv
º)Í/*reference number*/°dONLNdNxZÑΔ(ÅZFormatType format;°dONLNdmx
DÑ
Œ)Í/*edition format type*/°dONLNdÜÜZí¿(èZlong formatIndex;°dONLNd§Ü
Dí
»)Í/* opener-specific */ °dONLNd…î
D†
™*/* enumeration */°dONLNdÈ¢
DÆ
û*/* of formats*/°dONLNd˙∞Zºÿ(πZunsigned long offset;°dONLNd
∞
Dº
»)Í/*offset into format*/°dONLNd
4æZ ¢(«ZPtr buffPtr;°dONLNd
Mæ
D 
º)Í/*data starts here*/°dONLNd
cÃZÿfi(’Zunsigned long buffLen;°dONLNd
ÜÃ
Dÿ
∞)Í/*length of data*/°dONLNd
ô⁄HÊT(„H};°dONLNd
ùˆH

Ü*5typedef struct FormatIOParamBlock FormatIOParamBlock;°dONLNd
‘
H

¬*?typedef pascal short (*FormatIOProcPtr) (FormatIOVerb selector,°dONLNd!
 
2
,
¬+ÍFormatIOParamBlock *PB);


OH
U4
PH
T 
QH
Q

ˇ·ˇ‚7^.
°dONLNd;
DH
OΔ(
LHEdition Manager Routinesˇˇˇˇˇˇa‡(
L
2
°dONLNdU
eH
qÍ(
nH Initializing the Edition Manager
.°dONLNdv
xH
Ñ*pascal OSErr InitEditionPack°dONLNdì
xÚ
Ñ
)™(void)
.
°dONLNdö
ñH
¢ˆ(
üH"Creating and Registering a Section
.°dONLNdΩ
®H
¥“*pascal OSErr NewSection°dONLNd’
®Ú
¥
‹)™'(const EditionContainerSpec *container,°dONLNd˝
µ¯
¡
¨+const FSSpec *sectionDocument,°dONLNd
¬¯
Œ
æ*!SectionType kind, long sectionID,°dONLNd>
œ¯
€
Ç*UpdateMode initialMode,°dONLNdV
‹¯
Ë
é*SectionHandle *sectionH);°dONLNdp
ÏH
¯(
ıHpascal OSErr RegisterSection°dONLNdç
˘Ú
¨+™(const FSSpec *sectionDocument,°dONLNd≠¯
Ç+SectionHandle sectionH,°dONLNd≈¯
î*Boolean *aliasWasUpdated);°dONLNd‡#H/¸(,Hpascal OSErr UnRegisterSection°dONLNdˇ0Ú<
à+™(SectionHandle sectionH);°dONLNd@HL
(IH pascal OSErr IsRegisteredSection°dONLNd:MÚY
à+™(SectionHandle sectionH);°dONLNdT]Hiˆ(fHpascal OSErr AssociateSection°dONLNdrjÚv
Ç+™(SectionHandle sectionH,°dONLNdãw¯É
ƒ+"const FSSpec *newSectionDocument);ˇà@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-120    )BSummary of the Edition Manager4^*¿
¯
°dONLNd\*h
(e**Creating and Deleting an Edition Container,
Courier
.°dONLNd+o*{
*'pascal OSErr CreateEditionContainerFile°dONLNdS|‘à
Ë+™.(const FSSpec *editionFile, OSType fdCreator, °dONLNdÅâ⁄ï
¶+"ScriptCode editionFileNameScript);°dONLNd§ô*•
(¢*'pascal OSErr DeleteEditionContainerFile°dONLNdö‘≤
|+™(const FSSpec *editionFile);
.
°dONLNdȃ*–](Õ*
Setting anÉ¿°dONLNdÛƒ]–|)3d Gett˘ °dONLNd˘ƒ|–Ÿ)ing a Format Mark
.°dONLNd
÷*‚(fl*!pascal OSErr SetEditionFormatMark°dONLNd
-„‘Ô
|+™(EditionRefNum whichEdition,°dONLNd
J⁄¸
d+FormatType whichFormat,°dONLNd
b˝⁄
    
p*unsigned long setMarkTo);°dONLNd
|
*
(
*!pascal OSErr GetEditionFormatMark°dONLNd
û
‘
&
|+™(EditionRefNum whichEdition,°dONLNd
ª
'⁄
3
d+FormatType whichFormat,°dONLNd
”
4⁄
@
Ç*unsigned long *currentMark);
.
°dONLNd

R*
^£(
[*Reading in Edition Data
.°dONLNd
e*
q∫*pascal OSErr OpenEdition°dONLNd!
e‘
q
¶)™#(SectionHandle subscriberSectionH, °dONLNdD
r⁄
~
d+EditionRefNum *refNum);°dONLNd\
Ç*
éÿ(
ã*pascal OSErr EditionHasFormat°dONLNdz
è‘
õ
|+™(EditionRefNum whichEdition,°dONLNdó
ú⁄
®
d+FormatType whichFormat,°dONLNdØ
©⁄
µ
F*Size *formatSize);°dONLNd¬
π*
≈∫(
¬*pascal OSErr ReadEdition°dONLNd€
π‘
≈
|)™(EditionRefNum whichEdition,°dONLNd¯
Δ⁄
“
æ+&FormatType whichFormat, void *buffPtr,°dONLNd
”⁄
fl
4*Size *buffLen);
.
°dONLNd/
Ò*
˝5(
˙*
WØ∞°dONLNd0
Ò4
˝•)
riting out Edition Data
.°dONLNdH*Ã(*pascal OSErr OpenNewEdition°dONLNdd‘
ö)™!(SectionHandle publisherSectionH,°dONLNdÜ⁄
@+OSType fdCreator,°dONLNdò⁄)
ƒ*'const FSSpec *publisherSectionDocument,°dONLNd¿*⁄6
d*EditionRefNum *refNum);°dONLNdÿ:*F¿(C*pascal OSErr WriteEdition°dONLNdÚ:‘F
|)™(EditionRefNum whichEdition,°dONLNdG⁄S
Ë+-FormatType whichFormat, const void *buffPtr, °dONLNd<T⁄`
4*Size *buffLen);
.
°dONLNdLr*~Ï({*%Closing an Edition After Reading or Wûê°dONLNdqrÏ~
)¬riting
.°dONLNdxÖ*ë¿(é*pascal OSErr CloseEdition°dONLNdíÖ‘ë
|)™(EditionRefNum whichEdition,°dONLNdØí⁄û
R+Boolean successful);ˇ(™@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äSummary of the Edition Manager

, (‡
ˇ2-121
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\Hh≈(eHDisplaying Dialog Boxes,
Courier
.°dONLNdoH{
8*(pascal OSErr GetLastEditionContainerUsed°dONLNdA|Úà
æ+™"(EditionContainerSpec *container);°dONLNddåHò
(ïH pascal OSErr NewSubscriberDialog°dONLNdÖôÚ•
ö+™(NewSubscriberReply *reply);°dONLNd¢©Hµ
(≤Hpascal OSErr NewPublisherDialog°dONLNd¬∂Ú¬
î+™(NewPublisherReply *reply);°dONLNdfiΔH“
(œH!pascal OSErr SectionOptionsDialog°dONLNd
”Úfl
†+™(SectionOptionsReply *reply);°dONLNd
„HÔ
(ÏH#pascal OSErr NewSubscriberExpDialog°dONLNd
BÚ¸
‚+™((NewSubscriberReply *reply, Point where,°dONLNd
k˝¯
    
é+short expansionDITLresID,°dONLNd
Ö

¯

î*ExpDlgHookProcPtr dlgHook,°dONLNd
†
¯
#
æ*!ExpModalFilterProcPtr filterProc,°dONLNd
¬
$¯
0
j*void *yourDataPtr);°dONLNd
÷
4H
@
(
=H"pascal OSErr NewPublisherExpDialog°dONLNd
˘
AÚ
M
‹+™'(NewPublisherReply *reply, Point where,°dONLNd!
N¯
Z
é+short expansionDITLresID,°dONLNd;
[¯
g
î*ExpDlgHookProcPtr dlgHook,°dONLNdV
h¯
t
æ*!ExpModalFilterProcPtr filterProc,°dONLNdx
u¯
Å
j*void *yourDataPtr);°dONLNdå
ÖH
ë
 (
éH$pascal OSErr SectionOptionsExpDialog°dONLNd±
íÚ
û
Ë+™)(SectionOptionsReply *reply, Point where,°dONLNd⁄
í
Ë
û
Ó)ˆ
 °dONLNd‹
ü¯
´˛(
®¯
s°dONLNd›
ü˛
´
é)hort expansionDITLresID,°dONLNdˆ
¨¯
∏
î(
µ¯ExpDlgHookProcPtr dlgHook,°dONLNd
π¯
≈
æ*!ExpModalFilterProcPtr filterProc,°dONLNd3
Δ¯
“
j*void *yourDataPtr);
.
°dONLNdG
‰H

K(
ÌH2Locating a Publisher and Edition From a Subscriber
.°dONLNdz
ˆHÍ*pascal OSErr GetEditionInfo°dONLNdñ
ˆÚ
¶)™(const SectionHandle sectionH,°dONLNdµ¯
∏+ EditionInfoRecord *editionInfo);°dONLNd÷H
(H!pascal OSErr GoToPublisherSection°dONLNd¯ Ú,
‚+™((const EditionContainerSpec *container);
.
°dONLNd!>HJÕ(GHEdition Container Formats
.°dONLNd;QH]
*pascal OSErr GetStandardFormats°dONLNd[^Új
‹+™'(const EditionContainerSpec *container,°dONLNdÉk¯w
î+FormatType *previewFormat,°dONLNdûx¯Ñ
‹*&Handle preview, Handle publisherAlias,°dONLNd≈Ö¯ë
X*Handle formats);ˇ‡@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@lEdition Manager4⁄*˙
¯

(‡*2-122    )BSummary of the Edition Manager4^*¿
¯
°dONLNd\*hw(e*Reading and WI∞°dONLNd\whfi)Mriting Non-Edition fiä∞°dONLNd"\fihÏ)gles,
Courier
.°dONLNd&o*{(x*!pascal OSErr GetEditionOpenerProc°dONLNdH|‘à
é+™(EditionOpenerProcPtr *opener);°dONLNdhå*ò(ï*!pascal OSErr SetEditionOpenerProc°dONLNdäô‘•
à+™(EditionOpenerProcPtr opener);°dONLNd©©*µˆ(≤*"pascal OSErr CallEditionOpenerProc°dONLNdÃ∂‘¬
|+™(EditionOpenerVerb selector,°dONLNdÈ√⁄œ
Ç+EditionOpenerParamBlock *PB,°dONLNd
–⁄‹
é*EditionOpenerProcPtr routine);°dONLNd
%‡*Ïÿ(È*pascal OSErr CallFormatIOProc°dONLNd
CÌ‘˘
^+™(FormatIOVerb selector,°dONLNd
[˙⁄

d+FormatIOParamBlock *PB,°dONLNd
s
⁄

p*FormatIOProcPtr routine);


5*
;
¯4
6*
:
¯ 
7*
7
¯

ˇ·ˇ‚7^.
°dONLNd
é
**
5w(
2*Application-Defiâ°°dONLNd
û
*w
5∑)Mned Routinesˇˇˇˇˇˇa‡(
2
Ú
2
.°dONLNd
¨
@*
L¿(
I*pascal OSErr MyExpDlgHook°dONLNd
Δ
@‘
L
ö)™!(short itemOffset, short itemHit,°dONLNd
Ë
M⁄
Y
R+DialogPtr theDialog,°dONLNd
˝
Z⁄
f
@*Ptr yourDataPtr);°dONLNd
j*
vÿ(
s*pascal OSErr MyExpModalFilter°dONLNd-
w‘
É
R+™(DialogPtr theDialog,°dONLNdC
Ñ⁄
ê
^+EventRecord *theEvent,°dONLNdZ
ë⁄
ù
¶*"short itemOffset, short *itemHit, °dONLNd}
û⁄
™
@*Ptr yourDataPtr);°dONLNdè
Æ*
∫®(
∑*pascal OSErr MyOpener°dONLNd•
Æ‘
∫
|)™(EditionOpenerVerb selector,°dONLNd¬
ª⁄
«
à+EditionOpenerParamBlock *PB);°dONLNd‡
À*
א(
‘*pascal OSErr MyIO°dONLNdÚ
À‘
◊
^)™(FormatIOVerb selector,°dONLNd

ÿ⁄
‰
j+FormatIOParamBlock *PB);

*
¯4*
¯ *
¯

ˇ·ˇ‚7^°dONLNd$*~(*Result Codesˇˇˇˇˇˇ.
∑†(

2
.°dONLNd0*(H(%*noErr.
°dONLNd6◊(‹)≠
0°dONLNd8(
)No errE†°dONLNd>
(
)or.°dONLNdB(*4Z(1*abortErr.
°dONLNdK(Õ4‹)£–27°dONLNdO(4
ç)##Publisher has written a new edition.°dONLNdt3*?`(<*    dskFulErr.
°dONLNd~3Õ?‹)£–34°dONLNdÇ3?
)#Disk is full.°dONLNdê?*KN(H*nsvErr.
°dONLNdó?ÕK‹)£–35°dONLNdõ?K
8)#No such volume.°dONLNd´J*VH(S*ioErr.
°dONLNd±JÕV‹)£–36°dONLNdµJV
)#I/O err ‡°dONLNdºJ
V
) or.°dONLNd¿V*bZ(_*bdNamErr.
°dONLNd…VÕb‹)£–37°dONLNdÕVb
    )#Bad fiD@°dONLNd”V

b
*)lename.°dONLNd€a*mZ(j*fnOpnErr.
°dONLNd‰aÕm‹)£–38°dONLNdËam
))#File not open.°dONLNd˜m*yN(v*eofErr.
°dONLNd˛mÕy‹)£–39°dONLNdmy
)# No additional data in the format.°dONLNd$x*ÑN(Å*fnfErr.
°dONLNd+xÕÑ‹)£–43°dONLNd/xÑ
j)#Edition container not found.°dONLNdLÑ*êf(ç*
flLckedErr.
°dONLNdWÑÕê‹)£–45°dONLNd[Ñê
w)#Publisher writing to an edition.°dONLNd|è*õT(ò*fBsyErr.
°dONLNdÑèÕõ‹)£–47°dONLNdàèõ
@)#Section doing I/O.°dONLNdõõ*ßZ(§*paramErr.
°dONLNd§õÕß‹)£–50°dONLNd®õß
?)#Invalid parameter.°dONLNdª¶*≤Z(Ø*rfNumErr.
°dONLNdƒ¶Õ≤‹)£–51°dONLNd»¶≤
))#Bad edition rª‡°dONLNd’¶
)≤
9)9eferh°dONLNdŸ¶
:≤
s)ence number.°dONLNdÊ≤*æT(ª*permErr.
°dONLNdÓ≤Õæ‹)£–54°dONLNdÚ≤æ
8)#Not a subscriberˇ'B@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER à)>
2,    Helvetica    ˇˇ—ÚˇÆ(@äEdition Manager4⁄ä˙(‡äSummary of the Edition Manager

, (‡
ˇ2-123
ˇˇˇˇˇˇˇˇ4∏4÷lòÄ2∏A÷rHH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏A÷r∏A÷r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ
∏6÷@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""∏6÷@∏6÷@˜˜˜˜˜˜˜˜˜˜˜˜ˇˇ˛ˇˇ
˛ˇˇˇ    ˇˇˇˇ
ˇ˝ˇˇ˛
ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜
4€4
—?òÄ
€6
—@HH
 –ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""€6
—@€6
—@$˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˝¸ˇ
˛ˇ˛ˇˇ˜˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˛˙ˇ˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˙ˇˇ˛˙ˇ˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ˝˛ˇ˛˛ˇ˚    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier.°dONLNd]Hi~(fH    wrPermErr.
°dONLNd
]Îi˙)£–61°dONLNd]
i
S)#Not a publisher.°dONLNdiHu~(rH    noTypeErr.
°dONLNd)iÊu˙)û–102°dONLNd.i
u
i)(Format not available.°dONLNdDtHÄÑ(}H
memFullErr.
°dONLNdOtÊÄ˙)û–108°dONLNdTt
Ä
E)(Memory full.°dONLNdaÄHåx(âHdirNFErr.
°dONLNdjÄÊå˙)û–120°dONLNdoÄ
å
)(Dir͆°dONLNdrÄ
å
e)ectory not found.°dONLNdÑãHó¢(îHuserCanceledErr.
°dONLNdîãÊó˙)û–128°dONLNdôã
ó
%)(User ¿Ä°dONLNdûã
%ó
M)    clicked C}@°dONLNdßã
Nó
b))anceàÄ°dONLNd´ã
bó
x)l in dF`°dONLNd±ã
yó
°)    ialog box.°dONLNdºóH£Æ(†HeditionMgrInitErr.
°dONLNdŒóÊ£˙)û–450°dONLNd”ó
£
Í)(1Manager not initialized or could not load package.°dONLNd
¢HÆñ(´HbadSectionErr.
°dONLNd
¢ÊÆ˙)û–451°dONLNd
¢
Æ
w)(Not a valid section type.°dONLNd
3ÆH∫“(∑HnotRegisteredSectionErr.
°dONLNd
KÆÊ∫˙)û–452°dONLNd
PÆ
∫
%)(Not rÀ¿°dONLNd
UÆ
%∫
B)egister‡°dONLNd
\Æ
C∫
M)ed.°dONLNd
`πH≈ñ(¬HbadSubPartErr.
°dONLNd
nπÊ≈˙)û–454°dONLNd
sπ
≈
˛)(7Bad edition container spec or invalid edition container.°dONLNd
¨≈H—¿(ŒHmultiplePublisherWrn.
°dONLNd
¡≈Ê—˙)û–460°dONLNd
Δ≈
—
)(AlrÙ†°dONLNd
…≈
—
o)eady is a publisher.°dONLNd
fi–H‹¿(ŸHcontainerNotFoundWrn.
°dONLNd
Û–Ê‹˙)û–461°dONLNd
¯–
‹
P)(Alias was not r∑@°dONLNd–
P‹
q)Besolved.°dONLNd‹HË¥(ÂHnotThePublisherWrn.
°dONLNd#‹ÊË˙)û–463°dONLNd(‹
Ë
\)(Not the publisherˇJ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4^*¿
¯ˇ"û@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,    Helvetica    .
(‡∫Contents,Palatino

, (‡    3-1    3,Ã(#∫CHAPTER ÿ)h
3
ˇˇˇˇˇˇˇˇ4
4
0lòÄ2
A
0rMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
A
0r
A
0r$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜ˇˇˇˇˇˇ(JH
Figure 3-0*    Listing 3-0*    
T)able 3-0

zH
,
4zH
, 
H
°dONLNd
∫
*˘+m Contentsˇˇˇˇˇˇ

ˇ·ˇ‚7^ˇˇ∫Ρ◊(qH
3°dONLNd[∫xÂ)rIntr9°dONLNd[Âx
q)+oduction to ¶∞°dONLNd[
px)ãApple Events
°dONLNd&
;∫
Gÿ(
D∫About ØÄ°dONLNd,
;ÿ
G
)Apple Eventsâ`°dONLNd:
;
(
G
5)P3-3°dONLNd>
Hƒ
T
(
QƒApple Events and ˆ°dONLNdO
H

T
o)QApple Event Objectsy°dONLNdd
H
Ñ
T
ë)o3-6°dONLNdh
Uƒ
a˛(
^ƒApple Event >Ä°dONLNdt
U˛
a
r):Attributes and Parametersˇ‡°dONLNdè
U
Ü
a
ì)à3-7°dONLNdì
bŒ
n
(
kŒApple Event >Ä°dONLNdü
b

n
4):
Attributes=@°dONLNd´
b
I
n
V)A3-8°dONLNdØ
oŒ
{
9(
xŒApple Event Parametersr`°dONLNd«
o
N
{
[)Ä3-9°dONLNdÀ
|Œ
àÌ(
ÖŒInterpru†°dONLNd“
|Ì
à
)eting Ï °dONLNdÿ
|

à
?)Apple Event ™†°dONLNd‰
|
?
à
≥):Attributes and Parametersl°dONLNdˇ
|
»
à
⁄)â3-10°dONLNd

âƒ
ïÁ(
íƒData Str``°dONLNd

âË
ïˇ)$ucturÊ@°dONLNd

âˇ
ï
)es W‡@°dONLNd

â

ï
+)ithin ∑¿°dONLNd

â
+
ï
f)Apple Events놰dONLNd
)
â
{
ï
ç)P3-12°dONLNd
.
ñŒ
¢
(
üŒDescriptor Recorfi °dONLNd
>
ñ

¢
")Jds6‡°dONLNd
B
ñ
7
¢
I)3-12°dONLNd
G
£Œ
ØÒ(
¨ŒKeywor¨`°dONLNd
M
£Ò
Ø
)#d-Specifi凰dONLNd
V
£

Ø
o)'ed Descriptor RecorP`°dONLNd
i
£
p
Ø
z)Xds© °dONLNd
m
£
é
Ø
†)3-15°dONLNd
r
∞Œ
º
(
πŒDescriptor Lists|@°dONLNd
Ñ
∞
(
º
:)Z3-16°dONLNd
â
Ω∫
…˝(
Δ∫Responding to ;¿°dONLNd
ó
Ω˝
…
8)CApple Events†°dONLNd
•
Ω
M
…
_)P3-20°dONLNd
™
 ƒ
÷
(
”ƒAccepting and Pr:Ä°dONLNd
∫
 

÷
8)M    ocessing Œ`°dONLNd
√
 
8
÷
s)'Apple Events®@°dONLNd
—
 
à
÷
ö)P3-20°dONLNd
÷
◊ƒ
„‚(
‡ƒAbout ØÄ°dONLNd
‹
◊‚
„
E)Apple Event HandlersÏÄ°dONLNd
Ú
◊
Y
„
k)w3-23°dONLNd
˜
‰Œ

R(
ÌŒExtracting and Checking Data[‡°dONLNd
‰
g

y)ô3-23°dONLNd
Ҍ
˝

(
˙ŒInteracting Wù`°dONLNd'
Ò


˝
=)<ith the User7`°dONLNd5
Ò
R
˝
d)H3-25°dONLNd:
˛Œ

D(ŒPerforming the Requested d°dONLNdS
˛
D

 )vAction and Returning a ResultÆ¿°dONLNdr
˛
fi

)ö3-25°dONLNdw∫≈(∫Cr\°dONLNdy≈
)eating and Sending ˇ°dONLNdå

#)W
AΔ@°dONLNdç
$
X)pple Eventsÿ‡°dONLNdö
l
~)H3-28°dONLNdüƒ$œ(!ƒCr\°dONLNd°œ$˙)
eating an #‡°dONLNd´˙$
M)+Apple Event Recorc °dONLNdº
M$
S)S
d~‡°dONLNdø
g$
y)3-29°dONLNdƒ%ƒ1Ë(.ƒAdding È@°dONLNdÀ%Ë1
")$Apple Event ß¿°dONLNd◊%
"1
ñ):Attributes and Parametersi °dONLNdÚ%
´1
Ω)â3-29°dONLNd˜2ƒ>¯(;ƒSending an 2`°dONLNd2¯>
ú)4"Apple Event and Handling the Reply˙¿°dONLNd&2
∞>
¬)∏3-30°dONLNd+?∫Kƒ(H∫
Wï°dONLNd,?√KÏ)    orking W»Ä°dONLNd4?ÏK
6))ith Object Specifil°dONLNdF?
7K
[)Ker Recor †°dONLNdN?
[K
e)$ds#`°dONLNdR?
zK
å)3-32°dONLNdWLƒXÀ(Uƒ
D=@°dONLNdXLÃXË)ata Str``°dONLNd_LËXˇ)ucturÊ@°dONLNddLˇX
)es W‡@°dONLNdhL
X
t)ithin an Object Specifi釰dONLNdL
uX
ô)aer RecorÌÄ°dONLNdáL
ôX
ü)$
d    @°dONLNdäL
¥X
Δ)3-34°dONLNdèYƒe˜(bƒThe Classifi*@°dONLNdõY¯e
 )4
cation of w °dONLNd•Y
 e
z)(Apple Event ObjectsÄ°dONLNd∫Y
èe
°)o3-39°dONLNdøfŒr
(oŒObject Classes∂Ä°dONLNdœf
!r
3)S3-39°dONLNd‘sŒ◊(|ŒPrN†°dONLNd÷sÿ
:)
operties and Elements] °dONLNdÌs
N
`)v3-42°dONLNdÚăåÈ(âƒFinding O °dONLNd˙ÄÈå
C)%Apple Event ObjectsflÄ°dONLNdÄ
Wå
i)n3-46ˇÿ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+ú"CHAPTER à)>
34⁄*˙
¯
(‡*3-2,    Helvetica    )rContents4^*¿
¯
°dONLNd\úh (eú
About the ‡°dONLNd
\Àh
,)/Apple Event Managerª¿°dONLNd\
@h
R)u3-48°dONLNd$i¶u⁄(r¶Supporting ‡ °dONLNd/i⁄u
J)4Apple Events as a Server ˜ °dONLNdHi
Ju
~)pApplicationu@°dONLNdUi
ìu
•)I3-48°dONLNdZv¶Ç⁄(¶Supporting ‡ °dONLNdev⁄Ç
H)4Apple Events as a Client ]¿°dONLNd~v
IÇ
})oApplication€‡°dONLNdãv
ëÇ
£)H3-49°dONLNdêɶè⁄(å¶Supporting ‡ °dONLNdõÉ⁄è
4)4Apple Event ObjectspÄ°dONLNd∞É
Iè
[)o3-49°dONLNdµê¶ú⁄(ô¶Supporting ‡ °dONLNd¿ê⁄ú
-)4Apple Event Recor`°dONLNd—ê
.ú
B)TdingÑ°dONLNd◊ê
Vú
h)(3-50ˇ<Z@ˇˇˇˇˇ@

ˇ·ˇ‚7^,Palatino
&e.
3+ä"CHAPTER ”)>
3
4⁄ä˙,    Helvetica    (‡äAbout ‡)Apple Events

, (‡    3-3
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜    ˇˇ—ÚˇÆ°dONLNd8äC¬(@äIntroduction to •°dONLNd8¬CÙ)8Apple Eventsˇˇˇˇˇˇ≠>(@
3
°dONLNd\äh”(eäThis chapter intrõ°dONLNd.\”hÙ)Ioduces À‡°dONLNd5\Ùh
T)!Apple events and the ?¿°dONLNdJ\
Uh
∂)aApple Event Manager1@°dONLNd]\
∂h
Ÿ)a    . Later c;‡°dONLNdf\
Ÿh
ı)#hapter°dONLNdl\
ˆh
¸)s °dONLNdniäuê(rä
dõ¿°dONLNdoiêu
F))escribe how your application can use the ‡`°dONLNdòi
Fu
π)∂Apple Event Manager to r °dONLNd∞i
∫u)tespond to and send °dONLNd√väÇÂ(äApple events, locate Ä°dONLNdÿvÊÇ
Y)\Apple event objects, and rÄ°dONLNdÚv
YÇ
k)secorŇ°dONLNdˆv
kÇ
s)d ø@°dONLNd¯v
sÇ
∞)Apple events.°dONLNd
àäî
R(ëä+The interapplication communication (IAC) arÖ°dONLNd
1à
Rî
x)»    chitectur9¿°dONLNd
:à
yî
Ò)'e for Macintosh computers °dONLNd
Tïä°é(ûä
c@°dONLNd
Uïé°ø)onsists of fiÔ°dONLNd
bï¿°
C)2ve parts: the Edition ManagerñÄ°dONLNd
ï
C°
ù)É, the Open Scripting &‡°dONLNd
îï
û°
©)[Ar≥ °dONLNd
ñï
©°
œ)    chitecturg‡°dONLNd
üï
–°
‘)'
e1Ä°dONLNd
†ï
’°
Û) (OSA)< °dONLNd
¶ï
Û°
¯), °dONLNd
®¢äÆó(´äthe]`°dONLNd
´¢òÆö)
 °dONLNd
¨¢öÆ˚)Apple Event ManagerpÄ°dONLNd
ø¢˚Æ
T)a, the Event Manager¡‡°dONLNd
“¢
SÆ
Ö)X, and the Pr[°dONLNd
ޢ
ÜÆ
º)3ogram-to-PrTÄ°dONLNd
È¢
ºÆ
€)6ogram °dONLNd
ÔØäª˚(∏äCommunications (PPC) Tú°dONLNdØ˙ª
i)poolbox. The chapter “Intr Ä°dONLNdØ
iª
Á)ooduction to Interapplication °dONLNd;ºä»
(≈äCommunication” in this book pr°dONLNdYº
»
í)êovides an overview of the r}‡°dONLNdtº
í»
Î)xelationships among °dONLNdá…ä’†(“äthesed°dONLNdå…°’£)
 ‰°dONLNdç…£’æ)parts. °dONLNdï€äÁù(‰äThe ª¿°dONLNdô€ùÁ
9)%Apple Event Registry: Standard Suites©Ä°dONLNdæ€
:Á
M)ù defi†°dONLNd√€
NÁ
˜)&nes both the actions performed by the °dONLNdÈËäÙ´(Òästandar±Ä°dONLNdË´Ù≥)!d Ó‡°dONLNdÚË≥Ù
j))Apple events, or “verbs,” and the standarŇ°dONLNdË
kÙ
s)∏d ø@°dONLNdË
sÙ)"Apple event object classes, which °dONLNd?ıä

”(˛äcan be used to cr)Ä°dONLNdPı‘


≠)J0eate “noun phrases” describing objects on which .`°dONLNdÄı
≠

)ŸApple events act. If °dONLNdï
ä
˚(
äyour application uses the ˇ°dONLNdØ
˚

n)qApple Event Manager to r*¿°dONLNd«

o

¸)tespond to some of these standar˝°dONLNdÊ

¸
)çd °dONLNdË
ä

ö(
ä>Apple events, you can make it scriptable—that is, capable of rˇ°dONLNd&

ö

ı(

öesponding to scripts °dONLNd;
ä
(
7(
%ä(written in a scripting language such as .@°dONLNdc

7
()≠/AppleScript. In addition, your application can °dONLNdí
)ä
5´(
2äuse the ¿°dONLNdö
)¨
5
#)"Apple Event Manager to cr®¿°dONLNd≥
)
#
5
b)weate and send ć°dONLNd¡
)
b
5)?'Apple events and to allow user actions °dONLNdË
6ä
B¸(
?äin your application to be r= °dONLNd
6˝
B
)secor±Ä°dONLNd
6

B
.)ded as ë@°dONLNd
6
.
B
k)Apple events.°dONLNd
Hä
T°(
QäBeforÛ¿°dONLNd!
H°
T
¨)>e you use this chapter or any of the other chapters about the Ã@°dONLNd_
H
¨
T(
Q
¨Apple Event ManagerΩ¿°dONLNdr
H
T)a, °dONLNdt
Uä
a
õ(
^ä<you should be familiar with the chapters “Event Manager” in ⁄¿°dONLNd∞
U
õ
a
Â(
^
õInside Macintosh: °dONLNd¬
bä
n¥(
kä    MacintoshpÄ°dONLNdÀ
bµ
n∑)+
 Ä°dONLNdÃ
b∑
nΩ)
TÄ°dONLNdÕ
bº
nÃ)oolb9@°dONLNd—
bÕ
n÷)ox©Ä°dONLNd”
b÷
nÿ)    
 )Ä°dONLNd‘
bŸ
n
)Essentials 5Ä°dONLNdfl
b

n
    )+
a5Ä°dONLNd‡
b
    
n
&)nd “Prq@°dONLNdÊ
b
&
n
y)ocess Manager” in f`°dONLNd¯
b
z
n
ø)TInside MacintoshH`°dONLNd
b
¿
n
Œ)F: Pr °dONLNd
b
œ
n
Ì)ocesses.é`°dONLNd
b
Ì
n
Ô)
 °dONLNd
tä
Ä
!(
}ä"This chapter begins by describing 'Ä°dONLNd8
t
!
Ä
»)ó%Apple events and some of the data strO`°dONLNd]
t
»
Ä
fl)ßuctur’@°dONLNdb
t
fl
Ä)es they °dONLNdj
Åä
çΔ(
ääcontain. The r4°dONLNdx
Å«
ç
%)=est of the chapter intr'@°dONLNdè
Å
%
ç
Ñ)^oduces the use of the Í°dONLNd•
Å
É
ç
Ô)^Apple Event Manager to,Zapf Dingbats°dONLNdº
óä
ûè(
ùä
n
°dONLNdæ
îñ
†ô)
rE°dONLNdø
îö
†¥)espondONLNdƒ
î¥
†ø)d tr¿°dONLNd«
î¿
†«)o     ‡°dONLNd…
î»
†˛)Apple eventT†°dONLNd‘
î˛
†
)6
s°dONLNd÷
©ä
∞è(
Øä
n
°dONLNdÿ
¶ñ
≤≠)send ï`°dONLNd›
¶≠
≤¥)
A\†°dONLNdfi
¶µ
≤Á)pple events °dONLNdÈ
¶Ë
≤˘)3 to rö°dONLNdÓ
¶˘
≤
~)equest services or information°dONLNd
ªä
(
¡ä
n
°dONLNd
∏ñ
ƒˇ)work with object specififl†°dONLNd'
∏ˇ
ƒ
)ier r‡‡°dONLNd+
∏

ƒ
 )ecorU@°dONLNd/
∏
!
ƒ
+)ds°dONLNd2
Õä
‘è(
ӊ
n
°dONLNd4
 ñ
÷π)    classify ?†°dONLNd=
 π
÷
)#Apple event objects °dONLNdR
flä
Êè(
Âä
n
°dONLNdT
‹ñ
Ë≤)locate {¿°dONLNd[
‹≤
Ë
)Apple event objects°dONLNdo
Ìä
˘®(
ˆäFinally°dONLNdv
Ì®
˘ƒ), this c6`°dONLNd~
̃
˘‹)hapte‡°dONLNdÉ
Ì›
˘
)r summarizes t†°dONLNdë
Ì

˘
∏)B"he tasks you can perform with the Ì°dONLNd≥
Ì
∑
˘
Ò)òApple Event °dONLNdø
˙ä«(äManager and ˇ °dONLNdÀ
˙«Ó)=    explains R†°dONLNd‘
˙Ô
)(wher    †°dONLNdÿ
˙

¸)8e to locate information you need to perform those tasks.

H(4H(

8H@49H@ :H:

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNd%H8y(3HAbout ÃÈ°dONLNd%y8⁄)1Apple EventsˇˇˇˇˇˇU˛(3
3
°dONLNd&IäUö(RäAn 
ò†°dONLNd)IöU—)Apple eventj°dONLNd4I“U
ä)8, is a high-level event that conforms to the Ê °dONLNd`I
äU
„)∏Apple Event Interpr¯†°dONLNdsI
„U
¸)Yocess °dONLNdyVäbΔ(_äMessaging Pr_Ä°dONLNdÖVΔb˘)<otocol. The 8`°dONLNdëV˘b)3>Apple Event Manager uses the services of the Event Manager to °dONLNdœcäo°(läsend ï`°dONLNd‘c°o
ú)5Apple events between applications on the same compute. °dONLNd        c
ùo
†)¸
rc`°dONLNd
c
†o
™), bΰdONLNd    c
™o)
etween applications on °dONLNd    $pä|ç(yä
rE°dONLNd    %pé|⁄)emote computers‚¿°dONLNd    4p⁄|Ú)L, or fr„¿°dONLNd    ;pÚ|
g)om an application to itself.ˇLÜ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-4    )BAbout ‡)Apple Events4^*¿
¯
°dONLNd\lh·(elApplications typically use ˆ†°dONLNd\·h
-)uApple events to r˚@°dONLNd,\
-h
√)L"equest services and information frn@°dONLNdN\
ƒh
Ó)ó    om other °dONLNdWilu≈(rlapplications or to pr€°dONLNdli≈u
_)Y#ovide services and information in rjÄ°dONLNdèi
`u
¨)õesponse to such rC`°dONLNd†i
¨u
—)L    equests. °dONLNd©vlÇ
c(l4Communication between two applications that support 쇰dONLNd›v
cÇ
Ê)˜Apple events is initiated by a 
°dONLNd¸Élèæ(ålclient application,©¿°dONLNd
Éæè
)R which sends an ü‡°dONLNd
É
è
N)IApple event to rgÄ°dONLNd
/É
Oè
‹)H!equest a service or information. °dONLNd
Pêlú(ôlThe ª¿°dONLNd
TêúΩ)application prπ¿°dONLNd
bêΩú
3)>oviding the service or the rL °dONLNd
~ê
4ú
¿)w equested information is called a
ÎÄ°dONLNd
ûê
¿ú
‡)å server °dONLNd
¶ùl©¢(¶lapplication.¢ °dONLNd
≤ù¢©
Q)6) The client and server applications can r?†°dONLNd
€ù
R©
Û)∞$eside on the same local computer or °dONLNd
ˇ™l∂}(≥lon r‡°dONLNd™~∂
9)(emote computers connected to a network. ‡°dONLNd+™
9∂
∫)ªAn application can also send Z@°dONLNdH™
∫∂
˜)ÅApple events °dONLNdU∑l√
0(¿l0to itself, thus acting as both client and serverp†°dONLNdÖ∑
0√
5)ƒ. p†°dONLNdá∑
5√
7)
 †°dONLNdà∑
7√
9)
 °dONLNdä…l’Ñ(“lFigurR¿°dONLNdè…Ñ’ò)e 3-1@°dONLNdî…ò’È) shows a common ~`°dONLNd§…Í’
œ)R0Apple event, the Open Documents event. The FindeÔ@°dONLNd‘…
œ’
ÿ)Âr iJ@°dONLNd◊…
Ÿ’
fl)
s °dONLNdŸ÷l‚y(fllthe]`°dONLNd‹÷z‚|)
 ›`°dONLNd›÷|‚•)client; it rkÄ°dONLNdÈ÷¶‚

)*equests that the SurfWfi‡°dONLNdˇ÷
    ‚
–)c+riter application open the documents named °dONLNd*„lÔq(Ïl
“°dONLNd+„qÔÑ)Dec.˜ °dONLNd/„ÑÔÜ)
 w °dONLNd0„áÔû)Invoi´ °dONLNd5„ûÔ≥)ce” ae°dONLNd:„¥Ôπ)
n6`°dONLNd;„∫Ô’)d “NoñÄ°dONLNd@„’Ô⁄)
v!°dONLNdA„⁄Ô˙). Invoic≈@°dONLNdI„˙Ô
) e.” T؆°dONLNdN„
Ô
8)he SurfWö†°dONLNdV„
8Ô
Ö))riter application r °dONLNdi„
ÖÔ
‰)Mesponds to the Finderå°dONLNd~„
ÊÔ
Ô)a’s °dONLNdÅl¸o(˘l
rE°dONLNdÇp¸Ë)equest by opening window„ °dONLNdö˸

)xs for tÄ°dONLNd°
¸
+)    he specifi߆°dONLNd´
+¸
k))ed documents.


*
/
¯4
*
/
¯"
*]

ˇ·ˇ‚7^
    °dONLNdπ
l
ñ(
l
Figure 3-1°dONLNdƒ
Æ

)BAn Open Documents event
°dONLNd›l)Œ(&lThe Finder is considerà‡°dONLNdÛŒ)
)b@ed the client application for the Open Documents event shown in °dONLNd3*l6Ñ(3lFigurR¿°dONLNd8*Ñ6ò)e 3-1@°dONLNd=*ò6
))# because the Finder initiates the rv°dONLNd`*
*6
È)í-equest for a service. The Finder can also be °dONLNdç7lCë(@lconsider‡°dONLNdï7íC√)&ed the sourH@°dONLNd†7√C
©)12ce application for the same Open Documents event. -`°dONLNd“7
©C
∞)Ê
Ah°dONLNd”7
∞C
≤)
 
Ë°dONLNd‘7
≤C
—)source °dONLNd€DlPü(Mlapplication" °dONLNdÊD†Pø)4 for an — °dONLNdÓDæP
O)!Apple event is one that sends an K†°dONLNdD
PP
Ï)í#Apple event to another application °dONLNd2Ql]≈(Zlor to itself. Similarly(‡°dONLNdIQ≈]ˆ)Y, the SurfWV@°dONLNdTQˆ]
·)18riter application can be described as either the server °dONLNdå^lj»(glapplication or the tar¿°dONLNd¢^…j
√)]6get application for the Open Documents event shown in 3‡°dONLNdÿ^
√j
€)˙Figur†°dONLNd›^
€j
Ô)e 3-1§ °dONLNd‚^
Ôj
Ù). °dONLNd‰klws(tl
A∫†°dONLNdÂkswu)
 
:†°dONLNdÊkvw»)target application ˜@°dONLNd˘k»w‰)Rfor an &@°dONLNdkÂw
_)Apple event is the one addrÄ¿°dONLNdk
_w
à)z
essed to r&†°dONLNd%k
âw
∑)*eceive the 
`°dONLNd0k
∑w
Ú).Apple event. °dONLNd=xlÑö(Ål
The terms K`°dONLNdGxõч)/client applicationÕ¿°dONLNdYx‡Ñı)E and ∫‡°dONLNd^xˆÑ
)sourS‡°dONLNdbx
Ñ
?)ce applicationd¿°dONLNdpx
?Ñ
J)7 ar©¿°dONLNdsx
JÑ
‹)e not always synonymous, nor ar¿°dONLNdíx
݄
Ù)ìe the °dONLNdòÖlëá(élterms †°dONLNdûÖàëœ)server applicationù °dONLNd∞Öœë‰)G and ä@°dONLNdµÖÂë)tar`°dONLNd∏ÖÒë
&)get applicatio» °dONLNdΔÖ
&ë
.)5n.◊@°dONLNd»Ö
.ë
6) Tí°dONLNd Ö
6ë
Y)ypically¿°dONLNd“Ö
Xë
j)", an ≥°dONLNd◊Ö
jë
Ò)Apple event client application °dONLNdˆílûï(õl    sends an #¿°dONLNdˇíïû—))Apple event r≥Ä°dONLNdí—û
?)<equesting a service to an ‡°dONLNd&í
@û
Õ)o Apple event server application; 


.d
¯4
/d
¯


0k
¯4
/j
0kò@@
˜@
˜
0k
pb¡¡?‡ˇ¯‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?Èˇ˛˝˛ˇ¸‰?Èˇ˛˝˛ˇ¸‰?Èˇ
˛˛˛ˇ¸‰?Èˇ
˛˛˛ˇ¸‰?Èˇ˛ IJˇ¸‰?Èˇ˛ @˛ˇ¸‰?Èˇ˛!Á¯˛ˇ¸‰?Èˇ˛¯˛ˇ¸‰?Èˇ˛¿Ä˛ˇ¸‰?Èˇ˛Ç`˛ˇ¸‰?Èˇ˛
ê˛ˇ¸‰?Èˇ˛˛ˇ¸‰?Èˇ˛
‰˛ˇ¸‰?Èˇ˛!R˛ˇ¸‰?Èˇ˛"©˛ˇ¸‰?Èˇ˛DQ˛ˇ¸‰?Èˇ˛ Ñ)˛ˇ¸‰?Èˇ˛ à4˛ˇ¸‰?Èˇ˛!"˛ˇ¸‰?Èˇ˛!Q˛ˇ¸‰?Èˇ˛"hIJˇ¸‰?Èˇ˛‘@˛ˇ¸‰?Èˇ˛ ™ ˛ˇ¸‰?Èˇ˛ ï˛ˇ¸‰?Èˇ˛ äà˛ˇ¸‰?Èˇ˛ ÖD˛ˇ¸‰?Èˇ˛
 Ƕ˛ˇ¸‰?Èˇ˛êAY˛ˇ¸‰?Èˇ˛P@π˛ˇ¸‰?Èˇ˛0 a˛ˇ¸‰ò@@Ä
˜@Ä
˜
pk
∞b?Èˇ˛#˛ˇ¸‰?Èˇ˛ ˛ˇ¸‰?Èˇ˛@˛ˇ¸‰?Èˇ˛Ä˛ˇ¸‰?Èˇ˛˝˛ˇ¸‰?Èˇ˛˝˛ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰ò@Ä¿
˜Ä¿
˜
∞k
b?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰ò@¿

˜¿

˜
k0b?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰?‡ˇ¸‰‡ˇ¸‰¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡    ˛èÉĬ»    ˛ÑÅ
.»

Ñ
"»

á
$»
H::$»
HÇ"D»
ˇ¡é»¡¡¡¡¡–0ÄÄ¿˛˛Äÿ@HÄ@ ˛˛Äÿ—d
õ*-Ç"4uñ›¡Èm¿ÿ≤ä8
ç=VÑ%\ö´J™¥Äÿ$ñúàI)‰Ñ)ÖíÚQ«O%◊3DS“âÑJ∑$DÿDTMÄÿ'8ÚyÑE•<ìÉ£…◊˛
Ä˚Õ˛
Ä˚Õ
˛˙Õ¡¡'?É
¿ÄË
˝Ä‡@
ć>
Ê&
≈ÄÄ@
1¸@@Ä@
Ê)%¶Ì ÀJHÀíl@-mdlò∫-ÄvˆC¢˘&« 1JDÈ€∏Áò@

@
˜

@
˜0kpb)%î™
4ïΩIU4@V¶¨¥©RVÄöH•eQSBP3ΩJ*È@Á)%d≤
%9%)í&)$@•BdîÄíâ)."íDêI)ú OJ8Á)%)"M¢>R⁄ˇ:L#©    M€ˆ©Å&—K:Û§Δ†äR–"TõÁ)%-ß#I)åë*$HIIE…"§I§êç≠"DÑAùåé|#ípÁ¸@ı ˘
‚¸@ı ˘
‚˘
Ï
‚¡¡¯Ä 0Δ
1ÄÄÿPÄ˝I)J@ÄÿR/Ïπ&√Æ$    )Wq’ÜÇäUŒâ@⁄VPëQSD2P8ÓÍÄU)CÑâ˙ê)W†⁄¢œbíCƒ‡RLp¶KÇàìKπ ⁄ÛÉ£Û§¿ËÄFRñ´Zî•ÇZ"@⁄¢›"¢Dá^t9åd‡“mÕûcm›Ä⁄ÙÄ˚ ŸÙÄ˚ ŸÙÄ˚ Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡˛Ä8Õ˛ÄƒÕ
äR!
5îéV±Äœ
ùÍQöªî®“ÄœIL·ííπ»îŒRñÄç$$Ì    5ÄœÏdpr%∏ç" œ˛
IJ 
Ã˛
IJ 
Ã˛
IJ  ¡¡ÄÉ¿4˛@–@Å 
$@–K¬$ylwb
%ˆ\V—îÇ í¥••'(H®®—%íî•))Igâ1(—=ÇTeMnjm¡—˘P—)(‚I∫DFInëPê—¸

˛Äø

˛ÄÃ˚‡»¡¡    ¯Ä`0À    PÄêHÀ    R/Ï∏¨àÀ    VPëQPpàÀ    ¢œbPàÀ    ÛÉ£Ú†àêÀ    ¢›"° r`Àò@
@
Ä
˜
@
Ä
˜pk∞b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜∞kb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜k"b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜
0k
pb
¡¡fl30‰fl‰ ¬fl‰fl‰fl‰ ¬fl‰ ¬fl‰fl‰fl‰ ¬Ù0Ô‰ @˘0˙

¿›˛e˙˜ææ˙
 ˚‰˛AY‹˙fiˇ>ˇ~˙
ç•∞˝‰˛A}(˙3fi¯0¯~˘‡˝‰ Ea(˙3˜øœ˙1 fl˛9]$˘Δˆ
œ‡˝‰ ÙΔ–fl‰fl‰˛˝˜ˇ‡¸ ˝‰ ˝˜0¸@fl
gs39∏˜    0

ùÃÃʇ˛‰
 ÙÀOöd
˜"    0
Ä”->iê‡
îÀDödˇ¸˜    1ˇˇ¿S-iê˛‰$ws;â§>¸    1`
›ÃÓ&ê˛‰"@˛àÎààÿ˛àéà±0˙‰ @˛
àc˜p€‹ˇéÔ1‹˙
àcfl¯fivˇfl˜‡1¯‰ ˚
"c˛z˛rˇ˙ˆ210⁄˙ˇˆ>˜¯Ûfiœ˜‡1ˇˇ`¯‰¯¿˙0
¿˙‰¯àà»˙à∞
Ä˙‰ ˇˇ˛˝˜0˝
 Ä›˛Ä˝˜0˝
 @˚‰ Ä˝˜ˇ˝!Á¯fi˛üˇÚ˝˜0˝¯¸‰˛üˇ˝˜0˝¿Ä˝‰˛üˇ˝˜0˝Ç`˝‰ ü˝˜0˝
êfl˛ü˝˜0˝˝‰ ü˝˜0˝
‰fl˛ü˝˜0˝!R˝‰˛ü˝˜0˝"©˝‰"˛ü˝˛0˝DQ˝‰ ü¿˝¸0˝ Ñ)fl"˛ü¿˝f“À00˝ à4˝‰ ê˝˘+,¯0˝!"fl"˛ò2˝à-,@0˝!Q˝‰"˛èˇ‚˝wC(À∏0˝"hÄ˝‰˛Ä˝˜0˝‘@˝‰ Ä˝˜0˝ ™ fl˛Ä˝˜0˝ ï˝‰ ÄÚ˝"˛0˝ äàfl ˛Ä˝2¸0˝ ÖD˝‰"˛Ä˝*i“À00˝
 Ƕ˝‰!˛Ä˝*ï+,¯0¸êAY˝‰ Ä˝&ñ-,@0¸P@πfl!˛ˇˇ˛˝"dC(À∏0¸0 a˝‰ò@@Ä
˜@Ä
˜
pk
∞b
 @˝˜0¸#fl˛@˝˜0¸ ˝‰˛@˝˜0¸
@¸‰˛ˇ¸˝˜0¸
ĸ‰ ¯˜0◊˜˜0ı‰ ¯˜0◊˜˜0ı‰˛
|¸˜0˝‡HÄ˝‰˛
@¸˜0˛
H˝‰ EŒl˝˜0˝…nÆ濇˛}2¯˝˜0˝9F¥üIJ‰ E2à˝˜ˇ˛
E¥òć˛E.x˝˜ˇ˝ÁEèIJ‰fl‰fl‰ ¬fl‰ ¬fl‰
²¸‰
Âä¸‰ ÊÇfi
Âí¸‰ Ê¢fi
ÂǸ‰
ÂΔ¸‰
Âä¸‰ ÊÇfi
Âí¸‰ Ê¢fiÊÉÄ˝‰Ê
G¸‰Ê

é¸‰ ÊÃfi
Âx¸‰ Ê0fifl‰fl‰fl‰ ¬È˘ˇ
¿‰ Í@˘`„È@¿¸
`‰È
@QDT@`‰È
@HÄÿ`‰ Í    @  `„È
@
QDT@`‰ Í@˘`„È˘ˇ
‡‰È@˙ `‰͢ˇ¸`‰ ΢
`„Íø˝
Ô˛`‰ Î
°à¿
È~`„Í°œ`ŸöŸÈ~`‰Í°ø`ŸöŸÔ~`‰Í°èdŸöŸË~`‰ Îø˝
Ô˛`„͢`‰ ΢ˇ
˛`„Í˙f`‰Í˙ˆ`‰Í˙û`‰ò@Ä¿
˜Ä¿
˜
∞k
b
 Î˙æ`„Í̸¶`‰ Îï!˝Ê`„ÍÌ&˝˛`‰Íù)˝`‰ÍÌ'˝`‰ Î˙`„Í˙`‰ Î˙`„Íà˝`‰Íÿ$˝`‰Í› ÙÈî`‰ Î
≠%*ùT`„Í™ÍÌH`‰ Î
Ä`„ÍÄ`‰ÍpÄ2`‰ÍIJ≤`‰ Î
eáiö€2`„ÍD]c‰Ñ `‰ Î
ÁDM[õCJ`„Í˚@`‰Í˚@`‰Í˙`‰ Î˙`„Í˙`‰ Î˙`„Í˙`‰Í˙`‰Í˙`‰ Î˙`„Í˝`‰ Îà˛`„Íés¿0§Ç`‰Íéı†§Ç`‰Í˜”†6$Ç`‰ Î

õ`„Í`‰ Î ¸`„Í`˛€`‰Íb˛1$Ç`‰Ín˛§Ç`‰ Îö˛4dÇ`„Íö˛õ`‰ θ`„Í˙`‰Í¸¸`‰ÍÑ˛`‰ Î
Ô@0§Ç`„Í醧Ç`‰ Î
é†6$Ç`„͸õ`‰Í
˚ˇ¬‡‰Í
˝`‰ Î

˜˚@õ`„ÍH£@2dɲ`‰ Î
H£@dÇÊ`„ÍH§¿5‰Ç¶`‰ÍG$õæ`‰Í¸∑‡‰ Î˙Á‡„Í˙F‰ ΢ˇ˛‚Í˙‰ò@¿

˜¿

˜
k0b
Í˙ˆ‰Í˙6‰ Î˙
ˆ‚Í˙ñ‰ Î˙
ˆ‚͢ˇ˛‰͢ˇ˛‰fl‰ ¬fl‰ ¬fl‰fl‰fl‰ ¬fl‰ ¬fl‰‡UT‰flÉ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡    ˛èÉĬ»    ˛ÑÅ
.»

Ñ
"»

á
$»
H::$»
HÇ"D»
ˇ¡é»¡¡¡¡¡–0ÄÄ¿˛˛Äÿ@HÄ@ ˛˛Äÿ—d
õ*-Ç"4uñ›¡Èm¿ÿ≤ä8
ç=VÑ%\ö´J™¥Äÿ$ñúàI)‰Ñ)ÖíÚQ«O%◊3DS“âÑJ∑$DÿDTMÄÿ'8ÚyÑE•<ìÉ£…◊˛
Ä˚Õ˛
Ä˚Õ
˛˙Õ¡¡'?É
¿ÄË
˝Ä‡@
ć>
Ê&
≈ÄÄ@
1¸@@Ä@
Ê)%¶Ì ÀJHÀíl@-mdlò∫-ÄvˆC¢˘&« 1JDÈ€∏Áò@

@
˜

@
˜0kpb
)%î™
4ïΩIU4@V¶¨¥©RVÄöH•eQSBP3ΩJ*È@Á)%d≤
%9%)í&)$@•BdîÄíâ)."íDêI)ú OJ8Á)%)"M¢>R⁄ˇ:L#©    M€ˆ©Å&—K:Û§Δ†äR–"TõÁ)%-ß#I)åë*$HIIE…"§I§êç≠"DÑAùåé|#ípÁ¸@ı ˘
‚¸@ı ˘
‚˘
Ï
‚¡¡¯Ä 0Δ
1ÄÄÿPÄ˝I)J@ÄÿR/Ïπ&√Æ$    )Wq’ÜÇäUŒâ@⁄VPëQSD2P8ÓÍÄU)CÑâ˙ê)W†⁄¢œbíCƒ‡RLp¶KÇàìKπ ⁄ÛÉ£Û§¿ËÄFRñ´Zî•ÇZ"@⁄¢›"¢Dá^t9åd‡“mÕûcm›Ä⁄ÙÄ˚ ŸÙÄ˚ ŸÙÄ˚ Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡˛Ä8Õ˛ÄƒÕ
äR!
5îéV±Äœ
ùÍQöªî®“ÄœIL·ííπ»îŒRñÄç$$Ì    5ÄœÏdpr%∏ç" œ˛
IJ 
Ã˛
IJ 
Ã˛
IJ  ¡¡ÄÉ¿4˛@–@Å 
$@–K¬$ylwb
%ˆ\V—îÇ í¥••'(H®®—%íî•))Igâ1(—=ÇTeMnjm¡—˘P—)(‚I∫DFInëPê—¸

˛Äø

˛ÄÃ˚‡»¡¡    ¯Ä`0À    PÄêHÀ    R/Ï∏¨àÀ    VPëQPpàÀ    ¢œbPàÀ    ÛÉ£Ú†àêÀ    ¢›"° r`Àò@
@
Ä
˜
@
Ä
˜pk∞b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜∞kb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜k"b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜"kbb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜bk¢b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜¢k‚b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜‚k"b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜"kbb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜bk¢b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜¢k‚b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜‚kb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜"kbb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜bk¢b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜¢k‚b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜‚k"b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜"kbb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜bk¢b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜¢k‚b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜‚kb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇE@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äAbout ‡)Apple Events

, (‡    3-5
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh
H(eä/in this case, the server application is the tarc‡°dONLNd/\
Hh
´)æget application for the ‡°dONLNdG\
´h
Ê)cApple event. ›@°dONLNdT\
Êh
Ì);
A‡°dONLNdU\
Óh) server °dONLNd]iäuÿ(räapplication may r_°dONLNdniÿu
v)N&eturn information to the client in a r£‡°dONLNdîi
vu
ã)ûeply ¿°dONLNdôi
åu)Apple event—in which case, °dONLNd¥väÇ
(ä!the client application is the tarº¿°dONLNd’v
Ç
v)Öget application for the rm °dONLNdÓv
wÇ
ä)heplydONLNdÚv
âÇ
ã)
.†°dONLNdÛv
åÇ
é)
 dONLNdÙv
éÇ
ê)
 °dONLNdˆàäîê(ëä
Tµ¿°dONLNd˜àèîî)
o+@°dONLNd¯àïî“) perform the rú°dONLNd
à“î
ï)=,equested service—that is, to open the specifiÄ°dONLNd
3à
ñî
Ó)ƒed documents—the °dONLNd
Dïä°¶(ûäSurfWP°dONLNd
Iﶰ
)riter application shown in FÄ°dONLNd
dï
°
3)uFigur@°dONLNd
iï
3°
G)e 3-1∂¿°dONLNd
nï
G°
O) fiCÄ°dONLNd
qï
P°
Ñ)    rst uses the ˇ@°dONLNd
~ï
É°
Ú)3Apple Event Manager to °dONLNd
ï¢äÆ
o(´ä2identify the event (the Open Documents event) and (Ä°dONLNd
«¢
pÆ
{)Êto ``°dONLNd
 ¢
{Æ
—)dispatch the event t†°dONLNd
ޢ
“Æ
ˆ)Wo SurfW⁄ °dONLNd
¢
ıÆ)#riterq °dONLNd
Í¢    Æ)’s °dONLNd
ÌØäªè(∏ä
hQ`°dONLNd
ÓØꪓ)andler for that ‡°dONLNd
˛Ø“ªÙ)BApple efi°dONLNdØÙª
)"vent. @°dONLNdØ
ª
)An 
‡°dONLNdØ
ª
z)Apple event handler¯°dONLNd!Ø
zª
Ÿ)] is an application-defik†°dONLNd8Ø
⁄ª)`ned function °dONLNdEºä»

(≈äthat extracts pertinent data fr˚‡°dONLNddº

»
()Äom an ∏`°dONLNdjº
(»
¢)Apple event, performs the r0‡°dONLNdÖº
£»){equested action, and °dONLNdö…ä’∑(“ä(usually) r‡°dONLNd•…∏’‚).
eturns a rÒ°dONLNdØ…·’
M))esult. In this case, SurfWŸ`°dONLNd……
M’
_)lriterp`°dONLNdŒ…
a’
˙) ’s Open Documents event handler °dONLNdÓ÷ä‚Δ(fläexamines the Ö†°dONLNd˚÷Δ‚
])< Apple event to determine which d1¿°dONLNd÷
^‚
˛)ò#ocuments to open (Dec. Invoice and °dONLNd>„äÔù(ÏäNovŒ‡°dONLNdA„úÔû)
.N‡°dONLNdB„üÔ°)
 Œ‡°dONLNdC„°Ôº)Invoics °dONLNdI„ΩÔ«)e),†°dONLNdL„»Ô
&) then opens them as rB`°dONLNda„
&Ô
R)^
equested. °dONLNdlıä

ê(˛ä
Tµ¿°dONLNdmıè

º)o identify y¿°dONLNdxıº


)-Apple events and r≥†°dONLNdäı



G)Tespond apprh@°dONLNdïı
H


o)8    opriately"†°dONLNdûı
o


Ÿ)', every application can r`°dONLNd∑ı
Ÿ


ˆ)jely on £`°dONLNdæı
ˆ


˝)a °dONLNd¿
ä
è(
ä
v&@°dONLNd¡
ê
Î)ocabulary of standarˇ¿°dONLNd’
Í
Ú)Zd = °dONLNd◊
Û

ä)    !Apple events that developers and X@°dONLNd¯

ä
)óApple have established for all °dONLNd
ä

(
ä"applications to use. These events Ü °dONLNd9



%)ìarK °dONLNd;

&

>)    e defi܇°dONLNdA

>

l)ned in the T¿°dONLNdL

m
)/&Apple Event Registry: Standard Suites.¬Ä°dONLNdr

)ü
 °dONLNds
ä
(æ(
%äThe standarÌ@°dONLNd~
æ
(Δ)4d 
â°dONLNdÄ
«
(›)    suiteº¿°dONLNdÖ
›
(„)s,≠°dONLNdá
‰
(˚) or gri@°dONLNdç
¸
(
#)    oups of r≥`°dONLNdñ

#
(
@)'elated Æ¿°dONLNdù

@
(
ô)Apple events that arQ†°dONLNd±

ö
(
)Ze usually implemented °dONLNd«
)ä
5Æ(
2ätogether£@°dONLNdœ
)Æ
5
)$, include the RequirD¿°dONLNd„
)

5
M)Wed suite, the CorëÄ°dONLNdÙ
)
M
5
ª)He suite, and functional-arê@°dONLNd
)
ª
5)nea suites such as °dONLNd 
6ä
B†(
?äthe T °dONLNd%
6†
B©)ex`°dONLNd'
6™
B∫)
t su‡°dONLNd+
6∫
B
)ite and the Databas°dONLNd>
6

B
 )Ue suú¿°dONLNdB
6
 
B
6)ite. TΔ‡°dONLNdH
6
5
B
„))o function as a server application, your °dONLNdq
Cä
O
(
Läapplication should be able to rM¿°dONLNdê
C

O
[)Üespond to all the ¿¿°dONLNd¢
C
[
O
—)KApple events in the Requir$‡°dONLNdº
C
“
O
)wed suite and °dONLNd…
Pä
\Ó(
Yäany of those in the Cor¢`°dONLNd‡
PÓ
\
A)de and functional-arh†°dONLNdÛ
P
B
\
∫)T ea suites that it is likely to r·°dONLNd
P
∫
\
Î)xeceive. For °dONLNd
]ä
ifi(
fäexample, most wor‘¿°dONLNd0
]fi
iÒ)Td-prÄ°dONLNd4
]Ú
i
≥),ocessing applications should be capable of rå`°dONLNd`
]
≥
i
ˇ)¡esponding to the °dONLNdq
jä
vË(
säApple events in the TT†°dONLNdÜ
jË
v
¸)^?ext suite, and most database applications should be capable of °dONLNd≈
wä
Éç(
Ää
rE°dONLNdΔ
wé
É
E)*esponding to those in the Database suite. °dONLNdÒ
âä
ïæ(
íäIf necessaryg@°dONLNd˝
âΩ
ï
))3, you can extend the defioÄ°dONLNd
â
)
ï
Ü)lnitions of the standar0 °dONLNd,
â
á
ï
è)^d mÄ°dONLNd.
â
è
ï
◊)Apple events to °dONLNd>
ñä
¢ß(
üämatch X°dONLNdD
ñ®
¢ƒ)specifiΔ °dONLNdK
ñƒ
¢
X)$c capabilities of your application. k‡°dONLNdo
ñ
Y
¢
_)ï
Y,`°dONLNdp
ñ
_
¢
£)ou can also defi˜†°dONLNdÄ
ñ
£
¢)Dne your own custom °dONLNdì
£ä
Ø(
¨äApple events; however`°dONLNd®
£
Ø
)f, beforÙ°dONLNdØ
£

Ø
#)e defi/¿°dONLNdµ
£
$
Ø
›)(ning custom events, you should check witª¿°dONLNd›
£
›
Ø
Â)πh °dONLNdfl
∞ä
ºö(
πäthe °dONLNd„
∞ö
º∑)Apple |Ä°dONLNdÈ
∞∏
º
)Event Registrar t≤°dONLNd˙
∞

º
)Jo fi¥@°dONLNd˛
∞

º
V)nd out whether ¢`°dONLNd
∞
W
º
ò)Gyou can adapt –°dONLNd
∞
ò
º
Ω)A    existing îÄ°dONLNd$
∞
Ω
º
ı)%Apple event °dONLNd0
Ωä
…ö(
Δädefir °dONLNd4
Ωõ
…ÿ)nitions or defi4¿°dONLNdC
ΩŸ
…
`)>nitions still under developmen*`°dONLNda
Ω
a
…
j)àt t/ °dONLNdd
Ω
j
…
Û)    o the needs of your application>°dONLNdÉ
Ω
Û
…
¯)â. °dONLNdÜ
ϊ
€˝(
ÿäBy supporting the standarıÄ°dONLNdü
œ˝
€
)sd 2‡°dONLNd°
œ

€
ß)    $Apple events in your application, yoÆ@°dONLNd≈
œ
ß
€
¥)°u eˇ°dONLNd»
œ
¥
€
»)nsurŸÄ°dONLNdÃ
œ
»
€
˙)e that your °dONLNdÿ
‹ä
Ë
(
Âäapplication can communicate ef≥@°dONLNdˆ
‹

Ë)å:fectively with other applications that also support them. °dONLNd    0
Èä
ı
(
ÚäInstead of supporting many difx†°dONLNd    N
È

ı
 )äfer[ °dONLNd    Q
È
 
ı
€)*ent custom events for a limited number of °dONLNd    {
ˆä
(
ˇä applications, you can support a ¥ °dONLNd    õ
ˆ

)ç
ry °dONLNd    ú
ˆ

C)
elatively Ω@°dONLNd    ¶
ˆ
C
Ø)(small number of standar
@°dONLNd    Ω
ˆ
∞
∏)md G†°dONLNd    ø
ˆ
∏)Apple events that °dONLNd    —ä
G(ä)can be used by any number of applications·@°dONLNd    ˙
G
L)Ω. °dONLNd    ˝ä!ê(ä
Y@Ä°dONLNd    ˛ê!˛)ou can begin supporting v@°dONLNd
˛!
√)n+Apple events by making your application a r;°dONLNd
A
ƒ!
)Δeliable server °dONLNd
P"ä.Δ(+äapplication: fiC†°dONLNd
_"«.¯)=rst for the rî°dONLNd
l"¯.
)1equir´@°dONLNd
q"
.
)ed ≤@°dONLNd
t"
.
z)Apple events, then fo2 °dONLNd
â"
{.
Ñ)_r tÁ °dONLNd
å"
Ñ.
û)    he cor¨‡°dONLNd
í"
ü.
Ω)e and f∑Ä°dONLNd
ô"
Ω.
Ú)unctional-ars °dONLNd
•"
Û.
ˇ)6ea °dONLNd
®/ä;Á(8äApple events as appr°dONLNd
º/Ë;
á)^$opriate. Once your application can r†°dONLNd
‡/
á;
⁄)üespond to the apprYÄ°dONLNd
Ú/
⁄;
˚)Sopriate °dONLNd
˙<äH´(Eästandar±Ä°dONLNd
<´H≥)!d Ó‡°dONLNd<≥H
;)Apple events, you can make it 
Ä°dONLNd!<
<H
c)â    scriptabl¿°dONLNd*<
dH
k)(e,í¿°dONLNd,<
kH
¨) or capable of r5@°dONLNd<<
≠H
È)Besponding to °dONLNdIIäUû(Räinstró¿°dONLNdNIûU
®)<uctions written in a system-wide scripting language such as Õ¿°dONLNdäI
®U
Î(R
®AppleScript. If °dONLNdöVäb¥(_ä    necessary4‡°dONLNd£V¥b
B)*!, your application can also send ‹°dONLNdƒV
Ab
)ç0Apple events to itself or to other applications.°dONLNdıhätΩ(qä“About the ‡°dONLNdhæt
)4Apple Event Manager˛`°dONLNdh
t
%)`,”~`°dONLNdh
&t
s) which begins on Ó¿°dONLNd&h
st
ä)Mpage …†°dONLNd+h
ãt
ù)3-48Ä°dONLNd/h
ût
¨), pr‰†°dONLNd3h
¨t
›)
ovides morô†°dONLNd=h
fit
Â)2e °dONLNd?uäÅ
Ç(~ä8information about the steps you need to take to support °dONLNdwu
ÉÅ
‚)˘Apple events in your °dONLNdåÇäé¿(ãäapplication. ˇ"h@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-6    )BAbout ‡)Apple Events4^*¿
¯
°dONLNd\lh∏(elThe next section, *@°dONLNd\πh
)M“Apple Events and 퇰dONLNd$\
h
q)VApple Event Objects,”£@°dONLNd9\
qh
µ)b describes how ^†°dONLNdH\
µh
Ú)DApple events °dONLNdUilu
Ë(rlUcan describe data and other items within an application or its documents. Subsequent °dONLNd™vlÇÎ*sections describe the basic orôÄ°dONLNd»vÎÇ
')ganization of ø°dONLNd÷v
'Ç
©)<Apple events and the data strÕ`°dONLNdÛv
©Ç
¿)ÇucturS@°dONLNd¯v
¡Ç
”)es frÚ¿°dONLNd˝v
ӂ
„)om °dONLNd
Élè®(ålwhich they ar‡°dONLNd
É©èÀ)=e constrb†°dONLNd
ÉÀèË)"ucted. 

¥*ª
¯4µ*ª
¯ ∂l∂
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd
•l¥€(∞lApple Events and Ùé°dONLNd
.•⁄¥
O)nApple Event Object@Í°dONLNd
@•
P¥
V)v
sˇˇˇˇˇˇ€r)†
3
°dONLNd
Cªl«
(ƒl"The Open Documents event shown in Ä°dONLNd
eª
«
.)™Figur”@°dONLNd
jª
-«
A)e 3-1p¿°dONLNd
oª
B«
ê), like the other thr‡°dONLNd
ɪ
ë«
°)Oee rÓ °dONLNd
áª
†«
∑)equir`°dONLNd
åª
∏«
Ê)ed events, °dONLNd
ó»l‘à(—lspecifiÓ °dONLNd
û»à‘
ÿ)Mes an action and the applications or documents to which that action applies. °dONLNd
Î’l·(filThe ª¿°dONLNd
Ô’·
)%Apple Event Registry: Standard Suites©Ä°dONLNd’
·
()ù pr†°dONLNd’
(·
fi)*ovides a vocabulary of actions for use by °dONLNdA‚lÓy(Îlall –¿°dONLNdE‚yÓΩ)applications. InÙÄ°dONLNdU‚ΩÓ
e)D( addition to a vocabulary of actions, efö‡°dONLNd}‚
fÓ
ı)©fective communication between °dONLNdõÔl˚®(¯lapplications r∏‡°dONLNd©Ô®˚ø)<equir– °dONLNdÆÔø˚
)es a method of rß¿°dONLNdæÔ
˚
≤)G&eferring to windows, data (such as wor1 °dONLNd‰Ô
≥˚
Ô)≠ds or graphic °dONLNdÚ¸l
ñ(
l    elements)=‡°dONLNd˚¸ó
¢)+, fiJ†°dONLNdˇ¸¢

b)-les, folders, volumes, zones, and other discr‹¿°dONLNd,¸
b

Í)¿ete items on which actions can °dONLNdK
    l
¿(
lbe performed. The b`°dONLNd]
    ¿

$)TApple Event Manager ë@°dONLNdq
    
$

O)d
includes r °dONLNd{
    
P

Ü),outines that Á†°dONLNdà
    
Ü

ñ)6allo-‡°dONLNdå
    
ó

¶)w a‡°dONLNdè
    
ß

Ù)ny application to °dONLNd°
l
"á(
lconstrï °dONLNdß
á
"ë)ucÄ°dONLNd©
í
"¬)t or interpr6Ä°dONLNdµ
¬
"Δ)0
e °dONLNd∂
«
"—)t “¬Ä°dONLNdπ
—
"
´)
1noun phrases” that describe the objects on which &°dONLNdÍ

¨
"
¯)€Apple events act.°dONLNd¸
(l
4†(
1lMost of the ≤Ä°dONLNd
(†
4È)4Apple event defio`°dONLNd
(Í
4
&)Jnitions in the Ó‡°dONLNd'
(
&
4
¬)<%Apple Event Registry: Standard Suites‹†°dONLNdL
(
√
4
Ë)ù     include °dONLNdU
5l
A|(
>ldefir °dONLNdY
5}
A©)nitions of 
£‡°dONLNdd
5©
A
#),Apple event object classes,Õ°dONLNd
5
#
A
L)z     which ar‰`°dONLNdà
5
L
A
ı))'e simply names for objects that can be °dONLNdØ
Bl
NÊ(
Klacted upon by each kind of Y¿°dONLNd 
BÊ
N
!)zApple event. F °dONLNd◊
B
!
N
1);An 
^¿°dONLNd⁄
B
1
N
É)Apple event objec °dONLNdÎ
B
Ñ
N
á)S
ts°dONLNdÏ
B
á
N
£) is any¯‡°dONLNdÛ
B
£
N
”) distinct ite› °dONLNd
B
‘
N
fl)1m °dONLNd
Ol
[Ó(
Xlsupported by an application t9†°dONLNd
OÔ
[
Ï)É8hat can be described within an Apple event. Apple event °dONLNdW
\l
h
(
el[objects can be anything that an application can locate on the basis of such a description, °dONLNd≤
il
u
p*;including items that a user can differentiate and manipulatÑ`°dONLNdÌ
i
p
u
≤(
r
pe while using a¿°dONLNd¸
i
≥
u
Ú)Cn application, °dONLNd
vl
Ç
y(
l;such as words, paragraphs, shapes, windows, or style format)¿°dONLNdF
v
z
Ç
Ä(

zs.Ê¿°dONLNdH
v
Ä
Ç
Ç)
 °dONLNdJ
àl
îê(
ëlThe defi≠‡°dONLNdR
àê
î“)$nition for each ¬ °dONLNdb
à“
î
Z)B Apple event object class in the Δ¿°dONLNdÇ
à
Z
î
∂)àApple Event Registry: °dONLNdò
ïl
°ë(
ûlStandard∂@°dONLNd†
ïë
°ì)%
 6@°dONLNd°
ïî
°≠)Suites6‡°dONLNdß
ï≠
°
E)" determines only how that kind of ±@°dONLNd…
ï
E
°
«)òApple event object should be °dONLNdÊ
¢l
Æñ(
´l    describedZ†°dONLNdÔ
¢ó
Æô)+
 ⁄†°dONLNd
¢ô
Æ≈)
within an ZÄ°dONLNd˙
¢Δ
Æ
b)-#Apple event, not how it should be rÄ°dONLNd
¢
c
Æ
q)ùepr≠@°dONLNd 
¢
q
Æ
›)esented internally by an °dONLNd9
Øl
ª”(
∏lindividual application. ·°dONLNdQ
Ø”
ªŸ)g
Y°Ä°dONLNdR
ØŸ
ª
Î)?ou do not have to write your application in an object-oriented °dONLNdë
ºl
»u(
≈lprG °dONLNdì
ºv
»–)
ogramming languagé`°dONLNd§
º–
»⁄)Ze t`°dONLNdß
º€
»
)
o support $`°dONLNd±
º

»
…)-,Apple event objects. Instead, you need to orè`°dONLNd›
º
…
»
Ë)¡ganize °dONLNd‰
…l
’⁄(
“lyour application so that i&@°dONLNd˛
…€
’ı)ot can i톰dONLNd
…ı
’
)nterpr)¿°dONLNd
…

’
&)et a r˙¿°dONLNd
…
&
’
M)    equest fo˜°dONLNd
…
N
’
^)(r sp®¿°dONLNd
…
_
’
q)ecifi◊¿°dONLNd#
…
q
’
w)c i†°dONLNd%
…
x
’
«)Apple event objec¬ °dONLNd6
…
«
’
Ô)Ots, locate °dONLNdA
÷l
‚ö(
fllthe objectsÍÄ°dONLNdL
÷ö
‚
Y).*, and perform the requested action on themh`°dONLNdv
÷
Z
‚
\)¿
.°dONLNdx
Ël
ÙÑ(
ÒlFigurR¿°dONLNd}
ËÑ
Ùò)e 3-2@°dONLNdÇ
Ëò
ÙÈ) shows a common ~`°dONLNdí
ËÍ
Ù
Å)R"Apple event, the Get Data event frπ`°dONLNd¥
Ë
Å
Ù
≤)ó
om the Cor1¿°dONLNdæ
Ë
≥
Ù
Ú)2e suite. In this °dONLNdœ
ıl
ü(
˛lexample, th °dONLNd⁄
ı†
¿)4e SurfC¸ °dONLNd·
ı¿

â) 2harter application is the client application; it r=`°dONLNd    
ı
ä

Ò) equests data contained °dONLNd    *lõ(lin a specifi߇°dONLNd    6õÈ)/c table in a SurfW‡°dONLNd    HÈ
6)Nriter document. Tg@°dONLNd    Y
5
^)L
o obtain t`°dONLNd    c
_
≥)*he data it wants, thw¿°dONLNd    w
≥
”)Te SurfCe¿°dONLNd    ~
‘
Ò)!harter °dONLNd    Öl
B(l1application must include a description of the datˆÄ°dONLNd    ∂
B
W)÷a in tÚ†°dONLNd    º
X
Ÿ)he Get Data event it sends to °dONLNd    ⁄l(à(%lSurfWP°dONLNd    flà(ö)riterl@°dONLNd    ‰ö(
). This description identifi;¿°dONLNd    ˇ
    (
()oes the r‰¿°dONLNd

((
l)equested data a€ °dONLNd

m(
~)Es aniÄ°dONLNd

(
â) A∞¿°dONLNd

â(
Ú)
pple event object called °dONLNd
5)l5Ñ(2la tabl≤`°dONLNd
;)Ñ5»)e. The table is n*Ä°dONLNd
L)…5
‚)E;amed “Summary of Sales” and is located in a document named °dONLNd
á6lB±(?l“Sales Report.” °dONLNd
òHlT
:*.The SurfWriter application’s Get Data handler m¿°dONLNd
ΔH
;T
Δ)œ extracts information about the r)°dONLNd
ÊH
«T
Ë)åequest, °dONLNd
ÓUlaπ(^llocates the specifi‚†°dONLNd
Uπa¯)Med table, and rˆ °dONLNdU¯a
")?
eturns a rœ@°dONLNdU
"a
7)*esult¿°dONLNdU
8a
Â)%. The Apple Event Manager provides a °dONLNdDbln
ˆ(klXreply Apple event to which the SurfWriter application adds the requested information in °dONLNdúol{
‰*Rthe form requested by the Get Data event. The Apple Event Manager sends the reply °dONLNdÓ|là
k*:event back to the SurfCharter application, which can use tÎÄ°dONLNd(|
kà
æ)ˇhe requested data i◊‡°dONLNd;|
øà
Û)Tn whatever °dONLNdFâlï
3(íl-way is appropriate—in this case, displaying i∂¿°dONLNdsâ
3ï
I)«t as a6 °dONLNdyâ
Jï
u) pie chart.ˇnû@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äAbout ‡)Apple Events

, (‡    3-7
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHw4gHw"hH]

ˇ·ˇ‚7^    °dONLNd\äg¥(dä
Figure 3-2°dONLNd\Ãg“)B
A0°dONLNd\“g
) Get Data event


√H
 4
ƒH
  
Ŋ
≈

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd
¥ä
√◊(
øäApple Event j»°dONLNd)
¥◊
√
v)MAttributes and Parametersˇˇˇˇˇˇ€r(
ø
3
°dONLNdD
…ä
’(
“äWhen an application cr)‡°dONLNdZ
…Ò
’
F)geates and sends an Õ`°dONLNdm
…
E
’
ê)TApple event, the  °dONLNd~
…
ë
’
)LApple Event Manager uses °dONLNdó
֊
‚í(
fläarE°dONLNdô
֓
‚Ë)    guments passed to †°dONLNd´
÷Ë
‚
P)UApple Event Manager r¯Ä°dONLNd¿
÷
O
‚
ò)goutines to constrD‡°dONLNd—
÷
ô
‚
⁄)Juct the data str °dONLNd·
÷
€
‚
Ú)Bucturû°dONLNdÊ
÷
Ú
‚)es that °dONLNdÓ
„ä
Ô√(
Ïämake up the µ°dONLNd˙
„√
Ô˛)9Apple event. °`°dONLNd

„˛
Ô
);An [†°dONLNd


„

Ô
˙)7Apple event consists of attributes (which identify the °dONLNd
A
ä
¸(
˘äYApple event and denote its task) and, often, parameters (which contain information to be °dONLNd
ö
˝ä    À*used by the tar%°dONLNd
©
˝Ã    
)Bget application). °dONLNd
ºäö(äAn 
ò†°dONLNd
øö˚)Apple event attributeT†°dONLNd
‘¸
)b is a rø°dONLNd
€

%)ecor3`°dONLNd
fl
&
b)d that identifi{‡°dONLNd
Ó
b
È)<!es the event class, event ID, tar °dONLNd
È
˘)áget °dONLNdä(
U(%ä0application, or some other characteristic of an ‘Ä°dONLNdC
U(
ñ)ÀApple event. TU°dONLNdQ
ñ(
“)Aaken together"`°dONLNd^
“()<, the attributes °dONLNdo)ä5¢(2äof an º`°dONLNdu)¢5
Ω)>Apple event denote the task to be performed on any data specifi€¿°dONLNd¥)
Ω5
Â(2
Ω
ed in the y‡°dONLNdæ)
Ê5))Apple °dONLNdƒ6äB‚(?äevent’s parameters. ¡ °dONLNdÿ6‚BÈ)X
A˚¿°dONLNdŸ6ÈB
:) client application Q°dONLNdÌ6
;B
L)Rcan †°dONLNdÒ6
MB
W)usV¿°dONLNdÛ6
WB
^)
e B°dONLNdı6
^B
e)
A    @°dONLNdˆ6
fB
Δ)pple Event Manager r5‡°dONLNd
6
ΔB)`outines to add °dONLNdCäOœ(Läattributes to an b`°dONLNd*CœO

)EApple event. N¿°dONLNd7C

O
');After r≠Ä°dONLNd>C
'O
[)eceiving an ˚Ä°dONLNdJC
[O
Á)4 Apple event, a server applicatioáÄ°dONLNdjC
ËO)çn can u°†°dONLNdqCO) se °dONLNdtPä\Ú(YäApple Event Manager rs‡°dONLNdâPÚ\
∑)h/outines to extract and examine its attributes. 

wá
ú4wà
ú

wä
ú4vâwäò@@
˜@
˜wä∑Å¡¡?‘ˇ˛?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇò@@Ä
˜@Ä
˜∑ä˜Å?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?‹ˇ˝˝ˇ?‹ˇ˝˝ˇ?‹ˇ
p˛˝ˇ?ˇˇ˛‡
„ˇ
à˛˝ˇ?ˇˇ˛`
„ˇ
Ò˛˝ˇ?ˇˇ˛Ä
„ˇ
Ò˛˝ˇ?ˇˇ˛
¡„ˇÒ?¿˝ˇ?ˇˇ˛!„ˇü¿0˝ˇ?ˇˇ˛„ˇ^Ã˝ˇ?ˇˇ˛ …„ˇ<˝ˇ?ˇˇ˛B•„ˇÄ˝ˇ?ˇˇ˛ D    S„ˇ @@˝ˇ?ˇˇ˛ ࣄˇ Ä ˝ˇ?ˇˇ˛A S„ˇAê˝ˇ?ˇˇ˛A@#„ˇÅ%H˝ˇ?ˇˇ˛B@%„ˇÇ Bà˝ˇ?ˇˇ˛B Ä„ˇÒ ¡H˝ˇ?ˇˇ˛D Ä
„ˇÒA†à˝ˇ?ˇˇ˛$!
„ˇÒAê˝ˇ?ˇˇ˛$A
„ˇÒÇàp˝ˇ?ˇˇ˛A?
„ˇÒÉD˝ˇ?ˇˇ˛G„
„ˇêÜ¢˝ˇ?ˇˇ˛O„}„ˇëQ˝ˇ?ˇˇ˛
¯„˝„ˇA®Ä˝ˇ?ˇˇ˛¯„無1T@˝ˇ?ˇˇ˛=„無* ˝ˇ?ˇˇ˛:˜ç„ˇ    0˝ˇ?ˇˇ˛=Λ„ˇÇ
»˝ˇ?ˇˇ˛:˜≠„ˇÇ»˝ˇ?ˇˇ˛}Λ„ˇ
Å˝ˇ?ˇˇ˛∫˜≠„ˇÄÅ˝ˇ?ˇˇ˛}Λ„ˇA¯˝ˇ?ˇˇ˛∫˜≠„ˇ"˝ˇ?ˇˇ˛}Λ„ˇ˝ˇ?ˇˇ˛Ôæ˘„ˇ˝˝ˇ?‹ˇ˝˝ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇò@Ä¿
˜Ä¿
˜˜ä
7Å?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇò@¿

˜¿

˜
7ä
wÅ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇò@

@
˜

@
˜
wä
∑Å?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ?”ˇ”ˇ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡

0»

    »»
à»
ê»
êËx†»
ëâ@»
˛x»¡¡¡ò@
@
Ä
˜
@
Ä
˜
∑ä
˜Å¡¡¿``
¿É‡ 
“Äêê Å 
“OF–¡rÖ“€Ä”R…(p 
Ç•
Ui“íYp@    }…ûJ“Ãr@àÄ1Ç'Ô®õ“úZ8p3Éœ≈JG퓲"≈˛"≈˛≈¡¡(}
‡@8˛DÅ$ 
¿|Ê&)ä˛Äƒ¸@

  Ä$Ê)%)Lfl+*î£/E±µµë⁄2‰õ
o¨éâÙ[@bîà#•æpÁ)%1TjTWz•RJ—
Zö≤jUEM5Uí§≠†gzî8™‘ÄÁ)%—dL‰íSHîíëRíñLâäI&d¥I) íS8A<òpÁ)%bDûàٕΈ’0é§$ûøŒìO"¨ÂÌSA•†EQ<Á)%sNåîx£D§â q%%îJâFJ!6≤HíÉ;¯è(‡Á˝
˛
 ıĢ
 ‚˝
˛
 ıĢ
 ‚˘
 Ï
 ‚¡¡$Ä√0aÅÿ  ˛
$§$í
ÿ$≤Ù[úê$•\ÁTrî+∏9%Ÿ    ,¬E$≠•@„ª©
T•Èu@RfiÄ⁄
EºII)ÄI0‚ô..¶8ó‰Ä⁄gèmSí
JX"≠h!(À¥âŸEÙäHí=–Ê1ë√I∑6<«2p€ˆŸı˙@Ÿı˙@Ÿı˙@Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡
‡Õ
Õ§D÷R8¨fŒ;‘§jÓQP    ™Œíôƒ    JJ„ê    0Œ•-:êì≤ vŒÿ»·ƒîb··H@œ˛!˝ÄÃ˛!˝ÄÃ
˛!˝Ä ¡¡˛–<Ä∏¸@÷ÇÄ@(

(@÷ò@
Ä
¿
˜
Ä
¿
˜
˜ä7Åó≟÷»Hú°uä
)ˆ\V‡ÿ*JjìTH°AÊZñ+(H®©◊L
&RL¢dQB"íºQgâ1(‡ÿ~    )îù¥Ëëá¬#§&y¡—˘P ÿTìàñ‰êø:ár•FQnëPë¿ÿ¸@
˝ÄÄ“¸@
˛Ä“¸
Ä˚œ¡¡     ¿¿À      
! À    $≤Ú∞" À        ,¬E%@‚ À
EºII@ À    gèjÅ@À    EÙäDÄÂÄÀ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜7äiÅ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜wä∑Å
¡¡”32”
 ‘¡”
¡ ‘”
 ‘¡”
¡ Ì`
ÄÎÏ`
Ä0Ó
 ÌÛ˝∏ÌÛ¯ÓÏÛw˝˜˚‹Ì
õw·á√Ó
Ì
õ˝ºˆ{¯‹ Ì
0ÍÏ
0Í
 ‘¡ıˇÒ
ˆà
âć Ûˆ

ÄÚÚ¿ˆ

ÄÚ
 Û`ˆ"
#åÚÛ¯8˛
‡¿˝
è·Ù¸˛0c`¿˛
à¿Ù
Ù˛àéè˚ˇ¸˛àâà‚  ıp˛„ofi˛
à
¿ıı¿˛<c{ˆ˛
àpı
! ˆˇ8˛"#˜ÛÔ˛˛"#è¿ıı8Ňˆ
Ä„ı‡¿
Ĉ
Ä
¸
¿ˆ
ˆÄ8˛ˆàâÄp‰ ˜‡˛ˆ
Ä
¿ˆˆIJıˇÄpˆ
 ˜
p˝ˆ
Ä
Ęˆ
¿8˝ˆ
Ŀ˜
ć˝ˆ
Ä
¿`˜
˜Ä˝ˆ

IJ
p0Â ¯
¸ˆ

IJ
˜!˜
¸~à˛˛

IJ
˜
# ¯
08¸ à˛˛

IJ
˜˜
``¸ò|Èé6Üp˛

IJ
ÅÄÊ!˜
¿¿¸|>õ…}Oê˛

Ä˝
¿¿¯
¯
Åĸ`2ö    MHê˛

Ä˝
``Ê# ˘
˚\È…=Gp˛

Ä˝
00¯¯
˚ˆ

Ä˝
¯
 ˘
˚ˆ

Ä˝
¯¯
0˚ˆ

Ä˝
Ê ¯
 ˚
W˝8
Ä˝
ܯ
¯
`˚XIJD
ĸÉÊ" ˘
0¿˚Nç§n1ñ8
ĸ¡¯!¯
`Ä˚
ÕJü$îfl`
ĸ
AĢ
# ˘
AÄ˚ÕJìîFX
ĸ
`Ģ¯√˙=Jèd9◊p
ĸ
0¿Á˘

Ç˙˝˚

ĸ
`˘
˘

˙˝ ˚

ĸ
 Á ˙
˙ˆ

ĸ
0˘˘
˙@ ˚
ĸ
˘
ò@@Ä
˜@Ä
˜∑ä˜Å
# ˙
˙( ˛@
ĸ
˘"¸ 0˙\~`Ïi–‹ÓfÜp
ĸÈ'˝(@ ˙R)Ò2ô©ÚIıOê
ĸÄ˚
&˝
Œ‡
‡˙R)Å2â©IïHê
ĸ
ám,¿Ï) ˛È@¯RpÏw®Ú)uGp
Ä˚ůæIJ˝+    @¯ˆ

Ä˚¡à–IJ
" ˛
 È ¯ˆ

ĸÅxéIJˆ

ĸ

ÅÁW˝

Ä˚¡˘
XÑ`˝

Ä˚cÁ& ˝@¯4«nf‡˝

Ä˚:`
˝$¸į
˝Ï˘î@˝

Ä˚@˝
) ;ôôÕ¿˘Õâî@˝

Ä˚Ófg7˛$˛¶Z|” ˘<Ó~d ˝

Ä˙ôiÛLÄÌ$˛¶Z$” ˘˝˚

Ä˙ôhìLÄ
!˛ªô‹M ˘˝˚

Ä˙Ógq4ÄÌ ˛"ıˆ

Ģà˚˝"ıˆ

Ģà˚
 Òˆ

ÄÚ
ıˇÄ‡ıˇÄÚ
¡ €p˚¸
‡·à˚
 ˝
`‚

˚¸
Ä‚

È˝
¿„
?¿˝
˝ ‚ü¿0Î ˛‚^Ã˝˝ »‚<˝
 ˛B§‚IJ˝ D    R‚ @@Ï˝ ࢂ Ä ˛
˝A R‚AêÏ ˛A@"‚Å%H˛˝B@$‚Ç Bà˛
 ˛B Ä„
 ¡H˛˝D Ä‚
A†àÏ˝
$!·
Aê˛
˝$A‚
ÇàpÏ ˛A?‚
ÉD˝˝G„·êÜ¢˝
 ˛O„|‚ëQ˝˝
¯„¸‚A®ÄÏ˝¯„å‚1T@˛
˝=„å‚* Ï ˛:˜å‚    0˛˝=΋‚Ç
»˛
 ˛:˜¨‚Ç»˛˝}΋‚
ÅÏ˝∫˜¨·ÄÅ˛
˝}΋·A¯Ï ˛∫˜¨·"¸˝}΋·¸
 ˛Ô毀¡”
¡ ‘€
¿    !˝
 ,Ä‚  @˛˛ÄrÄ„
ì∫≠ÌÄÌ˛N‡Êo∞„s…_˛
˛
Ã`üG‡‰3…QÏò@Ä¿
˜Ä¿
˜˜ä
7Å
 ÃbôF ‰
œI/˛˛<\óC‡‹
 ‘¡”
¡ ⁄
Ä˝‹<¿˝
 ›'Ä`˝¸
‡„a0θ
`„C4P˝
¸
†„¬8¯Î ˝ ¿ÊÇ@˝¸ 
‡Á
Ü    @˝
 ˝ 
8Á

@˝¸ 
Á@θ`
Á@˝
¸†

ÄË¿Î ˝ 
Á@˝¸ 
Á0    @˝
 ˝ 
Á
@˝¸ 
AÄË`@θ`
‡ÄË@@˝
¸† ¿Ë0@¿Î ˝ 0`Ë`¿@˝¸ 0Ë@Ä    @˝
 ˝ Ë¡Ä
@˝¸ È

ɲ
@θ`È
˛
@˝
¸†È
˛
¿Î ˝ 
ÇÈ
˛
@˝¸
 ˛ÉÈ
0˛
    @˝
 ˝
 ˛
¡ÄÍ
 ˛

@˝¸
 ˛
`¿Í
0`˛
@θ
`˛
0pÍ
`¿˛
@˝
¸
†˛
Î
¡Ä˛
¿Î" ˝
 ˛
¯`¿˜
˝
@˝#¸
 ˛
¯`¿˙
˝
    @˝
& ˝
 ˛
ĢÛfi¯ÌÛº˙
˝

@˝ ¸
 ˛
¿¿˘Û{˝˜˚ÿ˙
p˝
@Î$¸
`˝
`p˙
õ{·á√ÿ˙
¿0˝
@˝
!¸
º˝
0˙
õfi¸ˆ{‹˚ć˝
¿Î" ˝
˝
˘
˜
Ä˝
@˝ ¸
0˝Ä˙
˜
¸
¿˝
 ˝
`˝Ó
ˆ¸

¿˝
ÄÔÄ0‰˚ĸ‡Ä?ˆˇ˛ <‡ˆ
ı8(ˆàãq‡
ĉ ˆ‡ ˆ
flıı
¿?¸ ˆ˙ˇ˛
 ıxı"#
@˙&˙ˇ‡ ˝˝˛@˙Ó,@˙0¿ ˝Ä˝x˛@˛
-{Ô˝˛(˝à窛˝àã¿˛@å»Ã»Ó0
 z/ Ä/K˛
ˇÙ ˝IJé˝
@
  -
z/¨ÿÃØK¸
 ˝„˝¯˝
@@DP
&
 z/¨òÃØ{˚¸"/øˇ˝"#˝@˙#
z/¨fiÃØC˚ ¸
˝˚@˙Ó$
{Ô¨fiÃØ˚ ¸
˝˚˘ˇ

˙ˇ˚(ˆàã˚@˚
Ó @˚
0˚ ˆ˚@˚@˚
0˚?ıˇ˚@˚
! @˚
∞˚ ˆ˚
@ƒH"
Aê˚ ˆ˚@@HÓò@¿

˜¿

˜
7ä
wÅ
$
BP0˚ ˆ˚
@eíyÄ
"
B∏l“Ã0˚ ˆ˚@WóKÄÓ$
 BUËô˚‹0˚ ˆ˚
@Wy¿'
AîËiö¯˚
 p˝
Å˝˚@˚
$ @˚
0˚
 à˝
$A˝˚@˚'@˚
0˚ d¥–⁄Fs3Ä˚@Ä®Ó)@˚
0˚ ™©ÚI fl~˛˚
@ĮP
*B ˛
0˚ 噩1I$SAÄ˚@ΔÆX¿Ó,
 B 0˚ s™®ÒÜ#è?˛˚
@©^U¿(
C©€jq6@0˚ ˛
˙˚
@¶\T‡
%
 Bi4™ìƇ0˚ ˛˙˚@˚
Cë”fqßp0˚ ˆ˚@˚
Ó'@¸
0˚ f0ÿ3«˚@˚
(@!¸
0˚ ôHS LÄ(˚@ÄÓ) @˚
0˚ Hì LÄ.˚
@Ñ)@˚
0˚ )H
¿
LÄ¡˚
@K1îÄ
) @˚
0˚ ôH
     LÄ    ˚
@ÔrΩ¿'@˚
0˚ f0
¿3Ê˚@k·ú–Ó@˚
0˚ ˆ˚@˚
@˚
0˚ ˆ˚@˚
Ó @˚
0˚ ˆ˚@˚@˚
0˚ ˆ˚@˚
 @˚
0˚ ˆ˚@˚@˚
0˚ ˆ˚@˚
Ó@˚
0˚?ıˇ˚@˚
@˚
0˚ıˇ˚@˚
Ó @˚
0Ë@˚@˚
0Ë@˚
 @˚
0Ë@IJ0@˚
0Ë@NögC0Ó@˝`0Ë
@MU5D†
@N¥ŒÜ`0ˇÎ
˛@ÕUTƒ†Ó  @Mjjâ@0
¿Ï@=U4É @
Mj©â@0@Ï@˝Ä
  @=ji@0`Ï@˛
@˛
0 Ï@Ñ˝
Ó @˛0 Ï@då˛
@˚0 Ï@5P˛
Ó  @‚˛0 Ï@’»˛ @
F0 Ï@4ú˛
 @Œ®0 Ï@˚@6‰0 Ï@˚
Ó@
ŒN0 Ï@˚
@˚0 Ï@˚
Ó @˚0 Ï@˚@˚0 Ï@˚
 @˚0 Ï@˚@˚0 Ï@˚
Ó&@9 0 8˛Ä@ı@˚
)@Ä
–0 $@¸
ĸ@˚
Ó. @Δ`˚∞0 %üû≤Y¿˝

@
@˚0@)ëΩ‹H0?ˇ¯'œãÃ˘~@˝
\ÈÜKsøˇ¯@˝ˇ¿
1 @iì34∞0 &Lä¡¢@˝
“õœ/…@@/@íÏ0 9«âƒπ¿˝2ö4I@@Ó(@ÊfOv0 Ù<È«#»Ä@Δbê@
#@åŒ0 Û
ĸ
@)íh@Ó% @ª0 Û
ĸ@iíÿ@'@ˇ›0 @Û@í    $@
, @ˇ0
@¯

˛@Êbÿ@*@ã0 {4
ÓL¯

@@Ó,@F0 4™ô^¯ÀÄ@@
*@ä0 4™ôP¯/•@@Ó+ @&0 3*ÓN¯,!@˝ˇ¿)@10 ¸à˜ÀúÄ@@
ò@

@
˜

@
˜
wä
∑Å
( @1¢,,p0 ¸àˆ˛@@"@»Ë∏R@0 ˛
@@Ó$@»}‡6`0 ¸Ú@vb    ú@
%@»H0 ˝ Ù
@IíP@Ó( @>` 4∑9ù3pÙ@iíÿ@%@˚0`z¸íS|†Ù@í@
% @˚0¿CDíSD Ù@fbÿ@#@˚Ä:<âù;êÙ
Ä@@Ó@˚∞˛˚
Ò˛@@
@˚
0˙
@˝ˇ¿Ó @˚
0Ë@˚˙ˇˢˇ

 @˚
0Ë@˚@˚
∞Ë@˚
Ó@˚
∞Ë@˚
@˚
∞Ë@˚
Ó @˚
∞Ë@˚@˚
0Ë@˚
 ˙ˇˢˇ
?˙ˇË?˘ˇÓ”
¡ ‘”
 ‘¡”
¡ ‘”
 ‘¡”U”Ã¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡

0»

    »»
à»
ê»
êËx†»
ëâ@»
˛x»¡¡¡ò@
@
Ä
˜
@
Ä
˜
∑ä
˜Å
¡¡¿``
¿É‡ 
“Äêê Å 
“OF–¡rÖ“€Ä”R…(p 
Ç•
Ui“íYp@    }…ûJ“Ãr@àÄ1Ç'Ô®õ“úZ8p3Éœ≈JG퓲"≈˛"≈˛≈¡¡(}
‡@8˛DÅ$ 
¿|Ê&)ä˛Äƒ¸@

  Ä$Ê)%)Lfl+*î£/E±µµë⁄2‰õ
o¨éâÙ[@bîà#•æpÁ)%1TjTWz•RJ—
Zö≤jUEM5Uí§≠†gzî8™‘ÄÁ)%—dL‰íSHîíëRíñLâäI&d¥I) íS8A<òpÁ)%bDûàٕΈ’0é§$ûøŒìO"¨ÂÌSA•†EQ<Á)%sNåîx£D§â q%%îJâFJ!6≤HíÉ;¯è(‡Á˝
˛
 ıĢ
 ‚˝
˛
 ıĢ
 ‚˘
 Ï
 ‚¡¡$Ä√0aÅÿ  ˛
$§$í
ÿ$≤Ù[úê$•\ÁTrî+∏9%Ÿ    ,¬E$≠•@„ª©
T•Èu@RfiÄ⁄
EºII)ÄI0‚ô..¶8ó‰Ä⁄gèmSí
JX"≠h!(À¥âŸEÙäHí=–Ê1ë√I∑6<«2p€ˆŸı˙@Ÿı˙@Ÿı˙@Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡
‡Õ
Õ§D÷R8¨fŒ;‘§jÓQP    ™Œíôƒ    JJ„ê    0Œ•-:êì≤ vŒÿ»·ƒîb··H@œ˛!˝ÄÃ˛!˝ÄÃ
˛!˝Ä ¡¡˛–<Ä∏¸@÷ÇÄ@(

(@÷ò@
Ä
¿
˜
Ä
¿
˜
˜ä7Å
ó≟÷»Hú°uä
)ˆ\V‡ÿ*JjìTH°AÊZñ+(H®©◊L
&RL¢dQB"íºQgâ1(‡ÿ~    )îù¥Ëëá¬#§&y¡—˘P ÿTìàñ‰êø:ár•FQnëPë¿ÿ¸@
˝ÄÄ“¸@
˛Ä“¸
Ä˚œ¡¡     ¿¿À      
! À    $≤Ú∞" À        ,¬E%@‚ À
EºII@ À    gèjÅ@À    EÙäDÄÂÄÀ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜7äiÅ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜iä©Å¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜©äÈÅ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜Èä)Å¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜)äiÅ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜iä©Å¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜©äÈÅ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜Èä)Å¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜)ä[Å¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜iä©Å
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜©äÈÅ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜Èä)Å
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜)äiÅ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜iä©Å
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜©äÈÅ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜Èä)Å
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜)ä[Å
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ%¢@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-8    )BAbout ‡)Apple Events4^*¿
¯
°dONLNd\lh|(elAn 
ò†°dONLNd\|h‰)Apple event parameterÄ°dONLNd\Âh¸)i is a rn‡°dONLNd\¸h
)ecor„@°dONLNd#\
h
é)d containing data that the tar °dONLNdA\
èh
Î)Åget application uses. °dONLNdWiluå(rlUnlike c¿°dONLNd^iåu
Î) OApple event attributes (which contain information that can be used by both the °dONLNd≠vlÇ
(lApple Event Manager and the tarÄ¿°dONLNdÃv
Ç
J)îget application), H@°dONLNdfiv
JÇ
)J$Apple event parameters contain data °dONLNd
Élèƒ(ålused only by the tarc`°dONLNd
Ƀè
W)X"get application. For example, the &°dONLNd
8É
Wè
·)ìApple Event Manager uses the °dONLNd
Uêlú
‹(ôlWevent class and event ID attributes to identify the server application’s handler for a °dONLNd
¨ùl©à*specifiÓ °dONLNd
≥ùà©é)c °dONLNd
µùè©
≤)AApple event, and the server application must have a handler to pr•¿°dONLNd
ˆù
≤©
ˆ(¶
≤ocess the event °dONLNd™l∂ã(≥lidentifiV†°dONLNd™å∂
◊) Led by those attributes. By comparison, the list of documents contained in a °dONLNdZ∑l√
…(¿lMparameter to an Open Documents event is used only by the server application. Ɔ°dONLNdß∑
…√
Ó(¿
…As with °dONLNd؃l–
(Õl)attributes, a client application can use ˝¿°dONLNdÿƒ
–
|)®Apple Event Manager rÒ†°dONLNd̃
|–
Ú)houtines to add parameters °dONLNd—l›Ñ(⁄lto an ™‡°dONLNd—Ñ›
O).Apple event, and a server application can use Ê`°dONLNd;—
O›
∑)ÀApple Event Manager r⁄@°dONLNdP—
∑›
Â)houtines to °dONLNd[filÍ
$(Ál)extract and examine the parameters of an ¯`°dONLNdÑfi
$Í
z)∏Apple event it has r¡@°dONLNdòfi
{Í
û)Weceived.°dONLNd°l¸t(˘l
NŒ‡°dONLNd¢t¸ó)    ote that H °dONLNd´ò¸
)$Apple event parameters ar%‡°dONLNdƒ
¸
!)ve difô‡°dONLNd…
!¸
-)fer|`°dONLNdÃ
-¸
D)ent frÚ†°dONLNd“
D¸
§)om the parameters of RÄ°dONLNdÁ
•¸
¿)aApple–°dONLNdÏ
¿¸
¬)
 °dONLNdÌ˝l
    Ö(
lEvent`°dONLNdÚ˝Ü
    à)
 ü`°dONLNdÛ˝à
    ‡)Manager functions. û@°dONLNd˝‡
    
V)XApple event parameters ar|°dONLNd˝
V
    
a)ve r䆰dONLNd"˝
a
    
s)ecorˇ°dONLNd&˝
s
    
y)
d¿°dONLNd'˝
z
    
©)s used by tZ`°dONLNd2˝
©
    
≥)/heı`°dONLNd4˝
≥
    
µ)

 °dONLNd5˝
∂
    
—)AppleîÄ°dONLNd:˝
—
    
”)
 Ä°dONLNd;˝
‘
    
)Event °dONLNdA

l
˝(
lManager; function parameters ar≥@°dONLNd`

˝

)ëe ar¡‡°dONLNdd




“)-guments you pass to the function or that the °dONLNdë
l
#ó(
 l
function r”@°dONLNdõ
ó
#÷)+eturns to you. }`°dONLNd™
◊
#›)@
Y=‡°dONLNd´
›
#
5)ou can specify both Û°dONLNdø

4
#
ö)WApple event parameterN¿°dONLNd‘

õ
#
µ)gs and Ä°dONLNd⁄

µ
#
º)
A·¿°dONLNd€

º
#
Ì)pple event °dONLNdÊ
$l
0ë(
-l    attributezÄ°dONLNdÔ
$í
0õ)&s i‡°dONLNdÚ
$ú
0„)
n parameters to ò¿°dONLNd
$„
0
¡)G0Apple Event Manager functions. For example, the ,
Courier°dONLNd2
1l
=∫(
:lAEGetParamPtr{ °dONLNd?
1∫
=
)N function uses a bufâ °dONLNdS
1

=
-)Vfer to r °dONLNd[
1
.
=
µ)eturn the data contained in an Ó °dONLNdz
1
¥
=
Ï)ÜApple event °dONLNdÜ
>l
Jô(
Gl    parameterS†°dONLNdè
>ô
Jû)-. &°dONLNdë
>û
J§)
YÊÄ°dONLNdí
>£
J∞)ou „ °dONLNdï
>±
J¬)can §¿°dONLNdô
>√
J‹)specifZ°dONLNdü
>›
Jı)y the h °dONLNd•
>ı
J¸)
A/`°dONLNd¶
>˝
J
W)pple event paramete—@°dONLNdπ
>
W
J
¡)Zr whose data you want i•`°dONLNd–
>
¬
J
⁄)kn one@°dONLNd’
>
€
J
›)
 á@°dONLNd÷
>
›
J
Ë)of °dONLNdŸ
Kl
WÃ(
Tlthe parameters of the “ °dONLNdÔ
KÃ
W
)`AEGetParamPtrÕ@°dONLNd¸
K

W
A)N     function[Ä°dONLNd
K
B
W
D)(
.


u*
|
¯4
v*
|
¯ 
wl
w
¯

ˇ·ˇ‚7^°dONLNd
hl
vt(
rl
AÅ°dONLNd
ht
v∞)pple Event fi@°dONLNd
hØ
v·);
Attributesˇˇˇˇˇˇ‘@(
r
Ò
3
°dONLNd
|l
à±(
ÖlApple events arL¿°dONLNd.
|≤
àŸ)F    e identifim°dONLNd8
|Ÿ
à
ª)'5ed by their event class and event ID attributes. The 

¿°dONLNdm
|
º
à
Ì)„event class. °dONLNdx
|
Ì
à
Ô)1
 °dONLNdy
âl
ï‚(
ílis the attribute that identifi™°dONLNdó
â‚
ï˛)ves a gr¿°dONLNdû
âˇ
ï
")oup of r‡°dONLNd¶
â
"
ï
?)#elated @°dONLNd≠
â
?
ï
Ù))Apple events. The event class appears in °dONLNd÷
ñl
¢|(
ülthe ›`°dONLNd⁄
ñ|
¢¶)message⁄¿°dONLNd·
ñ¶
¢Æ)* figÄ°dONLNd‰
ñØ
¢˘)    eld of the event rÓ@°dONLNdˆ
ñ˘
¢
)Jecorb†°dONLNd˙
ñ

¢
1)    d for an -`°dONLNd
ñ
1
¢
—)%$Apple event. For example, the four rœ@°dONLNd'
ñ
—
¢
Ë)†equirÊÄ°dONLNd,
ñ
Ë
¢
ı)ed °dONLNd/
£l
ØÏ(
¨lApple events have the value Ö¿°dONLNdK
£Ï
Ø
)Ä'aevt'ÉÄ°dONLNdQ
£

Ø
.)$ in the ö†°dONLNdY
£
.
Ø
X)messageò°dONLNd`
£
X
Ø
`)* fi$¿°dONLNdc
£
a
Ø
∂)    elds of their event r√Ä°dONLNdx
£
∂
Ø
»)Uecor7‡°dONLNd|
£
…
Ø
Î)ds. The °dONLNdÑ
∞l
ºÜ(
πlvalue _`°dONLNdä
∞á
º´)'aevt'] °dONLNdê
∞´
º‰)$ can also be rO‡°dONLNdû
∞‰
ºÚ)9epr‡†°dONLNd°
∞Ú
º
4)esented by the  °dONLNd∞
∞
5
º
è)CkCoreEventClassÄ°dONLNdø
∞
è
º
fi)Z constant. Several °dONLNd“
Ωl
…∞(
Δlevent classes arkÄ°dONLNd‚
Ω∞
…Ê)De shown herA`°dONLNdÌ
ΩÊ
…Ì)6e:°dONLNd„,l8(5lThe 
ª¿°dONLNdÁ,8¶)event IDr°dONLNdÔ,ß8
)( is the attribute that identifi°dONLNd    ,
 8
i)yes the particular ìÄ°dONLNd     ,
i8
È)IApple event within its event °dONLNd    =9lE
¶(BlIclass. In conjunction with the event class, the event ID uniquely identifi⁄`°dONLNd    á9
¶E
¡(B
¶es the `°dONLNd    é9
¬E
fl)Apple °dONLNd    îFlR
#(Ol'event and communicates what action the 燰dONLNd    ªF
#R
È)∑+Apple event should perform. (The event IDs °dONLNd    ÊSl_®(\lappear in the W†°dONLNd    ÙS©_«)=whereU¿°dONLNd    ˘S«_œ) fi‚Ä°dONLNd    ¸Sœ_
)eld of the event ri@°dONLNd
S
_
,)Kecor›†°dONLNd
S
,_
Q)    d for an ®`°dONLNd
S
Q_
Ø)%Apple event. For morx‡°dONLNd
/S
∞_
Ó)_e information °dONLNd
=`ll¶(ilabout event rÿ‡°dONLNd
J`¶l∏):ecorM@°dONLNd
N`πl
)ds, see the chapter °dONLNd
b`
l
)T“E1¿°dONLNd
d`
l
h)vent Manager” in Å °dONLNd
u`
hl
‡)PInside Macintosh: Macintosh °dONLNd
ëmlyr(vl
T°dONLNd
ímqy∏)oolbox Essentials.≈°dONLNd
§m∏y
Ú)GE) For example, the event ID of an Open Documents event has the value °dONLNd
ÈzlÜê(Él'odoc'}¿°dONLNd
ÔzêÜÍ)$ (which can also be rñ¿°dONLNdzÍܯ)Zepr'Ä°dONLNdz˘Ü
;)esented by the e°dONLNdz
;Ü
õ)BkAEOpenDocuments_°dONLNd&z
õÜ
fi)` constant). The °dONLNd6álìΔ(êlkCoreEventClassz`°dONLNdEáΔì
\)Z" constant in combination with the †°dONLNdgá
]ì
Ω)ókAEOpenDocuments†°dONLNdwá
Ωì
Á)`
 constant °dONLNdÅîl†ã(ùlidentifiV†°dONLNdâîå†
.) #es the Open Documents event to the P@°dONLNd¨î
.†
è)¢Apple Event ManagerA¿°dONLNdøî
è†
ë)a
.
    °dONLNd
÷l
·ù(
filEvent class°dONLNd¸
÷˛
·
)íValue°dONLNd
÷
6
·
g)8Description
°dONLNd
‰l
Δ(
ÌlkCoreEventClass°dONLNd
‰˛

")í'aevt'°dONLNd&
‰
6

=)8
A∫†°dONLNd'
‰
=

C) rˇ†°dONLNd)
‰
C

Z)equir‡°dONLNd.
‰
[

h)ed ‡°dONLNd1
‰
h

õ)
Apple even&@°dONLNd;
‰
õ

û)3
t°dONLNd>
Ùl¥(
˝lkAECoreSuite°dONLNdK
Ù˛
")í'core'°dONLNdR
Ù
6
=)8
A∫†°dONLNdS
Ù
=
?)
 :†°dONLNdT
Ù
@
D)
c™‡°dONLNdU
Ù
D
M)orÂ`°dONLNdW
Ù
M
T)    e –†°dONLNdY
Ù
T
ä)Apple event°dONLNdflΔ(lkAEFinderEvents°dONLNdv˛
")í'FNDR'°dONLNd}
6
¿)8An event that the Finder accept(‡°dONLNdú
¡
≈)ã
s°dONLNdül Í(lkSectionEventMsgClass°dONLNdµ˛ 
)í
'†°dONLNd∂
 
")sect'°dONLNdº
6 
⁄)2#An event sent by the Edition Manage•@°dONLNdfl
⁄ 
›)§
rˇ?"@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äAbout ‡)Apple Events

, (‡    3-9
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähõ(eäHer`°dONLNd\õh´)e arn†°dONLNd\´h
()e the event IDs for the four r] °dONLNd%\
(h
?)}equirt`°dONLNd*\
?h
L)ed {`°dONLNd-\
Lh
â)Apple events:°dONLNd
Z·äÌ
ë(Íä>In addition to the event class and event ID attributes, every ·°dONLNd
ò·
ëÌ(Í
ëApple event must include an °dONLNd
¥Óä˙‚(˜äattribute that specifi>¿°dONLNd
 Ó„˙
)Y
es the tar* °dONLNd
‘Ó
˙
k)(get application’s addr|‡°dONLNd
ÍÓ
k˙
x)`ess¿Ä°dONLNd
ÌÓ
x˙
Δ). Remember that tÜ °dONLNd
˛Ó
«˙
‡)Ohe tar®Ä°dONLNdÓ
‡˙
)get °dONLNd˚ä
ˇ(
äapplication is the one addrF†°dONLNd#˚


))v
essed to rÏÄ°dONLNd-˚
)

W))eceive the «@°dONLNd8˚
W

í).Apple event. ‰`°dONLNdE˚
í

ò);
Y§‡°dONLNdF˚
ò
)our application can send an °dONLNdb
ä

„(
äOApple event to itself or to another application (on the same computer or on a rf`°dONLNd±

„
(

„emote °dONLNd∑
ä
!
-(
ä#computer connected to the network).°dONLNd€
'ä
3¶*Every Ø°dONLNd·
'¶
3
ö)7Apple event must include event class, event ID, and tar–Ä°dONLNd
'
ö
3
ø)Ùget addrË °dONLNd 
'
ø
3
˝)%ess attributes. °dONLNd0
4ä
@§(
=äSome ÙÄ°dONLNd5
4§
@
h)-Apple events can include other attributes; se@`°dONLNdb
4
i
@
p)≈e ä°dONLNdd
4
p
@
ò)“Keywor∂`°dONLNdk
4
ò
@
æ)(d-Specifiñ‡°dONLNdt
4
ø
@
˝)'ed Descriptor °dONLNdÇ
Aä
M£(
JäRecor¢`°dONLNdá
A£
M¥)ds,”{ °dONLNdã
Aµ
M
) which begins on ÎÄ°dONLNdú
A

M
)Mpage Δ`°dONLNd°
A

M
,)3-15@°dONLNd•
A
-
M
5), fn °dONLNd®
A
5
M
É)or a complete list.


kH
r4
lH
r 
mä
m

ˇ·ˇ‚7^°dONLNdº
^ä
l
(
häApple Event Parametersˇˇˇˇˇˇ‘@(
h
3
°dONLNd‘
rä
~(
{äAs with attributes, ther±@°dONLNdÏ
r
~
)fe arø‡°dONLNd
r

~
Q)e various kinds of —°dONLNd
r
Q
~
¿)QApple event parameters. `°dONLNd
r
¡
~
»)p
AF°dONLNd
r
»
~
 )
 
Δ°dONLNd
r
 
~
Ê)direct °dONLNd$
ä
ã∫(
àä
parameter Ä°dONLNd.
ª
ã˙)1usually specifi≥¿°dONLNd=
˙
ã
é)?"es the data to be acted upon by th†°dONLNd_

è
ã
¢)ïe tarb†°dONLNdd

¢
ã
∑)get a}¿°dONLNdi

∑
ã
˙)pplication. For °dONLNdy
åä
ò—(
ïäexample, the dir ‡°dONLNdâ
å“
ò)HIect parameter of the Print Documents event contains a list of documents. °dONLNd“
ôä
•§(
¢äSome ÙÄ°dONLNd◊
ô§
•

)Apple events also take 
2@°dONLNdÓ
ô

•
q)gadditional parameters,Ó‡°dONLNd
ô
q
•
ö)f     which thU°dONLNd
ô
õ
•
Æ)*e tar¶°dONLNd
ô
Æ
•
√)get a¡ °dONLNd
ô
√
•)pplication uses in °dONLNd*
¶ä
≤ˇ(
Øäaddition to the data specifis°dONLNdF
¶

≤
5)ved in the dir8†°dONLNdS
¶
6
≤
r)6ect parameterÄ°dONLNd`
¶
r
≤
è)<. Thus,æ¿°dONLNdg
¶
è
≤
û) an 1¿°dONLNdk
¶
ü
≤
‡)Apple event fo≈‡°dONLNdy
¶
‡
≤
Ê)Ar °dONLNd{
≥ä
øè(
ºä
a°dONLNd|
≥è
ø    )Urithmetic operations might include additional parameters that specify operands in an °dONLNd—
¿ä
õ(
…ä
equation. °dONLNd‹
“ä
fiù*The ª¿°dONLNd‡
“ù
fi
9)%Apple Event Registry: Standard Suites©Ä°dONLNd
“
:
fi
’)ù% describes all parameters as either r» °dONLNd*
“
’
fi
Ï)õequirfl`°dONLNd/
“
Ï
fi)ed or °dONLNd5
flä
Î≥(
Ëä
optional. Û@°dONLNd?
fl≥
Î∫))
A-‡°dONLNd@
߻
ÎΩ)
 
≠‡°dONLNdA
flΩ
Î
)required parameter∂¿°dONLNdS
fl

Î
A)X is one thaÄ`°dONLNd^
fl
B
Î
w)-t must be prµ†°dONLNdj
fl
w
Î
º)5esent for the tar∫`°dONLNd{
fl
º
Î)Eget application tN¿°dONLNdå
fl
Î)Ho °dONLNdé
Ïä
¯
(
ıä"carry out the task denoted by the y@°dONLNd∞
Ï

¯
Y)îApple event. e†°dONLNdΩ
Ï
Y
¯
i);An 
~@°dONLNd¿
Ï
i
¯
¬)optional parameter Í °dONLNd”
Ï
¬
¯)Yis a supplemental °dONLNdÂ
˘ä
©(äAApple Event parameter that also can be used to specify data to th
@°dONLNd&
˘
™
Ω(
™e tarR@°dONLNd+
˘
Ω
“)get am`°dONLNd0
˘
“)pplication. °dONLNd<ä
`(ä/Optional parameters need not be included in an (@°dONLNdk
`)÷)Apple event; default values for optional °dONLNdîä«(äparameters arì°dONLNd°«
*)=e part of the event defi˘‡°dONLNdπ
*
U)c
nition. Th`°dONLNd√
V
i),e tarh`°dONLNd»
i
~)get aÉÄ°dONLNdÕ
~)"pplication that handles the event °dONLNdÔ ä,
Ç()ä8must supply default values if the optional parameters ar  °dONLNd' 
É,
±)˘e omitted. ¿°dONLNd2 
≤,
¥)/
 °dONLNd42ä>ò(;äDir͆°dONLNd72ò>‰)ect parameters ar˘‡°dONLNdH2‰>
)Le usually defi`¿°dONLNdV2
 >
B)<ned as rÄ°dONLNd^2
C>
Z)#equir0¿°dONLNdc2
Z>
∑)ed parameters in the {@°dONLNdx2
∑>)]Apple Event Registry: °dONLNdé?äK (HäStandard Suites6‡°dONLNdù?ÀKÕ)A
;∂‡°dONLNdû?ÕK
g)! additional parameters may be defi%@°dONLNd¿?
hK
¶)õned as either r‡°dONLNdœ?
¶K
Ω)>equir˜@°dONLNd‘?
ΩK
˚)ed or optional`°dONLNd‚?
¸K
)?. °dONLNd‰LäX≥(UäHowever†°dONLNdÎL≥X»)), the †°dONLNdÒL»X
k)"Apple Event Manager does not enforÖ°dONLNd    L
kX
ò)£
ce the defié`°dONLNd    L
òX
»)-nitions of rÖ °dONLNd    *L
»X
fl)0equirú`°dONLNd    /L
flX
ˇ)ed and °dONLNd    6Yäe
(bä"optional events. Instead, the sourÃÄ°dONLNd    XY
e
,)íce aÜ`°dONLNd    \Y
-e
S)    pplicatiok‡°dONLNd    eY
Te
x)'n specifi+`°dONLNd    nY
ye
¸)%es, when it sends the event, w“Ä°dONLNd    åY
¸e)Éhich °dONLNd    ëfär¬(oäApple event J¿°dONLNd    ùf√r
)9parameters the tar˝Ä°dONLNd    Øf
r
)PgeV@°dONLNd    ±f
r
<)t can tr·†°dONLNd    πf
<r
á)eat as if they werπ°dONLNd    Àf
ár
≥)K
e optional‘@°dONLNd    ’f
≥r
µ),
.°dONLNd    ◊xäÑè(Åä
F °dONLNd    ÿxêÑÆ)or mor¿°dONLNd    fixÆÑ
v)-e information about optional parameters, see ¡@°dONLNd
x
vÑ
)» “Specifying Optional Parameters °dONLNd
+Öäë¶(éäfor an Ø°dONLNd
2Ö¶ëÂ)Apple Event,”À‡°dONLNd
?ÖÂë
2)? which begins on <@°dONLNd
PÖ
3ë
J)Npage  °dONLNd
UÖ
Kë
X)5-7k°dONLNd
XÖ
Xë
Z)
.
    °dONLNd;uäÄÆ(}äEvent ID°dONLNdDu

Ä
)Ä
V¸/°dONLNdEu
Ä
!)alue°dONLNdJu
BÄ
s)3Description,
Courier
°dONLNdWÉäèˆ(åäkAEOpenApplication°dONLNdjÉ

è
.)Ä'oapp'°dONLNdqÉ
Bè
Ö)8Perform tasks rÊ`°dONLNdÄÉ
Öè
ú)Cequir˝†°dONLNdÖÉ
úè)ed when a user opens your °dONLNdüé
Bö(ó
B,application without opening or printing any °dONLNdÀô
B•
n*document:°dONLNd”ô
o•
s)-
s°dONLNd÷©äµÍ(≤äkAEOpenDocuments°dONLNdÁ©

µ
.)Ä'odoc'°dONLNdÓ©
Bµ
ç)8Open documents°dONLNd˛πä≈(¬äkAEPrintDocuments°dONLNd
π

≈
.)Ä'pdoc'°dONLNd
π
B≈
ã)8Print documents°dONLNd
(…ä’ˆ(“äkAEQuitApplication°dONLNd
;…

’
.)Ä'quit'°dONLNd
B…
B’
°)8Quit your applicationˇV˛@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-10    )BAbout ‡)Apple Events4^*¿
¯

j*p
¯4j*p
¯ klk
¯

ˇ·ˇ‚7^°dONLNd\ljo(fl
I’Ä°dONLNd
\oj´)nterpreting ⁄°dONLNd\´jÔ)<Apple Event 8@°dONLNd\Ôj
z)DAttributes and Parametersˇˇˇˇˇˇ‘@(f
Ò
3
°dONLNd4pl|Ñ(ylFigurR¿°dONLNd9pÑ|ò)e 3-3@°dONLNd>pò|Â) shows the major °dONLNdOpÊ|
k)NApple event attributes and dir“Ä°dONLNdmp
k|
…)Öect parameter for the °dONLNdÉ}lâÑ(ÜlOpen˘°dONLNdá}ÑâÜ)
 y°dONLNdà}áâ—)Documents evenú`°dONLNdñ}—âŸ)Jt iG °dONLNdô}⁄âÁ)    ntr‡°dONLNdú}Áâ
)
oduced in «†°dONLNd¶}
â
-).Figurö`°dONLNd´}
-â
A)e 3-17‡°dONLNd∞}
Bâ
D)
.

´*º
¯4¨*º
¯"¨*]

ˇ·ˇ‚7^
    °dONLNd≤°l¨ñ(©l
Figure 3-3°dONLNdΩ°Æ¨¡)BMajoˇ†°dONLNd¡°¡¨
H)#r attributes and direct parameter oÉ–°dONLNd‰°
I¨
π)àf an Open Documents event
°dONLNdˇ
òl
§å(
°lWhen tÆ¿°dONLNd

òå
§µ) he SurfWô¿°dONLNd

òµ
§ˆ))riter applicatioÿ‡°dONLNd

òˆ
§
)An rÔ@°dONLNd
 
ò

§
ê)"eceives any high-level event, it cI °dONLNd
B
ò
ë
§
≤)è    alls the ,
Courier°dONLNd
K
•l
±fi(
ÆlAEProcessAppleEventx‡°dONLNd
^
•fi
±
)r     function °dONLNd
g
•

±
)( to prÜ °dONLNd
m
•

±
É)ocess the event. For an D`°dONLNd
Ö
•
É
±
Ó)fApple event such as the °dONLNd
ù
≤l
æ
(
ªlOpen Documents event shown in ƒ¿°dONLNd
ª
≤

æ
)ñFiguróÄ°dONLNd
¿
≤

æ
.)e 3-35°dONLNd
≈
≤
/
æ
D), the í`°dONLNd
À
≤
D
æ
J)
Aí°dONLNd
Ã
≤
J
æ
∞)EProcessAppleEvenㆰdONLNd
›
≤
∞
æ
∂)f
tã@°dONLNd
fi
≤
∂
æ
ª) f_ °dONLNd
‡
≤
º
æ
ˆ)unction uses °dONLNd
Ì
øl
À
≠(
»lJthe event class and event ID attributes to dispatch the event to the SurfWô‡°dONLNd7
ø
≠
À
¬(
»
≠riter °dONLNd=
Ãl
ÿ
(
’l$application’s Open Documents handlerr`°dONLNda
Ã

ÿ
-)≠. In rÁ@°dONLNdg
Ã
-
ÿ
^)esponse, thQ@°dONLNdr
Ã
_
ÿ
‘)2e Open Documents handle‡°dONLNdâ
Ã
’
ÿ
‡)vr o°dONLNdå
Ã
·
ÿ
¯)pens °dONLNdë
Ÿl
ÂÃ(
‚lthe documents specifi¬Ä°dONLNd¶
ŸÃ
Â

)`ed in the dirà °dONLNd≥
Ÿ

Â
>)6ect parameterX°dONLNd¿
Ÿ
>
Â
C)<. °dONLNd√
Îl
˜ê(
ÙlThe defi≠‡°dONLNdÀ
Îê
˜⁄)$nition of a given ˝°dONLNd›
Î⁄
˜
.)JApple event in the ^‡°dONLNd
Î
/
˜
»)U$Apple Event Registry: Standard Suitei°dONLNd
Î
»
˜
À)ô
sL†°dONLNd
Î
Ã
˜
ˆ)
 suggests °dONLNd
¯lq(
l
hQ`°dONLNd 
¯r¶)ow the soury‡°dONLNd+
¯¶Â)4ce application j†°dONLNd:
¯Ê˜)@can ,@°dONLNd>
¯¯

)orf¿°dONLNd@
¯


)    ganiz؆°dONLNdE
¯

#)e t;†°dONLNdH
¯
$
b)he data in the mÄ°dONLNdW
¯
b
÷)>Apple event’s parameters °dONLNdpl|(landm °dONLNds})
 Ì °dONLNdt±)how the taro¿°dONLNd≤
)3get application interprA@°dONLNdñ

ë)cets that data. The data in an Ö °dONLNd¥
ë
…)|Apple event °dONLNd¿l©(lparameter mae°dONLNdÙ«)>y use s>‡°dONLNd”»Â)tandar3`°dONLNdŸÂÌ)d œ °dONLNd€Ì
)or private Δ†°dONLNdÊ

D).    data typeB°dONLNdÔ
E
ù)*s and may include aŒ °dONLNd
ù
Ï)X description of an °dONLNdl+æ((lApple event object‡°dONLNd'ø+€)S. Each ô‡°dONLNd.€+Ë)Apc@°dONLNd0È+
2)ple event handle’ °dONLNd@
2+
B)Ir pr‡°dONLNdD
C+
·)#ovided by an application should be °dONLNdg,l8
W(5l5written with the format of the expected data in mind.°dONLNdù>lJÌ*Apple events can use standar†°dONLNdπ>ÓJ
Δ)Ç4d data types, such as strings of text, long integers‰@°dONLNdÌ>
ΔJ
À)ÿ, °dONLNdÔKlWr(Tl
Bõ¿°dONLNdKrWè)oolean
 °dONLNdˆKêWí)
 ä °dONLNd˜KíW™)valueÈÄ°dONLNd¸K™WÆ)
s&Ä°dONLNd˝KØW±)
,¶Ä°dONLNd˛K±WÀ) and a솰dONLNdKÃW·)lias rÊ`°dONLNd
K·WÛ)ecorZ¿°dONLNdKÙW
)    ds, for t1‡°dONLNdK
W
4)"he corrÍ@°dONLNdK
4W
Ü)esponding data in ÿ°dONLNd0K
ÜW
ı)RApple event parameters. °dONLNdHXld
è(al@For example, the Get Data event can contain an optional paramete@°dONLNdàX
êd
ö(a
êr s.‡°dONLNdãX
õd
≠)peciS@°dONLNdèX
≠d
…)fying tAÄ°dONLNdñX
 d
Ô)he form °dONLNdûelq•(nlin which the ÈÄ°dONLNd´e•q®)9
rÆÄ°dONLNd¨e©q”)    equested Δ¿°dONLNdµe”q·)*dat$‡°dONLNd∏e‚qÌ)a s·‡°dONLNdªeÌq
)
hould be rJ@°dONLNd≈e
q
ˆ).1eturned. This optional parameter always consists °dONLNdˆrl~¨({lof a list of four¯`°dONLNdr¨~
6)@-character codes denoting desir˛¿°dONLNd&r
6~
°)äed descriptor types in orÇ°dONLNd?r
¢~
»)l    der of pr5`°dONLNdHr
…~
Ÿ)'efer·Ä°dONLNdLr
Ÿ~
Ò)ence. °dONLNdRlã
B(àl0Apple events can also use special data types defiÊ@°dONLNdÉ
Bã
s)÷ned by the ≤¿°dONLNdé
sã
‘)1Apple Event Manager§@°dONLNd°
‘ã
Ÿ)a. °dONLNd§ëlù“(ölApple event parameter€¿°dONLNdπë“ùÿ)fs ò¿°dONLNdªëŸùÚ)often øÄ°dONLNd¡ëÚùˆ)
c/¿°dONLNd¬ë˜ù
Y)ontain descriptions of | °dONLNdŸë
Yù
´)bApple event object°dONLNdÎë
¨ù
≤)Ss.‘°dONLNdÌë
≤ù
–) These °dONLNdÙûl™≠(ßldescriptions mÚ`°dONLNdû≠™
)Aake use of a standarS¿°dONLNdû
™
+)X    d classifi∑@°dONLNd û
+™
d)&cation schem5`°dONLNd,û
e™
p):e sº°dONLNd/û
p™
±)ummarized in Â@°dONLNd<û
±™
…)A“The °dONLNdA´l∑å(¥lClassifiÓÄ°dONLNdI´å∑¥)
cation of ;`°dONLNdS´µ∑
))Apple Event Objects,”K¿°dONLNdh´
∑
d)b which begins on º °dONLNdy´
d∑
{)Mpage ó°dONLNd~´
|∑
é)3-39͇°dONLNdÇ´
é∑
ê)
.

ªg
Å
¯4ºh
Ä
¯

ºk
Å
¯4ªjºkò@@
¯@
¯ºk¸c¡¡?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?¡IJÛˇ‡Ú?¡IJÛˇ‡Ú?¡ÉÄÛˇ‡Ú?¡Ñ@Ûˇ‡Ú?¡à Ûˇ‡Ú?¡àÛˇ‡Ú?¡ày˛Ûˇ‡Ú?¡Ñ˛
ÄÛˇ‡Ú?¡Ç`Ûˇ‡Ú?¡ŇÄÛˇ‡Ú?¡Ä¿dÛˇ‡Ú?¡ÅÛˇ‡Ú?¡ÅyÛˇ‡Ú?¡Ç@‘áÛˇ‡Ú?¡ÑÅ*GÛˇ‡Ú?¡ÑGÛˇ‡Ú?¡à!
GÛˇ‡Ú?¡à"GÛˇ‡Ú?¡àBÑáÛˇ‡Ú?¡àDCáÛˇ‡Ú?¡àÑ Ûˇ‡Ú?¡ÑÑ5Ûˇ‡Ú?¡Ñà*àÛˇ‡Ú?¡Ç%DÛˇ‡Ú?¡Åà"¢Ûˇ‡Ú?¡Äà!QÛˇ‡Ú?¡ÄH ©áÛˇ‡Ú?¡Ä$VGÛˇ‡Ú?¡Ä.GÛˇ‡Ú?¡ÄGÛˇ‡Ú?¡Ä«Ûˇ‡Ú?¡Ä«Ûˇ‡Úò@@Ä
¯@Ä
¯¸k
<c?¡Ä
Ûˇ‡Ú?¡ćÛˇ‡Ú?¡IJÛˇ‡Ú?¡IJÛˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Úò@Ä¿
¯Ä¿
¯
<k
|c?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Ú?“ˇ‡Úò@¿

¯¿

¯
|k
ºc“ˇ‡Ú¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡


ò»

    d»
D»
\»
ê‰tB»
ëD¢»
˛É»¡¡¡¡¡-†`00@Ä˝@
¿¿˛˛@Ï-ÄêHPÄ˝@  ˛˛@Ï.*/F»
bƒ∞ª⁄§y8-éY[-bÂ`∏]àÇ"5ãn·t∂‡Ï.*2…p8
• AQ"‹í¿Vî)"™:§V•JÅP¶àÆÑ%.Zï•ïZ@Ï.*RY8)RBb$ïß8î§J'D$îÆúÇQ$àÙÑ)B“π(Á'íÄÏ.*lr àD/îÉÛFß4˘¨[D^%ˢ—°ÈåiIÑJ[§"l$*&¿Ï.*\Zp8zàÇ¢D≈£©6nC§H©Gè
!IÜ9Ñ"ÂI√ë‰ÄÏ˛"˚Ĉ ¸ ·˛"˚Ĉ ¸†·˛¸
ı ¸@·¡¡(Ç
–@˛$
¿Ä$ 
¿|Ê&%ä
˛Äb¸ ÄÄ  Ä$Ê)%%L
flñîëóDÿÄö⁄—⁄2Ù[ÌÏéâÙMé@bîà#•∑pÁ)%)Tj*/zí™JhÅMMrjU$≠
4ëUí§¶Ñ†gzî8™“ÄÁ)%…dLrJS$LíHÇIIVLâI)
%d¥I$â íS8A<îpÁ)%RDûD|•µ˛‘òFíûømSM¢¨ÂÌIçA•†EQ6Á)%[NFî<S"Tàê9íñîJHí#I!6≤HâÉ;¯è$‡Á¸Ä ı@˘
 ‚¸Ä ı@˘
 ‚˘
 Ï
 ‚¡¡$Äaå0c
ÿ  ˝íRîÅÿ$YtMáúHRÆÁRrò´ú9Ä⁄    ,¬"§¶à§†q›’
R•xı RØ@⁄
Eº$…$á    ¿§ò‚ï.(¶ór@⁄gGÌIÅëå•,"ßh    )K¥DÄ⁄EÙEHâ<Ës…√E∑Δ28€ªŸı
˙@Ÿı
˙@Ÿı
˙@Ÿò@

@
¯

@
¯
ºk
¸c¡¡¡¡¡¡¡¡¡¡¡¡¡¡
‡Õ
Õ§D÷R<¨cŒ;‘§jÓIP    •Œíôƒ    JJ”ê    (Œ•-:êìö kŒÿ»·ƒîb—·D@œ˛!˝ÄÃ˛!˝ÄÃ
˛!˝Ä ¡¡
˛–¯Ä–ÅÄ@PÄ–óà≟÷ƒR/Ï∏¨—)JjìJVPëQP—J
&RL¢R¢œbP—{    )îù¥‘ÛÉ£Ú†—Rìàñ‰à墛"° —
¸@
À
¸@
À¸
Ä»¡¡     ¿`À      
 êÀ    $YrX!À        ,¬"• ·À
Eº$… À    gGÍA À    EÙED@‰¿À¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
¯
@
Ä
¯
¸k<c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
¯
Ä
¿
¯<k|c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
¯
¿
Ú
¯|kÆc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
¯@
¯ºk¸c
¡¡—3 Ú—@Ú “ Ú—@Ú—@Ú—@Ú “ Ú—@Ú “ Ú—@Ú—@Ú‹
¯ˇ
@Ú į
ÄÙ‡˚
˘
Ä Ú$˛f˘
IJ`˘

˚
¸
Ä@Ú( Bõú˘œ{·ˆÓ¯Δil˝
˛ 
Ä Ú'˛BæH˘ÕÔÛˇˇ`¯?E¯˝
àÄ
Ä@Ú(˛F¢H˘mÔÉè`˘
Fà˝


Ä@Ú'˛:ûD˘o{Ò¯ˇp¯ÁDx˝
ààÄ
Ä@Ú Û
`Ì
˘
Ä ÚÚ
`Ì
¯ˇ
Ä@Ú ›
˘ÅÄ Ú˛È˝˘ˇ˘Ä@Ú ˛ ¸?ˆˇ¸˚ ˝˘çÄ@Ú(nu3s8˝(ˆàé¸nu3s8˛ˇ‡˝ˇ˝Ä@Ú, ˘MO¥§˛
  ˆ

˘MO¥§˛á· 
Â˝Ä Ú,ôMD¥§˛
0 ˆ

ÄôMD¥§˛á·¨¡7g≥½Ä@Ú+ ~u;ì$˛8ı"
&
¿~u;ì$˛á·¨¡7g≥˝˝Ä Ú.@˛    
ˇˇÏ Ä˚ˇˇ`@˚á·l¡7g≥·˝Ä@Ú1@˛    
 ¿˛

Ä0@˚ˇ·,—7g≥ˇ˝Ä@Ú$˙
(àòflŒõ˚Ω˚ü¸àé¯˘Ä@Ú& ˚
 €ÔŒ˝ˇfl¯¯˘ˇ˝Ä Ú%˙
 €Œ=˛å0¯˙    çÄ@Ú* ˚
ˇˇÏ""/øÔ>{ˇ˚ˇ˙"&ˇˇ`Ä˚˙ÕÄ Ú&˛ˇˇ¸˝8 ˘
¿@˚˙
mÄ@Ú&˛Ä˝0 ˘
Ä ˚˙mÄ@Ú#˛Ä˝
 (ˆàé
˚˙
MÄ@Ú$ üˇ‚¸ ˆ¸y˛¸h¸ÕÄ Ú%˛∞2¸?ˆˇ˛¸˛
Ä˝    )˝˝Ä@Ú& Øˇ¸ ˆ¸`˝i0˝Ä Ú%˛Øˇ¸ ˆ¸
‡Ä˝    iH˝Ä@Ú$˛Ø¸ ˆ˚¿d˝i8˝Ä@Ú"˛†¸ ˆ¸
˝˙Ä@Ú# ظ ˆ¸
y˝˙Ä Ú.˛Ø¸ ˛0˛¸@‘IJÄ¿˝Ä@Ú/ ظ ¸Å*@˛Å ˝Ä Ú/˛Ø¿¸ ñw«qøºüà¸@
©ßM@Ä@Ú/˛Ø¿¸ _J'Ï√”2ó¿¸!
@
Ä
©)TÎ@Ä@Ú/˛†¸ hJ##2S2ñ¸"@
¿
ê«WjÄÄ@Ú0 ∞2¸ GIÓ·…<s»¸BÑġ`ÄÄ Ú'˛üˇ‚¸ ˆ¸DCÄ    0 
Ä@Ú$ ĸ ˆ¸Ñ
"8˙àÄ Ú'˛Ä¸ ˆ¸Ñ5< àÄ@Ú,˛Ä¸
 ˚
ĸà*àDp ˛%àÄ@Ú/˛Ä¸ x‡<ĸ%Dˇ‡,;LÊÿ!àÄ@Ú0 Ä‚¸ â€q;;fiDLJ¸
à"¢
¿
z"Î/$&HÄ Ú.˛Ä¸ Ç,âäE(@á1Ä˚à!Q
Ä:"jÏ⁄HÄ@Ú- ĸ
ä(˘*})Dâ`˚H ©Ä
¸Ä Ú,˛Ä¸ qfi3‰∂;Á˚¿˚$V@˛¸Ä@Ú"˛ˇˇ˛¸ ˆ˚.@˛˙Ä@Ú"˛Ä¸ ˆ˚@˛˙Ä@Ú# ĸ?ˆˇ˛˚¿˛˙Ä Ú"˛Ä¸ ˆ˚¿˛˙Ä@Úò@@Ä
¯@Ä
¯¸k
<c
! ˇˇ¸¸ ˆ˚

¸˙Ä Ú ˆ 
@˝˙‡¸˙Ä@Úˆ ÄP@˛Ù˙Ä@Úˆ ñwܡr~ Ù˙Ä@Ú# ˜ _JèUJ_˛ÙÄLÃÄ Ú!ˆ hJâUJX˛ÙIJ√2Ä@Ú. x˚ GI-qœ ¸I˝≥∂g2Ä Ú%˛
@˚ ˆ¸"…˝˜’Ÿ2Ä@Ú'˛Kéø ˆ¸ù’◊Ã˛>µnÃÄ@Ú'˛zS˸ ˆ¸ò÷ì˲@Ä@Ú( JS¸
 ˜¸"ò∂ì˛`˝Ä Ú.˛JN˸ cÓx˛
¸x¢ë˲
˝GÃÄ@Ú# ˜ 11Òfi%œoG{¿Ù˛≈2Ä Ú!ˆ QëJ)&1&®•Ùp˛g2Ä@Ú!ˆ
q1KÈ&0&Ø• Ù    P˛—2Ä@Ú!ˆ €Óp›˘œ£v¿Ù    P˛fÃÄ@Ú ˜ ˛@˙Ù¸@Ä Úˆ ˛‡˙Ù˙Ä@Ú ˜ ˆÙ˙Ä Úˆ ˆÙ†˛LÃÄ@Úˆ?ˆˇ˛Ù ˛√2Ä@Úˆ ˆÙ∫˛g2Ä@Ú ˜ ˆÙµ˛Ÿ2Ä Úˆ ˆÙµ˛nÃÄ@Ú  ˜
 ˛ÄÄÙ
?˚ˇÄ Ú ˆ @ÄêÄ Ù˝Ä@Ú!ˆ lÏÊ;∂;粉¸FÙ≤FÃÄ@Ú!ˆ ˘>OLØföîæÙä2…2˝Ä@Ú# ˜ ô0IL®íöî∞Ùä2i2ÕÄ Ú!ˆ xÓ';ßwJ„ûFÙäJ◊2
MÄ@Ú ˜  ˘ÙrKÄnÃmÄ Úˆ 
¿˘Ù¸@oÄ@Úˆ ˆÙ˙œÄ@Úˆ †D˛Ù˙    å@Ú ˜ Ä˛Ù˘ˇ¸ Úˆ Œ¶ngflòÙ˙@Ú ˜ )©ˆîñÃÜ|Ù˙Ï Úˆ )®ñîçLÜ`Ù˙
¨@Úˆ ŒßrdâDÇ\Ù˙¨@Úˆ 
¯Ù˙
,@Ú ˜ 
¯Ù˙Ï Úˆ ˆÙ˘ˇ¸@Ú ˜
 
˜Ù˘ˇ¸ Úˆ 
ôÄÈ@Úˆ ?ñ¿êìgÈ@Úˆ LΩï‡
πHÄÈ@Ú ˜ L•ïIOÄÈ Úˆ <úÙ‡    <ɲÈ@Ú ˜ ¯È Úˆ p¯È@Úˆ ˆÈ@Úˆ ˆÈ@Ú ˜?ˆˇ˛È Úˆ ˆÈ@Ú ˜ ˆÈ Úˆ ˆÈ@Úˆ ˆÈ@Úˆ>ˆ
‡Í@Ú ˜ıÍ Úˆˆ

‡Í@Ú ˜ˆ
¿Í Úˆ0ˆ
ÄÍ@Úˆ`ˆÈ@Úˆ¿ˆÈ@Úò@Ä¿
¯Ä¿
¯
<k
|c
 ¯

Ĉ<È Ú˜ıxÈ@Ú ¯ıÈ Ú˜
‡ˆ|È@Ú˜
‡@¯È@Úˆ     
˛˝È@Ú ˜     sπô¥7Ã˛È Úˆ     g•'”Í{θÈ@Ú ˜     d!&RjC˛È Úˆ cúπ—Í9˲È@Úˆ ˛ ˙È@Úˆ ˛ ˙È@Ú ˜ (˙È Úˆ H˙È@Ú ˜ ¯‹Èú˚È Úˆ (k˚È@Úˆ —(j˚È@Úˆ à»i¯˚È@Ú ˜ ˆÈ Úˆ ˆÈ@Ú ˜ ˆÈ Úˆ     ¿@
˚È@Úˆ      @˙È@Úˆ ,`y-3¸È@Ú ˜ >êd≥OÄ˝È Úˆ 0Äd”D¸È@Ú ˜ Œtdç;Ä˝È Úˆ
 ˜È@Úˆ
 ˜È@Úˆ ˆÈ@Ú ˜ @@
@˝È Úˆ @@@˝È@Ú ˜ M zY3 ˝È Úˆ R†eeO†˝È@Úˆ “¿e•D ˝È@Úˆ Làe;†˝È@Ú ˜ ˚@˝È Úˆ ˚@˝È@Ú ˜ ˆÈ Úˆ ˆÈ@Úˆ ˆÈ@Úˆ ˆÈ@Ú ˜ ˆÈ Úˆ ˆÈ@Ú ˜ ˆÈ Úˆ ˆÈ@Úˆ ˆÈ@Úˆ ˆÈ@Ú ˜ ˆÈ Úˆ ˆÈ@Ú ˜?ˆˇ˛È Úˆˆˇ˛È@Ú—@Ú—@Ú “ Ú—@Ú “ Ú—@Ú—@Ú—@Ú “ Ú—@Ú “ Ú“ÿÚò@¿

¯¿

¯
|k
ºc
“U@Ú¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡


ò»

    d»
D»
\»
ê‰tB»
ëD¢»
˛É»¡¡¡¡¡-†`00@Ä˝@
¿¿˛˛@Ï-ÄêHPÄ˝@  ˛˛@Ï.*/F»
bƒ∞ª⁄§y8-éY[-bÂ`∏]àÇ"5ãn·t∂‡Ï.*2…p8
• AQ"‹í¿Vî)"™:§V•JÅP¶àÆÑ%.Zï•ïZ@Ï.*RY8)RBb$ïß8î§J'D$îÆúÇQ$àÙÑ)B“π(Á'íÄÏ.*lr àD/îÉÛFß4˘¨[D^%ˢ—°ÈåiIÑJ[§"l$*&¿Ï.*\Zp8zàÇ¢D≈£©6nC§H©Gè
!IÜ9Ñ"ÂI√ë‰ÄÏ˛"˚Ĉ ¸ ·˛"˚Ĉ ¸†·˛¸
ı ¸@·¡¡(Ç
–@˛$
¿Ä$ 
¿|Ê&%ä
˛Äb¸ ÄÄ  Ä$Ê)%%L
flñîëóDÿÄö⁄—⁄2Ù[ÌÏéâÙMé@bîà#•∑pÁ)%)Tj*/zí™JhÅMMrjU$≠
4ëUí§¶Ñ†gzî8™“ÄÁ)%…dLrJS$LíHÇIIVLâI)
%d¥I$â íS8A<îpÁ)%RDûD|•µ˛‘òFíûømSM¢¨ÂÌIçA•†EQ6Á)%[NFî<S"Tàê9íñîJHí#I!6≤HâÉ;¯è$‡Á¸Ä ı@˘
 ‚¸Ä ı@˘
 ‚˘
 Ï
 ‚¡¡$Äaå0c
ÿ  ˝íRîÅÿ$YtMáúHRÆÁRrò´ú9Ä⁄    ,¬"§¶à§†q›’
R•xı RØ@⁄
Eº$…$á    ¿§ò‚ï.(¶ór@⁄gGÌIÅëå•,"ßh    )K¥DÄ⁄EÙEHâ<Ës…√E∑Δ28€ªŸı
˙@Ÿı
˙@Ÿı
˙@Ÿò@

@
¯

@
¯
ºk
¸c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡
‡Õ
Õ§D÷R<¨cŒ;‘§jÓIP    •Œíôƒ    JJ”ê    (Œ•-:êìö kŒÿ»·ƒîb—·D@œ˛!˝ÄÃ˛!˝ÄÃ
˛!˝Ä ¡¡
˛–¯Ä–ÅÄ@PÄ–óà≟÷ƒR/Ï∏¨—)JjìJVPëQP—J
&RL¢R¢œbP—{    )îù¥‘ÛÉ£Ú†—Rìàñ‰à墛"° —
¸@
À
¸@
À¸
Ä»¡¡     ¿`À      
 êÀ    $YrX!À        ,¬"• ·À
Eº$… À    gGÍA À    EÙED@‰¿À¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
¯
@
Ä
¯
¸k<c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
¯
Ä
¿
¯<k|c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
¯
¿
Ú
¯|kÆc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
¯@
¯ÆkÓc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
¯@Ä
¯Ók.c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
¯Ä¿
¯.knc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

¯¿

¯nkÆc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
¯

@
¯ÆkÓc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
¯
@
Ä
¯Ók.c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
¯
Ä
¿
¯.knc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
¯
¿
Ú
¯nk†c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
¯@
¯ÆkÓc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
¯@Ä
¯Ók.c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
¯Ä¿
¯.knc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

¯¿

¯nkÆc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
¯

@
¯ÆkÓc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
¯
@
Ä
¯Ók.c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
¯
Ä
¿
¯.knc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
¯
¿
Ú
¯nk†c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇÅ @ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äAbout ‡)Apple Events

, (‡3-11
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähè(eä
F °dONLNd
\êh¡)
or exampleq†°dONLNd\¡hË)1    , every GN°dONLNd\Èh
Y)(et Data event includes a r'¿°dONLNd.\
Yh
p)pequir?°dONLNd3\
ph
ª)ed parameter tha… °dONLNdC\
ªh
Ô)Kt describes tI¿°dONLNdP\
h
˝)5he °dONLNdSiäu•(räApple˝Ä°dONLNdXi•uß)
 }Ä°dONLNdYi®uŸ)event objecÿÄ°dONLNddiŸu‹)1
t‡°dONLNdei›u
') containing the dê °dONLNdvi
'u
/)Jat“Ä°dONLNdxi
/u
:)a rÄ°dONLNd{i
;u
{)equested by th⁄@°dONLNdâi
{u
»)@e client applicatioß¿°dONLNdúi
…u
Ÿ)Nn. Tô‡°dONLNd†i
⁄u
Í)husØ`°dONLNd£i
Íu
Ï)
,/`°dONLNd§i
Ìu) one °dONLNd©väÇ
ù(ä?application can send a Get Data event to another application, r0‡°dONLNdËv
ûÇ
√(
ûequestinùÄ°dONLNdv
√Ç)%g, for instance, °dONLNd

Éäèè(åä
oıÄ°dONLNd
Éèè
')!ne paragraph of a document, the fi»°dONLNd
$É
(è
¸)ô1rst and last paragraphs of a document, all picturS@°dONLNd
UÉ
˝è)’es in °dONLNd
[êäú
b(ôä/the document, all paragraphs containing the worZ °dONLNd
äê
bú
–)ÿd “sales,” or pages 10 thrz†°dONLNd
§ê
–ú)nough 12 of the °dONLNd
≥ù䩪(¶ä
document. °dONLNd
æØ䪢*FigurR¿°dONLNd
√Ø¢ª∂)e 3-4@°dONLNd
»Ø∂ªÁ) shows the  °dONLNd
”Ø˪
m)2Apple event attributes and dirø†°dONLNd
ÒØ
mª
)Ö#ect parameter for the Get Data even‡°dONLNdت)ût °dONLNdºä»å(≈ä
ih`°dONLNdºç»ö)ntrA °dONLNdºö»»)
oduced in ˇ°dONLNd$º»»‡).Figurª†°dONLNd)º‡»Ù)e 3-2Y °dONLNd.ºı»
)    . The dir^°dONLNd7º
»
Ô)%1ect parameter for the Get Data event sent by the °dONLNdh…ä’
#(“ä#SurfCharter application describes t\ °dONLNdã…
$’
1)öhe w °dONLNdé…
1’
4)
r< °dONLNdè…
5’
_)    equested ˆ°dONLNdò…
^’
≠))Apple event objecNÄ°dONLNd©…
Æ’
∏)Pt a‡°dONLNd¨…
π’
◊)s a tabl@°dONLNd¥…
ÿ’
˚)    e called °dONLNdΩ÷ä‚è(flä
“°dONLNdæ÷è‚⁄)Summary of Sale´¿°dONLNdÕ÷⁄‚„)Ks”Ë¿°dONLNdœ÷„‚)    A in the document “Sales Report.” Both the table and the document °dONLNd„äÔí(ÏäarE°dONLNd„ìÔö)    e 0@°dONLNd„öÔ
V)+Apple event objects. The description of an ·†°dONLNd?„
UÔ
§)ªApple event objec: °dONLNdP„
•Ô
œ)P
t always ip`°dONLNdZ„
œÔ
Ì)*nclude܇°dONLNd`„
ÌÔ
Ò)
s√‡°dONLNda„
ÒÔ
˚) a °dONLNddä¸√(˘ädescription oV‡°dONLNdqƒ¸¸):f its location.“@°dONLNdÄ¸¸
>)8 In most cases, †Ä°dONLNdê
>¸
†)BApple event objects arΩ`°dONLNd¶
†¸)be located inside other °dONLNdΩ˝ä
    „(
äApple event objects.


+H
<4
,H
<"
,H]

ˇ·ˇ‚7^
    °dONLNd“
!ä
,¥*#
Figure 3-4°dONLNd›
!Ã
,fl)BMajoˇ†°dONLNd·
!fl
,
f)#r attributes and direct parameter oÉ–°dONLNd
!
g
,
∞)àf a Get Data event


;H≠4
<H¨


<H≠4
;G
<Hò@@
˜@
˜
<H
|?¡¡?Àˇ¯?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘ò@@Ä
˜@Ä
˜
|H
º??ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?‹ˇ˝ıˇÄ˘?ˇˇ˛‡
„ˇ˝ıˇÄ˘?ˇˇ˛`
„ˇ
p˛ıˇÄ˘?ˇˇ˛Ä
„ˇ
à˛ıˇÄ˘?ˇˇ˛
¡„ˇ
Ò˛ıˇÄ˘?ˇˇ˛!„ˇ
Ò˛ıˇÄ˘?ˇˇ˛„ˇÒ?¿ıˇÄ˘?ˇˇ˛ …„ˇü¿0ıˇÄ˘?ˇˇ˛B•„ˇ^ÃıˇÄ˘?ˇˇ˛ D    S„ˇ<ıˇÄ˘?ˇˇ˛ ࣄˇÄıˇÄ˘?ˇˇ˛A S„ˇ @@ıˇÄ˘?ˇˇ˛A@#„ˇ Ä ıˇÄ˘?ˇˇ˛B@%„ˇAêıˇÄ˘ò@Ä¿
˜Ä¿
˜
ºH
¸??ˇˇ˛B Ä„ˇÅ%HıˇÄ˘?ˇˇ˛D Ä
„ˇÇ BàıˇÄ˘?ˇˇ˛$!
„ˇÒ ¡HıˇÄ˘?ˇˇ˛$A
„ˇÒA†àıˇÄ˘?ˇˇ˛A?
„ˇÒAêıˇÄ˘?ˇˇ˛G„
„ˇÒÇàpıˇÄ˘?ˇˇ˛O„}„ˇÒÉDıˇÄ˘?ˇˇ˛
¯„˝„ˇêÜ¢ıˇÄ˘?ˇˇ˛¯„無ëQıˇÄ˘?ˇˇ˛=„無A®ÄıˇÄ˘?ˇˇ˛:˜ç„ˇ1T@ıˇÄ˘?ˇˇ˛=Λ„ˇ* ıˇÄ˘?ˇˇ˛:˜≠„ˇ    0ıˇÄ˘?ˇˇ˛}Λ„ˇÇ
»ıˇÄ˘?ˇˇ˛∫˜≠„ˇÇ»ıˇÄ˘?ˇˇ˛}Λ„ˇ
ÅıˇÄ˘?ˇˇ˛∫˜≠„ˇÄÅıˇÄ˘?ˇˇ˛}Λ„ˇA¯ıˇÄ˘?ˇˇ˛Ôæ˘„ˇ"ıˇÄ˘?‹ˇıˇÄ˘?‹ˇ˝ıˇÄ˘?‹ˇ˝ıˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘ò@¿

˜¿

˜
¸H<??ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘ò@

@
˜

@
˜<H|??ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘ò@
@
Ä
˜
@
Ä
˜|Hº??ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘ÀˇÄ˘¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ºH¸?¡
|8»
$ »
 "`»
8"†»
C°„»
"D"$@»
g¯|‡»¡¡¡¡¡(?
Ä AÅHÄ04˛`
¿É‡ Ê(@@bÄHÄ˛Ä Å Ê($=@@¿SÖ˝uƒ·lpv»¯QYuèÖ¡H¡ÚÖ“flÊ($K(°¡@U+*
Hñ≤㥆•PÍ¢öñ*
Çà
Ç%
UjÊ($"Ii¿?‡YIJê§ó‰•!): L§íºrÑà}IûLÊ($C1— ÄëzTŸ5ê'Õan"ó«§&Då1Ç/o®ûÊ($bqp·¡¿”“$ë&≈I±∫ eE%<    œ JGîÊ˛à¸ıÄ˝
›˛à¸ıÄ˝›˛p¸ıÄ˝›¡¡(1ÙÄ    ‡˛

 

Ê'¶(˝

 
êÊ)%•0‹¨¥§åΩƒ÷÷F»Àílæ¥:/ëlr
R@éñ˘¿Á($≈PIQ{‘ïI+DjjÀIU4‘JVU¥%͆‚´RÊ)%#EêSíRô"RJD    JJZR&)$òRí‚$§IâM¡Úa¿Á)%!â$⁄#Â-Ø€T¬:êêt⁄ˇ:L<î≥Ø5Ljíó
D@Á)%qÕ:4ë‚ò…í$Ńîî\ë*$I(à⁄“"HDÃd„‚<£ÄÁ˝˛!ı¯
Ä‚˝˛!ı¯
Ä‚˘!Î
Ä‚¡¡?¿
F ¿`¬¿ÿÄ
¸à  @ë@ÿ¢˛Àël:rAêewQ»hÆ·»îŸ$    ¥Bï§Æ®Rî8tï’ïzŸ),Ò&$§<.˚Ù«
d∏ ~ò‰ªíŸM∏:?5LH
"Ia
µ†0åI,%¢$Ÿi-“*"Ht˜CúÊN&‹ÿsú…Δ›ÿŸı˚
˛ Ÿı˚
˛ Ÿı˚
˛ Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡8Ä@pÕ@@ ÕRíYH‚∞-òŒò@
¿
Ú
˜
¿
Ú
˜¸H.?ÔU´πE@F®ŒJn%)+é@D¿Œ"î∏ÍBN»ÄâÿŒgc'Qãáà…"Œ˛Ñ˛Ã˛Ñ˛Ã
˛Ñ˛…¡¡<<@Ú‡ ÷
†@  ÷\"'ñ«[!"rÑI÷H$_Yr[Äÿ®,Y+JMQ"Öôj®    ,¢"•$◊!0(ôJRâëDyäK–
Eú$…#Äÿ!¯$¶T÷”¢FéëgGÍ@ÄÿqPrN$õíB¸Í îÒEºEDG◊¸˛˛—¸˛˛—
¸˙œ¡¡?¿
     Ä
ÑÄÀ    ¢˛Àä¿àÄÀ    $    àÄÀ    ),Ò&%HÄÀM∏:?*I i-“*ñ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜
<H
|?
¡¡ 3¯À
¯ Ã
¯ ĢÀ
¯ Ģ Ã
¯À
¯ Ã
¯ ĢÀ
¯ Ģ Ì
¿‚
¯Ï
¿˛`Ê
¯ Ó
Á˚q€ÁÊ
¯Ì
ÊÔ˚Ô˜‡ÂĢÌ6Ô√á‡Ê
¯Ì7˚yϘÂĢ Ì
`‚
¯Ï
`‚
¯ Ã
¯ ĢÒÙˇ¿Í
¯ÒÙà‡ÈĢ ÚÙ`Í
¯ÒÙ`Í
¯ Ú˝"#‚'¢¸"`Í
¯Ò˝`Δ¡Ä˝`ÈĢÒ˝Êˇ¯˝`Í
¯Ò˝àåˇŒflº˝à‡ÈĢ Ú˝xΔ˜Ï˝`Í
¯Ò˝ÔÁü¸˝`Í
¯ ÚÙ"`Í
¯ÒÙ`ÈĢÒÙ`Í
¯ÒÙà‡ÈĢ ÚÙ`Í
¯ÒÙˇ‡Í
¯ ÚÙ`Í
¯ÒÙ`ÈĢÒÙ`Í
¯ÒÙ`ÈĢ ÚÙ`Í
¯Ò    x
Ä˝`Í
¯ Ú
@êÄ ˛`Í
¯ÒD≥∏÷;罉¸@`ÈĢÒ
z˙Q?fôîæ˛`Í
¯Ò
CBQíôî∞˛`ÈĢ Úz:H˜wI„û@`Í
¯ÒÙ`Í
¯ ÚÙ`Í
¯ÒÙ`ÈĢÒ¿¸ ¸`Í
¯ÒCx‡
¸`ÈĢ ÙYââ€qcŒ˝`Í
¯Û¯båÇ,à…!˝
`Î
¯ ÙSâä(˙)!?˝`Ï
¯Û<fiflqfi3«¯Δ˝`ÎĢÛ‡Ù`¿Ì
¯ÙÄÙ`xÏĢ ı<Ùˇ‡Ì
¯ı
‡∞Ù`
‡
‡Ó
¯ò@@Ä
˜@Ä
˜
|H
º?
 ˆ‡Ù`<<Ó
¯ı<p¿x∏
˚`ÄÄÓĢ!ˆ
‡¿@§ÇÄ˝`¯Ô
¯!ˆD≥∏§7˚ìÒ˝`ÓĢ# ˜8pz˙P§z™R¯˝`
‡Ô
¯#˜
‡¿CBP§J™R¿˝`˛<
¿
¯% ¯˛    z:H∏9kéy˝`˛Äp
¯˜x˛Ù`˝
ÔĢ˜p¿˛Ù`˝

¯¯
¿˝Ù`˝
¿Ģ ˘x˝¿ˆ`˝ÄpÒ
¯ ¯
¿˝Cx˚`¸
‡Ò
¯" ˘
0¸YâÅfiHû ¸`¸
8Ò
¯!¯
‡¸båö(I»p¸`¸
¿ÒĢ"˘Ä¸SâãÈJIê¸`¸ÄcÚ
¯!˘p¸fiflpΔÒÊx¸`˚
‡?ÒĢ ˙
¿¸Ù`˚0ÄÛ
¯˘
0˚Ù`˚ÄÛ
¯ ˙
`˚Ù`˚¿Û
¯˙
¿˚Ù`˚
¿@ÚĢ˙p˚Ùˇ‡˙
``Û
¯˙
¿˚Ù`˙
  ÚĢ ˚
˙Ù`˙
` Û
¯˙
˙Ù`˙
?Û
¯ ˚
˙¯˛D˛˛`Í
¯˙

˙ DÑ
`ÈĢ˘¿˙#gg1›±‹o˜'‚`Í
¯Ò'…Úze{0Ù‘•`ÈĢ Ú$…ÇJe@Ãî‘•Ä`Í
¯Ò#«q9›;∏rWÚ`Í
¯ Ú
˜`Í
¯¸ ˜˜`ÈĢ˝(@˘Ù`˘Û
¯"˝
Œ‡˘     ˝`˘ÚĢ' ˛È@˘     `0˝`˘m,¿ˆ
¯&˝+    @˘
nu3s8ñ¯|¿˛`˘¯æĈ
¯( ˛
 È ˘
˘MO¥§∂d3‡˛`˘à–Ĉ
¯Ò    ôMD¥§jd3˝`˘xéÄıĢÒ
~u;ì$J$‡˛`Í
¯Ò@˜`ÈĢ ˝@˘@˜`Í
¯¸ĢÙ`¯
`
ı
¯ ;ôôÕ¿˙ˆ`¯
@ı
¯)˛¶Z|” ˙˛ÃIJ`˙Ófg7ıĢ*˛¶Z$” ˙
y¯‹∂Ñõ8IJ`˙ôiÛLĘ
¯)˛ªô‹M ˙     eÏØU D˝`˙ôhìLÄˆÄ˘& ˛"ˆ    :e,®zJ|˝`˙Ógq4Ę
¯˝"ˆ    ȉÁßI‰˝`˘àÛ
¯ Ú@˜`˘àÛ
¯ÒĘ`ÈĢÒÙ`Í
¯¸
‡¯Ù`ÈĢ ˝
`¯Ùˇ‡˘pÛ
¯¸
įÙ`˘àÛ
¯ ˛
¿˘Ù`˙

Û
¯˝ ˘Ù`˙

ÚĢ˝˘Ù`˙
?¿ı
¯˝ »˘
ı˘ü¿0ÙĢ ˛B§˘

‡ı
Ä˙^Ãı
¯˝ D    R¯¿ı˘<ı
¯ ˛ à¢˘

Äı˘Ĉ
¯˝A R˘Ù|˘ @@ıĢ˝A@"˘Ù¯˘ Ä ˆ
¯˝B@$˘ı

˘AêıĢò@Ä¿
˜Ä¿
˜
ºH
¸?
! ˛B Ģr˜
¿˘Å%Hˆ
¯$˝D į0H˛˝
ĢÇ Bàˆ
¯' ˛
$!˜    ~Kò›ÃÕ°æ`˛
¿˙
 ¡Hˆ
¯&˝$A¯
>K=)>üSfl_‡˛`˙
A†àıĢ%˝A?¯    K!    2ìR@˝`˙
Aêˆ
¯%˝G„¯    sÂŒèQœ@˝`˙
ÇàpıĢ" ˛O„|˘˛
¯`˙
ÉDı
¯˝
¯„¸˘˛
¯`˘êÜ¢ı
¯ ˛¯„å˘Ù`˘ëQı
¯$˝=„å˘  ¸`˘A®ÄıĢ$˝:˜å˘ @¸`˘1T@ˆ
¯$˝=΋˘`ÏÌƈpŒ¸`˘* ıĢ& ˛:˜¨˘Ò?ì)YI$¸`˘    0ˆ
¯$˝}΋˘ë0q)YI$¸`˘Ç
»ˆ
¯& ˛∫˜¨˘pÔœ.6Hƒ¸`˘Ç»ˆ
¯ ˝}΋˘˝˘`˘
ÅıĢ˝∫˜¨˘˝˘`¯Äň
¯˝}΋˘Ù`¯A¯ıĢ% ˛Ôæ¯˘@˛
IJ`¯"Ù
¯Ò
@`¯Ù
¯ Ún
ÁLY‹Œòfi`Í
¯Ò˘îfi=}))Ω(`ÈĢÒôî–!°))°`Í
¯ÒyÁN$ŒúÊ`ÈĢ% ,į˛Ñ¸Ä˛`˙
¿    !ı
¯&˛ÄrĢ˛Ñ˝
˝`˙  @ˆ
¯! N‡Êo∞˙Ù`˙
ì∫≠ÌĘ
¯&˛
Ã`üG‡˙ ˛@¸`˘s…_ıĢ'˛ÃbôF ˙Ñ ˛@¸`˙3…Qˆ
¯'˛<\óC‡˙a˜,8⁄¿¸`˙
œI/ıĢ Ú¸æ%ı>@¸`Í
¯ÒêÃ∞%5"@¸`Í
¯ Úp.$ı¿¸`Í
¯ÒÙ`ÈĢÒÙ`Í
¯ÒÙ`ÈĢ ÚÆ˝p ˛`Í
¯Ò±˝à ˛`Í
¯ Ú
ùH‹c,p˛`Í
¯Ò
öï>I(æ¿˛`¯
ÛĢÒ
öï&)(å∞0˛`¯
Äı
¯Ò
zï0»sƇ˛`¯
¿ÙĢ ˝
‡¯¸ ˙`¯
`ı
¯¸
 ¯¸@˙`¯
0ı
¯ ˝
 ¯Ù`¯
:xı
¯¸
 ¯Ä@˚ `¯
@ÙĢ"¸
`¯P@˛Ä `¯
@ı
¯"¸
†¯∏¸¡ÿ”°π‹Õ‡`¯
¿ÙĢ$ ˝
 ¯§S‚e3S‰ìÍü `¯
@ı
¯"¸
 ¯§SeR$ì*ë `¯
    @ı
¯$ ˝
 ¯§2·ÿÔQ‰RÍé‡`¯

@ı
¯¸ ˙Ù`¯
@ÙĢ¸`¿˚Ù`¯
@ı
¯¸†x˚Ù`¸
¿¿ÙĢ) ˝ 
˚Æ8 ¸`¸p@ı
¯'¸ 

˚±$¿¸`¸    @ı
¯) ˝ 
˚ié$‹Õ¿¸`¸
@ı
¯'¸ 
˚˚ÿ9Û(ĸ`¸0@ÙĢ(¸`
Åĸö%(ĸ`¸0`@ı
¯(¸†Ä¿¸y‹$¸»@¸`¸`¿¿ÙĢ& ˝ ‡`¸¸˙`¸AÄ@ı
¯$¸ 0¸¸˙`¸√˛
    @ı
¯# ˝ ú¸Ù`˝

ܲ

@ı
¯!¸ ¸Ù`˝
˛
@ÙĢò@¿

˜¿

˜
¸H<?
!¸`¸Ù`˝
˛
@ı
¯!¸†
ɸÙ`˝
˛
¿ÙĢ$ ˝
 ˛
¡Ä˝Ù`˝
0˛
@ı
¯"¸
 ˛
`¿˝Ù`˝
0`˛
    @ı
¯$ ˝
 ˛
0`˝Ùˇ‡˝
`¿˛

@ı
¯"¸
 ˛
0˝
Ùˇ‡˝
¡Ä˛
@ÙĢ¸
`˛
Î
É˝
@ı
¯¸
†˛
Î
˝
¿ÙĢ ˝
 ˛
Î
˝
@ı
¯¸
 ˛
ÅÄÏ
8˝
    @ı
¯ ˝
 ˝
¿‡Ï
`p˝

@ı
¯¸
 ˝
`8Ì
¿¿˝
@ÙĢ¸
`˝
8Ì
Ä˝
@ı
¯¸
†˝
Ì
¸
¿ÙĢ ˝
 ˝
ÄÓ
¸
@ı
¯¸
 ˝
¿‡Ó
0¸
    @ı
¯ ˝
 ¸
`0Ô‡p¸

@ı
¯!¸
 ¸
8˙¿
ĢÄ¿¸
@ÙĢ$¸
`¸
˙¿
Ä0¸ĸ
@ı
¯%¸
†¸ĸ
ÁΩÒ€Áx¸
˚
¿ÙĢ' ˝
 ¸
¿¿¸
ʘ˚Ô˜∞¸
0˚
@ı
¯$¸
 ˚
`ĸ6˜√á∞¸
 8˚
    @ı
¯& ˝
 ˚
9ĸ7Ω˘Ï˜∏¸
``˚

@ı
¯¸
 ˚˙
0¯
@ ˚
@ÙĢ¸
`˚˙
0¯
ˇ˚
@ı
¯¸
†‡
¿ÙĢ ˝
 ‡
@ı
¯¸
 ¯Ùˇ¿¯
    @ı
¯ ˝
 ¯Ù"`¯

@ı
¯¸
 ¯Ù`¯
@ÙĢ¸
`¯Ù`¯
@ı
¯¸
†¯¸àºàË¸à‡¯
¿ÙĢ  ˝
 ¯¸6`¸`¯
@ı
¯¸
 ¯¸6Ô{¸`¯
    @ı
¯  ˝
 ¯¸"?ˇÔ¸"`¯

@ı
¯¸
 ¯¸7çÓ¸`¯
@ÙĢ¸
`¯¸6ˇn¸`¯
@ı
¯¸
†¯˚à
åé¸à‡¯
¿ÙĢ ˝
<¯˚
¸`¯
@ı
¯¸
¯Ù`¯
    @ı
¯ ˝
0¯Ù"`¯

@ı
¯¸
`¯Ù`¯
@ÙĢ¸
¿¯Ùˇ‡¯
@ı
¯¸

įÙ`¯
¿ÙĢ ÚÙ`Í
¯ÒÙ`Í
¯ ÚÙ`Í
¯ÒÙ`ÈĢÒ8˝‡@˝`Í
¯ÒD˝@˝`ÈĢ Ú
1:46ë∏ΔX‡˛`Í
¯Ò
5*|íP?}IJ`Í
¯ Ú
E5*LRQ``˛`Í
¯Ò
8ı*<aêÁ]¿˛`ÈĢÒ¸@˙`Í
¯Ò¸Ä˙`ÈĢ ÚÙ`Í
¯Ò1òˆ0
ÿ¿3Ä`Í
¯ ÚJdH%     L`Í
¯Ò
d)H•     `ÈĢÒdF0e 0Ä`Í
¯ÒJdIHe     DÄ`ÈĢ Ú1òF0
ò¿{`Í
¯ÒÙ`¸?˘ˇ¯
¯ò@

@
˜

@
˜<H|?
  ?˙ˇ¸Ù`¸ ˙
ø˙
¯  ˙¸Ù`¸ ˙
ĢĢ(=˜Ä˛ø¯¸Ù`¸
 

Ä˙
¯(
=å@•¯¸Ù`¸
 ƒDDH
Ä˘Ä˘(
 =å@•¯¸Ù`¸
 2!
Ä˙
¯(
=â÷lfWΩ¯¸Ùˇ‡¸
 TETA
Ä˙
¯$
 =Ö÷LfW°¯¸
Ùˇ‡¸ ˙
Ä˙
¯
=˜ç÷ofWø¯Ë?˘ˇ
ĢĢ ˙Ë ˚

Ä˙
¯?˙ˇ¯Ë ˚

ĢĢ  ˚
    òË ˚

Ä˙
¯ ˚
ÿÍ˛ ‚$

Ä˙
¯  ˚
xÍ 
 $

Ä˙
¯"
!ê¯Í 
2…<¿

ĢĢ"
"P
òÍ 
+À•¿
ˇÄ˙
¯"
"∏l“ÃòÍ 
+⺇

ĢĢ
 "UËô˚‹¯Í ˚

Ä˙
¯
!îËiö¯Í ˚

Ä˙
¯  ˚
Í ˚

Ä˙
¯ ˚
Í @T

ĢĢ"" ˛
Í @T(

Ä˙
¯(
" 8˛  
„W,`

ĢĢ(
 #©Ûj—6@$˛  ‘Ø*‡

Ä˙
¯(
"i$´Ƈ%≥78 S.*p

Ä˙
¯%
 #ë„f—ßp;Á¶|§¯ ˚

Ä˙
¯# ¸
"d¶L§ ˚

ĢĢ& !¸
!„û?$ @

Ä˙
¯# ˚
Ó B

ĢĢ#  ˚
Ó8 
•ò @

Ä˙
¯ ˚
Í ˜π^‡

Ä˙
¯#  ˚
Ó  5Œh

Ä˙
¯  ˚
Ó ˚

ĢĢ  ˚
Ó7,n ˚

Ä˙
¯  ˚
ÓLæî ˚

ĢĢ   ˚
ÓL∞Ñ ˚

Ä˙
¯  ˚
Ó7.r ˚

Ä˙
¯  ˚
Ì ˛ ˚

Ä˙
¯ ˚
Ì@˝ ˚

ĢĢ ˚
Ë ˚

Ä˙
¯ ˚
Ë ˚

ĢĢ  ˚
Ë ˚

Ä˙
¯ ˚
Ë ˚

Ä
¿˝
¯  ˚
Ë ˚

Ä
 ˛
@
¯ ˚
Ë ˚

Ä
,i–‹‡Ä˘  ˚ˇÄÍ ˚

Ä
2ô©Ú@
¯! ˚¿Í ˚

Ä
2â©@Ģ"  ˝``Í ˚

Ä
Ãw®Ú 
¯  N¥ŒÜ` Í ˚

ġ˚
¯!  Mjjâ@ Ï˛ ˚

Ä˙
¯$ 
Mj©â@ Ï 
¿˛

ĢĢ' =ji@ Ï 'M3°ò

Ä"˝
¯) ˛
 Ï 
¶™ö¢P

Ä  ˛Ä˘(  ˛ Ï f™™bP

Ä
∫cp
¯( ‚˛ Ï û™öAê

ÄfÙ†
¯'  
F Ï ˝@

ÄfÑ 
¯( Œ® Ï ˝
Ä

Ä
∫sê˛Ä˘& 6‰ Ï 
¬˝

Ä˝
¯' 
ŒN Ï 2F˛

ĸĢ!  ˚ Ï 
ö®˛

Ä˙
¯! ˚ Ï j‰˛

Ä˙
¯!  ˚ Ï öN˛

Ä˙
¯( ˝ê p
ÄÙ ˚

ĢĢ) ¿h HÄÙ ˚

Ä˙
¯) c0<ÿ K>=d≥ÄÙ ˚

ĢĢò@
@
Ä
˜
@
Ä
˜|Hº?
+  »˚º    $?OüôÚ¸ÄÙ ˝ˇ‡

Ä˙
¯, 4…ùfiÿ LôÉDÄÙ 
 

Ä˙
¯0  …/2 sèâr;į>Ä 
 

Ä˙
¯( s3Ô Ä c1H 

ĢĢ( Gw ‹ò¯ …¥ 

Ä˙
¯( äÕ     Úº 4…l 

ĢĢ/  ˚ªÄ  Ñ"˜    2† …í 

Ä˙
¯1 ˇÄ @Ñ @˘¸ú s1l 

Ä˙
¯-  "Ä ˆh>‰√:f‡ı 
 

Ä˙
¯- âÄ iT˘@ı 
 

ĢĢ- E iTï¶à@ı 
 

Ä˙
¯0 ã fT‰„:w ˘  ˝ˇ‡

ĢĢ,  
" ˚˜ 
 

Ä˙
¯, 
ë&8 ˚˜7,n 
 

Ä˙
¯(  òÚ<Q  Læî 
 

Ä˙
¯( dx30 L∞Ñ ;1Œ 

ĢĢ( d¿L 7.r $…
( 

Ä˙
¯' d70¯`Ô  4…l 

ĢĢ&  ò˝ò@Ô@ …    Ç 

Ä˙
¯! ˚
ò
¿Ï 31Ï 

Ä˙
¯   ˚¯ˇÎ 
 

Ä˙
¯ ˚
XÍ 
 

ĢĢ ˚
ÿÍ ˝ˇ‡

Ä˙
¯ ˚
    òÍ ˚

ĢĢ ?˙ˇ¯Í˛?˘ˇ
Ä˙
¯ ˚
Ë ˚

Ä˙
¯  ˚
ÿË ˚

Ä˙
¯ ˚
ÿË ˚

ĢĢ ˚
ÿË ˚

Ä˙
¯ ˚

XË ˚

Äp˘Ä˘  ˚
ÿË ˚

ø¿˙
¯?˙ˇ¯Ë?˘ˇÄ˘
¯ ˙ˇ¯Ë˘ˇÄ˘
¯ ĢÀ
¯ Ģ Ã
¯À
¯ Ã
¯ ĢÀ
¯ Ģ Ã
¯À
¯ 3¯ÀÃĢ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ºH¸?
¡
|8»
$ »
 "`»
8"†»
C°„»
"D"$@»
g¯|‡»¡¡¡¡¡(?
Ä AÅHÄ04˛`
¿É‡ Ê(@@bÄHÄ˛Ä Å Ê($=@@¿SÖ˝uƒ·lpv»¯QYuèÖ¡H¡ÚÖ“flÊ($K(°¡@U+*
Hñ≤㥆•PÍ¢öñ*
Çà
Ç%
UjÊ($"Ii¿?‡YIJê§ó‰•!): L§íºrÑà}IûLÊ($C1— ÄëzTŸ5ê'Õan"ó«§&Då1Ç/o®ûÊ($bqp·¡¿”“$ë&≈I±∫ eE%<    œ JGîÊ˛à¸ıÄ˝
›˛à¸ıÄ˝›˛p¸ıÄ˝›¡¡(1ÙÄ    ‡˛

 

Ê'¶(˝

 
êÊ)%•0‹¨¥§åΩƒ÷÷F»Àílæ¥:/ëlr
R@éñ˘¿Á($≈PIQ{‘ïI+DjjÀIU4‘JVU¥%͆‚´RÊ)%#EêSíRô"RJD    JJZR&)$òRí‚$§IâM¡Úa¿Á)%!â$⁄#Â-Ø€T¬:êêt⁄ˇ:L<î≥Ø5Ljíó
D@Á)%qÕ:4ë‚ò…í$Ńîî\ë*$I(à⁄“"HDÃd„‚<£ÄÁ˝˛!ı¯
Ä‚˝˛!ı¯
Ä‚˘!Î
Ä‚¡¡?¿
F ¿`¬¿ÿÄ
¸à  @ë@ÿ¢˛Àël:rAêewQ»hÆ·»îŸ$    ¥Bï§Æ®Rî8tï’ïzŸ),Ò&$§<.˚Ù«
d∏ ~ò‰ªíŸM∏:?5LH
"Ia
µ†0åI,%¢$Ÿi-“*"Ht˜CúÊN&‹ÿsú…Δ›ÿŸı˚
˛ Ÿı˚
˛ Ÿı˚
˛ Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡8Ä@pÕ@@ ÕRíYH‚∞-òŒò@
¿
Ú
˜
¿
Ú
˜¸H.?
ÔU´πE@F®ŒJn%)+é@D¿Œ"î∏ÍBN»ÄâÿŒgc'Qãáà…"Œ˛Ñ˛Ã˛Ñ˛Ã
˛Ñ˛…¡¡<<@Ú‡ ÷
†@  ÷\"'ñ«[!"rÑI÷H$_Yr[Äÿ®,Y+JMQ"Öôj®    ,¢"•$◊!0(ôJRâëDyäK–
Eú$…#Äÿ!¯$¶T÷”¢FéëgGÍ@ÄÿqPrN$õíB¸Í îÒEºEDG◊¸˛˛—¸˛˛—
¸˙œ¡¡?¿
     Ä
ÑÄÀ    ¢˛Àä¿àÄÀ    $    àÄÀ    ),Ò&%HÄÀM∏:?*I i-“*ñ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜.Hn?¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜nHÆ?¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜ÆHÓ?¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜ÓH.?¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜.Hn?¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜nHÆ?¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ÆHÓ?¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜ÓH ?¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜.Hn?
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜nHÆ?
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜ÆHÓ?
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜ÓH.?
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜.Hn?
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜nHÆ?
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ÆHÓ?
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜ÓH ?
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ"(@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-12    )BAbout ‡)Apple Events4^*¿
¯
°dONLNd\lhr(el
Tµ¿°dONLNd
\qhÇ)o prr`°dONLNd\Éh€)ocess the informatioc °dONLNd\‹hÁ)Yn iú‡°dONLNd\Áh
s)n the Get Data event, the SurfWs°dONLNd;\
sh
‚)åriter application calls the ,
Courier°dONLNdWilufi(rlAEProcessAppleEventx‡°dONLNdjifiu
)r function. The B‡°dONLNdyi
u
ê)@AEProcessAppleEvent;¿°dONLNdåi
êu
‡)r function uses the °dONLNdüvlÇ
ù(lFevent class and event ID attributes to dispatch the event to the SurfW<Ä°dONLNdÂv
ùÇ
Ì(
ùriter application’s °dONLNd˘Élè⁄(ålhandler for the Get Data J‡°dONLNd
É⁄è
)nApple event. dONLNd
É
è
Á);/The SurfWriter application responds to the Get °dONLNd
Nêlú´(ôlData event by 
c†°dONLNd
\ê¨ú÷)@    resolving(`°dONLNd
eê◊ú
Ô)+A the description of the Apple event object—that is, by using the °dONLNd
¶ùl©¢(¶l    AEResolve|†°dONLNd
Øù¢©
¨)6; function, other Apple Event Manager routines, and its own °dONLNd
Í™l∂
π(≥lJapplication-defined functions to locate the table named “Summary of Sales.ç@°dONLNd4™
π∂
⁄(≥
π” After °dONLNd<∑l√ï(¿l
locating tõ¿°dONLNdF∑ï√∑))he table2¿°dONLNdN∑∏√Û)#, SurfWriter a¿°dONLNd\∑Ù√
˜)<=dds a copy of the table’s data to the reply event, which the °dONLNdôƒl–
’(ÕlOApple Event Manager then sends to the SurfCharter application. The SurfCharter °dONLNdË—l›
*#application then displays the data ò‡°dONLNd—
›
)òin “†°dONLNd—
›
b)its active window. >@°dONLNd!—
c›
e)T
 °dONLNd#„lÔr(Ïl
T†¿°dONLNd$„rÔ∏)he next section, *@°dONLNd5„πÔ·)G    “Data Str
†°dONLNd>„‚Ô˘))ucturêÄ°dONLNdC„˘Ô
)es WäÄ°dONLNdG„
Ô
%)ithin b°dONLNdM„
%Ô
h)Apple Events,”ª‡°dONLNd[„
hÔ
«)C describes the data strQ@°dONLNdr„
»Ô
fl)`uctur◊ °dONLNdw„
flÔ
Í)es °dONLNdzl¸|(˘lthe °dONLNd~|¸
)Apple Event Manager uses for V@°dONLNdõ
¸
¥)â'Apple event attributes and parameters. 


!*
(
¯4
"*
(
¯ 
#l
#
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd√
l
!€(
lData Structures Wué°dONLNd‘
‹
!¯)pithin h¬°dONLNd⁄
¯
!
H)Apple Eventsˇˇˇˇˇˇ€r)¯
3
°dONLNdË
(l
4r(
1l
T†¿°dONLNdÈ
(r
4)he ]`°dONLNdÏ
(
4˛)Apple Event Manager constr°`°dONLNd
(˛
4
{)ucts its own internal data strL°dONLNd$
(
|
4
ì)~uctur—‡°dONLNd)
(
ì
4
›)es to contain the °dONLNd;
5l
Aª(
>linformation in an Ë °dONLNdM
5ª
A
q)O)Apple event. Neither the sender nor the rÌ°dONLNdv
5
q
A
´)∂eceiver of an ˜¿°dONLNdÑ
5
´
A
fi):
Apple even °dONLNdé
5
fl
A
‰)4t °dONLNdê
Bl
Nï(
Klshould mc °dONLNdò
Bñ
N’)*anipulate data¯†°dONLNd¶
B’
N‰)? dirA¿°dONLNd™
BÂ
N˘)ectly5Ä°dONLNdØ
B˙
N
|) after it has been added to an ı °dONLNdŒ
B
{
N
ƒ)ÅApple event; eacy¿°dONLNdfi
B
≈
N
Ó)J    h should °dONLNdÁ
Ol
[o(
Xl
rE°dONLNdË
Op
[ç)ely on n†°dONLNdÔ
Oç
[
?)&Apple Event Manager functions to do sod`°dONLNd
O
@
[
E)≥. °dONLNd
al
m
G(
jl2This section describes the most important data str€°dONLNdJ
a
G
m
^)€uctur`‡°dONLNdO
a
_
m
†)es used by the &¿°dONLNd^
a
†
m
ÿ)AApple event °dONLNdj
nl
zº(
wlManager to constrfl°dONLNd{
nº
zÃ)Puct ∫`°dONLNd
nÃ
z
$)Apple events. The fi䆰dONLNdì
n
%
z
>)Yrst str⁄†°dONLNdö
n
>
z
U)uctur`Ä°dONLNdü
n
V
z
ÿ)e described is the descriptor rf¿°dONLNdæ
n
ÿ
z
Í)Çecor€ °dONLNd¬
n
Í
z
Ú)d,v‡°dONLNdƒ
n
Û
z
ı)    
 °dONLNd≈
{l
áî(
Ñl
a data str< °dONLNdœ
{ï
á¨))uctur¬°dONLNd‘
{¨
á‘)
e of type r@°dONLNdfi
{’
á˘))AEDescp°dONLNd‰
{˘
á˛)$. †°dONLNdÊ
{˛
á
G)Applications ma ¿°dONLNdı
{
G
á
T)Iy a/‡°dONLNd¯
{
T
á
‹) ccess the data in an individual °dONLNd
àl
îü(
ëldescriptor rfl@°dONLNd$
àü
î±)3ecorS†°dONLNd(
à≤
î«)d dir∏Ä°dONLNd-
à«
î
$)ectly if it is not part onÄ°dONLNdF
à
%
î
O)^
f another z‡°dONLNdP
à
O
î
V)*
AB °dONLNdQ
à
W
î
‘)pple Event Manager data str‡°dONLNdl
à
‘
î
Î)}ucturk¿°dONLNdq
à
Ï
î
Û)e.µ`°dONLNds
à
Û
î
ı)
 °dONLNdu
öl
¶o(
£l
IfiÄ°dONLNdv
öo
¶Ô)n some cases it is convenient ¬ °dONLNdî
ö
¶
)Åfor the ˝ °dONLNdú
ö

¶
´)!Apple Event Manager to describe dæÄ°dONLNdΩ
ö
¨
¶
’)ù
escriptor °dONLNd«
ßl
≥o(
∞l
rE°dONLNd»
ßp
≥Ç)ecorπ`°dONLNdÃ
ßÇ
≥¡)ds by data typ⁄†°dONLNd⁄
ß¡
≥ )?es·@°dONLNd‹
ß 
≥
Z)    # that indicate their contents; thusdONLNdˇ
ß
[
≥
b)ë, i~°dONLNd
ß
c
≥
Ç)t also dw°dONLNd

ß
É
≥
ç) efiM`°dONLNd
ß
é
≥
¿)nes data str·Ä°dONLNd
ß
¿
≥
◊)2ucturg`°dONLNd
ß
ÿ
≥
„)es °dONLNd!
¥l
¿§(
Ωlsuch as type `°dONLNd.
¥•
¿Û)9AEAddressDesc[ °dONLNd;
¥Û
¿¯)N, [ °dONLNd=
¥¯
¿
4)
AEDescListW`°dONLNdG
¥
4
¿
L)<, and ƒÄ°dONLNdM
¥
L
¿
|)AERecord¡Ä°dONLNdU
¥
|
¿
ß)0
, which arX‡°dONLNd_
¥
®
¿
fi),e descriptor °dONLNdl
¡l
Õo(
 l
rE°dONLNdm
¡p
ÕÇ)ecorπ`°dONLNdq
¡Ç
Õ›)ds used to hold addr;°dONLNdÖ
¡fi
Õ
)\esses, list’`°dONLNdê
¡

Õ
)(s of oQ@°dONLNdñ
¡

Õ
e)ther descriptor rÄ°dONLNdß
¡
f
Õ
x)Hecort‡°dONLNd´
¡
x
Õ
ö)ds, and ‹`°dONLNd≥
¡
ö
Õ
“)"Apple event °dONLNdø
Œl
ڦ(
◊lparameters, r°dONLNdÃ
Χ
⁄ÿ);espectivelyL°dONLNd◊
Œ◊
⁄
z)0&. These and most of the other data strÏ¿°dONLNd˝
Œ
z
⁄
ë)£ucturr†°dONLNd
Œ
í
⁄
Ë)es described in this °dONLNd
€l
Áñ(
‰l
section ar≠Ä°dONLNd!
ۖ
Á÷)*e formally defiY °dONLNd0
€◊
Á
)Aned as data strâ°dONLNd?
€

Á
.)@uctur‡°dONLNdD
€
/
Á
[)es of type ¸ °dONLNdO
€
[
Á
),AEDesc˘‡°dONLNdU
€

Á
¶)$
; they dif¿°dONLNd_
€
ß
Á
Á)(fer only in the °dONLNdo
Ël
Ù„(
Òlpurposes for which they arw°dONLNdâ
Ë„
Ù

)we used.

*
¯4*
¯ l
¯

ˇ·ˇ‚7^°dONLNdël“(lDescriptor Recordsˇˇˇˇˇˇ‘@(
Ò
3
°dONLNd•l%°("lDescriptor rÄ¿°dONLNd±°%≥)5ecorı °dONLNdµ≥%»)ds ar퇰dONLNd∫…%
])"e the building blocks used by the _ °dONLNd‹
]%
Á)îApple Event Manager to constr€°dONLNd˘
Á%
˜)äuct °dONLNd˝&l2
(/l'Apple event attributes and parameters. fl°dONLNd    $&
2
")Ø
A†°dONLNd    %&
#2
%)
 
ô†°dONLNd    &&
%2
r)descriptor record °dONLNd    7&
s2
ß)N is a data strÛ†°dONLNd    E&
ß2
æ)4ucturyÄ°dONLNd    J&
ø2
Á)
e of type °dONLNd    T3l?ê(<lAEDesc}¿°dONLNd    Z3ê?
©)$D; it consists of a handle to data and a descriptor type that identifz@°dONLNd    û3
©?
È(<
©ies the type of °dONLNd    Æ@lL(Ilthe data to which the handle rÿ†°dONLNd    Ã@L
)Ñefers.°dONLNd    ”Wlc¿(`lTYPE AEDesc = °dONLNd    ‚elqr*
R†°dONLNd    „erqê)ECORD°dONLNd    Ûe
2q
§)¿{descriptor record}°dONLNd
s~ÿ(|~descriptorType:°dONLNd
sÍ
 )l    DescType;°dONLNd
*s
2
z)H{type of dat{Ä°dONLNd
6s
z
Ü)Ha}°dONLNd
:Å~çΔ(ä~dataHandle: °dONLNd
LÅÍç
)lHandle°dONLNd
TÅ
ç
)$
;°dONLNd
WÅ
2ç
Ü)${handle to datz¿°dONLNd
eÅ
Üç
í)Ta}°dONLNd
hèlõr(òl
E†°dONLNd
ièrõÑ)ND;ˇd~@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äAbout ‡)Apple Events

, (‡3-13
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähŒ(eäIf a descriptor r놰dONLNd\Œh‡)Decor°dONLNd\·h
;)d exists separately fr–Ä°dONLNd+\
;h
e)Z    om other 
 °dONLNd4\
fh
Î)+Apple Event Manager data strl °dONLNdP\
Îh)ÖucturÚ°dONLNdU\h)es, °dONLNdYiäu“(räit is possible to r`†°dONLNdli“u
©)H2etrieve the data associated with its handle by der°dONLNdûi
™u
∫)ÿefer≈ °dONLNd¢i
∫u)encing the handle °dONLNd¥väǶ(ätwice. ›@°dONLNdªv¶Ç˙)After a descriptor rV@°dONLNdœv˚Ç
)Uecor †°dONLNd”v
Ç
ï)d has been added to any other }`°dONLNdÒv
ïÇ)àApple Event Manager data °dONLNd

Éäèï(åästrfi°dONLNd
Éïè¨)ucturc‡°dONLNd
É≠èÙ)e, you must use √ °dONLNd
"ÉÙè
\)GApple Event Manager r∑°dONLNd
7É
\è
«)houtines to extract data fr? °dONLNd
QÉ
ȏ
È)lom the °dONLNd
XêäúΩ(ôädescriptor rfl@°dONLNd
dêΩúœ)3ecorS†°dONLNd
hê–úÿ)d.°dONLNd
k¢äÆù(´äThe 
ª¿°dONLNd
o¢ùÆ·)descriptor typeP†°dONLNd
~¢‚Æ

)E     is a strT°dONLNd
á¢

Æ
)ucturŸ‡°dONLNd
å¢
Æ
@)
e of type ,
Courierä °dONLNd
ñ¢
AÆ
q))DescTypeá °dONLNd
û¢
qÆ
ı)0 , which in turn is of data type °dONLNd
æØ䪥(∏äResType}`°dONLNd
≈Ø¥ª¯)*—that is, a fouré`°dONLNd
’دª
w)D-character code. Constants arCÄ°dONLNd
ÚØ
xª)Ä!e usually used in place of these °dONLNdºä»ú(≈äfourÄ°dONLNdºù»
)-character codes when r°dONLNd.º
»
“)i0eferring to descriptor types. Descriptor types rπ†°dONLNd^º
“»
‡)ÃeprJ`°dONLNdaº
·»
˙)esent °dONLNdg…ä’Ò(“ävarious data types. Her”@°dONLNd~…Ò’

)ge ar·‡°dONLNdÇ…

’)=e some of the major descriptor type constants, their values, °dONLNdø÷䂶(fläand th‡°dONLNd≈÷ß‚⁄)e kinds of d—@°dONLNd—÷⁄‚fl)3
a—@°dONLNd“÷fl‚
")ta they identify@°dONLNd‚÷
"‚
$)C
.°dONLNdR
’ä
·
ë(
fiä>For a complete list of the basic descriptor types used by the π°dONLNdê
’
ë
·
Ú(
fi
ëApple Event Manager™Ä°dONLNd£
’
Ú
·)a, see °dONLNd©
‚ä
Óê(
Îä
Tµ¿°dONLNd™
‚è
ÓŸ)able 4-2 on page °dONLNdª
‚Ÿ
Ó·)J4-8‡°dONLNdΩ
‚‚
ÓÏ)    578‡°dONLNdø
‚Ï
ÓÓ)

.°dONLNd¡
Ùä¢(
˝äFigurR¿°dONLNdΔ
Ù¢∂)e 3-5@°dONLNdÀ
Ù∂
ò)6 illustrates the logical arrangement of a descriptor r‡@°dONLNd

Ù
ò
™)‚ecorT†°dONLNd
Ù
´
)d with a descriptor °dONLNd
ä´(
ätype of ʆ°dONLNd!
´€)!typeChar&@°dONLNd)
€
)0, which specifif¿°dONLNd8


X)?es that the dat°dONLNdG

X
e)>a h–`°dONLNdJ

e
Ñ)andle r¥Ä°dONLNdQ

Ñ
î)eferé@°dONLNdU

ï
´)s to aÉ °dONLNd[

¨)n unterminated strin‡°dONLNdo
)\g °dONLNdqäΔ(ä(in this case, t°dONLNdÅΔ
6)<he text “Summary of SaleΩ¿°dONLNdô
6
E)ps”).

<HM4=HM"=H]

ˇ·ˇ‚7^
    °dONLNdû2ä=¥(:ä
Figure 3-5°dONLNd©2Ã=“)B
A0°dONLNd™2“=
) descriptor recor
Ä°dONLNdª2
=
7)Ad whose P°dONLNd√2
7=
K)$data °dONLNd»2
K=
ë)handle refers to a†°dONLNd⁄2
ë=
‡)Fn unterminated striné@°dONLNdÓ2
‡=
Â)O
g
°dONLNd‰Ôä˙À(˜äDescriptor type°dONLNdÙÔ˛˙
)t
V¸/°dONLNdıÔ
˙
)alue°dONLNd˙Ô
6˙
g)3DescriptionÕ`°dONLNdÔ
g˙
Ü)1 of data
°dONLNd˝ä
    Ã(
ätypeBoolean°dONLNd˝˛
    
")t'bool'°dONLNd"˝
6
    
S)81-byte v†°dONLNd)˝
T
    
ç)Boolean valuÄ°dONLNd5˝
é
    
í):
e°dONLNd8
ä
∫(
ätypeChar°dONLNdA
˛

")t'TEXT'°dONLNdH

6

ä)8Unterminated strinxÄ°dONLNdZ

ã

ê)U
g°dONLNd]
ä
)‰(
&ätypeLongInteger°dONLNdm
˛
)
")t'long'°dONLNdt

6
)
l)832-bit intege$¿°dONLNdÅ

m
)
p)7
r°dONLNdÑ
-ä
9Í(
6ätypeShortInteger°dONLNdï
-˛
9
")t'shor'°dONLNdú
-
6
9
l)816-bit intege$¿°dONLNd©
-
m
9
p)7
r°dONLNd¨
=ä
Iÿ(
FätypeMagnitude°dONLNd∫
=˛
I
")t'magn'°dONLNd¡
=
6
I
ö)8Unsigned 32-bit intege®†°dONLNd◊
=
ö
I
ù)d
r°dONLNd⁄
Mä
YΔ(
Vä
typeAEList°dONLNdÂ
M˛
Y
")t'list'°dONLNdÏ
M
6
Y
á)8List of descriptor r, °dONLNd
M
à
Y
ö)Recor†Ä°dONLNd
M
ö
Y
†)
dº@°dONLNd
M
†
Y
§)
s°dONLNd
]ä
i“(
fätypeAERecord°dONLNd
]˛
i
")t'reco'°dONLNd
]
6
i
u)8List of keyworF@°dONLNd*
]
v
i
õ)@d-specifi$°dONLNd3
]
ú
i
‹)&ed descriptor rˆ°dONLNdB
]
‹
i
Ó)@ecor]°dONLNdF
]
Ô
i
ı)
dx¿°dONLNdG
]
ı
i
˘)
s°dONLNdJ
mä
yfi(
vätypeAppleEvent°dONLNdY
m˛
y
")t'aevt'°dONLNd`
m
6
y
r)8Apple event r¿°dONLNdm
m
s
y
Ö)=ecorÑ °dONLNdq
m
Ö
y
ã)
d°dONLNdt
}ä
âfi(
ÜätypeEnumerated°dONLNdÉ
}˛
â
")t'enum'°dONLNdä
}
6
â
})8Enumerated dat
`°dONLNdò
}
~
â
É)H
a°dONLNdõ
çä
ô∫(
ñätypeType°dONLNd§
ç˛
ô
")t'type'°dONLNd´
ç
6
ô
J)8FourP¿°dONLNdØ
ç
K
ô
â)-character cod…@°dONLNdΩ
ç
â
ô
ê)>e °dONLNd¡
ùä
©¥(
¶ätypeFSS°dONLNd…
ù˛
©
)t'fss ~ °dONLNdŒ
ù

©
")
'°dONLNd–
ù
6
©
Ü)File system specifi¿°dONLNd„
ù
á
©
ú)Qcatio@°dONLNdË
ù
ú
©
°)
n°dONLNdÎ
≠ä
πÃ(
∂ätypeKeyword°dONLNd˜
≠˛
π
")t'keyw'°dONLNd˛
≠
6
π
ê)8Apple event keyworƒ °dONLNd
≠
ê
π
ñ)Z
d°dONLNd
Ωä
…∫(
ΔätypeNull°dONLNd
Ω˛
…
")t'null'°dONLNd#
Ω
6
…
h)8
Nonexisten
¿°dONLNd-
Ω
i
…
t)3t dˇ°dONLNd0
Ω
t
…
|)at+@°dONLNd2
Ω
}
…
ç)    a (h–Ä°dONLNd6
Ω
ç
…
•)andleo†°dONLNd;
Ω
¶
…
Ï) whose value is ò‡°dONLNdK
Ω
Ï
…
˛)FNILó¿°dONLNdN
Ω
˛
…
)
)

Lü4Mü

Mâü4LàMâò@@
˜@
˜MâçÄ¡¡?‰ˇfl?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡ò@@Ä
˜@Ä
˜çâÕÄ?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡?‰ˇÄ‡‰ˇÄ‡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡
p0‡»    ê I«
0Ä     ¿»
0‡  »
IG  »
âDB@»

ü‡¯yÄ»¡¡¡¡¡-˙
¿ÄIJ@
Ç@>
Ä
˝ÄÄ` Ï,    H    
˛Ä˛@Ç@
˝Ä˛Ä Î/+BÙlÅÄ';ï≈eëíŒuYÉóYltÖóV„ê-Ñw≈z÷≈»·˝≠ºÌ/+c,ëG@
XT∫äÇ*©j°E*(j¥•B*©
(VåöäçSJïB&»Ì/+Ö%ìÄ@ÁÖÇtI$)LüâLHL•+Çs»‚HîÖìâbS:A‚D»Ì/+
«"ÑÄ"Åπ•ïE“,*]~x_ÕnE#P˘á'ë4fl¢¿ti∞Ì/+
Ö≈°«g~I    :"64í9Õ‘PïIπƒ<Ò¬ ©•§ïc§IqÌ ˘ ÚÛàÌ ˘ ÚÛàÌ
¿˘ ÚÛpÌ¡¡(«`8 $
¿˛ @`@@¿ Ê'"X†   ˝ @@ Ê($bT¿ÒYiItMà    ≠≠£/E∞fi»ËüDÿ‰)HÇ:[wÊ($Rï@&¢¢˜©*§¶à‘◊&•RJ–IY*JhJw©Cä≠(Ê($åñ@$«$•2D…$à$îïd»îíêQ&KDíHí    %3Ñ…GÊ($Ö$@I‰G [_ÌIÑi!!…Έ’0$⁄*Œ^‘ò‘JZUaÊ($
≈¥‰iC≈1í%Hâë))iD§â"4ík$àêà3±ëœàÚNÊ˝˛Bı¯B·˝˛Bı¯B·
˘BÎB·ò@Ä¿
˜Ä¿
˜ÕâÄ¡¡ˇ @¿@#
„0◊R ˝    % @
$◊RGıóDÿyƒÅ%*Óu' –HW8r%ÿíÃ"*JhäJ›P*PpíÍ@•^ÄŸ§[¬LíHpúäIé)R‡@ùL9.‰ÄŸ
6p‰~‘ò R¬*vÄañ    hâÿ
§_DTàêÛŒá1åú4[q±dq∑vÿı˚Äÿı˚Äÿı˚Äÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡‡˛ćÕ@1˛Ä@Õ1JD@-e# ¿v0Œ3ΩJ@VƉïöPŒI)ú@î§≠9íÄŒäR–#©    9¢
&∞Œ
ùåéIF-§DŒ˛ Ã˛ Ã˛…¡¡ƒ;Ä8‡@÷HHÄ
@@÷IxàûMùlDÑÍ'Xê
QeÂn◊Rê±d¶©4§Öe©PrÑäJê◊ц¢e$ %%‰")+†ñxííé◊á∞íôI€MI<":B0&‹’◊
≈!…8ânHãÈËw*Q‚4ñÈâ◊¸D˛˛—¸D˛˛P—
¸8˙`œ¡¡ˇ  R      RGıó%Ç íÃ"*R §[¬Lí
 
6p‰~§ 
§_DTDL ¡¡¡¡¡¡¡ò@¿

˜¿

˜âMÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜MâçÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜çâÕÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ÕâÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜â?Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜MâçÄ
¡¡„3fl‰
fl Â
fl„ć‰
fl„ć Â
fl‰
fl Â
fl„ć‰
fl„ć ˛
è¯Ì
flÿ0
ålÌ
fl
 flˇ>˝√œÌfi‡Ô
fl
€˜õ˜„Ão˝∞Óć
fi˝õ∑loÄÔ
fl
ÛˇüΩÊo˘¸Óć ˛

∞Í
fl˝
0Í
fl Â
fl„ć

Áˇ
¿
fl
ˆÛ@ć
 ˆÛ
@
fl
ˆÛ
@
fl
 ˆÛ
@
fl
ˆÛ@ć
ˆÛ
@
fl
ˆÛ@ć 
¿˚˝

Ģ
@
fl
 ˝Ģ
@
fl 
&;w>«<d7„¢·6˙
@
fl
/d‘ôÉ2î`ìò˙@ć
(TôÇ≤Äîó‚îê˙
@
fl
«s◊Å‹t·ù€¸˙@ć
 ˝ê˛Ę
@
fl
˝
˛9¿˜
@
fl
 ˆÛ
@
fl
ˆÛ@ć
ˆÛ
@
fl
ˆÛ@ć

 Áˇ
¿
fl
ˆÛ
@
fl
 ˆÛ
@
fl
ˆÛ@ć
ˆÛ
@
fl
ˆÛ@ć
 ˆÛ
@
fl
¿˘˘`@
fl 
  ˙é¸
¿ (@
fl
&|Ä˚ëæÙFˆû#á(@ć
/>˙ïj„H
é$L@
fl
)2˙"ïk"HR'√@ć 
«Ä˚<}j˜àûè˘û@
fl
ˆ˚˙
@
fl
 ˆ˚8˙
@
fl
ˆÛ@ć
ˆÛ
@
fl
ˆÛ@ć
 ˆÛ
@
fl
ˆÛ
@
flò@@Ä
˜@Ä
˜çâÕÄ


 Áˇ
¿
fl
ÙÒć‰
fl„ć Â
fl‰
fl Â
fl„ć‰
fl„ć Â
fl‰
fl Â
fl‰Ãć‰Ufl¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡
p0‡»    ê I«
0Ä     ¿»
0‡  »
IG  »
âDB@»

ü‡¯yÄ»¡¡¡¡¡-˙
¿ÄIJ@
Ç@>
Ä
˝ÄÄ` Ï,    H    
˛Ä˛@Ç@
˝Ä˛Ä Î/+BÙlÅÄ';ï≈eëíŒuYÉóYltÖóV„ê-Ñw≈z÷≈»·˝≠ºÌ/+c,ëG@
XT∫äÇ*©j°E*(j¥•B*©
(VåöäçSJïB&»Ì/+Ö%ìÄ@ÁÖÇtI$)LüâLHL•+Çs»‚HîÖìâbS:A‚D»Ì/+
«"ÑÄ"Åπ•ïE“,*]~x_ÕnE#P˘á'ë4fl¢¿ti∞Ì/+
Ö≈°«g~I    :"64í9Õ‘PïIπƒ<Ò¬ ©•§ïc§IqÌ ˘ ÚÛàÌ ˘ ÚÛàÌ
¿˘ ÚÛpÌ¡¡(«`8 $
¿˛ @`@@¿ Ê'"X†   ˝ @@ Ê($bT¿ÒYiItMà    ≠≠£/E∞fi»ËüDÿ‰)HÇ:[wÊ($Rï@&¢¢˜©*§¶à‘◊&•RJ–IY*JhJw©Cä≠(Ê($åñ@$«$•2D…$à$îïd»îíêQ&KDíHí    %3Ñ…GÊ($Ö$@I‰G [_ÌIÑi!!…Έ’0$⁄*Œ^‘ò‘JZUaÊ($
≈¥‰iC≈1í%Hâë))iD§â"4ík$àêà3±ëœàÚNÊ˝˛Bı¯B·˝˛Bı¯B·
˘BÎB·ò@Ä¿
˜Ä¿
˜ÕâÄ
¡¡ˇ @¿@#
„0◊R ˝    % @
$◊RGıóDÿyƒÅ%*Óu' –HW8r%ÿíÃ"*JhäJ›P*PpíÍ@•^ÄŸ§[¬LíHpúäIé)R‡@ùL9.‰ÄŸ
6p‰~‘ò R¬*vÄañ    hâÿ
§_DTàêÛŒá1åú4[q±dq∑vÿı˚Äÿı˚Äÿı˚Äÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡‡˛ćÕ@1˛Ä@Õ1JD@-e# ¿v0Œ3ΩJ@VƉïöPŒI)ú@î§≠9íÄŒäR–#©    9¢
&∞Œ
ùåéIF-§DŒ˛ Ã˛ Ã˛…¡¡ƒ;Ä8‡@÷HHÄ
@@÷IxàûMùlDÑÍ'Xê
QeÂn◊Rê±d¶©4§Öe©PrÑäJê◊ц¢e$ %%‰")+†ñxííé◊á∞íôI€MI<":B0&‹’◊
≈!…8ânHãÈËw*Q‚4ñÈâ◊¸D˛˛—¸D˛˛P—
¸8˙`œ¡¡ˇ  R      RGıó%Ç íÃ"*R §[¬Lí
 
6p‰~§ 
§_DTDL ¡¡¡¡¡¡¡ò@¿

˜¿

˜âMÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜MâçÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜çâÕÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜ÕâÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜â?Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜?âÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜âøÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜øâˇÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜ˇâ?Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜?âÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜âøÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜øâˇÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜ˇâ1Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜?âÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜âøÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜øâˇÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜ˇâ?Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜?âÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜âøÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜øâˇÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜ˇâ1Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ?‚@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-14    )BAbout ‡)Apple Events4^*¿
¯
°dONLNd\lhÑ(elFigurR¿°dONLNd\Ñhò)e 3-6@°dONLNd
\òh
z)6 illustrates the logical arrangement of a descriptor r‡@°dONLNd@\
zh
å)‚ecorT†°dONLNdD\
çh
„)d with a descriptor °dONLNdXiluç(rltype of ,
Courierʆ°dONLNd`içuΩ)!typeType„†°dONLNdhiΩu¸)0, which specifi$ °dONLNdwi˝u
;)@es that the dat<`°dONLNdÜi
;u
H)>a hç¿°dONLNdâi
Hu
g)andle rq‡°dONLNdêi
gu
w)eferK†°dONLNdîi
xu
é)s to a@Ä°dONLNdöi
èu
§) fourV°dONLNdüi
§u
‚)-character codŒÄ°dONLNd≠i
‚u
È)>e °dONLNdØvlÇr(l(iº@°dONLNd±vrÇö)
n this cast°dONLNdªvõÇ•))e t°dONLNdæv¶Ç⁄)he constant Â@°dONLNd v⁄Ç
4)4kCoreEventClassfl†°dONLNdŸv
4Ç
|)Z, whose value is à‡°dONLNdÍv
}Ç
°)I'aevt'܆°dONLNdv
°Ç
µ)$). ThÆ°dONLNdıv
µÇ
Ó)is descriptor °dONLNd
Élèo(ål
rE°dONLNd
ÉpèÇ)ecorπ`°dONLNd
ÉÇèŸ)d can be used in an æ@°dONLNd
ÉŸè
m)W"Apple event attribute that identifi∞@°dONLNd
?É
nè
µ)ïes the event clas˜ °dONLNd
PÉ
µè
ø)Gs f°dONLNd
SÉ
¿è
fi)or any °dONLNd
Zêlúü(ôl
Apple evenà`°dONLNd
dêüú–)3t in the Cor3`°dONLNd
pê—úÚ)2    e suite. 

æ*œ
¯4ø*œ
¯"ø*]

ˇ·ˇ‚7^
    °dONLNd
z¥løñ(ºl
Figure 3-6°dONLNd
Ö¥Æø¥)B
A0°dONLNd
Ü¥¥øÙ) descriptor recor
Ä°dONLNd
ó¥ıø
s)Ad whose data handle refers to e†°dONLNd
∂¥
sø
Ø)~vent class data
°dONLNd
«
=l
Ià(
FlEvery Ø°dONLNd
Õ
=à
I
) Apple event includes an attribut∑‡°dONLNd
Ì
=

I
Q)èe specifying tQ °dONLNd
˚
=
R
I
t);he addrh†°dONLNd
=
t
I
´)"ess of the tar⁄`°dONLNd
=
´
I
Ò)7get application. °dONLNd!
Jl
Vs(
Sl
A∫†°dONLNd"
Js
V©) descriptor rô‡°dONLNd/
J©
Vª)6ecor@°dONLNd3
Jº
V
])%d that contains an application’s addry`°dONLNdX
J
]
V
†)°ess is called an 
⁄ °dONLNdi
J
†
V
¬)Caddress’¿°dONLNdp
J
√
V
≈)#
 
U¿°dONLNdq
J
Δ
V
Ù)
descriptork‡°dONLNd{
J
Ù
V
ˆ).
 
°dONLNd|
Wl
cã(
`lrecord.°dONLNdÑ
nl
zÑ*TYPE°dONLNdä
nê
z
)$AEAddressDesc = AEDesc;°dONLNd´
n
D
z
Ê)¥{address descriptor record}°dONLNd«
Ül
íî(
èlThe addr∏@°dONLNdœ
Üî
í—)(ess in an addrÄ°dONLNd›
Ü“
í
)>ess descriptor r&`°dONLNdÌ
Ü

í
')Cecorö¿°dONLNdÒ
Ü
'
í
j)d can be specifi7Ä°dONLNd

Ü
k
í
})Ded aú‡°dONLNd
Ü
}
í
Ë)s one of these four basic °dONLNd
ìl
ü
8(
úl.types (or as any other descriptor type you defiƆ°dONLNdN
ì
8
ü
ä)Ãne that can be coerß°dONLNda
ì
ä
ü
ƒ)Rced to one of °dONLNdo
†l
¨Ç(
©lthesed°dONLNdt
†É
¨Ö)
 ‰°dONLNdu
†Ö
¨¢)types):°dONLNd\l˙(l"Like several of the other data str÷¿°dONLNd~˙
)éuctur\†°dONLNdÉ

.)es defi’`°dONLNdä
.
_)ned by the °‡°dONLNdï
_
Ô)1Apple Event Manager for use in °dONLNd¥l(‰(%lApple event attributes and °dONLNdœÂ(
w)yApple event parameters, an addr˜†°dONLNdÓ
v(
π)ëess descriptor rÄ°dONLNd˛
∫(
Ã)Decor釰dONLNd
Ã(
fi)d is °dONLNd)l5⁄(2lidentical to a descriptor r9†°dONLNd")€5Ì)oecorÆ°dONLNd&)Ì5
,)d of data type éÄ°dONLNd5)
-5
Q)@AEDescå@°dONLNd;)
Q5
à)$; the only difR`°dONLNdI)
â5
ï)8fer4‡°dONLNdL)
ï5
Ô)ence is that the data °dONLNdb6lBù(?lfor an addr    ‡°dONLNdm6ûB·)2ess descriptor r,¿°dONLNd}6·BÛ)Cecor° °dONLNdÅ6ÛB
ø).d must always consist of an application’s addrQ °dONLNdØ6
¿B
“)Õess. î¿°dONLNd¥6
“B
‘)
 ¿°dONLNdµ6
’B
◊)
 
    °dONLNd}
πl
ĭ(
¡lDescriptor type°dONLNdç
π


ƒ
)û
V¸/°dONLNdé
π

ƒ
!)alue°dONLNdì
π
B
ƒ
s)3Description
°dONLNd†
«l
”“(
–ltypeApplSignature°dONLNd≤
«


”
.)û'sign'°dONLNdπ
«
B
”
ù)8Application signaturÄ°dONLNdÕ
«
û
”
¢)\
e°dONLNd–
◊l
„∫(
‡ltypeSessionID°dONLNdfi
◊


„
.)û'ssid'°dONLNdÂ
◊
B
„
i)8    Session rw†°dONLNdÓ
◊
i
„
y)'efer#¿°dONLNdÚ
◊
z
„
≥)ence number°dONLNdˇ
Ál
Û¥(
ltypeTargetID°dONLNd
Á


Û
.)û'targ'°dONLNd
Á
B
Û
H)8
Tµ¿°dONLNd
Á
G
Û
O)arz¿°dONLNd
Á
P
Û
q)    get ID rˆ†°dONLNd
Á
q
Û
É)!ecork°dONLNd"
Á
Ñ
Û
ä)
d°dONLNd%
˜lˆ(ltypeProcessSerialNumber°dONLNd=
˜


.)û'psn '°dONLNdD
˜
B
K)8PrN†°dONLNdF
˜
L
¢)
ocess serial number

Œl
&
¯4œl
%
¯4ÕkŒlò@@
˜@
˜Œl
c¡¡?Êˇ˛fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fiò@@Ä
˜@Ä
˜
l
Nc?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi?¡fi¡fi¡¡¡¡¡¡¡¡¡¡
G¡¿cÄ»    B@Äî«    ¬Å«
√ÄÅÄ»

$9Ä»    $A)«    É‡Δ«¡¡¡¡¡)Ë˝

¯˛@8
ÇË)
 $˝

P˛@ÇË+'
—≤0úÓWñFK9’dr\Qe±“][é@∫[‡—{Éó(È+'
å≤E0)aRÍ*™§PU™Ö®°™“°J≠ARƒ*PÈ+'ñN›HKûLJ    —$ê•2~%1!2îÆ    œ#â#ì…Ç$ªâLêÈ+'à"àZÊñTH∞©t-˘·5∏@çB¬˜àã~È+'á
úm˘$d$Ëàÿ“HÁ7QBU&ÁÛ«Å»ÚÅ%w‘†ÈĢÄÚfiĢÄÚPfi¯ÄÚ fi¡¡'¡Ä‡Ätê˝Ä    p 
Ä    
pÄÊ'âbÄ@Ä ÄÄ˝  Ä
     ÄÊ($
âSw≈e•$e—6 &∂¥våΩ¿;{#¢}cê•"Èm‹Ê($
JUöäãfi§™íö SS\öïI+@M$Ud©)°(fi•*¥†Ê($2Yìíî…$í íRUì"RJ@IDô-I"H$îŒO%Ê($ë
'ë)mµ&§Ñá'Ø€T¿ìh´9{RcPE)hTMÑÊ($”ë•ΔHï"$D§••í$à“HM¨í"B ŒΔG>#…8Ê˝ 
ı˘

·˝ 
ı˘

·ò@Ä¿
˜Ä¿
˜
Nl
éc˙

Ï

·¡¡¸Ä     c
å0¿◊
HÄ˝$îÅ»@◊
I÷]aÁî´π‘úÉDâ\·»îÿK0à©)¢)(wu@T©A«©ïzÿëo    2I!¬p)&8•KÅ    !0‰ªíÿŸ√ë˚R`d@#)K©⁄
âBX%¢$ÿë}R"Cœ:Δ2p—mΔΔyëΔ›ÿÿı@¸˛ ÿı@¸˛ ÿı@¸˛ ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡@Ä8ÄÕ
@
ƒ
Ã≈)µîè+
ÿ¿ŒŒı)
ZªíTi@Œ
$¶qRí¥‰JÕ)K@é§$Êàö¿Œv28q%¥xFëŒ@˛ ÄÃ@˛ ÄÃ@˛ …¡¡¿C¿4Ó‡Ä
’
 A 
D@)
’
%‚"y6u±®Dùb@)E˝óï∏◊
JB≈íö§“íPyñ•@I )*@◊Çâîì(îî#êà§ÆÄRY‚JJ8◊¬Je'm5$pàÈ¿õpt{T◊á$‚%π"/ß°‹©Gà“[§R$p◊˝

˛@˛ —˝

˛@
@—¸‡˚

Äœ¡¡¸Ä0 
HÄH$ 
I÷\ñD K0à©H8D ëo    2HD Ÿ√ë˙êDH ë}Q90 ¡¡¡¡¡¡ò@¿

˜¿

˜
él
Œc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜
Œlc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜lNc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜Nléc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜él¿c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜Œl
c
¡¡Â32fiÂ
fi Êfi¡Â
fi¡ ÊfiÂ
fi Êfi¡Â
fi¡ ˛
è¯Ófiÿ0
ålÓ
fi
 flˇ>˝√œÌfi‡fi
€˜õ˜„Ão˝∞Ã
fi˝õ∑loÄ
fi
ÛˇüΩÊo˘¸à ˛

∞Îfi˝
0Î
fi Êfi¡

ˡ
¿
fi
ˆÙ@›
 ˆÙ
@fi
ˆÙ
@
fi
 ˆÙ
@fi
ˆÙ@›
ˆÙ
@
fi
ˆÙ@› 
¿˚Ù
@fi
 ˝
˘
@
fi 
&;w>«<d€Ò’oŒ˚
@fi
/d‘ôÉ2

J$)1˚@›
(TôÇ≤Ä
*K‰)?˚
@
fi
«s◊Å‹tƒpŒΔ˚@›
 ˝ê˛@˙
@fi
˝
˛‡sÄ˚
@
fi
 ˆÙ
@fi
ˆÙ@›
ˆÙ
@
fi
ˆÙ@›

 ˡ
¿fi
ˆÙ
@
fi
 ˆÙ
@fi
ˆÙ@›
ˆÙ
@
fi
¿˘ ˙@› 
  ˙Ä  ˙
@fi
&|Ä˚Ñ∑q¶w˚
@
fi 
/>˙Ú¸¢oÃ˚
@fi
)2˙ÉD¢)3˚@›
«Ä˚Ú<ëÁÓ˚
@
fi
ˆÙ@›
 ˆÙ
@fi
ˆ@¯@
fi
 ˆp˚
Ä@fi
ˆêx¿xÄ@›
ˆñã∂r[wûàÑ8Ë@
fi
ˆòÑXã
äHÄéaà@›
 ˆîåP˙J˙Iàíh@fi
ˆ∂sº7ƒ7fsÔÛ»@
fiò@@Ä
˜@Ä
˜
l
Nc

 ˆ@¯@fi
ˆ@¯
@›
ˆÙ
@
fi
ˆÙ@›
 ˆÙ
@fi
ˆÙ
@
fi

 ˡ
¿fiÙœÂ
fi¡ ÊfiÂ
fi Êfi¡Â
fi¡ ÊfiÂ
fi ÊfiÂÃfiÂUfi¡¡¡¡¡¡¡¡¡¡
G¡¿cÄ»    B@Äî«    ¬Å«
√ÄÅÄ»

$9Ä»    $A)«    É‡Δ«¡¡¡¡¡)Ë˝

¯˛@8
ÇË)
 $˝

P˛@ÇË+'
—≤0úÓWñFK9’dr\Qe±“][é@∫[‡—{Éó(È+'
å≤E0)aRÍ*™§PU™Ö®°™“°J≠ARƒ*PÈ+'ñN›HKûLJ    —$ê•2~%1!2îÆ    œ#â#ì…Ç$ªâLêÈ+'à"àZÊñTH∞©t-˘·5∏@çB¬˜àã~È+'á
úm˘$d$Ëàÿ“HÁ7QBU&ÁÛ«Å»ÚÅ%w‘†ÈĢÄÚfiĢÄÚPfi¯ÄÚ fi¡¡'¡Ä‡Ätê˝Ä    p 
Ä    
pÄÊ'âbÄ@Ä ÄÄ˝  Ä
     ÄÊ($
âSw≈e•$e—6 &∂¥våΩ¿;{#¢}cê•"Èm‹Ê($
JUöäãfi§™íö SS\öïI+@M$Ud©)°(fi•*¥†Ê($2Yìíî…$í íRUì"RJ@IDô-I"H$îŒO%Ê($ë
'ë)mµ&§Ñá'Ø€T¿ìh´9{RcPE)hTMÑÊ($”ë•ΔHï"$D§••í$à“HM¨í"B ŒΔG>#…8Ê˝ 
ı˘

·˝ 
ı˘

·ò@Ä¿
˜Ä¿
˜
Nl
éc
˙

Ï

·¡¡¸Ä     c
å0¿◊
HÄ˝$îÅ»@◊
I÷]aÁî´π‘úÉDâ\·»îÿK0à©)¢)(wu@T©A«©ïzÿëo    2I!¬p)&8•KÅ    !0‰ªíÿŸ√ë˚R`d@#)K©⁄
âBX%¢$ÿë}R"Cœ:Δ2p—mΔΔyëΔ›ÿÿı@¸˛ ÿı@¸˛ ÿı@¸˛ ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡@Ä8ÄÕ
@
ƒ
Ã≈)µîè+
ÿ¿ŒŒı)
ZªíTi@Œ
$¶qRí¥‰JÕ)K@é§$Êàö¿Œv28q%¥xFëŒ@˛ ÄÃ@˛ ÄÃ@˛ …¡¡¿C¿4Ó‡Ä
’
 A 
D@)
’
%‚"y6u±®Dùb@)E˝óï∏◊
JB≈íö§“íPyñ•@I )*@◊Çâîì(îî#êà§ÆÄRY‚JJ8◊¬Je'm5$pàÈ¿õpt{T◊á$‚%π"/ß°‹©Gà“[§R$p◊˝

˛@˛ —˝

˛@
@—¸‡˚

Äœ¡¡¸Ä0 
HÄH$ 
I÷\ñD K0à©H8D ëo    2HD Ÿ√ë˙êDH ë}Q90 ¡¡¡¡¡¡ò@¿

˜¿

˜
él
Œc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜
Œlc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜lNc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜Nléc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜él¿c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜¿lc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜l@c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜@lÄc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜Äl¿c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜¿lc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜l@c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜@lÄc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜Äl≤c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜¿lc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜l@c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜@lÄc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜Äl¿c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜¿lc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜l@c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜@lÄc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜Äl≤c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ<J@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äAbout ‡)Apple Events

, (‡3-15
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

jHp4jHp käk

ˇ·ˇ‚7^°dONLNd\äj‡(fäKeyword-Specifi,¿°dONLNd\·j
X)Wed Descriptor Recordsˇˇˇˇˇˇ‘@(f
3
°dONLNd&pä|≥(yä
After the ¿°dONLNd0p¥|
À)*<Apple Event Manager has assembled the necessary descriptor r–@°dONLNdlp
À|
›(y
ÀecorD†°dONLNdpp
fi|)
ds as the °dONLNdz}äâ
(Üä attributes and parameters of an /°dONLNdö}
â
ˆ)ç1Apple event, your application cannot examine the °dONLNdÀääñÕ(ìäcontents of the \@°dONLNd€äÕñ
)CApple event dir °dONLNdÍä
ñ
&)Eectly» °dONLNdÔä
&ñ
ø)#. Instead, your application must us0†°dONLNd
ä
¿ñ
«)öe ‡°dONLNd
ä
«ñ
Œ)
A„ °dONLNd
ä
Œñ)pple Event °dONLNd
 óä£∏(†ä    Manager rW°dONLNd
)ó∏£Í).outines to rS@°dONLNd
5óÍ£
∫)2-equest each attribute and parameter by keywor °dONLNd
bó
ª£
Δ)—d. 
5‡°dONLNd
eó
Δ£
Ù)Keywordsfi‡°dONLNd
mó
Ù£
ˇ). ar#‡°dONLNd
pó£)e °dONLNd
r§ä∞
(≠äarbitrary names used by the ц°dONLNd
é§
∞)~8Apple Event Manager to keep track of various descriptor °dONLNd
Δ±äΩç(∫ä
rE°dONLNd
«±éΩ†)ecorπ`°dONLNd
À±†Ω¬)ds. The ,
CourierM‡°dONLNd
”±√Ω˘)#    AEKeywordJÄ°dONLNd
‹±˘Ω
B)6 data type is defi]`°dONLNd
Ó±
BΩ
{)Ined as a fourf†°dONLNd
˚±
{Ω
¿)9-character code.°dONLNd»ä‘¢(—äTYPE°dONLNd»Æ‘
í)$&AEKeyword = PACKED ARRAY[1..4] OF Charq¿°dONLNd8»
í‘
û)‰; q°dONLNdG»
û‘
˛){keyword for a }°dONLNdg÷
ò‚
∞(fl
ò { d~Ä°dONLNdk÷
∞‚
Ï)
escriptor z¿°dONLNdu÷
Ï‚)<record}°dONLNd}Óä˙¡(˜äConstants arÛ°dONLNdâÓ¡˙
9)7e typically used for keywor߆°dONLNd§Ó
:˙
Z)yds. Her‡`°dONLNd´Ó
Z˙
ø) e is a list of the keywor?†°dONLNdƒÓ
¿˙)fd constants for °dONLNd‘˚ä
Ô(
äApple event attributes:@°dONLNdˇˇ)f
 °dONLNdD^äjõ(gäHer`°dONLNdG^õj
)e is a list of the keyworø@°dONLNd`^
j
ç)ed constants for commonly used µÄ°dONLNd~^
çj
˙)çApple event parameters:
    °dONLNdÏ
ä
÷(
äAttribute keywordw¿°dONLNd˛

"

()ò
VÛÔ°dONLNdˇ

'

9)alueuÄ°dONLNd

Z

ã)3Description
°dONLNd
"ä
.‰(
+äkeyAddressAttr w¿°dONLNd!
"
"
.
F)ò'addr'uÄ°dONLNd(
"
Z
.
q)8Addr9@°dONLNd,
"
r
.
ô)
ess of tarM†°dONLNd6
"
ô
.
£)'ge¶`°dONLNd8
"
£
.)
t or client application
¶ °dONLNdO
"

.)^
 & °dONLNdP
"
.)
 °dONLNdS
2ä
>ˆ(
;äkeyEventClassAttr w¿°dONLNdf
2
"
>
F)ò'evcl'uÄ°dONLNdm
2
Z
>
ò)8Event class of “Ä°dONLNd|
2
ò
>
Œ)>Apple event@°dONLNdá
2
œ
>
—)7
 °dONLNdä
Bä
Nfi(
KäkeyEventIDAttrw¿°dONLNdô
B
"
N
F)ò'evid'uÄ°dONLNd†
B
Z
N
è)8Event ID of †°dONLNd¨
B
è
N
≈)5Apple eventf`°dONLNd∑
B
≈
N
«)6
 °dONLNd∫
Rä
^ˆ(
[äkeyEventSourceAttrw¿°dONLNdÕ
R
"
^
F)ò'esrc'uÄ°dONLNd‘
R
Z
^
t)8Natur“‡°dONLNdŸ
R
t
^
™)e of the sourA‡°dONLNdÊ
R
´
^
Ë)7ce application°dONLNdˆ
bä
n
(
käkeyInteractLevelAttrw¿°dONLNd
b
"
n
F)ò'inte'uÄ°dONLNd
b
Z
n
»)8Settings for allowing the ™†°dONLNd,
b
»
n)nApple Event uÄ°dONLNd8
m
Z
y(
v
Z)Manager to bring a server application to uÄ°dONLNda
x
Z
Ñ
w*the fora@°dONLNdh
x
w
Ñ
Ö)egr°dONLNdk
x
Ö
Ñ
ñ)ounÕ°dONLNdn
x
ñ
Ñ
‘)d, if necessaryY‡°dONLNd}
x
‘
Ñ)>, to interact uÄ°dONLNdã
É
Z
è
î(
å
Zwith the user¶`°dONLNdò
É
î
è
ñ):
 °dONLNdõ
ìä
ü
(
úäkeyMissedKeywordAttrw¿°dONLNd∞
ì
"
ü
F)ò'miss'uÄ°dONLNd∑
ì
Z
ü
})8Keywor°‡°dONLNdΩ
ì
}
ü
ö)#d for fiÜ`°dONLNd≈
ì
õ
ü
¨)rst r=`°dONLNd 
ì
≠
ü
ƒ)equirT†°dONLNdœ
ì
ƒ
ü
)ed parameter uÄ°dONLNd‹
û
Z
™
](
ß
Z
r:Ä°dONLNd›
û
^
™
¢)emaining in an áÄ°dONLNdÏ
û
¢
™
ÿ)DApple event“@°dONLNd˜
û
ÿ
™
⁄)6
 °dONLNd˙
Æä
∫
(
∑äkeyOptionalKeywordAttrw¿°dONLNd
Æ
"
∫
F)ò'optk'uÄ°dONLNd
Æ
Z
∫
ô)8List of keywor;¿°dONLNd&
Æ
ö
∫)@ds for parameters of the uÄ°dONLNd?
π
Z
≈
€(
¬
ZApple event that should be tr˛ °dONLNd\
π
€
≈
)Å    eated as uÄ°dONLNde
ƒ
Z
–
´(
Õ
Zoptional by the tar¬†°dONLNdx
ƒ
´
–
Ï)Qget application°dONLNdâ
‘ä
‡
(
›äkeyOriginalAddressAttrw¿°dONLNd†
‘
"
‡
F)ò'from'uÄ°dONLNdß
‘
Z
‡
q)8Addr9@°dONLNd´
‘
r
‡
≈)ess of original sourΔ†°dONLNdø
‘
≈
‡
‹)Sce of kÄ°dONLNd≈
‘
‹
‡)
Apple evens‡°dONLNdœ
‘
‡)3t uÄ°dONLNd—
fl
Z
Î
‘(
Ë
Zif the event has been forwar/°dONLNdÌ
fl
’
Î){ded (available uÄ°dONLNd¸
Í
Z
ˆ
ı(
Û
Z%only in version 1.01 or later versionZ@°dONLNd!
Í
ˆ
ˆ)ús of‡†°dONLNd%
Í
ˆ)
 uÄ°dONLNd&
ı
Z

j(
˛
Zthe tÄ°dONLNd*
ı
j

—)Apple Event Manager) ˜@°dONLNd?
ı
—

”)g
 °dONLNdBäÍ(äkeyReturnIDAttr w¿°dONLNdS
"
F)ò'rtid'uÄ°dONLNdZ
Z
õ)8Return ID for r`°dONLNdi
ú
±)Beply |@°dONLNdn
±
È)Apple event °dONLNd|ä!fi(äkeyTimeoutAttrw¿°dONLNdã
"!
F)ò'timo'uÄ°dONLNdí
Z!
ö)8Length of time`‡°dONLNd†
õ!
ù)A
,‡‡°dONLNd°
ù!
µ) in tic5†°dONLNd®
∂!
»)ks, tD °dONLNd≠
»!)hat the client uÄ°dONLNdº 
Z,
û()
Zwill wait for a rà`°dONLNdÕ 
û,
À)Deply or a rx¿°dONLNdÿ 
À,
È)-esult frJ °dONLNd‡ 
Í,)om the uÄ°dONLNdÁ+
Z7
u(4
Zserver—@°dONLNdÌ+
u7
w)
 °dONLNd;äG
(DäkeyTransactionIDAttrw¿°dONLNd;
"G
F)ò'tran'uÄ°dONLNd;
ZG
`)8
T∞@°dONLNd;
_G
˛)&ransaction ID identifying a series of uÄ°dONLNd3F
ZR
î(O
ZApple events˝@°dONLNd?F
îR
ñ):
 
    °dONLNdñwäÇ›(äParameter keywordz`°dONLNd®w¯Dz)n
Vˆè°dONLNd©w˝Ç
)aluex °dONLNdÆw
0Ç
a)3Description
°dONLNdªÖäë‰(éäkeyDirectObjectz`°dONLNdÀÖ¯ë
)n'----'x °dONLNd“Ö
0ë
>)8Dir‚¿°dONLNd’Ö
>ë
z)ect parameterp°dONLNd‚Ö
{ë
})=
 °dONLNdÂïä°fi(ûäkeyErrorNumberz`°dONLNdÙﯰ
)n'errn'x °dONLNd˚ï
0°
>)8ErrKÄ°dONLNd˛ï
>°
ú)or number parameter°dONLNd•ä±fi(ÆäkeyErrorStringz`°dONLNd"•¯±
)n'errs'x °dONLNd)•
0±
>)8ErrKÄ°dONLNd,•
>±
ì)or string parameterˇF§@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-16    )BAbout ‡)Apple Events4^*¿
¯
°dONLNd\lh(elThe ª¿°dONLNd\h
)%Apple Event Registry: Standard Suites©Ä°dONLNd)\
h
/)ù defi†°dONLNd.\
0h
í)nes additional keyworʇ°dONLNdC\
íh
’)bd constants for °dONLNdSiluá(rlApple˝Ä°dONLNdXiáuâ)
 }Ä°dONLNdYiäu
V)-event parameters that can be used with specifiÏÄ°dONLNdái
Vu
\)Ãc ~`°dONLNdâi
]u
ú)Apple events. °dONLNdò{lá(ÑlThe ]`°dONLNdú{á
2)%Apple Event Manager associates keywor¿°dONLNd¡{
3á
s)¥ds with specifi0¿°dONLNd–{
sá
≠)@c descriptor rÄ@°dONLNdfi{
≠á
ø):ecorÙ†°dONLNd‚{
øá
Ÿ)ds by °dONLNdËàlîù(ëlmeans of a 
u`°dONLNdÛàûîÁ)2keyword-specifi¬`°dONLNd
àÁî
B)Ied descriptor record÷†°dONLNd
à
Bî
D)[
,V†°dONLNd
à
Eî
L) a÷†°dONLNd
à
Lî
o)     data strí¿°dONLNd
"à
pî
á)$uctur†°dONLNd
'à
àî
∞)
e of type ,
Courier»‡°dONLNd
1à
∞î
Ê)(    AEKeyDesc≈Ä°dONLNd
:à
Êî
Ë)6
 °dONLNd
;ïl°Ÿ(ûlthat consists of a keywor±¿°dONLNd
T
0)md and a descriptor rô‡°dONLNd
hï
0°
B)Wecor@°dONLNd
lï
C°
N)d. °dONLNd
p¨l∏Ñ(µlTYPE°dONLNd
v¨ê∏ÿ)$AEKeyDesc = {Ä°dONLNd
ɨÿ∏
∞)H${keyword-specified descriptor recordn°dONLNd
ߨ
∞∏
∂)ÿ
}°dONLNd
©∫lΔê(√lRECORD°dONLNd
±»~‘Æ+descKey:°dONLNd
æ»ÿ‘
)Z
AEKeyword;°dONLNd
Õ»
2‘
h)Z    {keyword}°dONLNd
ÿ÷~‚Δ(fl~descContent:°dONLNd
È÷ÿ‚
)ZAEDesc;°dONLNd
ı÷
2‚
§)Z{descriptor record}°dONLNd    ‰lÑ(ÌlEND;°dONLNd¸l
Ñ*FigurR¿°dONLNd¸Ñ
ò)e 3-7@°dONLNd¸ò
Ò) illustrates a keyword‡°dONLNd-¸Ú

)Zd-specifiB†°dONLNd6¸


X)&ed descriptor r@°dONLNdE¸
Y

k)Aecor{†°dONLNdI¸
k

º)d with the keywor¡@°dONLNdZ¸
º

ƒ)Qd °dONLNd\
    l
“(
lkeyEventClassAttry†°dONLNdm
    “

)f—the keyworP`°dONLNdx
    


G)<d that identif∞Ä°dONLNdÜ
    
G

÷)9#ies an event class attribute. The fÎ`°dONLNd©
    
÷

Ë)èigur/°dONLNd≠
    
È

)e °dONLNdØ
l
"
€(
lRshows the logical arrangement of the event class attribute for the Open Documents °dONLNd

#l
/Ü*event M@°dONLNd
#á
/≤)    shown in ≥@°dONLNd
#≤
/ )+FigurÜ°dONLNd
# 
/
)e 3-3 on page E@°dONLNd#
#

/
)=3-ô °dONLNd%
#

/
)10ô °dONLNd'
#

/
d)
. The descriptor r4 °dONLNd9
#
e
/
w)Lecor®Ä°dONLNd=
#
w
/
ä)d in ~°dONLNdB
#
ã
/
£)FigurP¿°dONLNdG
#
£
/
∑)e 3-7Ó@°dONLNdL
#
∑
/
ˆ) is identical to °dONLNd]
0l
<u(
9lthì¿°dONLNd_
0u
<á)    e on$@°dONLNdc
0à
<í)e iV@°dONLNdf
0í
<ö)
n ߆°dONLNdh
0ö
<≤)Figurz`°dONLNdm
0≤
<Δ)e 3-6‡°dONLNdr
0«
<
(); its descriptor type is \Ä°dONLNdã
0
(
<
X)atypeTypeYÄ°dONLNdì
0
X
<
Ì)0#, and the data to which its handle °dONLNd∂
=l
Io(
Fl
rE°dONLNd∑
=p
Iä)efers iƒ °dONLNdæ
=ä
I¶)dentifi≤`°dONLNd≈
=ß
I
)es the event class as s@°dONLNd€
=


I
[)ZkCoreEventClassm†°dONLNdÍ
=
[
I
`)Z. 
    °dONLNdÌ
al
lñ(
il
Figure 3-7°dONLNd¯
aÆ
l¥)B
A0°dONLNd˘
a¥
lÙ) keyword-specifiÇ`°dONLNd    
aÙ
l
À)@9ed descriptor record for the event class attribute of an 


u*
Ü
¯4
v*
Ü
¯

ˇ·ˇ‚7^°dONLNdB
kÆ
vƒ(
sÆOpenÇê°dONLNdF
kƒ
vΔ)
 ∞°dONLNdG
k«
v
)Documents eveÖ–°dONLNdT
k

v
)>nt

,*3
¯4,*2
¯ -l-
¯

ˇ·ˇ‚7^°dONLNdXl,æ((lDescriptor Listsˇˇˇˇˇˇ‘@((
Ò
3
°dONLNdj2l>‘(;lWhen extracting data fr °dONLNdÅ2’>Û)iom an ¬†°dONLNdá2Ú>
R)Apple event, you use »Ä°dONLNdú2
R>
Â)`Apple Event Manager functions t°dONLNdª2
Ê>
Ì)îo °dONLNdΩ?lKä(Hlcopy dí¿°dONLNd√?äKí)at’ °dONLNd≈?íK©)a to aç°dONLNdÀ?™Kª) buf¬°dONLNdœ?ªKÂ)
fer specifi¿@°dONLNd⁄?ÊK
()+ed by a pointerØ°dONLNdÈ?
(K
H)B    , or to rî°dONLNdÚ?
HK
Z) eturô¿°dONLNdˆ?
ZK
o)n a d܇°dONLNd˚?
pK
ù)escriptor r `°dONLNd?
ùK
Ø)-ecor>¿°dONLNd
?
∞K
Ì)d whose data °dONLNdLlXê(Ulhandle r5Ä°dONLNdLëX
)%efers to a copy of the data,°dONLNd;L
X
")t or to re°dONLNdCL
"X
è)eturn lists of descriptor rq‡°dONLNd^L
èX
°)mecorÊ@°dONLNdbL
°X
Õ)ds (called °dONLNdmYle≠(bldescriptor listsß`°dONLNd}Y≠e≤)A).
{@°dONLNdY≥eµ)
 


k*
rß4
l*
rß"
m*]


Öl
¯4
Ül
¯


ál
¯4
Ük
álò@@
˜@
˜
ál
«c¡¡?ŸˇÄÎ?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Îò@@Ä
˜@Ä
˜
«lc?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿Î?Ÿˇ¿ÎŸˇ¿Î¡¡¡ò@Ä¿
˜Ä¿
˜lGc¡¡¡¡¡¡¡¡¡¡¡¡¡
>»
     »
@»
ê»
    !–ÒË»
"à»
3¸>p»¡¡¡¡¡    Ä¿˛    G
ÅÄ@@ÿ        
 ˛    ÄÄ@ÿûã˛ 
IÍK8Í#]#Éìµ ‚∞Ÿ•îP‡@π*§QUIU,R]E@Ÿ$¥‡@ S$êÈËäÈ    sÇââ@Ÿ!òËÅÄ"UH∞2ã”ã@¥“ ÄŸ18∏p‡ÄgÍhàŸÃtí}çøDåÑÄŸ˛D˚˛˝◊˛D˚˛P˝◊˛8˚˛ ˝◊¡¡#¸aÄ    ˛ÄÅ@Ä¿˛˛Ä‰#¸"    ˛
Ä@ @ ˛˛Ä‰&"-,Á+dKn∏_ÌQAp[*-Ç"4uñ›¡tÌ¿‰&"™ëBT    ™)U§,@§ëk(¢†≠=VÑ%\ö´Jïtĉ%!DíBî<ry("Kπ)Iqƒ°))‰Ñ)ÖíÚQ«'•„&"$]"ƒ®pB¢l/xâÌ£QŸAÛ“âÑJ∑$DÿD*Mĉ%!#¢#dHN9HWqI"ap‚ARyÑE•<ìÉë…„¸Û@Ÿ¸Ù
@Ÿ¸ÛÄŸ¡¡(˙@Äp˛ààÄįÊ&S
à¸ÄÄÄ
HÊ)%RònVZRF^ãb
kk#de…6flZ»∂9
Ö) GK|‡Á($
b®    §®ΩÍJ§ï¢µ5e§™äöj%+*âZÅéıPqU©Ê)%¢»    )…)Lë)%"•%-)íL)IqR$ÇD¶‡Çy0‡Á)%ƒàmÚñ◊Ì™aHH:mù&ûJY◊ö¶5IKÄä¢x Á)%8ÊùHÒLdâI@‚JJ.Hï$åîDmi$"Ê2qÒQ¿Á˝˛
Ĉ
¯
@‚˝˛
Ĉ
¯
@‚˘
ÄÏ
@‚¡¡‡à

Ü0`    å`ÿ
@IJIH :R ÿ
Qe»∂9 IJªé®‰4BWp‰JŸò@¿

˜¿

˜GlácrÑäâZ!JÅ«wT©JÑÍÅJΩŸñxìR"ícÖ2\Lr]…Ÿ&‹ö¶$2î∞ÖZ–ñ—Ÿ4ñÈ$:{°Ãc'ìnl;fid„nÏŸı˙ÄŸı˙ÄŸı˙ÄŸ¡¡¡¡¡¡¡¡¡¡¡¡¡¡
¿ 8Õ  Õ)I¨§qXÃŒw™à
’‹¢†#TŒ    %7îï« "`ŒJ\u!'d@DÏŒ3±ìÉâ(≈√ƒdëŒ˛B˛
Ã˛B˛
Ã
˛B˛
…¡¡
†yp¯
÷        ˛ÄP ê
÷    .Àc≠êë9B$Î$í/¨π-¿ÿ
T,ï•&®ëBÉõTñQRí◊òL•)D»¢<ÑE%Ë"Œdë¿ÿ¸S*ki—#ÑGHå    ≥É#ı @ÿ8®9'M…!~uÂJxç"fi"¢#Äÿ¸Ä˛

—¸Ä˛

—
¸˙œ¡¡    ‡Ä
ÅÄÀ
@ÄB@À
Qe≈`D@À    rÑääŃ@À    ñxìÄ$@À    &‹ï$ÄÀ4ñÈ    
À ¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜ál«c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜«lc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜lGc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜Glyc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜
ál
«c
¡¡ÿ3Íÿ@Î ¬ÿ¿Îÿ@Îÿ¿Î ¬ÿ@Î ¬ÿ¿Îÿ@Îÿ¿Î ¬˛
èÓ„@Î
 ÿ0
åxÿÃflˇfi„œÒ€€Ω¿Â¿Î€˜è€ÛÃ{Ôfl˚`Â@Îfi˝èõÜlofi‰¿Î ÛˇèûˆoÔÓÛ˘‡Œ˝

ò˛‚@Î ˛
˛Àÿ¿Îÿ@Îÿ¿Î    
 ‹ˇ‡È
˜Á @Î
 ˜"*Á" È
˜Á ¿Î
˜Á @Î
‹à†¿Î
 ˜Á ÈÄ0˝
8¸Ó @Î ">˛"2˝"*:"?¢"cÊ""sÆÚ" È!}Ô˜ˆ˝Ïˇfl˛f˜˚ˇ~Û ¿Î!ˇˇü∞˝ˇœÌÊyˇ˘å0Û @Î àõœøü∏¸àûÀÃæçÓÓÿ΢Ω∏Ûà†¿Î ˇ6ˆˆ˝?}ü≥ˇ˚œ}Ô¸Á|Û È˙
ÄÍ @Î ""&˙"*"'¢Í" È
˜Á ¿Î
˜Á @Î
‹à†¿Î
 ˜Á È
˜Á @Î    
 ‹ˇ‡È
˜Á ¿Î
˜Á @Î
˜Á ¿Î
 ˜Á È
˜Á @Î
 ˜Á È
˜Á ¿Î
˜Á @Î
˜Á ¿Î
 ˜
Èˇ
 È
˜
@ˆÄı @Î
 ˜
@ˆÄı
 È
˝@ˆÄı ¿Î˛@ˆÄı @ÎgmwÃlfŒÄ@ˆÄı ¿Î ¸ôK(^ôí@ˆÄı
 È!ÉâK(Pâí@Ä˚Äı @Îò@@Ä
˜@Ä
˜
«lc
& ~yq»NvéÄ@    
˝Ä 
˙
 È(
˝@¸@    1€ª∂9„ Äyø9]º‡¸ ¿Î(
˝@¸@    {&•LóÄÄ §ƒE¸ @Î$
˜    @    @‚•Lî˛Ä$§¸E¸ ¿Î"
 ˜@;û∏¥„†ÄG‚`¸
 È"
˜
@˝ IJÄD˚ @Î 
 ˜
@˝ IJÄ
Œ8˚
 È
˜
@ˆÄı ¿Î
˜
@ˆÄı @Î
˜
@ˆÄı ¿Î
 ˜
@ˆÄı
 È
˜
@ˆÄı @Î
 ˜
Èˇ
 È
˜
@ˆÄı ¿Î
˜
@ˆÄı @Î
˜
@ˆÄı ¿Î
 ˜
@ˆÄı
 È
˜
@ˆÄı @Î
 ˜@¯Ä<˙
 È
˜@    
˘Ä ˙ ¿Î 
˜@    3‰˙Ä"Y‹iù¿¸ @Î
˜@    y˙Ä=}(õÛ˚ ¿Î
 ˜@    Iê˙Ä!°(äL¿¸
 È 
˜@8Ù˙Ä=$y˚ĸ @Î
 ˜
@ˆÄı
 È
˜
@ˆÄı ¿Î
˜
@ˆÄ¯ @Î
˜
@ˆÄ˙` ¿Î
 ˜
@ˆÄ$
  È
˜
@ˆÄ%¢Ìúñ›Á¢!: @Î
 ˜
@ˆÄ&!"¬¢í #òb È
˜
@ˆÄ%#>íæíb$Ü ¿Î
˜
@ˆÄ-úÔÒŸú˚¸Ú @Î
˜
@ˆÄ¯ ¿Î
 ˜
@ˆÄ¯ È
˜
@ˆÄı @Î
 ˜
@ˆÄı
 È
˜
@ˆÄı ¿Î
˜
Èˇ @Î
˜Á ¿Î
 ˜Á È
˜Á @Î
 ˜Á È
˜Á ¿Î
˜Á @Î
‹ˇ‡¿Î ¬ÿ@Î ¬ÿ¿Îÿ@Îÿ¿Î ¬ÿ@Î ¬ÿ¿Îÿ@Îÿ¿Î ¬ŸU@Ο3Í¡¡¡ò@Ä¿
˜Ä¿
˜lGc
¡¡¡¡¡¡¡¡¡¡¡¡¡
>»
     »
@»
ê»
    !–ÒË»
"à»
3¸>p»¡¡¡¡¡    Ä¿˛    G
ÅÄ@@ÿ        
 ˛    ÄÄ@ÿûã˛ 
IÍK8Í#]#Éìµ ‚∞Ÿ•îP‡@π*§QUIU,R]E@Ÿ$¥‡@ S$êÈËäÈ    sÇââ@Ÿ!òËÅÄ"UH∞2ã”ã@¥“ ÄŸ18∏p‡ÄgÍhàŸÃtí}çøDåÑÄŸ˛D˚˛˝◊˛D˚˛P˝◊˛8˚˛ ˝◊¡¡#¸aÄ    ˛ÄÅ@Ä¿˛˛Ä‰#¸"    ˛
Ä@ @ ˛˛Ä‰&"-,Á+dKn∏_ÌQAp[*-Ç"4uñ›¡tÌ¿‰&"™ëBT    ™)U§,@§ëk(¢†≠=VÑ%\ö´Jïtĉ%!DíBî<ry("Kπ)Iqƒ°))‰Ñ)ÖíÚQ«'•„&"$]"ƒ®pB¢l/xâÌ£QŸAÛ“âÑJ∑$DÿD*Mĉ%!#¢#dHN9HWqI"ap‚ARyÑE•<ìÉë…„¸Û@Ÿ¸Ù
@Ÿ¸ÛÄŸ¡¡(˙@Äp˛ààÄįÊ&S
à¸ÄÄÄ
HÊ)%RònVZRF^ãb
kk#de…6flZ»∂9
Ö) GK|‡Á($
b®    §®ΩÍJ§ï¢µ5e§™äöj%+*âZÅéıPqU©Ê)%¢»    )…)Lë)%"•%-)íL)IqR$ÇD¶‡Çy0‡Á)%ƒàmÚñ◊Ì™aHH:mù&ûJY◊ö¶5IKÄä¢x Á)%8ÊùHÒLdâI@‚JJ.Hï$åîDmi$"Ê2qÒQ¿Á˝˛
Ĉ
¯
@‚˝˛
Ĉ
¯
@‚˘
ÄÏ
@‚¡¡‡à

Ü0`    å`ÿ
@IJIH :R ÿ
Qe»∂9 IJªé®‰4BWp‰JŸò@¿

˜¿

˜Glác
rÑäâZ!JÅ«wT©JÑÍÅJΩŸñxìR"ícÖ2\Lr]…Ÿ&‹ö¶$2î∞ÖZ–ñ—Ÿ4ñÈ$:{°Ãc'ìnl;fid„nÏŸı˙ÄŸı˙ÄŸı˙ÄŸ¡¡¡¡¡¡¡¡¡¡¡¡¡¡
¿ 8Õ  Õ)I¨§qXÃŒw™à
’‹¢†#TŒ    %7îï« "`ŒJ\u!'d@DÏŒ3±ìÉâ(≈√ƒdëŒ˛B˛
Ã˛B˛
Ã
˛B˛
…¡¡
†yp¯
÷        ˛ÄP ê
÷    .Àc≠êë9B$Î$í/¨π-¿ÿ
T,ï•&®ëBÉõTñQRí◊òL•)D»¢<ÑE%Ë"Œdë¿ÿ¸S*ki—#ÑGHå    ≥É#ı @ÿ8®9'M…!~uÂJxç"fi"¢#Äÿ¸Ä˛

—¸Ä˛

—
¸˙œ¡¡    ‡Ä
ÅÄÀ
@ÄB@À
Qe≈`D@À    rÑääŃ@À    ñxìÄ$@À    &‹ï$ÄÀ4ñÈ    
À ¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜ál«c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜«lc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜lGc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜Glyc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜ylπc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜πl˘c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜˘l9c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜9lyc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜ylπc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜πl˘c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜˘l9c¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜9lkc¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜ylπc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜πl˘c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜˘l9c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜9lyc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜ylπc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜πl˘c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜˘l9c
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜9lkc
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇg@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äAbout ‡)Apple Events

, (‡3-17
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh¢(eäAs prÀ`°dONLNd\¢h
,) eviously noted, the descriptor r°dONLNd%\
-h
?)ãecort`°dONLNd)\
?h
Ç)d (of data type ,
Courier®¿°dONLNd9\
Çh
¶)CAEDesc¶Ä°dONLNd?\
¶h
)$) is the fundamental °dONLNdTiäuï(rästrfi°dONLNdWiïu¨)ucturc‡°dONLNd\i≠uø)e in à‡°dONLNdaiøu
˜)IApple events, and it consists of a descriptor type and a handle to data. ◊Ä°dONLNd™i
˜u
˛(r
˜
A °dONLNd´i
ˇu
)
 
°dONLNd¨väÇ…(ädescriptor listÇ°dONLNdªv…Ç˝)? is a data strcÄ°dONLNd…v˛Ç
)5ucturÈ`°dONLNdŒv
Ç
=)
e of type ô†°dONLNdÿv
>Ç
z))
AEDescListdONLNd‚v
zÇ
ç)< defi°dONLNdÁv
éÇ
Î)ned by the data type °dONLNd¸ÉäèÆ(åäAEDesc}¿°dONLNd
ÉÆè
c)$-—that is, a descriptor list is a descriptor rË@°dONLNd
/É
cè
u)µecor\†°dONLNd
3É
vè
ÿ)d whose data handle r∞Ä°dONLNd
HÉ
ÿè)befers to a list °dONLNd
Xêäú‚(ôäof other descriptor rÓ °dONLNd
mê‚úÙ)XecorbÄ°dONLNd
qêıú˚)
d~@°dONLNd
rê˚ú
u)s (unless it is an empty list).°dONLNd
íßä≥¢(∞äTYPE°dONLNd
òßÆ≥
&)$AEDescList = AEDesc;°dONLNd
µß
P≥
¯)¢{list of descriptor records}°dONLNd
“øäÀ€(»äLike several other ïÄ°dONLNd
Âø€À
`)QApple Event Manager data strÄ°dONLNd
ø
aÀ
x)ÜucturÜ`°dONLNdø
xÀ)(es, a descriptor list is identical to a °dONLNd.ÃäÿΩ(’ädescriptor rfl@°dONLNd:ÃΩÿœ)3ecorS†°dONLNd>Öÿ
)d of data type 4 °dONLNdMÃ
ÿ
4)@AEDesc1‡°dONLNdSÃ
4ÿ
k)$; the only dif¯°dONLNdaÃ
kÿ
w)7fer⁄Ä°dONLNddÃ
wÿ)&ence is that the data in a descriptor °dONLNdäŸäÂ
p(‚ä8list must always consist of a list of other descriptor rô†°dONLNd¬Ÿ
pÂ
Ç)Êecor°dONLNdΔŸ
ÉÂ
í)ds. °dONLNdÀÎ䘢(ÙäFigurR¿°dONLNd–΢˜∂)e 3-8@°dONLNd’Î∂˜
›)G illustrates the logical arrangement of the descriptor list that specifi°dONLNdÎ
fi˜(Ù
fi
es the dir∫ °dONLNd'Θ)(ect °dONLNd+¯ä

k(

ä/parameter of the Open Documents event shown in |Ä°dONLNdZ¯
l

Ñ)‚FigurO@°dONLNd_¯
Ñ

¿)e 3-3 on page Ä°dONLNdm¯
¡

…)=3-b`°dONLNdo¯
…

”)10b`°dONLNdq¯
”

Ì)
. This °dONLNdx
ä

O(
ä2descriptor list consists of a list of descriptor rE`°dONLNd™

P

b)Δecorπ¿°dONLNdÆ

b

¿)ds that contain alias rÓ†°dONLNd≈

¿

“)^ecorc°dONLNd…

”

Î)ds to °dONLNdœ
ä
ê(
ä
fiå¿°dONLNd—
ê
º)
lenames. (>†°dONLNd€
Ω

)-See the chapter “Ax†°dONLNdÌ



Z)Rlias Manager” in R °dONLNd˛

[

†)LInside Macintosh4 °dONLNd

°

∏)F: Files°dONLNd

π

¯) for a detailed °dONLNd%
ä
+‰(
(ädescription of alias r}Ä°dONLNd;
‰
+ˆ)ZecorÒ‡°dONLNd?
ˆ
+
)ds.)


MH
^4
NH
^"
NH]

ˇ·ˇ‚7^
    °dONLNdD
Cä
N¥(
Kä
Figure 3-8°dONLNdO
CÃ
N“)B
A0°dONLNdP
C“
N
T)& descriptor list for a list of aliases
°dONLNdx9äEÁ(BäThe descriptor list in _‡°dONLNdè9ËE
)^Figur2†°dONLNdî9
E
)e 3-8– °dONLNdô9
E
 ) pr@°dONLNdú9
!E
ü)ovides the data for a keywor.†°dONLNd∏9
üE
ƒ)~d-specifi`°dONLNd¡9
≈E
)&ed descriptor °dONLNdœFäRç(Oä
rE°dONLNd–FéR†)ecorπ`°dONLNd‘F†R≤)d. K@°dONLNdÿF≥Rœ)eywor
Ä°dONLNd›FœRÙ)d-specififl@°dONLNdÊFÙR
4)%ed descriptor r£‡°dONLNdıF
5R
G)Aecor@°dONLNd˘F
HR
d)ds for Œ†°dONLNdF
cR)&Apple event parameters can in turn be °dONLNd&Sä_–(\äcombined in an 
k†°dONLNd5S—_
)G
AE record,1°dONLNd?S

_
©)0) which is a descriptor list of data type W‡°dONLNdhS
©_
”)®AERecorU@°dONLNdoS
”_
Ÿ)*
dT‡°dONLNdpS
Ÿ_
€)
.°dONLNdrjäv¢(säTYPE°dONLNdxjÆv
2)$AERecord = AEDescList;°dONLNdòj
bv
)¥{list of keyword-specified }°dONLNd¡x
bÑ
‡*{ descriptor records}


]ä"4
^ä!


^ä"4
]á
^àò@@
ˆ@
ˆ
^à
û~¡¡¡ŸˇÄΟˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿Îò@@Ä
ˆ@Ä
ˆ
ûà
fi~Ÿˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿Îò@Ä¿
ˆÄ¿
ˆ
fià~Ÿˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿ÎŸˇ¿Îò@¿

ˆ¿

ˆà^~Ÿˇ¿Î¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡
#‡‡3¿»
! @H@»
a@àÄ»    a¿@â«    íéâ«    
 àí«    ?¡b«¡¡¡¡¡
Ù 0:¿ÄÿêÄ  
Ä ÿÖËŸÄ`rs¥ÆK¸r∞QO¡pYìÄ€ΔY"é`•ÖE‘§%@°Pdž©,,⁄

K'
Èë.xHô$$)A"è°2KÛÄ€éD    
hç-H68JÅ„√ÖA˚x¿Ä€ãCé9∑‰à»à%–DÅBùARW?⁄@˙
˝@˝@◊@˙
˛

@˛

@◊Ä˙
˝Ä˝Ä◊¡¡(
臿p@:HIJ@Ä8¿ÄÄ8Ä@Ê'D±@ @@@˝@ÄÄ@Ê($ƒ©Ä;‚≤“í2Ëõ[Z;F^ã`Ωë—>â±»Rët∂ÓÊ($•*ÄMEEÔRUIM)©ÆMJ§ï†&í*≤Tî–îÔRáZPÊ($
,ÄIéIJdâíII)*…ë)% $¢Lñâ$ë$Jg'íéÊ($

HÄì»èî∂ø⁄ì“BCì◊Ì™`I¥UúΩ©1®"&¬Ê($ãi»“áäc$Jë"RR“âIDi$&÷I!gc#ü‰úÊ˝˛Ñı¯Ñ·˝˛Ñı¯Ñ·
˘ÑÎÑ·¡¡
˛@Ä1ÄÄFå` ◊§@˝J@Äíê 
◊§èÎ.â∞ÛâJU‹ÍNA†íïsá"PŸ
%òDTî—î;∫†*T†·~§
UËŸ
H∑Ñô$ê·8
ìR•¿Å$$√íÓHŸl·»˝©02 î•ÑTÌ¡%)`ñàêŸHæà©!Áùc8h∂„còΔGw`Ÿı ˚˛ÄŸı ˚˛ÄŸı ˚˛ÄŸ¡ò@

@
ˆ

@
ˆ^àû~¡¡¡¡¡¡¡¡¡¡¡¡¡ 
¿

¿Õ Äb
ÄÕbîàÄZ GïÄÏ`ŒgzîÄ≠]…*
4†ŒíS8Å)IZr
%Õ
•†GRsDM`Œ;8íåZ<#HàŒ ˛@à ˛@à ˛…¡¡
‡!‡àwp?¿Ä÷ê ê" ÄÄ÷íÒ<õ:ÿâ    ‘"N± ¢˛À ‹◊•!b…MRiI
(<ÀR†$Â    ï ◊
    AD IîJJ»DRW@),Ò%%◊
a%2ì∂öí8xDtÑ`M∏:=™◊äCíq‹ë”–ÓT£ƒi-“)8◊¸à˛ ˛—¸à˛ ˛†—
¸p˙¿œ¡¡
˛@ §@$ §èÎ.K" 
%òDT§" 
H∑Ñô$" l·»˝H"$ Hæà®àò ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆûàfi~¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆfià~¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆàP~¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
ˆ@
ˆ
^à
û~
¡¡¡ŸUͬÿ¿ÎŸ@Îÿ¿Î¬Ÿ@άÿ¿ÎŸ@Îÿ¿Î¬˝1ˇ
å‰@Î
Ä1çÄ
ÄŒˇ„€‹y˝π˝ç¸Â¿Î~Ò˚~yçˇ˜èÿÂ@Îfl±ÛpÕç‡qåx¿ÎÒÛfiÕˇ?flˇ‹Œ˝3fi@νc«ÿ¿ÎŸ@Îÿ¿Î    

‹ˇÈ

˜Á@Î

˜ÁÈ

˜Á¿Î

˜Á@Î

˜Á¿Î

˜ÁÈ

˜Á@Î

˜ÁÈ

˜Á¿Î
8˚˚@Ó@Î
$IJœ∏Ô¿Î
%雜±œ=ød꡸ÔÈ
'Ÿ5&`ú§¢¶CÔ@Î
&&`¨†§æ‰í@“ÔÈ
9‹ı√†wGøø˜åÔ¿Î

˛
$˛DÍ@Î

˛
D˛
ŒÍ¿Î

˜ÁÈ

˜Á@Î

˜ÁÈ

˜Á¿Î

˜Á@Î

˜Á¿Î

˜ÁÈ

˜Á@Î

˜ÁÈ

‹ˇ¿Î

˜Á@Î

˜Á¿Î

˜ÁÈ

˜Á@Î

˜ÁÈ

˜ÄaÄ0˝Ù¿Î

˜    ¡Ä`˛Ù@Î
8˘øüÁª˘ˇˇsÛΩ˝¯ı¿Î
$˙˚3ÕˇÌΩ˘„˛ÁÔ¿ıÈ!
%ü ˚è3Õ‡·Ω˘„ΔgÏ`ı@Îò@@Ä
ˆ@Ä
ˆ
ûà
fi~

'œÄ˚˚û«øΩøc{˝øÿıÈ
&LÄ˚˙Ô¿Î
9«†˚˙Ô@Î

˜Á¿Î

˜ÁÈ

˜Á@Î

˜
Èˇ
¯È

˜
˜Ù¿Î

˜
˜Ù@Î

˜
˜Ù¿Î

˜
˜Ù
È

˜
˜Ù@Î

˜
˜Ù
È

˜p˚˝

Ç˙¿Î!

˜H
˝0Ä˙@Î$

˜Kªücû2oŒÜ‡¸¿Î"

˜O≤jL¡ôx)1(Ç9ĸ
È$

˜L*L¡Y@    )?8ÇH`¸@Î"

˜sπÎá@Ó:ΔoÔø¿¸
È

˜
˛H˛˜¿Î 

˜
˛à˛sį@Î

˜
˜Ù¿Î

˜
˜Ù
È

˜
˜Ù@Î

˜
˜Ù
È

˜
˜Ù¿Î

˜
Èˇ¯@Î

˜
˜Ù¿Î

˜
˜Ù
È

˜
˜Ù@Î

˜
˜Ù
È

˜
˜Ù¿Î

˜
˜Ù@Î

˜
˜`˛ ˝¿Î

˜
˜
@˛@    ˝
È

˜
˜
f9±õ8˚7C@Î

˜p˘oazfHf|æßÄÈ"

˜H˙iB&HfD¶§¿Î#

˜K>@˚gq9⁄8Z<û£Ä@Î

˜Oü˙Ù¿Î

˜Lô˙Ù
È

˜sè@˚Ù@Î

˜
˜
  Ä ¸
È

˜
˜   ¸¿Î

˜
˜¶ê=,≥¸@Î

˜
˜©P2≤œê¸¿Î

˜
˜i`2“ƒ¸
È

˜
˜&D2åªê¸@Î

˜
˜¸ ¸
È

˜
˜¸ ¸¿Î

˜
˜Ù@Î

˜
˜Ù¿Î

˜
Èˇ
¯È

˜Á@Î

˜ÁÈ

˜Á¿Î

˜Á@Î

˜Á¿Î

˜ÁÈ

˜Á@Î

˜
Èˇ
¯È

˜
˜Ù¿Î

˜
˜Ù@Î

˜
˜Ù¿Îò@Ä¿
ˆÄ¿
ˆ
fià~


˜
˜Ù
È

˜
˜Ù@Î

˜
˜Ù
È

˜p˚˝

Ç˙¿Î!

˜H
˝0Ä˙@Î$

˜Kªücû2oŒÜ‡¸¿Î"

˜O≤jL¡ôx)1(Ç9ĸ
È$

˜L*L¡Y@    )?8ÇH`¸@Î"

˜sπÎá@Ó:ΔoÔø¿¸
È

˜
˛H˛˜¿Î 

˜
˛à˛sį@Î

˜
˜Ù¿Î

˜
˜Ù
È

˜
˜Ù@Î

˜
˜Ù
È

˜
˜Ù¿Î

˜
Èˇ¯@Î

˜
˜Ù¿Î

˜
˜Ù
È

˜
˜Ù@Î

˜
˜Ù
È

˜
˜`˛ ˝¿Î

˜
˜
@˛@    ˝@Î

˜
˜
f9±õ8˚7C¿Î

˜
˜oazfHf|æßÄÈ

˜
˜iB&HfD¶§@Î

˜p˘gq9⁄8Z<û£ÄÈ

˜H˙Ù¿Î

˜K>@˚Ù@Î

˜Oü˙Ù¿Î

˜Lô˙    ¿ Ä ¸
È!

˜sè@˚       ¸@Î

˜
˜&`=,≥¸
È

˜
˜/ê2≤œê¸¿Î

˜
˜(Ä2“ƒ¸@Î

˜
˜«t2åªê¸¿Î

˜
˜¸ ¸
È

˜
˜¸ ¸@Î

˜
˜Ù
È

˜
˜Ù¿Î

˜
˜Ù@Î

˜
Èˇ¯¿Î

˜ˆÛÈ

˜Á@Î

˜ÁÈ

˜Á¿Î

˜Á@Î

˜Á¿Î

˜ÁÈ

˜Á@Î

˜ÁÈ

‹ˇ¿ÎŸ@Îÿ¿Î¬Ÿ@άÿ¿ÎŸ@Îÿ¿Î¬Ÿ@άŸÃ¿Îò@¿

ˆ¿

ˆà^~
ŸU@Ρ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡
#‡‡3¿»
! @H@»
a@àÄ»    a¿@â«    íéâ«    
 àí«    ?¡b«¡¡¡¡¡
Ù 0:¿ÄÿêÄ  
Ä ÿÖËŸÄ`rs¥ÆK¸r∞QO¡pYìÄ€ΔY"é`•ÖE‘§%@°Pdž©,,⁄

K'
Èë.xHô$$)A"è°2KÛÄ€éD    
hç-H68JÅ„√ÖA˚x¿Ä€ãCé9∑‰à»à%–DÅBùARW?⁄@˙
˝@˝@◊@˙
˛

@˛

@◊Ä˙
˝Ä˝Ä◊¡¡(
臿p@:HIJ@Ä8¿ÄÄ8Ä@Ê'D±@ @@@˝@ÄÄ@Ê($ƒ©Ä;‚≤“í2Ëõ[Z;F^ã`Ωë—>â±»Rët∂ÓÊ($•*ÄMEEÔRUIM)©ÆMJ§ï†&í*≤Tî–îÔRáZPÊ($
,ÄIéIJdâíII)*…ë)% $¢Lñâ$ë$Jg'íéÊ($

HÄì»èî∂ø⁄ì“BCì◊Ì™`I¥UúΩ©1®"&¬Ê($ãi»“áäc$Jë"RR“âIDi$&÷I!gc#ü‰úÊ˝˛Ñı¯Ñ·˝˛Ñı¯Ñ·
˘ÑÎÑ·¡¡
˛@Ä1ÄÄFå` ◊§@˝J@Äíê 
◊§èÎ.â∞ÛâJU‹ÍNA†íïsá"PŸ
%òDTî—î;∫†*T†·~§
UËŸ
H∑Ñô$ê·8
ìR•¿Å$$√íÓHŸl·»˝©02 î•ÑTÌ¡%)`ñàêŸHæà©!Áùc8h∂„còΔGw`Ÿı ˚˛ÄŸı ˚˛ÄŸı ˚˛ÄŸ¡ò@

@
ˆ

@
ˆ^àû~
¡¡¡¡¡¡¡¡¡¡¡¡¡ 
¿

¿Õ Äb
ÄÕbîàÄZ GïÄÏ`ŒgzîÄ≠]…*
4†ŒíS8Å)IZr
%Õ
•†GRsDM`Œ;8íåZ<#HàŒ ˛@à ˛@à ˛…¡¡
‡!‡àwp?¿Ä÷ê ê" ÄÄ÷íÒ<õ:ÿâ    ‘"N± ¢˛À ‹◊•!b…MRiI
(<ÀR†$Â    ï ◊
    AD IîJJ»DRW@),Ò%%◊
a%2ì∂öí8xDtÑ`M∏:=™◊äCíq‹ë”–ÓT£ƒi-“)8◊¸à˛ ˛—¸à˛ ˛†—
¸p˙¿œ¡¡
˛@ §@$ §èÎ.K" 
%òDT§" 
H∑Ñô$" l·»˝H"$ Hæà®àò ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆûàfi~
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆfià~
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆàP~
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
ˆ@
ˆPàê~¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
ˆ@Ä
ˆêà–~¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
ˆÄ¿
ˆ–à~¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

ˆ¿

ˆàP~¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
ˆ

@
ˆPàê~¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆêà–~¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆ–à~¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆàB~¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
ˆ@
ˆPàê~
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
ˆ@Ä
ˆêà–~
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
ˆÄ¿
ˆ–à~
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

ˆ¿

ˆàP~
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
ˆ

@
ˆPàê~
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆêà–~
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆ–à~
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆàB~
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ*(@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-18    )BAbout ‡)Apple Events4^*¿
¯
°dONLNd\lh
-(el.The handle for a descriptor list of data type ,
Courier`°dONLNd.\
.h
X)¬AERecor¿°dONLNd5\
Xh
^)*
d`°dONLNd6\
^h
d) rY`°dONLNd8\
dh
©)efers to a list of °dONLNdKiluç(rlkeywor˘`°dONLNdQiçu≤)!d-specifi◊ °dONLNdZi≥uÛ)&ed descriptor rõ¿°dONLNdiiÙu
)Aecor °dONLNdmi
u
!)ds tha¸†°dONLNdsi
!u
É)t can be used to constrH`°dONLNdäi
Ñu
î)cuct #¿°dONLNdéi
îu
õ)
AΰdONLNdèi
õu
Ã)pple event °dONLNdövlÇô(l    parameter°dONLNd£vödž).s.Œ°dONLNd•v†Çµ) The +`°dONLNd™v∂Ç
$)Apple Event Manager pr!`°dONLNd¿v
$Ç
G)novides r凰dONLNd»v
GÇ
‰)#$outines that allow your application °dONLNdÏÉlèw(ålto ∑‡°dONLNdÔÉwè)crÌ °dONLNdÒÉèì)eate ‰`°dONLNdˆÉìèß)AE r`°dONLNd˙É®è∫)ecorÄ¿°dONLNd˛É∫è
)ds and extract data frÄ°dONLNd
É
è
e)^om them when crã°dONLNd
#É
eè
í)Meating or r°dONLNd
.É
ìè
œ).esponding to °dONLNd
;êlúâ(ôlApple }Ä°dONLNd
Aêäú´)events. °dONLNd
J¢lÆ|(´lAn :@°dONLNd
M¢|Æê)AE rb@°dONLNd
Q¢êÆ¢)ecor÷†°dONLNd
U¢¢Æ
)d has the descriptor type †°dONLNd
o¢
Æ
[)qtypeAERecord °dONLNd
{¢
[Æ
¢)H and can be coerÄ°dONLNd
ã¢
¢Æ
‡)Gced to several °dONLNd
öØlª“(∏lother descriptor types. [†°dONLNd
≤Ø“ª‚)fAn 
t@°dONLNd
µØ‚ª
9)Apple event record®°dONLNd
«Ø
9ª
q)W, which is difJ °dONLNd
’Ø
rª
~)9fer,†°dONLNd
ÿØ
~ª
ï)ent fr¢‡°dONLNd
ޯ
ïª
≥)om an _`°dONLNd
‰Ø
≥ª
«)AE rá`°dONLNd
ËØ
ǻ
Ÿ)ecor˚¿°dONLNd
ÏØ
ٻ
‰)d, °dONLNd
Ôºl»s(≈lis•`°dONLNd
Òºs»u)
 %`°dONLNd
Úºv»{)
a%`°dONLNd
Ûº{»
2),nother special descriptor list of data type 5 °dONLNdº
2»
n)∑
AppleEvent1`°dONLNd)º
n»
…)< and descriptor type °dONLNd>…l’∫(“ltypeAppleEven{ °dONLNdK…∫’¿)N
tz¿°dONLNdL…¿’¬)
.°dONLNdN‡lÏÑ(ÈlTYPE°dONLNdT‡êÏ
)$AppleEvent = AERecord;°dONLNdt‡
DÏ
Œ)¥{list of attributes andw`°dONLNdå‡
ŒÏ
⁄)ä }°dONLNdõÓ
D˙
Ï(˜
D{ parameters necessary for }°dONLNdƒ¸
D

™*{ an Apple event}°dONLNd÷
l
 |(
lAn :@°dONLNdŸ
|
 ∏)Apple event r °dONLNdÊ
∏
  )<ecor>`°dONLNdÍ
À
 
)d describes a full-flb`°dONLNdˇ


 
<)Tedged ›‡°dONLNd

<
 
o)
Apple evenÊ@°dONLNd

o
 
œ)3t. Like the data for an °dONLNd'
!l
-y(
*lAEc°dONLNd)
!z
-|)
 „°dONLNd*
!|
-)
r®°dONLNd+
!Ä
-í)ecor`°dONLNd/
!ì
-‡)d, the data for an ¢†°dONLNdB
!‡
-
)MApple event r2`°dONLNdO
!

-
/)=ecor¶¿°dONLNdS
!
/
-
¨)d consists of a list of keywor∑†°dONLNdq
!
¨
-
—)}d-specifiï`°dONLNdz
!
“
-
fl)&ed °dONLNd}
.l
:ü(
7ldescriptor rfl@°dONLNdâ
.ü
:±)3ecorS†°dONLNdç
.≤
:Ó)ds. Unlike an ·Ä°dONLNdõ
.Ó
:
)<AE r    Ä°dONLNdü
.

:
)ecor}‡°dONLNd£
.

:
b)d, the data for an  °dONLNd∂
.
c
:
ü)NApple event r쇰dONLNd√
.
ü
:
±)<ecor@°dONLNd«
.
≤
:
È)d is divided °dONLNd‘
;l
G
’(
DlTinto two parts, one for attributes and one for parameters. This division within the ¢†°dONLNd(
;
’
G
Ú(
D
’Apple °dONLNd.
Hl
Tä(
Qlevent r@°dONLNd5
Hã
Tù)ecor܆°dONLNd9
Hù
T’)d allows the {†°dONLNdF
H’
T
≠)8.Apple Event Manager to distinguish between an Ó‡°dONLNdt
H
≠
T
Ï)ÿApple event’s °dONLNdÇ
Ul
aÔ(
^lattributes and its parameters. °dONLNd¢
gl
ss*
D=@°dONLNd£
gt
s¥)escriptor lists, ÍÄ°dONLNd¥
g≥
s«)?AE rÄ°dONLNd∏
g»
s⁄)ecor܇°dONLNdº
g⁄
s¸)ds, and Ó`°dONLNdƒ
g¸
s
8)"Apple event r~ °dONLNd—
g
9
s
K)=ecorÚÄ°dONLNd’
g
K
s
`)ds arê@°dONLNd⁄
g
a
s
©)e all descriptor r⇰dONLNdÏ
g
©
s
ª)Hecor˛@°dONLNd
g
ª
s
Ê)    ds whose °dONLNd˘
tl
Äï(
}l    handles rrÄ°dONLNd
tï
Ä
B))+efer to a nested list of other descriptor rB °dONLNd-
t
C
Ä
U)Æecor∂Ä°dONLNd1
t
U
Ä
Í)"ds. The data associated with each °dONLNdS
Ål
çƒ(
äldata type may be orj@°dONLNdf
Ń
çˆ)Xganized difB‡°dONLNdq
ň
ç
)2fer%`°dONLNdt
Å

ç
m)ently and is used by the L°dONLNdç
Å
m
ç
—)kApple Event Manager °dONLNd°
él
öx(
ólfor<°dONLNd§
éy
ö{)
 º°dONLNd•
é{
öá)difÊ`°dONLNd®
éá
öì)fer»‡°dONLNd´
éì
ö«)ent purpose†`°dONLNd∂
é»
ö⁄)5s. In@°dONLNdª
é€
ö
)
 each caseè`°dONLNd≈
é

ö
)+
,`°dONLNdΔ
é
    
ö
)
 è`°dONLNd«
é

ö
1)howeverú°dONLNdŒ
é
1
ö
6)&, ú°dONLNd–
é
6
ö
Ö)the data is identifiSÄ°dONLNd‰
é
Ü
ö
‹)Ped by a handle in a °dONLNd¯
õl
ßü(
§ldescriptor rfl@°dONLNd
õü
ß±)3ecorS†°dONLNd
õ≤
ß
N)#d. This means that you can pass an EÄ°dONLNd+
õ
N
ß
ä)úApple event r’@°dONLNd8
õ
ä
ß
ú)<ecorI†°dONLNd<
õ
ù
ß
√)    d to any °dONLNdE
®l
¥á(
±lApple˝Ä°dONLNdJ
®á
¥â)
 }Ä°dONLNdK
®ä
¥
<)'Event Manager function that expects an 3‡°dONLNdr
®
<
¥
P)≤AE r[‡°dONLNdv
®
P
¥
b)ecor–@°dONLNdz
®
b
¥
ï)d. Similarly@°dONLNdÜ
®
ï
¥
’)3, you can pass Ú`°dONLNdï
®
‘
¥
Ò)?Apple °dONLNdõ
µl
¡ä(
ælevent r@°dONLNd¢
µã
¡ù)ecor܆°dONLNd¶
µù
¡Ω)ds and n °dONLNd≠
µΩ
¡—) AE rñ °dONLNd±
µ—
¡„)ecor
Ä°dONLNdµ
µ‰
¡
™)0ds, as well as descriptor lists and descriptor r¬`°dONLNdÂ
µ
™
¡
º)Δecor6¿°dONLNdÈ
µ
Ω
¡
Í)ds, to any °dONLNdÙ
¬l
Œ
2(
Àl+Apple Event Manager functions that expect r‡°dONLNd
¬
3
Œ
E)«ecorz@°dONLNd#
¬
E
Œ
â)ds of data type ó¿°dONLNd3
¬
â
Œ
≠)DAEDescïÄ°dONLNd9
¬
≠
Œ
Ø)$
.°dONLNd;
‘l
‡v(
›l
W°dONLNd<
‘v
‡æ)
hen you use the „@°dONLNdL
‘æ
‡
*)HAECreateAppleEvent‹Ä°dONLNd^
‘
*
‡
f)l function, the i¿°dONLNdm
‘
g
‡
”)=Apple Event Manager crÕ‡°dONLNdÉ
‘
”
‡
Î)leates °dONLNdâ
·l
Ìy(
Ílan s°dONLNdå
·y
̵)Apple event r¿°dONLNdô
·∂
Ì»)=ecorw °dONLNdù
·»
Ì
[)#d containing the attributes for an “‡°dONLNd¿
·
[
Ì
œ)ìApple event’s event class, °dONLNd€
Ól
˙Ñ(
˜leventÕ@°dONLNd‡
ÓÑ
˙Ü)
 M@°dONLNd·
Óá
˙£)ID, tarp`°dONLNdË
Ó£
˙»)get addrà°dONLNd
Ó»
˙fi)%ess, rꆰdONLNdˆ
Ófi
˙
_)eturn ID, and transaction ID. °dONLNd
Ó
`
˙
f)Ç
YƒÄ°dONLNd
Ó
e
˙
ö)ou then use @°dONLNd!
Ó
õ
˙
’)6Apple Event °dONLNd-
˚l‰(lManager functions such as  °dONLNdG
˚Â
9)yAEPutParamDesc¿°dONLNdU
˚
9
N)T and ‡°dONLNdZ
˚
O
ª)AEPutAttributeDesc
 °dONLNdl
˚
ª
”)l to ad‘¿°dONLNdr
˚
”
Á)d or °dONLNdwlì(lmodify a0†°dONLNdîœ)(ttributes and U@°dONLNdçœÌ);to add D†°dONLNdîÓ
4)any necessary pw‡°dONLNd£
4
})Farameters to the ˙†°dONLNd¥
}
≥)IApple eventE`°dONLNdø
¥
π)7. °dONLNd¬l&Ñ(#lFigurR¿°dONLNd«Ñ&ò)e 3-9@°dONLNdÃò&
,)  shows an example of a complete ∏¿°dONLNdÏ
,&
ï)îApple event—a data strø†°dONLNd    
ï&
¨)iucturEÄ°dONLNd    
≠&
’)
e of type °dONLNd    'l3®(0l
AppleEvent|@°dONLNd    '®3
 )< containing a list of keyworã@°dONLNd    7'
 3
C)xd-specifĆ°dONLNd    ?'
C3
Ü)#ied descriptor r-†°dONLNd    O'
á3
ô)Decor¢°dONLNd    S'
ô3
‰)ds that name the °dONLNd    d4l@
(=l;attributes and parameters of an Open Documents event. The fi4†°dONLNd    †4
Ä@
è(=
Ägur臰dONLNd    £4
è@
È)e includes the event °dONLNd    ∏AlM◊(Jlclass attribute shown in ≥ °dONLNd    —A◊MÔ)kFigurÖ‡°dONLNd    ÷AÔM
)e 3-7#`°dONLNd    €A
M
ï)" and the descriptor list shown in >@°dONLNd    ˝A
ïM
≠)ëFigur°dONLNd
A
≠M
¡)e 3-8ÆÄ°dONLNd
A
¡M
„), which °dONLNd
NlZ•(Wlforms the dirÛÄ°dONLNd
N•Z
)9ect parameter—the keyworWÄ°dONLNd
4N
Z
C)yd-specifi5@°dONLNd
=N
DZ
Ñ)&ed descriptor r˘‡°dONLNd
LN
ÑZ
ñ)@ecorn@°dONLNd
PN
óZ
Ë)d with the keywor≥‡°dONLNd
aN
ËZ
)Qd °dONLNd
c[lgΔ(dlkeyDirectObjectz`°dONLNd
r[ΔgÚ)Z. The entir@‡°dONLNd
}[Ûg˝)-e fƇ°dONLNd
Ä[˝g
)
igurÚÄ°dONLNd
Ñ[
g
()e corrŸÄ°dONLNd
ä[
(g
ı)*esponds to the Open Documents event shown °dONLNd
¥hltw(qlin π¿°dONLNd
∑hwtè)FiguråÄ°dONLNd
ºhètÀ)e 3-3 on page K¿°dONLNd
 hÃt‘)=3-ü†°dONLNd
Ãh‘tfi)10ü†°dONLNd
Œhfit‡)

.°dONLNd
–zlÜr(Él
T†¿°dONLNd
—zrÜ–)he next two sections, ˆ °dONLNd
Áz–Ü
)^“Responding to ±‡°dONLNd
ˆz
Ü
X)HApple Events”ã¿°dONLNdz
YÜ
n)A and x‡°dONLNdz
oÜ
)“CrT‡°dONLNdz
Ü
◊)eating and Sending ˜‡°dONLNdz
ֆ
Û)WApple °dONLNd$álìë(êlEvents,”‹`°dONLNd,áëìù)% pr#Ä°dONLNd/áûì
≈)Covide a quick overview of the steps your application must take to rr‡°dONLNdrá
œ
Û(ê
≈
espond to °dONLNd|îl†ñ(ùl    and send Ä°dONLNdÖîó†—)+Apple eventsä@°dONLNdëî—†”):
.ˇÉú@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äAbout ‡)Apple Events

, (‡3-19
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHw4gHw"hH]

ˇ·ˇ‚7^    °dONLNd\äg¥(dä
Figure 3-9°dONLNd\Ãg
ê)B.Data structures within an Open Documents event

wº4wº

xâº4wàxâò@@
˜@
˜xâ∏Ä¡¡?“ˇÒ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚò@@Ä
˜@Ä
˜∏â¯Ä?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚò@Ä¿
˜Ä¿
˜¯â
8Ä?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚò@¿

˜¿

˜
8â
xÄ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚò@

@
˜

@
˜
xâ
∏Ä?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚò@
@
Ä
˜
@
Ä
˜
∏â
¯Ä?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚò@
Ä
¿
˜
Ä
¿
˜
¯â8Ä?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚò@
¿
Ú
˜
¿
Ú
˜8âjÄ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚò@@
˜@
˜xâ∏Ä
¡¡—3Ò“
Ò ”
Ò—ÄÚ“
Ò—ÄÚ ”
Ò“
Ò ”
Ò—ÄÚ“
ÒIJ0|€ÄÚ ¡Ä¿0`fi
Ò˚Ò˜Ó∑~›fifi
Ò ˝¯flønˇ„ˇÏfi
ÒÌÿ›∏3n¸c±Ï›ÄÚΩ¯˝Ô3∑ˇÓfi
Ò˝ÄfŸÄÚ ˛Äf⁄
Ò“
Ò ”
Ò
ÿˇ¿˝ÄÚ
ıÂ@˛
Ò
ıÂ@˝ÄÚ
 ıÂ@˛
Ò
ıÂ@˛
Ò 8˘˙

ÄÓ@˛
Ò%$@¸˛    @
ÄÄ|ÄÚ@˝ÄÚ'
$Œ⁄ÔòÁòIJ˛    Û~8fixá'gy‡Ú@˛
Ò&    %˘2ñPf|˝˛    AIEI$à±H§ÄÚ@˝ÄÚ&     %ñPV`˝˛    II}…$è•O§êÚ@˛
Ò'
8¸Ú„ê;úIJ˛    0én;„|Év`Ú@˛
Ò
 ˝Ä¸˝à Ì@˛
Ò
˝Ä"¸˛úpÌ@˝ÄÚ
ıÂ@˛
Ò
ıÂ@˝ÄÚ
 ÿˇ¿˛
Ò
ıÂ@˛
Ò
 ıÂ@˛
Ò
ıÂ@˝ÄÚ
ıÂ@˛
Òp˜Â@˝ÄÚ  H¯˛Ñ˛
Ò@˛
Ò%Iæ ˘˛ÄÑ

˛
ı@˛
Ò& Kfl¯˛ѸŒoÔ'„åÁÕö3χ˜@˛
Ò&JY¯˛Öâ$ÙÕˆôÎ’y˘Ä˜@˝ÄÚ'qœ ˘˛Ñi$îÕÅíô*UAà`˜@˛
Ò#
ı˛ıƒƒrO˜óÈ’8˘¿˜@˝ÄÚ
 ııÚ@˛
Ò
ııÚ@˛
Ò
 ıÂ@˛
Ò
ıÂ@˝ÄÚ
ÿˇ¿˛
Ò
ÛćÄÚ ”
ÒÙ‰˛
Ò ”
Ò
ıfiÄÚı‚@
Ò—ÄÚ ˆ`fl
Ò    ’
Òò@@Ä
˜@Ä
˜∏â¯Ä
 ˜‡ˇ
Òˆ·
˛ÄÚˆ·

Òˆ·
˛ÄÚ ˜·

Òˆ·

Ò ˜·

Òˆ·
˛ÄÚˆ·

Òˆ
Ä¿Ï
˛ÄÚ ˜
Ä¿¿0Ì

Òˆ∑wù˚¸˜ˇ˜ˇÌ

Ò ˜ˇ˚7ø¯{€fløÄÓ

ÒˆÏ{1ÏÀ€flºÌ
˛ÄÚˆ«˚üø¯{˚ÛøÄÓ

Òˆ·
˛ÄÚ ˜·

Òˆ·

Ò ˜¡

ÒˆĈÚ
˛ÄÚˆĈÚ

ÒˆıàòÚàê
˛ÄÚ ˜ĈÚ

ÒˆĈÚ

Ò& ˜
¢""n""#¢˝"2"":¸".˚"0

Ò*ˆ
Äx
Ä˝?cΔqå
˛ÄÚ)ˆ
Äs∑ø∞˝˜¯ˇ˛˛fÒÁ˚ˇ¸

Ò)ˆ˛àˇfl¸˝¸àòààù˚fiˇ˚Óé˚Ô˘åËàê
˛ÄÚ+ ˜
Än¸˝Ä˝Éÿ6nfÿ√yΩ‡

Ò)ˆ
Äo›∑∑∞˝?˘ø3ˇªœœ¸Á¯

Ò! ˜¢˛".˙"2˛"
#¢˜"0

Ò ˆIJ˙˛
Ę
˛ÄÚˆĈÚ

ÒˆıàòÚàê
˛ÄÚ ˜ĈÚ

Òˆ¡

Ò ˜ÄÊ

ÒˆÄÊ
˛ÄÚˆÄÊ

ÒˆáÁˇ¯
˛ÄÚ ˜шÛ

ÒˆшÛ

Ò ˜шÛ

ÒˆшÛ
˛ÄÚˆшÛ

ÒˆÑp˚Û
˛ÄÚ& ˜
ÑH
˝¯˘

Ò'ˆÑKªücû2=∑úƸp˚

Ò) ˜ÑO≤jL¡ôx¢b"íà˚

Ò(ˆÑL*L¡Y@¢~"í¯˚
˛ÄÚ'ˆÑsπÎá@Ó:Cåq0˚

Ò&ˆÑ˝H˛˛B
˙
˛ÄÚ' ˜Ñ˝à˛
«8˙

ÒˆшÛ

Ò ˜шÛ

ÒˆшÛ
˛ÄÚˆшÛ

ÒˆáÁˇ¯
˛ÄÚ ˜шÛ

ÒˆшÛ

Ò ˜шÛ

ÒˆшÛ
˛ÄÚˆш˘

Òˆш˘
˛ÄÚò@Ä¿
˜Ä¿
˜¯â
8Ä
! ˜ш,Ó4Œ‡˚

ÒˆшæîM˘Ä˚

Ò$ ˜Ñp˘–îE&`˚

Ò$ˆÑH˙éí<˝¿˚
˛ÄÚˆÑK>@˚Û

ÒˆÑOü˙Û
˛ÄÚ" ˜ÑLô˙¯

Ò#ˆÑsè@˚˙
`

Ò$ ˜ш¯
 


Ò#ˆш‚vŒNŒÛ— á
˛ÄÚ"ˆш ãbëI!Ã1

Ò#ˆш¢äJüI1"C
˛ÄÚ$ ˜ш‹wܢÏŒ˘˛y

Òˆш¯

Ò ˜ш¯

ÒˆшÛ
˛ÄÚˆшÛ

ÒˆшÛ
˛ÄÚ ˜шÛ

ÒˆшÛ

Ò ˜áÁˇ¯

ÒˆÄÊ
˛ÄÚˆÄÊ

ÒˆÄÊ
˛ÄÚ ˜ÄÊ

Òˆ¡

Ò ˜·

Òˆ·
˛ÄÚˆ·

Òˆ·
˛ÄÚ ˜·

Òˆ·

Ò ˜·

Òˆ·
˛ÄÚˆ·

Òˆ    >?xÍ
˛ÄÚ ˜
0=ÄxÎ

Òˆ?nÔ=ûˇ˛ˇ‡Ï

Ò ˜1ˇˆ=è{{˜Ï

Òˆ1ÿˆ=õ{{˜ÄÏ
˛ÄÚˆ?è˜?~wÏ

Òˆ·
˛ÄÚ ˜·

Òˆ·

Ò ˜¡

ÒˆĈÚ
˛ÄÚˆĈÚ

ÒˆıàòÚàê
˛ÄÚ ˜ĈÚ

Ò ˆ
Än
Ä˝8ı

Ò* ˜
¢""z""#¢˝"2"":"?""cˇs.˝"0

Ò*ˆ
Äs∑ø∞˝˜¯ˇ˛˘çˇfl¸˛
˛ÄÚ)ˆ
Äfl¸˝Ä˝˚fi˚aç˚`˛

Ò)ˆ˛àÓù¸˝¸àòààüãÿæõÌç˚Ì˲àê
˛ÄÚ+ ˜
Äo›∑∑∞˝?˘ø3ˇªfl˝«¯˛

ÒˆIJ˙˛

Ę

Ò! ˜¢˛":˙"2˛"
'¢˜"0

ÒˆĈÚ
˛ÄÚˆĈÚ

ÒˆıàòÚàê
˛ÄÚ ˜ĈÚ

Òˆ¡

Ò ˜ÄÊ

ÒˆÄÊ
˛ÄÚò@¿

˜¿

˜
8â
xÄ
ˆÄÊ

ÒˆáÁˇ¯
˛ÄÚ ˜шÛ

ÒˆшÛ

Ò ˜шÛ

ÒˆшÛ
˛ÄÚˆÑp˚Û

Ò%ˆ
ÑH
˝¯˘
˛ÄÚ) ˜ÑKªücû2=∑úƸp˚

Ò'ˆÑO≤jL¡ôx¢b"íà˚

Ò) ˜ÑL*L¡Y@¢~"í¯˚

Ò(ˆÑsπÎá@Ó:Cåq0˚
˛ÄÚ%ˆÑ˝H˛˛B
˙

Ò&ˆÑ˝à˛
«8˙
˛ÄÚ ˜шÛ

ÒˆшÛ

Ò ˜шÛ

ÒˆшÛ
˛ÄÚˆшÛ

ÒˆáÁˇ¯
˛ÄÚ ˜шÛ

ÒˆшÛ

Ò ˜шÛ

ÒˆшÛ
˛ÄÚˆшÛ

Òˆш.˘
˛ÄÚ ˜ш)˘

Òˆш,Ó)˘

Ò" ˜Ñp˘æî)˘

Ò"ˆÑH˙–î)˘
˛ÄÚ"ˆÑK>@˚éí.˘

ÒˆÑOü˙Û
˛ÄÚ ˜ÑLô˙Û

Ò ˆÑsè@˚˜

Ò ˜ш˜

Ò"ˆш˚Ä˝ 
˛ÄÚ"ˆшÃL^wâq˚—fixË

Ò#ˆшdIäIä)™)!à
˛ÄÚ$ ˜шúLI˙Iä    ´È$h

Ò"ˆшˆ˚é7~qÁ®›õ»

Ò  ˜ш˙

Òˆш˙
˛ÄÚˆшÛ

ÒˆшÛ
˛ÄÚ ˜шÛ

ÒˆшÛ

Ò ˜áÁˇ¯

ÒˆÄÊ
˛ÄÚˆÄÊ

ÒˆÄÊ
˛ÄÚ ˜ÄÊ

Òˆ¡

Ò ˜·

Òˆ·
˛ÄÚˆ·

Òˆ·
˛ÄÚ ˜·

Òˆ·

Ò ˜·

Òˆ·
˛ÄÚˆ·

Òˆ·
˛ÄÚ ˜·

Òˆ?˝
‡Ô

Òò@

@
˜

@
˜
xâ
∏Ä
 ˜````

ÒˆÔÓˇ=ÔÔˇ‹ˇ˚ˇ
˛ÄÚˆˇg∑ø∑Ó~?mÔflÄÒ

Òˆøxm∑øçÓ~omÔ‹
˛ÄÚ ˜˝ÔwΩÔ˜ˇfi?˝˘flÄÒ

Òˆ˝`1ÄÈ

Ò ˜˛¿1ÄÈ

Òˆ·
˛ÄÚˆ¡

ÒˆıàòÚàê
˛ÄÚ ˜ĈÚ

ÒˆĈÚ

Ò ˜¢ˆ"2Ú"0

Ò%ˆ
Än
Ä˝8=‡˘
˛ÄÚ(ˆ
Äx
Ä˝`s˝

Ò*ˆ˛à˚øˇø∏˝àòààüˇ˛ˇˇ˘Ôˇfl¸˛àê
˛ÄÚ+ ˜
Äfl¸˝Ä˝˚fiŒxˇÔ˚`˛

Ò)ˆ
Än¸˝Ä˝ÉfiŒx¿√{m‡˛

Ò+ ˜
¢""oˇ∑∑≤˝"2""?˚ø˛ÔˇÁ˙˛"0

Ò ˆIJ˙˛

Ę
˛ÄÚˆIJ˙˛
Ę

ÒˆıàòÚàê
˛ÄÚ ˜ĈÚ

ÒˆĈÚ

Ò ˜¢ˆ"2Ú"0

Òˆ¡
˛ÄÚˆÄÊ

ÒˆÄÊ
˛ÄÚ ˜ÄÊ

ÒˆáÁˇ¯

Ò ˜шÛ

ÒˆшÛ
˛ÄÚˆшÛ

ÒˆшÛ
˛ÄÚ ˜шÛ

Ò!ˆÑp˚˙
`¸

Ò+ ˜
ÑH
˝`!¿@

Ò+ˆ!ÑKªücû2=∑ú7º"oÑÛ{p
˛ÄÚ*ˆ$ÑO≤jL¡ôx¢bRR!ÑöNA,à

Ò+ˆ!ÑL*L¡Y@¢~rR$DäRI(¯
˛ÄÚ, ˜$ÑsπÎá@Ó:Cå€úˇüo0˛0

Ò(ˆÑ˝H˛˛B˝

Ò* ˜Ñ˝à˛

«8p˝

ÒˆшÛ
˛ÄÚˆшÛ

ÒˆшÛ
˛ÄÚ ˜шÛ

ÒˆáÁˇ¯

Ò ˜шÛ

ÒˆшÛ
˛ÄÚˆшÛ

ÒˆшÛ
˛ÄÚ ˜шÛ

Ò!ˆш>˝P
 ˛

Ò$ ˜шÄ@ ˛

Ò#ˆшŸÕÃÓVg7˛
˛ÄÚ%ˆÑp˘    Ú^ûôYÛLò˛

Ò'ˆÑH˙    2PíôXìLܲ
˛ÄÚ) ˜ÑK>@˚ÒŒNÓWq4ú˛

Ò!ˆÑOü˙˝@à˙

Ò$ ˜ÑLô˙˛Äà˙

ÒˆÑsè@˚Û
˛ÄÚ"ˆш˛" ˛˛

Ò#ˆш˛"$fà˛
˛ÄÚò@
@
Ä
˜
@
Ä
˜
∏â
¯Ä
$ ˜шÔòÓDBç∏Ñ˛

Ò"ˆш=3=ò@+≈D˛

Ò$ ˜ш%3 f@>E|˛

Ò#ˆшÔ‹@%‚˛
˛ÄÚˆш˚ ˛˛

Ò ˆш˚ ˛˛
˛ÄÚ ˜шÛ

ÒˆшÛ

Ò ˜шÛ

ÒˆшÛ
˛ÄÚˆáÁˇ¯

ÒˆÄÊ
˛ÄÚ ˜ÄÊ

ÒˆÄÊ

Ò ˜ÄÊ

Òˆ¡
˛ÄÚˆ·

Òˆ·
˛ÄÚ ˜·

Òˆ·

Ò ˜·

Òˆ·
˛ÄÚˆ·

Òˆ·
˛ÄÚ ˜
Ä‚

Òˆ‡0
Ò ˜‡`
Òˆ‡¿ÄÚˆ`Â
Ä
Òˆ
IJ¿Î
˛ÄÚ ˜0üœ˜Áœ˝¿Ï
Òˆ ˜ç˛˜ˇˇÄÏ
Ò ˜`~1çfl∑¯ÒÄÏ
Òˆ¿{flœ~˜ÔˇÄÏ˛ÄÚˆ¯¸Á
Òˆ¸Á
˛ÄÚ ˜·

Òˆ¡

Ò ˜¢ˆ"2Ú"0

ÒˆĈÚ
˛ÄÚˆĈÚ

ÒˆıàòÚàê
˛ÄÚ ˜ĈÚ

Ò(ˆ
Än
Ä˝80˛
‡¿˝

Ò+ ˜
¢""z""#¢˝"2"":">""#/b"#¢""0

Ò*ˆ
Äs∑ø∞˝˜˚w˛Ÿ˚œ{‡
˛ÄÚ)ˆ
Äfl¸˝Ä˝˚€3?€ÏflŸÄ

Ò)ˆ˛àÓù¸˝¸àòààü〪∏À˘Ïÿ…∏ààê
˛ÄÚ+ ˜
Äo›∑∑∞˝?˘æflyœ¯œ¯‡

Ò#ˆIJ˙˛

ĸ¿˝

Ò& ˜¢˛":˙"2˛"
'¢˝"
#¢˝"0

ÒˆĈÚ
˛ÄÚˆĈÚ

ÒˆıàòÚàê
˛ÄÚ ˜¡

ÒˆÄÊ

Ò ˜ÄÊ

ÒˆÄÊ
˛ÄÚˆáÁˇ¯

ÒˆшÛ
˛ÄÚ ˜шÛ

ÒˆшÛ

Ò ˜шÛ

ÒˆшÛ
˛ÄÚò@
Ä
¿
˜
Ä
¿
˜
¯â8Ä
ˆшÛ

Ò!ˆÑp˚˙ ˚
˛ÄÚ) ˜
ÑH
˝    g¯¸

Ò(ˆÑKªücû2=∑ú2Pafi¸

Ò* ˜ÑO≤jL¡ôx¢bS#¸

Ò)ˆÑL*L¡Y@¢~rR …¸
˛ÄÚ(ˆÑsπÎá@Ó:Cåfl˛ˇÜ¸

Ò#ˆÑ˝H˛˛B˜
˛ÄÚ$ ˜Ñ˝à˛
«˜

ÒˆшÛ

Ò ˜шÛ

ÒˆшÛ
˛ÄÚˆáÁˇ¯

ÒˆшÛ
˛ÄÚ ˜шÛ

ÒˆшÛ

Ò ˜шÛ

ÒˆшÛ
˛ÄÚ"ˆÑp˘!
˚

Ò%ˆÑH˙     ¸
˛ÄÚ( ˜ÑK>@˚
!~7é››∞˝

Ò%ˆÑOü˙
!ƒJ'Ÿ5*`˝

Ò' ˜ÑLô˙
!4J&*`˝

Ò'ˆÑsè@˚
=‚2‹ı≈†˝
˛ÄÚˆш˙
˚

Òˆш˙
˚
˛ÄÚ ˜шÛ

Òˆш˝
¯

Ò ˜ш˝
¯

Òˆш337:˘
˛ÄÚˆш'é`˘

Òˆш$D©˘
˛ÄÚ ˜ш#ª'r˘

ÒˆшÛ

Ò ˜шÛ

ÒˆшÛ
˛ÄÚˆшÛ

ÒˆшÛ
˛ÄÚ ˜шÛ

ÒˆáÁˇ¯

Ò ˜ĘÒ

ÒˆĘ@ÒP
˛ÄÚˆĘ@Ò

Òˆį
˛ÄÚ ˜¡0

Òˆ‚

Ò ˜ˆ Ó
Å
Òˆ˜Ï
˛ÄÚˆ˜ÄÏ    
Òˆ·
˛ÄÚ ˜¯Î
@
Òˆ˘Í

Ò ˜˘¿Í

Òˆ·
˛ÄÚˆ˙È

Òˆ˚Êˇ˛ÄÚ ˜˚Ê

Òˆ˚Ê

Ò ˜˚Ê

Òˆ˚ÊÄÚˆ˚
Áˇ
Ç
Òˆ˚
˜@ÚÇÄÚ ˜˚
˜@Ú
Ç
Òˆ˚
˜@Ú
Ç
Òò@
¿
Ú
˜
¿
Ú
˜8âjÄ
 ˜˚
˜@Ú
Ç
Òˆ˚
˜@ÚÇÄÚˆ˚
˜@Ú
Ç
Òˆ˚@¸@˝
¯ÇÄÚ" ˜˚ÄIJ@ ¬˜
Ç
Ò#ˆ˚ô€]ÛÛ@yø8bCÄ˙
Ç
Ò$ ˜˚ø&R œÄ@ §ƒ¢Ê˘
Ç
Ò$ˆ˚†‚R
Ã@$§¸‚    !Ä˙ÇÄÚ"ˆ˚û\rsê@Gøæˇ˘
Ç
Òˆ˚
˝    @@DıÇÄÚ ˜˚
˝    @@
Œı
Ç
Òˆ˚
˜@Ú
Ç
Ò ˜˚
˜@Ú
Ç
Òˆ˚
˜@ÚÇÄÚˆ˚
Áˇ
Ç
Òˆ˚
˜@ÚÇÄÚ ˜˚
˜@Ú
Ç
Òˆ˚
˜@Ú
Ç
Ò ˜˚
˜@Ú
Ç
Òˆ˚
˜@ÚÇÄÚˆ˚
˜@IJ Ä˚
Ç
Òˆ˚˘@)˝!$˚ÇÄÚ% ˜˚    
˙@)òÊΔl„Ït‹m˛
Ç
Ò$ˆ˚    3‰˚@9ΩÖÈô!ò5Ú˙û˛
Ç
Ò& ˜˚    y˚@E§eô!ò5öê˛
Ç
Ò%ˆ˚    Iê˚@EùƒÁh·h4Úzé˛ÇÄÚˆ˚8Ù˚@Ú
Ç
Òˆ˚
˜@ÚÇÄÚ ˜˚
˜@Ú
Ç
Òˆ˚
˜@(ÄÄÄ˙
Ç
Ò ˜˚
˜@,ÄÄÄ˙
Ç
Òˆ˚
˜@Jö@Ù≤Ã@˙ÇÄÚˆ˚
˜@J•@ À>@˙
Ç
Òˆ˚
˜@I•ÄÀK@˙ÇÄÚ ˜˚
˜@Hô 2Ó@˙
Ç
Òˆ˚
˜@ ¸Ä˙
Ç
Ò ˜˚
˜@ ¸Ä˙
Ç
Òˆ˚
˜@ÚÇÄÚˆ˚
˜@Ú
Ç
Òˆ˚
˜@ÚÇÄÚ ˜˚
˜@Ú
Ç
Òˆ˚
Áˇ
Ç
Ò ˜˚Ê

Òˆ˚ÊÄÚˆ˚Ê

Òˆ˚ÊÄÚ ˜˚Ê

Òˆ˚Ê

Ò ˜˚
Áˇ
Ç
Òˆ˚
˜@ÚÇÄÚò@@
˜@
˜jâ™Ä?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚò@@Ä
˜@Ä
˜™âÍÄ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ?“ˇÄÚ“ˇÄÚ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡    G¡¿Δ«    B@Å)«    ¬Ç)«    √ÄÇ.«    
$92«    $AR«    É·å«¡¡¡¡¡#Ë¿ Ä@
$ >˝@‚#
 $  Ä@˛$˛b˝@‚$ 
—≤"ÚèÌË⁄q’u≠ÇÿÅQl£¨[Á•æ‚$ 
å≤E%%ì%Y%ÄU&¶ÖhÅÍ¥!*‰‘≠H™‘‚$ ñNƒ)Ihã.p¶DƒâHÅO$!L,ï…á9<ò‚$ à"$Oo°ÀŒH´eÈèòΔîL"Uπ!¡!Q<‚$ áäJ!dãG‡“II
ê8c»|"-(Úéè(‚ÄÔÄÿÄÔÄÿ
ÓÄÿ¡¡'¡Ä‡Ätê˝Ä    p 
Ä    
pÄÊ'âbÄ@Ä ÄÄ˝  Ä
     ÄÊ($
âSw≈j•$≈—6 &ΩdvåΩ¿;{#¢}√ê•"Èm‹Ê($
JUöäïfi•Jíö SV¨öïI+@M$Ud©+A(fi•*¥†Ê($2Yì§î $í íT•ì"RJ@IDô-JBH$îŒO%Ê($ë
'ë=)nflµ&§â'Ø€T¿ìh´9{T√PE)hTMÑÊ($”ë•(ΔI"$D©E•í$à“HM¨í$Ç ŒΔG>#…8Ê˝ 
ı˘

·˝ 
ı˘

·˙

Ï

·¡¡¸Ä     c

å 
Äÿ
HÄ˝$îÅ@Äÿ
I÷]¡Áî´π’ÉG ¡]√ë(ŸK0à©+B)(wu@U)A¿…C™*ÙŸëo    2JA¬p)&8¶KŘ·1…w$ŸŸ√ë˚T¿d@#)K´Z
âDÇXKDHŸë}R$Éœ:Δ2p“mΔΔ9¡ìçª∞Ÿò@Ä¿
˜Ä¿
˜Íâ*Äı@˚˛@Ÿı@˚˛@Ÿı@˚˛@Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡@Ä8ÄÕ
@
ƒ
Ã≈)µîè+
ÿ¿ŒŒı)
ZªíTi@Œ
$¶qRí¥‰JÕ)K@é§$Êàö¿Œv28q%¥xFëŒ@˛ ÄÃ@˛ ÄÃ@˛ …¡¡¿C¿4Ó‡Ä
’
 A 
D@)
’
%‚"y6u±®Dùb@)E˝óï∏◊
JB≈íö§“íPyñ•@I )*@◊Çâîì(îî#êà§ÆÄRY‚JJ8◊¬Je'm5$pàÈ¿õpt{T◊á$‚%π"/ß°‹©Gà“[§R$p◊˝

˛@˛ —˝

˛@
@—¸‡˚

Äœ¡¡¸Ä0 
HÄH$ 
I÷\ñD K0à©H8D ëo    2HD Ÿ√ë˙êDH ë}Q90 ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜*âjÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜jâ™Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜™âÍÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜Íâ*Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜*â\Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜jâ™Ä
ˆ˚
˜@Ú
Ç
Òˆ˚
˜@ÚÇÄÚ ˜˚
˜@Ú
Ç
Òˆ˚
˜@Ú
Ç
Ò ˜˚
˜@Ú
Ç
Òˆ˚@¸@˝
¯ÇÄÚ ˆ˚ÄIJ@ ¬˜
Ç
Ò$ˆ˚ô€]ÛÛ@yø8bCÄ˙ÇÄÚ$ ˜˚ø&R œÄ@ §ƒ¢Ê˘
Ç
Ò#ˆ˚†‚R
Ã@$§¸‚    !Ä˙
Ç
Ò$ ˜˚û\rsê@Gøæˇ˘
Ç
Òˆ˚
˝    @@DıÇÄÚˆ˚
˝    @@
Œı
Ç
Òˆ˚
˜@ÚÇÄÚ ˜˚
˜@Ú
Ç
Òˆ˚
˜@Ú
Ç
Ò ˜˚
Áˇ
Ç
Òˆ˚
˜@ÚÇÄÚˆ˚
˜@Ú
Ç
Òˆ˚
˜@ÚÇÄÚ ˜˚
˜@Ú
Ç
Òˆ˚˘@Ú
Ç
Ò" ˜˚    
˙@IJ Ä˚
Ç
Ò!ˆ˚    3‰˚@)˝!$˚ÇÄÚ$ˆ˚    y˚@)òÊΔl„Ït‹m˛
Ç
Ò%ˆ˚    Iê˚@9ΩÖÈô!ò5Ú˙û˛ÇÄÚ& ˜˚8Ù˚@E§eô!ò5öê˛
Ç
Ò ˆ˚
˜@EùƒÁh·h4Úzé˛
Ç
Ò ˜˚
˜@Ú
Ç
Òˆ˚
˜@ÚÇÄÚˆ˚
˜@Ú
Ç
Òˆ˚
˜@'ÄÄ˙ÇÄÚ ˜˚
˜@$ÄÄÄ˙
Ç
Òˆ˚
˜@DôÄÙ≤Ã@˙
Ç
Ò ˜˚
˜@Dæ@ À>@˙
Ç
Òˆ˚
˜@D¢ÀK@˙ÇÄÚˆ˚
˜@G– 2Ó@˙
Ç
Òˆ˚
˜@ ¸Ä˙ÇÄÚ ˜˚
˜@ ¸Ä˙
Ç
Òˆ˚
˜@Ú
Ç
Ò ˜˚
˜@Ú
Ç
Òˆ˚
˜@ÚÇÄÚˆ˚
˜@Ú
Ç
Òˆ˚
ÁˇÇÄÚ ˜˚Ê

Òˆ˚Ê

Ò ˜˚Ê

Òˆ˚ÊÄÚˆ˚Ê

Òˆ˚ÊÄÚ ˜˚Êˇ
˛
Òˆ·

Ò ˜·

Òˆ·
˛ÄÚˆ·

Òˆ·
˛ÄÚ ˜·

Òˆ‡ˇ
Ò ”
Ò—ÄÚ“
Ò—ÄÚ ”
Ò“
Òò@@Ä
˜@Ä
˜™âÍÄ
 ”
Ò—ÄÚ“
Ò“ÃÄÚ“3Ò¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡    G¡¿Δ«    B@Å)«    ¬Ç)«    √ÄÇ.«    
$92«    $AR«    É·å«¡¡¡¡¡#Ë¿ Ä@
$ >˝@‚#
 $  Ä@˛$˛b˝@‚$ 
—≤"ÚèÌË⁄q’u≠ÇÿÅQl£¨[Á•æ‚$ 
å≤E%%ì%Y%ÄU&¶ÖhÅÍ¥!*‰‘≠H™‘‚$ ñNƒ)Ihã.p¶DƒâHÅO$!L,ï…á9<ò‚$ à"$Oo°ÀŒH´eÈèòΔîL"Uπ!¡!Q<‚$ áäJ!dãG‡“II
ê8c»|"-(Úéè(‚ÄÔÄÿÄÔÄÿ
ÓÄÿ¡¡'¡Ä‡Ätê˝Ä    p 
Ä    
pÄÊ'âbÄ@Ä ÄÄ˝  Ä
     ÄÊ($
âSw≈j•$≈—6 &ΩdvåΩ¿;{#¢}√ê•"Èm‹Ê($
JUöäïfi•Jíö SV¨öïI+@M$Ud©+A(fi•*¥†Ê($2Yì§î $í íT•ì"RJ@IDô-JBH$îŒO%Ê($ë
'ë=)nflµ&§â'Ø€T¿ìh´9{T√PE)hTMÑÊ($”ë•(ΔI"$D©E•í$à“HM¨í$Ç ŒΔG>#…8Ê˝ 
ı˘

·˝ 
ı˘

·˙

Ï

·¡¡¸Ä     c

å 
Äÿ
HÄ˝$îÅ@Äÿ
I÷]¡Áî´π’ÉG ¡]√ë(ŸK0à©+B)(wu@U)A¿…C™*ÙŸëo    2JA¬p)&8¶KŘ·1…w$ŸŸ√ë˚T¿d@#)K´Z
âDÇXKDHŸë}R$Éœ:Δ2p“mΔΔ9¡ìçª∞Ÿò@Ä¿
˜Ä¿
˜Íâ*Ä
ı@˚˛@Ÿı@˚˛@Ÿı@˚˛@Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡@Ä8ÄÕ
@
ƒ
Ã≈)µîè+
ÿ¿ŒŒı)
ZªíTi@Œ
$¶qRí¥‰JÕ)K@é§$Êàö¿Œv28q%¥xFëŒ@˛ ÄÃ@˛ ÄÃ@˛ …¡¡¿C¿4Ó‡Ä
’
 A 
D@)
’
%‚"y6u±®Dùb@)E˝óï∏◊
JB≈íö§“íPyñ•@I )*@◊Çâîì(îî#êà§ÆÄRY‚JJ8◊¬Je'm5$pàÈ¿õpt{T◊á$‚%π"/ß°‹©Gà“[§R$p◊˝

˛@˛ —˝

˛@
@—¸‡˚

Äœ¡¡¸Ä0 
HÄH$ 
I÷\ñD K0à©H8D ëo    2HD Ÿ√ë˙êDH ë}Q90 ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜*âjÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜jâ™Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜™âÍÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜Íâ*Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜*â\Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ∞@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-20    )BResponding to Ü)<Apple Events4^*¿
¯

^*x
¯4^*x
¯

à*ê
¯4â*ê
¯ ä*ä
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNdu*àó(É*Responding to =Í°dONLNduóà¯)mApple EventsˇˇˇˇˇˇU˛(É

3
°dONLNdôl•s(¢l
A∫†°dONLNdôs•¡) client application臰dONLNd0ô¬•Î)O
 typicallyú°dONLNd:ôΕ
))
 uses the ¿°dONLNdDô
•
ä)(Apple Event Manager to crÅ¿°dONLNd]ô
ã•
◊)xeate and send an ´@°dONLNdnô
ץ
Ù)LApple °dONLNdt¶l≤ä(Ølevent r@°dONLNd{¶ã≤
&)$equesting a service or information. dONLNdü¶
&≤
-)õ
AœÄ°dONLNd†¶
-≤
Ö) server application r' °dONLNdµ¶
Ü≤
Ê)Yesponds by using the °dONLNd ≥løÂ(ºlApple Event Manager to pr≠‡°dONLNd„≥Âø
)y
ocess the V@°dONLNdÌ≥
ø
E)*Apple event°°dONLNd¯≥
Eø
N)6, ej†°dONLNd˚≥
Oø
á)
xtract data frÒ‡°dONLNd
    ≥
áø
Ë)8om the attributes and °dONLNd
¿lê(…lparameters of the `°dONLNd
1¿ºÃ
)PApple event, an2Ä°dONLNd
@¿
Ã

)Fd Œ@°dONLNd
B¿

Ã
W)if necessary add rW†°dONLNd
T¿
XÃ
∑)Nequested data to the r®@°dONLNd
j¿
∑Ã
Á)_eply event °dONLNd
uÕlŸo(÷l
rE°dONLNd
vÕpŸ≥)eturned by the @°dONLNd
ÖÕ≥Ÿ
)CApple Event Manager tàÄ°dONLNd
öÕ
Ÿ
¥)g%o the client application. The server H °dONLNd
øÕ
µŸ
ÿ)õusually °dONLNd
«⁄lÊu(„lprG °dONLNd
…⁄vÊõ)
    ovides it`°dONLNd
“⁄úÊ∏)&s own dONLNd
ÿ⁄∏Ê
)Apple event handler fñ†°dONLNd
Ì⁄
Ê
ã)aor performing the action r@°dONLNd⁄
åÊ
ı)sequested by the client’s °dONLNd ÁlÛß(lApple event. °dONLNd.˘l
ç*As its fi¯¿°dONLNd7˘ç
Ó)!rst step in supporting M°dONLNdN˘Ô

q)bApple events, your applicatio8†°dONLNdk˘
r

ƒ)Én should support tN`°dONLNd}˘
ƒ

—)Rhe °dONLNdÄ
l
o(
l
rE°dONLNdÅ
p
á)equir\@°dONLNdÜ
á
î)ed c@°dONLNdâ
î

 )Apple events sent by the Finder]°dONLNd®

 

Õ)å'. If you plan to implement publish and °dONLNdœ
l

K(
l4subscribe capabilities, your application must also r˘`°dONLNd

K

â)flespond to the †°dONLNd

ä

È)?Apple events sent by °dONLNd&
 l
,«(
)lthe Edition Manager√Ä°dONLNd9
 Δ
,À)Z. dONLNd;
 À
,—)
YV`°dONLNd<
 —
,
})(our application should also be able to r.@°dONLNdd
 
}
,
‹)¨espond to the standar‡`°dONLNdy
 
‹
,
‰)_d °dONLNd{
-l
9
(
6l'Apple events that other applications ar\@°dONLNd¢
-

9
„)¨4e likely to send to it or that it can send to itselfô°dONLNd÷
-
„
9
Ë)À. °dONLNdÿ
:l
Fr(
Cl
T†¿°dONLNdŸ
:r
F¨)his section prG °dONLNdÁ
:≠
Ffl);ovides a qu‡°dONLNdÚ
:‡
F
Ê)3;ick overview of the tasks your application must perform in °dONLNd-
Gl
So(
Pl
rE°dONLNd.
Gp
S¨)esponding to R¿°dONLNd;
G¨
SÈ)<Apple events.°dONLNdI
Yl
er(
bl
Tµ¿°dONLNdJ
Yq
e|)o rp@°dONLNdM
Y}
e´)
espond to 5 °dONLNdW
Y´
e
L).#Apple events, your application must,Zapf Dingbats°dONLNd{
ol
vq(
ul
n
°dONLNd}
lx
x¨)set the appro†°dONLNdâ
l¨
x”)4    opriate fl[°dONLNdì
l‘
x˝)(ags in its ,
Courier»†°dONLNdû
l˝
x
))
'»@°dONLNdü
l

x
)SIZEΔ¿°dONLNd£
l

x
!)
'Δ`°dONLNd§
l
!
x
') r`°dONLNd¶
l
(
x
@)esourS†°dONLNd´
l
@
x
I)ce°dONLNdÆ
Ål
àq(
ál
n
°dONLNd∞
~x
ä{)
t¬`°dONLNd±
~{
ä
-)+est for high-level events in its event loop°dONLNd›
ìl
öq(
ôl
n
°dONLNdfl
êx
úÅ)prG °dONLNd·
êÇ
úñ)
ovidg°dONLNdÂ
êñ
úù)e R@°dONLNdÁ
êù
ú
)Apple event handlers fë°dONLNd˝
ê

ú
)eor the x °dONLNd
ê

ú
Ü)Apple events it supportÄ°dONLNd
ê
á
ú
ã)i
s°dONLNd
•l
¨q(
´l
n
°dONLNd
¢x
Æô)use the k °dONLNd'
¢ö
Æ
)"AEInstallEventHandlerc@°dONLNd<
¢

Æ
w)~ function to install its º†°dONLNdU
¢
w
Æ
÷)_Apple event handlers°dONLNdj
∑l
æq(
Ωl
n
°dONLNdl
¥x
¿ô)use the k °dONLNdt
¥ö
¿
)"AEProcessAppleEventd°dONLNdá
¥

¿
K)r function to prq@°dONLNdñ
¥
K
¿
d)?ocess º@°dONLNdú
¥
d
¿
û)Apple events°dONLNd©
≈l
—É(
ŒlBeforÛ¿°dONLNdÆ
Ń
—è)e yÃÄ°dONLNd±
Ő
—Õ)our applicatio°@°dONLNdø
≈Œ
—Ï)>n can ry@°dONLNdΔ
≈Ï
—
)
espond to > °dONLNd–
≈

—
r).Apple events sent fr˘ °dONLNd‰
≈
r
—
Ü)Xom rᆰdONLNdË
≈
á
—
Ë)emote computers, the °dONLNd˝
“l
fi
Ã(
€lPuser of your application must allow network users to link to your application. Tο°dONLNdM
“
À
fi
ˆ(
€
Ào do this, °dONLNdX
fll
Î
5(
Ël/the user selects your application in the Finder5‡°dONLNdá
fl
5
Î
ã)…, chooses Sharing fr†°dONLNdõ
fl
ã
Î
)Vom the File menu, and °dONLNd±
Ïl
¯≠(
ılthen clicks the ´ °dONLNd¡
Ï≠
¯˘)AAllow Remote Pr´`°dONLNd–
Ï˘
¯
P)Logram Linking checü†°dONLNd‚
Ï
Q
¯
\)Xkb∂`°dONLNd‰
Ï
\
¯
Ó)$ox. If the user has not yet started °dONLNd
˘lu(lprG °dONLNd

˘v
&)
%ogram linking, the Sharing command ofÕ °dONLNd/
˘
&
œ)∞'fers to display the Sharing Setup contr `°dONLNdV
˘
œ
Ù)©    ol panel °dONLNd_l„(lso that the user can start pr#Ä°dONLNd|‰
Æ)x-ogram linking. The user must also authorize r`°dONLNd©
Æ
Ù) emote users for °dONLNdπlu(lprG °dONLNdªv
)
!ogram linking by using the Users  °dONLNd‹

)ñ
&“`°dONLNd›

!) Gr∏Ä°dONLNd‡
!
P)
oups contr≤¿°dONLNdÍ
P
Ç)/ol panel. Pr‰¿°dONLNdˆ
Ç
˜)2ogram linking and setting °dONLNd l,Ë()lup authenticated sessions ar3¿°dONLNd, È,
k)}e described in the chapter “Pr °dONLNdJ 
l,
¢)Éogram-to-Pr˘†°dONLNdU 
°,
¿)5ogram °dONLNd[-l9¿(6lCommunications TJ°dONLNdk-¿9
)Toolbox” in this book∑¿°dONLNd-
9
)Y
.

^*e
¯4_*e
¯ `l`
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdÅOl^
(ZlAccepting and ProcessinSÇ°dONLNdòO
^
)óg Û°dONLNdöO
^
=)
Apple E˝†°dONLNd°O
=^
])0ventsˇˇˇˇˇˇ€r)≥
3
°dONLNd®elqr(nl
Tµ¿°dONLNd©eqq∫)o accept or send `°dONLNd∫eªq
”)J@Apple events (or any other high-level events), you must set the °dONLNd˙rl~Ä({lapprI@°dONLNd˛rÅ~®)    opriate fl4†°dONLNd    r©~
)(ags in your application’s t°dONLNd    "r
~
<)o'SIZE'q¿°dONLNd    (r
<~
B)$ r∂¿°dONLNd    *r
B~
Z)esourˇ°dONLNd    /r
Z~
‡)ce and include code to handle °dONLNd    Mlã
d(àl9high-level events in your application’s main event loop. ˇm@@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äResponding to Ü)<Apple Events

, (‡3-21
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähê(eä
T∫¿°dONLNd
\èh•)wo fl°dONLNd\¶h“)ags in the ,
Courier˜@°dONLNd\“hˆ),'SIZE'ı°dONLNd\ˆh¸)$ r:°dONLNd\˝h
)esourÇ@°dONLNd\
h
Ω)%ce determine whether an application rÜ¿°dONLNdC\
Ωh)®eceives high-level °dONLNdViäu´(räevents: ,Zapf Dingbats°dONLNd_äÜè*
n
°dONLNda|ñà©)The ª¿°dONLNde|©à
')isHighLevelEventAware≥‡°dONLNdz|
'à
/)~ fl@†°dONLNd}|
0à
€)    (ag must be set for your application to r≤†°dONLNd•|
€à)´eceive any °dONLNd∞àñî·(ëñhigh-level events†°dONLNd¡à‚î‰)L
.°dONLNd√ùä§è(£ä
n
°dONLNd≈öñ¶©)The ª¿°dONLNd…ö©¶
-)localAndRemoteHLEvents≥Ä°dONLNdflö
-¶
5)Ñ fl@@°dONLNd‚ö
6¶
·)    (ag must be set for your application to r≤@°dONLNd

ö
·¶
˛)´eceive °dONLNd
¶ñ≤ˇ(Øñhigh-level events sent fr5‡°dONLNd
*¶
≤
•)j"om another computer on the network'¿°dONLNd
L¶
¶≤
®)¶
.°dONLNd
N∑ä√ö(¿äAn :@°dONLNd
Q∑ö√
p)3Apple event (like all high-level events) is identifi%†°dONLNd
Ö∑
q√
fi)◊ed by a message class of °dONLNd
ûƒä–‰(ÕäkHighLevelEventz`°dONLNd
≠ƒ‰–
)Z in the ëÄ°dONLNd
µƒ
–
)whatê°dONLNd
πƒ
–
) f4`°dONLNd
ªƒ
 –
m)ield of the event r£Ä°dONLNd
Œƒ
m–
)Mecor‡°dONLNd
“ƒ
Ä–
ã)d. °dONLNd
’ƒ
ã–
ë)
YΔÄ°dONLNd
÷ƒ
ê–
¿)ou test the +‡°dONLNd
‚ƒ
¡–
Ÿ)1what*`°dONLNd
ʃ
Ÿ–
fi) fŒ¿°dONLNd
˃
fi–
¸)ield of °dONLNd
—ä›ó(⁄äthe]`°dONLNd
Û—ò›ö)
 ›`°dONLNd
Ù—ö›∏)event ro†°dONLNd
˚—π›À)ecor‰°dONLNd
ˇ—À›
/)d to determine whetheB`°dONLNd—
0›
C)er it c–°dONLNd—
C›
ï)ontains the value r—¿°dONLNd-—
ï›
£)ReprbÄ°dONLNd0—
§›
Ê)esented by the °dONLNd?fiä͉(ÁäkHighLevelEventz`°dONLNdNfi‰Í
)Z constan@°dONLNdVfi
    Í
)%t; if yê°dONLNd]fi
Í
s)our application defø‡°dONLNdpfi
sÍ
)T!ines any high-level events other °dONLNdëÎ䘆(Ùäthan Ü¿°dONLNdñΆ˜fl)Apple events, Ä°dONLNd§Î‡˜
()@you should also ƒ@°dONLNd¥Î
(˜
J)H    test the -°dONLNdΩÎ
K˜
u)#message*`°dONLNdƒÎ
u˜
})* fi∑ °dONLNd«Î
}˜
«)eld of the event r=‡°dONLNdŸÎ
»˜
⁄)Kecor≤@°dONLNd›Î
⁄˜
Ì)d to °dONLNd‚¯ä

≥(

äBdetermine whether the high-level event is something other than an ê °dONLNd$¯
≥
(


≥Apple event. If the °dONLNd8
ä

F(
ä+high-level event is not one that you’ve defi‡°dONLNdd

G
)Ω/ned for your application, assume that it is an °dONLNdì
ä
≈(
äApple event.  ¿°dONLNd†
≈
Œ);(Yfl °dONLNd¢
Œ
”)    
oT†°dONLNd£
‘
Â)u ar†¿°dONLNdß
Â

?)e encouraged to use ¿†°dONLNdª

?

∫)ZApple events instead of defi¢`°dONLNd◊

ª

ˇ)|ning your own °dONLNdÂ
ä
+
0(
(ä%high-level events whenever possible.)°dONLNd
1ä
=
/*&After determining that an event is an ·Ä°dONLNd1
1
/
=
å)•Apple event, use the `°dONLNdF
1
ç
=
ˇ)^AEProcessAppleEvent@°dONLNdY
1
ˇ
=
)r
 °dONLNdZ
>ä
J⁄(
Gäfunction to let the πÄ°dONLNdn
>⁄
J
ë)P(Apple Event Manager identify the event. ø‡°dONLNdñ
>
ë
J
©)∑Figur톰dONLNdõ
>
©
J
¬)e 3-100 °dONLNd°
>
√
J
) shows how the °dONLNd∞
Kä
W¶(
TäSurfWP°dONLNdµ
K¶
W
Z)*riter application accepts and begins to prO`°dONLNdfl
K
Z
W
Ä)¥    ocess an ο°dONLNdË
K
Ä
W)&Apple event sent by the Finder®Ä°dONLNd
K
W
)à
.


yH
ä4
zH
ä"
zH]

ˇ·ˇ‚7^
    °dONLNd
oä
z∫(
wäFigure 3-10°dONLNd
oÃ
z
†)B0Accepting and processing an Open Documents event


âHó4
äHñ


äHó4
âF
äGò@@
˜@
˜
äG
 >¡¡?œˇÄı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ıò@@Ä
˜@Ä
˜
 G
>?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?Ρ˝͡¿ı?Ρ˝͡¿ı?Ρ˛͡¿ı?ΡÄ͡¿ı?Ρ@͡¿ı?Ρ ͡¿ı?ΡÛ¸͡¿ı?Ρ    ¸͡¿ı?Ρ‡¿͡¿ı?Ρ¡0͡¿ı?Ρ
Ä»͡¿ı?Ρ͡¿ı?ΡÚ͡¿ı?ΡÅ©͡¿ı?ΡTè͡¿ı?Ρ"(è͡¿ı?ΡBè͡¿ı?ΡDè͡¿ı?ΡÑ    ͡¿ı?Ρà(á͡¿ı?Ρ4@͡¿ı?Ρ    j ͡¿ı?Ρ    U͡¿ı?ΡJà͡¿ı?ΡED͡¿ı?Ρ
B¢͡¿ı?ΡêAS͡¿ı?ΡH ¨è͡¿ı?Ρ( \è͡¿ı?Ρ0è͡¿ı?Ρè͡¿ı?Ρè͡¿ı?Ρ ͡¿ı?Ρ
¿͡¿ı?Ρ˝͡¿ı?Ρ˝͡¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ıò@Ä¿
˜Ä¿
˜
GJ>?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ıò@¿

˜¿

˜JGä>?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ıò@

@
˜

@
˜äG >?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ı?œˇ¿ıœˇ¿ı¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡


»

    »

»
(»
êËr|»
ëÇ»
˛8»¡¡¡¡¡'¿`Äà
IJ ˛‡
˛˛ Â$Äêr@IJÄ˚à˛˛ Â'#OEê@0Ã≥ÖY;≠ºƒ
ã`àçbflp]-Â'#R (p$@1UzãR’¢™ƒ&»+DU°    W&•jÄ•V†Â'#íZp$@J#ìR$ô§«;ƒ»JD
y!
adÆLq…‰¿Â'#Ãt@à$ÄäÓ%úÃ=;    E\È∞|Δ4¢a≠…û
â‡Â'#ú\8ps
ùŸú)-ÜB#˜IpTÅ√C·iGy@²"˙ "˝à⁄˛"˙ "˝à⁄˛˙ ˝p⁄¡¡(}†@8˛DÅD@
¿|Ê&)ä
ƒ¸@

@@Ä$Ê)%)L∑+-)#/E±µµë≤2‰õ
o≠ã‰[Ĭîê#•æpÁ)%1T“T^ı%RJ—
Zö≤“UEM5ïïD≠    @«z®8™‘ÄÁ)%—dî‰î¶HîíëRíñîâäI&§∏â)A"SpA<òpÁ)%bD    6à˘Kkˆ’0é§$6øŒìO%,ÎÕSÇ$•¿EQ<Á)%sNç$x¶2D§â q%%$JâFJ"6¥àís8¯è(‡Á˝
˛
@ıĢ
 ‚˝
˛
@ıĢ
 ‚ò@
@
Ä
˜
@
Ä
˜ G
>˘
@Ï
 ‚¡¡DÄÑ06
0ÿ @˝"$I
ÿ(ø≤‰[úêd]«TrÅ+∏r%Ÿ    9BED≠•@©+™
T•    'u@•^Ä⁄
K<Iâ)Å˛˝1¬ô.–¶9.‰Ä⁄nèÕSíHíXB≠h!À    hâŸKtäàí=–Á9ìÉI∑6<Á2q∑vŸı˙@Ÿı˙@Ÿı˙@Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡
‡Õ
Õ§Ñ÷R8¨fŒ;’DjÓQP™ŒíõÑ    JJ„ê0Œ•.:êì≤ "vŒÿ…¡ƒîb·‚2HÄœ˛!˝ÄÃ˛!˝ÄÃ
˛!˝Ä ¡¡˛–¯
–ÇÄ@ê
–óâ±÷»í?Ÿy,—*J“ìTña"íê—L
&Rî¢d"fi$§ê—~    )ï5¥Ë    ≥áGµ —Tìâ&‰êç"˙E" —
¸@
À
¸@
À¸
Ä»¡¡    @¿¿À     @
! À    (ø≤‚∞" À        9BEE@‚ À
K<Iâ@ À    nè Å@À    KtäÑÄÂÄÀ¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜
GJ>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜JG|>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜
äG
 >
¡¡Œ3ÙŒ@ı ¬Œ¿ıŒ@ıŒ¿ı ¬Œ@ı ¬Œ¿ıŒ@ıŒ¿ı ¬˛3¯0fi@ı  ˙0‘˛É3∏˙<˜ænÔ·¿ı˛ÉzP˙<fiˇ?ˇˆ·@ı˛ãBP˙ffi¯1ÿˆ·¿ı s:H˙f˜ø蘑
ÛΔ›@ı ÙΔ–Œ¿ı˛
‘@ı˛@˝˜ˇ¿‰¿ı ‹Ífˆp˛˜`◊
ÚöüYH˛˜`‰@ı
 
2öâYH˜"`◊
¸Íw6H˜`‰¿ıIJˇˆ>¸aˇˇ¯Á@ı IJàÎààÿ˛àéà·Á¿ı ˚
êc˜p€›ÔúÔ‡a¿€˙–cfl¯fiwÔ˛˜¿a˛@Ë@ı ˚
í"c˛z˛sÔÚˆba˛`€˙>˜¯ÛfiÔfi˜¿a˛ Ë¿ı˛
ˇˇ¯ˇ˛¿˙aˇˇ¸ Ë@ı
Ä˛àà»˙à‡0Ë¿ı 
˛
˜`€
ˇƒ˝˜`Ë@ı 
0d˝˜ˇ‡€
?˛$˝˜`Ë¿ı
?˛$˝˜`Ë@ı
?‡$˝˜`Ë¿ı 
?‡$˝˜`€
>$˝˜`Ë@ı 
>$˝˜`€
>$˝˜`Ë¿ı
 $˝˜`Ë@ı 
?Ä$˝˛`Ë¿ı 
 $˝¸`0€ 
 $˝Δ“”0``Ë@ı 
?ˇ‰˝È+4¯`
¿€
˝-4@`‰¿ı
˝ÁE(”∏`‰@ı
˝˜`
¿Á¿ı 
˝˜` ⁄
?ƒ˝˜`
åÂòÈ@ı 
˝"˛`~ó–‹
˝2¸`0öÈ¿ı!
˝*…“”0`
Œë–È@ı
Ä˝+%+4¯`‰¿ı ˇˇ¯˝'&-4@`◊˛Ä˝"ƒE(”∏`‰@ıò@@Ä
˜@Ä
˜
 G
>
 Ä˝˜`
 ‹˛Ä˝˜`@È¿ı˛ˇˇ¯˝˜`› ÃʇÍ@ı˜˜`
Û+>iêÍ¿ı ¯˜`
3+iꛘ˜`˝ Ó&êÍ@ı ¯˜`Ÿ˛
¯¸˜`Ê¿ı˛
ĸ˜`‰@ı˛ãúÿ˝˜`‰¿ı ˙e˝˜`◊˛äe˝˜`Ê@ı ä\˝˜ˇ‡Ä⁄˜˜ˇ‡@Á¿ıÍ
 Á@ıÍ۸˿ı
 Î    ¸€Í‡¿È@ı Ρ0‹Í
ĻȿıÍÈ@ıÍÚÈ¿ı ÎÅ©‹ÍTÄÍ@ı Î"(Ä›ÍBÄÍ¿ıÍDÄÍ@ıÍÑ    È¿ı Îà(á‹Í4@È@ı Î    j ‹Í    UÈ¿ıÍJàÈ@ıÍEDÈ¿ı Î
B¢‹ÈêASÈ@ı ÍH ¨Ä›È( \ÄÍ¿ıÈ0ÄÍ@ıÈÄÍ¿ı ÍÄ›È
 Ë@ı     Í

¿€Œ¿ıŒ@ıŒ¿ı ¬Í8
í È@ı ÎDí‹Í2_´Ø∞Í¿ıÍR≠'‡Í@ıÍFRm& Í¿ı Î9“E#‡›Œ@ı ¬Œ¿ıŒ@ıŒ¿ı ¬Œ@ı ¬ÚÓˇÒ¿ıÚÔ

ÄÚ@ıÚÔ

ÄÚ¿ıò@Ä¿
˜Ä¿
˜
GJ>
 ÛÔ

ÄÂÚÔ

ÄÚ@ı ÛÄ Û

ÄÂÚ
 Û

ÄÚ¿ıÚKs¶7Ù

ÄÚ@ıÚØ…)LÄı

ÄÚ¿ı Û4I)LÄı

ÄÂÚ£»¶7Ù

ÄÚ@ı Û˝Ù

ÄÂÚ˝Ù

ÄÚ¿ıÚÔ

ÄÚ@ıÚÓˇÄÚ¿ı ÛÔ

ÄÂÚÔ

ÄÚ@ı ÛÔ

ÄÂÚ˘¯

ÄÚ¿ıÚ∞ÔÄį¸

ÄÚ@ıÚôÄÌπÔ
ü    ‡"à¸

ÄÚ¿ı Û(Δ
DîîúÄ"‡¸

ÄÂÚ∫$Åı|îÄÙ§ê"ĸ

ÄÚ@ı ÛoœÄb€ûfi`¿¸

ÄÂÚÔ

ÄÚ¿ıÚÔ

ÄÚ@ıÚÔ

ÄÚ¿ı Û`
Ę

ÄÂÚ#∞é    ˙

ÄÚ@ı Û-&6‰9∑ùùÁÄ˚

ÄÂÚ1‚LîD®à≈"í˚

ÄÚ¿ıÚ)"Dî¸Øàï>í@˚

ÄÚ@ıÚoøΩflòC?ÚŸà˚

ÄÚ¿ı Û˛Û

ÄÂÚ˛8Û

ÄÚ@ı ÛÔ

ÄÂÚ˝@`˝Ä
ÄÚ¿ıÚ¿v!¿>ÄÄB
ÄÚ@ıÚ
'$Δ¯á6‚≥Ω·€ºÒ
ÄÚ¿ı Û
(ºI§àï§RÅ"TRA
ÄÂÚ
(§H§üïÚß“ë>W“I
ÄÚ@ı Û«w˜˜ÛoæAªa!ª1
ÄÂÚ¸Ä˙Ä
ÄÚ¿ıÚ˝Ù

ÄÚ@ıÚÔ

ÄÚ¿ı ÛÔ

ÄÂÚÓˇÄÚ@ı ÛÓˇÄÂŒ¿ıŒ@ıŒ¿ı ¬Œ@ı ¬Œ¿ıŒ@ıÚÓˇÒ¿ı ÛÔ

ÄÂÚÔ

ÄÚ@ı ÛÔ

ÄÂÚÔ

ÄÚ¿ıÚÔ

ÄÚ@ıÚ
IJ˛
ÄÚ¿ı Û∞é    
ÄÂÚπ&6‰9∑ùùÁàÊ‹˜à
ÄÚ@ı Û≈‚LîD®à≈"í    ¢J
ÄÂÚ≈"Dî¸Øàï>íIÚæJH
ÄÚ¿ıò@¿

˜¿

˜JGä>
Ú;øΩflòC?ÚŸàaÌà
ÄÚ@ıÚ˛˙˛
ÄÚ¿ı Û˛8Û

ÄÂÚÔ

ÄÚ@ı ÛÔ

ÄÂÚÓˇÄÚ¿ıÚÔ

ÄÚ@ıÚÔ

ÄÚ¿ı ÛÔ

ÄÂÚ∞ÔÄ˚
¸˛

ÄÚ@ı ÛôÄÌπÔßq‡"D˛

ÄÂÚ(Δ
Dî
Xò√ß"p˛

ÄÚ¿ıÚ∫$Åı|îÅ_Ü4£"@˛

ÄÚ@ıÚoœÄb€S=„fi`‡˛

ÄÚ¿ı Ûˆ˚

ÄÂÚˆ˚

ÄÚ@ı ÛÔ

ÄÂÚ˛
˛¿˛@¸

ÄÚ¿ıÚ¿pOÄ¿¸

ÄÚ@ıÚÎd∞fl ÌúD∂Áº@¸

ÄÚ¿ı ÛUGë4°"FPA¸

ÄÂÚUDë•ı>DïÚR@¸

ÄÚ@ı Û‘鸲¸bˇàgmÒ˛ 
ÄÂÚÄÙ

ÄÚ¿ıÚćÙ

ÄÚ@ıÚÔ

ÄÚ¿ı  Û˛
˛¿˛@¸
ĈˇÛ!Ú¿pOƸ
ÄĘ@ı! ÛÎd∞fl ÌúD∂Áº ¸
ÄĘÛ!ÚUGë4°"FPA¸
ÄĘ¿ı!ÚUDë•ı>DïÚRê¸
ÄĘ@ı#Ú‘鸲¸bˇàglÒ˛ 
ÄĘ¿ı  ÛÄÙ
ÄÄ
x
˛Û ÚćÙ
ÄÄÄ(
@ò˛@ı ÛÔ
ü˛¿Ä+ù0D≥πõ9éÿÛÚÔ
ê`Ä:Sxz˙Qoß”¿ı"Úø˘üùˆ
ê0ÄFS@CBQl¶S@ı"Ú’$•
 êˆ
ê0ÄGù8z:IK•Œ¿ı ÛëÊ8™¿ˆ
ê`Ä˚ÛÚë$®ÚDêˆ
ü˛¿Ä˚@ı Û;øÊü˘ˆ
ÄÄĘÛÚÔ
ÄĘ¿ıÚÔ
ÄĘ@ıÚÔ
ÄĘ¿ı Û¯˝˛AÄĘÛ!Ú3Ô˝¿AĈˇ¯@ı# Û$ÏÁ∏sçÔ‚vÁº#∂wû!ʡ¯ÛÚ)á1ƒΔîâP$TäH!ÄÚ¿ıÚ9$!|1úîâÚUÚR'‘˙I!ÄÚ@ıÚoÓxÁôÔ6Á>g»gl!à7f!ÄÚ¿ı Û˘Ñ¸˛
AÄÂÚ˙

Œ¯

ÄÚ@ı ÛÔ

ÄÂÚÔ

ÄÚ¿ıÚÓˇÄÚ@ıÚÓˇÄÚ¿ı ¬Œ@ı ¬Œ¿ıŒ@ıŒ¿ı ¬Œ@ıò@

@
˜

@
˜äG >
 ¬Œ¿ıŒ@ıŒ¿ı ¬Œ@ı ¬Œ¿ıœU@ıœÃ¿ı¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡


»

    »

»
(»
êËr|»
ëÇ»
˛8»¡¡¡¡¡'¿`Äà
IJ ˛‡
˛˛ Â$Äêr@IJÄ˚à˛˛ Â'#OEê@0Ã≥ÖY;≠ºƒ
ã`àçbflp]-Â'#R (p$@1UzãR’¢™ƒ&»+DU°    W&•jÄ•V†Â'#íZp$@J#ìR$ô§«;ƒ»JD
y!
adÆLq…‰¿Â'#Ãt@à$ÄäÓ%úÃ=;    E\È∞|Δ4¢a≠…û
â‡Â'#ú\8ps
ùŸú)-ÜB#˜IpTÅ√C·iGy@²"˙ "˝à⁄˛"˙ "˝à⁄˛˙ ˝p⁄¡¡(}†@8˛DÅD@
¿|Ê&)ä
ƒ¸@

@@Ä$Ê)%)L∑+-)#/E±µµë≤2‰õ
o≠ã‰[Ĭîê#•æpÁ)%1T“T^ı%RJ—
Zö≤“UEM5ïïD≠    @«z®8™‘ÄÁ)%—dî‰î¶HîíëRíñîâäI&§∏â)A"SpA<òpÁ)%bD    6à˘Kkˆ’0é§$6øŒìO%,ÎÕSÇ$•¿EQ<Á)%sNç$x¶2D§â q%%$JâFJ"6¥àís8¯è(‡Á˝
˛
@ıĢ
 ‚˝
˛
@ıĢ
 ‚ò@
@
Ä
˜
@
Ä
˜ G
>
˘
@Ï
 ‚¡¡DÄÑ06
0ÿ @˝"$I
ÿ(ø≤‰[úêd]«TrÅ+∏r%Ÿ    9BED≠•@©+™
T•    'u@•^Ä⁄
K<Iâ)Å˛˝1¬ô.–¶9.‰Ä⁄nèÕSíHíXB≠h!À    hâŸKtäàí=–Á9ìÉI∑6<Á2q∑vŸı˙@Ÿı˙@Ÿı˙@Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡
‡Õ
Õ§Ñ÷R8¨fŒ;’DjÓQP™ŒíõÑ    JJ„ê0Œ•.:êì≤ "vŒÿ…¡ƒîb·‚2HÄœ˛!˝ÄÃ˛!˝ÄÃ
˛!˝Ä ¡¡˛–¯
–ÇÄ@ê
–óâ±÷»í?Ÿy,—*J“ìTña"íê—L
&Rî¢d"fi$§ê—~    )ï5¥Ë    ≥áGµ —Tìâ&‰êç"˙E" —
¸@
À
¸@
À¸
Ä»¡¡    @¿¿À     @
! À    (ø≤‚∞" À        9BEE@‚ À
K<Iâ@ À    nè Å@À    KtäÑÄÂÄÀ¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜
GJ>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜JG|>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜|Gº>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜ºG¸>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜¸G<>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜<G|>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜|Gº>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜ºG¸>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜¸G<>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜<Gn>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜|Gº>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜ºG¸>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜¸G<>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜<G|>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜|Gº>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜ºG¸>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜¸G<>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜<Gn>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇP÷@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-22    )BResponding to Ü)<Apple Events4^*¿
¯
°dONLNd\lh(elThe ,
Courierª¿°dONLNd\hÒ)AEProcessAppleEvent¥†°dONLNd\Òh
!)r function fiœ†°dONLNd#\
!h
N)0rst identifiò@°dONLNd/\
Oh
j).es the ‡°dONLNd6\
kh
Û)Apple event by examining the °dONLNdSilu
F(rl3data in the event class and event ID attributes. Th‡°dONLNdÜi
Gu
Q)€e f≤`°dONLNdâi
Qu
Á)
$unction then uses that data to call °dONLNd≠vlÇ|(lthe °dONLNd±v|Ç
C),Apple event handler that your application pr`°dONLNd›v
CÇ
∂)«ovides for that event. The b†°dONLNd¯v
∂Ç
Ó)sApple event °dONLNd
Élè
(ål&handler extracts the pertinent data frf@°dONLNd
*É
è
/)¢om the .¿°dONLNd
1É
/è
©)!Apple event, performs the rß@°dONLNd
LÉ
©è
Ú)zequested action, °dONLNd
]êlúÉ(ôland r≤ °dONLNd
bêÉú≠)
eturns a rã@°dONLNd
lê≠ú
ì)*7esult. For example, if the event has an event class of Â@°dONLNd
£ê
ìú
Ì)ÊkCoreEventClassfl†°dONLNd
≤ê
Ìú
Ô)Z
 °dONLNd
≥ùl©¿(¶land an event ID of ‡°dONLNd
Δù¿©
 )TkAEOpenDocuments͇°dONLNd
÷ù
 ©
5)`, the H@°dONLNd
‹ù
6©
®)AEProcessAppleEventA °dONLNd
Ôù
®©
Ë)r function calls °dONLNd
ˇ™l∂
n(≥l8your application’s handler for the Open Documents event.î¿°dONLNd7™
n∂
p(≥
n
 °dONLNd9ºl»É(≈lBeforÛ¿°dONLNd>ºÉ»
>)+e your application attempts to accept or prl@°dONLNdiº
?»
k)º
ocess any ó¿°dONLNdsº
k»
Ì),Apple events, it must use the °dONLNdë…l’Í(“lAEInstallEventHandlerx °dONLNd¶…Í’
<)~ function to install È¿°dONLNdª…
<’
›)R$Apple event handlers. This function °dONLNdfl÷l‚œ(fllinstalls handlers in an 
Ú °dONLNd˜÷œ‚
K)cApple event dispatch table ‚Ä°dONLNd÷
L‚
π)}for your application; the R¿°dONLNd,÷
∫‚
Ù)nApple Event °dONLNd8„lÔ¯(ÏlManager uses this table to map AÄ°dONLNdW„¯Ô
˜)å8Apple events to handlers in your application. When your °dONLNdèl¸q(˘l
a°dONLNdêq¸π)pplication calls t˜@°dONLNd¢π¸Δ)Hhe @°dONLNd•«¸
9)AEProcessAppleEvent °dONLNd∏
9¸
x)r function to pr`°dONLNd«
x¸
û)?    ocess an ¥¿°dONLNd–
û¸
È)&Apple event, the °dONLNd·˝l
    …(
lApple Event Manage<@°dONLNdÛ˝ 
    Û)^
r checks t∏‡°dONLNd˝˝Û
    
))he uÄ°dONLNd˝

    
Ù)8Apple event dispatch table and, if your application has °dONLNd8

l
„(
linstalled a handler for that  °dONLNdU

‰

.)xApple event, call뇰dONLNdf


.

N)Js that hˆ`°dONLNdn


N

f) andleïÄ°dONLNds


g

j)
r ¿°dONLNdt


j

l)
.J¿°dONLNdu


m

o)
  ¿°dONLNdv


o

á)FigurùÄ°dONLNd{


á

õ)e 3-1Æ`°dONLNdÄ


õ

†)
1Æ`°dONLNdÅ


†

Á) shows how the °dONLNdê
l
#r(
 l
flå¿°dONLNdí
r
#§)ow of contr· °dONLNdù
§
#’)2ol passes fr⁄†°dONLNd©
’
#
M)1om your application to the ê@°dONLNdƒ

M
#
Ê)x Apple Event Manager and back to °dONLNd‰
$l
0∑(
-lyour application.


R*
c
¯4
S*
c
¯"
S*]

ˇ·ˇ‚7^
    °dONLNdˆ
Hl
Sú*#Figure 3-11°dONLNd
HÆ
S¿)BThe ê°dONLNd
H¿
S
‹)CApple Event Manager calling the handler for an Open Documents event


bgÇ
¯4
chÅ
¯


ckÇ
¯4
bj
ckò@@
˜@
˜
ck
£b¡¡?”ˇ¸Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?˘ˇ˛˝·ˇ˛Ò?˘ˇ˛˝·ˇ˛Ò?˘ˇ
˛˛·ˇ˛Ò?˘ˇ
˛˛·ˇ˛Ò?˘ˇ˛ Ä·ˇ˛Ò?˘ˇ˛ @·ˇ˛Ò?˘ˇ˛!Á¯·ˇ˛Ò?˘ˇ˛¯·ˇ˛Ò?˘ˇ˛¿Ä·ˇ˛Ò?˘ˇ˛Ç`·ˇ˛Ò?˘ˇ˛
ê·ˇ˛Ò?˘ˇ˛·ˇ˛Ò?˘ˇ˛
‰·ˇ˛Ò?˘ˇ˛!R·ˇ˛Ò?˘ˇ˛"©·ˇ˛Ò?˘ˇ˛DQ·ˇ˛Ò?˘ˇ˛ Ñ)·ˇ˛Ò?˘ˇ˛ à4·ˇ˛Ò?˘ˇ˛!"·ˇ˛Ò?˘ˇ˛!Q·ˇ˛Ò?˘ˇ˛"hÄ·ˇ˛Ò?˘ˇ˛‘@·ˇ˛Ò?˘ˇ˛ ™ ·ˇ˛Ò?˘ˇ˛ ï·ˇ˛Ò?˘ˇ˛ äà·ˇ˛Ò?˘ˇ˛ ÖD·ˇ˛Ò?˘ˇ˛
 Ƕ·ˇ˛Ò?˘ˇ˛êAY·ˇ˛Ò?˘ˇ˛P@π·ˇ˛Ò?˘ˇ˛0 a·ˇ˛Ò?˘ˇ˛#·ˇ˛Ò?˘ˇ˛ ·ˇ˛Ò?˘ˇ˛@·ˇ˛Ò?˘ˇ˛Ä·ˇ˛Òò@@Ä
˜@Ä
˜
£k
„b?˘ˇ˛˝·ˇ˛Ò?˘ˇ˛˝·ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Òò@Ä¿
˜Ä¿
˜
„k#b?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Òò@¿

˜¿

˜#kcb?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Òò@

@
˜

@
˜ck£b?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò?”ˇ˛Ò”ˇ˛Ò¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡
¯p‡»    H 9«
@     ¿»
p  »
$áCê »
DàD@»
œ¯9Ä»¡¡¡¡¡1~Ñ– 
¿|`˝?Äà
¯`˛
˛1$Éú    P Ä$†˝à
PÄ1˛
˛2."z,ÄÄÑ
@bîê#•æ¬ÿæVR∂yÀ!e±—Y ¡l@®∂Fé±oú.ñ¯2.2ñQCņgz®8™‘Eid®*íöêçQ™“í†ï¥@ıZ´ìRµ R´P2.Dí”Äy¿íSpA<òIJe»D•ë    ·2îß •§@ßí%0≤W&‰Ú`2.Üc¢A
•¿EQ<$OõŸ_∑¶aãÅ5¥A*ÃcJ&-V‰ÑOÖD2.ƒ‚·√Éú$„;8¯è(4Íí∏%%$·rU&„¡H1‰6ॣ 8r<†ò@
@
Ä
˜
@
Ä
˜£k„b
˙
 ˙D˛

¸
˝@Ê
˙
 ˙D˛

¸˝@Ê˛‡˙
 ˙8˝‡¸˝@Ê¡¡(cË08
¿˛ 0 @‡ Ê'LP ˝@
  Ê)%1J`πYiIz-à≠¨çëó$ÿ}ht_"ÿ‰§Å-ÛÄÁ($)ä†&í¢˜©*íVà
‘’ñí™*h®î¨™%hJ;’A≈V§Ê)%Fã $ß$•2D§îàîLRH0•%ƒIHí    õÇ    ‰√ÄÁ)%C I¥G [_∂©Ñu! ȵ˛tò"y)g^jò‘%.*â‡ÄÁ($„öti#≈1í%$Iâ)(π"THí2Qµ§Dêà3ò…«ƒyGÊ˝˛Bı¯!·˝˛Bı¯!·
˘BÎ!·¡¡Ä ¿@!Ä√
Äÿ)˝    % @Ä
$∏Äÿ)E˝ó"ÿt‰Å&*Ó:£ê–$â]√ë(ŸI *%hÖ*:=P
•(pG™*ÙŸRY‚LIHx\ )é…p@â1…w$Ÿõpt~jòê R¬k@a    XKDHŸ“[§TDêÈÓá1åúMπ±Ê9ìçª∞Ÿı˚˛@Ÿı˚˛@Ÿı˚˛@Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡p˛ćÕ ÄÄ@Õ•$ ≤ë≈`[0Œfi™ +WräÄçPŒ$î‹ JRWÄâÄŒE)p‘Ñùë
∞ŒŒΔN$£íDŒ
˛ Ã
˛ Ã
˛…¡¡xxÄ
‰¿8‡@÷$$
@Ä
@@÷$∏DO-é∂BDÂì¨ê
Hæ≤‰∑◊)PX≤Vîö¢E
2’PYDEJH◊B`Q2î•"àÚó†ã8IíG◊CIL©≠ßDå>"0&Œè‘Å◊‚†‰úI7$Ö˘‘;ï)‚4ãxäàé◊¸"˛˛—¸"˛˛(—
¸˙0œ¡ò@
Ä
¿
˜
Ä
¿
˜„k#b¡Ä )         )E˝óÅ I ** RY‚LJë õpt~Tí “[§T$, ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜#kUb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜
ck
£b
¡¡“30Ò“Ò ”Ò“Ò“Ò“Ò ”Ò“Ò ”Ò“Ò“Ò˜

¿fiÒ ¯
 fiÒ˜
åÂò‡Ò ˜~ó–‡Ò˜0ö‡Ò˜
Œë–‡Ò“Ò ”Ò“Ò ˜
 ‡Òˆ@‡Ò¯
ù Ãʇ·Ò¯”+>iê·Ò ˘S+iê·Ò¯
› Ó&ê·Ò ¯›Ò
˜›Ò“Ò“Ò ¯›Ò
˜›Ò ¯
 ÄfiÒ˜
 @fiÒ˜!Á¯flÒ˜¯flÒ ¯¿ćÒ˜Ç`‡Ò ¯
ê‡Ò˜‡Ò˜
‰‡Ò˜!R‡Ò ¯"©‡Ò˜DQ‡Ò ¯ Ñ)‡Ò˜ à4‡Ò˜!"‡Ò˜!Q‡Ò ¯"hćÒ˜‘@‡Ò ¯ ™ ˜Ïˇ
‡Ò˜ ï˜Ï
0Ò˜ äà˜Ï
0Ò˜ ÖD˜Ï
0Ò ¯
 Ƕ˜Ï
0ÒˆêAY˜Ï
0Ò ˜P@π˜˚  ˘
0Òˆ0 a˜˚PÄ&`˘
0Òˆ#˜˚    W:`ânvf„9∞¸
0Òˆ ˜˚    t¶ı˘%ØóÀ‡¸
0Ò ˜
@ˆ˚    å¶ÄÜâ%©î  ¸
0Òˆ
Ĉ˚    è:pÙy'ìπ‡¸
0Òò@@Ä
˜@Ä
˜
£k
„b
 Í˚
 ˚˚
0ÒÈ˚
 ˚p˚
0ÒÈÏ
0ÒÈÏ
0Ò ÍÏ
0Ò˜8
í ˜Ï
0Ò ¯Dí˜Ïˇ
Ò˜2_´Ø∞¯Ïˇ
Ò˜R≠'‡·Ò˜FRm& ·Ò ¯9“E#‡·Ò“Ò ”Ò“Ò“Ò“Ò ”Ò“Ò ”Ò“Ò“Ò“Ò ”Ò“Ò ”Ò“Ò“ÒÔˇ˛ËÒ ÔËÒ˘¸ ˛B˛?Ôˇ¸Ò# 3Ô˝¯
 B˛ ÔÒ$$õ„‹8Êy‚Nn{¿G3wû"ˇ ÔÒ$%ábaâ$í"bQ%HíäH"≈‡ ÔÒ3=$    >o$í>Jü%Oî˙H"à∏ ˛@˛@˛Ò3 gÓ„ÃqŸ∏Ôå˘v‡C7g"Ä ˛
@@B˛Ò-˙
 ĸ ˛Bë ˛
ÁLY‹y˘üp˚ì˛Ò) ˙
q¿¯˛& ˛îfi=}(õ'û~WÄÒ$ÔÇ ˛î–!°(òÊLHfT˛Ò$Ô« ˛ÁN${π«»?ìÄÒÔI ˝Ñ¸ ˙Ò Ôa ˝Ñ¸ ˙ÒÔˇ˛1 ÔÒ Î# ÔÒÍ! ¿˘H0˛ÒÍ% Ä˚H0˛ÒÍ) %π¿˚    y∏Û`Ò Î! ◊‰Ä˚    KÂ7¿ÒÍ1 $Ä˚    Je4@Ò Î# —‰@˚    I‰Û¿ÒÍ! ÔÒÍ% ÔÒÍ) ÔÒ Î!?Ôˇ¸ÒÍ1 ˘¯Ò Î# ˘
˛
0˛ÒÍ! ‡˝    åÄ
xÒÍ% !ê˛€iœ»•«ÑÒÍ) !Êpìt7?©O91(¶(ÑÒ  Î! !üHî¶j|úâII3˶(¸ÒÍ1 !òHî¢jDì‹ùøΩ¸«y«ÑÒ Î# ÁH„Í<éÄ˚ÒÍ! Ä˚Ä˚ÒÍ% Ä˚¯ÒÍ) ˘¯Òò@Ä¿
˜Ä¿
˜
„k#b
 Î!?Ôˇ¸ÒÍ1 ˘¯Ò Î# ˘
˛
0˛ÒÍ! @¸    åÄ
xÒÍ% DÄ
€iœƒ•«ÑÒÍ) ‹‰ô•£;∏©O91'&(ÑÒ  Î! RD¶eW•`âII3‰&(ÒÍ1 RD¶%T%‹ùøΩ¸Œy«ÑÒ Î# R'›S§Ä˚ÒÍ! ˘Ä˚ÒÍ% ˘¯ÒÍ) ˘¯Ò Î!?Ôˇ¸ÒÍ1 ˘¯Ò Î# ˘¯ÒÍ! ˘¯ÒÍ% ˘¯ÒÍ) ˘¯Ò Î! ˘¯ÒÍ1 ˘¯Ò Î# ˘¯ÒÍ! ˘¯ÒÍ% ˘¯ÒÍ) ˘¯Ò Î!?Ôˇ¸ÒÍ1 ˘¯Ò Î# ˘¯ÒÍ! ˘¯ÒÍ% ˘¯ÒÍ) ˘¯Ò Î! ˘¯ÒÍ1 ˘¯Ò Î# ˘¯ÒÍ! ˘¯ÒÍ% ˘¯ÒÍ) ˘¯Ò Î!?Ôˇ¸ÒÍ1ÏÒ Î#ÏÒÍ!ÏÒÍ%ÏÒÍ)ÏÒ Î!Òˇ˛ÒÍ1ÒÒ Î#ÄêÒÒÍ ¿–˘˙ÒÍ4p¿˛
˛ÒÍü∞%-∏˜s=‚ñ›ÁÄÒ  Î1ΔE∞≈í"¬¢í˛ÒÍ%Eå7í>íæí@Ò  Î",ˇè8ÛyÌúÔçÒŸÄÒÍ
¿˙
Ä˙ÒÈ
˙
9¿˙ÒËÒÒ È–ÒÒËÒÒ ÈÒˇ˛ÒËÒÒÔˇ˛˛ÒÒÔ˛ÒÒ Ô@ÒÄÒÔ¿Ò?ÄÒ/ ˝ÿ˝Ä˝
˛ˇ–
 (@p˝ˇÄÒ3c¿HºÄ
¯
˛P2
 (Ä!H˛ˇˇ¸Òò@¿

˜¿

˜#kcb
37¥â„»‰Rs¡ÒºÒNŒÛƒ˛DP j9úȱÛ!s8IöZªÇÄÒ3*ßúîIRåAJíIbëI˛à–8 ˙'”+‡ !O§JfU>V
ÄÒ2 "§§î…ÙRå
$KíIJüI$˛P"ö&S*  !L$JbU"QÇ˝Ò2*wNfl€~cºs¡Ó‹wΔ˘σˇˇ–z%“ȇ≤s§qù’O˝Ò$ @˙Ä@˝¿¯@˚˝Ò!
¿¯
8‡¸¿¯@˚˝ÒÔ@Ò˝ÒÔ˛Ò˝Ò Ôˇ˛˛˛ı˝ÒÔ˛Y‹ı˝Ò Ô˛=}(ı˝ÒÔ˛!°(ı˝Ò#ÄB¯˛$ı˝Ò#
Dz¸˛Ò˝Ò$ ü±∫üôŒΔùœ¿˝˛Ò˝Ò#ezR±$ì)öü'¸˛Ò˝Ò$ eJç$ì(öë$¿˝˛Ò˝Ò$ì9 ∏òé«zè#Ä˝˛Ò˝ÒÔ˛Ò˝ÒÔ˛Ò˝Ò Ô˛Ò˝Ò†ı˛Ò˝Ò! ÄÄ
˙˛Ò˝Ò"mπç‹Ã⁄Ê˚˛Òˇ˛˝ÒöÑ≥“ìÈı=Ù˚ËÒöÑ≤ì)5!Ñ˚ËÒ jɱŒ\ËıÙ˚ËÒ˙˜ËÒ ˙˜ËÒÔËÒ˛

˝ ¸ËÒ
Ä
˛˚ËÒ Ò∏3á3KFw<˝ËÒÀ‰¶IL ØJ2<˝ËÒ  $D¢ILJ®J2$˝ËÒq‰;ûG3∫ßI2˝ËÒ˛@ÛËÒ˛@ÛËÒ ÔËÒ˛
@ ÙËÒ ˝ ÙËÒ‹ÏîıËÒ”2¥ıËÒS2hıËÒ     RÏHıËÒÔËÒ ÔËÒÔËÒ


˛˝ËÒ
    ˛˝ËÒ     7-«.ogè73ú˝ËÒ{)#)ïîìŸ2zd˝ËÒ     C)#)Öîí2Jd˝ËÒ    9È"Èsdë‹Ò:\IJËÒÛIJËÒÛIJËÒ ÔËÒ˛¸ ¸ËÒ ˝˛˚ËÒ3π≥¥fl
ûl?Æp˝ËÒzeJeÔÉ‘òc)ê˝ËÒJeJe,ò)ê˝ËÒ ;π3§Áë‘hq)p˝ËÒ˛ ˝˝ËÒò@

@
˜

@
˜ck£b
 ˛ ˝‡˝ËÒÔËÒÔËÒÔËÒ Ôˇ˛ËÒ“Ò ”Ò“Ò“Ò“Ò ”Ò“Ò ”Ò“Ò“Ò“Ò ”Ò“Ò ”Ò“Ò“Ò“Ò ”Ò“Ò ”Ò“Ò”UTÒ“ÃÒ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡
¯p‡»    H 9«
@     ¿»
p  »
$áCê »
DàD@»
œ¯9Ä»¡¡¡¡¡1~Ñ– 
¿|`˝?Äà
¯`˛
˛1$Éú    P Ä$†˝à
PÄ1˛
˛2."z,ÄÄÑ
@bîê#•æ¬ÿæVR∂yÀ!e±—Y ¡l@®∂Fé±oú.ñ¯2.2ñQCņgz®8™‘Eid®*íöêçQ™“í†ï¥@ıZ´ìRµ R´P2.Dí”Äy¿íSpA<òIJe»D•ë    ·2îß •§@ßí%0≤W&‰Ú`2.Üc¢A
•¿EQ<$OõŸ_∑¶aãÅ5¥A*ÃcJ&-V‰ÑOÖD2.ƒ‚·√Éú$„;8¯è(4Íí∏%%$·rU&„¡H1‰6ॣ 8r<†ò@
@
Ä
˜
@
Ä
˜£k„b

˙
 ˙D˛

¸
˝@Ê
˙
 ˙D˛

¸˝@Ê˛‡˙
 ˙8˝‡¸˝@Ê¡¡(cË08
¿˛ 0 @‡ Ê'LP ˝@
  Ê)%1J`πYiIz-à≠¨çëó$ÿ}ht_"ÿ‰§Å-ÛÄÁ($)ä†&í¢˜©*íVà
‘’ñí™*h®î¨™%hJ;’A≈V§Ê)%Fã $ß$•2D§îàîLRH0•%ƒIHí    õÇ    ‰√ÄÁ)%C I¥G [_∂©Ñu! ȵ˛tò"y)g^jò‘%.*â‡ÄÁ($„öti#≈1í%$Iâ)(π"THí2Qµ§Dêà3ò…«ƒyGÊ˝˛Bı¯!·˝˛Bı¯!·
˘BÎ!·¡¡Ä ¿@!Ä√
Äÿ)˝    % @Ä
$∏Äÿ)E˝ó"ÿt‰Å&*Ó:£ê–$â]√ë(ŸI *%hÖ*:=P
•(pG™*ÙŸRY‚LIHx\ )é…p@â1…w$Ÿõpt~jòê R¬k@a    XKDHŸ“[§TDêÈÓá1åúMπ±Ê9ìçª∞Ÿı˚˛@Ÿı˚˛@Ÿı˚˛@Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡p˛ćÕ ÄÄ@Õ•$ ≤ë≈`[0Œfi™ +WräÄçPŒ$î‹ JRWÄâÄŒE)p‘Ñùë
∞ŒŒΔN$£íDŒ
˛ Ã
˛ Ã
˛…¡¡xxÄ
‰¿8‡@÷$$
@Ä
@@÷$∏DO-é∂BDÂì¨ê
Hæ≤‰∑◊)PX≤Vîö¢E
2’PYDEJH◊B`Q2î•"àÚó†ã8IíG◊CIL©≠ßDå>"0&Œè‘Å◊‚†‰úI7$Ö˘‘;ï)‚4ãxäàé◊¸"˛˛—¸"˛˛(—
¸˙0œ¡ò@
Ä
¿
˜
Ä
¿
˜„k#b
¡Ä )         )E˝óÅ I ** RY‚LJë õpt~Tí “[§T$, ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜#kUb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜Ukïb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜ïk’b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜’kb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜kUb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜Ukïb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜ïk’b¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜’kb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜kGb¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜Ukïb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜ïk’b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜’kb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜kUb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜Ukïb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜ïk’b
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜’kb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜kGb
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ=ò@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äResponding to Ü)<Apple Events

, (‡3-23
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

kHr4lHr mäm

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\äk±(gäAbout [T°dONLNd\±k
5)'Apple Event Handlersˇˇˇˇˇˇ€r(g
3
°dONLNdrä~ê({ä
Y@Ä°dONLNdrê~°)our —`°dONLNd!r°~
ƒ)@Apple event handlers must generally perform the following tasks:,Zapf Dingbats°dONLNdbàäèè(éä
n
°dONLNddÖñë
)extract the parameters anV†°dONLNd}Ö
ë
)pd aÚ`°dONLNdÄÖ
ë
3)ttributeχ°dONLNdàÖ
4ë
B)!s fr¬¿°dONLNdåÖ
Bë
V)om tŒ†°dONLNdêÖ
Vë
c)he ã@°dONLNdìÖ
cë
ô)Apple event°dONLNdüöä°è(†ä
n
°dONLNd°óñ£Á)check that all the rS‡°dONLNdµóÁ£˛)Qequirk °dONLNd∫ó˛£
ó)!ed parameters have been extracted°dONLNd‹¨ä≥è(≤ä
n
°dONLNdfi©ñµ≈)locate any \@°dONLNdÈ©≈µ
:)/Apple event objects specifi"@°dONLNd
©
;µ
é)ved by object specifi‹†°dONLNd
©
éµ
ù)Ser r›‡°dONLNd
©
ùµ
Ø)ecorR@°dONLNd
 ©
∞µ
ÿ)
ds in the c¿°dONLNd
*©
ÿµ)(Apple event °dONLNd
6µñ¡«(æñ
parameters°dONLNd
A ä—è(–ä
n
°dONLNd
C«ñ”
p)3if your application needs to interact with the user≈@°dONLNd
v«
o”
ï)Ÿ
, use the ,
Courier∞`°dONLNd
Ä«
ñ”)'AEInteractWithUser©†°dONLNd
í«”)l
 °dONLNd
ì”ñfl
(‹ñfunction to bring it to the forW†°dONLNd
≤”
fl
")~egru`°dONLNd
µ”
"fl
9)ound°dONLNd
∫ËäÔè(Óä
n
°dONLNd
ºÂñÒÓ)perform the action r“†°dONLNd
–ÂÓÒ
6)Xequested by the Ć°dONLNd
‡Â
6Ò
l)HApple event°dONLNd
Ï˙ä

è(
ä
n
°dONLNd
Ó˜ñ

5)%dispose of any copies of descriptor rË¿°dONLNd˜
5

G)üecor] °dONLNd˜
H

†)ds that have been crn¿°dONLNd+˜
†

∑)Xeated°dONLNd1
ä
è(
ä
n
°dONLNd3
    ñ

)add information to the rÕ °dONLNdK
    


)jeply 2°dONLNdP
    


[)Apple event if r~°dONLNd`
    
[

Ç)Eequested°dONLNdi
ä
&
U(
#ä.This section describes how your application’s t‡°dONLNdó

U
&
⁄)ÀApple event handlers can use °dONLNd¥
'ä
3ó(
0äthe]`°dONLNd∑
'ò
3ö)
 °dONLNd∏
'ö
3µ)Apple¸Ä°dONLNdΩ
'µ
3∑)
 |Ä°dONLNdæ
'∏
3
Œ)=Event Manager to accomplish some of these tasks. The chapter °dONLNd˚
4ä
@ƒ(
=ä“Responding‚@°dONLNd
4ƒ
@Δ):
 b@°dONLNd
4«
@œ)to °dONLNd    
4–
@“)    
 ;¿°dONLNd

4“
@
U)Apple Events” in this book pr—`°dONLNd'
4
U
@
“)Éovides detailed information °dONLNdC
Aä
M£(
JäaboutΔ†°dONLNdH
A£
M•)
 F†°dONLNdI
A¶
M–)    handling X°dONLNdR
A–
M
å)**Apple events and interacting with the usert@°dONLNd|
A
å
M
é)º
.


kH
r4
lH
r 
mä
m

ˇ·ˇ‚7^°dONLNd~
^ä
l¬(
häExtracting ,¿°dONLNdâ
^√
l
)9and Checking Dá@°dONLNdó
^

l
")UatàÄ°dONLNdô
^
"
l
()

aˇˇˇˇˇˇ‘@)Ì
3
°dONLNdú
rä
~ê(
{ä
Y@Ä°dONLNdù
rê
~»)ou must use G°dONLNd©
r»
~
±)84Apple Event Manager functions to extract the data fr'@°dONLNd›
r
±
~
¡)Èom í`°dONLNd‡
r
¡
~
˜)Apple event› °dONLNdÎ
r
˜
~
˝)6s.ö °dONLNdÌ
r
˛
~)
 °dONLNdÓ
ä
ãê(
àä
Y@Ä°dONLNdÔ
ê
ãõ)ouΩ °dONLNdÒ
õ
ãù)
 = °dONLNdÚ
û
ã’)can also use I°dONLNdˇ
’
ã
h)7Apple Event Manager functions tÖÄ°dONLNd

h
ã
ñ)ìo extract d†°dONLNd)

ñ
ã
û).at3°dONLNd+

ü
ã
≠)    a frÀ‡°dONLNd/

≠
ã
√)om d± °dONLNd3

ƒ
ã
Ò)escriptor rÙ†°dONLNd>

Ò
ã)-ecori°dONLNdB

ã)ds, °dONLNdF
åä
ò„(
ïädescriptor lists, and ∂ °dONLNd\
å„
ò˜)YAE rfi °dONLNd`
å˜
ò
    )ecorRÄ°dONLNdd
å


ò
Z)ds. Most of these r¿°dONLNdw
å
[
ò
Ü)Q
outines arà °dONLNdÅ
å
Ü
ò
)+e available in two forms‹°dONLNdô
å

ò
)j: they °dONLNd†
ôä
•©(
¢äeither rG°dONLNd®
ô™
•Ú) eturn a copy of t†‡°dONLNdπ
ôÚ
•
)Hhe dat°dONLNdø
ô

•
7)
a in a buf¿°dONLNd…
ô
7
•
U))fer or rF°dONLNd—
ô
U
•
fi) eturn a copy of the descriptor r °dONLNdÒ
ô
fi
•
)âecoréÄ°dONLNdı
ô

•)d for °dONLNd˚
¶ä
≤
3(
Øä(the data, including a copy of the data. °dONLNd$
∏ä
Đ*
T†¿°dONLNd%
∏ê
ƒ
Ï)Phe following list shows the main functions you can use to access the data of an °dONLNdu
Ŋ
—•(
ŒäApple˝Ä°dONLNdz
ť
—ß)
 }Ä°dONLNd{
≈®
—Ω)evenà`°dONLNd
≈Ω
—¬)t:
    °dONLNdÇ
fiä
ÈØ(
ÊäFunction°dONLNdã
fi


È
;)ÄDescriptionÕ`°dONLNdˇˇ)1
 
°dONLNd£
Ïä
¯ÿ(
ıäAEGetParamPtr°dONLNd±
Ï


¯
7)Ä
Uses a buf?‡°dONLNdª
Ï
8
¯
U).fer to rÇ°dONLNd√
Ï
U
¯
o)eturn $°dONLNd…
Ï
p
¯
û)a copy of t&¿°dONLNd‘
Ï
û
¯).he data contained in an °dONLNdÏ
˜


p(

Apple event parameter`°dONLNd

˜
p
ô)f
. Usually     †°dONLNd
˜
ö
†)*
u¿°dONLNd
˜
†)sed to extract data of fiy °dONLNd%
˜)dxed °dONLNd)

(

8length or known maximum length; for example, to extract °dONLNda


*the r¢`°dONLNdf

T)esult code fr懰dONLNds
T
u)6om the ¿°dONLNdz
u
…)!keyErrorNumber‡Ä°dONLNdà
…)T parameter of a °dONLNdò

$
(!


rE°dONLNdô
$
#)eply ©‡°dONLNdû
#$
[)Apple event.°dONLNd¨(ä4fi(1äAEGetParamDesc°dONLNdª(

4
()ÄReturn °dONLNd¡(
)4
Z)s a copy of ÇÄ°dONLNdÕ(
Z4
ù)1the descriptor r? °dONLNd›(
û4
∞)Decor≥Ä°dONLNd·(
∞4)d or descriptor list for °dONLNd˙3

?
(<

an s°dONLNd˝3
?
})Apple event parameter`°dONLNd3
}?)f". Usually used to extract data of °dONLNd4>

J(G

Avariable length; for example, to extract the descriptor list for °dONLNduI

U
G*a list of alias rl@°dONLNdÜI
GU
Y)=ecor‡†°dONLNdäI
YU
Ç)    ds specifi'Ä°dONLNdîI
ÉU
∏)*ed in the dirÌ °dONLNd°I
∏U)5ect parameter of the °dONLNd∂T

`
t(]

Open Documents event.°dONLNdÕdäp(mäAEGetAttributePtr°dONLNdfld

p
7)Ä
Uses a buf?‡°dONLNdÈd
8p
U).fer to rÇ°dONLNdÒd
Up
o)eturn $°dONLNd˜d
pp
ö)
a copy of ‰`°dONLNd
d
öp)*the data contained in an °dONLNdo

{
Ÿ(x

0Apple event attribute. Used to extract data of fit‡°dONLNdKo
⁄{)–xed length or °dONLNdYz

Ü
(É

4known maximum length; for example, to determine the °dONLNdçÖ

ë
*sour˛†°dONLNdëÖ
ë
A)    ce of an Ù‡°dONLNdöÖ
Aë
„)$%Apple event by extracting the data frMÄ°dONLNdøÖ
‰ë)£om the °dONLNdΔê

ú
v(ô

keyEventSourceAttry@°dONLNdÿê
vú
†)l attribute.]°dONLNdÁü
¯®+Ç    continuedˇ&@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-24    )BResponding to Ü)<Apple Events4^*¿
¯
°dONLNdˆ
`l
lr(
il
Y@Ä°dONLNd˜
`r
l
))+ou can specify the descriptor type of the rC¿°dONLNd"
`
)
l
˜)∑3esulting data for these functions; if this type is °dONLNdU
ml
yx(
vldif™`°dONLNdX
mx
yÑ)fer凰dONLNd[
mÑ
yõ)ent fr °dONLNda
mú
y
Ä)4om the descriptor type of the attribute or parameteræÄ°dONLNdï
m

y
î)„, the ΩÄ°dONLNdõ
m
î
y
Œ)Apple Event °dONLNdß
zl
Ü›(
ÉlManager attempts to coerb °dONLNdø
z›
Ü
))qce it to the specifi  °dONLNd”
z
)
Ü
x)Led type. In the dir£ °dONLNdÊ
z
x
Ü
“)Oect parameter of the °dONLNd˚
ál
ìÑ(
êlOpen˘°dONLNdˇ
áÑ
ìÜ)
 y°dONLNd
áá
ì
])/Documents event, for example, each descriptor r†°dONLNd/
á
]
ì
o)÷ecorÙ°dONLNd3
á
o
ì
È)d in the descriptor list is an °dONLNdR
îl
†Ü(
ùlalias r“¿°dONLNdY
îÜ
†ò)ecorG °dONLNd]
îô
†’)d; each alias r@‡°dONLNdl
î’
†Á)<ecorµ@°dONLNdp
îÁ
†
)d specifiø °dONLNdy
î

†
å)%es a document to be opened. ¢Ä°dONLNdï
î
å
†
‰)ÄAs explained in the °dONLNd©
°l
≠•(
™lchapter “Intry†°dONLNd∂
°•
≠
9)9 oduction to File Management” of o`°dONLNd÷
°
:
≠
ö)ïInside Macintosh: Files,∂@°dONLNdÓ
°
ö
≠
ı)` all your application °dONLNd
Æl
∫À(
∑lusually needs is the fi¯°dONLNd
ÆÀ
∫
)_le system specifi
@°dONLNd,
Æ

∫
4)Ication (,
Courier∑°dONLNd4
Æ
4
∫
X) FSSpec¥¿°dONLNd:
Æ
X
∫
a)$) rM†°dONLNd=
Æ
b
∫
t)
ecor¬°dONLNdA
Æ
t
∫
Ê)d of the document. When °dONLNdY
ªl
«fl(
ƒlyou extract the descriptor ]@°dONLNdt
ª‡
«„)t
r"@°dONLNdu
ª‰
«ˆ)ecorñ†°dONLNdy
ªˆ
«˛)d 2`°dONLNd{
ªˇ
«
)    frK@°dONLNd}
ª

«
í)!om the descriptor list, you can rn‡°dONLNdû
ª
í
«
’)åequest that the v‡°dONLNdÆ
ª
’
«
Ú)CApple °dONLNd¥
»l
‘∂(
—lEvent Manager rv`°dONLNd√
»∂
‘
f)J)eturn the data to your application as a fi?‡°dONLNdÌ
»
g
‘
Ø)±le system specifiI °dONLNd˛
»
Ø
‘
–)Hcation rp°dONLNd
»
–
‘
‚)!ecor‰`°dONLNd

»
‚
‘
Í)d °dONLNd
’l
·¡(
filinstead of an alias r°dONLNd!
’¬
·‘)VecorÄ`°dONLNd%
’‘
·‹)d.°dONLNd(
Ál
Û„(
lAfter extracting all known -@°dONLNdC
Á„
Û
Ë)w:Apple event parameters, your handler should check that it °dONLNd}
Ùlo(
˝l
rE°dONLNd~
Ùp
 ))etrieved all the parameters that the sourØÄ°dONLNdß
Ù
 
Ö)∞ce application consider' °dONLNdæ
Ù
Ü
Ø)f
ed to be rZ†°dONLNd»
Ù
Ø
Δ))equirq‡°dONLNdÕ
Ù
Δ
–)edW@°dONLNdœ
Ù
—
”)
.◊@°dONLNd–
Ù
”
’)
 W@°dONLNd—
Ù
÷
‹)
Tç°dONLNd“
Ù
€
Ò)o do °dONLNd◊
l≤(
lso, determine wD‡°dONLNdÊ
≥‚)Ghether the ç@°dONLNdÒ
‚
Z)/keyMissedKeywordAttrÖ¿°dONLNd

Z
•)x attribute exists. Iu¿°dONLNd

¶
¿)Lf so, yã@°dONLNd 

¿
ˆ)our handler °dONLNd,lí(l    has not r‹†°dONLNd5í⁄)&etrieved all the r°dONLNdG€Ú)Iequir#@°dONLNdLÚ
w)ed parameters, and it should rB†°dONLNdj
w
´)Öeturn an errl`°dONLNdv
´
¥)4or °dONLNdx
¥
∂)    
.°dONLNdz l,©()lAlthough the ˝‡°dONLNdá ©,
H)=&Apple Event Registry: Standard Suites k†°dONLNd≠ 
I,
Y)†defi]¿°dONLNd± 
Z,
k)nes W`°dONLNdµ 
k,
„)Apple event parameters as °dONLNdœ-l9ã(6leither rG°dONLNd◊-å9£) equir^@°dONLNd‹-£9ˆ)ed or optional, the |`°dONLNd-ˆ9
ô)S"Apple Event Manager does not enforı¿°dONLNd    -
ô9
Δ)£
ce the defiˇ °dONLNd    -
Δ9
Ú)-nitions of °dONLNd    (:lFo(Cl
rE°dONLNd    ):pFá)equir\@°dONLNd    .:áF
:))ed and optional events. Instead, the sour{@°dONLNd    W:
:F
ñ)≥ce application specifi⁄ °dONLNd    m:
ñF
Ù)\es, when it sends the °dONLNd    ÉGlSß(Plevent, which A@°dONLNd    êGßS
0);Apple event parameters the taræ¿°dONLNd    ÆG
0S
Y)â
get can tr¢‡°dONLNd    ∏G
YS
§))eat as if they werz@°dONLNd     G
§S
Ê)Ke optional. For °dONLNd    ⁄Tl`~(]lmoréÄ°dONLNd    ›T~`
F)-e information about optional parameters, see J°dONLNd

T
G`
˜)…'“Specifying Optional Parameters for an °dONLNd
1alm´(jlApple Event,”ú‡°dONLNd
>a´m¯)? which begins on @°dONLNd
Oa˘m
)Npage Ë °dONLNd
Ta
m
)5-7<°dONLNd
Wa
m
 )
.°dONLNd
Yslo(|l
IfiÄ°dONLNd
Zso£)f any of the €@°dONLNd
gs£
l)4,Apple event parameters include object specifi1 °dONLNd
îs
m
|) er r2`°dONLNd
òs
|
é)ecor¶¿°dONLNd
ús
é
Ÿ)ds, your handler °dONLNd
≠ÄlåÆ(âlshould use the z@°dONLNd
ºÄØåÂ)C    AEResolvev‡°dONLNd
≈ÄÂå
+)6 function, other l@°dONLNd
ր
+å
ì)FApple Event Manager r` °dONLNd
ÎÄ
ìå
„)houtines, and your °dONLNd
˝çlô»(ñlown application-defiö¿°dONLNdç»ô“)\ne5¿°dONLNdç”ô

)d functions tfl °dONLNd ç

ô
P)7o locate the corr)Ä°dONLNd1ç
Qô
Ç)G
esponding ˇ`°dONLNd;ç
Åô
Ó)0Apple event objects. For °dONLNdTöl¶~(£lmoréÄ°dONLNdWö~¶“)e information abou¿°dONLNdiö”¶˛)Ut locating U °dONLNdtö˛¶
W)+Apple event objects,≠°dONLNdàö
W¶
b)Y se3†°dONLNdãö
c¶
j)e }@°dONLNdçö
j¶
y)“Wí@°dONLNdèö
x¶
°)orking W≈¿°dONLNdóö
°¶
Î))ith Object Specifii@°dONLNd©ö
϶
˜)Ker °dONLNd¨ßl≥Ö(∞lRecor¢`°dONLNd±ßÖ≥ñ)ds,”{ °dONLNdµßó≥‰) which begins on ÎÄ°dONLNdΔ߉≥˚)Mpage Δ`°dONLNdÀ߸≥
)3-32@°dONLNdœß
≥
)
.°dONLNdvlÇÿ(lAEGetAttributeDesc°dONLNdvÏÇ

)ÄReturn °dONLNdv
Ç
<)s a copy of ÇÄ°dONLNd%v
<Ç
)1the descriptor r? °dONLNd5v
ÄÇ
í)Decor≥Ä°dONLNd9v
íÇ
‚)d for an attribute. °dONLNdMÅÏç
˘(äÏ>Used to extract data of variable length; for example, to make °dONLNdãåÏò
Q*a copy of a descriptor r†°dONLNd£å
Rò
d)fecorî°dONLNdßå
dò
√)d containing the addr¿°dONLNdºå
ƒò
Ï)`
ess of an °dONLNdΔóÏ£
 (†Ïapplication.°dONLNd‘ßl≥¥(∞lAECountItems°dONLNd·ßÏ≥
Ö)Ä"Returns the number of descriptor r8Ä°dONLNd
ß
Ü≥
ò)öecor¨‡°dONLNd
ß
ò≥
˘)ds in a descriptor list. °dONLNd
 ≤Ïæ
ÿ(ªÏ5Used, for example, to determine the number of alias r} °dONLNd
U≤
ÿæ
Í)ÏecorÒÄ°dONLNd
Y≤
Íæ
ˆ)ds °dONLNd
\ΩÏ…
K(ΔÏfor documents specifi° °dONLNd
qΩ
K…
Ä)_ed in the dirf¿°dONLNd
~Ω
Å…
€)6ect parameter of the °dONLNd
î»Ï‘
V(—ÏOpen Documents event.°dONLNd
´ÿl‰Æ(·lAEGetNthPtr°dONLNd
∑ÿω
)Ä
Uses a buf?‡°dONLNd
¡ÿ
‰
7).fer to rÇ°dONLNd
…ÿ
7‰
Q)eturn $°dONLNd
œÿ
R‰
|)
a copy of ‰`°dONLNd
Ÿÿ
|‰
Ë)*the data for a descriptor °dONLNd
Û„ÏÔÔ(ÏÏ
rE°dONLNd
Ù„Ô
)ecorπ`°dONLNd
¯„
Ô
)d c≈`°dONLNd
˚„
Ô
Û)7ontained in a descriptor list. Used to extract data of °dONLNd2ÓÏ˙Ú(˜Ï
fiå¿°dONLNd4ÓÚ˙
Ê)4xed length or known maximum length; for example, to °dONLNdh˘Ï

(
ÏextracÄ°dONLNdn˘


ä)t the name and location of a d8@°dONLNdå˘
ä

≠)Éocumenî °dONLNdí˘
≠

∂)#t f™`°dONLNdï˘
∂

π)    
ro`°dONLNdñ˘
∫

€)om the °dONLNdù
Ï

G(
Ïdescriptor list specifiXÄ°dONLNd¥

H

})\ed in the dir °dONLNd¡

~

ÿ)6ect parameter of the °dONLNd◊
Ï

T(
ÏOpen Documents eventfi¿°dONLNdÎ

T

V)h
.°dONLNdÓ
l
+¥(
(lAEGetNthDesc°dONLNd˚
Ï
+
)Ä    Returns a¬ °dONLNd


+
-)* copyπ °dONLNd    

.
+
0)
 9 °dONLNd


1
+
C)of a Ä°dONLNd

D
+
w)descriptor ra¿°dONLNd

w
+
â)3ecor÷ °dONLNd

â
+
ò)d frä¿°dONLNd#

ô
+
Û)om a descriptor list. °dONLNd9
*Ï
6
Ó(
3Ï=Used to extract data of variable length; for example, to get °dONLNdv
5Ï
A
/*the descriptor r<†°dONLNdÜ
5
0
A
B)Decor±°dONLNdä
5
B
A
£)d containing an alias rm°dONLNd°
5
§
A
∂)becor·`°dONLNd•
5
∂
A
≈)d frñ°dONLNd©
5
Δ
A
ˆ)om the list °dONLNdµ
@Ï
L
(
IÏspecifiÓ °dONLNdº
@

L
=)ed in the dir≥¿°dONLNd…
@
>
L
Ë)6$ect parameter of the Open Documents °dONLNdÌ
KÏ
W
(
TÏevent.
    °dONLNdˇˇ(plFunction°dONLNdˇˇ)ÄDescriptionÕ`°dONLNdˇˇ)1 (continued)ˇCû@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äResponding to Ü)<Apple Events

, (‡3-25
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

jHp4jHp käk

ˇ·ˇ‚7^°dONLNd\äj–(fäInteracting W,@°dONLNd\—j
)Gith the Userˇˇˇˇˇˇ‘@(f
3
°dONLNdpä|
È(yäPIn some cases, the server may need to interact with the user when it handles an ≤‡°dONLNdkp
È|(y
ÈApple °dONLNdq}äâ(ÜäUevent. For example, your handler for the Print Documents event may need to display a °dONLNdΔääñ
F*,print options dialog box and get settings fr‡`°dONLNdÚä
Fñ
ì)ºom the user beforg@°dONLNd
ä
îñ)Ne printing. By specifying °dONLNd
óä£ê(†ä
flå¿°dONLNd
ó꣺)ags to the ,
Couriern °dONLNd
*óΩ£
G)-AESetInteractionAllowedeÄ°dONLNd
Aó
G£
°)ä function, you can seG¿°dONLNd
Vó
¢£
≠)[t p@°dONLNd
Yó
Æ£
±)
r—@°dONLNd
Zó
±£
¡)efer}`°dONLNd
^ó
£
Ú)ences to all‡°dONLNd
jó
Û£)1ow °dONLNd
m§ä∞¢(≠äuser iË¿°dONLNd
s§¢∞
+)nteraction with your applicatioQ†°dONLNd
í§
,∞
G)än (a) o@@°dONLNd
ô§
H∞
ˇ))nly when your application is sending the °dONLNd
¬±äΩ‡(∫äApple event to itselú`°dONLNd
÷±‡ΩÎ)Vf, (D °dONLNd
⁄±ÏΩ¸)b) o °dONLNd
fi±˝Ω);nly when the client application is on the same computer as °dONLNdæä Õ(«äyour applicatio„‡°dONLNd(æÕ ›)Cn, o*¿°dONLNd,æfi ‰)r ù`°dONLNd.æ‰ Ò)(c) 5`°dONLNd2æÚ 
˛)<for any event sent by any client application on any computer±†°dONLNdnæ
˝ («
˝. In °dONLNdsÀä◊
U(‘ä-addition, your handler should always use the ¯¿°dONLNd†À
U◊
¡)ÀAEInteractWithUserÚ°dONLNd≤À
¡◊)l function beforfl‡°dONLNd¡À◊    )Ae °dONLNd√ÿä‰
œ(·äKdisplaying a dialog box or alert box or otherwise interacting with the user*`°dONLNdÿ
œ‰
‘(·
œ. *`°dONLNdÿ
‘‰
Á)The °dONLNdÂäÒˆ(ÓäAEInteractWithUsery@°dONLNd&ˆÒ)l< function determines whether user interaction can occur and °dONLNdbÚä˛∏(˚ä
takes appr°`°dONLNdlÚ∏˛
S).#opriate action depending on the cir䇰dONLNdèÚ
S˛
à)õcumstances.°dONLNdõ
ä

@(
ä+Both the client and server specify their pr≠Ä°dONLNdΔ

@

P)∂eferY†°dONLNd 

Q

Ô)'ences for user interaction: the client °dONLNdÒ
ä
¶(
äspecifiÓ °dONLNd¯
¶

ƒ)Aes whether the server should be allowed to interact with the useri@°dONLNd9

ƒ

Ï(

ƒ
, and the °dONLNdC
ä
*ß(
'äserver [¿°dONLNdJ
®
*ƒ)specifi…‡°dONLNdQ
ƒ
*Ì)    es when i|@°dONLNdZ
Ó
*¯)*t a>†°dONLNd]
˘
*
)llow€‡°dONLNda


*
)
s‡°dONLNdb


*
Ä) user interaction while pr=`°dONLNd|

Ä
*
µ)oocessing an "†°dONLNdà

µ
*
Î)5Apple eventm`°dONLNdì

Î
*
)6. °dONLNdï
+ä
7ï(
4äThr °dONLNdó
+ñ
7ù)e ]`°dONLNdô
+ù
7˙)Apple Event Manage†°dONLNd´
+˚
7
)^r does nuÄ°dONLNd≥
+

7
.)#ot a≠`°dONLNd∑
+
.
7)7llow a server application to interact with the user in °dONLNdÓ
8ä
Dç(
Aä
rE°dONLNdÔ
8é
D
)"esponse to a client application’s N@°dONLNd
8

D
O)é
Apple evenV†°dONLNd
8
O
D
ó)3t unless at least tS†°dONLNd.
8
ò
D
“)Iwo conditionÕ°dONLNd:
8
“
D
·):s arO°dONLNd>
8
‚
D
Ú)e ml†°dONLNdA
8
Ú
D
ˆ)
e6@°dONLNdB
8
˜
D
ˇ)t: °dONLNdE
Eä
Qè(
Nä
F °dONLNdF
Eê
Q¨)irst, th}@°dONLNdN
E¨
Q
-)e client application must set fd°dONLNdm
E
-
Q
:)Ålag€Ä°dONLNdp
E
:
Q
\)    s in the /†°dONLNdy
E
]
Q
c)#
s/@°dONLNdz
E
c
Q
ç)endMode,†°dONLNdÅ
E
ç
Q
€)* parameter of the d`°dONLNdì
E
€
Q
ˇ)NAESendb °dONLNdô
E
ˇ
Q
)$
 °dONLNdö
Rä
^©(
[äfunctioº‡°dONLNd°
R©
^¥)n iˆ†°dONLNd§
R¥
^Ã)ndica<`°dONLNd©
RÕ
^˙)ting that u$‡°dONLNd¥
R˚
^
:).ser interaction8`°dONLNd√
R
:
^
l)? is allowed.``°dONLNdœ
R
l
^)2% Second, the server application must °dONLNdÙ
_ä
kü(
häeithe`°dONLNd˘
_†
k™)r sø°dONLNd¸
_™
kÆ)

eà†°dONLNd˝
_Ø
k»)t no u°dONLNd
_…
k
)ser interaction prs†°dONLNd
_

k
$)Kefer¿°dONLNd
_
%
k
Ä)ences, in which case 4†°dONLNd.
_
Ä
k
Ï)[AEInteractWithUser-‡°dONLNd@
_
Ï
k
Ó)l
 °dONLNdA
lä
x    (
uäYassumes that only interaction with a client on the local computer is allowed; or it must °dONLNdö
yä
Öû*set flU¿°dONLNd†
yü
Ö©)ag‰‡°dONLNd¢
y©
Öæ)
s to t °dONLNd®
yø
ÖÃ)he 7 °dONLNd´
yÃ
Ö
V)AESetInteractionAllowed.Ä°dONLNd¬
y
V
Ö
Ä)ä
 function <¿°dONLNdÃ
y
Ä
Ö
Ø)*indicating v °dONLNd◊
y
Ø
Ö
≤)/
t∏Ä°dONLNdÿ
y
≤
Ö
º)ha⇰dONLNd⁄
y
Ω
Ö
»)t uS`°dONLNd›
y
…
Ö)ser interactioïÄ°dONLNdÎ
y
Ö)9
nf‡°dONLNdÏ
y
Ö
)
 °dONLNdÌ
Üä
íì(
èäis %`°dONLNd
Üî
í∑)
allowed®°dONLNd˜
Ü∑
íº)#. °dONLNd˙
òä
§˙(
°äIf these two conditions arT °dONLNd
ò˙
§
0)pe met and if ' °dONLNd!
ò
1
§
ù)7AEInteractWithUser `°dONLNd3
ò
ù
§
Á)l determines that n‡°dONLNdD
ò
Á
§)J    both the °dONLNdM
•ä
±
)(
Æä%client and server applications allow ¯`°dONLNdr
•
)
±
h)üuser interactioA†°dONLNdÅ
•
i
±
w)@n uö °dONLNdÑ
•
w
±
∞)nder the currO‡°dONLNdë
•
±
±
Ã):ent cir ‡°dONLNdò
•
Ã
±
˙)    cumstance†‡°dONLNd°
•
˚
±
)/s,]‡°dONLNd£
•
±)
 °dONLNd§
≤ä
æê(
ªä
A†°dONLNd•
≤ê
æ)EInteractWithUsey†°dONLNdµ
≤
æˆ)`
ry@°dONLNd∂
≤ˆ
æ˛) bć°dONLNd∏
≤˛
æ
ä)!rings your application to the forR@°dONLNdŸ
≤
ã
æ
ô)çegrp°dONLNd‹
≤
ô
æ
Â)ound if it isn’t alrÓÄ°dONLNd
≤
Â
æ)Leady in °dONLNd¯
øä
Àß(
»äthe fork¿°dONLNdˇ
øß
Àµ)egrâÄ°dONLNd
øµ
À—)ound. ≈†°dONLNd
ø—
À◊)
YÜ °dONLNd    
ø◊
À)Jour application can then display its dialog box or alert box or otherwise °dONLNdS
Ãä
ÿË(
’äinteract with the userfiÄ°dONLNdi
ÃÁ
ÿˇ)]. The @°dONLNdo
Ã

ÿ
l)AEInteractWithUserÄ°dONLNdÅ
Ã
l
ÿ
È)l function brings your server °dONLNdû
Ÿä
·(
‚äapplication to the fre°dONLNd≥
Ÿ·
Â
)Wont either dir9`°dONLNd¡
Ÿ

Â
~):ectly or after the user r
Ä°dONLNd⁄
Ÿ

Â
–)desponds to a notifii °dONLNdÌ
Ÿ
–
Â
Ò)Qcation rê°dONLNdı
Ÿ
Ò
Â)!equestB‡°dONLNd˚
Ÿ
Â)
.°dONLNd˝
Îä
˜
(
ÙäFor detailed information about◊ °dONLNd    
Î

˜
()à howı°dONLNd    
Î
(
˜
*)
 u°dONLNd     
Î
+
˜
6)to ¨‡°dONLNd    #
Î
6
˜
O)specifb °dONLNd    )
Î
P
˜
[)y fdONLNd    ,
Î
[
˜
ä)lags to the °dONLNd    8
¯ä
(
äAESetInteractionAllowedw`°dONLNd    O
¯

;)ä     function†°dONLNd    X
¯
<
x)( and how the †°dONLNd    e
¯
x
‹)<Apple Event Manager °dONLNd    yäΩ(ädetermines x`°dONLNd    Ñæ
\)4$whether user interaction is allowed,˝°dONLNd    ®
\
†)û see the section °dONLNd    ∫äÀ(ä“Interacting Wù`°dONLNd    »À˛)Aith the Userz°dONLNd    ‘˛
)3,”˙°dONLNd    ÷

R) which begins on j`°dONLNd    Á
S
j)Npage E@°dONLNd    Ï
k
})4-45ô °dONLNd    
}
)
.

<HC4=HC >ä>

ˇ·ˇ‚7^°dONLNd    Ú/ä=
(9äPerforming the Requested 4Ä°dONLNd
/
=
3)èActio‡Ä°dONLNd
/
3=
∑)n and Returning a Resultˇˇˇˇˇˇ‘@)‹
3
°dONLNd
*CäOˆ(LäWhen your application rʆ°dONLNd
ACˆO
5)lesponds to an 9‡°dONLNd
OC
6O
Û)@*Apple event, it should perform the standarõ¿°dONLNd
yC
ÛO
˚)Ωd °dONLNd
{Pä\´(Yäaction r¶‡°dONLNd
ÉP´\
J)!#equested by that event. For examplej‡°dONLNd
¶P
K\
ü)†, your application s] °dONLNd
∫P
†\
¿)Uhould rÙ@°dONLNd
¡P
¿\
˛) espond to the °dONLNd
œ]äiÔ(fäOpen Documents evenú`°dONLNd
‚]Ôi
,)et by opening t`°dONLNd
]
-i
V)>    he specifiúÄ°dONLNd
˙]
Vi))*ed documents in titled windows just as if °dONLNd$jäv
6(sä&the user had selected each document fry†°dONLNdJj
6v
„)¨%om the Finder and then chosen Open fr˛@°dONLNdoj
„v)≠om the °dONLNdvwäÉ∏(Ää
File menu.†°dONLNdÄwπɪ)/
 ˇ&Ê@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-26    )BResponding to Ü)<Apple Events4^*¿
¯
°dONLNd\lhà(elMany w`°dONLNd\àh
B)*Apple events can ask your application to r?°dONLNd/\
Ch
–)ª"eturn data. For instance, if your °dONLNdQilu¯(rl!application is a spelling checkerà °dONLNdri¯u
Ó)å:, the client application might expect your application to °dONLNd¨vlÇo(l
rE°dONLNd≠vpÇ
E)2eturn data in the form of a list of misspelled worΡdONLNdflv
EÇ
T)’ds. &¿°dONLNd„v
UÇ
m)Figur˘Ä°dONLNdËv
lÇ
≠)e 3-14 on page ∏¿°dONLNd˜v
ÆÇ
∂)B3-†°dONLNd˘v
∑Ç
¡)    38†°dONLNd˚v
¡Ç
È)
     shows a °dONLNd
Élè
€(ålUsimilar example: a Get Data event that asks the server application to locate a specifiÄÄ°dONLNd
ZÉ
ۏ
·(å
€c °dONLNd
\êlúÿ(ôlApple event object and rÕ°dONLNd
têÿú
j)l#eturn the data associated with it. °dONLNd
ò¢lÆÿ(´lIf the client application r™°dONLNd
≥¢ÿÆ
)lequests a r^‡°dONLNd
æ¢
Æ
)/eplyÜ`°dONLNd
¢
Æ
.), the Ö`°dONLNd
Ȣ
.Æ
ú)Apple Event Manager pr{`°dONLNd
ޢ
úÆ
Ø)nepar °dONLNd
‚¢
∞Æ
Δ)es a r◊¿°dONLNd
Ë¢
ΔÆ
€)eply °dONLNd
ÌØlªü(∏l
Apple evenà`°dONLNd
˜ØüªØ)3t byaÄ°dONLNd
˚Ø∞ª
) passing a default rV†°dONLNdØ
ª
)Teply ªÄ°dONLNdØ
ª
ñ)Apple event to your handler‚@°dONLNd/Ø
ñª
œ)}. If the client °dONLNd?ºl»Ã(≈lapplication does not rù°dONLNdUºÃ»ˆ)`
equest a r‡°dONLNd_º˜»

)+eply<`°dONLNdcº
    »
), the ;`°dONLNdiº
»
®)Apple Event Manager passes a 
̰dONLNdܺ
®»
Ì)änull descriptor °dONLNdñ…l’à(“lrecordb`°dONLNdú…â’Ó)—that is, a descriptor r= °dONLNd¥…Ó’
)eecor±Ä°dONLNd∏…
’
*)
d of type ,
Courier≥‡°dONLNd¬…
*’
Z)*typeNull∞‡°dONLNd …
Z’
´)0 whose data handl⁄`°dONLNd€…
´’
Ô)Qe has the value °dONLNdÎ÷l‚r(fll
N†°dONLNdÏ÷r‚~)IL~‡°dONLNdÓ÷~‚
*)'—to your handler instead of a default r0@°dONLNd÷
+‚
@)≠eply ï °dONLNd÷
@‚
¥)Apple event. The default rÀ¿°dONLNd4÷
¥‚
…)teply 0†°dONLNd9÷
 ‚
Á)Apple °dONLNd?„lÔ
j(Ïl8event has no parameters when it is passed to your handleå@°dONLNdw„
jÔ
m)˛
r¡Ä°dONLNdx„
mÔ
é), but yo@°dONLNdÄ„
èÔ
›)"ur handler can adQÄ°dONLNdë„
›Ô
Â)Nd °dONLNdìl¸r(˘l
pÇ °dONLNdîr¸£)arameters t`°dONLNdü§¸≤)2o it0†°dONLNd£≤¸
d)+. If your application is a spelling checkerÈÄ°dONLNdŒ
c¸
 )±, for example, you can r≤@°dONLNdÊ
À¸
Ï)heturn a °dONLNdÓ˝l
    À(
llist of misspelled worc@°dONLNd˝À
    
)_ds in a parameter…`°dONLNd˝

    
E)L    . HoweverV°dONLNd˝
E
    
Í).$, your handler should check whether °dONLNdB

l
Ä(
lthe r¢`°dONLNdG

Ä
ï)eply @°dONLNdL

ñ

)Apple event exists befor»†°dONLNdd




Í)j6e attempting to add any attributes or parameters to itb °dONLNdö


Î

)Î. °dONLNdú
l
#©(
 lAny attempt tQ°dONLNd©
™
#“)>    o add an Ò°dONLNd≤
“
#
…)(9Apple event attribute or parameter to a null descriptor ro¿°dONLNdÎ

 
#
‹)¯ecor‰ °dONLNdÔ

‹
#
‰)d °dONLNdÒ
$l
0ù(
-lgenerates a/`°dONLNd¸
$û
0≥)2n err°dONLNd

$≥
0º)or¨¿°dONLNd
$ª
0¿). °dONLNd
6l
B˜(
?lWhen you extract a descriptor r1@°dONLNd%
6¯
B

)åecor•†°dONLNd)
6


B
>)d using the ´¿°dONLNd5
6
>
B
í)4AEGetParamDesc¶Ä°dONLNdC
6
í
B
ó)T, °dONLNdE
Cl
Oÿ(
LlAEGetAttributeDescy@°dONLNdW
Cÿ
O›)l, y@°dONLNdY
C›
O
%)AEGetNthDesct¿°dONLNde
C
%
O
5)H, or \‡°dONLNdj
C
6
O
~)AEGetKeyDescX`°dONLNdv
C
~
O
∫)H function, the †°dONLNdÖ
C
∫
O
Ù)<Apple Event °dONLNdë
Pl
\û(
Yl
Manager cr«@°dONLNdõ
Pû
\
%)2 eates a copy of the descriptor r÷‡°dONLNdª
P
%
\
7)áecorK@°dONLNdø
P
8
\
Â)'d for you to use. When your handler is °dONLNdÊ
]l
ir(
fl
fiå¿°dONLNdË
]r
i
)%nished using a copy of a descriptor rf‡°dONLNd
]

i
%)°ecor€@°dONLNd
]
%
i
…)$d, you should dispose of it—and therT‡°dONLNd5
]
 
i
‹)•eby °dONLNd9
jl
v
`(
sl6deallocate the memory used by its data—by calling the r@°dONLNdo
j
a
v
Ø)ıAEDisposeDescm`°dONLNd|
j
Ø
v
Ÿ)N
 function.


Ñ*
í
¯4
Ö*
í
¯
    °dONLNdá
Él
é(
ãlNote

ˇ·ˇ‚7^
°dONLNdå
êl
úö*
Outputs frΔ‡°dONLNdñ
êö
ú˘).om functions such as `°dONLNd´
ê˙
ú
<)`AEGetKeyPtr@°dONLNd∂
ê
<
ú
o)B and other r뇰dONLNd¬
ê
o
ú
ë)3outines °dONLNd 
úl
®»(
•lwhose names end in A°dONLNd›
ú…
®·)]-Ptr?Ä°dONLNd·
ú·
®
)
 use a bufÇ@°dONLNdÎ
ú

®
à)*fer rather than a descriptor rô`°dONLNd    
ú
à
®
ö)}ecor¿°dONLNd
ú
õ
®
Æ)d to °dONLNd
®l
¥o(
±l
rE°dONLNd
®p
¥
+)+eturn data. Because these functions don’t ræ °dONLNd>
®
+
¥
B)ªequir’`°dONLNdC
®
B
¥
v)e the use of °dONLNdP
¥l
¿∫(
ΩlAEDisposeDesc{ °dONLNd]
¥∫
¿€)N
, it is prí`°dONLNdg
¥€
¿
ù)!.eferable to use them for any data that is not °dONLNdï
¿l
Ãã(
…lidentifiV†°dONLNdù
¿å
Ãœ) ed by a handle.,Zapf Dingbats√@°dONLNd≠
√‘
À⁄)H
u
°dONLNdØ
—l
›r(
⁄l
Y@Ä°dONLNd∞
—r
›É)our —`°dONLNd¥
—É
›
j)4Apple event handler should always set its function r‡°dONLNdË
—
k
›
©)Ëesult either to @°dONLNd¯
—
™
›
»)?noErr`°dONLNd˝
—
»
›
€) if it °dONLNd
fil
ÍŸ(
Álsuccessfully handles the O†°dONLNd
fiŸ
Í
O)mApple event or to a nonzera@°dONLNd7
fi
O
Í
Z)vo r¿°dONLNd:
fi
[
Í
¨)esult code if an errÆ@°dONLNdN
fi
¨
Í
Ÿ)Qor occurs. °dONLNdY
Îl
˜r(
ÙlIf2`°dONLNd[
Îs
˜u)
 ≤`°dONLNd\
Îu
˜µ)your handler rÿ‡°dONLNdj
ε
˜˘)@eturns a nonzer쇰dONLNdy
Î˙
˜
)Eo rN`°dONLNd|
Î

˜
G)esult code, the —°dONLNdå
Î
G
˜
 )AApple Event Manager adds a °dONLNdß
¯l¿(
lkeyErrorNumberz¿°dONLNdµ
¯¿
)T parameter to the rf°dONLNd»
¯

')Reply  ‡°dONLNdÕ
¯
'
∏) Apple event (unless you have alrh`°dONLNdÌ
¯
π
–)íeady °dONLNdÚlà(laddedú‡°dONLNd˜àä)
 ‡°dONLNd¯ãê)
a‡°dONLNd˘êí)
 ú‡°dONLNd˙íÊ)keyErrorNumberó†°dONLNd    Ê
ü)T* parameter). This parameter contains the r7†°dONLNd    2
†
‚)∫esult code that °dONLNd    Bl¨(lyour handler r¶Ä°dONLNd    P¨
o)@,eturns. The client should check whether the Õ‡°dONLNd    |
o
√)√keyErrorNumber»†°dONLNd    ä
√
ı)T parameter °dONLNd    ïl+
k((l8exists to determine whether your handler performed the r‡°dONLNd    Õ
l+
Ù((
l equested action. In addition to °dONLNd    Ì,l8o(5l
rE°dONLNd    Ó,p8§)eturning a r*°dONLNd    ˙,§8
;)4#esult code, your handler can also r∞†°dONLNd
,
;8
o)óeturn an err⁄`°dONLNd
),
o8
≤)4or string in the °dONLNd
:9lE¿(BlkeyErrorStringz¿°dONLNd
H9¿E
)T parameter of the rwÄ°dONLNd
[9
E
')Reply ‹`°dONLNd
`9
'E
Ì)/Apple event. The client can use this string in °dONLNd
èFlRÜ(Olan errR†°dONLNd
ïFÜRË)or message to the user`°dONLNd
´FËRÍ)b
.°dONLNd
≠Xldÿ(alIf the client application r™°dONLNd
»Xÿd
)lequested a r@°dONLNd
‘X
d
!)6eply.¿°dONLNd
ÿX
 d
5), the -¿°dONLNd
fiX
5d
ù)Apple Event Manager r!†°dONLNd
ÛX
ùd
œ)heturns the rÿ °dONLNd
ˇX
œd
‰)2eply °dONLNdelqÓ(nlApple event, which is identifi °dONLNd"eÔq
L)Éed by the event class íÄ°dONLNd8e
Lq
¶)]kCoreEventClass凰dONLNdGe
¶q
Ù)Z and by the event °dONLNdYrl~y({lID ¿°dONLNd\rz~∞)    kAEAnswer[°dONLNderØ~
)5. When the client has fifi@°dONLNd}r
~
b)dnished using the r; °dONLNdèr
c~
x)Peply †°dONLNdîr
x~
›)Apple event, it should °dONLNd´lãΔ(àldispose of both the rº°dONLNd¿Δã
Ü)Z*eply event and the original event—and theruÄ°dONLNdÍ
áã
ÿ)¡eby deallocate the °dONLNd˝ålò
(ïlmemory they use—by calling the a °dONLNdå

ò
O)ïAEDisposeDesc\@°dONLNd)å
Oò
é)N function. The «‡°dONLNd8å
éò
Ú)?Apple Event Manager °dONLNdLôl•í(¢l    takes car`°dONLNdUôì•˙)'e of disposing both the Ó‡°dONLNdmô˘•
Y)fApple event and the rI °dONLNdÇô
Z•
o)aeply Æ°dONLNdáô
o•
„)Apple event after a server ˇÇ<@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äResponding to Ü)<Apple Events

, (‡3-27
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähÓ(eäapplication’s handler rc@°dONLNd\Óh
)d
eturns to ,
Courier/@°dONLNd!\
h
ä)*AEProcessAppleEvent( °dONLNd4\
äh)r, but a server application is °dONLNdRiäuç(rä
rE°dONLNdSiéu
) esponsible for disposing of any 9¿°dONLNdsi
u
t)åApple event data str@†°dONLNdái
tu
ã)ZucturΔÄ°dONLNdåi
ãu
ß)es it cr- °dONLNdîi
®u
)eates while extracting °dONLNd´väÇß(ädata frw°dONLNd≤vßÇ»)om the ?Ä°dONLNdπv»Ç
)!Apple event.°dONLNdΔàäî¢(ëäFigurR¿°dONLNdÀà¢îª)e 3-12@°dONLNd—àªî

) shows the entir@°dONLNd·à

î
)Fe pr
°dONLNdÂà
î
;)
ocess of r∏¿°dONLNdÔà
;î
Ñ)(esponding to an ‡°dONLNdˇà
Öî
¿)JApple event. 

∂H«4∑H«"∑H]

ˇ·ˇ‚7^
    °dONLNd
¨ä∑∫(¥äFigure 3-12°dONLNd
¨Ã∑
s)B%Responding to an Open Documents event°dONLNd
>¨
t∑
v)®
 é °dONLNd
?¨
v∑
x)
 

ΔDπ4«Eπ

«Eπ4ΔD«Eò@@
˘@
˘«E
>¡¡…ˇ¯˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚ò@@Ä
˘@Ä
˘
E
G>…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚Êˇ˝Èˇ¸˚Êˇ˝Èˇ¸˚Êˇ˛Èˇ¸˚ÊˇÄÈˇ¸˚Êˇ@Èˇ¸˚Êˇ Èˇ¸˚ÊˇÛ¸Èˇ¸˚Êˇ    ¸Èˇ¸˚Êˇ‡¿Èˇ¸˚Êˇ¡0Èˇ¸˚Êˇ
Ä»Èˇ¸˚ÊˇÈˇ¸˚ÊˇÚÈˇ¸˚ÊˇÅ©Èˇ¸˚ÊˇTèÈˇ¸˚Êˇ"(èÈˇ¸˚ÊˇBèÈˇ¸˚ÊˇDèÈˇ¸˚ÊˇÑ    Èˇ¸˚Êˇà(áÈˇ¸˚Êˇ4@Èˇ¸˚Êˇ    j Èˇ¸˚Êˇ    UÈˇ¸˚ÊˇJàÈˇ¸˚ÊˇEDÈˇ¸˚Êˇ
B¢Èˇ¸˚ÊˇêASÈˇ¸˚ÊˇH ¨èÈˇ¸˚Êˇ( \èÈˇ¸˚Êˇ0èÈˇ¸˚ÊˇèÈˇ¸˚ÊˇèÈˇ¸˚Êˇ Èˇ¸˚Êˇ
¿Èˇ¸˚Êˇ˝Èˇ¸˚Êˇ˝Èˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚ò@Ä¿
˘Ä¿
˘
GE
á>…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚ò@¿

˘¿

˘
áE
«>…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚ò@

@
˘

@
˘
«E>…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚ò@
@
Ä
˘
@
Ä
˘EG>…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚ò@
Ä
¿
˘
Ä
¿
˘GEá>…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚ò@
¿
Ú
˘
¿
Ú
˘áEπ>…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚…ˇ¸˚¡¡¡ò@@
˘@
˘«E
>
¡¡…30˚…˚¬»˚…˚»˚¬…˚¬»˚…˚Ò
¿˛`fi˚Û
‡˛`◊Û
Ô{·œÓpfi˚Û
ÌÔÛÔˇ`◊Ú
ÌÔÉè`fi˚Û?{ÒÊˇpfi˚Ò
`⁄˚    Ú
`”…˚
ı˜ˇ˛ŸÙį‡˚ıį‡˚Ù˜àä‡˚ıįŸıć˝
`‡˚ı¢&2"/¢˛"
b"ŸÙÄ?wπœ¯Ó·˚¯Ä=ˇçÔo˝ˇ~    ¯‚˚˜¸àéΩœçÔè˝èÔäÄ„˚¯ÄÔè9Á¸ˇ~‡‹¯Ä˙<„˚¯p¢".˘"Ä›¯
¿į‡‡‰˚˘į>0‰˚¯0˜ˇ˛¿‰˚˘p‡Ä¯|›˘¿8¿Ä¯
ÄÂ˚˙ćį
ćfi˘Äį˛
‡8Â˚˙
8˛Ä¯˛
8Â˚˘
`8˛Ä¯˛Ê˚˚
¿`˛Ä¯˛
¯fl˚
¿˛Ä¯˛
¿hÊ˚˚
˝
Ä
¿ Ä˝
pfl˙
˝Ä
  ˝˝
Ê˚ ˚
08˝
Ä
&`=l≥˝
Ê˚˙
``˝
Ä
/ê3RœÄ˝
Ê˚˚
¿¿˝
Ä
(Ä3Rƒ˝
fl!¸
ÅÄ˝
Ä
«t2åªÄ˝
ÅÊ˚¸
¸Ä¯¸ˇfl˚
¸Ä¯¸
Ê˚¸
¸Ä¯‡˚˚
¸
Ä  ć˚¸
0¸Ä  ˝Ÿ¸
‡¸
Ķ∞=l≥‡˚¸
ĸ
Ä©†3RœÄŸ˚
˚
Äi†3Rƒ‡˚ı
Ä&D2åªÄ‡˚Ùį‡˚ıįŸıį‡˚ò@@Ä
˘@Ä
˘
E
G>
‘@˙į˝

‡fl
0@˙į˝Â˚‹‡˙į˝
Ã÷ÿË˚Ú@˙į¸æïË˚
5@˙į˝0ï·‘Ú`˙į˝
ŒàË˚ıįŸÙį‡˚ıį‡˚˛(
Ä˙˜ˇ˛¸
`Ë˚ 
È@·s©ªô¿Ì
‹ÍnÊpÈ˚
 jM• ÏröìiH‚ j5• Ì
≤öçiHÈ˚Û©›ô ϸÍwfHÈ˚BË
ÄÊ˚BË
ÄflBË
ÄÊ˚¬»˚ÊÂ˚Â
ÄÊ˚ˇˇ‡Î
@fl0Î
 Ê˚ÎÛ¸‡ˇˇêÎ    ¸Á˚    ˇê·¿Ë˚    êΡ0Ë˚    ÄêÎ
Ä»·    ÄêÎË˚    xêÎÚ·    xêÎÅ©Ë˚    xêÎTÄÈ˚    xêÎ"(ÄÈ˚    ~êÎBÄ‚    ~êÎDÄÈ˚    ÄêÎÑ    ·ˇˇêÎà(áË˚Î4@Ë˚Î    j Ë˚Î    U·ÎJàË˚ˇÎED·Î
B¢Ë˚ÍêASË˚ÍH ¨ÄÈ˚0Í( \Ä‚ˇˇ‡Í0ÄÈ˚ ÍÄ‚ ÍÄÈ˚ Í
 Á˚ˇˇ‡Í

¿Á˚¬…˚¬»˚Ê<“$Ë˚Â@
ZË˚Ê9;€Øò‚
‡Í1['–È˚
ÍE1%&‚
.;0Î8Ò%'–È˚
ÈO†Œ˚
)L Œ˚ò@Ä¿
˘Ä¿
˘
GE
á>
    
);†«…˚¬»˚…˚»˚¬…˚Ûˇ‡„˛
Ę Í˚¿˜ Í˚˛
`˜ Í˚0˜ „0˜ Ù Í˚88˜ Ù „˛
 ˜[w&gı Í˚ ˜W )îĈ Í˚˛
 ˜TJ)îĈ Í˚ ˜#À&gı „ ˜˝ı Í˚ ˜˝ı „˛
 ˜˝ı Í˚ ˜ Í˚˛
 ˜ˇ‡Í˚ ˜ „ ˜ Í˚ ˜˘˘ „ ˛
 ˜0ˇ˛Ä¯˝ Í˚! ˜)    
Õªœ
üq‡"à˝ Í˚ ˛
 ˜8Ã%E$î∏Ä"‡˝ Í˚ ˜D)Â}$ÄÙ»ê"Ä˝ „! ˜oflÇ≥û¸`¿˝ Í˚ ˜ „˛
 ˜ Í˚ ˜ Í˚˛
 ˜`˛0¯ Í˚ ˜#0
˚ „ ˜-,?ƒ;gùπÔ˚ Í˚ ˜9‰E$EHê≈Dî¸ „˛
 ˜)$E$˝Oêï|îĸ Í˚  ˜g??øêÇ}Ú€¸ Í˚˛
 ˜˛Ù Í˚ ˜˛8Ù „ ˜ Í˚ ˜˝Ä¿˛˛
  „!˛
 ˜¿ÃG      Í˚" ˜
.IèÚ€àñ›Ô̪œ Í˚!˛
 ˜
1xëJTH¬¢î    E$ Í˚ ˜
1HëJ_W»íæîâı}$ê „" ˜ŒœÔÔƒ!?Ò    €B≥ Í˚ ˜˝
˙˛
  „˛
 ˜˝ı Í˚ ˜ Í˚˛
 ˜ Í˚ ˜ˇ‡„ Õ˚ Δ˛
 Õ˚ Õ˚˛
 Õ˚ Δ Õ˚ Δ˛
 Õ˚ò@¿

˘¿

˘
áE
«>
 ˜ˇ‡Í˚˛
 ˜ Í˚ ˜ „ ˜ Í˚ ˜ „˛
 ˜ Í˚" ˜˛0˛˛ Í˚$˛
 ˜0
 Ìˇ
Ä˚$ ˜    9,?ƒ;gùπÔÌùÁà Ì¿˙% ˜    E‰E$EHê≈Dî    "í Ì
¿˚$ ˜    E$E$˝Oêï|îâı>íH Ì¿˙$˛
 ˜;??øêÇ}Ú€B    Ÿà Ì
¿˚! ˜˛˙˛ Ì
¿˚$˛
 ˜˛8Ù ¸ D˘
¿˚  ˜ ¸ l˘¿˙$ ˜ ¸    w&∂ÓlÓ„≥¸
¿˚# ˜ˇ‡¸    LØØîl94˙¸¿˙#˛
 ˜ ¸    î®îTŸ‘¬¸
¿˚$ ˜ ¸    ˜'GñTys∫¸
¿˚˛
 ˜ ˚D˙ĸ
¿˚) ˜0ˇ˛˚¯ ˚D˚˚¿˙) ˜)    
Õªœß~‡"à ˚DÙ
¿˚$ ˜8Ã%E$
X†á#"‡ Ì¿˙$˛
 ˜D)Â}$Å_úy#"Ä Ì
¿˚% ˜oflÇ≥R(ßû@¿ Ì
¿˚˛
 ˜ˆ¸ Ìˇ
¿˚ ˜ˆ¸ 
Ìˇ¿˙ ˜ Í˚ ˜˛
˛¿˛@˝ „ ˛
 ˜ÄpOÄ¿˝ Í˚! ˜Îi1˜!Õ∏DÏÔ<@˝ Í˚ ˛
 ˜UO$¢%DF)êB˝ Í˚ ˜UI$ßÂ|D©Ùí@˝ „" ˜‘ô˝Ó¸ÇˇêNÕÚ
@ Í˚ ˜Ä ı „˛
 ˜Ä
¿ı Í˚ ˜ Í˚˛
 ˜˝Ä`˛˝ Í˚ ˜˛
f#Ä|ÑIJ „( ˜[%á˘l‚%∑=‡Ä˛ ˇ˚% ˜™<à•©0®íÅ˛ ¯&˛
 ˜™$à•/©Ú$Øíñ˝ ˚( ˜§gÁ˜‚O¸B;gà@ ˚-˛
 ˜Ĉ 
D˛˚* ˜ı ÄD˛¯( ˜ ùÀ[wnw‹>t¿˚% ˜ ì/èW &˘M‡¯.˛
 ˜;?{?ü‡˜ S,TJ&ŸkM˛˚/ ˜U)&! ˜ ]Àá#Àn;Út‡˚(˛
 ˜Ï9RĘ ˛¸˙˚& ˜))‚ ˜ ˛¸˙¯) ˜;?g/˚‡˜ ˛¸˙˚# ˜ ˛ ¸˛¯%˛
 ˜ ˛Ä ¸˛˚& ˜ ˛ãnp¸    Ó<ÿ˚-˛
 ˜˘˝Ä ˛˙˘ ¸    9M˚1 ˜3¸˛¿@ġ‡˛äâ ¸ŸM¯4 ˜)3ß=«=kDrwfiÒ∑˜â<˛Ùy0¸    y<˚% ˜9úÿΔ(G5§ã)A"®     "'¯'˛
 ˜E0à√Á8•$˙WÈI>Ø I
Ä˚( ˜o˘Á<ä]πfl'»ù±BÌâDDÄ˚!˛
 ˜˙!¸Äˇ»¿ˇ˚  ˜˙
sĢ p@˘˘¯# ˜ @˘
`˛ÿ˛˚ò@

@
˘

@
˘
«E>
% ˜ `‡˛
 ò√0Hx¯'˛
 ˜ˇ‡ $ê˛ =Ì<ۻ˕œ˚# ‰`Bʇì4¥gvZ©ÓLI¶1˚"˛
 ‰†BüêîÙÙØ8©2L…¯¶0˚! ‰ $òêÑ≠˝”?Ô~Gyœ˘  ‰     Áê„;™t∂˚˚ ‰
 Ä˚p˚
˘˛
 ‰ Ä˚˘˚ ‰`Ä˚˘˚˛
 ‰†ˇ˚ ‰ ˘˘
˘ ‰     ˘
`˛ÿ˛˚! ‰
 8@G˛
ò√0Hx˘"˛
 ‰ $DÄ
=Ì<Û»‰•œ˚# ‰`%‹‰ô•£;‡Z©ÓLI&1˚"˛
 ‰†9RD¶eW•8©2L…Ù&0˚! ‰ !RD¶%T%–˝”?Ô~Nyœ˘  ‰     !Rg›S•‡˚˚ ‰
 ˘p˚
˘˛
 ‰ ˘˘˚ ‰`˘˘˚˛
 ‰†ˇ˚ ‰ ˘˘
˘ ‰     ˘˘˚ ‰
 ˘˘
˘˛
 ‰ ˘˘˚ ‰`˘˘˚˛
 ‰†˘˘˚ ‰ ˘˘
˘ ‰     ˘˘˚ ‰
 ˘˘
˘˛
 ‰ ˘˘˚ ‰`˘˘˚˛
 ‰†ˇ˚ ‰ ˘˘
˘ ‰     ˘˘˚ ‰
 ˘˘
˘˛
 ‰ ˘˘˚ ‰`˘˘˚˛
 ‰†˘˘˚ ‰ ˘˘
˘ ‰     ˘˘˚ ‰
 ˘˘
˘˛
 ‰ ˘˘˚ ‰`˘˘˚˛
 ‰†ˇ˚ ‰
 Ó˘ ‰
     Ó˚ ‰

 Ó˘˛
 ‰
 Ó˚ ‰
`Ó˚˛
 ‰
†Ó˚ ‰
 Ó˘ ‰
     Ó˚ ‰

 Ó˘˛
 ‰ Òˇ¸˚ ‰`Ò˚˛
 ‰†Ò˚ ‰0Ò˘ ‰˘

Ä˚˚! ‰.˛
ÄÄ|
˛˘"˛
 ‰ˆâNéy«9Zhé'g{¿˚( ?˘ˇ‡ÓDGåsQä(AÕ4ë1H•˛˚'˛  ˘0ÓàâÑIBÉÁ:)$ü%O• ˚ò@
@
Ä
˘
@
Ä
˘EG>
%  ˘0̇flÁéxäSn;‰|Çv¿˘#      
˝0Ì
?ˆ˙
 ˙˚!  300Ï˙
p˙˘˛  ˛û0ÏÒ˚  
DA0ÏÒ˚˛  ˛Dû0ÏÒˇ¸˚  ˘0ÏÒ˘ ?˘ˇÏÒ˚  ˙ 0ˇ‡Ò˘˛
#˘ˇ˛0,Ò˚"˘0<Ò˚,˛#fl¯¸˜ˇ0?˛ˇ0(Ä¿
0
¿˛@˚;#–¯P@ÄÙø0˛

∞˛˛`˛`
H(Ä¿H
 ˛@ê˘=!#–¯V`LÃ≥Ùø01Ü`êx0 >
—˛á(Ósëÿáç¡&ihŒ¯ˇê˚;7#–¯v`LÃ≥˜ø0⁄yÁêË•œ    œ+Z#ì∑{ƒ¢""#Å®ìLfiÉ0Ü_!)ôUÈ|ˇ˘<˛6#–¯V`LÃ≥Ù?0S‹òë¶1‰π≠$X®•¿
N®ùL–É0JQ!)âU    t?Ä˚=!#fl¯VdLÃ≥˜ˇ0Rdô믶0    $≈)'“Ø•$g˛ˇ3®óKŒÇ–3è!ΔwTÈxÄ˚-˛
#¯ˇ0;¶fi¸Gyœ˛ÌŒ˘>Bvƒ<˘˙˛˚("˙
0 ˚
˝<˘˙˜)"˙
s0‡˘
ú¸,˘˙˛˚"˙
[0 ˛ ı˜!˛
"˙
fl0 ˛ ı˛˚%" ˝
S0ˇ‡kgpı˛˚$˛"
÷ ˝
s0 ˙Ù†ı˛˚""
&,IJ
0 äцı˜%"
÷2˝
ˇ0 tt∞ı˛˚+"
62˝
0˛xî˛ ˛ Ò˜/˛"
÷,IJ
0˛@ê˛ ˛ Ò˛˚,"˙
0˛
Bøç‘‹Œs4¥g|˛ Ò˛˚6˛
"˙
0Äy“ïÈ$îÙÙæ˛
 J
ĸ
˛˚3"˙
0¿APï©$Ñ∫˛
 R
ĸ˜<"
˝
0˛
zôŒ‘Ãs;™tº˛ ?ˆ{ù«õºÓcçœl«û77˛˚+"
∫%µÀ(
0 ‚#RG)æ‘…ÚS"˘"ôKLј.˛"
∫"k.®
0 Ä
òR[)¢…“S$â"ôCLÑ˛˚/"
∫&k6®
0 DGRO'û€…bM/x¬y;4Ñ˛˚-˛"
T´Œê
0˛ ˛¸ ã˛Ò˛˚*"

0˛@˛¸ Ò˜/"
 
0˛    Û4lnÁn–›∞˝ Ò˛˚5"‡˛    d™%^îë√©Î‡˝
 0
 
    Ä˚˜;˛"
    àÀ    )˛    d™%PÑñÕ©
 ˝  
 
Ä
3˛˚<"ÕNéبàp˛    c*Nv„«®Ì‡˝ `ÿ”pÁ8≥∂ñ¥vöfiévIJ˚3˛"5Hñ§§â)ˇˇ¿˙Ģ †ΩÛ 9H‰T√ZãVMIã@˛˚0"
ÕHéüFE@˙Ģ  °≥ ŸHß‘íäMI˙˜1"˚@
@˙Ģ      úœ8w9ë    ˜ºw∫=^'IJ˚/"˙
""@0˛
˛˝
 ˛˛˘˜.˛
"˙
@H˛
˛˝  ˙8˘˛˚,"˙
ˇ¿áç¡∏‹öZπq¿ `Ò˛˚7˛
"˙
ÄÜ_#Õ2&fU>QH` †˝
¿Ä ˛D˛˚4"˙
¿JQ"5&bU"QI†  ˝
¿ÄP˛D˜9"˙
0˛"3è!‹Úù’YH‡      Ó|—üc±ÒÜŒ¨W:`÷Œ‰˛˚+"˙
0˛Ù
 ìF´œ¡HÀ≈È®t¶ÒıÈD˜.˛
"˙
0˛Ù  ùZ™AH     ®å¶Å    D˛˚/"˙
0˛Ù `ÁN©œ¡∞…ƒÓêè:pËÈd˛˚/˛"
‡õ
0˛

ı †Ä˙ ˛˛˚+"
Ü¿*dÅ0˝
ı  Ä˙  ˛˜2"
⁄†§Å0˛ñÁ4†˜      Ä˙ ˛˛˚2"
Z†$Å0˛∂ôM†˜
 H˛ÄIJ@
˜5˛"
Áñ†?€
0˛VôJ†˜  P˛ÄIJ@(
˛˚6"
0˛Jó2@˜ `{3•çÛÉ7ùΔgV+ù0˛˚-˛"˝
0 †R|ßfi¸Çzô$Ù‘:Sx˛˚)"¸
0 `RD¶ƒÇBô$Ñ‘FS@˜/"B˛€
0 1@R;ùÃ˚í;y$wHGù8˛˚9"∫˛)$Å0˛p˛ê 
ˇ‚¿˛Ä˛˜9˛"R˛§Å0˛H˛ê 
IJÄ˚˛˚ò@
Ä
¿
˘
Ä
¿
˘GEá>
6"≤˛
dÅ0˛IºÓ<Òπ∏liªú‡
DEʲ˚3˛"
˛=õ
0Äs‘… Zd^˘ê” 
àã˛ ı˛˚."¸
0¿J… dPŸìS 
˛ ı˜0"˙
0˛I€……Ÿ§Ngô“‰
ˇkgpı˛˚%"
¯˛õ
0Û
 ˙Ù†ı˜%˛"
@*dÅ0 äцı˛˚&"
⁄†§Å0 tt∞ı˛˚.˛"
†$Å0˛à˛
 @˛˝ Ò˛˚*"
†?€
0˛˝@˛˝ Ò˜."¸
0˛ªùÕùƯÛ1øq¿ Ò˛˚)"˚ˇ·˛ê”*S#|§£’J@ Ò˜+˛
"˙
0˛ìS*S-`§£UJ@ Ò˛˚0"ÓrÄ
0˛ë›…ù'|é£!ùI¿ Òˇ¸˛˚&˛"Q%Ä*§Åˇ0˝Ä˝@ Í˚!"Q"ħÅs0˝˚Ä „!"Q%Ä
§ÅS0˝˜ Í˚"N(‡?
fl0 „˛
"¸
€ Í˚"˙
sˇ‡Í˚˛
"˙

÷˚
#¯ˇœ"˙

Û÷˚"˙

õœ˛
"˙

õ÷˚"˙

˚÷˚˛
"˙

{÷˚"˙

œ#¯ˇ÷˚
!¯ˇœ˛
 Õ˚ Õ˚˛
 Õ˚ ‹Ï ‹xÛ˚ ›
»Ï˛
 ›
Û˚ ›
8Û˚˛
 fi
‡Û˚ fiÏ fi8Û˚ fip‡Ï˛
 fl¿ÄÛ˚ ¿
Ä0ˆÚ˚˛
 Ò
‡
Ä0ˆ88Ú˚ Ò
ÁΩÔw8˜
‡
‡Î Ò
ʘ˘ˇˇ∞˜Ò˚ Ò
ʘ¡è«∞˜Ͳ
 Ò7Ω¯ˆ∏˜Ò˚ 
0ÙÄÄÒ˚˛
 
0Ù¯˚ ‚ÄÈ ‚¯Ä˚ ˆÚˇ¯Ä˲
 ˆÚ¯
Ô˚ ˆÚÄÓ˚˛
 ˆÒà0|
Ó˚ ˆ˚0˚w¿Ê8ˆ˚0˚\
Ì˚˜ˇ
¸
˚";wø¢¸"(¿Â˛ˆ
˚˛˜Ä¸    Ä
Ï˚ˆ
˚Δ˜˚    Î˚˛

¿˜
˚àõˇª˚àâÅÎ˚˛p˜
˙
˚
Ô„˛˜ˇ
¸˙
˚
8Í˚ò@
¿
Ú
˘
¿
Ú
˘áEπ>
Ú
Ú"
(„ÒÚ
Í˚ÚÚÈ˚ÒÚˇ¯È˚ÚÚ‚ÚÚÈ˚ÚÚ‚ÒÚÈ˚ÚÚÈ˚Ò
˚

Ä˝È˚Ú    Ä
òÄ˝‚ÚªdÈßh›ÙÁ4;ü4gÿÈ˚ÚEF4ÿ¥¥™òö$—™Û‚Ò}D†à†î™üê'V™ÉÈ˚Úêè˘Áy”΂<9”™sÈ˚ÒÄ˙ ˝È˚ÚÄ˙ ˝‚Ú˜ ˝È˚Ú
˙@˝‚ÒÄt˚È˚ÚªdÈßhè4œs∑hgÿÈ˚ÒEF4ÿ¥dD¢H·‘ÛÈ˚Ú}D†à†êD¢Kf‘É‚Úêè˘Áy„=˛fiq„‘sÈ˚ÚÄ˚
@˝‚ÒÄ˚
@˝È˚Ú˜@˝È˚ÒÚÈ˚ÚÚ‚ÚÚÈ˚ÚÚ‚ÒÚÈ˚ÚÚÈ˚ÒÚˇ¯È˚¬…˚¬»˚…˚»˚¬…˚¬»˚…˚»Ã˚…30˚¡¡¡ò@@
˘@
˘πE˘>¡¡¡¡¡¡¡¡    
Ü«    
    à«    ê«    
$«    ê‰q:«    ëA"«    ˛Éú«¡¡¡¡¡ †`    Äx˛–˛
˛fi Äê:@$˛@1˛
˛fi /F»@DùE±÷fi9ÿ@—lÜçb€∏]-∏fi 2…pÄYc™“ìdÖh@Í¥)Kñ•i@•Vêfi RY8Sù2î¢d$âH@œ$JP¥ÆJ9…‰†fi lr àJU5¥ÿ5òcîLZñÈõ
â∞fi \Zp;¿Â˘â&‰∏"
êc»mπGíp‰y fi"˚˛D˝Ä‘"˚˛D˝Ä‘˚˛8˝Ä‘¡¡$Ĭ0f
◊  ˝ô
◊$YtMáúH2ÆÁRrë+ú9ÄŸ    ,¬"§¶à§†Tï’
R•ru RØ@Ÿ
Eº$…$á    ¿ˇ~ò‚ï.>$&ór@ŸgGÌIÅë$I,"ßh    (K¥DÄŸEÙEHâ<sú…√E∑œ28€ªÿˆ
˙@ÿˆ
˙@ÿˆ
˙@ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡(‡¿p :DIJ Ä8`@Ä8¿@Ê'$±@  @@˝ Ä@@Ê($$©Ä;r≤“í2‰õ[Y#.â∞ΩêËæI±»Rë:[ÓÊ($)*ÄM%EÔRUEM©´-%Tî–&í)YTT–îÔRÉä≠PÊ($…,ÄINIJdâäI%))iHô$ê$¢JKà§ë$Jg…éÊ($IHÄShèî∂øŒìÍBA”k˝©0)¥RŒºÈ1®"î¥U¬Ê($_È»ÚGäc$JâRQrD©$y$#kHë!gc#èàÚúÊ˝˛Ñı¯Ñ·ò@@Ä
˘@Ä
˘˘E9>˝˛Ñı¯Ñ·
˘ÑÎÑ·¡¡

‡Ã

çD÷R<¨cÕ;‘§jÓIP    •Õíôƒ    JJ”ê    (Õ•-:êìö
kÕÿ»·ƒîb—·D@Œ!˝ÄÀ!˝ÄÀ
!˝Ä…¡¡
˛–¯ÄœÅÄ@PÄœóà≟÷ƒR/Ï∏¨–)JjìJVPëQP–J
&RL¢R¢œbP–{    )îù¥‘ÛÉ£Ú†–Rìàñ‰à颛"° –
˝@

˝@
 ˝
Ä«¡¡ ¿`   
 ê $YrX!     ,¬"• ·
Eº$…  gGÍA  EÙED@‰¿ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˘Ä¿
˘9Ey>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˘¿

˘yEπ>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˘

@
˘πE˘>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˘
@
Ä
˘˘E9>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˘
Ä
¿
˘9Ey>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˘
¿
Ú
˘yE´>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˘@
˘πE˘>
¡¡¡¡¡¡¡¡    
Ü«    
    à«    ê«    
$«    ê‰q:«    ëA"«    ˛Éú«¡¡¡¡¡ †`    Äx˛–˛
˛fi Äê:@$˛@1˛
˛fi /F»@DùE±÷fi9ÿ@—lÜçb€∏]-∏fi 2…pÄYc™“ìdÖh@Í¥)Kñ•i@•Vêfi RY8Sù2î¢d$âH@œ$JP¥ÆJ9…‰†fi lr àJU5¥ÿ5òcîLZñÈõ
â∞fi \Zp;¿Â˘â&‰∏"
êc»mπGíp‰y fi"˚˛D˝Ä‘"˚˛D˝Ä‘˚˛8˝Ä‘¡¡$Ĭ0f
◊  ˝ô
◊$YtMáúH2ÆÁRrë+ú9ÄŸ    ,¬"§¶à§†Tï’
R•ru RØ@Ÿ
Eº$…$á    ¿ˇ~ò‚ï.>$&ór@ŸgGÌIÅë$I,"ßh    (K¥DÄŸEÙEHâ<sú…√E∑œ28€ªÿˆ
˙@ÿˆ
˙@ÿˆ
˙@ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡(‡¿p :DIJ Ä8`@Ä8¿@Ê'$±@  @@˝ Ä@@Ê($$©Ä;r≤“í2‰õ[Y#.â∞ΩêËæI±»Rë:[ÓÊ($)*ÄM%EÔRUEM©´-%Tî–&í)YTT–îÔRÉä≠PÊ($…,ÄINIJdâäI%))iHô$ê$¢JKà§ë$Jg…éÊ($IHÄShèî∂øŒìÍBA”k˝©0)¥RŒºÈ1®"î¥U¬Ê($_È»ÚGäc$JâRQrD©$y$#kHë!gc#èàÚúÊ˝˛Ñı¯Ñ·ò@@Ä
˘@Ä
˘˘E9>
˝˛Ñı¯Ñ·
˘ÑÎÑ·¡¡

‡Ã

çD÷R<¨cÕ;‘§jÓIP    •Õíôƒ    JJ”ê    (Õ•-:êìö
kÕÿ»·ƒîb—·D@Œ!˝ÄÀ!˝ÄÀ
!˝Ä…¡¡
˛–¯ÄœÅÄ@PÄœóà≟÷ƒR/Ï∏¨–)JjìJVPëQP–J
&RL¢R¢œbP–{    )îù¥‘ÛÉ£Ú†–Rìàñ‰à颛"° –
˝@

˝@
 ˝
Ä«¡¡ ¿`   
 ê $YrX!     ,¬"• ·
Eº$…  gGÍA  EÙED@‰¿ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˘Ä¿
˘9Ey>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˘¿

˘yEπ>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˘

@
˘πE˘>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˘
@
Ä
˘˘E9>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˘
Ä
¿
˘9Ey>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˘
¿
Ú
˘yE´>
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ¸@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-28    )BCreating and Sending â)YApple Events4^*¿
¯
°dONLNd\lh…(elWhen your handler r퇰dONLNd\…hÛ)]
eturns a rl°dONLNd\Ûh
=)*esult code to the ¶Ä°dONLNd/\
=h
û)JApple Event Managerò°dONLNdB\
ûh
‘)a, you have fiÒ¿°dONLNdO\
‘h
Ù)6nished °dONLNdViluá(rlyour r√`°dONLNd\iáu
)$esponse to the client application’s ™°dONLNdÄi
u
V)óApple event.

|*ó
¯4}*ó
¯

ß*Ø
¯4®*Ø
¯ ©*©
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNdéî*ß<(¢*CrJ9°dONLNdêî<ßÀ)eating and Sending ‚{°dONLNd£î ß÷)é
AΔ+°dONLNd§î◊ß
+)pple EventsˇˇˇˇˇˇU˛(¢

3
°dONLNd±∏lƒr(¡l
Y@Ä°dONLNd≤∏rƒ€)our application can use W†°dONLNd ∏€ƒ
')iApple events to r\@°dONLNd€∏
'ƒ
∂)L!equest services or information frJ@°dONLNd¸∏
∂ƒ
‡)è    om other °dONLNd
≈l—ù(Œlapplication6‡°dONLNd
≈û—
⁄)2Js, send information to other applications, or trigger actions within your °dONLNd
Z“lfi≠(€lapplication. Fo;Ä°dONLNd
i“ÆfiÈ)Br example, yo- °dONLNd
v“Ífiˆ)<u c$Ä°dONLNd
y“˜fi
)an u‡°dONLNd
|“
fi
3)use the cor¿°dONLNd
á“
4fi
;)0e ˜°dONLNd
â“
:fi
ß)Apple event Get Data to ¶`°dONLNd
°“
®fi
´)n
rk`°dONLNd
¢“
¨fi
Á)equest specifi`°dONLNd
∞“
Ëfi
Ó)<c °dONLNd
≤fllÎâ(Ëldata frw°dONLNd
πflâÎ
*)"om another application’s documents    Ä°dONLNd
€fl
+Î
X)¢. Similarly$¿°dONLNd
Êfl
WÎ
¨),, you can use other g°dONLNd
˙fl
¨Î
≥)U
A.@°dONLNd
˚fl
¥Î
‚)
pple event±¿°dONLNdfl
‚Î
Û).s to °dONLNd
Ïl¯o(ıl
rE°dONLNdÏp¯â)equesµÄ°dONLNdÏ⯪)t services—v†°dONLNdϺ¯
Ô)3Hfor example, asking a spell-checking application to check the text in a °dONLNdc˘l
£(
ldocument crÔ@°dONLNdn˘£

N)7'eated by your application. Consult the ÷¿°dONLNdï˘
O

Î)¨%Apple Event Registry: Standard SuitesƒÄ°dONLNd∫˘
Ï

Ó)ù
 °dONLNdª
l

#(
l*for the format and function of the standar?`°dONLNdÂ

$

,)∏d |¿°dONLNdÁ

,

|)Apple events that Z†°dONLNd˘

}

©)Q    you want — °dONLNd

©

Ï),your applicatio5°dONLNd

Ì

ı)Dn °dONLNd
l
{(
lto sÙ‡°dONLNd
{
ã)end´†°dONLNd
å
ë). °dONLNd
%l
1r(
.l
Tµ¿°dONLNd
%q
1
_)3o communicate with another application by sending aÍ`°dONLNdQ
%
_
1
g)Ón ›`°dONLNdS
%
g
1
π)Apple event, your °dONLNde
2l
>ù(
;lapplication6‡°dONLNdp
2û
>†)2
 ∂‡°dONLNdq
2†
>∂)must,Zapf Dingbats°dONLNdv
Hl
Oq(
Nl
n
°dONLNdx
Ex
Q¨)set the appro†°dONLNdÑ
E¨
Q”)4    opriate fl[°dONLNdé
E‘
Q˝)(ags in its ,
Courier»†°dONLNdô
E˝
Q
))
'»@°dONLNdö
E

Q
)SIZEΔ¿°dONLNdû
E

Q
!)
'Δ`°dONLNdü
E
!
Q
') r`°dONLNd°
E
(
Q
@)esourS†°dONLNd¶
E
@
Q
I)ce°dONLNd©
Zl
aq(
`l
n
°dONLNd´
Wx
cÄ)crµ@°dONLNd≠
WÄ
c°)eate an ˝‡°dONLNdµ
W°
cŸ)!Apple event »†°dONLNd¡
W⁄
c›)9
r熰dONLNd¬
Wfi
c)ecor°dONLNdΔ
WÒ
c˘)d ù¿°dONLNd»
W˘
c
6)by calling the õ¿°dONLNd◊
W
7
c
£)>AECreateAppleEventï°dONLNdÈ
W
£
c
 )l     function°dONLNdÛ
ll
sq(
rl
n
°dONLNdı
ix
uâ)use Ø`°dONLNd˘
iâ
u
Ô)NApple Event Manager functions to add parameters and any additional attributes °dONLNdG
ux
Åì(
~xto the ∂‡°dONLNdN
uì
Å…)Apple event°dONLNdZ
äl
ëq(
êl
n
°dONLNd\
áx
ìö)    call the û`°dONLNde
áö
ìæ)"AESendú °dONLNdk
áæ
ì
)$ function to send the U°dONLNdÅ
á

ì
Q)]Apple event°dONLNdç
úl
£q(
¢l
n
°dONLNdè
ôx
•
)%dispose of any copies of descriptor rË¿°dONLNd¥
ô

•
))üecor] °dONLNd∏
ô
*
•
~)ds that you have cré@°dONLNdÀ
ô
~
•
ï)Teated°dONLNd—
Æl
µq(
¥l
n
°dONLNd”
´x
∑≠)handle the r퇰dONLNdfl
´≠
∑¬)5eply ˜¿°dONLNd‰
´¬
∑
1)Apple event (if necessary£@°dONLNd˝
´
2
∑
5)p
)°dONLNdˇ
ºl
»
î(
≈lCThe sections that follow describe how your application can use the ~`°dONLNdB
º
î
»
Œ(
≈
îApple Event °dONLNdN
…l
’
Q(
“l2Manager to accomplish these tasks. The chapter “Crfi¿°dONLNdÄ
…
Q
’
©)Âeating and Sending Å¿°dONLNdì
…
©
’
˜)XApple Events” in °dONLNd§
÷l
‚°(
fllthis book prÇ°dONLNd∞
÷°
‚
B)5$ovides detailed information about crΩ†°dONLNd‘
÷
B
‚
ò)°eating and sending ]‡°dONLNdÁ
÷
ô
‚
÷)WApple events.°dONLNdı
Ël
Ùr(
Òl
Tµ¿°dONLNdˆ
Ëq
Ù
3)/o act as a server for your application, the tarÆ°dONLNd%
Ë
3
Ù
‰)¬(get application must support high-level °dONLNdM
ıl
»(
˛levents and must be rÅ¿°dONLNda
ı»

≈)\8unning. The server can be your own application, another °dONLNdôl§(lapplication rïÄ°dONLNd¶§˜)8unning on the userÍ@°dONLNd∏¯
,)T’s computerr¿°dONLNd√
,
Ç)4, or an application r¡¿°dONLNdÿ
Ç
È)Vunning on another userP°dONLNdÓ
Î
Ù)i’s °dONLNdÒl
(l#computer connected to the network. °dONLNd!l-r*
Y@Ä°dONLNd!r-
Á)Tour application should also allow the user to choose among the various applications °dONLNdj.l:Ÿ(7lavailable as servers. The B °dONLNdÑ.⁄:
)n
PPCBrowser>`°dONLNdé.
:
´)<$ function allows users to select taré¿°dONLNd≤.
´:
Û)ïget applications °dONLNd√;lG
¨(DlEon their own computers or on computers connected to the network. The ∞ °dONLNd;
¨G
Ë(D
¨
PPCBrowser¨`°dONLNd;
ËG
Í)<
 °dONLNdHlTù(Qlfunction pr’`°dONLNdHùT„)1esents a standar'‡°dONLNd.H‰T
x)G#d user interface for choosing a tar°dONLNdQH
xT
ˆ)îget application, much as the °dONLNdnUlaé(^lStandar¥@°dONLNduUéa⁄)"d File Package pr¢`°dONLNdÜU⁄a
")Lovides a standar˙`°dONLNdñU
"a
ÿ)H)d user interface for opening and saving fi °dONLNd¿U
Ÿa
È)∑les. °dONLNd≈bln¿(klSee the chapter “Pr¡`°dONLNdÿb¿nˆ)Togram-to-Pr∫‡°dONLNd„bˆn
j)6ogram Communications T– °dONLNd˘b
in
Û)s!oolbox” in this book for details °dONLNd    ol{•(xlon using the ±@°dONLNd    'o•{·)9
PPCBrowser≠Ä°dONLNd    1o·{
)<
 function.ˇA@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äCreating and Sending â)YApple Events

, (‡3-29
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh
(eä#If the server application is on a r”†°dONLNd#\
h)é7emote computer on a network, the user of that computer °dONLNdZiäu«(rämust allow pr>‡°dONLNdgi»u)>Logram linking to the server application. The user of the server application °dONLNd≥väÇ
}(ä9does this by selecting the application icon in the Finder @°dONLNdÏv
|Ç
◊)Ú, choosing Sharing fr‚@°dONLNd

v
ׂ
¯)[om the °dONLNd
Éäèú(åäFile )Ä°dONLNd
Éùè
)menu, then clicking the ÷†°dONLNd
%É
è
R)iAllow Remote Pr÷‡°dONLNd
4É
Rè)L(ogram Linking checkbox. If the user has °dONLNd
\êäú÷(ôänot yet started prÖ@°dONLNd
nê÷ú
Ü)L%ogram linking, the Sharing command of@°dONLNd
ìê
áú
ÿ)±fers to display the °dONLNd
ßùä©Æ(¶äSharing L†°dONLNd
ØùØ©·)%Setup contr‡ °dONLNd
∫ù·©
~)2&ol panel so that the user can start prg°dONLNd
‡ù
©)ûogram linking. The user must °dONLNd
˝™ä∂Œ(≥äalso authorize r‡°dONLNd™œ∂
)Eemote users for prtÄ°dONLNd™
∂
 )P%ogram linking by using the Users & Gr‡°dONLNdD™
 ∂
˘)´
oups contr‡ °dONLNdN™
˘∂)/ol °dONLNdQ∑ä√±(¿ä    panel. Pr‘ °dONLNdZ∑±√
¢)'6ogram linking and setting up authenticated sessions ar醰dONLNdê∑
£√
Û)Úe described in the °dONLNd£ƒä–º(Õächapter “Pr°dONLNdÆƒΩ–Û)3ogram-to-Pr
Ä°dONLNdπƒÛ–
g)6ogram Communications T¿°dONLNdœƒ
f–
¡)soolbox” in this book.

ıH¸4ˆH¸ ˜ä˜

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdÂÊäıì(Òä
Cwé°dONLNdÊÊîı‘)
reating an J(°dONLNdÒÊ‘ıÔ)@ApplΩÄ°dONLNdıÊÔı

)e Ev0ÿ°dONLNd˘Ê
ı
)ent9‚°dONLNd¸Ê
ı
N) Recordˇˇˇˇˇˇ€r)
3
°dONLNd¸ä
≠(
äUse the ,
Courier+@°dONLNd¸Æ

)$AECreateAppleEvent$Ä°dONLNd¸


W)l function to crü‡°dONLNd.¸
W

x)=eate an ËÄ°dONLNd6¸
x

¥)!Apple event rx@°dONLNdC¸
µ

«)=ecorφ°dONLNdG¸
«

ˇ)d. Using the °dONLNdT
    ä
í(
äarE°dONLNdV
    ì


)    guments you pass to the f¿°dONLNdn
    



m)nAECreateAppleEvent`°dONLNdÄ
    
m

©)l function, the Ì@°dONLNdè
    
©
)<Apple Event Manager °dONLNd£
ä
"•(
äconstrï °dONLNd©
•
"Î)ucts the data str•`°dONLNd∫
Î
"
)Fuctur+@°dONLNdø


"
Ô)8es describing the event class, the event ID, and the tarÖÄ°dONLNd˜

Ô
"
ˇ)Ïget °dONLNd˚
#ä
/ü(
,äaddr|Ä°dONLNdˇ
#ü
/Ù)ess attributes of an 4°dONLNd
#Ù
/)UCApple event. The event class and event ID, of course, identify the °dONLNdW
0ä
<
B(
9ä*particular event you wish to send. The tar`°dONLNdÅ
0
C
<
h)πget addr°dONLNdâ
0
h
<
ó)%ess identifiπ@°dONLNdï
0
ó
<
´)/es thS†°dONLNdö
0
¨
<
·)e intended rzÄ°dONLNd¶
0
·
<)5ecipient of °dONLNd≤
=ä
Iç(
Fä
t¬`°dONLNd≥
=ç
Iö)he °dONLNd∂
=ö
I–)Apple event…¿°dONLNd¡
=–
I“)6
.°dONLNd√
Oä
[ê(
Xä
Y@Ä°dONLNdƒ
Oê
[
R)-ou can specify two other attributes with the ˇÄ°dONLNdÒ
O
R
[
æ)¬AECreateAppleEvent¯¿°dONLNd
O
æ
[
˙)l function: the °dONLNd
\ä
hç(
eä
rE°dONLNd
\é
h°)eplyà@°dONLNd
\°
h£)
 @°dONLNd
\§
h
>)$ID and the transaction ID. For the r… °dONLNd<
\
>
h
ı)ö+eply ID attribute, you usually specify the °dONLNdg
iä
u
(
räkAutoGenerateReturnIDx °dONLNd|
i

u
M)~ constant to the W†°dONLNdç
i
N
u
∫)FAECreateAppleEventP‡°dONLNdü
i
∫
u
¸)l function. This °dONLNdØ
vä
Ç (
äconstant ensurÓ`°dONLNdΩ
v 
Ǣ)@es that the J °dONLNd…
v˙
Ç
∑)0(Apple Event Manager generates a unique r °dONLNdÒ
v
∏
Ç
ˇ)æeturn ID for the °dONLNd
Éä
èç(
åä
rE°dONLNd
Éé
è£)eply ©‡°dONLNd
É£
èfl)Apple event r9†°dONLNd
ɇ
è
)=
eturned frè°dONLNd
É

è
H),om the serverT@°dONLNd,
É
H
è
Ê)<&. For the transaction ID attribute, yoi°dONLNdR
É
Ê
è
Ù)ûu u˜@°dONLNdU
É
Ù
è)sually °dONLNd\
êä
úº(
ôäspecify the °¿°dONLNdh
êº
ú
")2kAnyTransactionIDõ`°dONLNdy
ê
"
ú
Ω)f% constant, which indicates that this `°dONLNdû
ê
Ω
ú
¯)õApple event i °dONLNd´
ê
˘
ú)<s not °dONLNd±
ùä
©è(
¶ä
oıÄ°dONLNd≤
ùè
©Í)ne of a series of inter@°dONLNd…
ùÎ
©
)\
dependent ≥Ä°dONLNd”
ù

©
V)1Apple events;@°dONLNdfl
ù
W
©
Y);
.


ŒH
’4
œH
’ 
–ä
–

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd·
øä
θ(
 äAdding 7Ç°dONLNdË
ø∏
Œ
).Apple Event "J°dONLNdÙ
ø

Œ
§)MAttributes and Parametersˇˇˇˇˇˇ€r(
 
3
°dONLNd
ڊ
Êù(
„äThe ]`°dONLNd
⁄ù
ÊŸ)Apple event rÌ °dONLNd 
⁄Ÿ
ÊÎ)<ecoraÄ°dONLNd$
⁄Ï
ʸ)d cr2İdONLNd(
⁄˝
Ê
>)eated with the ‘`°dONLNd7
⁄
>
Ê
™)AAECreateAppleEventÕ†°dONLNdI
⁄
™
Ê
˝)l function serves as ø°dONLNd]
⁄
˛
Ê)Ta °dONLNd_
Áä
Û¡(
äfoundation fÉ °dONLNdk
Á¡
Û›)7or the j@°dONLNdr
Á›
Û
d)Apple event you want to send.W °dONLNdè
Á
e
Û
ú)à Descriptor r◊‡°dONLNdú
Á
ú
Û
Æ)7ecorL@°dONLNd†
Á
Ø
Û)ds and descriptor lists °dONLNd∏
Ùäí(
˝äarE°dONLNd∫
Ùì¯)    e the building blocks fr͇°dONLNd“
Ù¯
a)eom which the complete †°dONLNdË
Ù
b
û)jApple event r`°dONLNdı
Ù
ü
±)=ecorÉ¿°dONLNd˘
Ù
±
fi)d is constr⁄°dONLNd
Ù
fi
)-ucted. TƇ°dONLNd
Ù
)#o °dONLNd
äí(
äcrµ@°dONLNd
íŸ)eate descriptor rj °dONLNd!
⁄Ï)HecorfiÄ°dONLNd%
Ï)Dds and descriptor lists and add items to a descriptor list, use the °dONLNdiä‚(äfollowing functions:
    °dONLNd~'ä2Ø*Function°dONLNdá'Ê2
)\Description
°dONLNdî5äA“(>äAECreateDesc°dONLNd°5ÊAÏ)\
Tµ¿°dONLNd¢5ÎA)Dakes a descriptor type and a pointer to data and converts them into °dONLNdÊ@ÊL
!(IÊa descriptor r_@°dONLNdÙ@
!L
3);ecor”†°dONLNd¯@
3L
9)
d°dONLNd˚Pä\“(YäAECreateList°dONLNd    PÊ\Ò)\Cr\°dONLNd
PÒ\
Å)"eates an empty descriptor list or %`°dONLNd    ,P
Å\
ï)êAE rM`°dONLNd    0P
ï\
ß)ecor¡¿°dONLNd    4P
ß\
Ø)d.°dONLNd    8`äl∫(iäAEPutPtr°dONLNd    A`ÊlÏ)\
Tµ¿°dONLNd    B`Îl
˛)?akes a descriptor type and a pointer to data and adds the data °dONLNd    ÅkÊwÓ(tÊto7‡°dONLNd    ÉkÔwÒ)    
 ∑‡°dONLNd    ÑkÒwˆ)
a∑‡°dONLNd    Ökˆw¯)
 7‡°dONLNd    Ük˘w
)!descriptor list as a descriptor r>Ä°dONLNd    ßk
w
ë)Üecor≤‡°dONLNd    ´k
ëw
˚)d; used, for example, to °dONLNd    ƒvÊǘ(Êadd∑Ä°dONLNd    «v˜Ǣ)
 7Ä°dONLNd    »v˙Ç
r)to a descriptor list a numbe◊Ä°dONLNd    ‰v
rÇ
~)xr uQ@°dONLNd    Áv
Ç
ı)sed as the parameter of an [`°dONLNd
v
ıÇ)vApple °dONLNd
ÅÊç
(äÊevent r@°dONLNd
Å
ç
l)equesting a calculation.°dONLNd
)ëäù¿(öä    AEPutDesc°dONLNd
3ëÊù
;)\Adds a descriptor r°dONLNd
Fë
<ù
N)Vecorè`°dONLNd
Jë
Nù
ˇ)+d to a descriptor list; used, for example, °dONLNd
uúÊ®Ó(•Êto7‡°dONLNd
wúÔ®Ò)    
 ∑‡°dONLNd
xúÒ®
~)#add to a descriptor list an alias r5¿°dONLNd
õú
®
ë)éecor™ °dONLNd
üú
ë®
ü)d uM°dONLNd
¢ú
†®
⁄)sed as the dir“‡°dONLNd
∞ú
⁄®
Ë):ect °dONLNd
¥ßÊ≥
.(∞Êparameter of an Õ`°dONLNd
ħ
.≥
j)HApple event r] °dONLNd
—ß
k≥
û)=equesting fi†°dONLNd
ݧ
û≥
Ê)3le manipulation.ˇ%¯@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-30    )BCreating and Sending â)YApple Events4^*¿
¯
°dONLNd\lhr(el
Tµ¿°dONLNd
\qh†)o add the rÖ °dONLNd\°h
ï)06emaining attributes and parameters necessary for your ƒ†°dONLNdB\
ïh
È)ÙApple event to the °dONLNdUilu®(rlApple event r¿°dONLNdbi©uª)=ecorÑ °dONLNdfiªu—)d, yo§Ä°dONLNdki—uÒ)u can uÙ`°dONLNdriÒu
E) se these additional zÄ°dONLNdÜi
Fu
’)UApple Event Manager functions:°dONLNd&
 l
÷s(
”l
AG@°dONLNd'
 t
÷ˆ)pple event parameters for corÄ°dONLNdD
 ˆ
÷
h)Çe events and functional-arP°dONLNd^
 
i
÷
…)sea events can include °dONLNdt
◊l
„Ø(
‡ldescriptions of     `°dONLNdÑ
װ
„
h)D+Apple event objects in special descriptor rƒ°dONLNdØ
◊
h
„
z)∏ecor8`°dONLNd≥
◊
{
„
›)ds called object specifiu¿°dONLNdÀ
◊
›
„
Ë)ber °dONLNdŒ
‰l
o(
Ìl
rE°dONLNdœ
‰p
Ç)ecorπ`°dONLNd”
‰Ç

 )$ds. For an overview of object specifiȆ°dONLNd¯
‰
 

/)ûer r͇°dONLNd¸
‰
/

A)ecor_@°dONLNd
‰
B

a)ds, see @°dONLNd
‰
b

q) “W@°dONLNd

‰
p

ô)orking WP¿°dONLNd
‰
ô

„))ith Object SpecifiÙ@°dONLNd$
‰
„

Ó)Jer °dONLNd'
Òl
˝Ö(
˙lRecor¢`°dONLNd,
ÒÖ
˝ñ)ds,”{ °dONLNd0
Òó
˝‰) which begins on ÎÄ°dONLNdA
Ò‰
˝˚)Mpage Δ`°dONLNdF
Ò¸
˝
)3-32@°dONLNdJ
Ò

˝
)
.

"*)
¯4#*)
¯ $l$
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdLl"µ(lSending an °dONLNdW¥"
ê)H"Apple Event and Handling the Replyˇˇˇˇˇˇ€r(

3
°dONLNd{)l5
B(2l1After you add all the attributes and parameters rB¿°dONLNd¨)
C5
Z)◊equirZ°dONLNd±)
Z5
Ü)ed for the ˙`°dONLNdº)
Ü5
„),Apple event, use the ,
Courier°dONLNd—6lBê(?lAESend}¿°dONLNd◊6êBÌ)$ function to send the 6†°dONLNdÌ6ÌB
;)]Apple event. The ^¿°dONLNd˛6
;B
≈)NApple Event Manager uses the °dONLNdClOÖ(LlEvent`°dONLNd CÜOà)
 ü`°dONLNd!CàOı)Manager to transmit the ™`°dONLNd9CıO
õ)m&Apple event to the server application.°dONLNd`Ula(^lThe ª¿°dONLNddUa£)AESendπÄ°dONLNdjU£a—)$ function rå¿°dONLNduU—aË).equir§°dONLNdzUËa
])es that you specify whethe @°dONLNdîU
^a
j)vr y"°dONLNdóU
ja
ˆ) our application should wait for °dONLNd∑blnw(kla r≈°dONLNd∫bwnî)eply fr° °dONLNd¡bînÃ)om the serve1 °dONLNdÕbÕn–)9
rf`°dONLNdŒb–n“)
.Ê`°dONLNdœb“n
^)! If you specify that you want a rzÄ°dONLNdb
_n
r)çeply¢°dONLNdÙb
qn
Ü), the °°dONLNd˙b
Ün
Í)Apple Event Manager °dONLNd    ol{u(xlprG °dONLNd    ov{â)
epar◊‡°dONLNd    oâ{ü)es a r£Ä°dONLNd    o†{µ)eply `°dONLNd    o∂{
®)7Apple event for your application by passing a default r–@°dONLNd    Vo
®{
Ω)Úeply 5 °dONLNd    [o
æ{
ˆ)Apple event °dONLNd    g|là¢(Ölto the server≥†°dONLNd    t|¢à∫)6. The ë°dONLNd    z|∫à
")Apple Event Manager rч°dONLNd    è|
"à
r)heturns any nonzer†`°dONLNd    †|
rà
})Po rZ‡°dONLNd    £|
~à
¥)esult code frw`°dONLNd    ∞|
¥à
’)6om the °dONLNd    ∑âlïá(ílserverô °dONLNd    Ωâàï—)’s handler in the ó†°dONLNd    œâ“ï
&)JkeyErrorNumberí`°dONLNd    ›â
&ï
x)T parameter of the rè °dONLNd    â
xï
ç)Reply Ù°dONLNd    ıâ
çï
»)Apple event. °dONLNd
ñl¢|(ülThe;¿°dONLNd
ñ}¢)
 ª¿°dONLNd
ñ¢≤)server can r °dONLNd
ñ≥¢Á)4eturn an errG‡°dONLNd
ñÁ¢
*)4or string in the °dONLNd
/ñ
+¢
)DkeyErrorString¸¿°dONLNd
=ñ
~¢
–)S parameter of the r˘Ä°dONLNd
Pñ
–¢
Â)Reply °dONLNd
U£lØ
$(¨l*Apple event. The server can also use the rn‡°dONLNd
£
$Ø
9)∏eply ”¿°dONLNd
Ñ£
9Ø
Ä)Apple event to rõ`°dONLNd
î£
ÅØ
◊)Heturn any data you °dONLNd
ß∞lºo(πl
rE°dONLNd
®∞pºÔ)equested—for example, the r∂°dONLNd
√∞Ôº
>)esults of a numeriΔ°dONLNd
’∞
>º
I)Oc c&Ä°dONLNd
ÿ∞
Jº
Í)&alculation or a list of misspelled wor´†°dONLNd
˛∞
ͺ
ˆ)†ds.
    °dONLNd•Çlçë(älFunctiony@°dONLNdÆÇÏç
)ÄDescription
°dONLNdªêlú∫(ôlAEPutParamPtry@°dONLNd…êÏúÚ)Ä
TØ°dONLNd êÒú
0)akes a keyworæ °dONLNd◊ê
0ú
Ì)?,d, descriptor type, and pointer to data and y@°dONLNd
õÏß
B(§Ïadds the data to an ‘ °dONLNd
õ
Bß
~)VApple event rc‡°dONLNd
$õ
ß
ë)=ecorÿ@°dONLNd
(õ
ëß
Û)d as a parameter with y@°dONLNd
>¶Ï≤
(ØÏ
the specifiD¿°dONLNd
I¶
≤
H)-    ed keywor#Ä°dONLNd
R¶
H≤
W)/d (rÿ °dONLNd
V¶
W≤
Á) eplacing any existing parameter y@°dONLNd
v±ÏΩ
N(∫Ïwith the same keywor}¿°dONLNd
ä±
NΩ
Õ)bd); used, for example, to put y@°dONLNd
®ºÏ»
Ü(≈Ï"numbers into the parameters of an °dONLNd
 º
á»
È)õApple event that asks y@°dONLNd
‡«Ï”
Ü(–Ï$the server to perform a calculation.°dONLNd◊l„¿(‡lAEPutParamDescy@°dONLNd◊Ï„Ú)Ä
TØ°dONLNd◊Ò„
0)akes a keyworæ °dONLNd#◊
0„
á)?d and a descriptor r¶@°dONLNd7◊
á„
ô)Wecor†°dONLNd;◊
ö„
fi)d and adds the y@°dONLNdJ‚ÏÓ
(ÎÏdescriptor rÿÄ°dONLNdV‚
Ó
1)3ecorL‡°dONLNdZ‚
2Ó
S)d to an Ä°dONLNdb‚
SÓ
è)!Apple event r£@°dONLNdo‚
èÓ
°)<ecor†°dONLNds‚
¢Ó
Ì)d as a parameter y@°dONLNdÑÌÏ˘
/(ˆÏwith the specifi‡°dONLNdîÌ
0˘
_)D    ed keyworˆ†°dONLNdùÌ
^˘
m).d (r´@°dONLNd°Ì
n˘
Õ)eplacing any existing y@°dONLNd∑¯Ï

~(

Ïparameter with the same keyworé¿°dONLNd’¯
~

Î)íd); used, for example, to y@°dONLNdÔ
Ï

ò(
Ï*place a descriptor list containing alias r÷‡°dONLNd

ò

™)¨ecorK@°dONLNd

´

‹)ds into the y@°dONLNd)
Ï
¯(
ÏdirB`°dONLNd,
˘

P)ect parameter of an å°dONLNd@

P

†)WApple event that rÒ‡°dONLNdR

†

Ù)Pequests a server to y@°dONLNdf
Ï
%
'(
"Ïmanipulate fië`°dONLNds

'
%
5);les.°dONLNdy
)l
5“(
2lAEPutAttributePtry@°dONLNdã
)Ï
5Ú)Ä
TØ°dONLNdå
)Ò
5
0)akes a keyworæ °dONLNdô
)
0
5
Ì)?,d, descriptor type, and pointer to data and y@°dONLNd≈
4Ï
@
G(
=Ïadds the descriptor r*`°dONLNd⁄
4
H
@
Z)\ecorû¿°dONLNdfi
4
Z
@
{)d to an e`°dONLNdÊ
4
{
@
∑)!Apple event rı °dONLNdÛ
4
∑
@
…)<ecoriÄ°dONLNd˜
4
 
@
fi)d as y@°dONLNd¸
?Ï
Kˆ(
HÏanJ†°dONLNd˛
?˜
K˘)
  †°dONLNdˇ
?˘
K
e)attribute with the specifi„¿°dONLNd
?
e
K
î)l    ed keywor¬Ä°dONLNd"
?
î
K
£)/d (rw °dONLNd&
?
§
K
fi)eplacing any y@°dONLNd3
JÏ
V
õ(
SÏ'existing attribute with the same keywor °dONLNdZ
J
ú
V
”)∞d); used, for y@°dONLNdh
UÏ
a
L(
^Ïexample, to change th+°dONLNd}
U
M
a
õ)ae transaction ID o+ °dONLNdè
U
õ
a
Æ)Nf an Ú°dONLNdî
U
≠
a
Â)Apple event y@°dONLNd†
`Ï
lÔ(
iÏ
r>@°dONLNd°
`
l
)ecor≤†°dONLNd•
`

l
v)d that is waiting to be sent8°dONLNd¡
`
w
l
|)u. °dONLNd≈
pl
|ÿ(
ylAEPutAttributeDescy@°dONLNdÿ
pÏ
|Ú)Ä
TØ°dONLNdŸ
pÒ
|
0)akes a keyworæ °dONLNdÊ
p
0
|
á)?d and a descriptor r¶@°dONLNd˙
p
á
|
ô)Wecor†°dONLNd˛
p
ö
|
Õ)d and adds y@°dONLNd    
{Ï
á˘(
ÑÏtheV†°dONLNd
{˙
á¸)
 ÷†°dONLNd
{¸
á
/)descriptor r5‡°dONLNd
{
0
á
B)4ecor™@°dONLNd
{
B
á
c)d to an p‡°dONLNd%
{
c
á
ü)!Apple event r†°dONLNd2
{
†
á
≤)=ecoru°dONLNd6
{
≤
á
”)d as an y@°dONLNd>
ÜÏ
í
X(
èÏattribute with the specifií`°dONLNdX
Ü
X
í
á)l    ed keyworq °dONLNda
Ü
á
í
ñ)/d (r%¿°dONLNde
Ü
ó
í
—)eplacing any y@°dONLNdr
ëÏ
ù
(
öÏexisting °dONLNdz
ë

ù
)#
 ú °dONLNd{
ë

ù
õ)attribute with the same keywor °dONLNdô
ë
ú
ù
”)ãd); used, for y@°dONLNdß
úÏ
®
%(
•Ïexample, to rÄ°dONLNd¥
ú
%
®
á)9eplace the descriptor r °dONLNdÀ
ú
à
®
ö)cecorèÄ°dONLNdœ
ú
ö
®
Ê)d used for the taruÄ°dONLNd·
ú
Ê
®
ˆ)Lget y@°dONLNdÂ
ßÏ
≥

(
∞Ïaddru¿°dONLNdÈ
ß


≥
Q)ess attribute in an ‡†°dONLNd˝
ß
Q
≥
ç)PApple event rp`°dONLNd

ß
é
≥
†)=ecor‰¿°dONLNd
ß
†
≥
‰)d waiting to be y@°dONLNd
≤Ï
æ
(
ªÏsent.ˇB2@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡äCreating and Sending â)YApple Events

, (‡3-31
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähê(eä
Y@Ä°dONLNd
\êh
s)3ou specify how your application should wait for a rfÄ°dONLNd4\
sh
Ó)„eply by using one of these fl °dONLNdQ\
Ôh)|ags in °dONLNdXiäuö(räthe ,
Courier›`°dONLNd\iöu )sendMode⁄`°dONLNddi u
)0 parameter of the  °dONLNdvi
u
=)OAESend‡°dONLNd|i
=u
g)$
 function:°dONLNdΩ

ä
ÿ(
äIf you specify the _‡°dONLNd–

Ÿ

!)OkAEWaitReply[`°dONLNd‹


!

))H flË °dONLNdfl


)

C)ag, yo{‡°dONLNdÂ


D

s)
u should p@°dONLNdÔ


t

w)0
rŸ@°dONLNd


w

Ú)ovide an idle function. This °dONLNd
ä
#‹(
 äfunction should pr‰Ä°dONLNd
‹
#
)REocess any non-high-level events that occur while your application is °dONLNdd
$ä
0»(
-äwaiting for a rK†°dONLNds
$…
0‹)?eplys °dONLNdw
$€
0‡). EÄ°dONLNdy
$‡
0Ê)
Y°dONLNdz
$Ê
0
˚)@ou supply a pointer to your idle function as a parameter to the °dONLNd∫
1ä
=Æ(
:äAESend}¿°dONLNd¿
1Æ
=
c)$* function. So that your application can prU`°dONLNdÍ
1
c
=
ñ)µocess other e‡°dONLNdˆ
1
ñ
=)3Apple events while it is °dONLNd
>ä
J»(
Gäwaiting for a rK†°dONLNd
>…
J‹)?eplys °dONLNd"
>€
J
u)$, you can also specify an optional fiOÄ°dONLNdG
>
v
J
 )õlter function to the ⁄°dONLNd\
>
 
J
Ó)TAESend◊¿°dONLNdb
>
Ó
J
)$
 °dONLNdc
Kä
W±(
Tä    function.°dONLNdm
]ä
iÿ*If you specify the _‡°dONLNdÄ
]Ÿ
i
)O
kAENoReply\ °dONLNdä
]

i
)< flˇ°dONLNdç
]

i
@)    ag, the rö`°dONLNdñ
]
A
i
V)$eply ˇ@°dONLNdõ
]
V
i
ò)Apple event prë °dONLNd©
]
ô
i
¨)Cepar!‡°dONLNd≠
]
≠
i
ÿ)
ed by the °dONLNd∑
]
ÿ
i)+Apple Event °dONLNd√
jä
v
•(
säBManager for the server application consists of a null descriptor r®¿°dONLNd
j
•
v
∑(
s
•ecor °dONLNd    
j
∏
v
¿)d.°dONLNd
|ä
à™(
ÖäIf your “`°dONLNd
|™
à¸) Apple event may rE@°dONLNd%
|˝
à
)Sequir\Ä°dONLNd*
|

à
È)3e the user to interact with the server application °dONLNd]
âä
ïö(
íä(for臰dONLNda
âö
ïú)
 ‡°dONLNdb
âù
ï
)example, to specify print or fiÏ@°dONLNdÅ
â

ï
€)Å)le options), you can communicate your useº¿°dONLNd™
â
‹
ï
Â)ær i¿°dONLNd≠
â
Ê
ï)
nteraction °dONLNd∏
ñä
¢ì(
üäprG °dONLNd∫
ñî
¢§)
eferÛ@°dONLNdæ
ñ§
¢
-) ences to the server by specifyinã°dONLNdfi
ñ
.
¢
i)äg additional f∏`°dONLNdÏ
ñ
i
¢
ò);lags in the Ñ°dONLNd¯
ñ
ô
¢
…)0sendModeÅ°dONLNd
ñ
…
¢)0 parameter of °dONLNd
£ä
Øö(
¨äthe ›`°dONLNd
£ö
Øæ)AESend€ °dONLNd
£æ
Øfl)$ functioò°dONLNd 
£‡
Ø
)"
n. These fl∏Ä°dONLNd+
£

Ø
=)-ags specifyI°dONLNd6
£
>
Ø
@)1
 …°dONLNd7
£
@
Ø
ú)the conditions, if anyë@°dONLNdM
£
ú
Ø
)\, under which the server °dONLNdf
∞ä
º
Î(
πäSapplication can interact with the user and, if interaction is allowed, whether the °dONLNdπ
Ωä
…•*server€¿°dONLNdø
Ω•
…ß)
 [¿°dONLNd¿
Ω®
…)should come dir7`°dONLNdœ
Ω
…
/)Hectly to the forŒ¿°dONLNdfl
Ω
/
…
=)?egrÏÄ°dONLNd‚
Ω
=
…
ó)ound or post a notifi3¿°dONLNd˜
Ω
ò
…
π)[cation rZ†°dONLNdˇ
Ω
π
…
ÿ)!equest.°dONLNd
ϊ
€
(
ÿäThe server application specifi<Ä°dONLNd%
œ

€
D)Çes its own pr臰dONLNd2
œ
D
€
T)8efer<°dONLNd6
œ
U
€
æ)ences for user interactioS °dONLNdO
œ
æ
€
À)in b, °dONLNdR
œ
Ã
€)y specifying °dONLNd_
‹ä
Ëê(
Âä
flå¿°dONLNda
‹ê
˺)ags to the n °dONLNdl
‹Ω
Ë
G)-AESetInteractionAllowedeÄ°dONLNdÉ
‹
G
Ë
“)ä! function, as described in the pri†°dONLNd§
‹
“
Ë)ãevious section. °dONLNd¥
Èä
ı
|(
Úä9The interaction of the client and server applications’ prf@°dONLNdÌ
È
|
ı
å)Úefer`°dONLNdÒ
È
ç
ı)ences is explained in detail i‡ °dONLNd
È
ı){n °dONLNd
ˆäÀ(
ˇä“Interacting Wù`°dONLNd
ˆÀ˛)Aith the Userz°dONLNd+
ˆ˛
)3,”˙°dONLNd-
ˆ

R) which begins on j`°dONLNd>
ˆ
S
j)Npage E@°dONLNdC
ˆ
k
})4-45ô °dONLNdG
ˆ
}
)
.°dONLNdIä€(äAfter you send an @°dONLNd[‹
p)R"Apple event, your application is rv†°dONLNd}
p
È)îesponsible for disposing of °dONLNdôä!ó(äthe]`°dONLNdúò!ö)
 °dONLNdùö!÷)Apple event r¿°dONLNd™◊!È)=ecorÉ °dONLNdÆÈ!
)
d—and therÆ`°dONLNd∏
!
ô)5eby deallocating the memorÌ°dONLNd“
ô!
…){y its data u… °dONLNdfi
 !
Ó)1ses—by °dONLNdÂ"ä.ß(+äcalling    ‡°dONLNdÏ"®.™)
 ⇰dONLNdÌ"™.∑)theg@°dONLNd"∏.∫)
 Á@°dONLNdÒ"∫.
)AEDisposeDesc‚`°dONLNd˛"
.
Y)N function. If you crd°dONLNd    "
Z.
¥)Reate one descriptor r©`°dONLNd    '"
¥.
Δ)Zecor¿°dONLNd    +"
«.
)d and add it to °dONLNd    ;/ä;¨(8äanotherŸÄ°dONLNd    B/´;Ω)!, the∂‡°dONLNd    G/æ;¿)
 ÿÄ°dONLNd    H/¿;
ù)/Apple Event Manager adds a copy of the newly cr8`°dONLNd    w/
û;)fieated one to the existing °dONLNd    ë<äHï(EäonΔ‡°dONLNd    ì<ïH°)e aÄ°dONLNd    ñ<¢H≠)nd˝†°dONLNd    ò<≠HØ)
 }†°dONLNd    ô<∞H
a)(also makes a copy of the associated dataÓ°dONLNd    ¡<
aH
k)±. F} °dONLNd    ƒ<
lH
Ù)or example, you might use the °dONLNd    ‚IäU“(RäAECreateDesc{Ä°dONLNd    ÓI“U
)H function to crˆ‡°dONLNd    ˝I
U
^)=eate a descriptor r+¿°dONLNd
I
_U
q)Pecor† °dONLNd
I
qU
)d that you wish to add to an Ö¿°dONLNd
1I
U)Apple °dONLNd
7Väb˘(_äevent. When you use the 0Ä°dONLNd
OV˙b
N)pAEPutParamDesc+@°dONLNd
]V
Nb
˚)T( function, it adds a copy of your newly °dONLNd
Öcäoí(läcrµ@°dONLNd
ácíofl)eated descriptor rÖ‡°dONLNd
ôc‡oÚ)Necor˙@°dONLNd
ùcÚo
J)d, including its dataZ°dONLNd
≤c
Ko
ì)Y, as a parameter ®°dONLNd
√c
ìo
–)Hto an existing ı¿°dONLNd
“c
–o)=
Apple even˛ °dONLNd
‹co)3t.¿Ä°dONLNd
fic    o)
 °dONLNd
flpä|
h(yä1When you no longer need the original descriptor rx`°dONLNdp
h|
z)fiecorÏ¿°dONLNdp
z|
À)d, you should call °dONLNd'}äâÿ(ÜäAEDisposeDesc{ °dONLNd4}ÿâ
)N to disposeÚ`°dONLNd?}
â
    )/
 r`°dONLNd@}

â
)of it.
    °dONLNdáÇäçú(ääFlag°dONLNdåÇÏç
)bDescription
°dONLNdôêäúΔ(ôä
kAENoReply°dONLNd§êÏúÚ)b
Y@Ä°dONLNd•êÚú
Ñ)!our application does not want a r∑Ä°dONLNdΔê
Ñú
ô)íeply `°dONLNdÀê
öú
“)Apple event.°dONLNdŸ†ä¨ÿ(©äkAEQueueReply°dONLNdÁ†Ï¨Ú)b
Y@İdONLNdˆڨ
`)our application wants a r”`°dONLNd

†
`¨
u)neply 8@°dONLNd
†
v¨
≈)Apple event; the r•`°dONLNd
†
≈¨)Oeply appears in °dONLNd
(´Ï∑
˛(¥Ï>your event queue as soon as the server has the opportunity to °dONLNd
f∂Ϭı*prG °dONLNd
h∂ˆ¬
')
ocess and r"†°dONLNd
s∂
'¬
l)1espond to your e‡°dONLNd
Ç∂
l¬
§)EApple event.°dONLNd
êΔä““(œäkAEWaitReply°dONLNd
ùΔÏ“Ú)b
Y@Ä°dONLNd
ûΔÚ“
`)our application wants a r”`°dONLNd
∑Δ
`“
u)neply 8@°dONLNd
ºΔ
v“)#Apple event and is willing to give °dONLNd
fl—Ï›
(⁄Ï    up the pr-¿°dONLNd
Ë—
›
õ))ocessor while waiting for the r+°dONLNd—
õ›)Üeply; for example, if the °dONLNd!‹ÏË(ÂÏ@server application is on the same computer as your application, °dONLNdaÁÏÛ
o*your application yields the pr\°dONLNdÁ
oÛ
Ò)Éocessor to allow the server to °dONLNdûÚÏ˛Ô(˚Ï
rE°dONLNdüÚ˛
5)espond to your à@°dONLNdÆÚ
5˛
m)EApple event.ˇ*b@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-32    )B
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records4^*¿
¯
°dONLNd\lhr(el
Y@Ä°dONLNd
\rh
Y)6our application should dispose of all the descriptor r‡°dONLNd7\
Zh
l)ËecorÄ@°dONLNd;\
lh
ï)
ds that arÙ °dONLNdE\
ïh
§))e crs°dONLNdI\
•h
∂)eateH†°dONLNdM\
∑h
fl)
d for the °dONLNdWilu (rlpurposes of adding p°dONLNdkiÀu
Q)_arameters and attributes to an û`°dONLNdäi
Qu
å)ÜApple event. ªÄ°dONLNdói
åu
í);
Y|°dONLNdòi
íu
Ô)ou normally dispose °dONLNd¨vlÇé(lof your È`°dONLNd¥véÇÎ)"Apple event and its rŒ°dONLNd…vÎÇ
/)]eply after you r¥Ä°dONLNdŸv
/Ç
X)D
eceive a r’@°dONLNd„v
XÇ
v))esult fr¶†°dONLNdÎv
wÇ
ò)om the ,
CourierÕÄ°dONLNdÚv
òÇ
º)!AESendÀ@°dONLNd¯v
ºÇ
Ë)$ function. °dONLNd
Élèr(ål
Y@Ä°dONLNd
Érè

)#ou should dispose of these even if Ä °dONLNd
'É

è
.)òAESend}‡°dONLNd
-É
.è
4)$ r¬‡°dONLNd
/É
4è
l)eturns an err)†°dONLNd
<É
mè
|)9or r÷¿°dONLNd
@É
|è
ñ)esult. °dONLNd
Hïl°o(ûl
IfiÄ°dONLNd
Iïo°∫)f you specify the _‡°dONLNd
[練
)LkAEWaitReply[`°dONLNd
gï
°
)H flË °dONLNd
jï
°
.)    ag, the rô†°dONLNd
sï
/°
D)$eply ˛Ä°dONLNd
xï
D°
ä)Apple event is r3†°dONLNd
àï
ã°
Û)Geturned in a parameter °dONLNd
ü¢lƱ(´lyou pass to the ù °dONLNd
Ø¢±Æ’)EAESendö‡°dONLNd
µ¢’Æ
P)$ function. If you specify the     °dONLNd
Ӣ
QÆ
ü)|kAEQueueReply °dONLNd
‡¢
üÆ
ß)N flꇰdONLNd
„¢
ßÆ
œ)
ag to the 5@°dONLNd
Ì¢
–Æ
Ù))AESend3°dONLNd
Û¢
ÙÆ
ˆ)$
 °dONLNd
ÙØlª™(∏lfunction, the r∞†°dONLNdØ™ªø)>eply Ä°dONLNdØ¿ª
)Apple event is rJ†°dONLNdØ
ª
Ã)F/eturned in the event queue. In this case, the r(`°dONLNdGØ
ê
·)Δeply °dONLNdLºl»s(≈lis•`°dONLNdNºs»u)
 %`°dONLNdOºv»ï)identifi¸°dONLNdWºï»Ú)ed by the event class u`°dONLNdmºÛ»
M)^kCoreEventClasso¿°dONLNd|º
M»
õ)Z and the event ID #@°dONLNdéº
ú»
Ã)OkAEAnswe @°dONLNdñº
û
“)0
rbÄ°dONLNdóº
—»
÷). °dONLNdô…l’r(“l
Y@Ä°dONLNdö…r’w)
o∂°dONLNdõ…w’Ä)urØ¿°dONLNdù…Å’É)

 /¿°dONLNdû…Ñ’¬)application pr-¿°dONLNd¨…¬’Ë)>    ocesses r¢¿°dONLNdµ…Ë’
)&
eply event≥@°dONLNdø…
’
).s iX†°dONLNd¬…
 ’
õ)
n its event queue in the sam¡¿°dONLNdfi…
õ’
∫){e way t≥‡°dONLNdÂ…
ª’
È) hat server °dONLNd÷l‚Æ(fllapplications prª°dONLNdˇ÷Æ‚«)Bocess °dONLNd÷»‚˛)Apple eventP¿°dONLNd÷˛‚
)6s. °dONLNdËlÙr(Òl
Y@Ä°dONLNdËrÙÏ)our application should checÒ@°dONLNd0ËÏÙ
L)zk for the existence of t‘`°dONLNdHË
MÙ
Z)ahe Ô`°dONLNdKË
ZÙ
Æ)keyErrorNumberÍ °dONLNdYË
ÆÙ
Î)T parameter of °dONLNdgıl

Ä(˛lthe r¢`°dONLNdlıÄ

ï)eply @°dONLNdqıñ

Ú)Apple event to ensurÆ°dONLNdÖıÚ


Å)\!e that the server performed the r›°dONLNd¶ı
Å


≈)èequested action◊ °dONLNdµı
Δ


÷)E. Th…@°dONLNdπı
◊


fi)e °dONLNdª
l
á(
lserver€¿°dONLNd¡
á
ò) canù`°dONLNd≈
ô
õ)
 `°dONLNdΔ
ú
∞)also 8@°dONLNdÀ
∞
≥)
r˝@°dONLNdÃ
≥
≈)etur°dONLNd–
Δ
Ï)
n, in the kÄ°dONLNd⁄
Ï
Ú)&
kk °dONLNd€
Ú

@)eyErrorStringf@°dONLNdË

@

l)N     parameteц°dONLNdÒ

l

o),
rπ‡°dONLNdÚ

o

ì)    , any err†°dONLNd˚

î

˜)%or messages you need °dONLNd
l
…(
lto display to the user ‡°dONLNd&
»
 )\
.°dONLNd(
!l
-ˇ(
*l Whenever a server application prÚ@°dONLNdH
!ˇ
-
8)ìovides an errk`°dONLNdU
!
9
-
´):or string, it should also pr™@°dONLNdq
!
´
-
‡)rovide an errÊ`°dONLNd}
!
‡
-
Î)5or °dONLNdÄ
.l
:é(
7lnumber≥°dONLNdÜ
.é
:º)"    . However?†°dONLNdè
.º
:
ı).J, you can’t count on all server applications to do so. The absence of the °dONLNdŸ
;l
G¿(
DlkeyErrorNumberz¿°dONLNdÁ
;¿
G
â)T- parameter doesn’t necessarily mean that theráÄ°dONLNd
;
â
G
Δ)…e won’t an errÀ@°dONLNd"
;
Δ
G
Ó)=
or string °dONLNd,
Hl
Tu(
QlprG °dONLNd.
Hv
T≥)
ovided in the cÄ°dONLNd<
H≥
T
)=keyErrorString^@°dONLNdJ
H

T
7)T
 parameter±‡°dONLNdT
H
6
T
;)/. SÄ°dONLNdV
H
;
T
B)
Aé °dONLNdW
H
B
T
Δ) client application should therdONLNdv
H
Δ
T
◊)Ñeforχ°dONLNdz
H
◊
T
fi)e °dONLNd|
Ul
aΩ(
^lcheck for both the 4‡°dONLNdè
Uæ
a
)RkeyErrorNumber/†°dONLNdù
U

a
')T and ¿°dONLNd¢
U
(
a
|)keyErrorStringÄ°dONLNd∞
U
|
a
…)T parameters befor≈ °dONLNd¡
U
…
a
–)Me °dONLNd√
bl
n«(
klassuming that no errº@°dONLNd◊
b«
n
)[or has occurrGÄ°dONLNd‰
b


n
):ed. If _@°dONLNdÎ
b

n
%)a s@°dONLNdÓ
b
&
n
p)tring has been pr€‡°dONLNdˇ
b
p
n
—)Jovided without an err≈‡°dONLNd
b
—
n
‹)aor °dONLNd
ol
{é(
xlnumber≥°dONLNd
oé
{≠)", an errÖ†°dONLNd%
o≠
{Ê)or has occurr‡°dONLNd2
oÁ
{Ò):edˆ@°dONLNd4
oÒ
{ˆ)
. °dONLNd7
Ål
ç∑(
älAfter extracting t˛‡°dONLNdI
Å∑
ç
')Khe information it needs frV@°dONLNdc
Å
(
ç
M)qom the rB °dONLNdk
Å
M
ç
{)%
eply eventR†°dONLNdu
Å
{
ç
¿)., your handler sÒ °dONLNdÖ
Å
¿
ç
‹)Ehould °dONLNdã
él
öØ(
óldispose of the r+ °dONLNdõ
é∞
ö
)Deply by calling the Ï`°dONLNdØ
é

ö
Q)SAEDisposeDescÁÄ°dONLNdº
é
Q
ö
•)N function. Similarlyë°dONLNd–
é
•
ö
‹)T, when your °dONLNd‹
õl
ßfl(
§lhandler no longer needs d}¿°dONLNdı
õ‡
ß
)tescriptor r¡@°dONLNd
õ

ß
)-ecor5†°dONLNd
õ
 
ß
&)
dQ`°dONLNd
õ
&
ß
y)s it has extracted frü†°dONLNd
õ
y
ß
ç)Som t´Ä°dONLNd
õ
ç
ß
û)he rãÄ°dONLNd"
õ
û
ß
´)epl?†°dONLNd%
õ
¨
ß
±)
y≥°dONLNd&
õ
∞
ß
¡), it sö¿°dONLNd,
õ
¬
ß
÷)houl— °dONLNd0
õ
÷
ß
)d call °dONLNd7
®l
¥∫(
±lAEDisposeDesc{ °dONLNdD
®∫
¥Õ)N to dN¿°dONLNdI
®Œ
¥Ò)ispose oÁ‡°dONLNdQ
®Ò
¥
)#f them.°dONLNdY
∫l
Δ¿(
√lThe next section prq`°dONLNdl
∫¿
Δ
e)T$ovides an overview of the way a sour|°dONLNdê
∫
e
Δ
ƒ)•ce application identifiC`°dONLNdß
∫
≈
Δ
–)`es k†°dONLNd™
∫
–
Δ
Ì)Apple °dONLNd∞
«l
Ӡ(
–levent object`°dONLNdº
«°
”˘)5s supported by a tarP¿°dONLNd–
«˘
”
=)Xget application.¢¿°dONLNd‡
«
=
”
e)D
 If you ar•‡°dONLNdÍ
«
e
”
Ë)(e starting by supporting only °dONLNd
‘l
‡ö(
›l
the Requir¢†°dONLNd
‘ö
‡‚).ed suite and the ,†°dONLNd#
‘„
‡
ù)I(Apple events sent by the Edition Manager©°dONLNdK
‘
ú
‡
Î)π, you can skip the °dONLNd^
·l
Ì≠(
Ílnext section an?‡°dONLNdm
·Æ
̺)Bd gj¿°dONLNdp
·º
Ì–)o dir)`°dONLNdu
·—
ÌÛ)    ectly to ’°dONLNd~
·Û
Ì
&)"“About the a‡°dONLNdâ
·
'
Ì
à)4Apple Event ManagerS`°dONLNdú
·
à
Ì
è)a,””`°dONLNdû
·
è
Ì
‹) which begins on °dONLNdØ
Ól
˙É(
˜lpage Z‡°dONLNd¥
ÓÑ
˙ñ)3-48Æ¿°dONLNd∏
Óñ
˙õ). 


*
¯4*
¯

,*4
¯4-*4
¯ .*.
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNdº*,:('*
WõÇ°dONLNdΩ9,})orking Wˆ≠°dONLNd≈|,†)Cith OD/°dONLNd °,ı)%bject Specifi!®°dONLNd◊ˆ,
1)Uer RecorE°dONLNdfl
1,
A);dsˇˇˇˇˇˇU˛)ø
3
°dONLNd„=lI¡(FlMost of the standarB`°dONLNdˆ=¬I )Vd ¿°dONLNd¯= I
F)Apple events allow the sourÄ¿°dONLNd    =
FI
ï)|ce application to rn`°dONLNd    &=
ïI
•)Oeferä¿°dONLNd    *=
•I
¬), in an ∑Ä°dONLNd    2=
¬I
fl)Apple °dONLNd    8JlV¥(Slevent parameter ‡°dONLNd    GJ¥Vƒ)H, to ˙`°dONLNd    LJ√V
X)"Apple event objects within the tarC‡°dONLNd    nJ
YV
Ï)ñ"get application or its documents. °dONLNd    êWlc(`lThe ]`°dONLNd    îWc
a)1Apple Event Manager allows applications to constrß`°dONLNd    ≈W
ac
£)‚uct and interprÕ¿°dONLNd    ‘W
£c
»)B    et such r$Ä°dONLNd    ›W
…c
Ÿ)&efer–†°dONLNd    ·W
Ÿc
Û)ences °dONLNd    ÁdlpÃ(mlby means of a standar=†°dONLNd    ¸dÕpÛ)a    d classifi° °dONLNd
dÛp
A)&cation system for I¿°dONLNd
d
Ap
»)NApple event objects. This systeŒ@°dONLNd
7d
»p
’)ám, °dONLNd
:ql}r(zl
dõ¿°dONLNd
;qr}ê)escribe>‡°dONLNd
Bqë}Œ)d in detail in t    °dONLNd
Rqœ}‹)>he $°dONLNd
Uq‹}
{)&Apple Event Registry: Standard Suites,ë¿°dONLNd
{q
{}
Ä)ü i˙ °dONLNd
}q
Ä}
Ã)s summarized in `°dONLNd
çq
Õ}
Â)M“The °dONLNd
í~läå(álClassifiÓÄ°dONLNd
ö~åä¥)
cation of ;`°dONLNd
§~µä
))Apple Event Objects,”K¿°dONLNd
π~
ä
d)b which begins on º °dONLNd
 ~
dä
{)Mpage ó°dONLNd
œ~
|ä
é)3-39͇°dONLNd
”~
éä
ì). åÄ°dONLNd
’~
ìä
ö)
A« °dONLNd
÷~
öä
È) description in an °dONLNd
Èãló
.(îl,Apple event parameter that uses this classifi}Ä°dONLNdã
/ó
‰)√*cation system takes the form of an object °dONLNd@òl§à(°lspecifiÓ °dONLNdGòà§ó)er rÔ`°dONLNdKòó§©)ecorc¿°dONLNdOò™§≤)d.ˇC@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡ä
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records

, (‡3-33
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähö(eäAn 
ò†°dONLNd\öh’)object specifiG`°dONLNd\÷h˛)<    er recordç`°dONLNd\˛h
E)( is a descriptor rí°dONLNd,\
Eh
W)Gecor`°dONLNd0\
Xh
±)d of descriptor type ,
Courier°dONLNdEiäu¸(rätypeObjectSpecifierx‡°dONLNdXi¸u
Ø)r* that describes the location of one or mor8Ä°dONLNdÇi
∞u
∑)¥e #¿°dONLNdÑi
∑u)Apple event objects: °dONLNdôvälj(äfor example, the tablF °dONLNdÆvÂÇÒ)[e “è¿°dONLNd±vÒÇ)=Summary of Sales” in the document “Sales Report,” or the thir#@°dONLNdÓvÇ(d °dONLNdÉäèç(åä
rE°dONLNdÒÉéè
    )ow in that table, or the last r†°dONLNd
É

è
e)|ow of the column “T3@°dONLNd
#É
dè
å)Z    otals.” Wɇ°dONLNd
,É
åè
Δ)(ith the aid of °dONLNd
;êäúœ(ôäapplication-defi|‡°dONLNd
Kê–ú
!)Fned functions, the ˝‡°dONLNd
^ê
!ú
˝)Q/Apple Event Manager can conduct a step-by-step °dONLNd
çùä©õ(¶äsearK†°dONLNd
ëùú©¿)ch accor(@°dONLNd
ôù¿©
)$ding to such instrb@°dONLNd
´ù
©
Ä)Muctions in an object specifiQ†°dONLNd
«ù
Å©
ê)ter rR‡°dONLNd
Àù
ê©
¢)ecor«@°dONLNd
ϝ
¢©
Ÿ)d, locating fi… °dONLNd
›ù
Ÿ©
˜)7rst the °dONLNd
™ä∂
®(≥äCdocument, then the table, then other objects, and so on until the r8°dONLNd(™
©∂(≥
©equested object has °dONLNd<∑ä√¡(¿äbeen identifi¬‡°dONLNdI∑¡√Œ)7ed.(@°dONLNdL∑œ√
) Object specifiÇ°dONLNd[∑
√
)=er rŒ °dONLNd_∑
√
-)ecorBÄ°dONLNdc∑
.√)0ds can specify many combinations of identifying °dONLNdìƒä–
((Õä%characteristics that cannot be specifi‡°dONLNdπƒ
)–
“)ü'ed using one of the simple data types. °dONLNd·÷ä‚–(fläThis section intrA °dONLNdÚ÷—‚
+)Goduces object specifi醰dONLNd÷
+‚
:)Zer r臰dONLNd÷
:‚
L)ecor@°dONLNd÷
M‚
á)ds and the or‚°dONLNd÷
Ü‚
Ú)9ganization of their data. Œ¿°dONLNd6÷
Ú‚
¯)l
Yè@°dONLNd7÷
¯‚)ou °dONLNd:„äÔ±(Ïä    need to r}@°dONLNdC„±Ô
â)'3ead this section (a) if you plan to support the Cor    Ä°dONLNdv„
äÔ)Ÿe suite or any of the standar¨Ä°dONLNdì„Ô)zd °dONLNdïä¸√(˘äfunctional-arèÄ°dONLNd¢√¸    )9Kea suites and (b) if you want to make your application scriptable—that is, °dONLNdÌ˝ä
    Ω(
äcapable of r∫`°dONLNd˘˝Ω
    
£)35esponding to scripts written in a scripting language.


H
%4
H
%
°dONLNd/
ä
 ©(
äIMPORT
ç°dONLNd5
©
 π)ANT

ˇ·ˇ‚7^
°dONLNd9
#ä
/“(
,äAn object specifiV‡°dONLNdJ
#”
/‚)Ier rX °dONLNdN
#‚
/Ù)ecorÃÄ°dONLNdR
#Ù
/
)    d identifi>‡°dONLNd\
#

/
Y))es one or morL†°dONLNdi
#
Y
/
`)<e 7‡°dONLNdk
#
`
/
π)Apple event objects °dONLNd
/ä
;
≥(
8äEamong many; it contains a description of each object, not the object °dONLNdƒ
;ä
G§*itself. è@°dONLNdÃ
;§
G´)
AVÄ°dONLNdÕ
;¨
G¥)n IÄ°dONLNdœ
;¥
G
ä)0Apple event object described by an object specifie`°dONLNd
;
ä
G
ô)÷er rf†°dONLNd
;
ô
G
´)ecor€°dONLNd
;
´
G
≥)d °dONLNd

Gä
S
§(
PäBexists only in the server application’s document or in the server °dONLNdL
Sä
_–*application itsel–†°dONLNd]
S–
_’)Ff.,Zapf Dingbats§Ä°dONLNd`
V€
^‚)
s
°dONLNdb
dä
pë(
mä
A∫†°dONLNdc
dë
p
) client application cannot r¿°dONLNd
d

p
4)vetrieve an ≥@°dONLNdä
d
4
p
ê)-Apple event object frÁ°dONLNdü
d
ê
p
˙)\om a server application °dONLNd∑
qä
}
˘(
zäXunless the server application can accurately locate it. Thus, to locate characters of a °dONLNd
~ä
ä¶*specifiÓ °dONLNd
~¶
ä√)c colorW@°dONLNd
~√
ä
Ÿ)B, a server application must be able to identify a single characterL`°dONLNd_
~
⁄
ä    (
á
⁄’s color; to °dONLNdl
ãä
ó(
îä]locate a character in a cell, a server application must be able to locate both the table and °dONLNd…
òä
§´*    the cell.°dONLNd”
™ä
∂ë*
A∫†°dONLNd‘
™ë
∂¸) client application can cr¿°dONLNdÓ
™˝
∂
J)leate object specifi†°dONLNd

™
J
∂
Y)Mer r‡°dONLNd
™
Y
∂
k)ecorê@°dONLNd    
™
k
∂
§)ds for use as ë`°dONLNd
™
§
∂
‹)9Apple event °dONLNd#
∑ä
þ(
¿äparameters.Œ°dONLNd.
∑æ
√¿)4
 N°dONLNd/
∑¡
√
R) Scripting components can also crï@°dONLNdO
∑
R
√
ü)ëeate object specifi© °dONLNdb
∑
ü
√
Æ)Mer r™`°dONLNdf
∑
Æ
√
¿)ecor¿°dONLNdj
∑
¡
√
Ÿ)ds as V °dONLNdp
∑
Ÿ
√
ˆ)Apple °dONLNdv
Ċ
–¢(
ÕäeventÕ@°dONLNd{
Ģ
–§)
 M@°dONLNd|
ĥ
–÷)
parameters@°dONLNdÜ
ƒ◊
–Ÿ)2
 õ@°dONLNdá
ƒŸ
–¯)for the ÷@°dONLNdè
ƒ¯
–)@Apple events they generate in the course of executing a script. °dONLNdœ
—ä
ݑ(
ڊ
AG@°dONLNd–
—í
ݔ)
 :†°dONLNd—
—î
›˝)server application that rË`°dONLNdÍ
—˝
›
,)ieceives an Ù °dONLNdı
—
,
›
‹)/'Apple event containing an object specifiJ†°dONLNd
—
›
›
Ï)±er rK‡°dONLNd!
—
Ï
›
˛)ecor¿@°dONLNd%
—
˛
›)d °dONLNd'
fiä
ÍØ(
Áäshould rT °dONLNd/
ޯ
Í
)%esolve the object specifiƒ °dONLNdH
fi

Í
%)ger r≈`°dONLNdL
fi
%
Í
7)ecor9¿°dONLNdP
fi
8
Í
ò)d—that is, locate the rÕÄ°dONLNdg
fi
ò
Í
¬)`    equested á`°dONLNdp
fi
¬
Í
˙)*Apple event °dONLNd|
Îä
˜®(
Ùäobjectsç °dONLNdÉ
ή
˜≠). °dONLNdÜ
˝ä    ê(ä
Tµ¿°dONLNdá
˝è    ö)o rp@°dONLNdä
˝õ    ÷)espond to cor>@°dONLNdó
˝◊    
*)<e and functional-arÄ°dONLNd™
˝
+    
7)Tea Ô¿°dONLNd≠
˝
6    
v)Apple events rºÄ°dONLNdª
˝
w    
)A!eceived by your application, you °dONLNd‹
ä®(ämust fig@°dONLNd„
©«)rst defiK`°dONLNdÎ
»˜)ne a hierar!`°dONLNdˆ
˜
)/chy of ] °dONLNd˝

)7Apple event objects for your application that you want °dONLNd    4ä#
∂( äFother applications or scripting languages to be able to describe. The 3¿°dONLNd    z
∂#( 
∂Apple event objects °dONLNd    é$ä0
Õ(-äJfor your application should be based as closely as possible on the standar´@°dONLNd    ÿ$
Õ0(-
Õd object classes °dONLNd    È1ä=’(:ädescribed by the Œ¿°dONLNd    ˙1’=
t)K&Apple Event Registry: Standard Suites.<Ä°dONLNd
 1
u=
w)†
 ^ °dONLNd
!1
w=
) After you have decided which of °dONLNd
A>äJª(Gäthe standar‡°dONLNd
L>ºJƒ)2d L@°dONLNd
N>ƒJ
Ó)CApple event objects make sense for your application, you can write °dONLNd
ëKäW
–(TäMfunctions that locate objects on the basis of information in an object specifie°dONLNd
flK
—W
‡(T
—er rf@°dONLNd
„K
‡W
Ú)ecor⁄†°dONLNd
ÁK
ÚW
¯)
dˆ`°dONLNd
ËK
¯W). IT‡°dONLNd
ÎK
W)    f °dONLNd
ÌXäd
A(aä(you want your application to send specifi≈Ä°dONLNdX
Ad
G)∑c W`°dONLNdX
Hd)-Apple events to other applications, you must °dONLNdEeäq
(nä also write functions that can crÒ °dONLNdee
q
^)áeate object specifi°dONLNdxe
_q
n)Ner r@°dONLNd|e
nq
Ä)ecorz†°dONLNdÄe
Äq
ÿ)ds and add them to LJ°dONLNdìe
ÿq
ı)XApple °dONLNdôrä~´({äevents. ‹†°dONLNd°r´~±)!
Yù °dONLNd¢r±~
J)#our application does not need to crQ‡°dONLNd≈r
K~
ò)öeate object specifie¿°dONLNdÿr
ò~
ß)Mer rg°dONLNd‹r
ß~
π)ecor€`°dONLNd‡r
π~
⁄)ds in or(`°dONLNdËr
€~)"
der to be °dONLNdÚäã≠(àäscriptab‘`°dONLNd˙≠ã‚)#le. However°dONLNd„ã˚)6, to w°‡°dONLNd˚ã
Ñ)!rite functions that can help the p`°dONLNd,
Ñã
Ï)âApple Event Manager rd@°dONLNdA
Ïã)hesolvo°dONLNdFã
)e °dONLNdHåäò¬(ïäobject specifi>@°dONLNdVå√ò“)9er r?Ä°dONLNdZå“ò‰)ecor≥‡°dONLNd^å‰ò
z) ds, you need to know how they arM°dONLNd~å
{ò
ù)óe constr´¿°dONLNdÜå
ùò
∏)"ucted. ‡°dONLNdåå
∏ò
∫)
 ˇ≤@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-34    )B
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records4^*¿
¯
°dONLNd\lhñ(el    “Finding O °dONLNd    \ñh¯)*Apple Event Objects,”_Ä°dONLNd\¯h
E)b which begins on œ‡°dONLNd/\
Eh
\)Mpage ™¿°dONLNd4\
]h
o)3-46˛†°dONLNd8\
oh
}), pr≈¿°dONLNd<\
~h
Ú)ovides an overview of the °dONLNdViluë(rlway the  °dONLNd^iëu
á)%3Apple Event Manager works with your application-defim†°dONLNdíi
àu
Ó)˜ned functions to locate °dONLNd™vlÇ|(lthe °dONLNdÆv|Ç
S)1Apple event objects described in an object specifiz‡°dONLNd‡v
TÇ
c)ÿer r| °dONLNd‰v
cÇ
u)ecorÄ°dONLNdËv
uÇ
Í)d. The chapter “Resolving °dONLNd
Élèä(åland Cr… °dONLNd
Éäè„)eating Object Specifi≈`°dONLNd
ɉè
)Zer Recor$°dONLNd
%É
    è
Í)%4ds” in this book describes in detail how to support °dONLNd
Yêlú§(ôlobject specifi>@°dONLNd
gê•ú¥)9er r?Ä°dONLNd
kê¥úΔ)ecor≥‡°dONLNd
oêΔú
a)&ds as a server or client application. 

¡*»
¯4¬*»
¯ √l√
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd
ñ≤l¡u(Ωl
Dwé°dONLNd
ó≤v¡€)
ata Structures Wué°dONLNd
ß≤‹¡
`)fithin an Object Specifiø°dONLNd
æ≤
`¡
ú)Ñ    er Recordˇˇˇˇˇˇ€r)ê
3
°dONLNd
…»l‘r(—l
T†¿°dONLNd
 »r‘w)
hr °dONLNd
À»x‘Ñ)e o1@°dONLNd
Œ»Ö‘à)
rˆ@°dONLNd
œ»à‘
)ganization of the data for an o∏Ä°dONLNd
Ó»
‘
@)Öbject specifi
@°dONLNd
˚»
A‘
P)4er rÄ°dONLNd
ˇ»
P‘
b)ecorv‡°dONLNd»
b‘
fl)d is nearly identical to that oc °dONLNd"»
‡‘
ˆ)~f the °dONLNd(’l·ñ(fil
data for aö °dONLNd2’ñ·û)*n ç °dONLNd4’û·≤)AE rµ °dONLNd8’≤·ƒ)ecor)Ä°dONLNd<’≈·À)
dE@°dONLNd=’À·–). ʇ°dONLNd?’œ·÷)
AÆ °dONLNd@’◊·
)n object specifiΩ¿°dONLNdP’
·
')Aer rø°dONLNdT’
'·
9)ecor3`°dONLNdX’
:·
_)
d is a strRÄ°dONLNdb’
_·
v)%ucturÿ`°dONLNdg’
v·
¥)e of data type ,
Courierf¿°dONLNdv’
µ·
Ÿ)?AEDescdÄ°dONLNd|’
Ÿ·
€)$
 °dONLNd}‚lÓÉ(ÎlwhosZ‡°dONLNdÅ‚ÑÓÈ)e data handle usually rc@°dONLNdò‚ÈÓ
)e
efers to fÖ¿°dONLNd¢‚
Ó
B)&
our keyworÓ`°dONLNd¨‚
BÓ
g)3d-specifià °dONLNdµ‚
hÓ
®)&ed descriptor rê¿°dONLNdƒ‚
©Ó
ª)Aecor °dONLNd»‚
ºÓ
¬)
d ‡°dONLNd…‚
¬Ó
»)s °dONLNdÀÔl˚Õ(¯ldescribing one or mor≈@°dONLNd‡ÔÕ˚‘)ae ∞Ä°dONLNd‚Ô‘˚
&)Apple event objectK`°dONLNdÙÔ
'˚
0)Ss. *°dONLNd˜Ô
0˚
=)    An¬†°dONLNd˘Ô
=˚
?)
 ‰@°dONLNd˙Ô
?˚
S)AE r@°dONLNd˛Ô
T˚
f)ecorĆ°dONLNdÔ
f˚
ã)
d is a strü¿°dONLNdÔ
ã˚
¢)%uctur%†°dONLNdÔ
£˚
·)e of data type °dONLNd ¸l
ú(
lAERecord}°dONLNd(¸ú
Ã)0
 whose dat†°dONLNd2¸Ã
¯)0
a handle rµ °dONLNd<¸¯

 ),
efers to o˘@°dONLNdF¸
 

K)(    ne or mor
‡°dONLNdO¸
L

S),e ˆ °dONLNdQ¸
R

º)Apple event parameters釰dONLNdg¸
Ω

ø)k
.°dONLNdi
l
∂(
lThe four keyworx@°dONLNdx
∂
€)Jd-specifiV°dONLNdÅ
‹

)&ed descriptor r†°dONLNdê



/)Aecorè°dONLNdî

/

ë)ds for an object specifi≥`°dONLNd¨

ë

†)ber r¥†°dONLNd∞

†

≤)ecor)°dONLNd¥

≥

≈)d prㇰdONLNd∏

≈

‡)ovide °dONLNdæ
l
'”(
$linformation about the r§`°dONLNd’
”
'˝)g    equested ^@°dONLNdfi
˝
'
w)*Apple event object or object1`°dONLNd˙

x
'
~){s.°dONLNd–
∂l
¬
#(
øl*For example, the data for an object specifi¯¿°dONLNd˚
∂
#
¬
2)∑er r˙°dONLNdˇ
∂
2
¬
D)ecorn`°dONLNd
∂
E
¬
P)d iÚÄ°dONLNd
∂
P
¬
f)denti‘°dONLNd
∂
g
¬
Ö)fying a‡°dONLNd
∂
Ü
¬
Ù) table named “Summary °dONLNd(
√l
œ
3(
Ãl+of Sales” in a document named “Sales ReportI†°dONLNdS
√
4
œ
?)»” c9‡°dONLNdV
√
@
œ
Y)onsist%Ä°dONLNd\
√
Z
œ
^)
sbÄ°dONLNd]
√
^
œ
¢) of four keyworË`°dONLNdl
√
¢
œ
«)Dd-specifiΔ °dONLNdu
√
»
œ
’)&ed °dONLNdx
–l
‹ü(
Ÿldescriptor rfl@°dONLNdÑ
–ü
‹±)3ecorS†°dONLNdà
–≤
‹‹)
ds that pr…†°dONLNdí
–‹
‹
l)* ovide the following information:,Zapf Dingbats°dONLNd≥
Êl
Ìq(
Ïl
n
°dONLNdµ
„x
Ôç)the oR‡°dONLNd∫
„é
Ôø)bject class Ifi†°dONLNd«
„ø
Ô›)1D for aW‡°dONLNdŒ
„fi
ÔÒ) tablä@°dONLNd”
„Ò
Ôı)
e°dONLNd’
¯l
ˇq(
˛l
n
°dONLNd◊
ıx
’)another object specifi’ °dONLNdÌ
ı’
‰)]er r÷`°dONLNdÒ
ı‰
ˆ)ecorJ¿°dONLNdı
ı˜

6)d identifying tû†°dONLNd
ı
6

—)?"he document “Sales Report” as the °dONLNd&
x‘(
xcontainer for the tablª@°dONLNd<
‘ÿ)\
e°dONLNd>lq(l
n
°dONLNd@x})
a°dONLNdA}
ê)> key form constant indicating that the key data contains a nam䆰dONLNd
ê
î(
ê
e°dONLNdÅ(l/q(.l
n
°dONLNdÉ%x1
a)5key data that consists of the string “Summary of Sale¬`°dONLNd∏%
a1
j)Ès”
    °dONLNd˝
4l
?ë(
<lKeyword°dONLNd
4Ê
?
7)zDescription of data
°dONLNd
Bl
N“(
KlkeyAEDesiredClass°dONLNd,
BÊ
N˙)zFourP¿°dONLNd0
B˚
N
ø).-character code indicating the object class ID°dONLNd`
Rl
^¿(
[lkeyAEContainer°dONLNdo
RÊ
^Ì)z
A∫†°dONLNdp
RÌ
^
C) description of the c≥°dONLNdÖ
R
D
^
è)Wontainer for the rꆰdONLNdó
R
è
^
œ)Kequested objec6†°dONLNd•
R
–
^
ÿ)At, °dONLNd®
]Ê
i
•(
fÊ,usually in the form of another object specifi¿°dONLNd’
]
•
i
¥)øer rÚ°dONLNdŸ
]
¥
i
Δ)ecorf`°dONLNd›
]
«
i
Õ)
d°dONLNd‡
ml
y¥(
vlkeyAEKeyForm°dONLNdÌ
mÊ
y˙)zFourP¿°dONLNdÒ
m˚
y
ˆ)9-character code for the key form, which indicates how to °dONLNd*
xÊ
Ñ
(
ÅÊinterprˇÄ°dONLNd1
x

Ñ
D)et the key data°dONLNdB
àl
î¥(
ëlkeyAEKeyData°dONLNdO
àÊ
î
è)z'Key data, used to distinguish the desirQ¿°dONLNdv
à
ê
î
ù)™ed X¿°dONLNdy
à
ù
î
Ú)Apple event object °dONLNdå
ìÊ
üÌ(
úÊfrò‡°dONLNdé
ìÌ
ü
’)6om other objects of the same object class in the same °dONLNdƒ
ûÊ
™
(
ßÊ    containerˇ=0@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡ä
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records

, (‡3-35
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähù(eäThe 
ª¿°dONLNd\ùhfl)object class IDZ¿°dONLNd\‡h˛)C specifiH‡°dONLNd\ˇh
)es the ŒÄ°dONLNd"\
h)Apple event object class to which the object belongs. °dONLNdXiäuö(räAn :@°dONLNd[iöu
O)+Apple event object class is a category for -`°dONLNdÜi
Ou
œ)µApple event objects that shar.¿°dONLNd£i
œu
÷)Äe °dONLNd•väǶ(äspecifiÓ °dONLNd¨v¶Ç¨)c fi`°dONLNdÆv≠Ç

)characteristics (see £°dONLNd√v
Ç
X)U“Apple Events and †°dONLNd’v
YÇ
‡)WApple Event Objects” on page Ω¿°dONLNdÚv
‡Ç
Ì)á3-6†°dONLNdıv
ÓÇ    )). The °dONLNd¸Éäè
)(åä'characteristics of each object class ar‹‡°dONLNd
#É
)è
f)üe listed in the s °dONLNd
3É
gè)>&Apple Event Registry: Standard Suites.‡‡°dONLNd
YÉè)ü
 °dONLNd
ZêäúÊ(ôäFor example, the Cor Ä°dONLNd
nêÁú
)]e suite defi¿°dONLNd
zê
ú
Û)01nes object classes for documents, paragraphs, wora†°dONLNd
´ê
Ûú)‹ds, °dONLNd
Øùä©—(¶äwindows, and fl/‡°dONLNd
æù“©
7)Hoating windows. The fi/ °dONLNd
‘ù
8©
g)f
rst keyworöÄ°dONLNd
fiù
g©
å)/d-specifix@°dONLNd
Áù
ç©
Õ)&ed descriptor r<‡°dONLNd
ˆù
Ω
‡)Aecor±@°dONLNd
˙ù
‡©
)d in an °dONLNd™ä∂¬(≥äobject specifi>@°dONLNd™√∂“)9er r?Ä°dONLNd™“∂‰)ecor≥‡°dONLNd™‰∂
)d uses a four/‡°dONLNd%™
∂)9:-character code or a constant to specify the object class °dONLNd_∑ä√

(¿äID. The object class for worG¿°dONLNd{∑
√
â)xds, for example, can be identifi¿`°dONLNdõ∑
â√)á!ed by either the object class ID ,
Courier°dONLNdºƒä–ê(Õä
'†°dONLNdΩƒê–®)cwor~ °dONLNd¡ƒ®–Æ)
'}¿°dONLNd¬ƒÆ–Ù) or the constant Ä°dONLNd”ƒı–
)GcWord†°dONLNdÿƒ
–
). 

fiHÏ4flHÏ
    °dONLNd€›äËù(ÂäNote

ˇ·ˇ‚7^
°dONLNd‡Íäˆ˛*The object class ID identifi–‡°dONLNd¸Í˛ˆ
f)tes the object class of an î°dONLNdÍ
fˆ
ª)hApple event object °dONLNd)ˆä

(ˇädescribed in an object specifi$°dONLNdGˆ
    

)er r%@°dONLNdKˆ


*)ecorô†°dONLNdOˆ
*

L)d, wherl`°dONLNdVˆ
L

Õ)"eas the event class and event °dONLNdt
ä
 (
äID identify an ;†°dONLNdÉ
 

)@Apple event.,Zapf Dingbats`°dONLNdê



)>
u
°dONLNdí
ä
ù(
äThe 
ª¿°dONLNdñ
ù
«)    container~°dONLNdü
»
Á)+ for an -°dONLNdß
Á

ç)&Apple event object is usually another P‡°dONLNdÕ

ç

ˆ)¶Apple event object. For °dONLNdÂ
 ä
,
å(
)ä7example, the container for a document might be a window{¿°dONLNd
 
å
,
Ô(
)
å, and the container for °dONLNd4
-ä
9
+(
6ä%characters, delimited items, or a wory`°dONLNdY
-
+
9
ì)°d might be another worÓ°dONLNdo
-
ì
9
Ï)hd, a paragraph, or a °dONLNdÑ
:ä
FÙ(
Cädocument. The containeÚ†°dONLNdö
:Ù
F˝)jr iM†°dONLNdù
:˛
F
$)
    s identifi·@°dONLNdß
:
$
F
í)&ed by the second keywor†°dONLNdæ
:
ì
F
∏)od-specifiÎ`°dONLNd«
:
∏
F
¯)%ed descriptor r∞°dONLNd÷
:
˘
F)Aecor$`°dONLNd⁄
:
F)d °dONLNd‹
Gä
S€(
Päin an object specifi…`°dONLNd
G€
SÍ)Qer r †°dONLNdÙ
GÍ
S¸)ecor?°dONLNd¯
G˝
S
L)d; usually this is a‰`°dONLNd
G
L
S
§)Onother object specifi9Ä°dONLNd!
G
•
S
¥)Yer r:¿°dONLNd%
G
¥
S
Δ)ecorØ °dONLNd)
G
Δ
S
Ã)
d ‡°dONLNd*
G
Ã
S). The container °dONLNd:
Tä
`é(
]ä
c@°dONLNd;
Té
`ß)an alsg°dONLNdA
T®
`Ÿ)o be specifiõ‡°dONLNdM
TŸ
`¯)1ed by aò°dONLNdT
T˘
`
C)  null descriptor r†Ä°dONLNdf
T
C
`
U)Jecor‡°dONLNdj
T
V
`),d, which indicates a default container or a °dONLNdñ
aä
m¡(
jäcontainer alr‡°dONLNd£
a¬
m
)8eady known to the Δ†°dONLNdµ
a

m
w)TApple Event Manager∏ °dONLNd»
a
w
m
y)a
.°dONLNd 
sä
–(
|äThe descriptor r°dONLNd⁄
s—
„)Gecorè`°dONLNdfi
s„
Î)d + °dONLNd‡
sÏ

=)    in an object specifitÄ°dONLNdÙ
s
=

L)Qer ru¿°dONLNd¯
s
L

^)ecorÍ °dONLNd¸
s
^

f)d Ö‡°dONLNd˛
s
g

u)    thaô†°dONLNd

s
u

ö)    t identifi2†°dONLNd
s
õ

≥)&es an ¨@°dONLNd
s
≥

Î)Apple event °dONLNd
Ää
å≠(
âä    object’s ‘`°dONLNd&
Ä≠
å›)#container c4 °dONLNd1
Äfi
å
)1    an in tur˚`°dONLNd:
Ä

å
!)%n use a⁄Ä°dONLNdA
Ä
"
å
z)nother object specifi/†°dONLNdV
Ä
{
å
ä)Yer r0‡°dONLNdZ
Ä
ä
å
ú)ecor•@°dONLNd^
Ä
ú
å
Â)d to identify the °dONLNdp
çä
ô≥(
ñä    container¨‡°dONLNdy
ç¥
ôÊ)*’s container„@°dONLNdÖ
çÊ
ôË)2
,c@°dONLNdÜ
çÈ
ô
@) and so on until the ¥`°dONLNdõ
ç
@
ô
è)WApple event objec‡°dONLNd¨
ç
ê
ô
ò)Pt i∑†°dONLNdØ
ç
ò
ô
“)s fully specifi†°dONLNdæ
ç
”
ô
‚);ed. °dONLNd¬
öä
¶ò(
£äForw@°dONLNd≈
öô
¶õ)
 ˜@°dONLNdΔ
öõ
¶
)example, an object specifiÅ@°dONLNd‡
ö

¶
)qer rÇÄ°dONLNd‰
ö

¶
-)ecorˆ‡°dONLNdË
ö
-
¶
8)d i{°dONLNdÎ
ö
9
¶
O)denti\Ä°dONLNd
ö
P
¶
n)fying a`°dONLNd˜
ö
o
¶
Ò) paragraph might specify the °dONLNd
ßä
≥
a(
∞ä0paragraph’s container with another object specifif°dONLNdE
ß
b
≥
q)ÿer rg@°dONLNdI
ß
q
≥
É)ecor€†°dONLNdM
ß
É
≥
ø)d that identifi$ °dONLNd\
ß
¿
≥
„)=es a pagº°dONLNdd
ß
„
≥)#e. That °dONLNdl
¥ä
¿¬(
Ωäobject specifi>@°dONLNdz
¥√
¿“)9er r?Ä°dONLNd~
¥“
¿‰)ecor≥‡°dONLNdÇ
¥‰
¿
)    d might i@°dONLNdã
¥

¿
"))n tur§¿°dONLNdê
¥
"
¿
.)n s3 °dONLNdì
¥
/
¿
D)pecif´`°dONLNdò
¥
D
¿
)y the page’s cg@°dONLNd¶
¥
Ä
¿
ˇ)<ontainer with another object °dONLNd√
¡ä
Õ¶(
 äspecifiÓ °dONLNd 
¡¶
Õµ)er rÔ`°dONLNdŒ
¡µ
Õ«)ecorc¿°dONLNd“
¡»
Õ”)d iÁ‡°dONLNd’
¡”
ÕÈ)denti…`°dONLNd⁄
¡Í
Õ
)fying au@°dONLNd·
¡
    
Õ
⁄)0 document. The ability to nest one object specifiû@°dONLNd
¡
⁄
Õ
È)—er rüÄ°dONLNd
¡
È
Õ
˚)ecor‡°dONLNd
¡
¸
Õ)d °dONLNd
Ί
⁄«(
◊äwithin anothe1 °dONLNd)
Œ»
⁄—)>r iå °dONLNd,
Œ—
⁄
Ë)    @n this way makes it possible to identify elements such as “the fi†Ä°dONLNdm
Œ
Ë
⁄
˘(
◊
Ërst rWÄ°dONLNdr
Œ
˙
⁄)ow in °dONLNdx
ۊ
Á (
‰äthe table nameH`°dONLNdÜ
€À
Á€)Ad ‘SÎ °dONLNdä
€€
Á
)ummary of SalÄ°dONLNdó
€

Á
.)Bes’ iC¿°dONLNdú
€
.
Á
é)n the document nameõÄ°dONLNdØ
€
é
Á
û)`d ‘S>@°dONLNd≥
€
ü
Á
Õ)
ales Reporè °dONLNdΩ
€
Õ
Á
›).t.’” ˇ"H@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-36    )B
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records4^*¿
¯
°dONLNd\lh(elThe 
ª¿°dONLNd\h®)key form †°dONLNd\©hæ)* and 
¿°dONLNd\øhÂ)key data®@°dONLNd\Âh
B)& distinguish the desirü†°dONLNd/\
Bh
O)]ed ¶†°dONLNd2\
Oh
´)Apple event object fr⁄`°dONLNdG\
´h
’)\    om other °dONLNdP\
÷h
Û)+Apple °dONLNdVilu
‹(rlUevent objects of the same object class. The key form describes the form the key data °dONLNd´vlÇ´*takes. The thirU°dONLNd∫v´Ç’)?d keyworj °dONLNd¬v’Ç˙)*d-specifiG‡°dONLNdÀv˚Ç
;)&ed descriptor rÄ°dONLNd⁄v
<Ç
N)Aecorć°dONLNdfiv
NÇ
ß)d in an object specifif°dONLNdÙv
®Ç
∑)Zer rg@°dONLNd¯v
∑Ç
…)ecor€†°dONLNd¸v
…Ç
Ù)
d usually °dONLNd
Élèà(ålspecifiÓ °dONLNd
Éàè
@))es the key form with one of seven standar`°dONLNd
6É
@è
t)∏d constants:°dONLNd◊
Yl
es(
bl
A∫†°dONLNdÿ
Ys
e´) key form of ,
Courier˚‡°dONLNdÂ
Y´
eˇ)8formPropertyIDˆ†°dONLNdÛ
Yˇ
e
Ñ)T indicates key data that specifi¯°dONLNd
Y
Ñ
e
†)Öes a pr≈¿°dONLNd
Y
°
e
æ)opertyØ`°dONLNd 
Y
Ω
e
¬). Q°dONLNd"
Y
¬
e
…)
AㆰdONLNd#
Y
…
e
À)
 
†°dONLNd$
Y
Ã
e
Û)property|Ä°dONLNd,
Y
Û
e
ı)'
 °dONLNd-
fl
rÑ(
olof an º`°dONLNd3
fÑ
r
)Apple event object is a specifij¿°dONLNdR
f

r
ÿ)É3c characteristic of that object that can be identifiÌ¿°dONLNdÜ
f
ÿ
r
Ú)—ed by °dONLNdå
sl
∫(
|la constant. The prM °dONLNdû
sª

‚)ODoperties associated with the object class for documents include the °dONLNd‚
Äl
åÚ(
âlname of the document and a flI†°dONLNdˇ
ÄÛ
å
‹)á1ag indicating whether the document has been modifi¿Ä°dONLNd1
Ä
‹
å
È)Èed °dONLNd4
çl
ô‹(
ñlsince the last save. The pr%Ä°dONLNdO
ç›
ô
Æ)q1operties associated with the object class for worõ`°dONLNdÄ
ç
Æ
ô
fi)—ds include °dONLNdã
öl
¶Ç(
£lcolor¯‡°dONLNdê
öÅ
¶˜), font, point size, and style.°dONLNdØ
¨l
∏Ñ(
µlFigurR¿°dONLNd¥
¨Ñ
∏ù)e 3-13@°dONLNd∫
¨ù
∏Ÿ) shows the str√Ä°dONLNd»
¨⁄
∏Ò)=ucturI`°dONLNdÕ
¨Ú
∏˛)e oÄ°dONLNd–
¨ˇ
∏
e)f a typical object specifiØ@°dONLNdÍ
¨
e
∏
t)fer r∞Ä°dONLNdÓ
¨
t
∏
Ü)ecor$‡°dONLNdÚ
¨
á
∏
ï)d: fîÄ°dONLNdˆ
¨
ï
∏
¶)our °dONLNd˙
πl
ō(
¬lkeywor˘`°dONLNd
πç
≈≤)!d-specifi◊ °dONLNd    
π≥
≈Û)&ed descriptor rõ¿°dONLNd
πÙ
≈
)Aecor °dONLNd
π

≈
ª)+ds that specify the class ID, the container^†°dONLNdG
π
∫
≈
·)≥
, the key °dONLNdQ
Δl
“
((
œl)form, and the key data. These four keyworü`°dONLNdz
Δ
(
“
M)ºd-specifi} °dONLNdÉ
Δ
N
“
é)&ed descriptor rA¿°dONLNdí
Δ
è
“
°)Aecor∂ °dONLNdñ
Δ
°
“
∂)ds arS‡°dONLNdõ
Δ
∑
“
Û)e the data for °dONLNd™
”l
flß(
‹la descriptor r_@°dONLNd∏
ӧ
flπ);ecor”†°dONLNdº
”π
flƒ)d (√@°dONLNdø
”≈
flÈ)AEDesc¡°dONLNd≈
”È
fl
?)$) of descriptor type ï¿°dONLNd⁄
”
@
fl
≤)WtypeObjectSpecifier—@°dONLNdÌ
”
±
fl
æ)q. N  °dONLNd
”
ø
fl
fl)ote the °dONLNd¯
‡l
Ï
(
Èl&similarities between the object specifi¡`°dONLNd
‡

Ï
)§er r¬†°dONLNd#
‡

Ï
1)ecor7°dONLNd'
‡
2
Ï
f)d shown in 8¿°dONLNd2
‡
f
Ï
~)4FigurÄ°dONLNd7
‡
~
Ï
ó)e 3-13©°dONLNd=
‡
ó
Ï
Ω)     and the ï °dONLNdF
‡
Ω
Ï
ı)&Apple event °dONLNdR
Ìl
˘o(
ˆl
rE°dONLNdS
Ìp
˘Ç)ecorπ`°dONLNdW
ÌÇ
˘∂)d shown in ª °dONLNdb
Ì∂
˘Œ)4Figur燰dONLNdg
̌
˘

)e 3-9 on page M °dONLNdu
Ì

˘
)=3-°°dONLNdw
Ì

˘
)19°°dONLNdy
Ì

˘
E)

. Like an p‡°dONLNdÉ
Ì
E
˘
Å)(Apple event r†°dONLNdê
Ì
Ç
˘
î)=ecoru°dONLNdî
Ì
î
˘
µ)d or an ·°dONLNdú
Ì
µ
˘
…)!AE r‡°dONLNd†
Ì
 
˘
‹)ecorà@°dONLNd§
Ì
‹
˘
Ù)d, an °dONLNd™
˙l§(lobject specifi>@°dONLNd∏
˙•¥)9er r?Ä°dONLNdº
˙¥Δ)ecor≥‡°dONLNd¿
˙Δ
C)d consists of a list of keyworƒ¿°dONLNdfi
˙
C
h)}d-specifi¢Ä°dONLNdÁ
˙
i
©)&ed descriptor rg °dONLNdˆ
˙
™
º)Aecor€Ä°dONLNd˙
˙
º
»)ds.¥@°dONLNd˝
˙
…
À)
 °dONLNdˇlÑ(lFigurR¿°dONLNdÑù)e 3-13@°dONLNd
ùŸ) shows the str√Ä°dONLNd⁄Ò)=ucturI`°dONLNdÚ
d)e of a simple object specifiH °dONLNd9
e
t)ser rI`°dONLNd=
t
Ü)ecorΩ¿°dONLNdA
Ü
æ)d that specifiù¿°dONLNdO
ø
Ì)9es the key °dONLNdZl%Ñ("lform ê°dONLNd_Ñ%ÿ)formPropertyIDä¿°dONLNdmÿ%›)T, ä¿°dONLNdo›%
)formNameá¿°dONLNdw
%
)0, or o‡°dONLNd|
%
ñ)formAbsolutePositionh`°dONLNdê
ñ%
“)x. For detailed °dONLNdü&l2⁄(/linformation about the str=`°dONLNd∏&€2Ú)ouctur√@°dONLNdΩ&Ú2
=)e of object specifiÄ°dONLNd–&
>2
M)Ler r¿°dONLNd‘&
M2
_)ecorä °dONLNdÿ&
_2
›)ds that specify the other key °dONLNdˆ3l?
!(<l(forms, see the chapter “Resolving and Crá¿°dONLNd    3
!?
z)µeating Object SpecifiÑ°dONLNd    33
{?
ü)Zer Recor‚†°dONLNd    ;3
ü?
È)$ds” in this book. 
    °dONLNd
Cú*ßP(§*Key form°dONLNd
Lú∂ߺ)å
V¸/°dONLNd
MúªßÕ)alue}¿°dONLNd
RúÓß
T)3Corresponding key data
°dONLNd
j™*∂~(≥*formPropertyID°dONLNd
y™∂∂º)å
'†°dONLNd
z™º∂‘)prop~ °dONLNd
~™‘∂⁄)
'}¿°dONLNd
Ä™Ó∂˜)PrL`°dONLNd
Ç™¯∂
x)
operty ID for an element’s prs@°dONLNd
ü™
x∂
ï)Äoperty°dONLNd
ß∫*ΔZ(√*formName°dONLNd
∞∫∂Δº)å
'†°dONLNd
±∫ºΔ‘)name~ °dONLNd
µ∫‘Δ⁄)
'}¿°dONLNd
∑∫ÓΔ
4)Element’s name°dONLNd
« *÷r(”*formUniqueID°dONLNd
‘ ∂÷º)å
'†°dONLNd
’ º÷‘)ID  ~ °dONLNd
Ÿ ‘÷⁄)
'}¿°dONLNd
€ Ó÷ı)
A∏`°dONLNd
‹ ı÷
p) value that uniquely identifiÊ¿°dONLNd
˘ 
p÷
—){es an object within its }¿°dONLNd’Ó·
3(fiÓcontainer or acr䆰dONLNd!’
3·
Ç)Eoss an application°dONLNd5Â*Ò¢(Ó*formAbsolutePosition°dONLNdJÂ∂Òº)å
'†°dONLNdKºґ)indx~ °dONLNdO‘Ò⁄)
'}¿°dONLNdQÂÓÒ
%)An integer où°dONLNd]Â
%Ò
I)7    r other cE`°dONLNdfÂ
JÒ
Ò)%'onstant indicating the position of one }¿°dONLNdçÓ¸
(˘Óor mort`°dONLNdì
¸
L)e elements in r¶¿°dONLNd¢
L¸
·)@#elation to the beginning or end of }¿°dONLNd≈˚Ó

.(
Ótheir container°dONLNd÷
*
¢(
*formRelativePosition°dONLNdÎ
∂
º)å
'†°dONLNdÏ
º
‘)rele~ °dONLNd
‘
⁄)
'}¿°dONLNdÚ
Ó
ı)
A∏`°dONLNdÛ
ı

O) constant that specifiF‡°dONLNd    

P

∫)[es the element just befor¿°dONLNd"

ª

Â)ke or after }¿°dONLNd-
Ó
"
'(
Óthe container°dONLNd<
&*
2Z(
/*formTest°dONLNdE
&∂
2º)å
'†°dONLNdF
&º
2‘)test~ °dONLNdJ
&‘
2⁄)
'}¿°dONLNdL
&Ó
2
#)Descriptor r~Ä°dONLNdX
&
#
2
5)5ecorÚ‡°dONLNd\
&
5
2
ã)ds that specify a tes/ °dONLNdq
&
å
2
è)W
t°dONLNdt
6*
B`(
?*    formRange°dONLNd~
6∂
Bº)å
'†°dONLNd
6º
B‘)rang~ °dONLNdÉ
6‘
B⁄)
'}¿°dONLNdÖ
6Ó
B
#)Descriptor r~Ä°dONLNdë
6
#
B
5)5ecorÚ‡°dONLNdï
6
5
B
à)ds that specify a gr:@°dONLNd©
6
â
B
“)Toup of elements }¿°dONLNdπ
AÓ
M
m(
JÓbetween two other elements ˇw⁄@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡ä
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records

, (‡3-37
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHw4gHw"hH]

ˇ·ˇ‚7^    °dONLNd\äg∫(däFigure 3-13°dONLNd\Ãg
%)BData structures within Å0°dONLNd#\
%g
N)Y
a simple oÇ°dONLNd-\
Ng
}))bject specifiÑ °dONLNd:\
}g
†)/    er record

wä∫4wä∫4vàwâò@@
˜@
˜wâ∑Ä¡¡?”ˇ˛Ò?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒò@@Ä
˜@Ä
˜∑â˜Ä?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒò@Ä¿
˜Ä¿
˜˜â
7Ä?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒò@¿

˜¿

˜
7â
wÄ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒò@

@
˜

@
˜
wâ
∑Ä?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒò@
@
Ä
˜
@
Ä
˜
∑â
˜Ä?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒò@
Ä
¿
˜
Ä
¿
˜
˜â7Ä?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒò@
¿
Ú
˜
¿
Ú
˜7âiÄ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒò@@
˜@
˜wâ∑Ä
¡¡“32Ò“
Ò ”Ò¡“
Ò¡ ”Ò“
Ò ”Ò¡“
Ò
‡˛  
∞`ÿ€Ò

ø˛=Ω«ü€ü¿›
Ò
 
∑Ô∑Áòflˇ`›Ò    
Ω˚7ÿfiÀ

Áˇ=ÏflÛ˝‡›
Ò˝
0« ˛
0ÿÒ“
Ò ”Ò    
ÿˇ˛Ì
Ù Ê˛
Ò
Ù ÊÌ
 Ù Ê˛Ò
Ù Ê˛
Ò
 Ù Ê˛ÒĢ ¸

Ÿ
 »ÙÌ%ÄÄ˚ Ä
Û˛
Ò&
±€πˆ9„ ˝ mÁ"Á˜ë„ûcÿv¿ˆÌ)
 ˚&§ÃóÄ˝ (ò¢ë#îb!ãı˛Ò(    ¿‚§Ãî¸ ®ü¢ë?bó‡!˙ı˛
Ò*
 ;û∏t„†˝ „·Òº·û˚˛7Ĉ˛Ò
˝ ĸ ˛Ä
˛ÄÒÌ#
˝ ĸ ˛q¿
¿Ò˛
Ò
Ù ÊÌ
 Ù Ê˛Ò
◊ˇ˛
Ò
 Ù Ê˛Ò
Ù ÊÌ
Ù Ê˛
Ò
Ù ÊÌ ˆ °˛ ÄÒ˛Ò    ˜ ` @ÅÒ˛
Ò!     g»¯ ycsÒöÊ√õ‡Ú˛Ò    Û‡¯ eÙ¶KÊoÑΩÚÌ!    ì ¯ eÑ! "hÑ•êÚ˛
Òq˯ πsóqfigÉúÚÌ
 Ù ˛
@Ì˛Ò
Ù ˛@Ì˛
Ò
 Ù Ê˛Ò
Ù ÊÌ
Ù Ê˛
Ò
◊ˇÌ ”Ò“
Ò Ù‰Ò¡Ù
‚Ä
Ò¡ ”ÒÙ‚
Òò@@Ä
˜@Ä
˜∑â˜Ä
 ”Ò
ı‡@ı‡ˇ
¿
Ò
ı‡@ ˆ‡
@Òı‡
@
Ò ˆ‡
@Ò
ı‡@ı‡
@
Ò
ı‡@ ˆ‰ˇ@Òı˜Ô@
Ò ˆ˜"*Ô"0@Òı˜Ô@ı˜Ô@
Òı‰àê@ ˆ˜Ô@Ò"ı    ¿˛
¸0<˘@
Ò& ˆ""/˛":˛"*#"#ø˙˛"
/Ê˘"0@Ò&ı    vÔ~˛ˇ˚ÿoœwÔ~f˜Ä¸@'ı    ˚ˇŒÿ˛øÛfioˇ3ŒyˇÄ¸@
Ò$ı    ààçÀæŒÿ˝àã¯˚ÿÓéªòŒÓÿÎ˚àê@( ˆ    ˚∂~~˛ˇgˇ˚˛œˇœ}Ô˚@Òı˛

ĸ`Ú@
Ò ˆ˛"#˚"*"#‚Ú"0@Òı˜Ô@ı˜Ô@
Òı‰àê@ ˆ‰ˇ@Òı‰@
Ò ˆ‰@Òı‰@ı?Êˇ¯@
Òı ¯@ ˆ ¯@Òı ¯@
Ò ˆ ¯@Òı Ä˝@ı     
 >Ù@
Ò ı     c∂ÛÏyÊ@∑„™flúˆ@# ˆ     ˆL…ò)üîHRbˆ@Ò!ı     Ń…ò%òTó»R~ˆ@
Ò# ˆ w<ËÁ@
à·ú#åˆ@Òı ˝
@ÄÄ"ı@ı ˝
@Ä9¿Áı@
Òı ¯@ ˆ ¯@Òı ¯@
Ò ˆ ¯@Òı ¯@ı?Êˇ¯@
Òı ¯@ ˆ ¯@Òı ¯@
Ò ˆ ¯@Òı ¯@ı ¯@
Òı ¯@ ˆ ¯@Òı ¯@
Ò ˆ ˙
†Äı@Òı     ˚`
@ı@ı     gƒ¸&;ä@ı@
Òı     Û‡¸/f
@ı@ò@Ä¿
˜Ä¿
˜˜â
7Ä
  ˆ     ì ¸iä@ı@Òı q‰¸ßwÄı@
Ò ˆ ¯@Òı ¯@ı ¯@
Òı ¯@ ˆ ¯@Òı ¯@
Ò ˆ ¯@Òı ¯@ı ¯@
Òı ¯@ ˆ ¯@Òı?Êˇ¯@
Ò ˆ‰@Òı‰@ı‰@
Òı‰@ ˆ‰@Òı‰ˇ@
Ò ˆ‡
@Ò
ı‡@ı‡
@
Ò
ı‡@ ˆ‡
@Òı‡
@
Ò ˆ‡
@Ò
ı‡@ı‰ˇ@
Òı‰àê@ ˆ˜Ô@Òı˜Ô@
Ò ˆ˜"*Ô"0@Òı˜Ô@ı    ¿˛Ô@
Òıààè˛àò˝àè˚àé˜àê@# ˆ    vÔ~˛øx`ˆ@Ò%ı    ˚ˇŒÿ˛ˇ˚ÿœ˛ˇé˚flÄ˙@
Ò& ˆ    ""/„æÓ˙˛"
*#øÛ˛Ê{cÊoÓ˘"0@Ò#ı    ˚∂~~˛
ÛÿŒ{nΔn˘@"ı˛

ĸ
ˇgˇ{ˇªÔˇˇ˘@
Òı˛àã¯àËÚàê@ ˆ˜
‡Ú@Òı˜Ô@
Ò ˆ˜"*Ô"0@Òı‰ˇ@ı˜Ô@
Òı‰@ ˆ‰@Òı‰@
Ò ˆ?Êˇ¯@Òı ¯@ı ¯@
Òı ¯@ ˆ ¯@Òı ¯@
Ò& ˆ Ä˝˝
¿Ä˝
 d¸@Ò&ı     
 @˛Ä¸@)ı     c∂ÛÏyÊ@∑„¢súàÛèaÏs`˛@
Ò(ı     ˆL…ò)üîbH¢äLQ ÑâIJ@* ˆ     Ń…ò%òTó‚HæÇQO– Ñ˘˝@Ò)ı w<ËÁ@
à·úåyûqè˘ˇ3¿˛@
Ò% ˆ ˝@ÄÄÄ@˘@Ò"ı ˝
@Ä9¿˛‡˘@ò@¿

˜¿

˜
7â
wÄ
ı ¯@
Òı ¯@ ˆ ¯@Òı ¯@
Ò ˆ?Êˇ¯@Òı ¯@ı ¯@
Òı ¯@ ˆ ¯@Òı ¯@
Ò ˆ ¯@Òı ¯@ı ¯@
Òı ¯@" ˆ ˙—˛
@˘@Ò"ı     ˚
0  @Ä˙@
Ò% ˆ     gƒ¸
=3q˘çsaŸ˙@Ò"ı     Û‡¸
3|£'”7¬|¯˙@#ı     ì ¸
3D Ê4Bd»˙@
Ò"ı q‰¸
›;ìπœ3¡‹x˙@ ˆ ¯
 ı@Òı ¯ ı@
Ò ˆ ¯@Òı ¯@ı ¯@
Òı ¯@ ˆ ¯@Òı ¯@
Ò ˆ ¯@Òı ¯@ı ¯@
Òı?Êˇ¯@ ˆ‰@Òı‰@
Ò ˆÛˆÄ@Òı‰@ı‰ˇ@
Ò
ı‡@ ˆÒ@ˆ˝
@Òı‡
@
Ò ˆ‡
@ÒıÚı

IJ@ı‡
@
Ò
ı‡@ ˆ‡
@ÒıÚ@Ù˛
@
Ò ˆ‡
@Ò
ı‡@ıÛÛ
˛
@
Òı‰
˛@ ˆ‡
@Òı‡
@
Ò ˆÛÚˇ@ÒıÛ@Ú@ıÛ@˛
ˆ@
ÒıÛNà´∏ààõ∏˘àê@ ˆÛ    C∂≤+;{<ñ;Ä˚@ÒıÛB{3/Ò'Ãw˙@
Ò ˆÛ    c≥{≥{Û;øˇ¢˚"0@ÒıÛ
@Û@ıÛ@Ú@
ÒıÛÚˇ@ ˆÛ@Ú@ÒıÛ@Ú@
Òò@

@
˜

@
˜
wâ
∑Ä
 ˆÛ@Ú@ÒıÛ@Ú@ıÛ@Ú@
ÒıÛ@Ú@ ˆÛ@Ú@ÒıÛ@Ú@
Ò ˆÛÚˇ@ÒıÛ@Ú@ıÛ@Ú@
ÒıÛ@Ú@ ˆÛ@Ú@ÒıÛ@Ú@
Ò ˆÛ@Ú@ÒıÛ@Ú@ıÛ@Ú@
ÒıÛÚˇ@ ˆ‡
@Òı‡
@
Ò ˆ‡
@Ò
ı‡@ıÛÚˇ@
ÒıÛHÚàê@ ˆÛ@˝
˜@ÒıÛF#∞ˆ@
Ò ˆÛc∂≤k3„3z˘"0@ÒıÛB{3D™1/†˘@ıÛC±{ª)˚´p˘@
ÒıÛ
HéÛàê@ ˆÛ@Ú@ÒıÛÚˇ@
Ò ˆÛ@Ú@ÒıÛ@Ú@ıÛ@Ú@
ÒıÛ@Ú@ ˆÛ@Ú@ÒıÛ@Ú@
Ò ˆÛ@Ú@ÒıÛ@Ú@ıÛÚˇ@
ÒıÛ@Ú@ ˆÛ@Ú@ÒıÛ@Ú@
Ò ˆÛ@Ú@ÒıÛ@Ú@ıÛ@Ú@
ÒıÛ@Ú@ ˆÛ@Ú@ÒıÛÚˇ@
Ò ˆ‡
@Ò
ı‡@ı‡
@
Ò
ı‡@ ˆÛÚˇ@ÒıÛ@Ú@
Ò ˆÛbÚ"0@ÒıÛF#òĘ@ıÛC∂≤3j7‡¯@
ÒıÛJ˚ªøª ¯¯àê@ ˆÛC±{´7P¯@ÒıÛ@`ˆ@
Ò ˆÛbÚ"0@ÒıÛÚˇ@ıÛ@Ú@
ÒıÛ@Ú@ò@
@
Ä
˜
@
Ä
˜
∑â
˜Ä
 ˆÛ@Ú@ÒıÛ@Ú@
Ò ˆÛ@Ú@ÒıÛ@Ú@ıÛ@Ú@
ÒıÛ@Ú@ ˆÛÚˇ@ÒıÛ@Ú@
Ò ˆÛ@Ú@ÒıÛ@Ú@ıÛ@Ú@
ÒıÛ@Ú@ ˆÛ@Ú@ÒıÛ@Ú@
Ò ˆÛ@Ú@ÒıÛÚˇ@ı‡
@
Ò
ı‡@ ˆ‡
@Òı‡
@
Ò ˆÛÚˇ@ÒıÛ@Ú@ıÛ@Ú@
ÒıÛNà´òãä˜àê@ ˆÛC∂≤3j„‡¯@ÒıÛB{37≤≤0¯@
Ò ˆÛc≥{´3{˙¯"0@ÒıÛ@`ˆ@ıÛ@Ú@
ÒıÛÚˇ@ ˆÛ@Ú@ÒıÛ@Ú@
Ò ˆÛ@Ú@ÒıÛ@Ú@ıÛ@Ú@
ÒıÛ@Ú@ ˆÛ@Ú@ÒıÛ@Ú@
Ò ˆÛÚˇ@ÒıÛ@Ú@ıÛ@Ú@
ÒıÛ@Ú@ ˆÛ@Ú@ÒıÛ@Ú@
Ò ˆÛ@Ú@ÒıÛ@Ú@ıÛ@Ú@
ÒıÛÚˇ@ ˆ‡
@Òı‡
@
Ò ˆ‡
@Ò
ı‡@ı‡
@
Ò
ı‡@ ˆ‡
@Òı‡
@
Ò ˆ‡
@Ò
ı‡@ı‡
@
Ò
ı‡@ ˆ‡
@Òı‡
@
Ò ˆ‡
@Ò
ı‡@ò@
Ä
¿
˜
Ä
¿
˜
˜â7Ä
ı‡
@
Òı‰ˇ‡@ ˆ˜Ô @Òı˜Ô @
Ò ˆ˜"*Ô" @Òı˜Ô @ı˜Ô @
Òı    ààç»ààòÎà†@ ˆ˛˛
 @Ò!ı    vÔ~˛ø¸¸ˆ @
Ò% ˆ    ""/˚ˇÓ˙˛"    *#ˇ˚˙{ˇcˇ˙¯" @Ò"ı    √æŒÿ˛    øÛfiw˛~l¸¯ @#ı    ˚∂~~˛    Ûÿ~fl¸¯ @
Òı˛àâ˙àèˇÔˇÔÏ˚fl¸¯à†@ ˆ˛˚`ı @Òı˜
‡<ı @
Ò ˆ˜"*Ô" @Òı˜Ô @ı‰ˇ‡@
Òı˜Ô @ ˆ‰ @Òı‰ @
Ò ˆ‰ @Òı?Êˇ @ı ¯ @
Òı ¯ @ ˆ ¯ @Òı ¯ @
Ò ˆ ¯ @Òı Ä˝¯˙ @$ı     
 >˝
@
˙ @
Ò$ı     c∂ÛÏyÊ@∑„íˆÙvƒÛè˙ @' ˆ     ˆL…ò)üîXJjãDQ˙ @Ò%ı     Ń…ò%òTó“Jj˙O”˙ @
Ò( ˆ w<ËÁ@
à·æÌÍ7è1çÄ˚ @Òı ˝@ÄÄÛ @ı ˝@Ä9¿Û @
Òı ¯ @ ˆ ¯ @Òı ¯ @
Ò ˆ ¯ @Òı?Êˇ @ı ¯ @
Òı ¯ @ ˆ ¯ @Òı ¯ @
Ò ˆ ¯ @Òı ˙¿¯

Ä˝ @&ı     ˚
<˛fif @
Ò&ı     gƒ¸›æ퀺vfiŸ    áπΩ4] @) ˆ     Û‡¸
"≈\dRãQ    %D ¨Í¢ @Ò'ı     ì ¸
"ÖPDR˙    Q    %Dä•*æ @
Ò) ˆ q‰¸›ÌxÛú7Ü'fiπ˙Ù˙å @Òı ¯¸ ˘ @ı ¯¸8‡˘ @
Òı ¯ @$ ˆ ¯``0˝
@˛ @Ò"ı ¯Ä 
‡˝ @
Ò% ˆ ¯aÓoC8Áø8óœÁÄ @Ò"ı ¯¿ë2•%àêîDËòD    @ @#ı ¯¿ë"ß$hêî¸àÜDâ@ @
Ò"ı ¯AÓ~≠˚«|{«=Û>Á` @ ˆ ¯ @Òı ¯ @
Òò@
¿
Ú
˜
¿
Ú
˜7âiÄ
 ˆ ¯ @Òı ¯ @ı ¯ @
Òı ¯ @ ˆ?Êˇ @Òı‰ @
Ò ˆ‰ @Òı‰ @ı‰ @
Òı‰ˇ‡@ ˆ‡
@Òı‡
@
Ò ˆ‡
@Ò
ı‡@ı‡
@
Ò
ı‡@ ˆ‡
@Òı‡
@
Ò ˆ‰ˇ@Òı˜Ô@ı˜Ô@
Òı‰àê@ ˆ˜Ô@Òı˜Ô@
Ò ˆ˜"*Ô"0@Òı    ¿˛
@"ı˛˛ø¸¯˜@
Ò!ı    ààé˛Ôˇ˛˝àãˇ˚ÿ˚ˇÔü¯¯àê@% ˆ    ˚ˇŒÿ˛    øÛfiw˛oÃx¯@Ò#ı    √æŒÿ˛    Ûÿ~nÕÿ¯@
Ò% ˆ    ""/˚∂~~˛"    *'ˇgˇÔÓ˚Á~¯"0@Òı˛

ĸ`ı@ı˛˚
‡<ı@
Òı‰àê@ ˆ˜Ô@Òı˜Ô@
Ò ˆ‰ˇ@Òı‰@ı‰@
Òı‰@ ˆ?Êˇ¯@Òı ¯@
Ò ˆ ¯@Òı ¯@ı ¯@
Ò!ı ¯>˛| ˝@$ ˆ ¯∑„™flúo«UÕ¯˝@Ò"ı ¯îHRb&)(í' ˝@
Ò) ˆ Ä˝Tó»R~&    )/ìÂ$˝@Ò'ı     
 
à·ú#å√8Õò˝@ò@@
˜@
˜iâ©Ä?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒò@@Ä
˜@Ä
˜©âÈÄ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ?“ˇÒ“ˇÒ¡¡¡¡¡¡¡¡¡¡¡¡¡    #·¿c«
! ÄîÄ»
aÅÄ»
a¿ÅÄ»    í«    
!)«    ?√‡Δ«¡¡¡¡¡&
¯`
˛    ÄA é˝`Â%êêÅ˛

˝@ ˝ Â'#âË≤ãä~¥_"…Œ´ñÏu¨§AQÍ&∫+,娇Â'# YEpïÑL™e©¥(Ñ’‘¢Î*°ZíTUQ@Â'#
KN
‰¶$xEƒ-9≈2$Hxîôƒ…t@ÈÒ‰¢R@Â'#éàà?<á^: E[Ãx!-RE‡2ó¶à".¢¿Â'#ãáp>*(ËÖ§.Üí%HPÈ(»‚b:AÃy$x!—#`Â@Ô
 ‡@Ô
†‡ÄÔ
@‡¡¡'
膿‡@tH˝@Äp ¿Ä
8ÄÄÊ'E1˛@ @Ä˝  @
ÄÄÊ($≈)ÄvÂe•$eË∂ ∂≤6F\ì`-ı°—|ãcêRít∑ŒÊ($¶*ÄöJãfi§™IZ +SVZJ®©†F¢R≤®ï°(ÔUZêÊ($
,Äíúíî…íR JRR“ë1I D¬îó%"H$Jn'ìÊ($
HÅ&—)m~⁄¶‘Ñɶ◊˘“`≕ùy™cPDî∏™'ÇÊ($éi—§èΔHîë$$§¢‰âQ"H…DF÷ëB Œc'ÂÊ˝ 
ı¯Ñ·˝ 
ı¯Ñ·˙

ÎÑ·¡¡
˛@Äc
Ü
Δ ◊§@˝$îÅ ◊•ˆ\ãa”íî´∏ÍéCCê%wD†Ÿ
'(H®ï¢®wu@*î°¿dN®´–Ÿ
Igâ1%!·p)&8S%¡zD«%‹êŸm¡—˘™`r@#)KU≠
Ñ¢âa- ŸInëQCß∫Δ2pi6Ê√ÜN6Ó¿Ÿò@Ä¿
˜Ä¿
˜Èâ)Äı@˚
ÿı@˚
ÿı@˚
ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡ 
¿ÄÕ
 Äb
ÃbîêÄZ GÅl¿Œgz®Ä≠] *5@ŒíSpÅ)I\r&Õ
•¿GRvDN¿Œ;88íå\<FIŒ ˛Äà ˛Äà ˛…¡¡
‡A‡êw‡Ä
’ê@ê"@)
’í·<∂:Ÿ    î"N≤@)"˙Àí‹◊•Ab…ZRjâ(<ÀU@Ie) ◊
    ÅD RîLä#»DR^ÄR,·&I◊
¡%2¶∂ù0¯Dtà¿õ82?R◊äÉíq$‹íÁPÓTßà“-‚*"8◊¸à˛ ˛—¸à˛ ˛†—
¸p˙¿œ¡¡
˛@ §@$$ •ˆ\VD 
'(H®®D 
Igâ1(D m¡—˘P"H InëPê∞ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜)âiÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜iâ©Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜©âÈÄ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜Èâ)Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜)â[Ä¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜iâ©Ä
$ı     c∂ÛÏyÊ@Ä"˛˘@
Ò$ı     ˆL…ò)ü9¿Á˛
sÄ˙@ ˆ     Ń…ò%ò@Òı w<ËÁ@@
Ò% ˆ ˝@Ä
|˘@Ò%ı ˝@Äc€yƒ;Δ—Ô8fl6¸@!ı ¯¡
&$E)êîE8ò¸@
Ò ı ¯¡*'‰≈(êî˝ê¸@# ˆ ¯@ƒ8œª∑˝€Û<¸@Ò ı ¯ ˛Ä˚@
Ò" ˆ ¯p˛‡˚@Òı ¯@ı ¯@
Òı ¯@ ˆ?Êˇ¯@Òı ¯@
Ò ˆ ¯@Òı ¯@ı ¯@
Òı ˙@" ˆ     ˚ć¯@Ò$ı     gƒ¸@ê˚@
Ò& ˆ     Û‡¸ss7"êÃ4⁄ú˚@Ò#ı     ì ¸§œ£"ë(}ı>H˚@$ı q‰¸$Ã"¢ë(E"H˚@
Òı ¯#s°¬‡»<ıD˚@ ˆ ¯@Äı@Òı ¯@
Ù@
Ò ˆ ¯@Òı ¯¸ˆ@ı ¯¸
(
˜@
Òı ¯6ÜÜ≥į@ ˆ ¯˝O    .y˜@Òı ¯ÕH    )¡˜@
Ò ˆ ¯ΩG/8į@Òı ¯@ı ¯@
Òı ¯@ ˆ ¯@Òı ¯@
Ò ˆ ¯@Òı?Êˇ¯@ı‰@
Òı‰@ ˆ‰@Òı‰@
Ò ˆ‰@Òı‰ˇ@ı‡
@
Ò
ı‡@ ˆ‡
@Òı‡
@
Ò ˆ‡
@Ò
ı‡@ı‡
@
Ò
ı‡@ ˆ‡
@Òı‡
@
Ò ˆ‡ˇ
¿Ò¡“
Ò¡ ”Ò“
Òò@@Ä
˜@Ä
˜©âÈÄ
 ”Ò¡“
Ò¡ ”Ò“
Ò—3Ò“ÃÒ¡¡¡¡¡¡¡¡¡¡¡¡¡    #·¿c«
! ÄîÄ»
aÅÄ»
a¿ÅÄ»    í«    
!)«    ?√‡Δ«¡¡¡¡¡&
¯`
˛    ÄA é˝`Â%êêÅ˛

˝@ ˝ Â'#âË≤ãä~¥_"…Œ´ñÏu¨§AQÍ&∫+,娇Â'# YEpïÑL™e©¥(Ñ’‘¢Î*°ZíTUQ@Â'#
KN
‰¶$xEƒ-9≈2$Hxîôƒ…t@ÈÒ‰¢R@Â'#éàà?<á^: E[Ãx!-RE‡2ó¶à".¢¿Â'#ãáp>*(ËÖ§.Üí%HPÈ(»‚b:AÃy$x!—#`Â@Ô
 ‡@Ô
†‡ÄÔ
@‡¡¡'
膿‡@tH˝@Äp ¿Ä
8ÄÄÊ'E1˛@ @Ä˝  @
ÄÄÊ($≈)ÄvÂe•$eË∂ ∂≤6F\ì`-ı°—|ãcêRít∑ŒÊ($¶*ÄöJãfi§™IZ +SVZJ®©†F¢R≤®ï°(ÔUZêÊ($
,Äíúíî…íR JRR“ë1I D¬îó%"H$Jn'ìÊ($
HÅ&—)m~⁄¶‘Ñɶ◊˘“`≕ùy™cPDî∏™'ÇÊ($éi—§èΔHîë$$§¢‰âQ"H…DF÷ëB Œc'ÂÊ˝ 
ı¯Ñ·˝ 
ı¯Ñ·˙

ÎÑ·¡¡
˛@Äc
Ü
Δ ◊§@˝$îÅ ◊•ˆ\ãa”íî´∏ÍéCCê%wD†Ÿ
'(H®ï¢®wu@*î°¿dN®´–Ÿ
Igâ1%!·p)&8S%¡zD«%‹êŸm¡—˘™`r@#)KU≠
Ñ¢âa- ŸInëQCß∫Δ2pi6Ê√ÜN6Ó¿Ÿò@Ä¿
˜Ä¿
˜Èâ)Ä
ı@˚
ÿı@˚
ÿı@˚
ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡ 
¿ÄÕ
 Äb
ÃbîêÄZ GÅl¿Œgz®Ä≠] *5@ŒíSpÅ)I\r&Õ
•¿GRvDN¿Œ;88íå\<FIŒ ˛Äà ˛Äà ˛…¡¡
‡A‡êw‡Ä
’ê@ê"@)
’í·<∂:Ÿ    î"N≤@)"˙Àí‹◊•Ab…ZRjâ(<ÀU@Ie) ◊
    ÅD RîLä#»DR^ÄR,·&I◊
¡%2¶∂ù0¯Dtà¿õ82?R◊äÉíq$‹íÁPÓTßà“-‚*"8◊¸à˛ ˛—¸à˛ ˛†—
¸p˙¿œ¡¡
˛@ §@$$ •ˆ\VD 
'(H®®D 
Igâ1(D m¡—˘P"H InëPê∞ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜)âiÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜iâ©Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜©âÈÄ
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜Èâ)Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜)â[Ä
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ\Ú@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-38    )B
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records4^*¿
¯
°dONLNd\lhÑ(elFigurR¿°dONLNd\Ñhù)e 3-14@°dONLNd\ùh
) shows the object specifi#¿°dONLNd$\
h
)ker r%°dONLNd(\
h
))ecorô`°dONLNd,\
)h
ü)d for the Get Data event pr†°dONLNdG\
†h
˜)weviously illustrated °dONLNd\iluw(rlin π¿°dONLNd_iwuè)FiguråÄ°dONLNddièu£)e 3-4*°dONLNdii§u¥) on p‡°dONLNdmi¥uÀ)page K¿°dONLNdriÃuŸ)3-1°dONLNduiŸufi)
1°dONLNdvifiu
x)%. The object class ID tells the SurfWT`°dONLNdõi
xu
Â)öriter application that the °dONLNd∂vlÇo(l
rE°dONLNd∑vpÇ
)%equested data is an element of class ,
Courier{ °dONLNd‹v
Ç
3)ücTablex‡°dONLNd‚v
3Ç
˜)$.. The container for the table is the document °dONLNd
Élè˘(ål “Sales Report.” The key form is ¨°dONLNd
0ɢè
))çformName©°dONLNd
8É
)è
Á)0., which tells the server application that the °dONLNd
fêlú¥(ôlkey data identifiú†°dONLNd
wê¥úœ)Hes the "@°dONLNd
~ê–ú
Ù)BApple event object by name. The key data is the name of the table.

æ*œ
¯4ø*œ
¯"ø*]

ˇ·ˇ‚7^
    °dONLNd
¡¥løú(ºlFigure 3-14°dONLNd
Õ¥ÆøÔ)BAn object specifi†°dONLNd
fi¥ø
d)Ber record in a Get Data event

Œ*Q
¯4œ*P
¯

œ*Q
¯4Œ)œ*ò@@
˜@
˜œ*
!¡¡?Àˇ¯?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘ò@@Ä
˜@Ä
˜
*
O!?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ˇˇ¸?¿‚ˇ¯˝˜ˇÄ˘?ˇˇ¸¿8‚ˇ¯˝˜ˇÄ˘?ˇˇ¸
‚ˇ
¯8˛˜ˇÄ˘?ˇˇ¸
É‚ˇ
¯D˛˜ˇÄ˘?ˇˇ¸C‚ˇ
¯Ç˛˜ˇÄ˘?ˇˇ¸ #‚ˇ
¯Å˛˜ˇÄ˘?ˇˇ¸@ì‚ˇ¯áü‡˜ˇÄ˘ò@Ä¿
˜Ä¿
˜
O*
è!?ˇˇ¸ ÑK‚ˇ¯O‡˜ˇÄ˘?ˇˇ¸@àß‚ˇ¯/f˜ˇÄ˘?ˇˇ¸A!G‚ˇ¯
ʡĢ?ˇˇ¸Ç@ß‚ˇ¯@˜ˇÄ˘?ˇˇ¸Ç ÄG‚ˇ¯  ˜ˇÄ˘?ˇˇ¸Ñ ÄK‚ˇ¯@ê˜ˇÄ˘?ˇˇ¸ÑA;‚ˇ¯ ÑH˜ˇÄ˘?ˇˇ¸àA‚ˇ¯@৘ˇÄ˘?ˇˇ¸HB‚ˇ¯A!D˜ˇÄ˘?ˇˇ¸HÇ>‚ˇ¯Ç`§˜ˇÄ˘?ˇˇ¸ Ç~‚ˇ¯Ç –D˜ˇÄ˘?ˇˇ¸èΔ‚ˇ¯Ñ àH˜ˇÄ˘?ˇˇ¸üΔ˚‚ˇ¯ÑAD8˜ˇÄ˘?ˇˇ¸Ò«˚‚ˇ¯àA¢˜ˇÄ˘?ˇˇ¸Ò«‚ˇ¯HCQ˜ˇÄ˘?ˇˇ¸{«‚ˇ¯HǮʡĢ?ˇˇ¸uÔ‚ˇ¯ ÇT@˜ˇÄ˘?ˇˇ¸{◊ª‚ˇ¯Ç* ˜ˇÄ˘?ˇˇ¸uÔ[‚ˇ¯Ç˜ˇÄ˘?ˇˇ¸˚◊ª‚ˇ¯Ç
ò˜ˇÄ˘?ˇˇ¸uÔ[‚ˇ¯Ad˜ˇÄ˘?ˇˇ¸˚◊ª‚ˇ¯
A‰˜ˇÄ˘?ˇˇ¸uÔ[‚ˇ¯¿ÅјˇÄ˘?ˇˇ¸˚◊ª‚ˇ¯@@å˜ˇÄ˘?ˇˇ¸fl}Û‚ˇ¯ Ä|˜ˇÄ˘?€ˇ¯˜ˇÄ˘?€ˇ¯˜ˇÄ˘?€ˇ¯˝˜ˇÄ˘?€ˇ¯˝˜ˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘ò@¿

˜¿

˜
è*
œ!?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘ò@

@
˜

@
˜
œ*!?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘ò@
@
Ä
˜
@
Ä
˜*O!?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘?ÀˇÄ˘ÀˇÄ˘¡¡ò@
Ä
¿
˜
Ä
¿
˜O*è!¡¡¡¡¡¡¡¡¡¡¡¡¡
#‡‡Ä»
! @r@»
a@@»
a¿@$@»
íé$@»

 à$Ä»    ?¡s«¡¡¡¡¡"
Ù


p˛

¿É‡ 
‡"ê

˛Ä˛

 Å 
‡#ÖËŸ
6
àèé¢5—±deg¡H¡qBÈoÄ·"ΔY"é(YU’Tí¿ä™äBàÇ¢Ö*µ‡"

K'
‚|í&K¢ûàß@ùíDàoƒéO&‡"éD¶*í/(Ω4Åu«å)Ç'ÁàTO‡"ãCé8‰“«I#ÅâÖ«≈E# ‡@˙

—@˙
—Ä˙ 
—¡¡(
臿p@:HIJ@Ä8¿ÄÄ8Ä@Ê'D±@ @@@˝@ÄÄ@Ê($ƒ©Ä;‚≤“í2Ëõ[Z;F^ã`Ωë—>â±»Rët∂ÓÊ($•*ÄMEEÔRUIM)©ÆMJ§ï†&í*≤Tî–îÔRáZPÊ($
,ÄIéIJdâíII)*…ë)% $¢Lñâ$ë$Jg'íéÊ($

HÄì»èî∂ø⁄ì“BCì◊Ì™`I¥UúΩ©1®"&¬Ê($ãi»“áäc$Jë"RR“âIDi$&÷I!gc#ü‰úÊ˝˛Ñı¯Ñ·˝˛Ñı¯Ñ·
˘ÑÎÑ·¡¡
˛@Ä
@ÄF` ◊§@˝ ÄÄÇê 
◊§èÎ.â∞ÛâAï‹ÍNA†Ñïsá"PŸ
%òDTî—î
í∫†*T†„à~§
UËŸ
H∑Ñô$ê·8Ô”R•¿ÄH$√íÓHŸl·»˝©02 â%ÑT̃Q)`ñàêŸHæà©!Áùsô8h∂„cêΔGw`Ÿı ˚˛ÄŸı ˚˛ÄŸı ˚˛ÄŸ¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜è*¡!¡¡¡¡¡¡¡¡¡ 
¿

¿Õ Äb
ÄÕbîàÄZ GïÄÏ`ŒgzîÄ≠]…*
4†ŒíS8Å)IZr
%Õ
•†GRsDM`Œ;8íåZ<#HàŒ ˛@à ˛@à ˛…¡¡
‡!‡àwp?¿Ä÷ê ê" ÄÄ÷íÒ<õ:ÿâ    ‘"N± ¢˛À ‹◊•!b…MRiI
(<ÀR†$Â    ï ◊
    AD IîJJ»DRW@),Ò%%◊
a%2ì∂öí8xDtÑ`M∏:=™◊äCíq‹ë”–ÓT£ƒi-“)8◊¸à˛ ˛—¸à˛ ˛†—
¸p˙¿œ¡¡
˛@ §@$ §èÎ.K" 
%òDT§" 
H∑Ñô$" l·»˝H"$ Hæà®àò ¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜œ*
!
¡¡ 3¯À
¯ Ã
¯ ĢÀ
¯ Ģ Ã
¯À
¯ Ã
¯ ĢÀ
¯ Ģ Ã
¯Ï¿
Ä„
¯ Ì¿
Ä0Ê
¯Ì
ÁΩ˚wxÂĢÌ
ʘ˘ˇˇ∞Ê
¯Ì6˜¡é«∞ÂĢ Ó7Ω¯¸∏Ê
¯Ï
0‚
¯ Ì
0‚
¯ ĢÀ
¯ı?Ρ¿ÓĢ ˆ Î`Ô
¯ı Î`Ô
¯ ˆÍ"`Ô
¯ı Î`ÓĢı ˘
‡¿˜`Ô
¯ı(˘àã∏ÎË»¯à‡ÓĢ ˆ ˘Û}¯¯`Ô
¯ı ˘c~¸¯`Ô
¯ ˆ¯"&:cvÓ¯"`Ô
¯ı ˘ˇsfi¸¯`ÓĢı Î`Ô
¯ı(Îà‡ÓĢ ˆ Î`Ô
¯ı Î`Ô
¯ ˆ?Ρ‡Ô
¯ı Î`ÓĢı Î`Ô
¯ı Î`ÓĢ ˆ Î`Ô
¯ı Î`Ô
¯ ˆ ¿
˛ı`Ô
¯ı Å
ˆ`ÓĢı %πÕ3∏o˜K‚˜`Ô
¯ı ◊‰ì~`ıT…˜`ÓĢ ˆ $ëIòïT…Ę`Ô
¯ı —‰O?pr◊8Ú˜`Ô
¯ ˆ Î`Ô
¯ı Î`ÓĢı Î`Ô
¯ı ¸
Ù`ÓĢ ˆ
 Û¿ı`Ô
¯ˆ Ãî\€ê€pˆ`Ô
¯ ¯√ ƒ"dLIàˆ`Ô
¯˜ úîbG‚I    ¯ˆ
`¿ÔĢ˜ ˜ÛúÒº?Δ0ˆ
`‡
¯˜ Î
`∞ÔĢ ¯8 Î
`ú
¯˜` Î
`Ü
¯ò@@Ä
˜@Ä
˜
*
O!
 ¯¿¯?Ρ
‡É
¯¯É∞ Î`¡¿Ģ¯ Î`p`Ò
¯¯ ¿ÄPÙ`8Ģ ˘88 ä@ı`Ò
¯¯`` %π C?]/êˆ`Ò
¯! ˘¿¿ ◊‰äGñS'¿ˆ`ÉÄÚ
¯˘ÉÄ $äDñS&ı`¿¿ÒĢ ˘ —‰KÉä\„–ˆ```Ú
¯˘ Î`88ÒĢ ˙8 Î`Ú
¯˘`p Î`Ú
¯ ˙¿¿ Ó`Ú
¯˘ÅÄ Û¿GÄ@Ù`
√ÒĢ ˙

Რ    ÃîÚHÒÙ`aÄÛ
¯!˙
˛
 ƒ‚B\CÄı`0¿ÚĢ# ˚
˛
 úî~JdLÄı``Û
¯!˙
˛
 ˜Ûå7û3¿ı`0Û
¯ ˚
0˛ Î`Û
¯˙
0`˛ Î`ÚĢ˙
 ¿˛ Î`Û
¯˙
aIJ?Ρ‡
ÇÚĢ ˚¡˝ Î`˛√Û
¯˚

É˝ Î`˛
aÄÙ
¯ ¸
˝ Î`˛
 ÿÙ
¯$˚
˝ ¿ ˛†˜`˛
0xÛĢ%˚
˝ 
  ( ¯`˛
Ù
¯&˚
0˝ 
3;qú˘ù√~∫_ ˘`˛
ÛĢ( ¸
`˝ 
zO£Â3Û¨¶OĢ`˛
Ù
¯%˚
@˝ 
JL"e2ƒ¨¶L¯`˛
Ù
¯( ¸
¿˝ 
:;ë‹Ò˚Éîπ«†˘`˛
Ù
¯˚

Ä˝ ˝`˛
ÛĢı ˝p`˛
ƒÙ
¯ı Î`˝|ÛĢ ˆ ˝(ÄĈ`˝Ù
¯ı ˝ 
Ĉ`Ô
¯ ˆ w+3õÑ∑«Êˆ`Ô
¯˝

î˚ è˘¶E≥"üˆ`ÓĢ ˝PÄ˝ èI¶CS"òˆ`Ô
¯$˝ù¿˝ ˜+∏öBQ!óˆ`˝ÛĢ ˛“Ä˝ ˛DÔ`˝Ù
¯ ˝VÄ˝ ˛DÔ`˝fñ¿˜
¯ ˛ï“@˝ Î`˝Ù_Ę
¯ı ˛@Ô`˝ÑhÄˆÄ˘ı ¸@&`ˆ`˝tGĘ
¯ı ›ÃÁ0$(€Ñˆ`ÓĢ! ˝0Ä˝ e>fxºT@ˆ`Ô
¯¸
 
¸ 
Â2f@‰W¿ˆ`Ô
¯( w33õIJ ].>8^!Ĉ`¸
P
ˆ
¯ ˛L¥˘¶@˛ ˛Ô`¸
@ıĢ$˛    L¥I¶@˛ ˛8Ô`˛ÁS73į
¯ ˛w3∏ö@˛ Î`˛î‘˚J@˜Ä˘ ˛D˙ Î`˛    î‘KJ@¯
¯˝D˙ Î`˛ÁSπ2@¯
¯ ˆ?Ρ‡˝ÑÙ
¯ı Î`˝ÑÛĢı Î`Ô
¯¸
?¿¸ Î`ÓĢ ˝
¿8¸
?¿Ï
Ä
¯˝
¸
ÄÏ
¿˛8Ù
¯ ˛
Ä˝Î
¿˛DÙ
¯˝@˝Î˝ÇÛĢ˝  ˝Î>˝ÅÙ
¯˝@ê˝0θ˝áü‡ıĢò@Ä¿
˜Ä¿
˜
O*
è!
 ˛ ÑH˝‡Ï

˝O‡ˆ
¯˝@à§˛

ÄÏ
‡˝/fˆ
¯$ ˛A!D˛˛
†
Ä˝
Ę
¯'˝Ç@§˛˛@Ä˛Äˆ¸@ˆÄ˘(˝Ç ÄD˛‡lÕŒfÕˆˆ
¿˝  ˜
¯(˝Ñ ÄH˛‡iÚâıͺ¸ˇˆ`˝@êˆÄ˘( ˛ÑA8˝
 iâï*†ƒı`˝ ÑH˜
¯$˝
àA˚
 ®ÓNtÍú|ı`˝@৘
¯  ˛
HB˚ ¸Ò`˝A!D˜
¯˝HÇ>¸ ¸Ò`˝Ç`§ˆÄ˘˝ Ç~¸ Î`˝Ç –D˜
¯)˝èΔ¸ 
@˛D˛˘`˝Ñ àHˆÄ˘, ˛üΔ¯˝
 IJ˘`˝ÑAD8˜
¯*˝Ò«¯˝ ∏7Ln~3\ÿÃËÄ˙`˝àA¢ˆ
¯+ ˛Ò«˝ §Lfiî…|Õü2§˘`˝HCQˆ
¯*˝{«˝ dL–Ñ9DM맢`˝HÇ®ÄˆÄ˘+˝uÔ˝ d7NrÓ;ÃéÏúÄ˙`˝ ÇT@˜
¯"˝{◊∏˝ ¸@Û`˝Ç* ˆÄ˘$ ˛uÔX˝ ¸ÄÛ`˝Ç˜
¯˝˚◊∏˝ Î`˝Ç
ò˜
¯' ˛uÔX˝ 
†˛
Ù`˝Ad˜
¯%˝˚◊∏˝     `>Ù`˝
A‰ˆÄ˘%˝uÔX˝
 &;£Í#Ñpı`¸¿Åј
¯%˝˚◊∏˝
 /fHrDàı`¸@@åˆÄ˘' ˛fl}˝
 iÑíD¯ı`¸ Ä|˜
¯ı
 ßw#‹ü0ı`¸ı
¯ ˆ Î`¸ı
¯ı Î`ÓĢı Î`Ô
¯ı 
Ä   ˙`ÓĢ% Y˚ @Ä@˚`Ô
¯-˛½ fl.fÜsÊq“3¶7˚`˛
¿ëˆ
¯0 ù¡Ãfl`˛ %/©Ù
œ¶oë2JoJ˚`˛ ê ˜
¯0˛ò¡>è¿˛ e,©ÑÃ"hë*JhB˚`˛
â›]|¿˜Ä˘/˛ò≈2å@˛ ô'©tásûgqÃ3ß9˚`˝içi>į
¯*˛xπ.á¿˛ ˘@˛ ˙`˛)ãi0Ä˜Ä˘# ˆ ˘@˛@˙`˛
«ä)į
¯ı Î`Ô
¯ ˆ ¯
¿˛A¸`Ô
¯ı ¯
˝B˛ `ÓĢı ˙Ê7Ÿç埫ÿs4Ëgp`Ô
¯ı ˙üM}”2C0îÑن`ÓĢ ˆ ˙òEa
2C0ц`Ô
¯%˚¸ ˙Á=]    Œ—¬–s;‘tê`˝Ù
¯ ¸¸ ˘ÄÙ`˝Ù
¯˚¸ ˘ÄÙ`˝
¿ÙĢ˚
Ä˝ Î`˝
¿ı
¯"˚
‡˝ ˙¿ÄĢ`˝
0ÄÙĢ$ ¸
00˝ ˙
 Ä@˘`˝
aÄı
¯!˚
 p˝ ˙
Üô¬Yï˘`˝CÙ
¯" ¸
 @˝ ˘oøΩ2ê˘`˝¬Ù
¯"˚
 `˝ ˙)†¬a2ê˘`˛

ÜÛĢ"˚
(0˝ ˙
«üÇ]Ãà˘`˛

Ù
¯˚
<˝ ˆ
˜`˛
ÛĢ ¸
6˝ ˆ
˜`˛
Ù
¯˚
˝ Î`˛
0Ù
¯" ¸
˝ ¿
Û`˛
 Ù
¯#˚

Ü˝ 
òˆ`˛
`ÛĢ$˙É˝ G€B=Õ˓ˇ¯`˛
¿Ù
¯$˙¡˝ >C2†&T∑U¯`˛
0ÄÛĢ' ˚
aIJ °C2†$TôU¯`˛
!ÄÙ
¯$˙
0¿˛ ]Ç“¢=œ’◊‘`¯`˛aÛ
¯ ˚
`˛ ˛
Ô`˛√Û
¯˙
0˛ ˛Ô`˛ÜÚĢò@¿

˜¿

˜
è*
œ!
˙
˛ Î`
ÑÛ
¯&˙
˛ ¿Ä^˝8 ˚`ÚĢ( ˚
˛ ÇQ˝D ˚`Û
¯)˙

ܲ C∑dNç»n1¶8˚`ı
¯* ˙√˛ >D˙MJΩHîÔ`˚`0ı
¯)˘AÄ °D êMJ•(îFh˚``ÄıĢ,¸¿`¿ ]Éπt=Jù0d9Áp˚`@¿ˆ
¯$¸¿0` ˛
˙ ˜`0¿8‡ıĢ& ˝@0 ˛˙@˜`aÄpˆ
¯¸    @ Î`√Ĉ
¯ ˝
@ Î`
ÜĈ
¯¸@ Î`ÄıĢ¸@
ÅÄ Î`Ĉ
¯¸¿‡¿ Î`ÄıĢ ˝@0p Î`0Ĉ
¯¸    @ Î`0`Ĉ
¯ ˝
@ Î``¿Ĉ
¯¸@?Ρ‡¡ÄÄıĢ¸@
ÉÄΡ‡
ɲ
Ĉ
¯¸
¿˛
¿¿È
˛
ÄıĢ ˝
@˛
p`È
˛
Ĉ
¯¸
    @˛
0È
˛
Ĉ
¯ ˝

@˛
Í00˛
Ĉ
¯¸
@˛
͇`˛
ÄıĢ¸
@˛
ÉÍ¿¿˛
Ĉ
¯¸
¿˝
¡ÄÎIJ
ÄıĢ ˝
@˝
`‡Î
˝
Ĉ
¯¸
    @˝
8`Î
˝
Ĉ
¯ ˝

@˝
@Î
˝
Ĉ
¯ ¸
@˝
¿˘¿
Ĉ
˝
ÄıĢ#¸
@˝
Ģ¿
Ä0˘
7¸˝
Ĉ
¯¸
¿Ù
ÁΩ˚wx˘<¸
ÄıĢ ˝
@Ù
ʘ˘ˇˇ∞Û
Ĉ
¯¸
    @Ù6˜¡é«∞Û
Ĉ
¯ ˝

@Ù7Ω¯¸∏Û
Ĉ
¯¸
@Û
0Ô
ÄıĢ¸
@Û
0Ô
Ĉ
¯¸
¿fl
ÄıĢ ˝
@fl
Ĉ
¯¸
    @¸?Ρ¿¸
Ĉ
¯ ˝

@¸Í"`¸
Ĉ
¯¸
@¸ Î`¸
ÄıĢ¸
@¸ Î`¸
Ĉ
¯¸
¿¸(¯àûà∏˜à‡¸
ÄıĢ  ˝
@¸ ¯0˜`¸
Ĉ
¯¸
    @¸ ¯wª˜`¸
Ĉ
¯ ˝

@¸˜">˛ˇ˜"`¸
Ĉ
¯¸
@¸ ¯Δ˛˜`¸
ÄıĢ¸
@¸ ¯æ˜`¸
Ĉ
¯¸
¿¸(˜à
éé˜à‡¸
ÄıĢ ˝
@¸ ˜
˜`¸
Ĉ
¯¸
    @¸ Î`¸
Ĉ
¯ ˝

@¸Í"`¸
Ĉ
¯¸
@¸ Î`¸
ÄıĢ¸
|p¸?Ρ‡¸
Ĉ
¯¸
8∞¸ Î`¸
ÄıĢ ˝
`¸ Î`¸
Ĉ
¯¸
¿¸ Î`¸
Ĉ
¯ ˝
ĸ Î`¸
Ĉ
¯¸˚ Î`¸
ÄıĢı ¸˝
¯`Ô
¯ı ¸
IJ"¯`ÓĢ ˆ ¸'FÜ“7À˘`Ô
¯ı ¸
¶•OíJÔ∞˘`Ô
¯ò@

@
˜

@
˜
œ*!
 ˆ ¸¶•IäJ#,˘`Ô
¯ı ¸•Gå2Î∏˘`ÓĢı ¯ı`Ô
¯ı ¯ı`ÓĢ ˆ Î`Ô
¯ı ¸
3Δ;Δp˚`Ô
¯ ˆ ¸
    LÄ)D§
)Ä˚`Ô
¯ı ¸

LÄ)t§
!‡˚`ÓĢı ¸
LÄΔ§Δ˚`Ô
¯ı ¸
    LÄ    )L§
(ê˚`ÓĢ ˆ ¸
3Δ3œ`˚`Ô
¯ı Î`Ô
¯ ˆ Î`Ô
¯ı Î
`˘ˇ¯¯Ä˘

˘ˇÄ Î`Ä˙˘
¯

˘¿ Î`Ä@ÄÄ‡˙Ģ# 
Ôº˝=ˇ¿ Î`Ä 3
0˚
¯$
˺`ÄzΩ/¿?Ρ‡ÄDD@˚
¯# 
˺`ÄzΩ/¿Ρ‡Ä 3˝˚
¯

˺N≥c2ΩÔ¿Á
ÄLÄåû¿˙Ģ

˺.≤c2Ω¿ÁÄ˙˚
¯

Ôºn≥{2Ωˇ¿Á˘ˇ¸˙Ģ
 
˘¿ÁÄ˚˚
¯

˘ˇ¿ÁÄ˚˚
¯
 
˙
L¿ÁÄ˚˚
¯

˙
^¿Á
Äê
˙Ģ

˙
s¿Á
ÄÄ!˚
¯

@w¿Á
Ä”%÷˙Ģ
 
    @  T¿Á
Ä∑/>˚
¯

b·≥K0\¿Á
Ä∂'◊˚
¯
 
    W¢gÔp¿ÁÄ˚˚
¯

S°¶k‡@¿ÁÄ˚˙Ģ

˙
@¿ÁÄ˚˚
¯

˙
@¿Á
Ä
† ˙Ģ  
IJ
@¿Á
Ä
††˚
¯

Ä@@@¿Á
Äé¨≥˚
¯
 
ßÕ´DŸ@¿Á
ÄS\Ø˚
¯

    §í¨NªÄ@¿Á
ÄMX´Ä˙Ģ

GçõFù¿@¿ÁÄ˚˚
¯
D¸
@¿ÁÄ˚˙Ģ 
Ѹ
@¿ÁÄ
˛˚
¯

˙
@¿Á
Ä
@˚
¯
 
˙
@¿Á
ÄñcI˚
¯

˙
@¿Á
ÄfiÂÎÄ˙Ģ

˙
@¿Á
Ä◊√i¿˚
¯

˙
@¿ÁÄ˚˙Ģ
 
˙
@¿ÁÄ˚˚
¯

˙
@¿ÁÄ˚˚
¯
 
˙
@¿ÁÄ˚˚
¯

˙
@¿ÁÄ˚˙Ģ

˙
@¿ÁÄ˚˚
¯

˙
@¿ÁÄ˚˙Ģ
 
˙
@¿ÁÄ˚˚
¯

˙
@¿ÁÄ˚˚
¯
 
˙
@¿ÁÄ˚˚
¯

˙
@¿ÁÄ˚˙Ģ

˙
@¿ÁÄ˚˚
¯

˙
@¿ÁÄ˚˙Ģ) 
8˛@«¸Ò ˝¯Ä˚

¯*
Bu¶t3@¿Ò     8Ä˚
dÄ
¯* 
2kSTJ@¿Ò    ;¶,Ó Ä˚
AùÚÊ`
¯+

kULJ@¿
Ò    &oæî`Ä˚BR˙ü@Ģ+
qÎSH2@¿
ÄÚ    ¶h–î@Ä˚
¸FR ò@
¯-

˝@¿ÄÚ
ªßéí@Ä˝¿9ízó@Ģò@
@
Ä
˜
@
Ä
˜*O!
'
 
˝@¿ÄÒ"¸@Äù4⁄å¿˚
¯$

˙@¿ÄÒ"¸@Äö™ríÄ˚
¯$ 
˛@¿ÄÎ@Ä
ö™±íÄ˚
¯)
“0@¿Ä@@Äz™qÄ˙Ģ)
u@@¿Ä@IJ
˚
¯)

∑ @¿ÄgL‹n@IJ˙Ģ( 
rp@¿Ä    îfl(î@Ä˝˚
¯%

˙@¿Ä
î—î@Ä 0˛˚
¯%
 
˙@¿Ä
gN‰d@Äm@˛˚
¯$

˙@¿ÄÔ@˛@Ä
Ø ˛˙Ģ$

˙@¿ÄÔIJ@Äjp˛˚
¯&

¸‰Ä@¿Ä‡
Ú@Ä˚˙Ģ.
 
˛˛+@@¿Äê  
¯BÄ@Ä˚˚
¯.
ÅflÄF¿@¿Äñ|6z…g¯@@Ä@Ä˚˚
¯1 
¶GÛ‡I @¿ˇ‡ü>/3¢˘
rΔÊô‹ˇ¿Ä?˝ˇ˚
¯2

¶LnF¿@¿Äô2(3â˘ÀÈIø0@Ä 
˙Ģ2
fLwp@¿ÄÁ'‰w˘ÀH§Ã@Ä 
˚
¯+
ôò¨ÿ@¿ÄÚrÁ'ü∏@Ä!çÑ:!˙Ģ( 
;∏@¿ÄÒ¸@Ä RDQ˚
¯(
ÿ@¿ÄÒ¸@Ä “D1˚
¯+ 
?Î<@¿Ä@
DÚ@Ä 2D…˚
¯4
 ¸@¿ÄÄ!@Ä˚aÄD@Ä!ÕÑ1˙Ģ6
0D@¿Ä
Ï–}…ÜtÕ¿˝‡ Ä
@Ä 
˚
¯6
å@¿Ä“®?+…MÚÄ˝z§8éˇò@Ä 
˙Ģ6 
2(@¿Ä“®3*    MÄ˝àé$ë‘ä|@Ä 
˚
¯5
q@¿Äî…ΔtÓ@˝Äí$üTä`@Ä?˝ˇ˚
¯1 
b0@¿Ä˚˚yœ{Ê    LÜ\@Ä 
˚
¯(
»±1¿@¿Ä˚Ú@Ä 
˙Ģ$
Ï«ƒ‚â@¿ÄÎ@Ä 
˚
¯$
ì#ÀÅôÄ@¿ÄÎ@Ä ÌÑ9˙Ģ) 
” ~`@@¿ÄÒ
&
˝@Ä íD)!˚
¯)
3 
㎨
ÄÒ

˝@Ä “D˚
¯* 
ÿ˝\¿
Ú?1æ«8⁄`Ä 2D$    ˚
¯'

˙T¿Úd˙kÈ%ı<0Ä ÕÑ1˙Ģ'

˙w¿Ú¬+    %5 Ä 
˚
¯'

˙r«¯Úw9ÍÁ$ı¯Ä 
˙Ģ
 
˙
^¿Ò¯
Ä?˝ˇ˚
¯

˙
L¿Ò¯Ä˚˚
¯
 
˘ˇ¿Á˘ˇ¸˚
¯

˙
@¿ÁÄ˚˙Ģ

˙
~¿ÁÄ˚˚
¯

˙
f¿ÁÄ˚˙Ģ
 
˙
~¿ÁÄ˚˚
¯

˙
R¿ÁÄ˚0˚
¯
 
˙
^¿ÁÄ˚‡˚
¯

˘ˇ¿Á˘ˇ¸Ä˙Ģ
˘ˇ¿Á˙ˇ¸˘
¯ Ģ Ã
¯À
¯ Ã
¯ ĢÀ
¯ Ģ Ã
¯À
¯ Ã
¯ ĢÀ
¯ Ģ 3¯ÀU¯¡¡ò@
Ä
¿
˜
Ä
¿
˜O*è!
¡¡¡¡¡¡¡¡¡¡¡¡¡
#‡‡Ä»
! @r@»
a@@»
a¿@$@»
íé$@»

 à$Ä»    ?¡s«¡¡¡¡¡"
Ù


p˛

¿É‡ 
‡"ê

˛Ä˛

 Å 
‡#ÖËŸ
6
àèé¢5—±deg¡H¡qBÈoÄ·"ΔY"é(YU’Tí¿ä™äBàÇ¢Ö*µ‡"

K'
‚|í&K¢ûàß@ùíDàoƒéO&‡"éD¶*í/(Ω4Åu«å)Ç'ÁàTO‡"ãCé8‰“«I#ÅâÖ«≈E# ‡@˙

—@˙
—Ä˙ 
—¡¡(
臿p@:HIJ@Ä8¿ÄÄ8Ä@Ê'D±@ @@@˝@ÄÄ@Ê($ƒ©Ä;‚≤“í2Ëõ[Z;F^ã`Ωë—>â±»Rët∂ÓÊ($•*ÄMEEÔRUIM)©ÆMJ§ï†&í*≤Tî–îÔRáZPÊ($
,ÄIéIJdâíII)*…ë)% $¢Lñâ$ë$Jg'íéÊ($

HÄì»èî∂ø⁄ì“BCì◊Ì™`I¥UúΩ©1®"&¬Ê($ãi»“áäc$Jë"RR“âIDi$&÷I!gc#ü‰úÊ˝˛Ñı¯Ñ·˝˛Ñı¯Ñ·
˘ÑÎÑ·¡¡
˛@Ä
@ÄF` ◊§@˝ ÄÄÇê 
◊§èÎ.â∞ÛâAï‹ÍNA†Ñïsá"PŸ
%òDTî—î
í∫†*T†„à~§
UËŸ
H∑Ñô$ê·8Ô”R•¿ÄH$√íÓHŸl·»˝©02 â%ÑT̃Q)`ñàêŸHæà©!Áùsô8h∂„cêΔGw`Ÿı ˚˛ÄŸı ˚˛ÄŸı ˚˛ÄŸ¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜è*¡!
¡¡¡¡¡¡¡¡¡ 
¿

¿Õ Äb
ÄÕbîàÄZ GïÄÏ`ŒgzîÄ≠]…*
4†ŒíS8Å)IZr
%Õ
•†GRsDM`Œ;8íåZ<#HàŒ ˛@à ˛@à ˛…¡¡
‡!‡àwp?¿Ä÷ê ê" ÄÄ÷íÒ<õ:ÿâ    ‘"N± ¢˛À ‹◊•!b…MRiI
(<ÀR†$Â    ï ◊
    AD IîJJ»DRW@),Ò%%◊
a%2ì∂öí8xDtÑ`M∏:=™◊äCíq‹ë”–ÓT£ƒi-“)8◊¸à˛ ˛—¸à˛ ˛†—
¸p˙¿œ¡¡
˛@ §@$ §èÎ.K" 
%òDT§" 
H∑Ñô$" l·»˝H"$ Hæà®àò ¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜¡*
!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜
*A!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜A*Å!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜Å*¡!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜¡*
!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜
*A!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜A*Å!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜Å*≥!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜¡*
!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜
*A!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
˜Ä¿
˜A*Å!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜Å*¡!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜¡*
!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜
*A!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜A*Å!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜Å*≥!
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇAä@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡ä
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records

, (‡3-39
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähê(eä
Tµ¿°dONLNd
\èh)o add an object specifir`°dONLNd\Òh
)ber rs†°dONLNd\
h
)ecorË°dONLNd \
h
3)d to an Ɔ°dONLNd(\
3h
)!+Apple event as one of its parameters, your °dONLNdSiäu›(räapplication must fiû °dONLNdfi›uÛ)Srst cr≈`°dONLNdliÛu
P)eate the object specifi6†°dONLNdÉi
Qu
`)^er r7‡°dONLNdái
`u
r)ecor¨@°dONLNdãi
ru
})d. »°dONLNdéi
}u
ç)“Cr§°dONLNdëi
çu
Ê)eating Object Specifi†@°dONLNd¶i
Áu
Ú)Zer °dONLNd©väÇ£(äRecor¢`°dONLNdÆv£Ç¥)ds,”{ °dONLNd≤vµÇ
) which begins on ÎÄ°dONLNd√v
Ç
)Mpage Δ`°dONLNd»v
Ç
,)6-55@°dONLNdÃv
-Ç
m), describes the ï °dONLNd‹v
mÇ
’)@Apple Event Manager râ°dONLNdÒv
’Ç)houtines for °dONLNd˝Éäèí(åäcrµ@°dONLNdˇÉíèË)eating object specifiH`°dONLNd
ÉÈè¯)Wer rI†°dONLNd
ɯè

)ecoræ°dONLNd
É

è
)ds.°dONLNd
 ïä°ê(ûä
Tµ¿°dONLNd
!ïè°ö)o rp@°dONLNd
$ïõ°…)
espond to 5 °dONLNd
.ï…°
v).'Apple events that include object specifiP °dONLNd
Vï
v°
Ö)≠er rQ`°dONLNd
Zï
Ö°
ó)ecor≈¿°dONLNd
^ï
ó°
È)ds, your applicatioÇ`°dONLNd
qï
Í°)S    n should °dONLNd
z¢äÆê(´ä
uá °dONLNd
{¢êÆî)
sƒ °dONLNd
|¢îÆû)e tP °dONLNd
¢üÆÕ)
he standarú†°dONLNd
â¢ÕÆÛ).    d classifi °dONLNd
ì¢ÙÆ
B)'cation system for ®¿°dONLNd
•¢
AÆ
∑)MApple event objects and pr4‡°dONLNd
ø¢
∏Æ)wovide functions that °dONLNd
‘Øäª
ˆ(∏äTcan locate those objects within your application or its documents. The next section °dONLNd(ºä»*summarizes the classifiÚ‡°dONLNd?º»
)f
cation of ?¿°dONLNdIº
»
è))Apple event objects as defiF¿°dONLNddº
è»
Ω)vned in the †°dONLNdoº
æ»
Ú)/Apple Event °dONLNd{…ä’Ù(“äRegistry: Standard Suites.(`°dONLNdï…ı’˜)k
 

˙H

4˚H

 ¸ä¸

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdóÎä˙—(ˆäThe ClassifiH°dONLNd£Î“˙
    )H
cation of ≥°dONLNd≠Î
˙
Ñ)6Apple Event Objectsˇˇˇˇˇˇ€r(ˆ
3
°dONLNd¬

ä
ê(

ä
Tµ¿°dONLNd√

è
ü)o cr‡Ä°dONLNd«

ü
√)    eate or r„@°dONLNd–

√

)$esolve object specifiı‡°dONLNdÂ




))Wer r˜ °dONLNdÈ


)

;)ecorkÄ°dONLNdÌ


<

Ø)ds, your application shoulχ°dONLNd


Ø

Ω)sd uè¿°dONLNd



æ

¬)
sÿ°dONLNd


¬

Ã)e tX¿°dONLNd


Õ

˜)
he classifi;Ä°dONLNd


¯
)+cation °dONLNd 
ä
ï(
äof k°dONLNd#
ï
ˇ)Apple event objects defiµ°dONLNd;
ˇ

0)jned by the fl‡°dONLNdF

0

Ã)1%Apple Event Registry: Standard SuitesÕ†°dONLNdk

Õ

œ)ù
.M†°dONLNdl

–
    ) This section °dONLNdz
ä
'
h(
$ä2summarizes the concepts that underlie that classifi\Ä°dONLNd≠

i
'
™)flcation system. y‡°dONLNdº

™
'
∞)A
Y:`°dONLNdΩ

∞
')ou should have a copy °dONLNd”
(ä
4•(
1äof the &¿°dONLNd⁄
(¶
4
B)%Apple Event Registry: Standard SuitesÄ°dONLNdˇ
(
C
4
Ç)ù available for rΔ °dONLNd
(
Ç
4
í)?eferr@°dONLNd
(
ì
4)ence purposes while you °dONLNd+
5ä
Aç(
>ä
rE°dONLNd,
5é
A‘)ead this section.°dONLNd>
Gä
Sê(
Pä
Y@Ä°dONLNd?
Gê
S
¨)Aou do not need to write your application in an object-oriented pr†°dONLNdÄ
G
≠
S(
P
≠ogramming language °dONLNdì
Tä
`û(
]äin orÙ@°dONLNdò
Tû
`‡)der to support ò†°dONLNdß
T‡
`
ç)B'Apple event objects in your application_Ä°dONLNdŒ
T
é
`
º)Æ    . HoweverÏ °dONLNd◊
T
ª
`
Ï)-, you must °dONLNd‚
aä
mê(
jä
uá °dONLNd„
aê
mÌ)nderstand the classifiB °dONLNd˘
aÓ
m
Æ)^-cation system described in this section in or7`°dONLNd&
a
Æ
m
Ì)¿der to classify ܇°dONLNd6
a
Ì
m
)?Apple °dONLNd<
nä
zæ(
wäevent object`°dONLNdH
nø
z»)5s i¬¿°dONLNdK
n»
z
X)    !n your application and to write rÒ`°dONLNdl
n
X
z)ê*outines that can locate them on the basis °dONLNdñ
{ä
á
>(
Ñä)of information contained in object specifi`°dONLNd¿
{
?
á
N)µer r†°dONLNdƒ
{
N
á
`)ecorã°dONLNd»
{
`
á
j)ds„¿°dONLNd 
{
j
á
l)

.


•H
¨4
¶H
¨ 
ßä
ß

ˇ·ˇ‚7^°dONLNdÃ
òä
¶ì(
¢ä
O’Ä°dONLNdÕ
òì
¶⁄)    bject Classesˇˇˇˇˇˇ‘@(
¢
3
°dONLNd‹
¨ä
∏
0(
µä'Except for the concept of inheritance, z°dONLNd
¨
0
∏
í)¶Apple event objects arñ‡°dONLNd
¨
í
∏
•)be dif
‡°dONLNd
¨
¶
∏
≤)ferÌ`°dONLNd!
¨
±
∏
»)ent frc†°dONLNd'
¨
…
∏
)om the objects °dONLNd6
πä
≈˚(
Šused in object-oriented prᠡdONLNdP
π˚
≈
c)qogramming languages. — °dONLNde
π
c
≈
≈)hApple event objects arÓ°dONLNd{
π
≈
≈)be distinct items in °dONLNdè
Δä
“
ú(
œä?a server application or any of its documents that can be specifiZÄ°dONLNdœ
Δ
ù
“
˛(
œ
ùed by an object specifif@°dONLNdÊ
Δ
˛
“    )aer °dONLNdÈ
ӊ
flç(
‹ä
rE°dONLNdÍ
ӎ
fl†)ecorπ`°dONLNdÓ
Ӡ
fl¡)d in an Ň°dONLNdˆ
”¡
fl
t)!*Apple event sent by a client application. Ù†°dONLNd 
”
t
fl
÷)≥Apple event objects arÄ°dONLNd6
”
◊
fl)ce often, but °dONLNdC
‡ä
Ï
((
Èä%not always, items that a user can dif‹†°dONLNdh
‡
(
Ï
4)ûferø °dONLNdk
‡
4
Ï).entiate and manipulate within an application, °dONLNdô
Ìä
˘æ(
ˆäsuch as wor‘@°dONLNd§
Ìæ
˘
º)49ds, paragraphs, shapes, windows, or style formats. Every h °dONLNd›
Ì
Ω
˘)ˇApple event object °dONLNd
˙äΔ(äcan be classifi⁄†°dONLNdˇ
˙ΔÍ)<ed accor[°dONLNd
˙Î
~)%#ding to its object class, which defiFÄ°dONLNd+
˙
)î%nes both its characteristics and its °dONLNdPä±(äbehavior‹°dONLNdX∞
;)&#. The object classes listed in the ¿°dONLNd{
<
ÿ)å%Apple Event Registry: Standard Suites˚Ä°dONLNd†
ÿ
‰)ú prB†°dONLNd£
Â)ovide a °dONLNd´ä Í(ämethod of describing ο°dONLNd¿Í 
Q)`Apple event objects thaW`°dONLNd◊
R 
\)ht a¿°dONLNd⁄
] 
õ)ll applications^`°dONLNdÈ
õ 
‚)> can understandΩ°dONLNd¯
‚ )G    . Object °dONLNd    
!ä-‹(*äclasses permit mor$‡°dONLNd    !›-Í)Se fl{@°dONLNd    !Í-
Ê):exibility than simple descriptor types; for example, a wor∑ °dONLNd    Q!
Ê-)¸    d can be °dONLNd    Z.ä:ö(7ädefir °dONLNd    ^.õ:
D)(ned as a simple string, or it can be defiÊ °dONLNd    á.
D:
p)©
ned as an Ç°dONLNd    ë.
p:
¯),Apple event object with specifi)°dONLNd    ∞.
˘:
ˇ)âc °dONLNd    ≤;äGƒ(Dächaracteristic„Ä°dONLNd    ¿;ƒGŒ):s s›Ä°dONLNd    √;œG
)uch as font or stylü`°dONLNd    ÷;
G
%)Oe.

UHc4VHc
    °dONLNd    ŸTä_ù(\äNote

ˇ·ˇ‚7^
°dONLNd    fiaämÆ*The defi≠‡°dONLNd    ÊaÆm
I)$%nition of an object class only specifiC@°dONLNd
a
Jm
°)úes conventions that °dONLNd
 mäy
J(vä)determine how applications should handle n`°dONLNd
Im
Jy
∑)¿Apple event objects that °dONLNd
byäÖfi(Çäbelong to that class@°dONLNd
vyfiÖ‡)T
.p@°dONLNd
wy·Ö„)
 ¬†°dONLNd
xy„ÖÈ)
YÉ °dONLNd
yyÈÖˇ)our ar`°dONLNd
~y
Ö
p)pplication must make sur9†°dONLNd
ñy
qÖ
∫)qe that it uses the °dONLNd
©Öäë”(éäconventions corrD`°dONLNd
πÖ‘ë
)Jectly; they ar頡dONLNd
«Ö
ë
;)8e not enfore‡°dONLNd
“Ö
<ë
k)0ced by the —@°dONLNd
›Ö
kë
•)/Apple Event °dONLNd
Èëäù±(öäManagerT†°dONLNd
ë±ù≥)'
.,Zapf Dingbats‘†°dONLNd
Úî∏úæ)
uˇÒ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-40    )B
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records4^*¿
¯
°dONLNd\lh‡(elEach object class is identifi| °dONLNd\·h
)ued by a fourç¿°dONLNd)\
h
ÿ)5.-character object class ID, which can also be °dONLNdWiluo(rl
rE°dONLNdXipu~)epr’¿°dONLNd[i~u
Ÿ)Qesented by a constant. Constants for object classes always begin with the letter ,
Courier\†°dONLNd¨i
⁄u
‡(r
⁄
c\@°dONLNd≠i
‡u
Â). °dONLNd∞{lár(Ñl
T†¿°dONLNd±{ráê)he defi≠‡°dONLNd∏{êá
) nition of an object class specifi‡°dONLNdŸ{
á
.)Ües its 
s@°dONLNd‡{
.á
])
superclass£@°dONLNdÍ{
]á
‘)/, which is the object class fr4°dONLNd
{
’á
Â)xom °dONLNd
àlîë(ëlwhich a 
“`°dONLNd
àëî∑)%subclass¿°dONLNd
à∏î
)' (the class being defiƇ°dONLNd
1à
î
º)Y)ned) inherits some of its characteristics
`°dONLNd
Zà
Ωî
¬)¨. °dONLNd
\ïl°
(ûl(Characteristics can also be inherited frÂ`°dONLNd
Ñï
°
°)®"om special object classes, called 
H`°dONLNd
¶ï
¢°
»)é    abstract °dONLNd
Ø¢lÆß(´lsuperclasses,†@°dONLNd
º¢ßÆΔ); that arª`°dONLNd
ƒ¢ΔÆ
)e used only in defi¿°dONLNd
ע
Æ
∑)R&nitions of object classes and do not r@Ä°dONLNd
˝¢
∑Æ
Ÿ)ü    efer to ró °dONLNd¢
ŸÆ
Ë)"eal °dONLNd
Ølª
ö(∏lEApple event objects. The pattern of inheritance among object classes B@°dONLNdOØ
õª
—(∏
õis called the 
°dONLNd]ºl»á(≈lobjectB‡°dONLNdcºà»ä)
 ¬‡°dONLNddºä»
)class inheritance hierarchyq@°dONLNdº
»
)y
.Ò@°dONLNdĺ
»
)
 q@°dONLNdź
»
 )FigurD°dONLNdܺ
 »
9)e 3-15·Ä°dONLNdåº
9»
Ω) shows a portion of this hierar¿°dONLNd´º
æ»
Õ)Öchy«¿°dONLNdƺ
û
‰). The °dONLNd¥…l’™(“labstract superÅ °dONLNd¬…™’¡)>class ”¿°dONLNd»…¡’Î)cObject— °dONLNdœ…Î’
Y)* is at the top of the hierar2°dONLNdÎ…
Z’
d)ochs†°dONLNdÌ…
d’
q)
y aÇ¿°dONLNd…
q’
ö)
nd is ther7†°dONLNd˙…
õ’
¨)*efor膰dONLNd˛…
¨’
ˆ)e the only object °dONLNd÷l‚œ(fllclass that has no super“‡°dONLNd'÷œ‚Ë)cclass. G °dONLNd.÷È‚
<)At the next level ar`°dONLNdB÷
=‚
D)Te M°dONLNdD÷
D‚
b)cTextK °dONLNdI÷
b‚
ô), which is a r‡°dONLNdW÷
ö‚
Ó)8egular object class, °dONLNdl„lÔ(Ïland Ì °dONLNdp„ÔŸ)cOpenableObjectÁÄ°dONLNd„ŸÔ
P)Z, which is an abstract super±¿°dONLNdõ„
QÔ
a)xclasG`°dONLNdü„
bÔ
v)s. Bo†°dONLNd§„
wÔ
Ç)th ©`°dONLNdß„
ÇÔ
ä)arn`°dONLNd©„
ãÔ
í)    e ∏°dONLNd´„
íÔ
Õ)subclasses of °dONLNdπl¸ñ(˘lcObject}`°dONLNd¿ñ¸ƒ)*
 and super?`°dONLNd ≈¸
§)/5classes for their own subclasses. The object classes µ°dONLNdˇ
§¸
¬)flcWord≥ °dONLNd
¬¸
«), ≥ °dONLNd
«¸
Â)cItem±@°dONLNd
¸
Í), °dONLNd˝l
    (
land Ì °dONLNd˝
    ù)cCharÎ@°dONLNd˝ù
    ®) ar0@°dONLNd˝©
    ˘)e all subclasses of 9°dONLNd-˝˘
    
)PcTex7Ä°dONLNd1˝

    
)
t7 °dONLNd2˝

    
D). SimilarlyR`°dONLNd=˝
C
    
H),, R`°dONLNd?˝
H
    
N)
cR°dONLNd@˝
N
    
r)Windowd¿°dONLNdF˝
q
    
v)#, d¿°dONLNdH˝
v
    
¨)    cDocumenta`°dONLNdQ˝
¨
    
ƒ)6, and ŒÄ°dONLNdW˝
ƒ
    
‚)cFileÆ°dONLNd\˝
‚
    
Ì) ar†°dONLNd_˝
Ó
    
ı)e °dONLNda

l
ß(
lsubclasses of Ó`°dONLNdo

ß


);cOpenableObjectË¿°dONLNd~





‰)Z9. Every object class inherits all the characteristics of °dONLNd∑
l
#v(
 litsÁ¿°dONLNd∫
v
#x)

 g¿°dONLNdª
y
#í)super<†°dONLNd¿
í
#¢)clas“@°dONLNdƒ
¢
#≠)s aè@°dONLNd«
Æ
#
e)+nd can also add characteristics of its own.


E*
V
¯4
F*
V
¯"
F*]

ˇ·ˇ‚7^
    °dONLNdÛ
;l
Fú(
ClFigure 3-15°dONLNdˇ
;Æ
F
$)BSuperclasses and subclasses
°dONLNdl%}("lHer`°dONLNd}%ç)e arn†°dONLNd#ç%
) e some of the object classes defi †°dONLNdD
%
Z)äned for the CorÏ@°dONLNdS
Z%
y)Ce suite:
    °dONLNd\2l=Ñ(:lClass°dONLNdb2º=fl)PClass ID°dONLNdk2Ù=
%)8Description
°dONLNdx@lLä(IlcChar°dONLNd~@ºL‡)P'cha '°dONLNdÖ@ÙL˙)8
Tµ¿°dONLNdÜ@˘L
5)ext characters°dONLNdñPl\¢(Yl    cDocument°dONLNd†Pº\‡)P'docu'°dONLNdßPÙ\
U)8Macintosh documents°dONLNdº`llä(ilcFile°dONLNd¬`ºl‡)P'cfil'°dONLNd…`Ùl
*)8Macintosh fir@°dONLNd’`
+l
6)7les°dONLNd⁄pl|®(yl
cSelection°dONLNdÂpº|‡)P'csel'°dONLNdÏpÙ|
v)8User or application selections°dONLNdÄlåä(âlcText°dONLNdĺå‡)P'ctxt'°dONLNdÄÙå
H)8Series of characters°dONLNd/êlúñ(ôlcWindow°dONLNd7êºú‡)P'cwin'°dONLNd>êÙú
)8Standar¥@°dONLNdEê
ú
x)"d Macintosh windows


U*
¯4
V*

¯


V*
¯4
U)
V*ò@@
˜@
˜
V*
ñ!¡¡?Àˇ‡˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘ò@@Ä
˜@Ä
˜
ñ*
÷!?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘ò@Äú
˜Äú
˜
÷*
Ú!?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘òů@
˜HH
Î’î"IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@
˜
V*
ñ!'ÅÅÅâÅÅÅâ
æÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎσÎÅÅÅ 
ÎÏ≈ÏÅÅÅ 
ÏÎ≈ÎÅÅÅ 
ÎÎ≈ÎÅÅÅ 
ÎÏ≈ÎÅÅÅ 
ÎÎ≈ÏÅÅÅ 
ÏÎ≈ÎÅÅÅ 
ÎÏ≈ÏÅÅÅ 
ÏÎ≈ÎÅÅÅ 
ÎÎ≈ÎÅÅÅ 
ÎÏ≈ÎÅÅÅ 
ÎÎ≈ÏÅ”ßˇÅ“
ÏÎ≈ÎÅ”ˇ©
ˇˇÅ”
ÎÏ≈ÏÅ”ˇ©
ˇˇÅ”
ÏÎ≈ÎÅ”ˇ©
ˇˇÅ”
ÎÎ≈ÎÅ”ˇ©
ˇˇÅ”
ÎÏ≈ÎÅ”ˇ©
ˇˇÅ”
ÎÎ≈ÏÅ”ˇ©
ˇˇÅ”
ÏÎ≈ÎÅ”ˇ©
ˇˇÅ”
ÎÏ≈ÏÅ”ˇ©
ˇˇÅ”
ÏÎ≈!ÎÅ”ˇ‹
ˇˇ˚ˇ◊
ˇˇÅ”
ÎÎ≈$ÎÅ”ˇ·˛ˇ˛ˇÌˇÂ
ˇˇÅ”
ÎÏ≈2ÎÅ”ˇÊ¸ˇ˛ˇ˛ˇ
˛ˇ
˛ˇ˛˘ˇÁ
ˇˇÅ”
ÎÎ≈=ÏÅ”ˇÁˇ˛
ˇˇ˛ˇˇˇ˛ˇˇ˛ˇˇ˛ˇˇÂ
ˇˇÅ”
ÏÎ≈;ÎÅ”ˇÁˇ˝ˇ˛ˇˇˇ˛
ˇ¸ˇ
ˇ¸ˇˇË
ˇˇÅ”
ÎÏ≈7ÏÅ”ˇÊ˝ˇ˛ˇ
˝ˇ˝ˇ˛
ˇˇ˛˝ˇˇˇÁ
ˇˇÅ”
ÏÎ≈ÎÅ”ˇ‘ˇ◊
ˇˇÅ”
ÎÎ≈ÎÅ”ˇ÷
ˇˇ÷
ˇˇÅ”
ÎÏ≈ÎÅ”ˇ©
ˇˇÅ”
ÎÎ≈ÏÅ”ˇ©
ˇˇÅ”
ÏÎ≈ÎÅ”ˇ©
ˇˇÅ”
ÎÏ≈ÏÅ”ˇ©
ˇˇÅ”
ÏÎ≈ÎÅ”ˇ©
ˇˇÅ”
ÎÎ≈ÎÅ”ˇ©
ˇˇÅ”
ÎÏ≈ÎÅ”ˇ©
ˇˇÅ”
ÎÎ≈ÏÅ”ˇ©
ˇˇÅ”
ÏÎ≈ÎÅ”ˇ©
ˇˇÅ”
ÎÏ≈ÏÅ”ˇ©
ˇˇÅ”
ÏÎ≈ÎÅ”ˇ©
ˇˇÅ”
ÎÎ≈ÎÅ”¶ˇÅ”
ÎÏ≈ÎÅ“ßˇÅ”
ÎÎ≈ÏÅßˇÅ•
ÏÎ≈ÎÅßˇÅ•
ÎÏ≈ÏÅßˇÅ•
ÏÎ≈ÎÅßˇÅ•
ÎÎ≈ÎÅßˇÅ•
ÎÏ≈ÎÅßˇÅ•
ÎÎ≈ÏÅßˇÅ•
ÏÎ≈ÎÅßˇÅ•
ÎÏ≈ÏÅßˇÅ•
ÏÎ≈ÎÅßˇÅ•
ÎÎ≈ÎïÅˇ¶ˇë
ÎÏ≈Îñ
ˇˇÅ®
ˇˇí
ÎÎ≈ÏñˇÅ¶ˇí
ÏÎ≈Îó
ˇˇÅ¶ˇí
ÎÏ≈ÏóˇÅ•ˇí
ÏÎ≈ÎóˇÅ•ˇí
ÎÎ≈ÎóˇÅ•ˇí
ÎÏ≈ÎóˇÅ•ˇí
ÎÎ≈ÏóˇÅ•ˇí
ÏÎ≈ÎóˇÅ•ˇí
ÎÏ≈òů@Ä
˜HH
Î’ê#IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@Ä
˜
ñ*
÷!'ÏóˇÅ•ˇí
ÏÎ≈ÎóˇÅ•ˇí
ÎÎ≈ÎóˇÅ•ˇí
ÎÏ≈ÎóˇÅ•ˇí
ÎÎ≈ÏóˇÅ•ˇí
ÏÎ≈ÎóˇÅ•ˇí
ÎÏ≈Ï√®ˇÅ˛ßˇæ
ÏÎ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÎ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÏ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÎ≈Ï√ˇ™
ˇˇÅˇ©
ˇˇø
ÏÎ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÏ≈Ï√ˇ™
ˇˇÅˇ©
ˇˇø
ÏÎ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÎ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÏ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÎ≈Ï√ˇ™
ˇˇÅˇ©
ˇˇø
ÏÎ≈2Î√ˇ™
ˇˇÅˇ‹
ˇˇ˝
ˇˇÛ
ˇˇ˚ˇÌ
ˇˇø
ÎÏ≈?Ï√ˇ›¸ˇıˇ‡
ˇˇÅˇˆ˛ˇÈˇ¸ˇ¯˛ˇ˛ˇÌˇ˚
ˇˇø
ÏÎ≈lÎ√ˇ·¸ˇˇˇ˛ˇˇˇ˚ˇ‚
ˇˇÅˇ˚¸ˇ˛¸ˇ˛˛ˇ˝ˇ˝ˇ˛˛ˇ˛ˇ˝˛ˇ
ˇ˛ˇ˛ˇ
˛ˇ
˛ˇ˛˘ˇ˝
ˇˇø
ÎÎ≈âÎ√ˇ‚ˇ˛ˇˇˇ˛ˇ˛ˇˇ‡
ˇˇÅˇ¸ˇ˛
ˇˇ˛ˇˇˇˇ˛ˇˇˇ˛ˇˇˇˇ˛ˇ˛
ˇˇ˛ˇˇˇ˛ˇˇ˛ˇˇ˛ˇˇ˚
ˇˇø
ÎÏ≈~Î√ˇ‚ˇ˚ˇ¸ˇ
ˇˇˇˇ„
ˇˇÅˇ¸ˇ˝ˇ˛ˇˇˇ¸ˇˇˇˇˇˇˇˇ˛˚ˇ˛ˇˇˇ˛
ˇ¸ˇ
ˇ¸ˇˇ˛
ˇˇø
ÎÎ≈wÏ√ˇ·˝ˇ˛ˇ˛ˇˇˇˇˇˇˇˇ‚
ˇˇÅˇ˚˝ˇ˛ˇ
˛ˇ˝ˇˇ˛ˇˇˇ˘ˇ¸ˇ˛ˇˇ˛ˇ
˝ˇ˝ˇ˛
ˇˇ˛˝ˇˇˇ˝
ˇˇø
ÏÎ≈'Î√ˇ™
ˇˇÅˇÒˇœˇÌ
ˇˇø
ÎÏ≈(Ï√ˇ™
ˇˇÅˇÚ˛ˇ“
ˇˇÏ
ˇˇø
ÏÎ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÎ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÏ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÎ≈Ï√ˇ™
ˇˇÅˇ©
ˇˇø
ÏÎ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÏ≈Ï√ˇ™
ˇˇÅˇ©
ˇˇø
ÏÎ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÎ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÏ≈Î√ˇ™
ˇˇÅˇ©
ˇˇø
ÎÎ≈Ï√ߡÅ
¶ˇø
ÏÎ≈ά®ˇÅ˛ßˇø
ÎÏ≈ÏñˇÅ•ˇì
ÏÎ≈ÎñˇÅ•ˇì
ÎÎ≈ÎñˇÅ•ˇì
ÎÏ≈ÎñˇÅ•ˇì
ÎÎ≈ÏñˇÅ•ˇì
ÏÎ≈ÎñˇÅ•ˇì
ÎÏ≈ÏñˇÅ•ˇì
ÏÎ≈ÎñˇÅ•ˇì
ÎÎ≈ÎñˇÅ•ˇì
ÎÏ≈ÎñˇÅ•ˇì
ÎÎ≈Ï‘Ñˇ¢Éˇ—
ÏÎ≈&Î÷˛ˇƒˇƒ
ˇˇ§
ˇˇ√ˇƒ
ˇˇ“
ÎÏ≈%Ï÷ˇ¬ˇ√
ˇˇ•ˇ¬ˇ√
ˇˇ”
ÏÎ≈%Î◊
ˇˇ¬ˇ¬ˇ¶
ˇˇ¬ˇ¬ˇ”
ÎÎ≈#Î◊ˇ¡ˇ¬ˇ¶ˇ¡ˇ¬ˇ”
ÎÏ≈#Î◊ˇ¡ˇ¬ˇ¶ˇ¡ˇ¬ˇ”
ÎÎ≈#Ï◊ˇ¡ˇ¬ˇ¶ˇ¡ˇ¬ˇ”
ÏÎ≈#Î◊ˇ¡ˇ¬ˇ¶ˇ¡ˇ¬ˇ”
ÎÏ≈#Ï◊ˇ¡ˇ¬ˇ¶ˇ¡ˇ¬ˇ”
ÏÎ≈#Î◊ˇ¡ˇ¬ˇ¶ˇ¡ˇ¬ˇ”
ÎÎ≈#Î◊ˇ¡ˇ¬ˇ¶ˇ¡ˇ¬ˇ”
ÎÏ≈#Î◊ˇ¡ˇ¬ˇ¶ˇ¡ˇ¬ˇ”
ÎÎ≈#Ï◊ˇ¡ˇ¬ˇ¶ˇ¡ˇ¬ˇ”
ÏÎ≈#Î◊ˇ¡ˇ¬ˇ¶ˇ¡ˇ¬ˇ”
ÎÏ≈#Ï◊ˇ¡ˇ¬ˇ¶ˇ¡ˇ¬ˇ”
ÏÎ≈#Î◊ˇ¡ˇ¬ˇ¶ˇ¡ˇ¬ˇ”
ÎÎ≈#Έ»ˇˆ«ˇˆ»ˇÊ»ˇˆ«ˇˆ»ˇÙ
ÎÏ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÎ≈òůÄú
˜HH
Î’î$IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêêÄú
˜
÷*
Ú!'Aψˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÏÎ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÏ≈Aψˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÏÎ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÎ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÏ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÎ≈Aψˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÏÎ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÏ≈]ψˇ€
ˇˇÚ
ˇˇ˜ˇ…
ˇˇ˜ˇÈ
ˇˇ‰
ˇˇÁˇÏˇ˜
ˇˇÏ
ˇˇ˜ˇ…
ˇˇ˜ˇÁˇ˛
ˇˇÍ
ˇˇı
ÏÎ≈yΈˇÓˇˇˇˇÛˇÚ
ˇˇ˜ˇÌ¸ˇ
ˇ‰
ˇˇ˜ˇÌ˝ˇ
ˇ‰
ˇˇÁˇÙˇˇˇˇÛˇÏ
ˇˇ˜ˇ˘˝ˇfiˇ˘
ˇˇ˜ˇÓ˚ˇ˚ˇÍ
ˇˇı
ÎÎ≈fiΈˇÚ¸ˇ˝˝ˇˇˇˇˇ˝ˇÚ
ˇˇ˜ˇÚ˝ˇ˛ˇ˝ˇ
˛ˇ˛ˇ
ˇÒ
ˇˇ˜ˇÚ¸ˇ˛
ˇ˛ˇ˝ˇˇˇˇˇÚ
ˇˇÁˇ¯¸ˇ˝ˇˇˇ˝ˇ
˝ˇ
˛ˇˇˇˇˇ¯
ˇˇ˜ˇ˝˝ˇˇˇ˛ˇ
˚ˇ¸ˇˇ˛ˇ
˝ˇ˝ˇ˚
ˇˇ˜ˇÛ˝ˇˇ˛˛ˇ˝ˇ˝˛ˇÒ
ˇˇı
ÎÏ≈
    ΈˇÛˇ˛ˇˇˇˇ˛ˇˇˇˇ˛ˇÚ
ˇˇ˜ˇÛˇ˛ˇ˛ˇ˛ˇ˛ˇ˛ˇˇˇˇÚ
ˇˇ˜ˇÛˇ˛
ˇˇ¸ˇˇ˛ˇˇˇ
ˇˇÁˇ˘ˇ˛    ˇˇˇˇˇ˛ˇˇˇ˛ˇˇ˛ˇˇˇ˜
ˇˇ˜ˇ˛ˇ˛ˇˇˇˇ˛
ˇˇ˛ˇˇˇˇˇˇˇ˛ˇˇˇˇ˘
ˇˇ˜ˇÙˇ˛ˇ˛ˇ˛ˇ˝ˇ˛ˇ˛ˇÚ
ˇˇı
ÎÎ≈ÈψˇÛˇ¸¸ˇ˛ˇˇ˛ˇˇˇÚ
ˇˇ˜ˇÛˇ˙ˇ˛ˇ˚ˇˇˇˇÚ
ˇˇ˜ˇÛˇ˝ˇ˛ˇˇˇˇˇˇÔ
ˇˇÁˇ˘ˇ¸˝ˇ˛ˇ˛
ˇˇˇˇˇˇ˛
ˇ˝ˇ˜
ˇˇ˜ˇ˛ˇ¸ˇˇˇ˛
ˇˇ¸ˇˇˇˇ˚ˇ
ˇˇˇˇ¸
ˇˇ˜ˇÙˇ˚ˇ¸ˇ˝ˇ˛¸ˇÚ
ˇˇı
ÏÎ≈fiΈˇÚ˝ˇˇˇ˛ˇ
˝ˇˇˇˇˇÛ
ˇˇ˜ˇÚ˝ˇ¸ˇˇˇ˛ˇˇˇˇˇˇÚ
ˇˇ˜ˇÚ˝ˇ˛ˇ˛ˇˇˇ˘ˇÒ
ˇˇÁˇ¯˝ˇˇˇ˘ˇ˝ˇˇˇ˛ˇˇˇ˜
ˇˇ˜ˇ˝˘ˇ˛˛ˇ
˝ˇ
¸ˇ    ˇˇˇˇ˛ˇˇˇˇˇ˚
ˇˇ˜ˇÛ˝ˇ˛ˇ
˜ˇ˛
ˇˇÒ
ˇˇı
ÎÏ≈Aψˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÏÎ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÎ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÏ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÎ≈Aψˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÏÎ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÏ≈Aψˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÏÎ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÎ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÏ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÎ≈Aψˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÏÎ≈AΈˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇÁˇ 
ˇˇ˜ˇ…
ˇˇ˜ˇ 
ˇˇı
ÎÏ≈#ψ«ˇ˜Δˇ˜«ˇÁ«ˇ˜Δˇ˜«ˇı
ÏÎ≈#Îı»ˇˆ«ˇˆ»ˇÊ»ˇˆ«ˇˆ»ˇı
ÎÎ≈ò@@
˜@
˜
Ú*2!?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘?Àˇ˘Àˇ˘¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡


»

    8»

»
»
êËr»
ëÇ»
˛8»¡¡¡¡¡¿`¿`˝`
‡÷Äêrê˝ 
@÷OEêÄÇ4VhΩ…¬Ï·—CEÓNÿR (p @vz®©b5B3•K∞ÿíZp @”…]˘…&A◊(íÔŒÿÃt@à$Å3•{ƒ`ON¿]Kfi#ÿú\8ps¬ÿíªüäKcóÑÿ
˛"˚ Ã
˛"˚ Ã
˛˚ á¡(}†@8˛DÅD@
¿|Ê&)ä
ƒ¸@

@@Ä$Ê)%)L∑+-)#/E±µµë≤2‰õ
o≠ã‰[Ĭîê#•æpÁ)%1T“T^ı%RJ—
Zö≤“UEM5ïïD≠    @«z®8™‘ÄÁ)%—dî‰î¶HîíëRíñîâäI&§∏â)A"SpA<òpÁ)%bD    6à˘Kkˆ’0é§$6øŒìO%,ÎÕSÇ$•¿EQ<Á)%sNç$x¶2D§â q%%$JâFJ"6¥àís8¯è(‡Á˝
˛
@ıĢ
 ‚˝
˛
@ıĢ
 ‚˘
@Ï
 ‚¡¡ò@@Ä
˜@Ä
˜2*r!DÄÑ01Å0ÿ @˝"B
ÿ(ø≤‰[úêd]«TrÑ+∏r%Ÿ    9BED≠•@©+™
T•    )u@•^Ä⁄
K<Iâ)Å˛˝1¬ô.    fi¶9.‰Ä⁄nèÕSíHíXB≠h    À    hâŸKtäàí=–Á9ìÉI∑6Á2q∑vŸı˙@Ÿı˙@Ÿı˙@Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡
‡Õ
Õ§Ñ÷R8¨fŒ;’DjÓQP™ŒíõÑ    JJ„ê0Œ•.:êì≤ "vŒÿ…¡ƒîb·‚2HÄœ˛!˝ÄÃ˛!˝ÄÃ
˛!˝Ä ¡¡˛–¯
–ÇÄ@ê
–óâ±÷»í?Ÿy,—*J“ìTña"íê—L
&Rî¢d"fi$§ê—~    )ï5¥Ë    ≥áGµ —Tìâ&‰êç"˙E" —
¸@
À
¸@
À¸
Ä»¡¡    @¿¿À     @
! À    (ø≤‚∞" À        9BEE@‚ À
K<Iâ@ À    nè Å@À    KtäÑÄÂÄÀ¡¡¡¡¡¡¡¡¡ò@Äú
˜Äú
˜r*é!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡òů@
˜HH
Î’ê%IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@
˜
Ú*2!'ÎÅÅÅ 
ÎÏ≈ÎÅÅÅ 
ÎÎ≈ÏÅÅÅ 
ÏÎ≈ÎÅÅÅ 
ÎÏ≈ÏÅÅÅ 
ÏÎ≈ÎÅÅÅ 
ÎÎ≈ÎÅÅÅ 
ÎÏ≈ÎÅÅÅ 
ÎÎ≈ÏÅÅÅ 
ÏÎ≈ÎÅÅÅ 
ÎÏ≈ÏÅÅÅ 
ÏÎ≈
æÎÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛ÎÏ˛Î≈
¡˛ÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎ8ÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏÎÏ≈ÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâ͡˛¸ˇ˝˛ˇ˘ˇ˝ˇÅÅÅæ ͡˝ˇˇ¸ˇ˙˛ˇ
˛ˇÅÅÅæÎ
ˇˇ˝ˇ˘ˇ¯ˇ˝ˇÅÅÅæÎ
ˇˇ˝˛ˇ˚ˇ˘ˇ˝ˇÅÅÅΩ%Ïˇˇˇ˝˛ˇ
ˇ˝˛ˇˇ˝ˇÅÅÅΩ'Ìˇ˛ˇˇ˛ˇ˝ˇ˛ˇ¸ˇ˝ˇÅÅÅΩÓˇˇ˘ˇ˝¸ˇ¸˛ˇ
˛ˇÅÅÅæÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâ-Ì˚ˇÍ
ˇˇ˘ˇ˛˛ˇ˙
ˇˇÈ˛ˇfi
ˇˇıˇ˘˛ˇÅŨ3ÏˇˇÍˇˇ¸˛ˇˇ¯ˇˇÈˇ‹ˇıˇ¯ˇÅÅ´íÏˇ˛ˇ˝ˇ
ˇ˛ˇˇˇˇ˙ˇ˙ˇ˛ˇ˙ˇ¸ˇ˛ˇˇˇ˛ˇˇˇˇˇˇˇ˛
ˇ˝ˇ˛ˇˇ˛ˇ˝
ˇ˛ˇˇˇ˛ˇ˝˛ˇ
ˇ˛ˇˇ˝ˇˇˇ˛
ˇ˝ˇ˛ˇˇ˛ˇÅÅ¿ìÏˇˇˇˇˇˇˇˇˇ˛ˇˇ˝˛ˇ˚ˇ˚ˇ˙˛ˇˇˇ˝ˇˇˇˇˇ˛
ˇˇˇˇˇˇ˛ˇ˝ˇˇˇ˚ˇˇˇˇˇˇˇ˝ˇ˛ˇˇ˛ˇˇˇˇˇˇˇˇ˛ˇ˝ˇˇˇÅÅΩêÌˇ˛ˇˇˇˇˇˇˇ˛ˇ˘˝ˇˇ˚ˇ¯
ˇˇˇˇˇ˝ˇˇˇ˛ˇˇˇ˛ˇ˚ˇ
˛ˇˇˇˇˇˇˇ¸˛ˇˇ˛ˇˇˇ˛ˇˇˇ˛ˇ˚ˇ
˛ˇÅÅ¿íÓˇ˝ˇˇˇˇ˛˛ˇ
ˇ˛ˇ˚ˇ˛ˇ¸ˇˇˇ˚ˇˇˇ˛ˇˇˇˇ˛ˇ˛
ˇ˝ˇ˝ˇ˛ˇ˛
ˇˇ˚ˇ˝ˇˇ˛ˇˇˇ˙
ˇ˛ˇˇˇˇ˝ˇ˝ˇ˛ˇ˛
ˇˇ˚ˇÅÅ¿ãÓ
ˇˇ˛ˇ˛ˇ˛
ˇ˛ˇ˝˛ˇ˝˛ˇ¸˛ˇˇˇ˘
ˇˇ˝ˇˇˇˇˇ˛˝ˇ˝    ˇˇˇˇ˛ˇ˛ˇ
˚ˇ˛ˇˇˇˇˇˇˇˇ˛˛ˇˇ˝ˇ˝    ˇˇˇˇ˛ˇ˛ˇ
˚ˇÅÅøÁˇ˛ˇŒˇÅÅÅ‹Áˇ˛ˇŒˇÅÅÅ‹Ê˛ˇÕˇÅÅÅ‹ÅÅÅâÅÅÅâdÌ
ˇˇ˛¸ˇ
ˇ¸
ˇˇ˚˛ˇ˚ˇÍ˛ˇ
ˇˆˇˇÒ˛ˇ‡ˇ˜ˇ˛ˇÒ˛ˇ˚ˇÙ
ˇˇ˜ˇ˛ˇÛˇıˇÙ˛ˇ˙¸ˇÚˇÅØ\Ρ˛ˇˇˇˇ˛ˇˇ˙ˇ˙ˇÈˇÛˇ
ˇˇ˛ˇ÷ˇÏˇ˙ˇÛˇ˜ˇÔˇıˇÛˇ¯ˇˇÚˇÅØ˚Ï
ˇˇ˛ˇˇˇˇˇˇ˘˛ˇˇˇ˛ˇˇˇˇˇˇˇˇˇˇˇˇˇ˛ˇˇˇ˝ˇ
ˇ˛ˇˇˇˇˇ˛ˇ˘ˇˇˇˇˇˇˇˇˇˇˇˇ˛ˇˇˇˇˇ˛ˇˇˇ˛ˇˇˇˇˇˇˇ˙ˇˇˇ¸ˇˇˇˇˇ˝˛ˇ
ˇ˛
ˇ¸ˇˇ˛ˇˇˇˇˇ˛˛ˇˇ˙
ˇˇ˝ˇˇˇˇˇˇ˚ˇ˛˛ˇˇˇˇˇ¸ˇ
˛ˇÅµ
Ïˇˇˇˇ˛ˇˇˇˇ˙ˇˇˇˇˇˇˇˇ˛
ˇ˝ˇ˝ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ˛ˇ˙*ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ˛
ˇˇˇˇˇˇ˚ˇ˛ˇˇˇˇ˛ˇˇˇˇˇˇˇˇˇˇˇ˛
ˇˇˇˇˇˇ˝ˇˇˇ˚
ˇˇ˛˛ˇ˝ˇˇˇˇˇ¸˛ˇ˛ˇˇˇˇˇˇˇˇˇÅ≤
Ìˇ˛ˇˇˇ˛ˇˇˇˇ˙
ˇˇˇˇ˛ˇˇˇˇˇˇˇˇˇˇˇ˛ˇˇˇˇˇˇˇˇ˛ˇ˚"ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ˛ˇˇˇ˛ˇˇˇˇˇ˚ˇ˛ˇˇˇ˝ˇˇˇˇˇˇ˛ˇ˛ˇ˛ˇˇˇˇˇ˛ˇˇˇ¸ˇˇ˛
ˇˇˇˇˇ˛ˇ¸ˇ¸ˇ˝ˇˇˇˇ˝˛ˇÅµ˚Ìˇ˝
ˇˇ˛ˇˇ˛ˇ˚ˇˇˇˇˇˇˇ˛ˇ˛¸ˇˇˇˇˇˇˇˇˇ˚ˇˇˇˇˇˇˇˇˇˇ˝ˇ˛˛ˇˇˇˇ˝ˇˇ¸˛ˇˇˇˇˇˇˇ˘ˇ
˛ˇˇˇˇˇ¸ˇ˛ˇ˝ˇˇˇˇˇˇˇ˛ˇˇ˝ˇˇˇˇˇˇˇˇ˛ˇˇˇˇ¸ˇ˛ˇˇˇˇˇ˛ˇ˙ˇ˛ˇˇˇˇ˛ˇ˝ˇ¸ˇÅµ
Ó˛ˇ˛˛ˇˇˇˇ˛ˇ
ˇ˛    ˇˇˇˇˇ˛˝ˇ˛ˇˇˇˇ˛ˇˇˇˇ˛ˇˇˇˇˇ˛ˇˇˇ˚˛ˇ˛ˇˇˇˇˇˇˇ˛
ˇ˛ˇˇˇ˛ˇˇˇˇ˛ˇˇ˛ˇˇˇ˛    ˇˇˇˇˇ˛ˇ˛ˇ˛ˇˇˇˇˇˇˇˇˇ˛ˇ˛ˇˇˇ˝ˇ˛ˇ¸ˇˇ˛ˇˇˇ˛ˇˇˇ˛ˇ˛¸ˇ˛ˇ˛˝ˇˇˇ˛˛ˇÅ¥⁄ˇÂˇ˝ˇõˇµˇ˝ˇÅå⁄ˇÂˇ˝ˇõˇµˇ˝ˇÅåΩˇ˝ˇÅŒˇ˝ˇÅåÅÅÅâÅÅÅâòů@Ä
˜HH
Î’î&IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@Ä
˜2*r!'KÌ˘ˇ˜ˇ˜ˇ˛ˇÔˇÔˇ˛
ˇˇ˝ˇ˚ˇÒˇ˝
ˇˇˇ˝
ˇˇ˛
ˇˇ˚ˇ˜
ˇˇÅÅΩ?Ïˇˇˇˆˇ˜ˇŸˇ˛ˇ¸ˇ˙ˇÎˇÚ˛ˇ˛ˇ˝ˇ˘ˇˆˇÅÅΩûÏˇˇˇˇ˛
ˇ˙ˇˇˇˇ˛ˇˇ˛ˇˇˇˇˇ˝˛ˇˇ˛ˇˇˇ¸ˇˇˇ¸ˇˇˇˇ˛ˇ˛ˇ˛˛ˇˇˇˇ˛˛ˇˇ˝ˇˇˇ˚ˇˇ˝ˇ˝ˇˇ˛ˇ˛ˇ˝˛ˇˇ˛ˇˇˇÅÅ…£Ìˇˇ˛ˇˇˇ˝ˇˇ˛ˇˇˇ˛
ˇˇˇˇˇˇ˛ˇ˝    ˇˇˇˇˇ˚ˇˇˇˇˇˇ˛ˇˇˇˇ˘ˇˇˇˇˇˇˇˇ˝˛ˇ¸ˇˇˇˇˇ˛ˇˇˇˇ˚
ˇˇˇˇˇ˝ˇ
ˇÅÅ ñÌˇˇˇˇˇˇ˝ˇ˛ˇˇˇˇ˛ˇˇˇˇˇ˝˝ˇ˝
ˇ˛ˇ˚˘ˇ˚ˇˇˇˇ˛˛ˇ˝ˇˇˇˇˇˇ˛ˇ¸ˇ˙ˇ˛ˇ˝ˇˇˇˇˇ˛˛ˇˇˇ˛ˇ˛ˇˇˇÅÅ ôÓˇˇˇˇˇ˛ˇ¸˛ˇ
ˇ˛˚ˇˇˇˇˇˇˇˇ˚˛ˇˇˇ˜ˇˇ˛ˇˇˇˇˇˇ˝ˇ˝ˇˇˇˇˇˇˇˇˇ˙
ˇˇ˚ˇˇ˛
ˇˇ˛ˇˇˇˇˇ˝ˇˇˇˇˇ˛ˇ˛ˇˇÅÅ…™Óˇˇˇˇˇˇˇ˛ˇˇˇ˛ˇˇˇ˛ˇ˛ˇˇˇ˝˛ˇˇ˝ˇ˛ˇ
ˇ˝˛ˇ
˛ˇ
˛ˇˇˇˇ˛ˇ¸ˇˇˇˇˇˇˇˇ˛ˇˇˇˇˇ˝˛ˇ
˛ˇ
˛ˇˇˇˇ˛ˇ˛ˇˇˇˇ˛ˇ˛ˇˇˇÅÅ»õˇ«ˇÁˇÅÅΔõˇ«ˇÁˇÅÅΔõˇ«ˇÁˇÅÅΔÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâ͡ı˛ˇ¯˛ˇÈˇÚ˛ˇÅÅÅÁ!ÍˇÙˇ˘
ˇˇ˛ˇÍˇÒˇÅÅÅÊQÎ
ˇˇ˛ˇˇˇˇˇˇ˝ˇ˘ˇˇˇˇˇˇˇˇˇ˛˛ˇ˛ˇˇˇˇ˚
ˇˇˇˇˇˇˇÅÅÅSΡˇ˛ˇ˝ˇˇˇˇˇ˛ˇ˙
ˇˇˇˇˇˇ˛ˇ˛ˇˇˇ˛ˇˇˇ˙ˇ˛ˇˇˇˇˇÅÅÅOÏˇˇˇˇˇˇˇ˛ˇ˝ˇ˚ˇˇˇˇˇˇˇˇ˛ˇ˛˛ˇˇ˙ˇ˛ˇˇˇÅÅÅÌSÌˇ˛ˇˇˇˇˇ˛ˇ˙ˇ˛˛ˇˇˇˇ˝ˇˇ˛ˇˇˇˇ˛ˇ˙ˇ˛ˇ˛ˇˇˇÅÅÅWÓˇˇ˛ˇˇˇ˛ˇˇˇ˛ˇ¸˛ˇ˛ˇˇˇˇ˛
ˇˇ˛
ˇ˛ˇ˝˝ˇ˛ˇ˛
ˇˇˇˇˇ˛ˇÅÅÅÚÁˇ˝ˇ·ˇÌˇÅÅÅflÁˇ˝ˇ·ˇÌˇÅÅÅflÁˇ˝ˇ·ˇÅÅÅ ÅÅÅâÅÅÅâ'Ì˝ˇ˚ˇ¸˝ˇÈˇˇˇ˘ˇ˜ˇˆˇÅÅÅ˝/Ïˇˇ¸ˇ˚ˇˇÈˇÌˇˇˇˆˇˆˇÅÅÅ˝aÏˇˇˇ˛ˇ˝ˇ˛ˇ˛ˇ˝ˇˇˇˇˇˇ˛˛ˇ
ˇˇˇˇˇˇ¯ˇˇˇˇ˛˘ˇˇˇˇ˝ˇˇˇˇˇÅÅáiÏ    ˇˇˇˇˇ¸ˇˇˇ˛"ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ˙ˇˇˇˇˇˇˇ˝ˇˇ˛ˇˇˇˇˇˇÅÅÖgÌˇ˝ˇˇˇ˚ˇˇ˛ˇˇˇˇˇˇˇˇˇˇˇ˛ˇˇˇˇ˙ˇˇˇ˛ˇˇˇ˝ˇ˛ˇˇˇˇˇˇˇÅÅÖ_Ìˇ˝˚ˇ¸#ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ˛ˇ
ˇ˙    ˇˇˇˇˇ˛ˇ˝˛ˇ
ˇ˛˝ˇ    ˇˇˇˇˇÅÅÑhÓ˛ˇ˛ˇˇˇ¸˛ˇˇˇ˛ˇ˛ˇˇˇˇˇ˛ˇˇˇˇ˝ˇ˛ˇˇˇˇ˛
ˇ¸ˇˇˇ˛ˇˇˇ˛ˇ˛ˇÅÅÑ‘ˇ˛ˇ‰ˇÅÅÅŸ‘ˇ˛ˇ‰ˇÅÅÅŸ”˛ˇÅÅÅ∫ÅÅÅâÅÅÅâÌ˘ˇ˜ˇ˜ˇÛ
ˇˇ˚
ˇˇÅÅÅ”'Ïˇˇˇˆˇ˜ˇÙˇˇ˝ˇˇÅÅÅ‘9Ïˇˇˇˇ˛
ˇ˙ˇˇˇˇ˛ˇ˛ˇˇˇˇ˚ˇ˛ˇ˛ˇÅÅÅ‘<Ìˇˇ˛ˇˇˇ˝ˇˇ˛ˇˇˇ˛ˇˇˇ˚˛ˇ˛ˇ˛ˇÅÅÅ‘:Ìˇˇˇˇˇˇ˝ˇ˛ˇˇˇˇ˛ˇˇˇ¯ˇˇ˛ˇÅÅÅ‘7Óˇˇˇˇˇ˛ˇ¸˛ˇ
ˇ˛˚ˇˇˇˇ˚ˇ˛ˇˇˇÅÅÅ”;Óˇˇˇˇˇˇˇ˛ˇˇˇ˛ˇˇˇ˝ˇˇ˙˛ˇˇˇˇÅÅÅ“ÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâòůÄú
˜HH
Î’ê'IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêêÄú
˜r*é!'ÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâò@@
˜@
˜é*Œ!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜Œ*!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Äú
˜Äú
˜**!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡òů@
˜HH
Î’î(IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@
˜é*Œ!'ÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâòů@Ä
˜HH
Î’ê)IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@Ä
˜Œ*!'ÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâòůÄú
˜HH
Î’î*IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêêÄú
˜**!'ÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâò@@
˜@
˜**j!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜j*™!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Äú
˜Äú
˜™*Δ!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡òů@
˜HH
Î’ê+IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@
˜**j!'ÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâòů@Ä
˜HH
Î’î,IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@Ä
˜j*™!'ÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâòůÄú
˜HH
Î’ê-IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêêÄú
˜™*Δ!'ÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâò@@
˜@
˜Δ*!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
˜@Ä
˜*F!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Äú
˜Äú
˜F*b!¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡òů@
˜HH
Î’î.IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@
˜Δ*!'ÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâòů@Ä
˜HH
Î’ê/IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêê@Ä
˜*F!'ÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâòůÄú
˜HH
Î’î0IJˇˇˇˇˇˇ
ˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôô    ˇˇÃÃff
ˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃà ˇˇôô!ˇˇff"ˇˇ33#ˇˇ$ÃÃˇˇˇˇ%ÃÃˇˇÃÃ&ÃÃˇˇôô'ÃÃˇˇff(ÃÃˇˇ33)ÃÃˇˇ*ÃÃÃÃˇˇ+ÃÃÃÃÃÃ,ÃÃÃÃôô-ÃÃÃÃff.ÃÃÃÃ33/ÃÃÃÃ0ÃÃôôˇˇ1ÃÃôôÃÃ2ÃÃôôôô3ÃÃôôff4ÃÃôô335ÃÃôô6ÃÃffˇˇ7ÃÃffÃÃ8ÃÃffôô9ÃÃffff:ÃÃff33;ÃÃff<ÃÃ33ˇˇ=ÃÃ33ÃÃ>ÃÃ33ôô?ÃÃ33ff@ÃÃ3333AÃÃ33BÃÃˇˇCÃÃÃÃDÃÃôôEÃÃffFÃÃ33GÃÃHôôˇˇˇˇIôôˇˇÃÃJôôˇˇôôKôôˇˇffLôôˇˇ33MôôˇˇNôôÃÃˇˇOôôÃÃÃÃPôôÃÃôôQôôÃÃffRôôÃÃ33SôôÃÃTôôôôˇˇUôôôôÃÃVôôôôôôWôôôôffXôôôô33YôôôôZôôffˇˇ[ôôffÃÃ\ôôffôô]ôôffff^ôôff33_ôôff`ôô33ˇˇaôô33ÃÃbôô33ôôcôô33ffdôô3333eôô33fôôˇˇgôôÃÃhôôôôiôôffjôô33kôôlffˇˇˇˇmffˇˇÃÃnffˇˇôôoffˇˇffpffˇˇ33qffˇˇrffÃÃˇˇsffÃÃÃÃtffÃÃôôuffÃÃffvffÃÃ33wffÃÃxffôôˇˇyffôôÃÃzffôôôô{ffôôff|ffôô33}ffôô~ffffˇˇffffÃÃÄffffôôÅffffffÇffff33ÉffffÑff33ˇˇÖff33ÃÃÜff33ôôáff33ffàff3333âff33äffˇˇãffÃÃåffôôçfffféff33èffê33ˇˇˇˇë33ˇˇÃÃí33ˇˇôôì33ˇˇffî33ˇˇ33ï33ˇˇñ33ÃÃˇˇó33ÃÃÃÃò33ÃÃôôô33ÃÃffö33ÃÃ33õ33ÃÃú33ôôˇˇù33ôôÃÃû33ôôôôü33ôôff†33ôô33°33ôô¢33ffˇˇ£33ffÃç33ffôô•33ffff¶33ff33ß33ff®3333ˇˇ©3333ÃÙ3333ôô´3333ff¨333333≠3333Æ33ˇˇØ33ÃÃ∞33ôô±33ff≤3333≥33¥ˇˇˇˇµˇˇÃÃ∂ˇˇôô∑ˇˇff∏ˇˇ33πˇˇ∫ÃÃˇˇªÃÃÃúÃÃôôΩÃÃffæÃÃ33øÃÿôôˇˇ¡ôôÃìôôôô√ôôffƒôô33≈ôôΔffˇˇ«ffÃûffôô…ffff ff33ÀffÃ33ˇˇÕ33ÃÃŒ33ôôœ33ff–3333—33“ˇˇ”ÃÑôô’ff÷33◊ÿˇˇˇŸ˘`˘`˘`⁄Ú–Ú–Ú–€Ï@Ï@Ï@‹Â∞Â∞Â∞›fl fl fl fiÿêÿêÿêfl“““‡ÀpÀpÀp·ƒ‡ƒ‡ƒ‡‚æPæPæP„∑¿∑¿∑¿‰±0±0±0™†™†™†Ê§§§ÁùÄùÄùÄËñññÈê`ê`ê`Íâ–â–â–ÎÉ@É@É@Ï|∞|∞|∞Ìv v v ÓoêoêoêÔiiibpbpbpÒ[‡[‡[‡ÚUPUPUPÛN¿N¿N¿ÙH0H0H0ıA†A†A†ˆ;;;˜4Ä4Ä4į---˘'`'`'`˙ – – –˚@@@¸∞∞∞˝   ˛êêêÄú
˜F*b!'ÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâÅÅÅâˇB»@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡ä
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records

, (‡3-41
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähõ(eäHer`°dONLNd\õh´)e arn†°dONLNd\´h
5) e some of the object classes defi †°dONLNd(\
5h
m)äned for the T–Ä°dONLNd5\
mh
v)8ex¬¿°dONLNd7\
wh
á)
t su…@°dONLNd;\
áh
î)ite:°dONLNd
    Îä˜
L(Ùä-As you can see, some object classes, such as ,
Courierfi °dONLNd
6Î
L˜
j)¬cChar‹@°dONLNd
;Î
j˜
) and …`°dONLNd
@Î
Ę
û)cText«Ä°dONLNd
EÎ
û˜
´), aråÄ°dONLNd
IÎ
¨˜
ƒ)e defi»@°dONLNd
OÎ
ƒ˜
Ù)
ned in morG@°dONLNd
YÎ
ı˜)1e than °dONLNd
`¯ä

(

äone suite. For example, the defiä °dONLNd
į


L)änition of the ‹@°dONLNd
é¯
L

j)8cText⁄`°dONLNd
ì¯
j

¡) object class in the T °dONLNd
©¯
¡

ˇ)Wext suite is an 
°dONLNd
π
ä
µ(
ä    extension^†°dONLNd
¬
∂
‘), of the Ö`°dONLNd
 
‘
Ú)cTextÉÄ°dONLNd
œ
Ú

9) object class defiò`°dONLNd
·

9

x)Gned in the Cor∑¿°dONLNd
Ô

x

)?e suite; it duplicates all the °dONLNd
ä
˜(
ächaracteristics of the Corò¿°dONLNd(
˜

Ó)m9e suite object class and adds some of its own. Like a wor,¿°dONLNda

Ô

)¯d in a °dONLNdh
ä
+∑(
(ä
dictionaryðdONLNdr
∂
+”),, one o“°dONLNdy
”
+
)bject class I]¿°dONLNdÜ


+
)2D c@°dONLNdâ


+
^)an have several r¥`°dONLNdö

^
+
å)J
elated defi@°dONLNd•

ç
+
∞)/    nitions. ;°dONLNdÆ

∞
+
∂)#
Y˚Ä°dONLNdØ

µ
+)ou can choose to °dONLNd¿
,ä
8–(
5äsupport the defiB`°dONLNd–
,—
8
Ñ)G+nition that best suits your application; or `°dONLNd˚
,
Ñ
8
º)≥, if necessaryëÄ°dONLNd    
,
ª
8
Ì)7, you can cr °dONLNd
,
Ó
8)3eate °dONLNd
9ä
EÛ(
Bäextensions of your own.^Ä°dONLNd1
9Ù
Eˆ)j
 fiÄ°dONLNd2
9ˆ
E
)The exÄ°dONLNd8
9

E
.)tensioÑ¿°dONLNd>
9
.
E
T)    n of an oÊ`°dONLNdG
9
T
E
{)&
bject clasV†°dONLNdQ
9
|
E
í)(s is d‘¿°dONLNdW
9
í
E
ò)if„`°dONLNdY
9
ò
E
§)fer≈‡°dONLNd\
9
§
E
ª)ent fr< °dONLNdb
9
º
E)om inheritance °dONLNdq
Fä
R(
Oäbetween object classes. @°dONLNdâ
FÒ
R
a)gAn extension of a standarȆ°dONLNd¢
F
a
R
ß)pd object class prÔ@°dONLNd≥
F
ß
R)Fovides additional ways °dONLNd 
Sä
_”(
\äof describing an zÄ°dONLNd€
S”
_
w)I&Apple event object of that class, wher>Ä°dONLNd

S
x
_)•!eas the object class inheritance °dONLNd"
`ä
l§(
iähierarª°dONLNd(
`§
l
|)2chy determines the pattern of characteristics shar3@°dONLNdZ
`
}
l
§)Ÿ    ed by difY¿°dONLNdc
`
§
l
∞)'fer<@°dONLNdf
`
∞
l
˝)ent object classes.C°dONLNdy
`
˝
l
ˇ)M
 °dONLNd{
rä
~Æ(
{äThe defi≠‡°dONLNdÉ
rÆ
~
T)$'nition of an object class always specifiê`°dONLNd´
r
U
~
Õ)ßes a default descriptor typeπ†°dONLNd«
r
Õ
~)x. Suppose, for °dONLNd÷
ä
ãÕ(
àäexample, that a–Ä°dONLNdÂ
Õ
ã
)C client applicati^‡°dONLNdˆ


ã
?)D
on sends a÷Ä°dONLNd

?
ã
¡). Get Data, Cut, or Copy event∂‡°dONLNd

¬
ã
Ù)É that specifi{ °dONLNd*

ı
ã)3es an °dONLNd0
åä
ò
´(
ïäCApple event object but does not specify a descriptor type for the rg`°dONLNds
å
´
ò(
ï
´eturned data. In this °dONLNdâ
ôä
•§(
¢äcase, t9@°dONLNdê
ô•
•
)he server application r+‡°dONLNdß
ô

•
a)ceturns a descriptor rü@°dONLNdº
ô
a
•
s)Yecor†°dONLNd¿
ô
t
•)%d of the default descriptor type for °dONLNdÂ
¶ä
≤
(
Øäthe object class of the specifiï°dONLNd
¶

≤
)|ed ú°dONLNd
¶

≤)8Apple event object. For example, the default descriptor °dONLNd?
≥ä
øØ(
ºä    type for z‡°dONLNdH
≥Ø
ø
*)%Apple event objects of class n¿°dONLNde
≥
+
ø
I)|cWordl‡°dONLNdj
≥
I
ø
U) is í@°dONLNdn
≥
U
ø
ù)typeIntlTextç¿°dONLNdz
≥
ù
ø)H, a descriptor type that °dONLNdì
¿ä
ö(
…äspecifiÓ °dONLNdö
¿¶
Ã
})2es an undelimited string of characters in a specifi≈ °dONLNdÕ
¿
~
Ã)ÿc language and script system. °dONLNdÎ
Õä
Ÿ
(
÷ä!The client application can also r2Ä°dONLNd
Õ

Ÿ
Ä)åequest that the data be r@°dONLNd%
Õ
Ä
Ÿ
Î)jeturned in a descriptor rb¿°dONLNd>
Õ
Î
Ÿ
˝)kecor◊ °dONLNdB
Õ
˝
Ÿ)d of °dONLNdG
ڊ
ÊÈ(
„äsome other data type.°dONLNd]
Ïä
¯Æ*The defi≠‡°dONLNde
ÏÆ
¯
K)$&nition of an object class includes thr+`°dONLNdã
Ï
L
¯
ƒ)ûee lists of characteristics: pr¸¿°dONLNd™
Ï
ƒ
¯)xoperties, element °dONLNdº
˘ä¿(äclasses, and h°dONLNd…
˘¿
ı)6HApple events that support the object class. (The next section describes °dONLNdäì(äprG °dONLNdî
)
operties and element classes.) @°dONLNd2
)Ö7Any or all of these characteristics may be inherited frhÄ°dONLNdi)Èom °dONLNdlä™(äa super‘‡°dONLNds™√) class. I °dONLNdzƒ‘)An `°dONLNd}‘
˛)HApple event is listed for an object class if its parameters can specify °dONLNd≈ ä,
()äobjects of that class. The defi- °dONLNd‰ 
,
3)~nition for Ä°dONLNdÔ 
4,
^),cWindow&‡°dONLNdˆ 
],
©)), for example, list-`°dONLNd         
©,
º)Ls 12 °dONLNd     
º,
√)
A”@°dONLNd     
√,
ı)pple eventsì¿°dONLNd     
ˆ,
˚)3, °dONLNd    -ä9
P(6ä+including the Open, Close, and Move events,"°dONLNd    G-
Q9
¯)«% whose parameters can include object °dONLNd    l:äF¶(CäspecifiÓ °dONLNd    s:¶Fµ)er rÔ`°dONLNd    w:µF«)ecorc¿°dONLNd    {:»F
/)ds that specify window–°dONLNd    ë:
/F
5)gs.ç°dONLNd    ì:
6F
K) The H¿°dONLNd    ò:
LF
v)cWindowF °dONLNd    ü:
vF
Â)* class inherits all of these Á†°dONLNd    º:
ÂF)oApple °dONLNd    ¬GäS∞(Pä    events fr£ °dONLNd    ÀG∞S
)&om its abstract superUÄ°dONLNd    ‡G
S
%)\class, ( °dONLNd    ÁG
&S
Ä)cOpenableObject"Ä°dONLNd    ˆG
ÄS
Ç)Z
.°dONLNd    ¯Yäeù(bäThe ª¿°dONLNd    ¸Yùe
9)%Apple Event Registry: Standard Suites©Ä°dONLNd
!Y
:e
a)ù     also defi6Ä°dONLNd
+Y
be
s)(nes 
éÄ°dONLNd
/Y
se
‡)primitive object classes,߇°dONLNd
HY
‡e
¯)m whic®‡°dONLNd
MY
¯e)h °dONLNd
Ofärê(oä
dõ¿°dONLNd
Pfêr±)escribe `Ä°dONLNd
Xf±r
œ)!BApple event objects that contain a single value. For example, the ®°dONLNd
öf
œr
ˇ(o
œcBoolean•°dONLNd
¢f
ˇr)0, °dONLNd
§sä“(|äcLongIntegeræ °dONLNd
∞s—È)G, and +@°dONLNd
∂sÍ
)cAlias)°dONLNd
ºs

V)$ object classes ar`°dONLNd
Œs
V)H+e all primitive object classes. The object °dONLNd
˘Ääå
á(âä=class ID for a primitive object class is the same as the fouréÄ°dONLNd6Ä
áå
Ë)˝-character value of its °dONLNdNçäô
u(ñä7descriptor type. Primitive object classes contain no pr›¿°dONLNdÖç
uô
˝)Î operties; they contain only the °dONLNd•öä¶÷(£ävalue of the data.‰@°dONLNd∑ö÷¶ÿ)L
 d@°dONLNd∏öŸ¶€)
 
    °dONLNd@uäÄ¢(}äClass|@°dONLNdFu⁄Ä˝)PClass IDz°dONLNdOu
Ä
C)8Description
°dONLNd\Éäè®(åäcChar|@°dONLNdbÉ⁄è˛)P'cha 'z°dONLNdiÉ
è
)8
TØ¿°dONLNdjÉ
è
S)ext characters°dONLNdzìäü®(úäcLine|@°dONLNdÄì⁄ü˛)P'clin'z°dONLNdáì
ü
H)8Lines of text°dONLNdñ£äØΔ(¨ä
cParagraph|@°dONLNd°£⁄Ø˛)P'cpar'z°dONLNd®£
Ø
D)8
Paragraphs°dONLNd¥≥äø®(ºäcText|@°dONLNd∫≥⁄ø˛)P'ctxt'z°dONLNd¡≥
ø
f)8Series of characters°dONLNd◊√䜿(Ãä    cTextFlow|@°dONLNd·√⁄œ˛)P'cflo'z°dONLNdË√
œ
)8
TØ¿°dONLNdÈ√
œ
,)ext flq °dONLNdÔ√
-œ
?)ows°dONLNdÙ”äfl®(‹äcWord|@°dONLNd˙”⁄fl˛)P'cwor'z°dONLNd

”
fl
)8
Wè°dONLNd
”
fl
$)    or…Ä°dONLNd
”
$fl
.)    dsˇä@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-42    )B
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records4^*¿
¯

j*p
¯4j*p
¯ klk
¯

ˇ·ˇ‚7^°dONLNd\ljÔ(flProperties and Elementsˇˇˇˇˇˇ‘@(f
Ò
3
°dONLNdpl|(ylThe ª¿°dONLNdp|à)prLJ°dONLNdpâ|¨)
opertiesË °dONLNd'p¨|Δ)# listedù†°dONLNd.p«|…)
 †°dONLNd/p |
)for an object clasê¿°dONLNdAp
|
)I
sÕ¿°dONLNdBp
|
) cæ°dONLNdDp
|
S)an be used tÃÄ°dONLNdPp
S|
Ã)5o identify characteristics of ˙`°dONLNdnp
Ã|
”)y
A¡†°dONLNdop
‘|
Í)pple °dONLNdt}lâ
6(Ül0event objects that belong to that class. Each pr≈@°dONLNd§}
6â
) operty is identifiΔ†°dONLNd∂}
â
¥)Ied by a fourÿ@°dONLNd¬}
¥â
‚)5-character °dONLNdÕälñu(ìlprG °dONLNdœävñ˙)
operty ID, which can also be r-`°dONLNdÌä˙ñ
)Ñepræ °dONLNdä
ñ
≥)'esented by a constant. Constants for pr†°dONLNd
ä
¥ñ
Ÿ)¨    operties °dONLNd
 ól£È(†lalways begin with the letter ,
Courier… °dONLNd
=óÈ£Ô)}
p»¿°dONLNd
>óÔ£Ò)
.°dONLNd
@©lµ}(≤lHer`°dONLNd
C©}µç)e arn†°dONLNd
G©çµ›)e constants and prÛ¿°dONLNd
Y©›µ
A)Poperty IDs for some pr% °dONLNd
o©
Bµ
g)e    operties:°dONLNdD
àl
îÖ(
ëlThe pΩ‡°dONLNdI
àÖ
îà)
rLJ°dONLNdJ
àâ
î®)operty @°dONLNdQ
à©
î¡) of an D†°dONLNdW
à¡
î
=)Apple event object is itself d@°dONLNdu
à
>
î
H)}efi䠡dONLNdx
à
H
î
R)
ne†°dONLNdz
à
S
î
l)d as aÿ`°dONLNdÄ
à
l
î
ã) single ±‡°dONLNdà
à
ã
î
⁄)Apple event objec
`°dONLNdô
à
€
î
‡)Pt °dONLNdõ
ïl
°
0(
ûl-whose container is the object to which the pr†°dONLNd»
ï
1
°
u)≈operty belongs.g†°dONLNd◊
ï
u
°
√)D For example, the 6†°dONLNdÈ
ï
ƒ
°
‚)OpFont4¿°dONLNdÓ
ï
‚
°
‰)
 °dONLNdÔ
¢l
Æu(
´lprG °dONLNdÒ
¢v
Æ∫)
operty of a wor'`°dONLNd
¢∫
Æ›)Dd is defiZ†°dONLNd    
¢›
Æ
ç)#'ned by the name of a font, such as New ü†°dONLNd0
¢
ç
Æ
ì)∞
Y` °dONLNd1
¢
ì
Æ
Á)ork; the string that °dONLNdF
Øl
ªã(
∏lidentifiV†°dONLNdN
Øå
ª”) es the font is an 0 °dONLNd`
Ø”
ª
J)GApple event object of class Á°dONLNd|
Ø
J
ª
h)wcText °dONLNdÅ
Ø
h
ª
m). °dONLNdÑ
¡l
Õw(
 lThr °dONLNdÜ
¡x
Õß)e constant Ü°dONLNdë
¡ß
Õ›)/    cPropertydž°dONLNdö
¡›
Õ˚)6 specifip¿°dONLNd¢
¡¸
Õ

)es t9¿°dONLNd¶
¡

Õ
¶)%he object class for any object specifi“@°dONLNdÃ
¡
¶
Õ
µ)õer r”Ä°dONLNd–
¡
µ
Õ
«)ecorG‡°dONLNd‘
¡
»
Õ
‰)d that °dONLNd€
Œl
ڋ(
◊lidentifiV†°dONLNd„
Ό
⁄®) es a pr$`°dONLNdÍ
Ω
⁄Δ)operty°dONLNd
Œ≈
⁄ ). °dONLNdÛ
Âl
Òÿ(
ÓlCONST cProperty = y@°dONLNd
Âÿ
Òfi)l
'x‡°dONLNd
Âfi
Òˆ)propw`°dONLNd

ˆ
Ò¸)
'w°dONLNd
¸
Ò
)
;°dONLNd
˝l    ¥(lAn object specifiV‡°dONLNd
˝µ    ƒ)Ier rX °dONLNd"
˝ƒ    ÷)ecorÃÄ°dONLNd&
˝÷    ˇ)
d for a prÎ`°dONLNd0
˝ˇ    
:))operty specififi‡°dONLNd>
˝
;    
F)<es eÄ°dONLNdA
˝
G    
})    cPropertyb °dONLNdJ
˝
}    
ã)6 as ü °dONLNdN
˝
ã    
“)the object class I˝¿°dONLNd`
˝
“    
‹)GD,;°dONLNdb
˝
›    
Ô) the °dONLNdg
l
(l"Apple event object to which the pr…†°dONLNdâ


ç)òoperty belongs as the containerË °dONLNd®

ç
í)â, Ë °dONLNd™

í
Ê)formPropertyID‚‡°dONLNd∏

Ê
Ì)T ab‡°dONLNd∫

Ó
Ù)s °dONLNdºl#
( l%the key form, and a constant such as O`°dONLNd·
#
-)£pFontMÄ°dONLNdÊ
-#
q) as the key data≠‡°dONLNdˆ
q#
v)D. ≠‡°dONLNd¯
v#
x)
 -‡°dONLNd˘
y#
{)
 °dONLNd˚)l5(2lThe 
ª¿°dONLNdˇ)5®)elements” °dONLNd)®5Ÿ)) of a specifi䆰dONLNd)⁄5‡)2c Ä°dONLNd)·5
?)Apple event object ar¸`°dONLNd+)
>5
o)]e the other 
Ä°dONLNd7)
p5
Δ)2Apple event objects‚`°dONLNdJ)
Δ5
—)V it °dONLNdN6lBö(?lcontains, e9‡°dONLNdY6õB
)/xcluding those that defi°dONLNdq6
B
&)h    ne its prH‡°dONLNdz6
'B
F)$opertieq °dONLNdÅ6
FB
L)s.. °dONLNdÉ6
MB
O)
 O¿°dONLNdÑ6
OB
ó)An object specifi&†°dONLNdï6
òB
ß)Ier r'‡°dONLNdô6
ßB
π)ecorú@°dONLNdù6
πB
fi)    d for an °dONLNd¶ClOÆ(Llelement specifiõ °dONLNdµCÆO…)Bes the  ¿°dONLNdºC O
Î)BApple event object in which the element is located as the containe†°dONLNd˛C
ÏO
Ú(L
Ïr °dONLNdPl\q(Yl
a°dONLNd
Pq\
    )!nd can specify any key form excep˘¿°dONLNd"P
    \
)òt º °dONLNd$P
\
)
fª¿°dONLNd%P
\
c)ormPropertyID∂‡°dONLNd2P
c\
h)N. ∂‡°dONLNd4P
h\
Ï) Each object class definition in °dONLNdT]li|(flthe ›`°dONLNdX]|i
)%Apple Event Registry: Standard SuitesÀ °dONLNd}]
i
e)ù includes a list of 
†Ä°dONLNdë]
fi
ä)MelementG†°dONLNdò]
ãi
ç)%
 
«†°dONLNdô]
çi
Æ)classes,\Ä°dONLNd°]
Øi
ÿ)"     which ars‡°dONLNd™]
ÿi
Ô))e the °dONLNd∞jlv
(sl'object classes of the elements that an É@°dONLNd◊j
v
ô)£Apple event object can contain.ì°dONLNdˆj
ôv
õ)ä
 
    °dONLNd
y¬lÕê( lProperty°dONLNd
Ǭ‘Õ
)hProperty IDˇÄ°dONLNd
é¬
Õ
I)DDescription
°dONLNd
õ–l‹ä(ŸlpName°dONLNd
°–‘‹¯)h'pnam'ˇÄ°dONLNd
®–
‹
N)DName of an ®`°dONLNd
≥–
N‹
†)6Apple event object°dONLNd
«‡lÏñ(ÈlpBounds°dONLNd
œ‡‘ϯ)h'pbnd'ˇÄ°dONLNd
÷‡
Ï
$)DCoå°dONLNd
ÿ‡
%Ï
.)orΔÄ°dONLNd
⁄‡
.Ï
à)    dinates of a window°dONLNd
Ôl¸ú(˘lpVisible°dONLNd
¯‘¸¯)h'pvis'ˇÄ°dONLNd
ˇ
¸
ø)D%Indicates whether a window is visible°dONLNd&
l
ú(
    lpIsModal°dONLNd/
‘
¯)h'pmod'ˇÄ°dONLNd6



æ)D#Indicates whether a window is modal°dONLNd[
l
ê(
lpClass°dONLNdb
‘
¯)h'pcls'ˇÄ°dONLNdi



X)DClass ID of an —°dONLNdx

X

™)@Apple event object°dONLNdå
 l
,ä(
)lpFont°dONLNdí
 ‘
,¯)h'font'ˇÄ°dONLNdô
 

,
,)DFont°dONLNdü
0l
<®(
9l
pTextStyle°dONLNd™
0‘
<¯)h'txst'ˇÄ°dONLNd±
0

<
)D
T5@°dONLNd≤
0

<
B)    ext style°dONLNdΩ
@l
Lê(
IlpColor°dONLNdƒ
@‘
L¯)h'colr'ˇÄ°dONLNdÀ
@

L
)D
T5@°dONLNdÃ
@

L
C)    ext color°dONLNd◊
Pl
\¿(
YlpTextPointSize°dONLNdÊ
P‘
\¯)h'ptps'ˇÄ°dONLNdÌ
P

\
B)D
Point size°dONLNd˘
`l
l®(
il
pScriptTag°dONLNd
`‘
l¯)h'psct'ˇÄ°dONLNd
`

l
u)DScript system identifié¿°dONLNd!
`
v
l
~)^er°dONLNd%
pl
|®(
yl
pFillColor°dONLNd0
p‘
|¯)h'flcl'ˇÄ°dONLNd7
p

|
>)D
Fill colorˇ>fi@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡ä
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records

, (‡3-43
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähë(eä
AG@°dONLNd
\íhö)n :@°dONLNd\öhÈ)Apple event objecí¿°dONLNd\ÈhÛ)Ot c≈`°dONLNd\Ûh
)
ontain`°dONLNd\
h
)
sE`°dONLNd\
h
)
 ≈`°dONLNd\
h
/)exactlR†°dONLNd%\
0h
=)y o◊@°dONLNd(\
=h
é)ne of each of its prø °dONLNd<\
éh
Õ)Qoperties, wher€`°dONLNdJ\
Õh
˜)?eas it can °dONLNdUiäu§(räcontaia‡°dONLNd[i•uÍ)n no elements oŸ†°dONLNdjiÍu)Er L@°dONLNdliÒu
ù)%many elements of the same element claÒ¿°dONLNdëi
ùu
Ì)¨ss. In general, a pr1Ä°dONLNd•i
Óu)Qoperty °dONLNd¨väÇ
{(ä8of an object describes something about that object; a pr«Ä°dONLNd‰v
{Ç
Ú)Òoperty can be examined or °dONLNd˛Éäè©(åächangeο°dONLNd
É©è∑)d b °dONLNd
É∏èæ)
u@°dONLNd
Éæè…)t n™°dONLNd
É…èÿ)eve„Ä°dONLNd
Éÿè‰)r dq‡°dONLNd
ÉÂè
)eleted. ∂‡°dONLNd
É
è
â)An element can be one or morñÄ°dONLNd
5É
âè
•)Öe discrVÄ°dONLNd
<É
¶è)ete objects contained in °dONLNd
Uêäú≈(ôäanother objec§†°dONLNd
bê≈úœ);t ag°dONLNd
eê–ú
E)nd can usually be deleted. °dONLNd
Å¢äÆ¿(´äFor exampleq†°dONLNd
墡Æ)7, because a¿‡°dONLNd
ó¢Æ
à)/! paragraph can contain one or mor܇°dONLNd
∏¢
âÆ
¢)ôe worb°dONLNd
Ω¢
¢Æ)ds, one of the element °dONLNd
‘Øäª
(∏ä$classes listed for the object class ,
Courier ‡°dONLNd
¯Ø
ª
T)é
cParagraph« °dONLNdØ
Tª
§)< is the object class φ°dONLNdØ
§ª
¬)PcWordÍ¿°dONLNdØ
»
«). Í¿°dONLNdØ
ǻ
¯)Individual °dONLNd)ºä»õ(≈äworÄ°dONLNd,ºú»Ò)ds can be deleted fr’ °dONLNd@ºÒ»
D)Uom a paragraph. H∫°dONLNdQº
E»
e)Toweverı@°dONLNdWº
e»
j) , ı@°dONLNdYº
j»
Ω)even though a worÄ°dONLNdjº
æ»
)Td in a paragraph °dONLNd{…ä’«(“äcan be in a dif˜°dONLNdä…«’”)=ferŸÄ°dONLNdç…”’ˇ)ent font fr¨‡°dONLNdò…ˇ’
1),
om the wore@°dONLNd¢…
2’
G)3ds ar°dONLNdß…
H’
m)    ound it, Ä°dONLNd∞…
m’
˜)%a paragraph can have only one °dONLNdŒ÷ä‚®(fläpFont~ °dONLNd”÷®‚¥) pr≈@°dONLNd÷÷¥‚»)oper˘ °dONLNd⁄÷»‚–)tyƇ°dONLNd‹÷–‚Ù)    . This prÄ°dONLNdÂ÷ı‚
)%operty i{@°dONLNdÌ÷
‚
+)"s defB°dONLNdÚ÷
,‚
ë)ined as the font of the f£¿°dONLNd÷
ë‚
Ë)eirst character in the °dONLNd!„äÔ
K(Ïä+paragraph and consists of the name of a fon…‡°dONLNdL„
KÔ
û)¡t. The paragraph’s @°dONLNd_„
üÔ
Ω)TpFont`°dONLNdd„
ΩÔ
…) pr[Ä°dONLNdg„
…Ô)operty can be °dONLNduä¸ÿ(˘ächanged but not r¶‡°dONLNdÜÿ¸˛)Nemoved.°dONLNdé
ä

‰(
äRThe properties and element classes listed for each object class definition in the °dONLNd‡
ä
°*Applec°dONLNdÂ
¢
§)
 „°dONLNdÊ
§

&)Event Registry: Standard Suitesm¿°dONLNd

'

¯)É1 can be inherited from a superclass, or they can °dONLNd6
ä
(¸(
%äoriginate with a subclass. ñ‡°dONLNdQ
¸
(
-)rFigure 3-164¿°dONLNd\

.
(
)20 illustrates the object class inheritance hierarËÄ°dONLNdå


()¬chy for °dONLNdî
)ä
5Œ(
2äthe object class Ä °dONLNd•
)Œ
5¯)DcWindow}Ä°dONLNd¨
)¯
5
&)* in the CorÊ °dONLNd∑
)
&
5
≠). e suite. Boldface terms in the fi>‡°dONLNdÿ
)
Æ
5
Ω)àgurö °dONLNd€
)
Ω
5
»)e r®¿°dONLNdfi
)
»
5
÷)epr9Ä°dONLNd·
)
◊
5
)esent those °dONLNdÌ
6ä
Bì(
?äprG °dONLNdÔ
6î
B
)
operties, element classes, or º`°dONLNd
6

B
i)|Apple events that ar_@°dONLNd!
6
j
B
ˆ)Z"e not inherited. The object class °dONLNdC
Cä
O¥(
LäcWindow}`°dONLNdJ
C¥
O
)* includes all the pr.Ä°dONLNd^
C

O
?)Roperties and "Ä°dONLNdk
C
?
O
≠)9Apple events of its super0@°dONLNdÑ
C
≠
O
Δ)nclass, °dONLNdã
Pä
\‰(
YäcOpenableObjectz`°dONLNdö
P‰
\
v)Z#, which in turn includes all the prE °dONLNdΩ
P
w
\
∞)ìoperties and 9 °dONLNd 
P
∞
\)9Apple events of its °dONLNdfi
]ä
i£(
fäsuperT‡°dONLNd„
]£
iº)class, 'Ä°dONLNdÍ
]Ω
iÁ)cObject$‡°dONLNdÒ
]Á
i
2)*. The object class `°dONLNd
]
3
i
])LcWindow¿°dONLNd
]
]
i
î)* also includeöÄ°dONLNd
]
î
i
ü)7s 1 ‡°dONLNd
]
ü
i
¨)1 pM°dONLNd
]
≠
i
∞)
r°dONLNd
]
±
i
¸)operties and one °dONLNd0
jä
v
(
sä"element class that originate with N@°dONLNdR
j

v
F)ícWindowK†°dONLNdY
j
F
v
d)* and ar˝¿°dONLNd`
j
d
v
©)e not inherited. °dONLNdr
|ä
àê(
Öä
T†¿°dONLNds
|ê
àù)he ª¿°dONLNdv
|ù
à¡)pClassπÄ°dONLNd|
|¡
àÕ)$ pr†°dONLNd
|Œ
à
)operty—the pr*Ä°dONLNdå
|

à
^)Aoperty that specifiÙ °dONLNdü
|
^
à
å)Oes the fourm†°dONLNd™
|
ç
à
Á)/-character class ID—°dONLNdæ
âä
ïœ(
íäoriginates with µÄ°dONLNdŒ
âœ
ï˘)EcObject≤‡°dONLNd’
â˘
ï
')*. Because tÿ†°dONLNd‡
â
'
ï
E).he defi¿°dONLNdÁ
â
E
ï
ƒ) nitions of all object classes ar÷†°dONLNd
â
ƒ
ï
˚)e ultimately °dONLNd
ñä
¢∂(
üä
derived frd‡°dONLNd
ñ∂
¢Δ),om .`°dONLNd!
ñ«
¢Ò)cObject+¿°dONLNd(
ñÒ
¢ˆ)*, +¿°dONLNd*
ñˆ
¢
)pClass)Ä°dONLNd0
ñ

¢
œ)$, is inherited by all object classes. The defie °dONLNd]
ñ
œ
¢
˙)µnition for °dONLNdh
£ä
Ø¥(
¨äcObject}`°dONLNdo
£¥
ØÔ)* also lists ten $`°dONLNd
£Ô
Ø);<Apple events, which include common events such as Get Data, °dONLNdª
∞ä
º
)(
πä"Move, and Delete Element. Because o °dONLNd›
∞
*
º
T)†cObjectlÄ°dONLNd‰
∞
T
º)*/ is at the top of the object class inheritance °dONLNd
Ωä
…§(
Δähierarª°dONLNd
Ω§
…≥)chyp°dONLNd
Ω≥
…·), these ten ”°dONLNd(
Ω·
…
z)."Apple events can use object specifiË`°dONLNdK
Ω
z
…
â)ôer rȆ°dONLNdO
Ω
â
…
õ)ecor^°dONLNdS
Ω
ú
…
„)ds that describe Ì`°dONLNdd
Ω
„
…)GApple °dONLNdj
 ä
÷
7(
”ä*event objects of any object class as a dir≠ °dONLNdî
 
7
÷
s)≠ect parameter}°dONLNd°
 
s
÷
Ÿ)<. Like all abstract super´¿°dONLNd∫
 
Ÿ
÷
˚)f    classes, °dONLNd√
׊
„¥(
‡äcObject}`°dONLNd 
״
„)* does not corrª‡°dONLNdÿ
◊
„
))<espond to a r$ °dONLNdÂ
◊
*
„
9):eal ˜¿°dONLNdÈ
◊
8
„
∂)Apple event object, so its def∂†°dONLNd    
◊
∑
„)inition does not list °dONLNd    
‰ä

h(
Ìä4any element classes. Unlike any other object class, Ò†°dONLNd    Q
‰
h

í)ficObjectÔ°dONLNd    X
‰
í
)* is at the top of the object °dONLNd    u
Òä
˝Ô(
˙äclass inheritance hierar°dONLNd    ç
Ò
˝˙)fchL†°dONLNd    è
Ò˙
˝
)
y a[¿°dONLNd    í
Ò

˝
')nd therk@°dONLNd    ô
Ò
'
˝
8) efor√@°dONLNd    ù
Ò
8
˝
ü)e does not have a superD °dONLNd    ¥
Ò
†
˝
π)hclass. ˇaD@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-44    )B
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records4^*¿
¯

g*w
¯4g*w
¯"h*]

ˇ·ˇ‚7^
°dONLNd\lgú(dlFigure 3-16°dONLNd\Æg
ï)B<The object class inheritance hierarchy for the object class ,
Courierâ¿°dONLNdH\
ïg
∏)ÁcWindow

w*í
¯4w*í
¯4v(w)ò@@
˜@
˜w)∑ ¡¡?…ˇ˛˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚ò@@Ä
˜@Ä
˜∑)˜ ?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚ò@Ä¿
˜Ä¿
˜˜)
7 ?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚ò@¿

˜¿

˜
7)
w ?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚ò@

@
˜

@
˜
w)
∑ ?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚ò@
@
Ä
˜
@
Ä
˜
∑)
˜ ?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚ò@
Ä
¿
˜
Ä
¿
˜
˜)7 ?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚ò@
¿
Ú
˜
¿
Ú
˜7)i ?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚ò@@
˜@
˜w)∑ 
¡¡»32˚»
˚ …˚¡»
˚¡ …˚»
˚ …˚¡È¯ˇ‡Î
˚
ÈH¯à∞‰ Í@¯0Î˚È@¯0Î
˚ Íb¯"0Î˚
È@¯0‰È@¯0Î
˚
ÈH¯à∞‰ Í@¯0Î˚È@¯0Î
˚ Íb˛"
>:˝"0Î˚È
@Ã`0‰È
@~o{œ¯0Î
˚È
HààfiÌü˚Ëàà∞‰ Í
@Δmûl0Î˚È
@{flÔ80Î
˚ Íb˝":˝"0Î˚È@˝p˝0‰È@¯0Î
˚
ÈH¯à∞‰ Í@¯0Î˚È@¯0Î
˚ Íb¯"0Î˚
È@¯0‰È@¯0Î
˚
ÈH¯à∞‰ Í@¯0Î˚È@¯0Î
˚ Íb¯"0Î˚
ȯˇ‰È?¯ˇÎ
˚‰@fl Â@Ê˚
‰@Ê
˚ Â@Ê˚‰@fl
‰@Ê
˚‰@fl Â@Ê˚
‰@Ê
˚ Â@Ê˚
Û¡‡ÌÛÂ0Ù
˚
ÛÂÌ ÙÂÙ˚ÛÂÙ
˚ ÙÂÙ˚
ÛÂÌÛÂÙ
˚
ÛÂÌ ÙÂÙ˚ÛÂÙ
˚ò@@Ä
˜@Ä
˜∑)˜ 
 ÙÂÙ˚
ÛÂÌÛÂÙ
˚
ÛÂÌ ÙÂÙ˚¯?¯ˇ¯ÔˆˇÄ˙
˚ ˘ ¯Ô¢˜"¿˙˚¯ ¯ÔĘ¿Û¯ ¯ÔĘ¿˙
˚¯ ¯Ôˆà¿Û ˘ ¯ÔĘ¿˙˚¯ ¯ÔĘ¿˙
˚ ˘ ¯Ô¢˜"¿˙˚¯ ¯ÔĘ¿Û¯ ¯ÔĘ¿˙
˚¯ ¯Ôˆà¿Û ˘ ¯ÔIJ8p0¿˙˚#¯ ˛Ä˛ÔÄ<∞¿¿˙
˚% ˘ ˛˙πø˛ÔØgÁˇÁ∫˛˛˜øÚ¿˙˚¯ 
D‰˛Ôõgø˜ÊŸ¸ˆ?ˆ¿¿Û#¯
 
|§ÄÔògº7fŸåˆ<0ÿ¿˙
˚¯ ˛˜≥˛ÔèΩÔˇˇºˇ¸øfi¯¿Û ˘ ¯ÔÄ
ĸ0¿˙˚¯ ¯ÔÄ¿¸‡¿˙
˚ ˘ ¯Ô¢˜"¿˙˚¯ ¯ÔĘ¿Û¯ ¯ÔĘ¿˙
˚¯ ¯Ôˆà¿Û ˘ ¯ÔĘ¿˙˚¯ ¯ÔĘ¿˙
˚ ˘ ¯Ô¢˜"¿˙˚¯ ¯ÔĘ¿Û¯ ¯ÔĘ¿˙
˚¯?¯ˇ¸Ôˆˇ¿Û ˘¯ˇ¸Ô˜ˇ¿˙˚ÛÂÙ
˚ ÙÂÙ˚
ÛÂÌÛÂÙ
˚
ÛÂÌ ÙÂÙ˚ÛÂÙ
˚ ÙÂÙ˚
ÛÂÌÛÂÙ
˚
ÛÂÌ ¸ÚˇıÚˇ¯¸˚˚˙˙ı˙˙¸
˚  ¸˙˙ı˙˙¸˚˚0˙˙ı˙˙ı˚ ˙˙ı˙˙¸
˚˚ ˙˙ı˙˙ı  ¸ ˙˙ı˙˙¸˚˚ ˙˙ı˙˙¸
˚  ¸ ˙˙ı˙˙¸˚˚ ˙˙ı˙˙ı˚ ˙˙ı˙˙¸
˚˚ ˙˙ı˙˙ı  ¸ ˙˙ı˙˙¸˚˚ ˙˙ı˙˙¸
˚  ¸ ˙˙ı˙˙¸˚˚ ˙˙ı˙˙ı&?˚ˇ
˙ˇ
¿˙ˇ˝˚ˇ¯˚ˇ
‡˙ˇ
Ä
˚) ˚Ä˚
`˚

IJ˚àå@˚
0˙¿˙ò@Ä¿
˜Ä¿
˜˜)
7 
*  ˚Ä˚
`˚

IJ˚@˚
0˙
¿˚* ˚Ä˚
`˚

IJ˚@˚
0˙
¿
˚*  ˚Ä˚
`˚

IJ˚",@˚
0˙
¿˚) ˚Ä˚
`˚

IJ˚@˚
0˙¿˙* ˚Ä˚
`˚

IJ˚@˚
0˙
¿
˚) ˚Ä˚
`˚

IJ˚àå@˚
0˙¿˙*  ˚Ä˚
`˚

IJ˚@˚
0˙
¿˚* ˚Ä˚
`˚

IJ˚@˚
0˙
¿
˚*  ˚Ä˚
`˚

IJ˚",@˚
0˙
¿˚5 ˝0Ä˚
`˛¿
IJ    `@˚
0˛#˛¿˙< 
òÄê˛    `@
IJ
?@<˝@0?
˛
¿
˚< =6ÄÚ<ÓÄ`‚q6
IJèûÔflˇ¯åC“„˜”º0—a¿˙=  D®ôÄ
@``Kò
IJûcsõ‡DSR¨R@0\!¿˚= @¯ë0Ä
ı@`"Lê
IJcsõ‡DØ“H0!¿
˚=  <ó<ÿġåm@`‹Ô¸
IJ'æ˜ˇÛb,C¸„œ©ª00¯ˇΔ¿˚) ˚Ä˚
`˚

IJ˚@˚
0˙¿˙* ˚Ä˚
`˚

IJ˚@˚
0˙
¿
˚) ˚Ä˚
`˚

IJ˚àå@˚
0˙¿˙*  ˚Ä˚
`˚

IJ˚@˚
0˙
¿˚* ˚Ä˚
`˚

IJ˚@˚
0˙
¿
˚*  ˚Ä˚
`˚

IJ˚",@˚
0˙
¿˚) ˚Ä˚
`˚

IJ˚@˚
0˙¿˙* ˚Ä˚
`˚

IJ˚@˚
0˙
¿
˚) ˚Ä˚
`˚

IJ˚àå@˚
0˙¿˙*  ˚Ä˚
`˚

IJ˚@˚
0˙
¿˚* ˚Ä˚
`˚

IJ˚@˚
0˙
¿
˚( ?˚ˇ
¯˙ˇ
‡˙ˇÄ˛˚ˇ¸˚ˇ
˙ˇ
¿˚(˚ˇ¯˚ˇ
‡
˙ˇÄ˛˚ˇ¸?˚ˇ

˙ˇ¿˙»
˚¡ …˚»
˚ …˚¡»
˚¡ …˚»
˚ …˚¡»
˚¡ …˚»
˚ …˚¡»
˚¡ …˚»
˚ …˚¡»
˚¡ …˚»
˚ …˚¡»
˚¡ …˚»
˚ …˚¡ò@¿

˜¿

˜
7)
w 
»
˚¡ …˚»
˚ …˚¡»
˚ŸÒˇ‡˙ ⁄ÄÚ
 ˚ŸÄÚ
 
˚ ⁄¢Ú"
 ˚
ŸÄÚ ˙ŸÄ˚¿˚
 
˚Ÿ˚àè»à»˚à†˙ ⁄Ä˝
ÁªÁˇ∏¸
 ˚ŸÄ˝gôºÁ¸
 
˚ ⁄¢˝"#'ªæÁÚ¸"
 ˚ŸÄ˝
Áøˇ˝∞¸ ˙ŸÄÚ
 
˚ŸÒà†˙ ⁄ÄÚ
 ˚ŸÄÚ
 
˚ ⁄¢Ú"
 ˚
ŸÄÚ ˙ŸÄÚ
 
˚ŸÒˇ‡˙ ⁄ÄÚ
 ˚ŸÄÚ
 
˚ ⁄ÄÚ
 ˚
ŸÄÚ ˙ŸÄÚ
 
˚
ŸÄÚ ˙ ⁄ÄÚ
 ˚ŸÄÚ
 
˚ ⁄ÄÚ
 ˚
ŸÄÚ ˙ŸÄÚ
 
˚
ŸÄÚ ˙ ⁄ÄÚ
 ˚ŸÄÚ
 
˚ ⁄ÄÚ
 ˚
ŸÄÚ ˙ŸÄˆ
 
˚Ÿ
Ä#‡¸ ˙ ⁄ÄõçπùI«zªy¿˛
 ˚ŸÄ&_    r, ä& ˛
 
˚ ⁄Ä&Q    K„$ä'‡˛
 ˚ŸÄè    ˘fiƒ8¿˛ ˙ŸÄ˛˛
 ˝
 
˚ŸÄ˛˛
p˝ ˙ ⁄ÄÚ
 ˚ŸÄ˚

Ä˙
 
˚ ⁄Ä˚
xÄ˙
 ˚ŸÄ¸àч¸ ˙ŸÄ¸    Äé1ĸ
 
˚ŸÄ¸    àí`¸ ˙ ⁄ĸsÔ{¿¸
 ˚ŸÄ¸¯
 
˚ ⁄ĸ¯
 ˚
ŸÄÚ ˙ŸÄ˙¸
 
˚ŸÄ˚#‡˛ ˙ ⁄ĸIœdz≠˘¿ ˚ŸÄ¸    J$9$ Ö&  
˚ò@

@
˜

@
˜
w)
∑ 
 ⁄ĸ    K‰I$$Ö'‡ ˚ŸÄ¸
œ<ˇ¬8¿ ˙ŸÄ¸¸  
˚ŸÄ¸¸p ˙ ⁄ÄÚ
 ˚ŸÄÚ
 
˚ ⁄Ä˚Ã˘
 ˚ŸÄ¸h∫8˚ ˙ŸÄ¸    Y’D˚
 
˚ŸÄ¸    JU|˚ ˙ ⁄ĸÈı˚
 ˚ŸÄ¸¯
 
˚ ⁄ĸ¯
 ˚
ŸÄÚ ˙ŸÄ¯¸
 
˚ŸÄ˚¯0¸ ˙ ⁄ĸmˇ}˜Ä˝
 ˚ŸÄ¸˚?7?Ä˝
 
˚ ⁄ĸÔ?73¸
 ˚ŸÄ¸˘Áˇˇ¸ ˙ŸÄ¸¯
 
˚ŸÄ¸¯ ˙ ⁄ÄÚ
 ˚ŸÄ˘

¿¸
 
˚ ⁄Ä˚
˛<¿Ä ˚ŸÄ¸
o«ÊœÊˇ ˙ŸÄ¸˝Ô‡Ÿø˜Á‡ 
˚ŸÄ¸
ÔcfŸèÁ‡ ˙ ⁄ĸˇˇ=Ô=ˇø ˚ŸÄ¸¯
 
˚ ⁄ĸ¯
 ˚
ŸÄÚ ˙ŸÄ¯
¿8˝
 
˚ŸÄ˚    ˛~Ä ˙ ⁄ĸo«ˇflÊ˚ ˚ŸÄ¸˝ÔòØΩÄ 
˚ ⁄ĸÔcÕõÌÄ ˚ŸÄ¸
ˇˇ=Á=ˇø‡ ˙ŸÄ¸¯
 
˚ŸÄ¸¯ ˙ ⁄ÄÚ
 ˚Ì
Òˇ˛Ä˙
Ä˚
 
˚ Ó
Ú"#˛Ä˚x
Ä˚
 ˚Ì
Ú
˛Ä¸3Ôø¸ ˙Ì
Ú
˛Ä¸±πˇ‡¸
 
˚Ì
Úàâ˛Ä¸±π·‡¸ ˙ Ó
Ú
˛Ä¸{ˇˇ¸
 ˚Ì
˙q¿ÅIJ
˛Ä¸¯
 
˚% Ó
˛"#‚""2‚?¢"&""#˛Ä¸¯
 ˚Ì
˛˛?    Ô<«ÁÁºˇÄ
˛ÄÚ ˙&Ì
˛o=ˇ∑∂œÁ±ˇ∂
˛Ä˘8¿˛
 
˚&Ì
˛àÎΩÈΩæÃÔπÈé»àâ˛Ä˚xò0˝ ˙+ Ó
˛=Ô?ˇ˝Áˇ·æÛÄ
˛Ä¸0¸˛}œø ˚&Ì
˝¸

IJ
˛Ä¸±ˇ?0ΔÊ 
˚' Ó
˝">¸"'˝"#˛Ä¸∞lΔÊ ˚Ì
Ú
˛Ä¸
y˛=ÔùÔ˛ ˙Ì
Ú
˛Ä¸˚ 
˚Ì
Úàâ˛Ä¸˚| ˙ Ó
Ú
˛ÄÚ
 ˚Ì
Òˇ˛Ä¯
8˝
 
˚ Ó
Ú
˛Ä˚xÄ0˝
 ˚Ì
Ú
˛Ä¸0ˇΩ˛˝ ˙Ì
Ú
˛Ä¸±ˇÁ?˝
 
˚Ì
Ú
˛Ä¸∞yÁ;˝ ˙ò@
@
Ä
˜
@
Ä
˜
∑)
˜ 
 Ó
Ú
˛Ä¸yˇΩˇº˝
 ˚Ì
Ú
˛Ä¸¯
 
˚ Ó
Ú
˛Ä¸¯
 ˚Ì
Ú
˛ÄÚ ˙Ì
Ú
˛Ä¯8 
˚Ì
Ú
˛Ä˚
x˛ ˙#
 Úˇ¯
Ú
˛Ä¸0˝º˛?«ô‡ ˚#
Ú
Ú
˛Ä¸±ˇˆÊ€ 
˚#

Ú"(
Ú
˛Ä¸∞o`ff€ ˚"
Ú
Ú
˛Ä¸
y˝ˇÔ?ˇΩ ˙
Ú
Ú
˛Ä¸¯
 
˚
Òà
Ú
˛Ä¸¯ ˙#
 ˚
˙
p ˜
˛ÄÚ
 ˚0
˚ˆ0¸
H@¿èÄ˝
˛Ä˜
á˛
 
˚6

¸"?øæ˜˛¸"(
Nn6Êty'ÍÌÁ˛
˛Ä˚xÄ
ɲ
 ˚6
¸mûÕ˝∞¸
tô|o¿%»∞Ç(òÄ
˛Ä¸
0Û=ˇy„< ˙7
¸aûÕå6¸
DôDh0%/åí(üÄ
˛Ä¸±ˆg?Ω≥~ 
˚5
¸àºˇåˇú˚à
Dn<'‰;√xg„˛
˛Ä¸
∞gÁ?Ì≥` ˙3
 ˙˙
˛ ˛
IJ
˛Ä¸yÔΩˇøÁæ ˚-
˙8˙
˛p˛
q¿˛
˛Ä¸¯
 
˚

Ú"(
Ú
˛Ä¸¯
 ˚
Ú
˙˙
˛ÄÚ ˙"
Ú
˚

‚˙
˛Äˆ˛
 
˚(
Òà
˚z"sÄ˝
˛Ä˚xÄ0˛ ˙*
 Úˇ¯
˚&8Δ¸
˛Ä¸0Û=ˇ=˛
 ˚+
Ú
˚&"H1Ä˝
˛Ä¸±ˆg?ˇ0˛
 
˚*
 Ú
˚9œΩÔ¸
˛Ä¸∞gÁ?„0˛
 ˚&
Ú
˚ ˘
˛Ä¸yÔΩˇø¯˛ ˙!
Ú
˚p˘
˛Ä¸¯
 
˚
Ú
Ú
˛Ä¸¯ ˙
 Ú
˘0˝
˛ÄÚ
 ˚)
Ú
˚    ¿èÄ
˛Ä˙˝
 
˚)
 Ú
˚    y'<MëÍ∑Á
˛Ä˚<¸
 ˚+
Ú
˚    %(ê‰êÇòÄ
˛Ä¸
aÊ=ˇ9ÔÄ ˙,
Ú
˚    %/ë$êíüÄ
˛Ä¸ªˆl¿ 
˚+
Ú
˚    ;√<Û¸g„
˛Ä¸
ècõ6¿ ˙*
 Ú
˚ ¸Ä
˛Ä¸yˇ?Á=Ô‡ ˚$
Ú
˚p¸9¿
˛Ä¸¯
 
˚
 Ú
Ú
˛Ä¸¯
 ˚
Ú
Ú
˛ÄÚ ˙$
Ú
˚

∞˙
˛Ä˙¿é¸
 
˚*ˆ
˚}ˇ¸¸
˛Ä˚¸
ܸ ˙3     |3¸
˚7˜ˇ¯¸
˛Ä¸y«πÊ<˝
 ˚5    ŸÃ›éè∑„ˇˇ¸˛
˚7˝ˇÄ¸
˛Ä¸¯œô∂~˝
 
˚5 •>èÿˇ˜«∑¯˛
˚=∑˛¯¸
˛Ä¸∞√∂`˝
 ˚1•0é˜
∂«∑IJ
˚0˘
˛Ä¸1Ô?Ô>˝ ˙-ôŒÖ‹á˝˜ù„<¯˛
˚x˘
˛Ä¸¯
 
˚'
˛˛
0˝
Ú
˛Ä¸¯ ˙$ 
˛˛
x˝
Ú
˛ÄÚ
 ˚
Ú
Ú
˛ÄÚ
 
˚
 ˚

¿˙
Ú
˛ÄÚ
 ˚
˚
<¿˙
Ú
˛ÄÚ ˙!
¸Êœ¸
Ú
˛ÄÚ
 
˚ 
¸‡«ø¸
Ú
˛ÄÚ ˙!
 ¸ÊÕå`¸
Ú
˛ÄÚ
 ˚!
¸ΩÁ˝‡¸
Ú
˛ÄÚ
 
˚
 ¸¯
Ú
˛ÄÚ
 ˚"
¸¯
|˝D˘
˛ÄÚ ˙!
Ú

Dd˘
˛
ÄÛ
 
˚3
˙
¿¸
DÕ‹T‹`˚
˛Ä¯˛

IJ ˙7
 ˚|1¯˛
}ÍΩ(U2˚
˛Ä3FwmÔÔ‡˛
 ˚8
¸∑Á˚„}ˇ¸
E
°(M2Ä˚
˛ÄzØJo;?ˇ∑IJ
 
˚8
 ¸˜Û=„0g∑¯
|Íù$D“p˚
˛ÄB®Jo8?¯7∞˛
 ˚.
¸˜m„6g∑Ä
Ú
˛Ä:ßI˘Ôˇˇ‡˛ ˙ò@
Ä
¿
˜
Ä
¿
˜
˜)7 
#
¸˝˜˛˜úÛ<¯
Ú
˛ÄÚ
 
˚ 
¸¸0
Ú
˛ÄÚ ˙#
 ¸¸    x
Ù
˛ÄÚ
 ˚
Ú
Ù
˛
ÄÛ
 
˚
 Ú
iùÿ˘
˛
ÄÛ
 ˚!
Ú
õÛ=Ę
˛Ägv:ˆ ˙"
Ú
äL‡`˜
˛Ä&¸œ`ˆ
 
˚!
Ú
y˚ù»˜
˛Ä"ì8ˆ ˙
 Ú
Ú
˛Ä~Árˆ
 ˚
Ú
Ú
˛ÄÚ
 
˚
 Ú
Ú
˛ÄÚ
 ˚
Ú
Ú
˛ÄÚ ˙
Ú
Ú
˛ÄÚ
 
˚IJ
Ģ
Ú
ÄÚ ˙  Ä
Ģ
Ú
ÄÄÚ
 ˚!    õCsÄ
≥ò˙
Ú
¿ÄÚ
 
˚!     æß…
 |˙˘ÅÚ
˛`ÄÚ
 ˚     ¢§I     `˙@¡Ú
0ÄÚ ˙!    û£»Ä≤\˙@aÚ
ÄÚ
 
˚
Ú@1Ú
ÄÚ ˙ 
 Ú@a ˛˘
ÄÚ
 ˚'
Ú@¡P˛e˘
0ÄÄ@˘
 
˚* Û˘ÅW:`A70˚
˛`ÄÄ@˘
 ˚*Û
t¶AL¯˚
¿ÄŒòMÃ˙ ˙.cª:ˆ
å¶ÄEL¿˚
ÄÄ)ºS>˙
 
˚-ˆg‡ˆ
è:p94∏˚
Ä#)†S0˙ ˙( ëúˆ
 ı
˛Ä#ŒúM.˙
 ˚"wsÚˆ
 ı
˛Ä
Ù
 
˚
 Ú
Ú
˛Ä
Ù
 ˚
Ú
˚>¸
˛ÄÚ ˙-
Ú
˛ d"
˛Ä¸ĸ
 
˚0
Ú
igw@@“Ó"mœ¿
˛Ä
Ä
˛ ˙1
 Ú
ıÙ¨A2î>˙ü'
˛ÄY›–4ªàõCs ˚1
Ú
ÜÑ£E2î"äë$¿
˛Ä=}+L•æß…¿ 
˚1
 Ú
ttû@8Œí>zè#Ä
˛Ä!°(¿L•¢§I0 ˚$
Ú
Ú
˛Ä'ê3§èû£»‡ ˙
Ú
Ú
˛ÄÚ
 
˚
Ú
Ú
˛ÄÚ ˙!
 Ú
˚@˝
˛ÄÚ
 ˚*
Ú
˚    d@

˛Ä¸–¸
 
˚3 @∞˘
˚    A±ªY£;Ä
˛Ä¸@ ˚2
@˘
˚    A{◊è}W•
˛Ä¸
ln¬hŒ‡ ˙5

ÓL?sÄ˚
˚    EBTaT%
˛Ä¸^ı„flUÈ@ 
˚4
ô^9ˇ¿˚
˚    99Àè]S§Ä
˛Ä¸
PïU    @ ˙+     ôP˘˛˙
Ú
˛Ä¸Nr„◊TÈ  ˚"
ÓN?{¿˚
Ú
˛ÄÚ
 
˚ àÙ
Ú
˛ÄÚ
 ˚àÙ
˚
8˙
˛ÄÚ ˙$
Ú
˚$ ˚
˛Ä¸
˘
 
˚,
¸Ä¯¸
˚$”v˚
˛Ä¸    ˙ ˙2 ¿c0
˚%˜Ø˚
˛Ä¸    4›Ä˚
 ˚2-œ–=ÓÛˇ>wÄ
˚%(˚
˛Ä¸    }ο˚
 
˚1 ø'gÔcøˇø
˚8Ûó˚
˛Ä¸    E
˙
 ˚+—$¿ÁÔc?«±Ä
Ú
˛Ä¸<¿˚ ˙%è#ê<Ôsˇøø
Ú
˛ÄÚ
 
˚
Ú
Ú
˛ÄÚ ˙"
 Ú
˚    8»Ä
˛ÄÚ
 ˚,
Ú
˚    $(
˛Ä¸Ú ¬˛
 
˚4
 ¸IJ¸
˚    $ƒ.ôªàô¯
˛Ä¸    

 ˚5
¸¿Δ
˚    %$)æVk
˛Ä¸
    1¶n‚&~ ˙6
¸?ˇœùfi
˚    %$)¢àh–
˛Ä¸    I
oïÉ⁄ƒ 
˚5
¸?ø¯«ÔˇÏ
˚    8√Œùœõà
˛Ä¸
    I
hÑb4 ˙1
 ¸¸o¿«ÒÏ
¯Ä¸
˛Ä¸0Ûßs√Ê‚ ˚+
¸7ø¯ˇÔflÓ
˘
˚
˛Ä˘ ˚
 
˚ò@
¿
Ú
˜
¿
Ú
˜7)i 

 Ú
Ú
˛Ä˘@˚
 ˚!
Ú
˚2

˛
˛ÄÚ ˙,
Ú
˚" 
˛
˛Ä¸Ä@@˛
 
˚1
¸ÅÄ˙
˚    @ŒÇgqw¿
˛Ä¸Å2Ä@IJ ˙2
 ¸¡Ü˙
˚    O‰Ç¸¡K 
˛Ä¸3†ô‹]˛
 ˚3
¸˘ˇ‡˚
˚    cäì1K 
˛Ä¸˘ ø0R»˛
 
˚3
 ¸˝ˇ˚
˚    ‚r~·J¿
˛Ä¸¡"§ÃR»˛
 ˚)
¸·«Ä˚
Ú
˛Ä¸∏úü∏R∞˛ ˙ 
¸Ωˇ˚
Ú
˛ÄÚ
 
˚
Ú
Ú
˛ÄÚ ˙
 Ú
˚p˚
˛ÄÚ
 ˚&
Ú
˚"H¸
˛Ä¸˙
 
˚1
 ¸Ä|Ã|
˚@ŒIª¸
˛Ä¸Å˚
 ˚2
¸¿Δ¿¿``
˚O‰K◊Ä˝
˛Ä¸3ín¿¸ ˙3
¸¸Δ˝›¸fl
˚cJTÄ˝
˛Ä¸˘ı‡¸
 
˚2
¸ÊΔflˆ¯cü`
˚‚qÀÄ˝
˛Ä¸¡ï ¸ ˙+
 ¸ÊΔfl0Ãcô‡
Ú
˛Ä¸∏úr‡¸
 ˚#
¸º|˝˛¯~flp
Ú
˛ÄÚ
 
˚
 ˘˚
Ú
˛ÄÚ
 ˚%
˘˚
˚p@˛
˛ÄÚ ˙*
Ú
˚"H˝
˛Ä¸ê˝
 
˚4
¸¿0˛
˚    @ŒIª}Ä
˛Ä¸Å@˝ ˙6
 ¸aô∞˛
˚    O‰K◊ÉK¿
˛Ä¸3ín√`˛
 ˚6
¸ÿ>˜èøÄ
˚cJTëR˛
˛Ä¸˘ı‡“˛
 
˚6
 ¸ˇò?Ô‹¿
˚    ‚qÀé}¿
˛Ä¸¡ï$TIJ
 ˚,
¸qõª1è‹¿
Ú
˛Ä¸∏úr„üp˛ ˙#
¸ˇŒ?ÔflÄ
Ú
˛ÄÚ
 
˚
Ú
Ú
˛ÄÚ ˙
 Ú
˚B˘
˛ÄÚ
 ˚"
Ú
˚f˘
˛Ä¸
Ģ
 
˚*
 ¸¿˙
˚fi`˚
˛Ä¸
Ģ
 ˚+
¸açÉ˚
˚Zï˚
˛Ä¸öX˙ ˙-
¸Õˇ¸
˚ZñÄ˚
˛Ä¸•|˙
 
˚,
¸ˇçøx¸
˚Rdp˚
˛Ä¸•†˙ ˙'
 ¸qçÔÿ¸
Ú
˛Ä¸ô˙
 ˚!
¸ˇœ?¯¸
Ú
˛ÄÚ
 
˚
 Ú
Ú
˛ÄÚ
 ˚
Ú
˚8‡˚
˛ÄÚ ˙&
Ú
˚Dê ¸
˛Ä¸8˙
 
˚/
¸¿ˆ˝
˚1úìv¸
˛Ä¸$˚ ˙1
 ¸açÉ
ò˝
˚»óظ
˛Ä¸g$›Ä¸
 ˚2
¸ÕˇÁ¸˛
˚F
˛Ä¸Ú%ο¸
 
˚2
 ¸ˇçøx6˛˛
˚9ƒ„ó¸
˛Ä¸Ç%*@¸
 ˚*
¸qçÔŸü∞˛
Ú
˛Ä¸q8¿¸ ˙#
¸ˇœ?¯˜˛˛
Ú
˛ÄÚ
 
˚
Ú
Ú
˛ÄÚ ˙
 Ú
˚
<¿˙
˛ÄÚ
 ˚#
Ú
˚
f¿˙
˛Ä¸
@˘
 
˚)
 ¸
`˘
˚`˝¸˚
˛Ä¸
@˘
 ˚)
¸
‡˘
˚`Á˛˚
˛Ä¸LÏ˙ ˙ò@@
˜@
˜i)© ?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚?»ˇ˚»ˇ˚¡¡¡¡¡¡¡¡¡¡
p    Ä»
ê :@»
0Ä @»
0‡ Ä»    IG«    âD«

ü‡¯;¿»¡¡¡¡¡+'˙Ü–A $ 0
 A 8d‡È+'H    à    P@ @
 @ D@È-)BÙlÅê
AQi]≈≤ÕÆ]ô¢µ5§‰≥¨ÅQp—]√L≠é]@Î-)c,ëG
$¢Î*†™¢”V$¶™Ü•JV‰JA5BÎ-!R¢R¶î•@Î-)Ö%ìÄÒ:ƒ…tAù»ízI$«ŒRÑ®RB'Ñ…xB$ù»SD•*@Î-)
«"Å"RE·ÑM2‰mÈ‹Ëûµ∏îÉ.RKb˜ÑKai≠JÄÎ,(
Ö≈°«ú$‚b:@ï;â$úII#âGîI(àÇI¬b<A%;ÑAI6çÍò@@Ä
˜@Ä
˜©)È  ˙Û
IJ· ˙Û
RIJ·
¿˙Ûa˝·¡¡(«`8 $
¿˛ @`@@¿ Ê'"X†   ˝ @@ Ê($bT¿ÒYiItMà    ≠≠£/E∞fi»ËüDÿ‰)HÇ:[wÊ($Rï@&¢¢˜©*§¶à‘◊&•RJ–IY*JhJw©Cä≠(Ê($åñ@$«$•2D…$à$îïd»îíêQ&KDíHí    %3Ñ…GÊ($Ö$@I‰G [_ÌIÑi!!…Έ’0$⁄*Œ^‘ò‘JZUaÊ($
≈¥‰iC≈1í%Hâë))iD§â"4ík$àêà3±ëœàÚNÊ˝˛Bı¯B·˝˛Bı¯B·
˘BÎB·¡¡ˇ @å @#Ï0
ÄÿR ˝
@@

HÄÿRGıóDÿyƒÉ  Óu' —¬äπ√ë(ŸíÃ"*JhäJI]P*Pp.èR*ÙŸ§[¬LíHpú˜Èé)R‡@!äa…w$Ÿ
6p‰~‘òDí¬*vÄbQî∞KDHŸ
§_DTàêÛŒá9Ãú4[q±éc#çª∞Ÿı˚˛@Ÿı˚˛@Ÿı˚˛@Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡‡˛ćÕ@1˛Ä@Õ1JD@-e# ¿v0Œ3ΩJ@VƉïöPŒI)ú@î§≠9íÄŒäR–#©    9¢
&∞Œ
ùåéIF-§DŒ˛ Ã˛ Ã˛…¡¡ƒ;Ä8‡@÷HHÄ
@@÷IxàûMùlDÑÍ'Xê
QeÂn◊Rê±d¶©4§Öe©PrÑäJê◊ц¢e$ %%‰")+†ñxííé◊á∞íôI€MI<":B0&‹’◊
≈!…8ânHãÈËw*Q‚4ñÈâ◊¸D˛˛—¸D˛˛P—
¸8˙`œ¡ò@Ä¿
˜Ä¿
˜È)) ¡ˇ  R      RGıó%Ç íÃ"*R §[¬Lí
 
6p‰~§ 
§_DTDL ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜))i ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜i)© ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜©)È ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜È)) ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜))[ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
˜@
˜i)© 
+
¸ˇæ˙
˚nÊp˚
˛Ä¸Sû˙
 
˚*
¸Ûˇ˙
˚8ˇfi˚
˛Ä¸Rp˙ ˙%
 ¸Û¯˙
Ú
˛Ä¸MŒ˙
 ˚
¸˛œ˙
Ú
˛ÄÚ
 
˚
 Ú
Ú
˛ÄÚ
 ˚
Ú
˚>˘
˛ÄÚ ˙!
Ú
˚c˘
˛Ä¸¯
 
˚)
¸Ä˙
˚c˜8˚
˛Ä¸
Ģ ˙,
 ¸√˚
˚cflº˚
˛Ä¸Ò∏˙
 ˚-
¸?õˇ‡¸
˚c‹<˚
˛Ä¸À‰˙
 
˚-
 ¸
ˇ~¸
˚>˜º˚
˛Ä¸ $˙
 ˚*
¸„fl∞¸
˙¿˙
˛Ä¸q‰˙ ˙)
¸øû¸
˙¿˙
˛Ä˚@˘
 
˚
Ú
Ú
˛Ä˚@˘ ˙
 Ú
Ú
˛ÄÚ
 ˚
Ú
Ú
˛ÄÚ
 
˚
 Ú
Ú
˛ÄÚ
 ˚
Ú
Ú
˛ÄÚ ˙
Ú
Ú
˛ÄÚ
 
˚
Ú
Ú
˛ÄÚ ˙
 Úˇ¯
Òˇ˛Òˇ
‡˚»
˚ …˚¡»
˚¡ …˚»
˚ …˚¡»
˚¡ …˚»U˚»3˚¡¡¡¡¡¡¡¡¡¡
p    Ä»
ê :@»
0Ä @»
0‡ Ä»    IG«    âD«

ü‡¯;¿»¡¡¡¡¡+'˙Ü–A $ 0
 A 8d‡È+'H    à    P@ @
 @ D@È-)BÙlÅê
AQi]≈≤ÕÆ]ô¢µ5§‰≥¨ÅQp—]√L≠é]@Î-)c,ëG
$¢Î*†™¢”V$¶™Ü•JV‰JA5BÎ-!R¢R¶î•@Î-)Ö%ìÄÒ:ƒ…tAù»ízI$«ŒRÑ®RB'Ñ…xB$ù»SD•*@Î-)
«"Å"RE·ÑM2‰mÈ‹Ëûµ∏îÉ.RKb˜ÑKai≠JÄÎ,(
Ö≈°«ú$‚b:@ï;â$úII#âGîI(àÇI¬b<A%;ÑAI6çÍò@@Ä
˜@Ä
˜©)È 
 ˙Û
IJ· ˙Û
RIJ·
¿˙Ûa˝·¡¡(«`8 $
¿˛ @`@@¿ Ê'"X†   ˝ @@ Ê($bT¿ÒYiItMà    ≠≠£/E∞fi»ËüDÿ‰)HÇ:[wÊ($Rï@&¢¢˜©*§¶à‘◊&•RJ–IY*JhJw©Cä≠(Ê($åñ@$«$•2D…$à$îïd»îíêQ&KDíHí    %3Ñ…GÊ($Ö$@I‰G [_ÌIÑi!!…Έ’0$⁄*Œ^‘ò‘JZUaÊ($
≈¥‰iC≈1í%Hâë))iD§â"4ík$àêà3±ëœàÚNÊ˝˛Bı¯B·˝˛Bı¯B·
˘BÎB·¡¡ˇ @å @#Ï0
ÄÿR ˝
@@

HÄÿRGıóDÿyƒÉ  Óu' —¬äπ√ë(ŸíÃ"*JhäJI]P*Pp.èR*ÙŸ§[¬LíHpú˜Èé)R‡@!äa…w$Ÿ
6p‰~‘òDí¬*vÄbQî∞KDHŸ
§_DTàêÛŒá9Ãú4[q±éc#çª∞Ÿı˚˛@Ÿı˚˛@Ÿı˚˛@Ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡‡˛ćÕ@1˛Ä@Õ1JD@-e# ¿v0Œ3ΩJ@VƉïöPŒI)ú@î§≠9íÄŒäR–#©    9¢
&∞Œ
ùåéIF-§DŒ˛ Ã˛ Ã˛…¡¡ƒ;Ä8‡@÷HHÄ
@@÷IxàûMùlDÑÍ'Xê
QeÂn◊Rê±d¶©4§Öe©PrÑäJê◊ц¢e$ %%‰")+†ñxííé◊á∞íôI€MI<":B0&‹’◊
≈!…8ânHãÈËw*Q‚4ñÈâ◊¸D˛˛—¸D˛˛P—
¸8˙`œ¡ò@Ä¿
˜Ä¿
˜È)) 
¡ˇ  R      RGıó%Ç íÃ"*R §[¬Lí
 
6p‰~§ 
§_DTDL ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

˜¿

˜))i 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
˜

@
˜i)© 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
˜
@
Ä
˜©)È 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
˜
Ä
¿
˜È)) 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
˜
¿
Ú
˜))[ 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ;F@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡ä
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records

, (‡3-45
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh
®(eäAThe chain of containers that determine the location of one or mor, °dONLNdA\
©h
∞(e
©e `°dONLNdC\
∞h)Apple event objects is °dONLNdZiäu∑(räcalled the 
É¿°dONLNdei∑u
)-container hierarchy-°dONLNdxi
u
)X
.≠°dONLNdyi
u
m) The container hierarì@°dONLNdéi
mu
|)\chyH@°dONLNdëi
|u
ª), which specifià¿°dONLNd†i
ªu)?es the location of °dONLNd≥väÇç(ä
rE°dONLNd¥véÇù)eal †°dONLNd∏vùÇ
)Apple event objects, is dif¿@°dONLNd”v
Ç
)qfer¢¿°dONLNd÷v
Ç
1)ent fr°dONLNd‹v
2Ç
S)om the ?‡°dONLNd„v
SÇ
‰)!"object class inheritance hierarchy˝†°dONLNd
v
„Ç)ê, which is °dONLNd
Éäè
P(åä,an abstract concept that determines which pr °dONLNd
<É
Qè
’)«operties, element classes, and `°dONLNd
[É
’è)ÑApple events °dONLNd
hêäúˆ(ôäan object class inherits frº °dONLNd
Éêˆú
,)lom its superB@°dONLNd
èê
-ú
Ÿ)7(class. For example, the container hieraré`°dONLNd
∑ê
Ÿú)¨chy for an °dONLNd
¬ùä©

(¶äApple event object of class ,
Courier6‡°dONLNd
fiù
©
 )xcWord5°dONLNd
„ù
 ©
R) can vary fr7Ä°dONLNd
Ôù
R©
á)2
om one wor#°dONLNd
˘ù
á©
º)5d to anotherP °dONLNdù
º©
)5, because various °dONLNd™ä∂Ì(≥äcombinations of other Z@°dONLNd-™Ì∂)cBApple event objects, such as a document, a paragraph, a delimited °dONLNdo∑ä√Í(¿ästring, or another worK`°dONLNdÖ∑Î√
D)ad, can contain a wormÄ°dONLNdô∑
D√
O)Yd. °dONLNdù…ä’˛(“äApplications that support •¿°dONLNd∑…˛’
€)t3Apple event objects must be able to identify the or_†°dONLNdÍ…
‹’
¯)fider of °dONLNdÒ÷ä‚
>(flä*several elements of the same class that ar*†°dONLNd÷
?‚
∏)µe contained within another R@°dONLNd6÷
∏‚)yApple event object. °dONLNdJ„äÔÓ(ÏäFor example, each woré`°dONLNd_„ÓÔ
†)d'd in a paragraph should have an identifi¶@°dONLNdá„
†Ô
æ)≤able orö`°dONLNdé„
æÔ
Ã)derµ°dONLNdë„
ÃÔ
¸), such as thãÄ°dONLNdù„
˝Ô)1e °dONLNdüä¸ö(˘ä5th ¿°dONLNd£õ¸£)
wj¿°dONLNd§£¸¨)or•@°dONLNd¶¨¸…)    d or th<‡°dONLNd≠ ¸Ô)e 12th wq@°dONLNdµÔ¸¯)%or´¿°dONLNd∑¯¸
∫)    .d. This allows other applications to identify ˘°dONLNdÂ
∫¸)¬Apple event objects °dONLNd˘˝ä
    
~(
ä8by describing their absolute position within a containerÄ°dONLNd1˝
~
    
É)Ù. °dONLNd4
ä
¢(
äFigurR¿°dONLNd9
¢
ª)e 3-17@°dONLNd?
ª
È)
 shows an ˚ °dONLNdI
È

}).#Apple event object of object class  °dONLNdl

~

ú)ïcWord@°dONLNdq

ú

»)—the worÔ °dONLNdy

«

˘)+
d “Sales”—°dONLNdÉ
ä
(Á(
%äcontained in another 
‡°dONLNdò
Ë
(
|)^#Apple event object of object class ‡°dONLNdª

|
(
∏)î
cParagraph °dONLNd≈

∏
()<. (Both these object °dONLNd⁄
)ä
5≥(
2ä
classes arû@°dONLNd‰
)≥
5À))e defi⁄°dONLNdÍ
)À
5ˇ)ned in the T›†°dONLNdˆ
)ˇ
5
E)4ext suite.) The fig °dONLNd
)
F
5
U)Ggur¬`°dONLNd
)
U
5)(e shows only a portion of the container °dONLNd3
6ä
B§(
?ähierarª°dONLNd9
6§
BÁ)chy for the wor6†°dONLNdH
6Ë
B
†)D*d, since a complete description of the worÄ°dONLNdr
6
†
B)∏d would also include the °dONLNdã
Cä
O
r(
Lä6containers that specify the location of the paragraph.‘‡°dONLNd¡
C
r
O
t)Ë
 °dONLNd√
Uä
aê(
^ä
Y@Ä°dONLNdƒ
Uê
a
U),our application must take account of the defiÊ°dONLNdÒ
U
U
a
ë)≈nitions in the eÄ°dONLNd
U
í
a
Ó)=Apple Event Registry: °dONLNd
bä
nØ(
käStandard∂@°dONLNd
bØ
n±)%
 6@°dONLNd
b≤
nÀ)Suites6‡°dONLNd%
bÀ
n
È)A for any object classes you want to support. For example, the defi_ °dONLNdg
b
È
n(
k
Ènition for °dONLNdr
oä
{Œ(
xäthe object class Ä °dONLNdÉ
oŒ
{Ï)DcText~@°dONLNdà
oÏ
{
e) lists paragraphs, lines, worÆ°dONLNd•
o
e
{
¬)yds, and characters as Q@°dONLNdª
o
√
{
˚)^Apple event °dONLNd«
|ä
à
(
Öä!objects that can be contained in j °dONLNdË
|

à
ë)åApple event objects of class ^°dONLNd
|
í
à
∞)|cText\ °dONLNd

|
∞
à
ª). T뇰dONLNd
|
∫
à
ø)

o`°dONLNd
|
¿
à
Á)     support õ‡°dONLNd
|
Á
à)'Apple °dONLNd
âä
ï¿(
íäevents that r%`°dONLNd*
â¡
ï
H)7!efer to elements of object class ç °dONLNdK
â
H
ï
f)ácTextã@°dONLNdP
â
f
ï
Æ), your applicatioÔ °dONLNda
â
Æ
ï
‹)H
n should aO†°dONLNdk
â
›
ï)/ssociate the °dONLNdx
ñä
¢®(
üäcText~ °dONLNd}
ñ®
¢
W)) object class with paragraphs, lines, wor5@°dONLNd¶
ñ
X
¢)∞)ds, and characters in its documents. The °dONLNdœ
£ä
ØØ(
¨ä
list of pr`†°dONLNdŸ
£Ø
ØÂ)%operties defi8°dONLNdÊ
£Ê
Ø
)7ned for class ˝`°dONLNdÙ
£

Ø
=)9cText˚Ä°dONLNd˘
£
=
Ø
Å) includes the pr[‡°dONLNd    
£
Ç
Ø
ß)E    operties A °dONLNd
£
®
Ø
Ã)&pColorÅÄ°dONLNd
£
À
Ø
–)#, ÅÄ°dONLNd
£
–
Ø
Ó)pFont†°dONLNd
£
Ó
Ø
Û), °dONLNd!
∞ä
ºΔ(
πä
pPointSize|@°dONLNd+
∞Δ
ºÀ)<, |@°dONLNd-
∞À
º
)
pScriptTagxÄ°dONLNd7
∞

º
)<, and 堡dONLNd=
∞

º
a)pTextStyles·Ä°dONLNdH
∞
a
º
Ã)B. If you want to support ÷¿°dONLNda
∞
Ã
º    )kApple events °dONLNdn
Ωä
…
:(
Δä(that distinguish a boldface 12-point worÄ°dONLNdñ
Ω
;
…
Ç)±d of object class ê`°dONLNd®
Ω
Ç
…
†)GcTextéÄ°dONLNd≠
Ω
†
…
©) fr'`°dONLNd∞
Ω
™
…)
om an italic 14-point °dONLNdΔ
 ä
÷õ(
”äworÄ°dONLNd…
 ú
÷)Xd, for example, your application must associate the point size and style of text in its ˇˇ«a°dONLNd    !
׊
„Ì(
‡ädocuments with the prD√°dONLNd    6
◊Ó
„
)d    operties ˇˇx$Òd°dONLNd    ?
◊

„
O)%
pPointSizeˇˇ«a̧°dONLNd    I
◊
O
„
d)< and ˇˇx$iÜ°dONLNd    N
◊
e
„
ß)pTextStylesˇˇ«aef°dONLNd    Y
◊
ß
„
∫)B defiûÁ°dONLNd    ^
◊
∫
„
Û)ned for class ˇˇx$∫j°dONLNd    l
◊
Û
„)9cTextˇˇ«a∏ä°dONLNd    q
◊
„). ˇZF@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-46    )B
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records4^*¿
¯
°dONLNd\lgú(dlFigure 3-17°dONLNd\Ægª)BAn É °dONLNd\ªg
()Apple event object of class ,
Courier¿°dONLNd+\
)g
B)ncWord
°dONLNd0\
Dg
Ü) contained in an í°dONLNdA\
Ög
€)AApple event object of 

q*Å
¯4q*Å
¯

ˇ·ˇ‚7^°dONLNdWfÆq≈(nÆclass Ä@°dONLNd]f≈q˜)
cParagraph

.*5
¯4.*4
¯ /l/
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdil.ú(*lFinding e–°dONLNdqú.
)0Apple Event Objectsˇˇˇˇˇˇ€r(*

3
°dONLNdÜ4l@†(=lMost of the ≤Ä°dONLNdí4†@
    )4Apple events in the Cor¢‡°dONLNd©4
    @
Ö)ie suite and the functional-ar°dONLNdΔ4
Ö@
æ)|ea suites defi∞@°dONLNd‘4
æ@
Ï)9ned in the °dONLNdflAlM
(Jl%Apple Event Registry: Standard Suitesm¿°dONLNd
A
    M
—)ù/ can include parameters that consist of object °dONLNd
3NlZà(WlspecifiÓ °dONLNd
:NàZó)er rÔ`°dONLNd
>NóZ©)ecorc¿°dONLNd
BN™Zπ)ds. 釰dONLNd
FNπZø)
YO`°dONLNd
GNøZ
∞)8our application’s handlers for these events can use the ‡°dONLNd
N
∞Z
Ê)Ò    AEResolveÌÄ°dONLNd
àN
ÊZ
Ë)6
 °dONLNd
â[lg¢(dlfunction to r °dONLNd
ñ[£g˙)7esolve object specifi¿°dONLNd
´[˙g
    )Wer r°dONLNd
Ø[
    g
)ecorì`°dONLNd
≥[
g
Ç)ds: that is, to locate the x†°dONLNd
Œ[
Çg
Ò)gApple event objects they °dONLNd
Áhltì(ql    describe.°dONLNd
ÒzlÜ*The ª¿°dONLNd
ızܵ)    AEResolve∏`°dONLNd
˛zµÜ
C)6! function parses an object specifi醰dONLNd z
DÜ
S)èer r臰dONLNd$z
SÜ
e)ecor@°dONLNd(z
fÜ
±)d and performs r›Ä°dONLNd8z
∞Ü
Ê)Jelated tasks °dONLNdEálìà(êlthat ar °dONLNdLáâì
) e the same for all object specifig¿°dONLNdmá
ì
)Üer ri°dONLNdqá
ì
0)ecor›`°dONLNduá
0ì
I)ds. W6 °dONLNdzá
Jì
á)hen necessary◊`°dONLNdáá
Üì
õ)<, the 4¿°dONLNdçá
úì
“)    AEResolve1`°dONLNdñá
“ì
‘)6
 °dONLNdóîl†ó(ùl
function c~Ä°dONLNd°îò†Ô),alls application-defi     °dONLNd∂î†
ñ)X&ned functions to perform tasks that arx°dONLNd‹î
ñ†
⁄)¶e unique to the °dONLNdÏ°l≠
(™l&application, such as locating a specifi¡ °dONLNd°
≠
)£c S°dONLNd°
≠
◊)-Apple event object in the application’s data °dONLNdBÆl∫w(∑lstrfi°dONLNdEÆw∫é)ucturc‡°dONLNdJÆè∫ì)
e-Ä°dONLNdKÆî∫ö)s.

f*mß4g*mß"h*]

Å*
¯4Å*
¯4Ä)Å*ò@@
ˆ@
ˆÅ*¡ ¡¡? ˇ¿˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙ò@@Ä
ˆ@Ä
ˆ¡*

 ? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙ò@Ä¿
ˆÄ¿
ˆ

*
A ? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙ò@¿

ˆ¿

ˆ
A*
Å ? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙ò@

@
ˆ

@
ˆ
Å*
¡ ? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙ò@
@
Ä
ˆ
@
Ä
ˆ
¡*
 ? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙? ˇ‡˙ò@
Ä
¿
ˆ
Ä
¿
ˆ
*A ? ˇ‡˙ ˇ‡˙¡¡¡¡¡¡¡¡¡¡¡¡¡    #·¿&«    ! ÄÈ«    aÄ!«    a¿ÄG«
í@Ä»

!HÄ»    ?√‡Á«¡¡¡¡¡$ 
¯x
Ç@2`@@
Ñ‚$ ê
Ä@" 
@Ä‚&"âË≤l)IȀǢ#·8hΩ¡¶IgõÂ[#á`ª‰&" YE 4w™Ö*È÷UBê©b©TäMJMU°M‰&"
KN
‰     $%7OJ    íËÑë]ƒ)§í"IíâÈ    "I‰&"éà@L"J\Tõ
§ã≈!{ƒE∞©.ìfi”ãc”‰&"ãá@3»g1ìá#íƒtÇ íªÇ ëîí}äBí‰@˙B¸ ÷@˙B¸†÷Ä˙B¸@÷¡¡ 
¿ ¡¿¿˛÷ Ä
Ä
 ˛÷bîê.ñ¯*">ÜäÓ%µ}ññ÷gz®R´P]eT
ï)JJí/Z÷íSp‰Ú`ô.à%$ÓBRíJR÷
•¿ÖD™Hº*º"Zûd|ñ÷;8r<†LGH    )‹'î‰S$÷ ¸@¸
’ ¸@
¸
’ ¸Ä˚
‡’¡¡'
膿‡@tH˝@Äp ¿Ä
8ÄÄÊ'E1˛@ @Ä˝  @
ÄÄÊ($≈)ÄvÂe•$eË∂ ∂≤6F\ì`-ı°—|ãcêRít∑ŒÊ($¶*ÄöJãfi§™IZ +SVZJ®©†F¢R≤®ï°(ÔUZêÊ($
,Äíúíî…íR JRR“ë1I D¬îó%"H$Jn'ìÊ($
HÅ&—)m~⁄¶‘Ñɶ◊˘“`≕ùy™cPDî∏™'ÇÊ($éi—§èΔHîë$$§¢‰âQ"H…DF÷ëB Œc'ÂÊ˝ 
ı¯Ñ·˝ 
ı¯Ñ·˙

ÎÑ·¡¡
˛@Ä0ÅÜ¿ ◊ò@
¿
Ú
ˆ
¿
Ú
ˆA*s §@˝A
ì  ◊•ˆ\ãa”íÉ+∏ÍéC@í%wD†Ÿ
'(H®ï¢®%u@*î°√úN®´–Ÿ
Igâ1%!·p?fl¶8S%¡dÑ«%‹êŸm¡—˘™`r@    KU≠
Ñe    a- ŸInëQCß∫Á2pi6Ê√ôÊN6Ó¿Ÿı@˚
ÿı@˚
ÿı@˚
ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡ 
¿ÄÕ
 Äb
ÃbîêÄZ GÅl¿Œgz®Ä≠] *5@ŒíSpÅ)I\r&Õ
•¿GRvDN¿Œ;88íå\<FIŒ ˛Äà ˛Äà ˛…¡¡
‡A‡êw‡Ä
’ê@ê"@)
’í·<∂:Ÿ    î"N≤@)"˙Àí‹◊•Ab…ZRjâ(<ÀU@Ie) ◊
    ÅD RîLä#»DR^ÄR,·&I◊
¡%2¶∂ù0¯Dtà¿õ82?R◊äÉíq$‹íÁPÓTßà“-‚*"8◊¸à˛ ˛—¸à˛ ˛†—
¸p˙¿œ¡¡
˛@ §@$$ •ˆ\VD ò@@
ˆ@
ˆÅ*¡ 
¡¡…3˘…@˙   ˙…@˙…@˙…@˙   ˙…@˙   ˙…@˙…@˙…@˙! Â0˛
å01Ä<˛¸ ˙‰0
Ä
Ä`006˛¸@˙! Â<˜ænÔ=ÔªœÛ˝ª˘œΩ„∑œfi¸˜¸ ˙ ‰<fiˇ?ˇˆgøÌôÊw˛Ûo˚Δ˝ÌˆfiflÄ˝@˙ ‰ffi¯1ÿˆgæaôÊwÊ3Ãf3ovˆflÄ˝@˙ ‰f˜øè˜=Ô˝œc˝ø˘Ô˚√ÒÌ˛fi˜Ä˝@˙ ‰Δ¸˛

Ä˚¿¸ ˙„Δ¸˛

Ä˚<¿¸@˙   ˙…@˙…@˙…@˙ „‡Ä˛9ƒ @˙ ˙‚`
˛F<
˙@˙ „9¡Àè=∑πΔwÇF$6áf„8˚ ˙‚&",HíFäNdY)D˚@˙‚'·ÊsâHí}ƒä5§Q(Ú|˚@˙‚&@â0≤@DäDS(≤@˚@˙ „w„™?∏_?éwsé?m˜Y<˚ ˙
‹DÔ@˙ ›DÔ ˙
‹8Ô@˙…@˙·ÄÄ¿¿Ä    Ĉ@˙ ‚Ä@@Ĉ ˙‚≥ú˘£‹CfiÌ6p⁄Ôsé{∏‡˚@˙ „íaÑ÷BDâHMîåA$E˙ ˙‚í\ºí^Dâ§HIîˇœ'¸‡˚@˙‚≤ƒ¨íVC    DHIîÑ$, ˚@˙‚[8WŸÎ„ú‰BÏ˝Öfi{≈Û◊»˚@˙ ›
@ ˙„˚
@ˆ¸@˙ ›
Ä ˙
„ÄË@˙
ŒÄ˝@˙
‰Á@˙   ˙Â
ν@˙   ˙
 Ê@˙ Í@˛@˙…@˙ Á ˙
Õ˛@˙ Á¿Â ˙…@˙ÁÁ`@˙…@˙ È
„ ˙Ë
Ê@˙ò@@Ä
ˆ@Ä
ˆ¡*

 
   ˙
Ë „@˙
ˉˇ@˙ËÄÂ@˙ ÈÄÂ ˙ËÄÂ@˙ ÈÄÂ ˙ËÄÂ@˙ËÄÂ@˙ËÄÂ@˙ ÈÄÂ ˙ËÄÂ@˙ ÈÄÏ
ĸ ˙ËÄ·¸@˙ËÄÎ ¸@˙ËÄÎ0¸@˙ ÈĘ¿¯¸ ˙ËÄà˝
Ä˝@¯¸@˙ ÈÅËàAŒ¿zHŸŸp¯¸ ˙ËÄò„ãúcìcâH¯¸@˙ËÄòâ Δ¿Ç$DëDâH¯¸@˙ËÄÁ>˜ºۜیϯ¸@˙ È
ÄĢ
˜¸ ˙Ë
Å¿˘˜¸@˙ ÈÄθ ˙ËÄ˙ı@˙ËÄ¿
˜    @˙Ëʼn]ÁÄ
I'åÛÖ˜    ŸÃ›é@˙  ÈÄó"í˛sàrL@˜•>èÿ ˙ËÄî"í@DàíDL@˜•0é@˙  ÈÄÓŸÄ„˛yüÔĘôŒÖ‹ ˙Ë
ÄÄÏ
˛@˙Ë
Å¿Ï
˛@˙ËÄθ@˙' ÈIJ1˛˛`˛Åê
êB  ˙$ËÄÄ@˝c¸à êä˛@˙' ÈÅ·6wòÛ'òwÄx1(q˛gyᱫêflß ˙%ËÄë¬A"rä@Q˛à    , Ç(üäl@˙%ËÄô2HA íHä@x
q)¯âI#$ÇÈêäc@˙%ËÄÊ·æ˜fiyæw`€ˇ1Ê0˛Á¸Δ–Ün@˙ È
ÄÄϸ ˙Ë
ſϸ@˙ ÈÄθ ˙ËÄ@
˛

ı˝@˙ËÄp˛
    ı˝@˙Ë
ʼnú«ºÉp
    ıŸèõú@˙ È
Äó"BPaà
    ıÛ”>R ˙Ë
Äî"BS¯
    ı2S&R@˙ È
ÄÓ˜mÁfi0ΔıÒœí ˙Ë
ÄÄÏ@˙Ë
Å¿Ï@˙ËÄθ@˙ Èĸ˝ ¯¸ ˙ËÄÄIJÒ˘¸@˙  ÈÅÍù∑ëÊ»q¿xIc≈˘¸ ˙ËÄí"‚Çàã˛q! ˘¸@˙ËÄí>¢bí௿xA! ˘¸@˙ËÄÁ±ºa>7ÄÁœ˚∞˘¸@˙ È
ÄIJ
0¸ ˙Ë
Å¿˛`¸@˙ ÈÄÏ

¿¸ ˙ËÄÏ˚@˙ËÄÂ@˙ËÄÂ@˙ò@Ä¿
ˆÄ¿
ˆ

*
A 
 ÈÄÂ ˙ËÄÂ@˙ ÈÄÂ ˙ËÄÂ@˙ËÄÂ@˙ËÄÂ@˙ ÈÄÂ ˙ËÄÂ@˙ ÈÄÂ ˙ËÄÂ@˙ËÄÂ@˙ËÄÂ@˙ ÈÄÂ ˙ËÄÂ@˙ ÈÄÂ ˙ËÄı
‡Û@˙ËÄÙ0Û@˙ËÄÙÛ@˙ ÈįˆÛ ˙ËÄò¸˛ÄÛ@˙ ÈÄé8˝ÄÛ ˙ËÄâD˝~ïõÄÛ@˙ËÄâ|˝ƒ∂TÄÛ@˙ËÄâ@˝4jTÄÛ@˙ ÈÄ
›º˝‚IìÄÛ ˙ËÄÙÛ@˙ ÈÄÙÛ ˙ËÄÙÛ@˙ËÄÙÛ@˙ËĈÛ@˙ Èĸ
Û ˙ËÄñ'˝    
Û@˙ ÈÄD*X˝
Á∂pÛ ˙ËÄÃÁ˝ôÃêÛ@˙Ëà˛Å˝ôLêÛ@˙ËÄT~˝ó    4pÛ@˙ Í

ÄÙÛ ˙ËÄÙÛ@˙ Í
0ÄÙÛ ˙ËÄÙÛ@˙ÍÄ
ĈÛ@˙Ë
Ä˚@Û@˙ Î@ÄœmÓp    @Û ˙ËÄR$ëÄ
ŒJÕ¿Û@˙ ÏÄR$üpí[*@Û ˙ËÄL,ê    í5*@Û@˙Ï
˛ÄÓœ‡é$…¿Û@˙ËĈÛ@˙ Ì ˛ÄˆÛ ˙Ì˝ÄˆÛ@˙ Ó˝ÄÙÛ ˙ÌÄ˝Ä
ĈÛ@˙Ë
Ä˚
 @Û@˙Ó¸Äs¿˝`@Û@˙ ÈÄⸯJŸ¿Û ˙Ô˚Ä⸉[2@Û@˙ ÈÄâ¸
d52@Û ˙Ô`˚ÄsÄ˝
$$—¿Û@˙ËÄÙÛ@˙˙ÄÙÛ@˙ ÈÄÙÛ ˙Ä˙ÄÙÛ@˙ ÈÄ
‚˜Û ˙Ò˘Ä#˝ @Û@˙ò@¿

ˆ¿

ˆ
A*
Å 
ËÄ
#˝`@Û@˙Ú¯Ä
'2˝¯JŸ¿Û@˙ ÈÄ
“˝
d[2@Û ˙$Ú@¯Ä
"˝        d52@IJ˙@˙" ÈÄπ«˝$$—¿Ä
˙ ˙Û˜ÄÙô£;‹˙@˙ËÄÙΩW•¡(˙@˙Ù
ˆÄÙ°T%1(˙@˙ ıˆÄÙùS§‡»˙ ˙Ù0ˆÄh@˘Û@˙  ˆıÄ @ @Û ˙ËÄ–Ï‹n`@Û@˙%ı@ıÄk%"—¯JŸ¿ ˝ ˚@˙ ËÄJ%_    d[2@¸ ˚@˙( ˜ÙÄJeP    d52@.9õ78˚ ˙"ËÄÌæÎ/$$—¿∏'◊¶|§˚@˙ ¯
ÛÄÙ¶&T¶L§˚ ˙ËÄÙº9”û?$˚@˙˜ ÛÄÙ¸ ˙@˙ËÄÙ˛ 8˙@˙ ˘ÚÄ
Ä †0˚Û ˙ËÄÄ Ä @¯@˙' ˘ÄÚÄÏ„æh˜
`@
˙ ˙"ËÄ$îa5êê¯JŸ¿ú”9«¿˚@˙&˘ÒħìØ$óêd[2@ΩÙ¶C ˚@˙"ËĨ∞´$ïêd52@•¶C ˚@˙( ˚Ä«ˆz¯$$—¿úúÛ%¡¿˚ ˙ËÄÙ˚@˙@˙ ˚`ÄÙ¸
Ä˙ ˙ËÄÙÛ@˙˚ÔÄÙ
¸¿˚@˙ËIJ
¿˘
`@˚@˙$ ÈIJ@ @3∏Ù<€¿˚ ˙8˝Δ¿6¿˛ÄfiÌ6p    `@~a¢d@˚@˙9 ¿¿06¿˛ÄâH    ¯JŸ¿Iô‚D¿˚ ˙9{fl∑wû˜œÁ˘˛›¸ÁfiÒˇflfi˛Äâ§Hd[2@?pÚ\Û`˚@˙1oüˇ˚3fl˚ÃÛ;ˇy∑˝„≥∂˛Ä    DH    d52@Û@˙1Ô|Ï{3flÃÛ;Ûáf3≥∂˛Äú‰BÏ$$—¿Û@˙) ˚flè«˚û˜ÔÁ±˛fl¸˜˝·Ôû˛Ä@ˆÛ ˙˛c¸˝¿˜Ä@ˆÛ@˙ c¸˝¿˜ÄĈÛ ˙ËÄÙÛ@˙Ë
ÄıÛ@˙0ÎÄ˙ @Û@˙ ÈÄ–¸    `@Û ˙
͡˛h¸    ¯JŸ¿Û@˙
 ÍH¸d[2@Û ˙
ÍH¸
d52@Û@˙
Íϸ$$—¿Û@˙
ÍÙÛ@˙
 ÍÙÛ ˙
ÍÙÛ@˙
 Ò
¯¸ÙÛ ˙
¸¿ˆÛ@˙
¸@¸aÛ@˙!
¸s‹‡˛ïÛ@˙!
 ¸I#˛üƒ¨‹Û ˙(`˚˙¸I?˛ï%≤§Û@˙)  ˝Ä
˙¸I!˝ï#R§Û ˙-¢!8
Ûo˙

Ôû˛c"LúÛ@˙#`#å`*âë˙ÄÙÛ@˙#b$Éâ˙Ê„ngÙÛ@˙$ ú˚fi
ÈsÕÄ˚IóΔ¸ÙÛ ˙ÒIîFÉÙÛ@˙ò@

@
ˆ

@
ˆ
Å*
¡ 
 ÒF„¬~ÙÛ ˙
Ä˙!Û@˙)
˘`˚
Ä=‹p˛%Û@˙.?+¿ ˝¸í"IJoƒ¨‹Û@˙0 ëwû¿)$ û3Œ˝
!ì˛p˛%%≤§Û ˙/\äH
Œ!»1¸C˛í˛%#R§Û@˙/ PäI¿
"I1¸
ÁÀĢ·˛#"LúÛ ˙%∏wfè˘Ê清C.ÙÛ@˙Ò    C)ÄÙÛ@˙ÒA/ÙÛ@˙
 ¸ÙÛ ˙"
˛
˚¸ÙÛ@˙( <A¿˛
$˚¸˙aÛ ˙*ísÚy¿x$˚˙ïÛ@˙*\â    AÑ $˚˙ƒ¨‹Û@˙*Pâ    LD#‡x$˚    [8˙e%≤§Û@˙* ∏w›∑üx¿˚fH˙Ö#R§0Û ˙!Ò¶H˚Û"Lú`Û@˙ Òö8ı
¿Û ˙
¸Â@˙
˝`¸
ǸÂ@˙!
;9 ˛‰ÄR¸Â@˙! íÛv˙C€!«
‡èÜ<R¸Â ˙!RIã1
",˛Ñ8ÇD¸Â@˙! RIäâ*#„
‡Ñ»Ç@¸Â ˙!åÔœwµƒ¯fi„?Ôº¸Â@˙˚¯¸Â@˙˚¯¸¡@˙
 Ò
¸„ ˙
Í„@˙
 Í„ ˙
Í„@˙
Í„@˙
Í„@˙
 Í„ ˙
Í„@˙
 Í„ ˙
Í„@˙
Í„@˙
Í„@˙
 Í„ ˙
Í„@˙
 Í„ ˙
Í„@˙
Í„@˙
Í„@˙
 Í„ ˙
Í„@˙
 Í„ ˙
Í„@˙
Í„@˙
Í„@˙ 
Ô„ ˙    Ä
 Ú„@˙ ?7v√˛Ù„ ˙Ä
bLæ|ØÄÙ„@˙Ä
D¶L(Ä
Ù„@˙
q<û;óÄ
Äı„@˙
 ˜Äı„ ˙
˜Äı„@˙
 ˜Äı„ ˙
˜Äı„@˙
˜Äı„@˙ÄÄ˝Äı„@˙ò@
@
Ä
ˆ
@
Ä
ˆ
¡*
 
 
@˛ÄÄı„ ˙ÄÛÜ„foòÄIJ˚„@˙ ÄLâóœó–ÄÄ
˚„ ˙ÄLàî…ÜÄõCsÒú˚„@˙Àáì«s–Äæß…¬H˚„@˙
˜Ä¢§I2H˚„@˙
 ˜Äû£»·à˚„ ˙
˜Äı„@˙
 ˜Äı„ ˙¯Äı„@˙
¸Ä@A˙„@˙ÅÄ˛C@¸„@˙ Áçôª`ÄNJŸ«Ã‡¸„ ˙
I&_>W¿ˇÃÿ[2C>@¸„@˙ …"S&@ÄΔ52C2@¸„ ˙GOÀ¿Ä‹$—¡. ¸„@˙
˜Äı„@˙
˜Äı„@˙
 ˜Äı„ ˙
˜Ä˛ ˚„@˙
 ˜Ä ˚„ ˙
˛
ê¸Ä”9«¡¨w¸„@˙

∞ÄÙ¶C"~ø„@˙ĸô±æ`ĶC"23¸„@˙ Ú&}z_@ÄÛ%¡¡ÓÓ¸„ ˙≤"eJ@IJ@˘„@˙ Äí]9œ@ÄĢ„ ˙
˜Äı„@˙
˜Ä˜„@˙
˜Äz˜„@˙
 ˜ÄãÑÿ˘„ ˙
˜ÄÇN`˘„@˙ ê¸ÄäR@˘„ ˙Ä0
Äwo˘„@˙|ô±æ`
Ù„@˙Ä≤&}z_@Ù„@˙ Ä≤"eJ@Ù„ ˙]9œC¸Ù„@˙
 Í„ ˙
Í„@˙
Í„@˙
Í„@˙
 Í„ ˙
Í„@˙
 Í„ ˙
Í„@˙
Í„@˙
Í„@˙
 Í„ ˙
Í„@˙
 ͡˛„ ˙…@˙…@˙…@˙   ˙…@˙   ˙…@˙…@˙…@˙   ˙…@˙   ˙…@˙ò@
Ä
¿
ˆ
Ä
¿
ˆ
*A 
 U@˙ ÿ˙¡¡¡¡¡¡¡¡¡¡¡¡¡    #·¿&«    ! ÄÈ«    aÄ!«    a¿ÄG«
í@Ä»

!HÄ»    ?√‡Á«¡¡¡¡¡$ 
¯x
Ç@2`@@
Ñ‚$ ê
Ä@" 
@Ä‚&"âË≤l)IȀǢ#·8hΩ¡¶IgõÂ[#á`ª‰&" YE 4w™Ö*È÷UBê©b©TäMJMU°M‰&"
KN
‰     $%7OJ    íËÑë]ƒ)§í"IíâÈ    "I‰&"éà@L"J\Tõ
§ã≈!{ƒE∞©.ìfi”ãc”‰&"ãá@3»g1ìá#íƒtÇ íªÇ ëîí}äBí‰@˙B¸ ÷@˙B¸†÷Ä˙B¸@÷¡¡ 
¿ ¡¿¿˛÷ Ä
Ä
 ˛÷bîê.ñ¯*">ÜäÓ%µ}ññ÷gz®R´P]eT
ï)JJí/Z÷íSp‰Ú`ô.à%$ÓBRíJR÷
•¿ÖD™Hº*º"Zûd|ñ÷;8r<†LGH    )‹'î‰S$÷ ¸@¸
’ ¸@
¸
’ ¸Ä˚
‡’¡¡'
膿‡@tH˝@Äp ¿Ä
8ÄÄÊ'E1˛@ @Ä˝  @
ÄÄÊ($≈)ÄvÂe•$eË∂ ∂≤6F\ì`-ı°—|ãcêRít∑ŒÊ($¶*ÄöJãfi§™IZ +SVZJ®©†F¢R≤®ï°(ÔUZêÊ($
,Äíúíî…íR JRR“ë1I D¬îó%"H$Jn'ìÊ($
HÅ&—)m~⁄¶‘Ñɶ◊˘“`≕ùy™cPDî∏™'ÇÊ($éi—§èΔHîë$$§¢‰âQ"H…DF÷ëB Œc'ÂÊ˝ 
ı¯Ñ·˝ 
ı¯Ñ·˙

ÎÑ·¡¡
˛@Ä0ÅÜ¿ ◊ò@
¿
Ú
ˆ
¿
Ú
ˆA*s 
§@˝A
ì  ◊•ˆ\ãa”íÉ+∏ÍéC@í%wD†Ÿ
'(H®ï¢®%u@*î°√úN®´–Ÿ
Igâ1%!·p?fl¶8S%¡dÑ«%‹êŸm¡—˘™`r@    KU≠
Ñe    a- ŸInëQCß∫Á2pi6Ê√ôÊN6Ó¿Ÿı@˚
ÿı@˚
ÿı@˚
ÿ¡¡¡¡¡¡¡¡¡¡¡¡¡¡ 
¿ÄÕ
 Äb
ÃbîêÄZ GÅl¿Œgz®Ä≠] *5@ŒíSpÅ)I\r&Õ
•¿GRvDN¿Œ;88íå\<FIŒ ˛Äà ˛Äà ˛…¡¡
‡A‡êw‡Ä
’ê@ê"@)
’í·<∂:Ÿ    î"N≤@)"˙Àí‹◊•Ab…ZRjâ(<ÀU@Ie) ◊
    ÅD RîLä#»DR^ÄR,·&I◊
¡%2¶∂ù0¯Dtà¿õ82?R◊äÉíq$‹íÁPÓTßà“-‚*"8◊¸à˛ ˛—¸à˛ ˛†—
¸p˙¿œ¡¡
˛@ §@$$ •ˆ\VD ò@@
ˆ@
ˆs*≥ 
'(H®®D 
Igâ1(D m¡—˘P"H InëPê∞ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
ˆ@Ä
ˆ≥*Û ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
ˆÄ¿
ˆÛ*3 ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

ˆ¿

ˆ3*s ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
ˆ

@
ˆs*≥ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆ≥*Û ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆÛ*3 ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆ3*e ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@
ˆ@
ˆs*≥ 

'(H®®D 
Igâ1(D m¡—˘P"H InëPê∞ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@@Ä
ˆ@Ä
ˆ≥*Û 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@Ä¿
ˆÄ¿
ˆÛ*3 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@¿

ˆ¿

ˆ3*s 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@

@
ˆ

@
ˆs*≥ 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
@
Ä
ˆ
@
Ä
ˆ≥*Û 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
Ä
¿
ˆ
Ä
¿
ˆÛ*3 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ò@
¿
Ú
ˆ
¿
Ú
ˆ3*e 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ˇ@j@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡ä
W’ê)orking WT¿)$ith Object Specifiÿ )C
er Records

, (‡3-47
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähê(eä
Y@Ä°dONLNd
\êhÒ)our application can prÔ`°dONLNd\Òh
å)a"ovide two kinds of application-defiO†°dONLNd:\
çh
˙)úned functions for use by ,
Courier°dONLNdSiäu¿(rä    AEResolve|†°dONLNd\i¿u≈)6. 
|†°dONLNd^i≈u
9)Object accessor functionsÜ@°dONLNdwi
9u
W)t locate °dONLNdi
Xu)'Apple event objects. Every application °dONLNd¶väÇ
 (ä"that supports simple object specifiÒ¿°dONLNd…v
 Ç
/)ñer rÛ°dONLNdÕv
/Ç
A)ecorg`°dONLNd—v
BÇ
q)
ds must pr·¿°dONLNd€v
qÇ
Ω)/ovide one or mor“`°dONLNdÎv
ΩÇ)Le object accessor °dONLNd˝Éäè∏(åäfunctions. 
À@°dONLNd
É∏è
,).Object callback functions`‡°dONLNd
!É
-è)u2 perform other tasks that only an application can °dONLNd
Sêäú
k(ôä1perform, such as counting, comparing, or marking z`°dONLNd
Ñê
kú
Δ)·Apple event objects. °dONLNd
ö¢äÆ∏(´ä
Each time •¿°dONLNd
§¢∏ÆÓ).    AEResolve¢`°dONLNd
≠¢ÓÆ
Ê)6; calls one of your application’s object accessor functions °dONLNd
ËØäªø(∏äsuccessfullyá`°dONLNd
ÙØæª
B)4 , the object accessor function rî`°dONLNdØ
Bª
º)Ñeturns a special descriptor r—Ä°dONLNd1Ø
ºª
Œ)zecorE‡°dONLNd5Ø
ϻ
˚)d, called a°dONLNd@Ø
¸ª
˛)-
 
°dONLNdAºä»¶(≈ätoken,Ä°dONLNdGºß»›) that identifiG@°dONLNdUº›»
f)6 es either an element in a specifiˆ °dONLNdvº
f»
º)âed container or a prz@°dONLNdäº
Ω»
Ô)Woperty of a °dONLNdñ…ä’¶(“äspecifiÓ °dONLNdù…¶’≥)ed ı °dONLNd†…≥’
Î)GApple event object. The token can be of any descriptor type, including °dONLNdÁ÷䂯(flädescriptor types you defiÚ`°dONLNd÷¯‚
.)nne yourself. °dONLNdËäÙê(Òä
Y@Ä°dONLNdËêÙ
c)2ou install object accessor functions by using the Ô¿°dONLNdAË
cÙ
Ì)”AEInstallObjectAccessorÁ °dONLNdXË
ÌÙ
Ô)ä
 °dONLNdYıä

Û(˛äfunction. Much like the ” °dONLNdqıÛ


q)iAEInstallEventHandlerÀ@°dONLNdÜı
q


ù)~ function, °dONLNdë
ä

(
äAEInstallObjectAccessorw`°dONLNd®



9)ä     uses an 
Ä°dONLNd±

:

¿)&object accessor dispatch table) °dONLNdœ

¿

‰)Ü to map °dONLNd◊
ä
ç(
ä
rE°dONLNdÿ
é
Æ)equests4‡°dONLNdfl
Ø
±)!
 ¥‡°dONLNd‡
±
π)fo~@°dONLNd‚
∫
¿)    r íÄ°dONLNd‰
¿

)Apple event objects Í`°dONLNd¯



I)Yto the apprH‡°dONLNd

J

Ê)1%opriate object accessor functions in °dONLNd(
ä
(û(
%äyour~`°dONLNd,
ü
(°)
 ˛`°dONLNd-
°
(˜)application. These rº†°dONLNdA
¯
(
)W    equests rÒÄ°dONLNdJ


(
c)'efer to objects oÖ¿°dONLNd[

d
(
ç)E
f a specifiG¿°dONLNdf

é
(
⁄)*ed object class in °dONLNdy
)ä
5∑(
2ä
containers,Ä°dONLNdÉ
)∏
5∫).
 ¨Ä°dONLNdÑ
)∫
5Ÿ)identifiÉ °dONLNdå
)⁄
5
G) ed by a token of a specifiò¿°dONLNd¶
)
G
5
í)med descriptor typl°dONLNd∑
)
ì
5
ö)Le.°dONLNd∫
;ä
G⁄(
DäResponding to an ç °dONLNdÀ
;⁄
G
G)PApple event that include,‡°dONLNd„
;
H
G
a)ns an o∞¿°dONLNdÈ
;
a
G
î)bject specifi˘Ä°dONLNdˆ
;
î
G
£)3er r˙¿°dONLNd˙
;
£
G
µ)ecoro °dONLNd˛
;
∂
G)d typically involves °dONLNd
Hä
Tº(
Qäthese steps:°dONLNd!
[ã
gí+
1.°dONLNd$
[ñ
g
>)'After determining that the event is an ÌÄ°dONLNdK
[
>
g
t)®Apple event8@°dONLNdV
[
u
g
ñ)7, your a∂†°dONLNd^
[
ñ
g
€)!pplication calls °dONLNdo
gñ
s
(
pñAEProcessAppleEventx‡°dONLNdÇ
g

s

)r
.°dONLNdÖ
yã
Öí(
Çã2.°dONLNdà
yñ
Ö©)The ª¿°dONLNdå
y©
Ö
)AEProcessAppleEvent¥†°dONLNdü
y

Ö
k)r function uses the 冰dONLNd≤
y
k
Ö
Ô)PApple event dispatch table to °dONLNd–
Öñ
ë˝(
éñdispatch the event to th=Ä°dONLNdË
Ö˛
ë
])he your application’s h°dONLNd˛
Ö
^
ë
z)`andler£¿°dONLNd
Ö
z
ë
∑) for that eventÉ °dONLNd
Ö
∏
ë
∫)>
.°dONLNd
óã
£í(
†ã3.°dONLNd
óñ
£©)The ]`°dONLNd
ó©
£
;)!Apple event handler extracts the ° °dONLNd>
ó
;
£
÷)í!Apple event parameters, and passeÏ¿°dONLNd_
ó
÷
£
Ú)õs the o|†°dONLNdf
ó
Û
£    )bject °dONLNdl
£ñ
Ø≤(
¨ñspecifiÓ °dONLNds
£≤
Ø¡)er rÔ`°dONLNdw
£¡
Ø”)ecorc¿°dONLNd{
£‘
Ø
%)ds they contain to î °dONLNdé
£
%
Ø
U)QAEResolvë °dONLNdñ
£
U
Ø
[)0
eê¿°dONLNdó
£
[
Ø
])
.°dONLNdö
µã
¡í(
æã4.°dONLNdù
µñ
¡©)The ª¿°dONLNd°
µ©
¡fl)    AEResolve∏`°dONLNd™
µfl
¡
∂)63 function uses the object accessor dispatch table t–¿°dONLNd›
µ
∂
¡)◊o call one or mor`°dONLNdÓ
µ

¡)Ke °dONLNd
¡ñ
Õ
ø(
 ñGobject accessor functions, one at a time, that can identify the nested @°dONLNd7
¡
¿
Õ
¯(
 
¿Apple event °dONLNdC
Õñ
ŸÈ(
÷ñobjects described bÔ`°dONLNdV
ÕÈ
Ÿ
)Sy each oˇ@°dONLNd^
Õ

Ÿ
@)$bject specifiH°dONLNdk
Õ
A
Ÿ
P)4er rI@°dONLNdo
Õ
P
Ÿ
b)ecorΩ†°dONLNds
Õ
b
Ÿ
Û)"d. Each object accessor function rf`°dONLNdï
Õ
Ù
Ÿ)íeturns °dONLNdú
Ÿñ
Â
(
‚ña token for the object it fi°dONLNd∏
Ÿ

Â)n<nds, which in turn helps to determine which object accessor °dONLNdÙ
Âñ
ÒÕ(
Óñfunction the k†°dONLNd

Œ
Ò
)8    AEResolveh@°dONLNd

Â

Ò
†)6& function will use to locate the next ´`°dONLNd0
Â
†
Ò
ı)úApple event object.°dONLNdE
˜ãí(ã5.°dONLNdH
˜ñú)
T†¿°dONLNdI
˜ú©)he ª¿°dONLNdL
˜©fl)    AEResolve∏`°dONLNdU
˜fl
)6 functiou@°dONLNd]
˜


)"n rㆰdONLNd`
˜

;)eturns the } °dONLNdk
˜
<
B)/
fi⇰dONLNdm
˜
B
R)nal √†°dONLNdq
˜
R
ê)token for the rÑ°dONLNdÄ
˜
ë
Ú)?equested object to the °dONLNdóñÛ(ñapplication’s handler`‡°dONLNd¨Ûı)]
.°dONLNdÆä °(äThe rÄ¿°dONLNd≥° 
)esolution of an object specifi7°dONLNd—
 
-)}er r8@°dONLNd’
- 
?)ecor¨†°dONLNdŸ
? )0d always begins with the outermost container it °dONLNd        !ä-¶(*äspecifiÓ °dONLNd    !¶-
˛)Les. For example, to locate a table named “Summary of Sales” in the document °dONLNd    \.ä:

(7änamed “Sales Report,” the ª °dONLNd    v.

:
7)w    AEResolve∑¿°dONLNd    .
7:
g)6 function fi“¿°dONLNd    ã.
g:)0&rst calls an object accessor function °dONLNd    ±;äG
i(Dä3that can locate the document, then uses the token r °dONLNd    ‰;
jG)‡(eturned by that function to identify an °dONLNd
HäT
Ñ(Qä=object accessor function that can locate the table. It then rJÄ°dONLNd
IH
ÖT)˚"eturns the token for the table to °dONLNd
kUäaö(^äthe °dONLNd
oUöa
() Apple event handler that called ©`°dONLNd
èU
(a
^)é    AEResolve¶°dONLNd
òU
^a
`)6
.°dONLNd
ögäsê(pä
T†¿°dONLNd
õgês
)he chapter “Resolving and CrH‡°dONLNd
∑g
s
l)Éeating Object SpecifiE °dONLNd
Ãg
ms
ë)Zer Recor£¿°dONLNd
‘g
ës)$ds” in this book describes in °dONLNd
ÚtäÄ (}ädetail how to r@°dONLNd
tÀÄ
")Aesolve object specifi%‡°dONLNdt
"Ä
1)Wer r' °dONLNdt
1Ä
C)ecorõÄ°dONLNdt
CÄ)0ds and how to write and install object accessor °dONLNdNÅäç
(ääand object callback functions.PÄ°dONLNdlÅ
ç
)Ç
 ˇ @ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-48    )B
About the ¿))Apple Event Manager4^*¿
¯

^*x
¯4^*x
¯

à*ê
¯4â*ê
¯ ä*ä
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNdu*àv(É*
About the F'°dONLNd
uvà
)LApple Event ManagerˇˇˇˇˇˇU˛(É

3
°dONLNdôl•r(¢l
Y@Ä°dONLNd ôr•≥)ou can use the ãÄ°dONLNd/ô≥•
)AApple Event Manager to,Zapf Dingbats°dONLNdFØl∂q(µl
n
°dONLNdH¨x∏{)
rE°dONLNdI¨|∏™)
espond to     ‡°dONLNdS¨™∏‰).Apple events놰dONLNd_¨‰∏
I): as a server application°dONLNdx¡l»q(«l
n
°dONLNdzæx Ä)crµ@°dONLNd|æÄ ø)eate and send ç`°dONLNdäæø ˘)?Apple events °dONLNdñæ˙ 
\); as a client application°dONLNdØ”l⁄q(Ÿl
n
°dONLNd±–x‹{)
rE°dONLNd≤–|‹∂)esolve and cr;¿°dONLNdø–∂‹
):eate object specifiO†°dONLNd“–
‹
)Mer rP‡°dONLNd÷–
‹
$)ecor≈@°dONLNd⁄–
$‹
.)ds°dONLNd›ÂlÏq(Îl
n
°dONLNdfl‚xÓù)support îÄ°dONLNdÁ‚ùÓ§)%
A[¿°dONLNdË‚•ÓŸ)pple event r$@°dONLNdÙ‚⁄ÓÏ)5ecorò†°dONLNd¯‚ÏÓ
)ding°dONLNd˝Ûlˇr(¸l
T†¿°dONLNd˛Ûrˇö)
his sectio.†°dONLNd
Ûõˇ∫))n brieflπ°dONLNd
Û∫ˇ
b)%y summarizes the steps involved in prE¿°dONLNd
5Û
cˇ
Ê)©oviding each kind of support °dONLNd
R
l
v(
    lanQ`°dONLNd
T
w
¢)
d tells whØ@°dONLNd
^
¢
™)+er=‡°dONLNd
`
´
√)    e to fià °dONLNd
g
√
Â)nd the r[†°dONLNd
o
Ê

v)#!elevant information in this book.


1*
8
¯4
2*
8
¯ 
3l
3
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd
ë
"l
1≤(
-lSupporting ≈Z°dONLNd
ú
"±
1
O)EApple Events as a Server R¯°dONLNd
µ
"
O
1
ë)ûApplicationˇˇˇˇˇˇ€r)°
3
°dONLNd
¬
8l
Dr(
Al
Y@Ä°dONLNd
√
8r
D
) ou do not need to implement all $ °dONLNd
„
8

D
c)êApple events at once. A`°dONLNd
˘
8
c
D
i)a
Y
‡°dONLNd
˙
8
i
D
˜) ou can begin by supporting just °dONLNd
El
QÄ(
Nlthe r¢`°dONLNd
EÄ
Qó)equirπ†°dONLNd$
Eó
Q
)ed events and, if necessaryáÄ°dONLNd?
E

Q
Ω)u(, the events sent by the Edition Managerc¿°dONLNdg
E
Ω
Q
’)±. The °dONLNdm
Rl
^ÿ(
[lbeginning of the section √†°dONLNdÜ
Rÿ
^
    )l
“Handling U°dONLNdê
R


^
r)2Apple Events” on page P†°dONLNd¶
R
s
^
Ä)i4-4§Ä°dONLNd©
R
Ä
^
Ÿ) describes how to prΩ@°dONLNdΩ
R
Ÿ
^
Ù)Yovide °dONLNd√
_l
kÓ(
hlthis minimal level of support.°dONLNd‚
ql
}o*
IfiÄ°dONLNd„
qo
}Ç)t is r@°dONLNdÈ
qÉ
}ƒ)elatively easy tßÄ°dONLNd˘
qƒ
}œ)Ao rb°dONLNd¸
q–
}

)espond to t«†°dONLNd
q


}
)1he r߆°dONLNd
q

}
))equir懰dONLNd
q
)
}
 )%ed events and the events sent by the °dONLNd5
~l
äå(
álEditionÄ°dONLNd<
~ç
äè)!
 ëÄ°dONLNd=
~è
ä≤)Manage0‡°dONLNdC
~≥
ä∂)$
rf °dONLNdD
~∂
äÌ). If, however% °dONLNdQ
~Ì
ä˜)7, y¥@°dONLNdT
~˜
ä
a)
our application cannot rÍ@°dONLNdl
~
a
ä
ª)jespond to any other U °dONLNdÄ
~
º
ä
Ÿ)[Apple °dONLNdÜ
ãl
ó
5(
îl0events, other applications will not be able to rd¿°dONLNd∂
ã
5
ó
◊)…&equest services that involve locating °dONLNd‹
òl
§à(
°lspecifiÓ °dONLNd„
òà
§é)c °dONLNdÂ
òè
§
≠)@Apple event objects within your application or its documents, an≤@°dONLNd%
ò
≠
§
Û(
°
≠d users will not °dONLNd6
•l
±Ø(
Ælbe able to contr
@°dONLNdF
•∞
±
i)D+ol your application by executing scripts. T© °dONLNdq
•
h
±
s)∏o rc†°dONLNdt
•
t
±
¢)
espond to (Ä°dONLNd~
•
¢
±
Ò).Apple events it is °dONLNdë
≤l
æñ(
ªllikely to rù‡°dONLNdú
≤ñ
æª)*    eceive fríÄ°dONLNd•
≤ª
æ
1)%om other applications or frñ`°dONLNd¿
≤
1
æ
Ú)v*om scripting components, your application °dONLNdÍ
øl
˵(
»lmust be able to r‚@°dONLNd˚
øµ
À
)Iespond to the appr, °dONLNd
ø
    
À
8)Topriate corµÄ°dONLNd
ø
8
À
J)/e an–Ä°dONLNd
ø
J
À
U)d f¿ °dONLNd
ø
V
À
ã)unctional-ar{¿°dONLNd+
ø
å
À
ò)6ea g°dONLNd.
ø
ò
À
◊)Apple events. °dONLNd=
—l
›s(
⁄l
O[‡°dONLNd>
—t
›∫)nce you have pr˚@°dONLNdM
—∫
›
ä)F0ovided the basic level of support for the Requir @°dONLNd}
—
ã
›
Ò)—ed suite and for events °dONLNdï
fil
ÍÈ(
Álsent by the Edition ManagerÙ†°dONLNd∞
fiË
Í
)|, you should°dONLNdΩ
Ùl
˚q(
˙l
n
°dONLNdø
Òx
˝œ)decide which other \‡°dONLNd“
Ҝ
˝
~)W&Apple event suites you want to support°dONLNd˘lq(l
n
°dONLNd˚xà)defir °dONLNdˇâ¿)ne the hierar%Ä°dONLNd¡fi)8chy of a@°dONLNdfi
‚):Apple event objects within your application that you want °dONLNdMx
5(x*scripting components or other applicationsT@°dONLNdw
6
8)æ
 ‘@°dONLNdx
8
;)
t†°dONLNdy
<
€)%o be able to identify—that is, which °dONLNdûx'
E($x.Apple event objects can be contained by other Å@°dONLNdÃ
E'
Ú)Õ'Apple event objects in your application°dONLNdÙ0l7q(6l
n
°dONLNdˆ-x9ä)writÙ`°dONLNd˙-ä9Ã)e handlers for t‹Ä°dONLNd
-Õ9⁄)Che ô °dONLNd-⁄9
ï)*Apple events you support, and install corr≥‡°dONLNd7-
ï9
Ò)ªesponding entries in °dONLNdL9xE (Bxyour application’s € °dONLNd_9 E
;)RApple event dispatch tablüÄ°dONLNdx9
<E
@)r
e°dONLNdzJlVr(Sl
Tµ¿°dONLNd{JqV∂)o decide which ¬†°dONLNdäJ∂V
≠)E5Apple event suites you want to support and how to defiY °dONLNd¿J
ÆV
À)¯ne the °dONLNd«WlcÜ(`lhierarª°dONLNdÕWÜcï)chyã¿°dONLNd–Wñcò)
 ¿°dONLNd—Wôc§)of ˆ¿°dONLNd‘W£c
à)
5Apple event objects in your application, consult the ¡°dONLNd    W
âc
Â)ÊApple Event Registry: °dONLNddlp¨(mlStandard Suites6‡°dONLNd.d≠p
)A and evaluate which É`°dONLNdBd
p
X)[Apple events and ô‡°dONLNdSd
Xp
Ë)P Apple event object classes make °dONLNdsql}
(zl(sense for your application. If necessary7 °dONLNdõq
}
É)´, you can extend the defi?`°dONLNd¥q
É}
‡)lnitions of the standar°dONLNd q
·}
È)^d °dONLNdÃ~läº(álApple events and ñÄ°dONLNd›~ºä
d)P'Apple events objects to cover special r∫@°dONLNd    ~
dä
{)®equir—Ä°dONLNd        ~
{ä
Î)ements of your applicatio∂¿°dONLNd    "~
Ïä
ˆ)qn. °dONLNd    %ãlór(îlIt ‡°dONLNd    'ãsóx) iâ@°dONLNd    )ãxóû)
s better tö‡°dONLNd    3ãûó¯)&o extend the standar䆰dONLNd    Gã¯ó
)Zd defiÄ°dONLNd    Mã
ó
^)nitions rather thaW@°dONLNd    _ã
^ó
Ç)Ln to defi“†°dONLNd    hã
Çó
î)$ne y|¿°dONLNd    lã
ïó
fl)our own custom °dONLNd    {òl§¶(°lApple events¿°dONLNd    áòߧ÷);, because oÃÄ°dONLNd    íò÷§
ÿ)/:nly those applications that choose to support your custom -Ä°dONLNd    Ãò
٤
ˆ(°
ŸApple °dONLNd    “•l±
G(Æl3events explicitly will be able to make use of them.ˇ>H@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@äIntroduction to •)8Apple Events4⁄ä˙(‡ä
About the ¿))Apple Event Manager

, (‡3-49
ˇˇˇˇˇˇˇˇ4
4
0lòÄ.
B
0oMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
B
0o
B
0o$””””””””””””””””””””””””””””””òÄ

6
0@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
6
0@
6
0@˜˜˜˜˜˜˜˜˜˜˜˜˜
˛ˇ˛ˇˇˇˇ˛ˇˇ    ˇˇˇ
˙ˇ
˛ˇˇˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
54+?òÄ

56+@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
56+@
56+@$˜˛˙ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇˇ˚ˇ˛˙ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˝˝ˇˇ˛ˇ˚˝ˇ¸˛¸ˇˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝ˇˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˛¸ˇ
ˇ˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähê(eä
T†¿°dONLNd
\êh
)he chapter “Responding to 9‡°dONLNd\
    h
z)yApple Events” in this boo˘@°dONLNd4\
zh
Ë)qk describes how to write 9†°dONLNdM\
Èh
)o
A‡°dONLNdN\
Òh)pple °dONLNdSiäuÂ(räevent handlers and rüÄ°dONLNdgiÂu
)[elated ræ@°dONLNdoi
u
&)!outines=†°dONLNdvi
'u
¥)!. The chapter “Resolving and CrÄ°dONLNdïi
µu
Ò)éeating Object °dONLNd£väÇß(äSpecifi‡°dONLNd™vßÇÀ)er RecorOÄ°dONLNd≤vÃÇ
.)%ds” describes how to r懰dONLNd»v
.Ç
Ö)besolve object specifi—Ä°dONLNd›v
ÖÇ
≠)W
ers in an wÄ°dONLNdÁv
≠Ç
˘)(Apple event that °dONLNd¯Éäèµ(åä
describes ùÄ°dONLNd
ɵè
±)+9Apple event objects in your application or its documents.°dONLNd
<ïä°Ù(ûäIf your application can rÓ@°dONLNd
UïÙ°
")j
espond to ≥ °dONLNd
_ï
"°).3Apple events, you can make it scriptable simply by °dONLNd
í¢äÆπ(´ä
adding an ,
Courier—¿°dONLNd
ú¢πÆø)/
'—`°dONLNd
ù¢øÆ◊)aeteœ‡°dONLNd
°¢◊Æ›)
'œÄ°dONLNd
¢¢›Æ„) rÄ°dONLNd
§¢‰Æ¸)esour\¿°dONLNd
©¢¸Æ
—)0ce. Scripting components use your application’s `°dONLNd
Ÿ¢
“Æ
ÿ)÷
'°dONLNd
⁄¢
ÿÆ
)aeteÄ°dONLNd
ޢ
Æ
ˆ)
' °dONLNd
ߢ
ˆÆ
¯)
 °dONLNd
‡Øäªç(∏ä
rE°dONLNd
·Ø骶)esourç@°dONLNd
Êضª
>)#ce to obtain information about the ˘@°dONLNd    Ø
>ª
†)òApple events and corrÄ°dONLNdØ
°ª
“)c
esponding °dONLNd(ºä»(≈äThuman-language terminology that your application supports. The chapter “Apple Event °dONLNd|…ä’ê*
Tµ¿°dONLNd}…è’„)erminology Resourg†°dONLNdé…‰’)UCces” in this book describes how to optimize your implementation of °dONLNd—÷ä‚
î(flä:Apple events for use by scripting components and how to cr °dONLNd÷
ï‚
∂(fl
ïeate an ∫ °dONLNd÷
∂‚
º)!
'π¿°dONLNd÷
º‚
‘)aete∏@°dONLNd÷
‘‚
⁄)
'∑‡°dONLNd÷
⁄‚
‡) r¸‡°dONLNd÷
‡‚
¯)esourE °dONLNd ÷
˘‚)ce.


H
4
H
 
    ä
    

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd$¯ä
–(
äSupporting ≈Z°dONLNd/¯œ

g)EApple Events as a Client ·°dONLNdH¯
g

©)òApplicationˇˇˇˇˇˇ€r)ß
3
°dONLNdU
ä
µ(
ä    Because ujÄ°dONLNd^
∂
Ú),sers can send ˜¿°dONLNdl
Ú

)<@Apple events to a variety of applications simply by executing a °dONLNd¨
ä
'
9(
$ä'script, many applications have no need ˝†°dONLNd”

9
'
D)Øto 5Ä°dONLNd÷

E
'
\)send J‡°dONLNd€

\
'
ƒ)Apple events. However_@°dONLNd

ƒ
'    )h, if you want to °dONLNd

(ä
4
(
1äfactor your application for r$‡°dONLNd
(

4
){ecorô@°dONLNd"
(

4
fl).ding, or if you want your application to send @°dONLNdP
(
‡
4
˝)…Apple °dONLNdV
5ä
A∂(
>ä
events dirS`°dONLNd`
5∂
A
d),)ectly to other applications, you can use 5 °dONLNdâ
5
d
A
Ã)ÆApple Event Manager r)°dONLNdû
5
Ã
A
˙)houtines to °dONLNd©
Bä
Ní(
Käcrµ@°dONLNd´
Bí
N—)eate and send ç`°dONLNdπ
B—
N
)?Apple events.ï °dONLNdΔ
B

N
)=
 °dONLNd»
Tä
`ê(
]ä
Tµ¿°dONLNd…
Tè
`ª)
o send an °dONLNd”
Tº
`
!)-Apple event, you must,Zapf Dingbats°dONLNdÈ
jä
qè(
pä
n
°dONLNdÎ
gñ
sû)crµ@°dONLNdÌ
gû
s¬)    eate the     ‡°dONLNdˆ
g√
s˘)%Apple event°dONLNd
|ä
Éè(
Çä
n
°dONLNd
yñ
Ö
)add parameters and attributes°dONLNd"
éä
ïè(
îä
n
°dONLNd$
ãñ
ó∑)use the k °dONLNd,
ã∏
ó‹)"AESendh‡°dONLNd2
ã‹
ó
Q)$ function to send the event°dONLNdN
úä
®ê(
•ä
T†¿°dONLNdO
úê
®–)he chapter “CrZ °dONLNd]
ú—
®
))Aeating and Sending ˝ °dONLNdp
ú
(
®
Δ)W#Apple Events” in this book describeäÄ°dONLNdì
ú
«
®)üs how to perform °dONLNd§
©ä
µº(
≤äthese tasks.


⁄H
·4
€H
· 
‹ä
‹

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd±
Àä
⁄–*$Supporting ≈Z°dONLNdº
Àœ
⁄
K)EApple Event Objectsˇˇˇˇˇˇ€r(
÷
3
°dONLNd—
·ä
Ì‚(
ÍäIf your application r,†°dONLNdÊ
·„
Ì
#)Yesponds to cor7†°dONLNdÙ
·
#
Ì
v)@e and functional-ar˝‡°dONLNd
·
v
Ì
Ç)Sea È °dONLNd

·
Ç
Ì)Apple events, it must also be °dONLNd(
Óä
˙≠(
˜ä    able to r6Ä°dONLNd1
ÓÆ
˙
)$esolve object specifiI °dONLNdF
Ó

˙
)Wer rJ`°dONLNdJ
Ó

˙
&)ecoræ¿°dONLNdN
Ó
&
˙
f)ds that describb‡°dONLNd]
Ó
g
˙
Ñ)Ae the o`°dONLNdd
Ó
Ñ
˙
‰)bjects on which those ·¿°dONLNdz
Ó
‰
˙
)`Apple °dONLNdÄ
˚ä
È(äQevents can act. In addition to the tasks described in the chapter “Responding to °dONLNd—ä•*Apple˝Ä°dONLNd÷•ß)
 }Ä°dONLNd◊®
•)8Events,” you must perform the following tasks to handle ∞‡°dONLNd
•
ı)˝Apple events that °dONLNd!ä!Â(äcontain object specifiqÄ°dONLNd7Ê!ı)\er rr¿°dONLNd;ı!
)ecorÁ °dONLNd?
!
)ds:°dONLNdC+ä2è(1ä
n
°dONLNdE(ñ4†)
W¬†°dONLNdF(ü4
q)    3rite object accessor functions that can locate the B °dONLNdy(
r4)”!Apple event objects you support, °dONLNdö4ñ@ÿ(=ñand install corr`°dONLNd™4Ÿ@)CGesponding entries in your application’s object accessor dispatch table.°dONLNdÚIäPè(Oä
n
°dONLNdÙFñR†)
W¬†°dONLNdıFüR
ç)    8rite any object callback functions that you decide to prq¿°dONLNd-F
éR
¢)Ôovid놰dONLNd1F
¢R
±)e. Të°dONLNd5F
±R
ˆ)o handle object °dONLNdERñ^≤([ñspecifiÓ °dONLNdLR≤^¡)er rÔ`°dONLNdPR¡^”)ecorc¿°dONLNdTR‘^
°)0ds that specify a test, your application must pr9@°dONLNdÑR
°^)Õovide at least two object °dONLNdû^ñj
¨(gñ?callback functions: one that counts objects and one that compar@°dONLNd›^
≠j
—(g
≠es them.°dONLNdÊsäzè(yä
n
°dONLNdËpñ|™)Call Á¿°dONLNdÌp™|‡)    AEResolve‰`°dONLNdˆp‡|È)6 fr}@°dONLNd˘pÍ|
)
om your f¿°dONLNd    
p
|
Ø)(!Apple event handlers whenever an ¥ °dONLNd    "p
Ø|
Á)ùApple event °dONLNd    .|ñà
3(Öñ#parameter includes an object specifi\Ä°dONLNd    R|
4à
C)ûer r]¿°dONLNd    V|
Cà
U)ecor“ °dONLNd    Z|
Uà
[)
ḋ°dONLNd    [|
[à
`). °dONLNd    ^çäô
(ñäThe chapter “Resolving and CrH‡°dONLNd    {ç
ô
l)âeating Object SpecifiE °dONLNd    êç
mô
ë)Zer Recor£¿°dONLNd    òç
ëô
Ô)$ds” describes how to °dONLNd    ≠öä¶
®(£äBperform these tasks. It also describes how applications that send 2¿°dONLNd    Ôö
®¶
(£
®Apple events to °dONLNd    ˇßä≥÷(∞äthemselves or dir˛Ä°dONLNd
ß÷≥
e)L"ectly to other applications can cr⁄`°dONLNd
2ß
e≥
≤)èeate object specifiÓ@°dONLNd
Eß
≤≥
¡)Mer rÔÄ°dONLNd
Iß
¡≥
”)ecorc‡°dONLNd
Mß
‘≥
‡)ds.ˇ2@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
3,    Helvetica    ˇˇ—ÚˇÆ(@lIntroduction to •)8Apple Events4⁄*˙
¯

(‡*3-50    )B
About the ¿))Apple Event Manager4^*¿
¯

k*r
¯4l*r
¯ mlm
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\lk≤(glSupporting ≈Z°dONLNd\±k
=)EApple Event Recordingˇˇˇˇˇˇ€r(g

3
°dONLNd"rl~®({lIf you make yz°dONLNd/r©~
®)=:our application scriptable, you may also want to make it ro`°dONLNdir
®~
∫)ˇecor„¿°dONLNdmr
∫~
Ú)dable. Users °dONLNdzlã{(àlof ré`°dONLNd~{ãç)ecor¿°dONLNdÇéãˆ)dable applications can r“†°dONLNdöˆã
)hecorG°dONLNdû
    ã
É)d their actions in the form o÷†°dONLNdª
Éã
à)zf L °dONLNdΩ
âã
ê)
A`°dONLNdæ
ëã
·)pple events that a °dONLNd—ålò
ù(ïlFscripting component translates into a script. When a user executes a r÷‡°dONLNd
å
ùò
Ø(ï
ùecorK@°dONLNd
å
∞ò
·)ded script, °dONLNd
'ôl•y(¢lthe]`°dONLNd
*ôz•|)
 ›`°dONLNd
+ô|•
)#scripting component sends the same ›Ä°dONLNd
Nô
•
Í)£.Apple events to the application in which they °dONLNd
|¶l≤}(Ølwere†°dONLNd
¶}≤à)e rt@°dONLNd
Ƕà≤ö)ecorˆ°dONLNd
ܶö≤≠)ded.°dONLNd
ã∏lƒr(¡l
Tµ¿°dONLNd
å∏qƒ„)o make your application r“@°dONLNd
•∏„ƒı)recorF†°dONLNd
©∏ˆƒ
)    dable, yo††°dONLNd
≤∏
ƒ
M)(
u should u>°dONLNd
º∏
Nƒ
Y)0se f@°dONLNd
ø∏
Yƒ
•)Apple events to rj‡°dONLNd
–∏
•ƒ
ˆ)Leport user actions °dONLNd
„≈l—á(Œlto the ∂‡°dONLNd
Í≈á—
) Apple Event Manager in terms of ö °dONLNd
≈
—
Ô)ñ0Apple events. One way to do this is to separate °dONLNd:“lfi
v(€l=the code that implements your application’s user interface frˆ`°dONLNdw“
vfi
Á(€
vom the code that actually °dONLNdëfllÎ
¢(ËlFperforms work when the user manipulates the interface. This is called 
I‡°dONLNd◊fl
£Î
Ã(Ë
£    factoringc °dONLNd‡fl
ÃÎ
Â)) your °dONLNdÊÏl¯ó(ıl
applicatioeÄ°dONLNdÏò¯†),n.∂‡°dONLNdÚφ¯¢)
 ÿÄ°dONLNdÛÏ¢¯©)
A °dONLNdÙÏ™¯≈) factor‘ °dONLNd˚Ï≈¯
‹)Bed application acts as both the client and server application for °dONLNd=˘l
ˇ(
l$Apple events it sends to itself in rÄ°dONLNda˘


ã)îesponse to user actions. When rf@°dONLNdĢ
ã

ù)ãecor⁄†°dONLNdÑ˘
ù

Ó)ding is turned on, °dONLNdó
l
|(
lthe °dONLNdõ
|

Û)TApple Event Manager sends a copy of every event than an application sends to itself °dONLNdÔ
l

(
l&to the scripting component or other pr¿°dONLNd



f)©ocess that turned r7 °dONLNd(

g

y)Recor´Ä°dONLNd,

y

ù)ding on.°dONLNd5
%l
1∏(
.lThe chapter “Intrµ`°dONLNdF
%∏
1
])L&oduction to Scripting” in this book prª†°dONLNdl
%
]
1
‚)•ovides an overview of how to °dONLNdâ
2l
>
-(
;l+make your application both scriptable and r+`°dONLNd¥
2
.
>
@)¬ecorü¿°dONLNd∏
2
@
>
c)dable. T‡°dONLNd¿
2
d
>
≥)$he chapter “Recor†°dONLNd—
2
≥
>
…)Oding õ‡°dONLNd÷
2
…
>
Ê)Apple °dONLNd‹
?l
K
Y(
Hl6Events” describes how to factor your application for rR‡°dONLNd
?
Y
K
k)Ìecor«@°dONLNd
?
k
K
å)ding an}@°dONLNd
?
ç
K
Δ)"d explains thÄ@°dONLNd*
?
Δ
K
Õ)9e °dONLNd,
Ll
Xá(
UlApple˝Ä°dONLNd1
Lá
Xâ)
 }Ä°dONLNd2
Lä
XÕ)Event ManagerÏ@°dONLNd?
LŒ
X€)D’s r5Ä°dONLNdC
L‹
XÓ)ecor©‡°dONLNdG
LÓ
X
:)ding mechanism.ˇ#T@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4⁄∫˙,    Helvetica    .
(‡∫Contents,Palatino

, (‡    4-1    3,Ã(#∫CHAPTER ÿ)h
4
ˇˇˇˇˇˇˇˇ4
l4
älòÄ2
lA
ärMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lA
är
lA
är$œœœœœœœœœœœœœœœœœœœœœœœœœœœœœœòÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜˜ˇˇˇˇˇˇ(JH
Figure 4-0*    Listing 4-0*    
T)able 4-0

zH
,
4zH
, 
H
°dONLNd
∫
*˘+m Contentsˇˇˇˇˇˇ

ˇ·ˇ‚7^ˇˇ∫Ρ◊(qH
4°dONLNd[∫xÀ)r
RCΰdONLNd
[Ãx
k)esponding to Ú °dONLNd[
jx)ûApple Events
°dONLNd$
;∫
GÊ(
D∫    Handling `°dONLNd-
;Á
G
")-Apple EventsÎ@°dONLNd;
;
6
G
C)O4-4°dONLNd?
Hƒ
T
(
QƒAccepting an Ò¿°dONLNdL
H

T
7)<Apple Event醰dONLNdY
H
L
T
Y)L4-5°dONLNd]
Uƒ
a
-(
^ƒInstalling Entries in the í¿°dONLNdw
U
-
a
ó)iApple Event Dispatch TŒ °dONLNdç
U
ñ
a
¨)iablesD¿°dONLNdî
U
¡
a
Œ)+4-7°dONLNdò
bŒ
n—(
kŒ
IfiÄ°dONLNdô
b—
n
Y) nstalling Entries for the Requir∏†°dONLNdπ
b
Y
n
f)àed ø†°dONLNdº
b
f
n
°)Apple EventsôÄ°dONLNd 
b
∂
n
√)P4-8°dONLNdŒ
oŒ
{
+(
xŒInstalling Entries for 7†°dONLNdÂ
o
+
{
Á)](Apple Events Sent by the Edition ManagerΔ@°dONLNd

o
˚
{)–4-9°dONLNd

|Œ
àÊ(
ÖŒHow øÄ°dONLNd

|Ê
à
b)Apple Event Dispatching W#°dONLNd
0
|
b
à
u)|orksW@°dONLNd
6
|
â
à
ñ)'4-9°dONLNd
:
âƒ
ï
(
íƒHandling the Requirí`°dONLNd
M
â

ï
,)[ed ô`°dONLNd
P
â
,
ï
g)Apple Eventss@°dONLNd
^
â
|
ï
â)P4-1:Ä°dONLNd
a
â
â
ï
é)
1°dONLNd
c
ñŒ
¢Î(
üŒRequirE@°dONLNd
i
ñÏ
¢˘)ed L@°dONLNd
l
ñ˘
¢
4)Apple Events& °dONLNd
z
ñ
I
¢
V)P4-1Ì`°dONLNd
}
ñ
U
¢
Z)
1°dONLNd

£Œ
Ø
&(
¨ŒHandling the Open g¿°dONLNd
ë
£
&
Ø
v)XApplication Event@°dONLNd
§
£
ã
Ø
ù)e4-14°dONLNd
©
∞Œ
º
t(
πŒ!Handling the Open Documents Event~°dONLNd
Ã
∞
â
º
õ)ª4-15°dONLNd
—
ΩŒ
…
r(
ΔŒ"Handling the Print Documents Event˝`°dONLNd
ı
Ω
Ü
…
ò)∏4-17°dONLNd
˙
 Œ
÷
!(
”ŒHandling the Quit ¸Ä°dONLNd
 
!
÷
q)SApplication Eventö°dONLNd
 
Ü
÷
ò)e4-19°dONLNd$
◊ƒ
„(
‡ƒ    Handling `°dONLNd-
◊Ò
„
≠)-(Apple Events Sent by the Edition Manager†°dONLNdW
◊
¡
„
”)–4-20°dONLNd\
‰Œ

K(
ÌŒThe Section Read, Section Wh@°dONLNdw
‰
K

¢)}rite, and Section Scrú†°dONLNdå
‰
¢

Õ)W
oll Events?@°dONLNdò
‰
‚

Ù)@4-21°dONLNdù
Ҍ
˝
(
˙ŒHandling the Cr© °dONLNd¨
Ò

˝
p)Heate Publisher EventQ‡°dONLNd¬
Ò
Ö
˝
ó)o4-22°dONLNd«
˛ƒ
˜(ƒGetting Dat8°dONLNd“
˛¯

#)4
a Out of a¶¿°dONLNd‹
˛
#

+)+n ô¿°dONLNdfi
˛
+

b)Apple Event6†°dONLNdÎ
˛
w

â)L4-25°dONLNdŒ
5(ŒGetting Data Out of an ô¿°dONLNd
5
ú)gApple Event ParameterO °dONLNd
±
√)|4-26°dONLNd#Œ$
5(!ŒGetting Data Out of an ô¿°dONLNd:
5$
])g    Attribute[Ä°dONLNdE
r$
Ñ)=4-28°dONLNdJ%Œ1
q(.Œ%Getting Data Out of a Descriptor ListÊ°dONLNdq%
Ö1
ó)∑4-31°dONLNdv2ƒ>Œ(;ƒ
W¬†°dONLNdw2Õ>Á)    riting JÄ°dONLNd~2Ë>
K)Apple Event HandlersáÄ°dONLNdî2
_>
q)w4-33°dONLNdô?ƒK
(HƒReplying to an e°dONLNd®?
K
>)CApple Event
‡°dONLNdµ?
SK
e)L4-36°dONLNd∫LƒX˛(UƒDisposing of À °dONLNd«L˛X
\):Apple Event Data Str»`°dONLNd€L
\X
s)^ucturN@°dONLNd‡L
tX
})esT‡°dONLNd‰L
ëX
£)4-39°dONLNdÈYƒeŒ(bƒ
W¬†°dONLNdÍYÕe
<)    riting and Installing Coerz°dONLNdY
=e
{)pcion Handlersπ†°dONLNdY
èe
°)R4-41°dONLNdf∫rˆ(o∫Interacting Wù`°dONLNd%fˆr
))<ith the User7`°dONLNd3f
>r
P)H4-45°dONLNd8sƒ
(|ƒSetting the Client  °dONLNdKs

§)O!Application’s User Interaction PrΩ°dONLNdls
§
¥)ëeferi °dONLNdps
µ
Õ)ences{°dONLNdws
·
Û),4-46°dONLNd|ăå
(âƒSetting the Server ¥Ä°dONLNdèÄ
å
•)P!Application’s User Interaction PrV`°dONLNd∞Ä
¶å
∂)íeferÄ°dONLNd¥Ä
∑å
œ)ences`°dONLNdªÄ
„å
ı),4-48°dONLNd¿çƒô
?(ñƒRequesting User Interaction˙†°dONLNd›ç
Sô
e)è4-49ˇ¶@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+ú"CHAPTER à)>
44⁄*˙
¯
(‡*4-2,    Helvetica    )rContents4^*¿
¯
°dONLNd\úh≥(eúRefer⁄ °dONLNd\≥h
)ence to Responding to "†°dONLNd\
h
S)eApple Events¸Ä°dONLNd)\
gh
y)O4-56°dONLNd.i¶u…(r¶Data Str``°dONLNd6i u·)$ucturÊ@°dONLNd;i·u
#)es Used by the l@°dONLNdJi
$u
Ö)CApple Event Manager °dONLNd_i
öu
¨)v4-56°dONLNddv∞Ç˙(∞Descriptor Recorfi °dONLNdtv˙Ç
b)Jds and Related Data Str °dONLNdãv
cÇ
z)iucturí°dONLNdêv
zÇ
É)esò†°dONLNdîv
óÇ
©)4-56°dONLNdôÉ∞èÍ(å∞Apple Event >Ä°dONLNd•ÉÍè
$):Array Data T¥Ä°dONLNd±É
#è
7)9ypesL`°dONLNd∑É
Lè
^))4-60°dONLNdºê¶ú
"(ô¶Routines for Responding to % °dONLNd◊ê
"ú
])|Apple Eventsˇ°dONLNdÂê
qú
É)O4-61°dONLNdÍù∞©ª(¶∞Cr\°dONLNdÏùª©
,)eating and Managing the ;†°dONLNd
ù
,©
ñ)qApple Event Dispatch Tw°dONLNd
ù
ï©
´)iables̆°dONLNd
!ù
ø©
—)*4-61°dONLNd
&™∞∂Ë(≥∞Dispatching S@°dONLNd
2™Ë∂
#)8Apple Events- °dONLNd
@™
8∂
J)P4-66°dONLNd
E∑∞√
A(¿∞ Getting Data or Descriptor Recor˛@°dONLNd
e∑
A√
G)ë
d°dONLNd
f∑
H√
m)    s Out of g`°dONLNd
o∑
m√
t)%
A.†°dONLNd
p∑
u√
Ô)pple Event Parameters and °dONLNd
ä¬∞Œ‹(À∞
Attributes~¿°dONLNd
ñ¬ÒŒ
)A4-68°dONLNd
õœ∞€
X(ÿ∞&Counting the Items in Descriptor Lists °dONLNd
√œ
m€
)Ω4-74°dONLNd
»‹∞˯(Â∞Getting Items Frà°dONLNd
ÿ‹¯Ë
N)Hom Descriptor ListsM¿°dONLNd
Ì‹
cË
u)k4-74°dONLNd
ÚÈ∞ı˛(Ú∞Getting Data and % °dONLNdÈˇı
")OKeyworQÄ°dONLNd    È
"ı
H)#d-Specifi2°dONLNdÈ
Iı
V)'ed ó`°dONLNdÈ
Vı
†)Descriptor RecorıÄ°dONLNd%È
†ı
¶)J
d@°dONLNd&È
ßı
Ã)    s Out of ^†°dONLNd/È
Ãı
”)%
A%‡°dONLNd0È
‘ı
‹)E °dONLNd2Ù∞
…(˝∞Recor¢`°dONLNd7Ù…
”)ds˚ °dONLNd;ÙÁ
˘)4-78°dONLNd@

∞

+(

∞Requesting User Interaction˙†°dONLNd]


?

Q)è4-81°dONLNdb
∞
˜(
∞Requesting MorYÄ°dONLNdp
˜

)Ge T7@°dONLNds



W)ime to Respond to Ë°dONLNdÖ

V

ë)RApple Events¡‡°dONLNdì

¶

∏)P4-84°dONLNdò
∞
'
)(
$∞Suspending and Resuming Ì°dONLNd∞

)
'
ç)yApple Event Handlingy†°dONLNdΔ

¢
'
¥)y4-85°dONLNdÀ
(∞
4
G(
1∞"Getting the Sizes and Descriptor T( °dONLNdÌ
(
G
4
≥)óypes of Descriptor RecorÁÄ°dONLNd
(
≥
4
Ω)lds@@°dONLNd    
(
“
4
‰)4-89°dONLNd
5∞
A
"(
>∞Deleting Descriptor Recor"@°dONLNd'
5
#
A
-)sds{°dONLNd+
5
A
A
S)4-92°dONLNd0
B∞
N
l(
K∞(Deallocating Memory for Descriptor Recorχ°dONLNdX
B
l
N
v)ºdsE†°dONLNd\
B
ã
N
ù)4-93°dONLNda
O∞
[≈(
X∞Coerõ °dONLNde
O≈
[
)cing Descriptor TJ¿°dONLNdv
O

[
%)Lypes⠡dONLNd|
O
9
[
K)(4-94°dONLNdÅ
\∞
hª(
e∞Cr\°dONLNdÉ
\ª
h
A)eating and Managing the Coerµ °dONLNdü
\
A
h
≠)Ücion Handler Dispatch TV@°dONLNd∂
\
≠
h
√)lablesÇ°dONLNdΩ
\
◊
h
È)*4-96°dONLNd¬
i∞
uª(
r∞Cr\°dONLNdƒ
iª
u
•)2eating and Managing the Special Handler Dispatch TË °dONLNdˆ
i
§
u
∫)Èables^¿°dONLNd˝
i
œ
u
·)+4-99°dONLNd
v∞
Ç
(
∞Getting Information ãÄ°dONLNd
v

Ç
9)[
About the `°dONLNd 
v
:
Ç
õ)/Apple Event Manager«@°dONLNd5
v
Ø
Ç
Δ)u4-103°dONLNd;
ɶ
è(
å¶Application-Defi†°dONLNdK
É
è
*)Jned RoutinesI¿°dONLNdY
É
?
è
V)O4-104°dONLNd_
êú
ú
(
ôúSummary of Responding to u¿°dONLNdx
ê

ú
S)|Apple EventsO†°dONLNdÜ
ê
h
ú
)P4-108°dONLNdå
ù¶
©Ô(
¶¶Pascal Summary‡°dONLNdú
ù

©
)^4-108°dONLNd¢
™∞
∂‹(
≥∞    ConstantsÆ°dONLNd≠
™
∂
)@4-108°dONLNd≥
∑∞
√Õ(
¿∞Data T:`°dONLNdπ
∑Õ
√·)ypes“@°dONLNdø
∑ı
√
)(4-1ôÄ°dONLNd¬
∑

√
)12°dONLNd≈
İ
–◊(
Õ∞Routines≠`°dONLNdÕ
ƒ◊
–
+)' for Responding to % °dONLNd‡
ƒ
,
–
g)UApple Eventsˇ°dONLNdÓ
ƒ
{
–
à)O4-1Δ@°dONLNdÒ
ƒ
à
–
í)14°dONLNdÙ
—∞
›˙(
⁄∞Application-Defi†°dONLNd
—˙
›
4)Jned RoutinesI¿°dONLNd
—
I
›
V)O4-1°dONLNd
—
V
›
`)18°dONLNd
ަ
Í€(
Á¶    C SummaryᆰdONLNd#
fiÔ
͸)I4-1N‡°dONLNd&
fi¸
Í
)18°dONLNd)
Î∞
˜‹(
Ù∞    ConstantsÆ°dONLNd4
Î
˜˝)@4-1u@°dONLNd7
ν
˜
)18°dONLNd:
¯∞∑(
∞
D=@°dONLNd;
¯∏Õ)ata T:`°dONLNd@
¯Õ·)ypes“@°dONLNdF
¯ı
)(4-123°dONLNdL∞◊(∞Routines≠`°dONLNdT◊
+)' for Responding to % °dONLNdg
,
g)UApple Eventsˇ°dONLNdu
{
í)O4-124°dONLNd{∞˙(∞Application-Defi†°dONLNdã˙
4)Jned RoutinesI¿°dONLNdô
I
`)O4-128°dONLNdü¶+
.((¶Assembly-Language Summary~†°dONLNd∫
C+
Z)ù4-128°dONLNd¿,∞8∂(5∞
T∫¿°dONLNd¡,µ8›)rap Macr⁄°dONLNd…,›8Ê)(osåÄ°dONLNdÕ,˚8
)4-128°dONLNd”9¶E‡(B¶Result Codesï`°dONLNd·9ÙE
)N4-130ˇ?:@ˇˇˇˇˇ@

ˇ·ˇ‚7^,Palatino
&e.
3+ä"CHAPTER ”)>
4
4⁄ä˙
, (‡    4-3
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜,    Helvetica    ˇˇ—ÚˇÆ°dONLNd8äCê(@ä
R—B°dONLNd
8êC√)esponding to ,°dONLNd8ƒCˆ)4Apple Eventsˇˇˇˇˇˇ≠>(@
4
°dONLNd\äh¥(eä    This chap[@°dONLNd$\µhΩ)+teg@°dONLNd&\Ωh
Ñ)-r describes how your application can use the w@°dONLNdS\
Ñh
Û)«Apple Event Manager to °dONLNdjiäuç(rä
rE°dONLNdkiéuº)
espond to     ‡°dONLNduiºu˚).Apple events. d°dONLNdÉi˚u

)?
Y$Ä°dONLNdÑi

u
ê)!our application must be able to r¨‡°dONLNd•i
êu
Á)èespond to the four r5†°dONLNdπi
Ëu
ˇ)XequirL‡°dONLNdæi
ˇu)ed °dONLNd¡väÇ¿(äApple event ¿°dONLNdÃv¿Ç…)6s t  °dONLNdœv Ç
§)
0o take advantage of the launching and terminatinÒ°dONLNdˇv
§Ç
Ë)⁄g mechanisms t©Ä°dONLNd
v
ÈÇ)Ehat ar@°dONLNd
vÇ
)e °dONLNd
Éäè§(åäpart o¨†°dONLNd
ɧèÿ)f System 7 al`°dONLNd
'ÉŸè
")5nd later versionsL@°dONLNd
8É
#è
s)J of system softwar„Ä°dONLNd
JÉ
sè
w)P
e≠ °dONLNd
KÉ
xè
€). If your application pr[‡°dONLNd
cÉ
‹è
˚)dovides °dONLNd
jêäú(ôäYpublish and subscribe capabilities, it should also handle the events sent by the Edition °dONLNd
√ù䩱*ManagerT†°dONLNd
 ù±©º)'. Tä`°dONLNd
Õùª©
?)
 o be scriptable, or capable of rz°dONLNd
Ìù
?©
{)Ñesponding to á¿°dONLNd
˙ù
{©)<Apple events sent by scripting °dONLNd™ä∂–(≥äcomponents, yo°¿°dONLNd'™–∂
)Fur applicatio
°dONLNd4™
    ∂
V)9n should handle tî`°dONLNdE™
V∂
x)Mhe apprx†°dONLNdL™
x∂
ß)"opriate cor°dONLNdW™
®∂
˚)0e and functional-ar»@°dONLNdj™
˚∂)Sea °dONLNdm∑ä√¿(¿äApple event ¿°dONLNdx∑¿√Δ)6s.°dONLNd{…ä’°(“äBeforÛ¿°dONLNdÄ…°’ø)e you ré °dONLNdá…¿’
)ead this chapter1†°dONLNdó…
’
∫)F), you should be familiar with the chapterd@°dONLNd¿…
∫’
æ)¥
s°@°dONLNd¡…
æ’
’) “IntrXÄ°dONLNd«…
÷’)oduction to °dONLNd”÷ä‚
K(flä)Interapplication Communication” and “Intr·°dONLNd¸÷
K‚
Ä)¡oduction to ¥¿°dONLNd÷
Ä‚
˜)5Apple Events” in this book@°dONLNd"÷
¯‚
˝)x. ’†°dONLNd$÷
¸‚)
Yñ °dONLNd%÷‚)
o†°dONLNd&÷‚)u ˇˇ€°dONLNd(„äÔ
(Ïäshould also have a copy of the ÜΩ°dONLNdG„
Ô
≠)á%Apple Event Registry: Standard Suites‡È°dONLNdl„
≠Ô
Ï)ú available for r#⁄°dONLNd|„
ÌÔ
˝)@eferœ˙°dONLNdÄ„
˝Ô)ence§⁄°dONLNdÑ„Ô). °dONLNdáıä

∫(˛ä
Although t‚‡°dONLNdëı∫

«)0he üÄ°dONLNdîı«


è)+Apple events used by the Edition Manager ar-`°dONLNdøı
ê

)…e discussed in this chapterÜ¿°dONLNd⁄ı

)s, °dONLNd‹
ä
∫(
ä
you must r´@°dONLNdÊ
∫
)0Pefer to the chapter “Edition Manager” in this book for a full discussion of how °dONLNd6
ä

"(
ä to implement the Edition Manager°dONLNdV

$

´)ö’s publish and subscribe featurJ†°dONLNdu

´

∂)áes.°dONLNdy
!ä
-Õ(
*äThis chapter pr°°dONLNdà
!Õ
-)CGovides the basic information you need to make your application capable °dONLNdœ
.ä
:ô(
7äof ré`°dONLNd”
.ô
:’)esponding to ú °dONLNd‡
.’
:
)<Apple events. TY†°dONLNdÔ
.

:
%)Eo r °dONLNdÚ
.
&
:
a)espond to cor‚ °dONLNdˇ
.
a
:
¥);e and functional-ar®`°dONLNd
.
µ
:
¡)Tea 솰dONLNd
.
¡
:)Apple events, °dONLNd#
;ä
G
3(
Dä'your application must also be able to r≤`°dONLNdJ
;
3
G
ä)©esolve object specifi≈°dONLNd_
;
ä
G
ô)Wer rΔ@°dONLNdc
;
ô
G
´)ecor:†°dONLNdg
;
¨
G
ª)ds. e¿°dONLNdk
;
ª
G
¡)
Y&@°dONLNdl
;
¡
G
)
ou should °dONLNdv
Hä
Tç(
Qä
rE°dONLNdw
Hé
Tù)ead*`°dONLNdz
Hû
T†)
 ™`°dONLNd{
H†
T
&)the chapter “Resolving and CrdONLNdò
H
&
T
)Üeating Object Specifië °dONLNd≠
H
Ä
T
§)Zer RecorÔ¿°dONLNdµ
H
§
T
Ã)$    ds” befor® °dONLNdæ
H
Õ
T
))e you write °dONLNd 
Uä
a•(
^äApple˝Ä°dONLNdœ
U•
aß)
 }Ä°dONLNd–
U®
a
õ)8event handlers for events that can contain object specifi:`°dONLNd    
U
ú
a
´)Ùer r;†°dONLNd
U
´
a
Ω)ecor∞°dONLNd
U
Ω
a
…)ds.°dONLNd
gä
sï(
päThr °dONLNd
gñ
s°)e s¯¿°dONLNd
g°
sµ)ectio“‡°dONLNd
g∂
sæ)n $@°dONLNd!
gø
s)
“Handling µ†°dONLNd+
g
s
3)1Apple Events,”Ä°dONLNd9
g
4
s
6)D
 èÄ°dONLNd:
g
6
s
Ä)which begins on ‡°dONLNdJ
g
Å
s
ò)Kpage Z¿°dONLNdO
g
ô
s
¶)4-4Ɔ°dONLNdR
g
¶
s
±), d `°dONLNdU
g
±
s
ı)escribes how to,Zapf Dingbats°dONLNde
}ä
Ñè(
Éä
n
°dONLNdg
zñ
Ü—)accept and pr"‡°dONLNdt
z“
ÜÎ)<ocess m‡°dONLNdz
zÎ
Ü
%)Apple events°dONLNdá
èä
ñè(
ïä
n
°dONLNdâ
åñ
òÔ)install entries in the ņ°dONLNd†
åÔ
ò
i)YApple event dispatch tables°dONLNdº
°ä
®è(
ßä
n
°dONLNdæ
ûñ
™À)handle the r퇰dONLNd 
ûÀ
™‚)5equir™ °dONLNdœ
û‚
™
)    ed events°dONLNdŸ
≥ä
∫è(
πä
n
°dONLNd€
∞ñ
º
S))handle events sent by the Edition Manager°dONLNd
Ŋ
Ãè(
Àä
n
°dONLNd
–
Œ¥)get dat˘@°dONLNd
´
Œ›)
a out of a
†°dONLNd
¬fi
ŒÊ)*n Ù†°dONLNd
¬Â
Œ
)Apple event°dONLNd&
׊
fiè(
݊
n
°dONLNd(
‘ñ
‡
E)(write handlers that perform the action r܇°dONLNdP
‘
E
‡
ä)Øequested by an (‡°dONLNd_
‘
ä
‡
¿)EApple event°dONLNdk
Èä
è(
Ôä
n
°dONLNdm
Êñ
Úô)
rE°dONLNdn
Êö
Ú»)eply to an 3 °dONLNdy
Ê»
Ú˛).Apple event°dONLNdÖ
˚äè(
ä
n
°dONLNdá
¯ñø)    dispose o4‡°dONLNdê
¯¿≈)*f ™`°dONLNdí
¯≈
)Apple event data str±@°dONLNd¶
¯

6)Zuctur7 °dONLNd´
¯
7
@)es°dONLNdÆäè(ä
n
°dONLNd∞
ñÛ)write and install coer©`°dONLNdΔ
Û
.)]cion handlers°dONLNd‘ä'∂($ä
The sectio“‡°dONLNdfi∂'æ),n $@°dONLNd‡ø'
)    “Interacting WA†°dONLNdÓ
'
3)Aith the User@°dONLNd˙
3'
:)3,”û@°dONLNd¸
:'
á) which begins on †°dONLNd
à'
ü)Npage ÈÄ°dONLNd
ü'
±)4-45=`°dONLNd
≤'
Ω), dY °dONLNd
Ω'
‚)    escribes °dONLNd#1ä8è(7ä
n
°dONLNd%.ñ:õ)
hQ`°dONLNd&.ú:
ù):ow a server application can interact with the user when pròÄ°dONLNd`.
ù:
“(7
ùocessing an }¿°dONLNdl.
“:)5
Apple evenÜ °dONLNdv.:)3
t°dONLNdxCäJè(Iä
n
°dONLNdz@ñLõ)
hQ`°dONLNd{@úL
_).ow client applications set user interaction pr⁄‡°dONLNd©@
_L
o)√eferá°dONLNd≠@
pL
É)ence[‡°dONLNd±@
ÑL
à)
s°dONLNd≥Uä\è([ä
n
°dONLNdµRñ^õ)
hQ`°dONLNd∂Rú^°)
oΔ‡°dONLNd∑R°^
)w the client application’s p÷‡°dONLNd”R
^
)w
rõ‡°dONLNd‘R
^
,)eferH°dONLNdÿR
-^
Œ)%ences and the server application’s prÇ`°dONLNd˝R
Œ^
fi)°efer.Ä°dONLNd    
R
fl^
)ences af校dONLNd        R
^)"fect °dONLNd    ^ñj’(gñuser interactio…@°dONLNd    ^’j⁄)?
nˇt@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-4    )B    Handling ê)&Apple Events4^*¿
¯

^*x
¯4^*x
¯

à*ê
¯4â*ê
¯ ä*ä
˛

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNdu*às(É*    Handling >°dONLNd    usà‘)IApple EventsˇˇˇˇˇˇU˛(É

4
°dONLNdôl•r(¢l
Y@Ä°dONLNdôr•
) ou do not need to implement all $ °dONLNd8ô
•
Ã)ê.Apple events at once. If you want to begin by °dONLNdf¶l≤ (Ølsupporting only the rúÄ°dONLNd{¶ ≤·)^equir≥¿°dONLNdĶ·≤Ó)ed ∫¿°dONLNdɶÓ≤
W)Apple events, you must,Zapf Dingbats°dONLNdöºl√q(¬l
n
°dONLNdúπx≈¥)set bits in the ,
CourierOÄ°dONLNd¨πµ≈Ÿ)='SIZE'M@°dONLNd≤πŸ≈fl)$ rí@°dONLNd¥πfl≈˜)esour⁄Ä°dONLNdππ˜≈
Î)9ce to indicate that your application supports high-level °dONLNdÚ≈x—î(Œxevents°dONLNd˘⁄l·q(‡l
n
°dONLNd˚◊x„
ó)@include code to handle high-level events in your main event loop°dONLNd
<ÏlÛq(Úl
n
°dONLNd
>Èxıï)write r°dONLNd
EÈñı
)outines that handle the rÎ`°dONLNd
^È

ı
)kequir†°dONLNd
cÈ
ı
B)    ed events°dONLNd
m˛l
q(
l
n
°dONLNd
o˚x
Ÿ)install entries for the rß@°dONLNd
à˚Ÿ
)aequiræÄ°dONLNd
ç˚
˝)ed ≈Ä°dONLNd
ê˚˝

ó)#Apple events in your application’s b °dONLNd
≥˚
ò

–)õApple event °dONLNd
ø
x
∏(
xdispatch table °dONLNd
œ
l
$
q(
!l;The following sections explain how to perform these tasks: z‡°dONLNd


r
$
≥(
!
r“Accepting an φ°dONLNd

≥
$
Ú)AApple Event,”    Ä°dONLNd%

Û
$
ı)@
 °dONLNd&
%l
1∂(
.lwhich begins on p`°dONLNd6
%∑
1Œ)Kpage K@°dONLNd;
%œ
1‹)4-5ü °dONLNd>
%‹
1·), ü °dONLNd@
%·
1
O)“Installing Entries in the ±‡°dONLNd[
%
O
1
π)nApple Event Dispatch TÌ@°dONLNdq
%
∏
1
’)iables,”„‡°dONLNdx
%
÷
1
ˆ) which °dONLNd
2l
>ô(
;l
begins on û°dONLNdâ
2ô
>∞)-page x‡°dONLNdé
2±
>æ)4-7ÿ°dONLNdë
2æ
>÷), and 9‡°dONLNdó
2◊
>
7)“Handling the RequirL@°dONLNd´
2
7
>
D)`ed S@°dONLNdÆ
2
D
>
á)Apple Events,”≠ °dONLNdº
2
á
>
‘)C which begins on °dONLNdÕ
?l
KÉ(
Hlpage Z‡°dONLNd“
?Ñ
Kë)4-1" °dONLNd’
?ë
Kñ)
1" °dONLNd÷
?ñ
Kò)
.°dONLNdÿ
Ql
]r(
Zl
Tµ¿°dONLNdŸ
Qq
]|)o rp@°dONLNd‹
Q}
]ª)espond to the íÄ°dONLNdÍ
Qª
]
ø)>:Apple events sent by the Edition Manager in addition to th„ °dONLNd$
Q
ø
]
 (
Z
øe rÒ¿°dONLNd'
Q
 
]
Œ)
eª`°dONLNd(
Q
œ
]
·)quir    °dONLNd,
Q
‚
]
Ô)ed °dONLNd/
^l
j
Å(
gl@events, you must install entries for the Section Read, Section W@°dONLNdo
^
Å
j
ƒ(
g
Årite, Section ScrFÄ°dONLNdÄ
^
≈
j
Ë)D    oll, and °dONLNdâ
kl
ww(
tlCr\°dONLNdã
kw
w
5),eate Publisher events in your application’s Ä°dONLNd∑
k
5
w
Î)æ)Apple event dispatch table and write the °dONLNd‡
xl
Ñ}(
Ålcorr`°dONLNd‰
x~
Ñ
)"esponding handlers, as described iÒ¿°dONLNd
x

Ñ
)òn C °dONLNd
x

Ñ
P)
“Handling ‘Ä°dONLNd
x
P
Ñ
‰)1!Apple Events Sent by the Edition °dONLNd3
Öl
ë¿(
élManager” on page 3¿°dONLNdD
Ö¡
ë”)U4-20ᆰdONLNdH
Ö”
ë’)
.†°dONLNdI
Ö÷
ëÿ)
 °dONLNdK
ól
£r(
†l
Tµ¿°dONLNdL
óq
£|)o rp@°dONLNdO
ó}
£∏)espond to cor>@°dONLNd\
óπ
£
)<e and functional-arÄ°dONLNdo
ó

£
)Tea Ô¿°dONLNdr
ó

£
Ó)1Apple events, you must install entries and write °dONLNd£
§l
∞fl(
≠lhandlers for those events. H†°dONLNdæ
§‡
∞Ê)t
Y     °dONLNdø
§Ê
∞
I)ou must also make sur±°dONLNd‘
§
I
∞
P)ce ˙†°dONLNd÷
§
P
∞
c)that –¿°dONLNd€
§
d
∞
›)your application can locate °dONLNd˜
±l
Ω
(
∫l(Apple event objects with the aid of the ‘‡°dONLNd
±

Ω
Ä)¨Apple Event Manager r»¿°dONLNd4
±
Ä
Ω
Î)houtines described in the °dONLNdM
æl
 ·(
«lchapter “Resolving and Cr °dONLNdf
æ‚
 
;)veating Object Specifi    `°dONLNd{
æ
<
 
`)Zer Recorh°dONLNdÉ
æ
`
 
î)$ds.” These r» °dONLNdè
æ
î
 
ø)4
outines aråÄ°dONLNdô
æ
¿
 
Ÿ),e curr °dONLNdü
æ
⁄
 
Ú)ently °dONLNd•
Àl
◊
Δ(
‘lMavailable as the Object Support Library (OSL), which you must link with your °dONLNdÚ
ÿl
‰Ù*application when you build it. °dONLNd
Íl
ˆ*The ]`°dONLNd
Í
ˆ
ã);Apple Event Manager (excluding the OSL) is available only i| °dONLNdQ
Í
ã
ˆ
Ω(
Û
ãn System 7 °dONLNd\
˜lq(l
a°dONLNd]
˜q|)ndm °dONLNd_
˜})
 Ì °dONLNd`
˜í)later‘ °dONLNde
˜ìï)
 T °dONLNdf
˜ñª)versions_‡°dONLNdn
˜ª
)% of system softwar˜ °dONLNdÄ
˜

)Pe. Uà°dONLNdÑ
˜

8)se the l°dONLNdã
˜
9
c)Gestalti`°dONLNdí
˜
c
¥)* function with the °dONLNd•l(lgestaltAppleEventsAttrw¿°dONLNdª
â)Ñ# selector to determine whether the `°dONLNdfi
â
√)ôApple Event °dONLNdÍlè(lManage`°dONLNdêì)$
r°dONLNdÒîñ)
 í°dONLNdÚñù)is∑`°dONLNdÙùü)
 7`°dONLNdı†•)
a7`°dONLNdˆ•¬)vailabl`°dONLNd˝√ )e.h°dONLNdˇ Ë) In the ı@°dONLNdË
)responseÚ@°dONLNd

H)0
 parameterE‡°dONLNd
H
|)0, the bit defi«¿°dONLNd'
|
‘)4ned by the constant °dONLNd;l*
('lgestaltAppleEventsPresentv†°dONLNdT
*
6)ñ is set if the  @°dONLNdc
6*
Δ)4Apple Event Manager is availabl€Ä°dONLNdÇ
Δ*
Õ)êe.°dONLNdÖ5lAä(>lCONST°dONLNdå5êA
V)$!gestaltAppleEventsAttr  = 'evnt';°dONLNdπ5
hA
‘)ÿ{Gestalt selector}°dONLNdŒCêO
D(LêgestaltAppleEventsPresent = 0;°dONLNd¯C
hO
Ú)ÿ{if this bit is set, } °dONLNdQ
h]
Ï*{ then the Apple Eventw¿°dONLNd4Q
Ï]
Ú)Ñ
 w`°dONLNd5Q
Ú]
¯)
}°dONLNdE_
hk
Ï(h
h{ Manager is availablew¿°dONLNd[_
Ïk
Ú)Ñ
}°dONLNd]wlÉr(Äl
Tµ¿°dONLNd^wqÉ)o fi∏°dONLNdbwÉ˚)nd out which version of the Õ†°dONLNd~w˚É
‹)|2Apple Event Manager is available, you can use the °dONLNd∞Ñlê∫(çlAEManagerInfo{ °dONLNdΩÑ∫ê
)N function; for morS‡°dONLNdœÑ
ê
D)Ne informationX‡°dONLNd‹Ñ
Dê
F)<
,ÿ‡°dONLNd›Ñ
Fê
X) see © °dONLNd‚Ñ
Yê
p)page Ñ°dONLNdÁÑ
qê
à)4-104◊‡°dONLNdÏÑ
àê
ä)
.ˇ9 @ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡    4-5
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

kHr4lHr mäm

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\äk‹(gäAccepting an ∏÷°dONLNd\‹k
%)RApple Eventˇˇˇˇˇˇ€r(g
4
°dONLNdrä~ê({ä
Tµ¿°dONLNdrè~ÿ)o accept or send `°dONLNd,rŸ~
Ò)J@Apple events (or any other high-level events), you must set the °dONLNdläãû(àäapprI@°dONLNdpüãΔ)    opriate fl4†°dONLNdz«ã
6)(ags in your application’s ,
Couriert°dONLNdî
6ã
Z)o'SIZE'q¿°dONLNdö
Zã
`)$ r∂¿°dONLNdú
`ã
x)esourˇ°dONLNd°
xã
˛)ce and include code to handle °dONLNdøåäò
Ç(ïä9high-level events in your application’s main event loop. °dONLNd˘ûä™ê*
T∫¿°dONLNd˙û處)wo fl°dONLNdˇû¶™“)ags in the ˜@°dONLNd

û“™ˆ),'SIZE'ı°dONLNd
ûˆ™¸)$ r:°dONLNd
û˝™
)esourÇ@°dONLNd
û
™
Ω)%ce determine whether an application rÜ¿°dONLNd
<û
Ω™)®eceives high-level °dONLNd
O´ä∑´(¥äevents: ,Zapf Dingbats°dONLNd
X¡ä»è*
n
°dONLNd
Zæñ ©)The ª¿°dONLNd
^æ© 
')isHighLevelEventAware≥‡°dONLNd
sæ
' 
/)~ fl@†°dONLNd
væ
0 
€)    (ag must be set for your application to r≤†°dONLNd
ûæ
€ )´eceive any °dONLNd
© ñ÷‰(”ñhigh-level events.°dONLNd
ºfläÊè(Âä
n
°dONLNd
æ‹ñË©)The ª¿°dONLNd
¬‹©Ë
-)localAndRemoteHLEvents≥Ä°dONLNd
ÿ‹
-Ë
5)Ñ fl@@°dONLNd
€‹
6Ë
·)    (ag must be set for your application to r≤@°dONLNd‹
·Ë
˛)´eceive °dONLNd
ËñÙˇ(Òñhigh-level events sent fr5‡°dONLNd#Ë
Ù
®)j#om another computer on the network.°dONLNdG˘ä
 (
äNote that in or¿°dONLNdV˘À

F)Ader for your application to r`‡°dONLNds˘
F

t){
espond to %¿°dONLNd}˘
t

Ã).Apple events sent fr‡¿°dONLNdë˘
Ã

‡)Xom ro@°dONLNdï˘
·

˛)emote °dONLNdõ
ä
(
äVcomputers, the user of your application must also allow network users to link to your °dONLNdÒ
ä

Œ*Kapplication. The user does this by selecting your application in the Finder>¿°dONLNd<

Œ

˝(

Œ, choosing °dONLNdG
 ä
,∂(
)ä
Sharing freÄ°dONLNdQ
 ∂
,
Q),#om the File menu, and clicking the !`°dONLNdt
 
Q
,
ù)õAllow Remote Pr!†°dONLNdÉ
 
ù
,)Logram Linking checkbox. °dONLNdõ
-ä
9
(
6ä"If the user has not yet started pr#¿°dONLNdΩ
-

9
«)ç%ogram linking, the Sharing command of©¿°dONLNd‚
-
«
9)∞fers to display °dONLNdÚ
:ä
FÒ(
Cäthe Sharing Setup contr=Ä°dONLNd    
:Ú
F
è)h&ol panel so that the user can start prƒ`°dONLNd/
:
è
F)ùogram linking. The user must °dONLNdL
Gä
SŒ(
Päalso authorize r‡°dONLNd\
Gœ
S
)Eemote users for prtÄ°dONLNdn
G

S
¥)P!ogram linking by using the Users 8Ä°dONLNdè
G
µ
S
º)ñ
&ˇ¿°dONLNdê
G
º
S
 ) Gr‡°dONLNdì
G
 
S
˘)
oups contr‡ °dONLNdù
G
˘
S)/ol °dONLNd†
Tä
`±(
]ä    panel. Pr‘ °dONLNd©
T±
`
¢)'6ogram linking and setting up authenticated sessions ar醰dONLNdfl
T
£
`
Û)Úe described in the °dONLNdÚ
aä
mº(
jächapter “Pr°dONLNd˝
aΩ
mÛ)3ogram-to-Pr
Ä°dONLNd
aÛ
m
g)6ogram Communications T¿°dONLNd
a
f
m
¢)soolbox” in thiŒ¿°dONLNd,
a
¢
m
¡)<s book.°dONLNd4
sä

(
|ä"For a complete description of the y@°dONLNdV
s


B)î'SIZE'w°dONLNd\
s
B

H)$ rº°dONLNd^
s
H

`)esour@°dONLNdc
s
a

≥)ce, see the chapter Æ °dONLNdw
s
≥

æ)R“E…‡°dONLNdy
s
æ
)vent Manager” in °dONLNdä
Ää
å
(
âäInside Macintosh: Macintosh T“Ä°dONLNdß
Ä

å
N)}oolbox Essentials.Ä°dONLNdπ
Ä
O
å
Q)H
 °dONLNdª
íä
û
Q(
õä-Apple events (and other high-level events) ar)¿°dONLNdË
í
R
û
y)»    e identifiJ°dONLNdÚ
í
y
û
Ê)'ed by a message class of °dONLNd
üä
´‰(
®äkHighLevelEventz`°dONLNd
ü‰
´
)Z in the ëÄ°dONLNd"
ü

´
)whatê°dONLNd&
ü

´
) f4`°dONLNd(
ü
 
´
m)ield of the event r£Ä°dONLNd;
ü
m
´
)Mecor‡°dONLNd?
ü
Ä
´
ã)d. °dONLNdB
ü
ã
´
ë)
YΔÄ°dONLNdC
ü
ê
´
“)ou can test the ÌÄ°dONLNdS
ü
“
´
Í)BwhatÏ°dONLNdW
ü
Í
´
Ô) fê`°dONLNdY
ü

´)ield of °dONLNda
¨ä
∏π(
µäthe event ro†°dONLNdl
¨π
∏À)/ecor‰°dONLNdp
¨À
∏
ª)7d to determine whether the event is a high-level event.°dONLNd®
æä
 ∏(
«äListing 4-1 @°dONLNd≥
æπ
 
)/ is an example of a pr!‡°dONLNd…
æ

 
5)^ocedurπ °dONLNdœ
æ
5
 
`)e called fr¬°dONLNd⁄
æ
`
 
˚)+"om an application’s main event looΔ`°dONLNd¸
æ
˚
 )õp to °dONLNd

Àä
׏(
‘ä
hQ`°dONLNd
Àê
◊£)andl&‡°dONLNd
ˤ
◊∞)e e: °dONLNd    
˰
◊
g)*vents, including high-level events. The pr~`°dONLNd3
À
g
◊
Ö)∑ocedur†°dONLNd9
À
Ü
◊)e determines the type of event °dONLNdX
ÿä
‰ç(
·ä
rE°dONLNdY
ÿé
‰
) eceived and then calls another r2@°dONLNdy
ÿ

‰
~)åoutine to take the apprn@°dONLNdê
ÿ
~
‰
Ω)dopriate action.

H4H"H_

ˇ·ˇ‚7^
    °dONLNd†
˝ä∂(äListing 4-1°dONLNd¨
˝Œ‘)D
A0°dONLNd≠
˝‘÷)
 ÇP°dONLNdÆ
˝÷˘)DoEventL¿°dONLNdµ
˝¸
')&
 procedure
°dONLNd¡ä#
n( ä&PROCEDURE DoEvent (event: EventRecord)q¿°dONLNdÁ
n#
t)‰
;°dONLNdÈ%ä1ê(.ä
B†°dONLNdÍ%ê1®)EGIN°dONLNdÙ3ú?
+CASE event.what OF°dONLNd3
>?
Ï)¢{determine the type of event}°dONLNd/AÆMÍ(JÆ
mouseDown:°dONLNd=O¿[
8+DoMouseDown (event);°dONLNdT]Æi¥(fÆ
.°dONLNdXkÆw
n* . {handle other kinds of events}°dONLNd{yÆÖ¥*
.°dONLNdáÆì
⁄*2{handle high-level events, including Apple events}°dONLNd¥ïÆ°
*kHighLevelEventz`°dONLNd√ï
°
)Z: Dy@°dONLNdΔï
°
™)oHighLevelEvent (event);°dONLNd‡£úØ¥(¨úEND;°dONLNd±äΩ®(∫äEND; ˇV@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-6    )B    Handling ê)&Apple Events4^*¿
¯
°dONLNd\lhö(elListing 4-2 @°dONLNd\õhÁ)/ is an example of ⁄¿°dONLNd\ÁhÙ)La p\‡°dONLNd \ıh¯)
r!‡°dONLNd!\˘h
)ocedurπ °dONLNd'\
h
W)e that handles `°dONLNd6\
Xh
n)Aboth 8‡°dONLNd;\
nh
µ)Apple events an°dONLNdJ\
∂h
¡)Hd t °dONLNdM\
¡h
Œ)he °dONLNdPilu’(rlhigh-level event identifi@°dONLNdii÷u
3)jed by the event class ,
CourierdONLNdi
3u
±)]mySpecialHLEventClassç¿°dONLNdîi
±u
Ú)~ and the event °dONLNd£vlÇy(lID ¿°dONLNd¶vzÇÊ)mySpecialHLEventID°dONLNd∏vÊÇ
ü)l+. Note that, in most cases, you should use º@°dONLNd„v
ûÇ
Ê)∏Apple events to °dONLNdÛÉlè
(ål%communicate with other applications. 
    °dONLNd
®l≥ò*$Listing 4-2°dONLNd
%®∞≥∂)D
A0°dONLNd
&®∂≥∏)
 ÇP°dONLNd
'®∏≥
)DoHighLevelEvent„P°dONLNd
7®
≥
m)V procedure for handling j†°dONLNd
O®
m≥
ı)_"Apple events and other high-level °dONLNd
q≤∞Ω (∫∞events
°dONLNd
x l÷
Ü(”l/PROCEDURE DoHighLevelEvent (event: EventRecord)n`°dONLNd
ß 
Ü÷
å(”
Ü
;°dONLNd
©ÿl‰r(·l
V†°dONLNd
™ÿr‰~)AR°dONLNd
ÆÊ~ÚÃ+myErr: OSErr;°dONLNd
ºÙl
ä(˝lBEGIN°dONLNd
√
~

»+7IF (event.message = LongInt(mySpecialHLEventClass)) AND°dONLNd
˝
ê

Œ+5(LongInt(event.where) = LongInt(mySpecialHLEventID)) °dONLNd4
~
*ñ(
'~THEN°dONLNd;
,ê
8
∞+0{it's a high-level event that doesn't use AEIMP}°dONLNdn
:ê
F
t*&myErr := HandleMySpecialHLEvent(event)°dONLNdñ
H~
Tñ(
Q~ELSE°dONLNdù
Vê
b
»+4{otherwise, assume that the event is an Apple event}°dONLNd‘
dê
p
h*$myErr := AEProcessAppleEvent(event);°dONLNd¸
Ä~
å
(
â~{check and handle error}°dONLNd
é~
ö
b*&IF myErr <> noErr THEN DoError(myErr);°dONLNd=
úl
®Ñ(
•lEND;°dONLNdB
¥l
¿
ì*EIf your application accepts high-level events that do not follow the Ï °dONLNdá
¥
ì
¿
Õ(
Ω
ìApple Event °dONLNdì
¡l
Õã(
 lInterpru†°dONLNdö
¡ã
Õ‡)ocess Messaging Pr˛Ä°dONLNd¨
¡‡
Õ
Â)U:otocol (AEIMP), you must dispatch these high-level events °dONLNdÊ
Œl
ڃ(
◊lbefor_†°dONLNdÎ
΃
⁄™)
e calling ≥ °dONLNdı
Ϊ
⁄
)'AEProcessAppleEvent¨°dONLNd
Œ

⁄
')r. T·¿°dONLNd
Œ
&
⁄
M)
    o dispatcÕ °dONLNd
Œ
N
⁄
\)(h hÔ‡°dONLNd
Œ
\
⁄
ù)igh-level eventd °dONLNd&
Œ
û
⁄
¢)B
s° °dONLNd'
Œ
¢
⁄
æ) that d°dONLNd.
Œ
ø
⁄
Ã)o nŸ‡°dONLNd1
Œ
Ã
⁄
ˆ)
ot follow °dONLNd;
€l
Áå(
‰lAEIMPˆ`°dONLNd@
ۋ
Á
◊)N, you should check the event class, the event ID, or both for each event to se´Ä°dONLNdé
€
ÿ
Á
fl(
‰
ÿe °dONLNdê
Ël
Ùò(
Òl    whether yQ °dONLNdô
Ëô
Ù
)-our application can handle©`°dONLNd≥
Ë

Ù
<)v the event.T°dONLNdæ
Ë
=
Ù
?).
 °dONLNd¿
˙lâ(lAfter rfi¿°dONLNd«
˙â
8))eceiving a high-level event (and, if apprE‡°dONLNd
˙
9
)∞opriate, checkinh‡°dONLNd
˙

è)Fg wœ°dONLNd
˙
è
¿)hether it is 
 °dONLNd
˙
¡
»)2a °dONLNdlq(l
hQ`°dONLNdrò)    igh-level¯`°dONLNdòö)&
 x`°dONLNdõÛ)event other than an c@°dONLNd1Û
Ã)X3Apple event), your application typically calls the °dONLNddl fi(lAEProcessAppleEventx‡°dONLNdwfi 
)r function. The B‡°dONLNdÜ
 
ê)@AEProcessAppleEvent;¿°dONLNdô
ê 
Ó)r function determines °dONLNdÆ!l-ù(*lthe type of †°dONLNd∫!ù-Ÿ)1Apple event ru`°dONLNd«!⁄-
N)=eceived, gets the event buf$†°dONLNd‚!
O-
)u%fer that contains the parameters and °dONLNd.l:¥(7lattributes of the ‡°dONLNd.¥:
:)HApple event, and calls the corr0Ä°dONLNd8.
;:
l)á
esponding `°dONLNdB.
l:
√)1Apple event handleA†°dONLNdT.
√:
Ã)Wr iú†°dONLNdW.
Ã:
Î)    n your °dONLNd^;lG†(Dlapplication.°dONLNdkMlYr*
Y@Ä°dONLNdlMrY´)ou should pr`°dONLNdxM´YΔ)9ovide |‡°dONLNd~MΔY”)an o‡°dONLNdÅM”Y
)Apple event h°dONLNdéM
Y
*)?andle´ °dONLNdìM
*Y
3)r fq†°dONLNdñM
4Y
V)
or each ܆°dONLNdûM
VY
Ó)""Apple event that your application °dONLNd¿Zlfì(clsupports؇°dONLNd»Zìf’)'. This handler i‡°dONLNdÿZ÷f‡)Cs rdONLNd€Z‡f
á)
&esponsible for performing the action rõ°dONLNd
Z
áf
œ)ßequested by the °dONLNdglsá(plApple˝Ä°dONLNdgásâ)
 }Ä°dONLNdgäsü)evenà`°dONLNdgüs©)t aJ¿°dONLNdg™s
)nd if necessary can rK`°dONLNd3g
s
S)Zeturn data in the r‹¿°dONLNdFg
Ss
h)Oeply A†°dONLNdKg
is
§)Apple event. 

≤*πß4≥*πß"¥*_ˇ@r@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡    4-7
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähˆ(eäIf the client application r™°dONLNd\ˆh
$)lequests a r^‡°dONLNd&\
%h
8)/eplyÜ`°dONLNd*\
7h
L), the Ö`°dONLNd0\
Lh
¸)&Apple Event Manager passes a default rÁ °dONLNdV\
¸h)∞eply °dONLNd[iäu
(räApple event to your handler¶¿°dONLNdvi
u
†)}&. If the client application does not rÒ‡°dONLNdúi
†u
 )ô
equest a ri¿°dONLNd¶i
Àu
fi)+eplyë@°dONLNd™i
›u
Ú), the ê@°dONLNd∞i
Úu)Apple °dONLNd∂väÇ
>(ä(Event Manager passes a null descriptor rº†°dONLNdfiv
>Ç
P)¥ecor1°dONLNd‚v
QÇ
ó)d (a descriptor rˇ‡°dONLNdÛv
óÇ
©)Fecort@°dONLNd˜v
™Ç)d of descriptor type ,
Courier°dONLNd
Éäè∫(åätypeNull}°dONLNd
É∫èœ)0 and j °dONLNd
É–è›)a d‡°dONLNd
Éfiè
)
ata handle8¿°dONLNd
&É
è
R). whose value is b°dONLNd
6É
Rè
d)FNIL`‡°dONLNd
9É
dè)') to your handler instead of a default °dONLNd
`êäúç(ôä
rE°dONLNd
aêéú£)eply ©‡°dONLNd
fê£ú€)Apple event.°dONLNd
s¢äÆÊ(´äAfter your handler fià°dONLNd
à¢ÊÆ
)\    nishes prù‡°dONLNd
ë¢
Æ
F)(ocessing the è °dONLNd
û¢
FÆ)8+Apple event and adds any parameters to the °dONLNd
…Øäªç(∏ä
rE°dONLNd
 Ø骣)eply ©‡°dONLNd
œØ£ª
)Apple event, it must r>‡°dONLNd
ÂØ
ª
))a    eturn a r€°dONLNd
ÓØ
)ª
c)%esult code to Ä°dONLNd
¸Ø
dª
÷);AEProcessAppleEvent`°dONLNdØ
ֻ
Ù)r    . If the °dONLNdºä»¢(≈äclientû`°dONLNdº¢»§)
 `°dONLNdº•»
!)application is waiting for a rΔ@°dONLNd=º
!»
4)|eplyÌ¿°dONLNdAº
3»
H), the Ï¿°dONLNdGº
H»
∞)Apple Event Manager r‡†°dONLNd\º
∞»
‚)heturns the ró °dONLNdhº
„»
¯)3eply °dONLNdm…ä’¯(“äApple event to the client.

˙H

4˚H

 ¸ä¸

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdàÎä˙
*$Installing Entries in the …,°dONLNd¢Î
˙
ú)åApple Event Dispatch MÚ°dONLNd∑Î
ù˙
•)á
T* °dONLNd∏Î
§˙
ƒ)ablesˇˇˇˇˇˇ€r)j
4
°dONLNdø

ä
ˆ(

äWhen your application rʆ°dONLNd÷

ˆ

%)leceives an Ú`°dONLNd·


%

Ç)/Apple event, use the (@°dONLNdˆ


É

ı)^AEProcessAppleEvent! °dONLNd    


ı

˜)r
 °dONLNd

ä
¿(
äfunction to r °dONLNd
¡

)7etrieve the data bufú °dONLNd+



})Ufer of the event and to r
@°dONLNdD

~

§)h    oute the ‡°dONLNdM

§

¯)&Apple event to the °dONLNd`
ä
'û(
$äapprI@°dONLNdd
ü
'¿)opriate …Ä°dONLNdl
¿
'
w)!)Apple event handler in your application. ∏¿°dONLNdï

w
'
})∑
Yy@°dONLNdñ

}
'
¯)our application supplies an °dONLNd≤
(ä
4•(
1äApple˝Ä°dONLNd∑
(•
4ß)
 }Ä°dONLNd∏
(®
4
4) event dispatch table to map the °dONLNdÿ
(
5
4
Ú)ç*Apple events your application supports to °dONLNd
5ä
Aó(
>äthe]`°dONLNd
5ò
Aö)
 °dONLNd
5ö
A
)Apple event handlers pr1°dONLNd
5

A
Ä)lovided by your application.°dONLNd9
Gä
Sê(
Pä
Tµ¿°dONLNd:
Gè
S
2)(o install entries in your application’s     °dONLNdb
G
3
S
–)§$Apple event dispatch table, use the °dONLNdÜ
Tä
`
(
]äAEInstallEventHandlerx °dONLNdõ
T

`
4)~ function. ÿ¿°dONLNd¶
T
4
`
:),
Yô@°dONLNdß
T
:
`
·)*ou usually install entries for all of the _°dONLNd—
T
·
`
˛)ßApple °dONLNd◊
aä
m
ë(
jä=events that your application accepts into your application’s °dONLNd
a
í
m(
j
íApple event dispatch table. °dONLNd1
sä
ê(
|ä
Tµ¿°dONLNd2
sè
¡)o install an ( °dONLNd?
s¬
…)3
AÔ`°dONLNd@
s…

)pple event handlec`°dONLNdQ
s


0)Pr in yû‡°dONLNdW
s
0

A)our /¿°dONLNd[
s
B

≥)Apple event dispatch tablÙ °dONLNdt
s
≥

Ì)qe, you must sa°dONLNdÅ
s
Ó
    );pecify,Zapf Dingbats°dONLNdà
âä
êè(
èä
n
°dONLNdä
Üñ
íÙ)the event class of the E†°dONLNd°
ÜÙ
í
*)^Apple event°dONLNd≠
õä
¢è(
°ä
n
°dONLNdØ
òñ
§Í)the event ID of the é¿°dONLNd√
òÍ
§
 )TApple event°dONLNdœ
≠ä
¥è(
≥ä
n
°dONLNd—
™ñ
∂ª)the addrŸ‡°dONLNdŸ
™ª
∂Ê)%ess of the ‡°dONLNd‰
™Ê
∂
c)+Apple event handler for the Œ¿°dONLNd
™
c
∂
ô)}Apple event°dONLNd
øä
Δè(
Ŋ
n
°dONLNd
ºñ
ȡ)a ršdONLNd
º°
»±)eferq °dONLNd
º≤
»Ì)ence constant°dONLNd#
Õä
Ÿê(
֊
Y@Ä°dONLNd$
Õê
Ÿß)ou pr@°dONLNd)
Õ®
Ÿ
()ovide this information to the ˜Ä°dONLNdG
Õ
(
Ÿ
¶)ÄAEInstallEventHandlerÔ†°dONLNd\
Õ
¶
Ÿ)~ function. In addition, °dONLNdt
ڊ
ʪ(
„äyou indicat|@°dONLNd
ڼ
ÊÀ)2e w‡°dONLNdÇ
⁄Ã
Ê
ø)7hether the entry should be added to your application’s T†°dONLNdπ
⁄
ø
Ê
˜)ÛApple event °dONLNd≈
Áä
Û÷(
ädispatch table or ´`°dONLNd◊
Á÷
Û·)Lto „@°dONLNd⁄
Á·
Û
)the system K`°dONLNdÂ
Á

Û
é)2Apple event dispatch table. °dONLNd
˘äù(äThe 
ª¿°dONLNd
˘ù
9)!system Apple event dispatch tableS@°dONLNd'
˘
:
ˆ)ù- is a table in the system heap that contains °dONLNdTä´(äsystem ä¿°dONLNd[´
Z)!%Apple event handlers—handlers that ar∞‡°dONLNdÄ
Z
Ô)Ø$e available to all applications and °dONLNd§äì(äprG °dONLNd¶î∫)
    ocesses r’¿°dONLNdØ∫
>)&unning on the same computerÀ†°dONLNd 
>
›)Ñ%. The handlers in your application’s º`°dONLNdÔ
›
˙)üApple °dONLNdı ä,Ó()äevent dispatch table arUÄ°dONLNd Ó,
ò)d)e available only to your application. If ≠†°dONLNd5 
ò,
)™AEProcessAppleEvent¶Ä°dONLNdH 
,)r
 °dONLNdI-ä9∞(6äcannot fi◊†°dONLNdR-∞9

)&nd a handler for the ‚‡°dONLNdg-

9
†)Z"Apple event in your application’s BÄ°dONLNdâ-
°9
Ÿ)óApple event °dONLNdï:äF≤(Cä    dispatch «@°dONLNdû:≤F
,)(table, it looks in the system Ø`°dONLNdº:
,F
Ù)z.Apple event dispatch table for a handler (see °dONLNdÎGäSß(Pä“How øÄ°dONLNdGßS
#)Apple Event Dispatching W#°dONLNd        G
#S
c)|orks” on page y°dONLNd    G
cS
p)@4-9Ç°dONLNd    G
pS
‚) for details). If it doesn’t fiÔ°dONLNd    9G
‚S
˜)rnd a °dONLNd    >Tä`¯(]ähandler for the event, it rπÄ°dONLNd    YT¯`
&)neturns the ´°dONLNd    dT
'`
ü)/errAEEventNotHandled£Ä°dONLNd    xT
ü`
•)x rËÄ°dONLNd    zT
•`
÷)esult code. °dONLNd    áfär
#(oä#If you add a handler to the system ¯¿°dONLNd    ™f
#r
Õ)ô&Apple event dispatch table, the handleT†°dONLNd    –f
Œr
ÿ)´r s@°dONLNd    ”f
Ÿr
˘)hould rõ`°dONLNd    ⁄f
˘r) eside °dONLNd    ‡sä¸(|äin the system heap. If therÚ °dONLNd    ˚s¸
#)r    e was alr˝ °dONLNd
s
#
ü)'eady an entry in the system ƒ°dONLNd
 s
ü)|Apple event dispatch °dONLNd
5Ääå
a(âä4table for the same event class and event ID, it is r˚ °dONLNd
iÄ
aå
˝)◊$eplaced unless you chain it to your °dONLNd
ççäô…(ñäsystem handleY†°dONLNd
öç ôÕ)@
r釰dONLNd
õçÕô„). See ·‡°dONLNd
°ç„ôÛ)“CrΩ‡°dONLNd
§çÛô
d)eating and Managing the ùÄ°dONLNd
ºç
dô
Œ)qApple Event Dispatch Tÿ‡°dONLNd
“ç
Õô
¯)i
ables” on °dONLNd
‹ö䶰(£äpage Z‡°dONLNd
·ö¢¶¥)4-61Æ¿°dONLNd
Âö¥¶Â) for details.ˇ∏@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-8    )B    Handling ê)&Apple Events4^*¿
¯

j*p
¯4j*p
¯ klk
¯

ˇ·ˇ‚7^°dONLNd\ljo(fl
I’Ä°dONLNd
\oj
 )#nstalling Entries for the Required â°dONLNd$\
 j
f)±Apple Eventsˇˇˇˇˇˇ‘@)—
4
°dONLNd2pl|ö(ylListing 4-3 @°dONLNd=põ|
D)/) illustrates how to add entries for the rF °dONLNdfp
D|
[)©equir]`°dONLNdkp
[|
h)ed d`°dONLNdnp
h|
«)Apple events to your °dONLNdÉ}lâß(Ülapplication’s \¿°dONLNdë}ßâ
 );Apple event dispatch table.
    °dONLNd≠¢l≠ò(™lListing 4-3°dONLNdπ¢∞≠
+)D Adding entries for the required à°dONLNdŸ¢
+≠
•){Apple events to an application’i`°dONLNd¯¢
•≠
¨)zs Í°dONLNd˙¢
´≠
›)Apple event °dONLNd
¨∞∑Á(¥∞dispatch table,
Courier
°dONLNd
ƒl–
å(Õl0myErr := AEInstallEventHandler(kCoreEventClass, °dONLNd
P“
 fi
&+¥
 †°dONLNd
Q“
&fi
û)kAEOpenApplication, °dONLNd
p‡
 Ï
&(È
 
 †°dONLNd
q‡
&Ï
b)
@MyHandleO{‡°dONLNd
{‡
bÏ
z)<App,z`°dONLNd
‡
zÏ
º) 0, FALSE);°dONLNd
ãÓl˙
P(˜l&IF myErr <> noErr THEN DoError(myErr);°dONLNd
≤¸l

Ä*.myErr := AEInstallEventHandler(kCoreEventClassn¿°dONLNd
‡¸
Ä

å(

Ä, °dONLNd
Ì


 

&(

 
 †°dONLNd
Ó


&

,)
k@°dONLNd
Ô


,

Ü)AEOpenDocumentsy†°dONLNd
˛


Ü

í)Z, °dONLNd

 
$
&(
!
 
 †°dONLNd

&
$
Ä)@MyHandleODoc,0z°dONLNd

Ä
$
∂)Z    , FALSE);°dONLNd%
&l
2
P(
/l&IF myErr <> noErr THEN DoError(myErr);°dONLNdL
4l
@
å*0myErr := AEInstallEventHandler(kCoreEventClass, °dONLNdá
B
 
N
&+¥
 †°dONLNdà
B
&
N
ò)kAEPrintDocuments, °dONLNd¶
P
 
\
&(
Y
 
 †°dONLNdß
P
&
\
b)
@MyHandleP{‡°dONLNd±
P
b
\
z)<Doc,z`°dONLNdµ
P
z
\
º) 0, FALSE);°dONLNd¡
^l
j
P(
gl&IF myErr <> noErr THEN DoError(myErr);°dONLNdË
ll
x
Ü*/myErr := AEInstallEventHandler(kCoreEventClass,°dONLNd"
z
 
Ü
&+¥
 †°dONLNd#
z
&
Ü
í)kAEQuitApplicationx‡°dONLNd5
z
í
Ü
ò)l
,°dONLNdA
à
 
î
&(
ë
 
 †°dONLNdB
à
&
î
Ä)@MyHandleQuit, z°dONLNdQ
à
Ä
î
¬)Z0, FALSE); °dONLNd]
ñl
¢
\(
ül(IF myErr <> noErr THEN DoError(myErr);  °dONLNdÜ
Æl
∫°*The code in @†°dONLNdí
Æ¢
∫–)6Listing 4-3‡‡°dONLNdù
Æ–
∫⁄). crñ °dONLNd†
Æ€
∫
I)eates entries for all four r¸†°dONLNdº
Æ
I
∫
`)nequir‡°dONLNd¡
Æ
a
∫
n)ed ‡°dONLNdƒ
Æ
n
∫
Δ)Apple events in the [`°dONLNdÿ
Æ
Δ
∫
„)XApple °dONLNdfi
ªl
«
d(
ƒl9event dispatch table. (For examples of handlers that corr°dONLNd
ª
d
«
fi)¯espond to these entries, see °dONLNd4
»l
‘Ã(
—l“Handling the Requirí`°dONLNdH
»Ã
‘Ÿ)`ed ô`°dONLNdK
»Ÿ
‘
)Apple Events,”Û@°dONLNdY
»

‘
i)C which begins on c†°dONLNdj
»
j
‘
Å)Npage >Ä°dONLNdo
»
Ç
‘
è)4-1¿°dONLNdr
»
è
‘
î)
1¿°dONLNds
»
î
‘
µ).) The fi¢ °dONLNd|
»
µ
‘
‹)!
rst entry °dONLNdÜ
’l
·t(
filcrµ@°dONLNdà
’t
·Ó)eates an entry for the Open ¨`°dONLNd§
’Ó
·
Ô)z;Application event. The entry indicates the event class and °dONLNdfl
‚l
ÓÀ(
Îlevent ID of the Open *`°dONLNdÙ
‚À
Ó
l)_$Application event, supplies the addro`°dONLNd
‚
l
Ó
À)°ess of the handler for °dONLNd/
Ôl
˚}(
¯lthat÷ °dONLNd3
Ô}
˚)
 V °dONLNd4
ÔÄ
˚Õ)event, and specifi~†°dONLNdF
ÔÕ
˚
)Mes 0 as the rd†°dONLNdS
Ô

˚
)3efer¿°dONLNdW
Ô

˚
Q)ence constant. °dONLNdg
l(
lThe ]`°dONLNdk

)Apple Event Manager passes thel`°dONLNdâ


)ë r±`°dONLNdã


&)efer]Ä°dONLNdè

'
_)ence constan∫@°dONLNdõ

_
h)8t tø°dONLNdû

h
•)    o your handle£`°dONLNd´

¶
±)>r efl†°dONLNdÆ

±
)ach time your °dONLNdºlπ(lhandler is called. 
@°dONLNdœ∫¿)N
Y¡¿°dONLNd–ø
?)our application can use this rµ`°dONLNdÓ
?
O)ÄeferaÄ°dONLNdÚ
P
‚)"ence constant for any purpose. If °dONLNdl'
($l"your application doesn’t use the rÿ@°dONLNd6
'
)îeferÑ`°dONLNd:
'
§)#ence constant, use 0 as the value. °dONLNd^-l9‹(6lThe last parameter to the I¿°dONLNdx-›9
[)qAEInstallEventHandlerA‡°dONLNdç-
[9
Í)~" function is a Boolean value that °dONLNdØ:lF
V(Cl4determines whether the entry is added to the system Ÿ °dONLNd„:
VF
Ê)Í!Apple event dispatch table or to °dONLNdGlSæ(Plyour application’s € °dONLNdGæS
?)RApple event dispatch table. Tû‡°dONLNd4G
?S
‚)Å&o add the entry to your application’s °dONLNdZTl`˘(]l Apple event dispatch table, use õ¿°dONLNdzT˘`
)çFALSEô‡°dONLNdT
`
ú) as the value of this parameterÈ¿°dONLNdûT
õ`
fi)Ñ. If you specify °dONLNdØalmÑ(jlTRUE~Ä°dONLNd≥aÑm
)!, the entry is added to the syste߆°dONLNd‘a
m
)âm ù@°dONLNd÷a
m
)
AdÄ°dONLNd◊a
 m
È)-pple event dispatch table. The code shown in °dONLNdnlzö(wlListing 4-3 @°dONLNdnõz
,)/# adds entries to the application’s E¿°dONLNd2n
,z
•)ëApple event dispatch table.

¨*≥ß4≠*≥ß"Æ*_ˇ46@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡    4-9
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

jHp4jHp käk

ˇ·ˇ‚7^°dONLNd\äjˆ(fäInstalling Entries for ÑÄ°dONLNd\ˆj
)lApplÜ¿°dONLNd\
j
&)e Evâ°dONLNd\
&j
6)ent6°dONLNd"\
7j
O)s Se8@°dONLNd&\
Oj
◊)nt by the Edition Managerˇˇˇˇˇˇ‘@)¿
4
°dONLNdApä|ç(yä
IfiÄ°dONLNdBpç|
c)/f your application supports the Edition Manager[°dONLNdqp
c|)÷&, you should also add entries to your °dONLNdó}äâ≈(Üäapplication’s \¿°dONLNd•}≈â
]);#Apple event dispatch table for the •¿°dONLNd»}
]â
˘)ò#Apple events that your application °dONLNdÎääñç(ìä
rE°dONLNdÏäéñ∑)
eceives frv†°dONLNdˆä∑ñ
"))om the Edition ManagerɆ°dONLNd
ä
"ñ
')k. Ɇ°dONLNd
ä
'ñ
U)Listing 4-4#‡°dONLNd
ä
Vñ
Â)/  shows how to add these entries.
    °dONLNd
:Øä∫∂(∑äListing 4-4°dONLNd
FØŒ∫
)DAdding entries for P°dONLNd
YØ
∫)I;Apple events sent by the Edition Manager to an application’n°dONLNd
îØ∫
)Ïs °dONLNd
ñπŒƒ
7(¡ŒApple event dispatch table,
Courier
°dONLNd
±—ä›
»(⁄ä5myErr := AEInstallEventHandler(sectionEventMsgClass, °dONLNd
Òfl
>Î
D+¥
 †°dONLNd
Úfl
DÎ
∞)sectionReadMsgID, °dONLNdÌ
>˘
D(ˆ
>
 †°dONLNdÌ
D˘
Ê)@MyHandleSectionReadEvent, °dONLNd6˚
>

D(

>
 †°dONLNd7˚
D

Ä)
0, FALSE);°dONLNdB
    ä

n(
ä&IF myErr <> noErr THEN DoError(myErr);°dONLNdi
ä
#
»*5myErr := AEInstallEventHandler(sectionEventMsgClass, °dONLNd©
%
>
1
D+¥
 †°dONLNd™
%
D
1
∂)sectionWriteMsgID, °dONLNd»
3
>
?
D(
<
>
 †°dONLNd…
3
D
?
Ï)@MyHandleSectionWriteEvent, °dONLNd
A
>
M
D(
J
>
 †°dONLNdÒ
A
D
M
Ä)
0, FALSE);°dONLNd¸
Oä
[
n(
Xä&IF myErr <> noErr THEN DoError(myErr);°dONLNd#
]ä
i
»*5myErr := AEInstallEventHandler(sectionEventMsgClass, °dONLNd_
kˆ
w
+l  °dONLNde
k
>
w
D)H
 †°dONLNdf
k
D
w
º)sectionScrollMsgID, °dONLNdÖ
y
>
Ö
Ú(
Ç
> @MyHandleSectionScrollEvent, °dONLNdÆ
á
>
ì
D*
 †°dONLNdØ
á
D
ì
Ä)
0, FALSE);°dONLNd∫
ïä
°
n(
ûä&IF myErr <> noErr THEN DoError(myErr);°dONLNd·
≠ä
πõ*See ”°dONLNdÂ
≠õ
πÃ)
“Handling d`°dONLNdÔ
≠Õ
π
∂)22Apple Events Sent by the Edition Manager” on page ¿°dONLNd!
≠
∑
π
…)Í4-20h†°dONLNd%
≠
…
π
Î)     for the °dONLNd.
∫ä
Δ
Ö(
√ä9parameters associated with these events. See the chapter Ú°dONLNdg
∫
Ö
Δ
ê)˚“E¿°dONLNdi
∫
ë
Δ)dition Manager” in this book °dONLNdÜ
«ä
”
e(
–ä0for information on how your application should reÄ°dONLNd∂
«
e
”
£)€espond to the á¿°dONLNdƒ
«
£
”)>Apple events sent by the °dONLNd›
‘ä
‡‘(
›äEdition Managerf °dONLNdÏ
‘‘
‡÷)J
.Ê °dONLNdÌ
‘÷
‡ÿ)
 


˛H4
ˇH ä

ˇ·ˇ‚7^°dONLNdÔ
Òä
ˇ•(
˚äHow ,°dONLNdÛ
Ò•
ˇ
6)Apple Event Dispatching WR¿°dONLNd
Ò
6
ˇ
L)ëorksˇˇˇˇˇˇ‘@)Ÿ
4
°dONLNdäŸ(äIn addition to the x@°dONLNd%Ÿ)OGApple event handler dispatch tables, applications can add entries to a 
°dONLNdlä
(äspecial handler dispatch tableÕ¿°dONLNdä
)à: in either the application heap or the system heap. These °dONLNdƒä+◊((ädispatch tables ar≈@°dONLNd÷◊+
©)M0e used for various specialized handlers; for mor1`°dONLNd
™+
˚)”e information, see °dONLNd,ä8ö(5ä“Cr\°dONLNd,ö8
Ñ)2eating and Managing the Special Handler Dispatch TË °dONLNdN,
É8
†)Èables,”fi¿°dONLNdU,
°8
Ó) which begins on °dONLNdf9äE°(Bäpage Z‡°dONLNdk9¢E¥)4-99Æ¿°dONLNdo9¥Eπ). °dONLNdrKäW˛(TäWhen an application calls Ú†°dONLNdåK˛W
p)tAEProcessAppleEventÎÄ°dONLNdüK
pW
r)r
,kÄ°dONLNd†K
sW
u)
 ÎÄ°dONLNd°K
uW
Ø)the function løÄ°dONLNdØK
∞W
Õ);ooks fi`°dONLNd∂K
ŒW
˜)rst in the °dONLNd¡Xäd
˘(aäVapplication’s special handler dispatch table for an entry that was installed with the °dONLNdeäq±*    constant J@°dONLNd e≤q
)(keyPreDispatchE°dONLNd.e
q)T?. If the application’s special handler dispatch table does not °dONLNdmrä~
>({ä*include such a handler or if the handler r†°dONLNdór
?~
])µeturns •¿°dONLNdûr
]~
’)errAEEventNotHandledû@°dONLNd≤r
’~)x, the function °dONLNd¡äã˙(àälooks in the application’s `°dONLNd‹˚ã)q?Apple event dispatch table for an entry that matches the event °dONLNdåäò
(ïä class and event ID of the specifiΩ†°dONLNd<å
ò
")ãed ƒ†°dONLNd?å
"ò
])Apple event. 

πH¿≈4∫H¿≈"ªH_ˇ Ç@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-10    )B    Handling ê)&Apple Events4^*¿
¯
°dONLNd\lh¿(elIf the application’s ÏÄ°dONLNd\¿h
Ì)TEApple event dispatch table does not include such a handler or if the °dONLNdZiluî(rl    handler r( °dONLNdciïu≥))eturns ,
Courierº@°dONLNdji≥u
+)errAEEventNotHandled¥¿°dONLNd~i
+u
@)x, the  °dONLNdÑi
Au
≥)AEProcessAppleEvent°dONLNdói
≥u
˜)r function looks °dONLNdßvlÇ
‹(lVin the system special handler dispatch table for an entry that was installed with the °dONLNd˝Élèì*    constant J@°dONLNd
ÉîèË)(keyPreDispatchE°dONLNd
ÉËè
÷)T8. If the system special handler dispatch table does not °dONLNd
Lêlú
 (ôl*include such a handler or if the handler r†°dONLNd
vê
!ú
?)µeturns •¿°dONLNd
}ê
?ú
∑)errAEEventNotHandledû@°dONLNd
ëê
∑ú
Û)x, the function °dONLNd
†ùl©√(¶llooks in the system A`°dONLNd
¥ù√©
Ô)WEApple event dispatch table for an entry that matches the event class °dONLNd
˘™l∂fl(≥land event ID of the specifik°dONLNd™‡∂Ì)ted r°dONLNd™Ì∂
()Apple event. °dONLNd%ºl»õ(≈lIf the syste$‡°dONLNd1ºú»ß)0m Ä°dONLNd3ºß»Â)Apple event d
°dONLNd@ºÊ»
¨)?-ispatch table does not include such a handlerÙ°dONLNdmº
´»
¿)≈, the Û°dONLNdsº
¿»
›)Apple °dONLNdy…l’∂(“lEvent Manager rv`°dONLNdà…∂’Ë)Jeturns the r,‡°dONLNdî…È’
)3esult code 0Ä°dONLNdü…
’
ê)/errAEEventNotHandled)°dONLNd≥…
ê’
À)x to the server °dONLNd¬÷l‚
f(fll=application and, if the client application is waiting for a r‡°dONLNdˇ÷
g‚
z)˚eply+`°dONLNd÷
y‚
Â), to the client application‡°dONLNd÷
Ê‚
Ë)m
.

*˛
¯4Ò*˛
¯,Zapf Dingbats°dONLNd X˙`(¯X
s
°dONLNd!Òl˘u(˜l
Wú°dONLNd"Òu˘†)    ARNING

ˇ·ˇ‚7^
°dONLNd)¸l
É(
lBeforÛ¿°dONLNd.¸É
è)e a=`°dONLNd1¸ê

)n application calls a system N`°dONLNdN¸


f){Apple event handler懰dONLNda¸
e

j)Z, 懰dONLNdc¸
j

ã)system °dONLNdj
l
ç(
lsoftwar‰¿°dONLNdq
ç
Δ)!e has set up tQ`°dONLNd
«
‘):he °dONLNdÇ
‘
Á)A5 r@°dONLNdÜ
Á

)egiste§`°dONLNdå



    )r fj‡°dONLNdè




°)
%or the calling application. For this °dONLNd¥
l
 o(
l
rE°dONLNdµ
p
 ¥)eason, if you pr°†°dONLNd≈
¥
 ¯)Dovide a system dONLNd‘
¯
 
S)DApple event handler`°dONLNdÁ

S
 
Æ)[, it should never use °dONLNd˝
 l
,
û(
)lFA5 global variables or anything that depends on a particular context; °dONLNdC
,l
8
é*Botherwise, the application that calls the system handler may crashq‡°dONLNdÖ
,
è
8
ë(
5
è
.Ò‡°dONLNdá
/
ñ
7
ù)
s
°dONLNdâ
=l
Iq(
Fl
F °dONLNdä
=r
IÕ)or any entry in your †°dONLNdü
=Õ
I
∏)[5Apple event dispatch table, you can specify a wildcar© °dONLNd‘
=
∏
I
€)Îd value °dONLNd‹
Jl
Vx(
Slfor<°dONLNdfl
Jy
V{)
 º°dONLNd‡
J{
V
)$the event class, event ID, or both. m†°dONLNd
J

V
)ï
Y. °dONLNd
J

V
n)ou specify a wildcarÁ‡°dONLNd
J
n
V
ƒ)Xd by supplying the °dONLNd,
Wl
c¥(
`ltypeWildCard{Ä°dONLNd8
W¥
c
p)H, constant when installing an entry into the ˝°dONLNdd
W
p
c
Î)ºApple event dispatch table. °dONLNdÄ
dl
ps(
ml
AG@°dONLNdÅ
dt
pv)
 :†°dONLNdÇ
dv
pó)wildcar≥`°dONLNdâ
dó
p
@)!&d value matches all possible values. W
@°dONLNdØ
d
A
p
Z)™ildcar#°dONLNdµ
d
Z
p
›)ds make it possible to supply °dONLNd”
ql
}|(
zloneêÄ°dONLNd÷
q|
}~)
 ≤ °dONLNd◊
q~
}
F)-Apple event handler that dispatches several rÄ°dONLNd
q
G
}
d)…elated ‡°dONLNd
q
d
}
°)Apple events.†°dONLNd
q
°
}
£)=
 °dONLNd
Él
è
4(
ål.For example, if you specify an entry with the fl°dONLNdH
É
4
è
|)»typeWildCard⁄Ä°dONLNdT
É
|
è
‘)H event class and the °dONLNdi
êl
úÃ(
ôlkAEOpenDocumentsz°dONLNdy
êÃ
ú
    )` event ID, the ‚°dONLNdà
ê
    
ú
û)=Apple Event Manager dispatches `°dONLNdß
ê
ü
ú
Á)ñApple events of °dONLNd∑
ùl
©
(
¶l$any event class with an event ID of W@°dONLNd€
ù
    
©
i)ùkAEOpenDocumentsQ@°dONLNdÎ
ù
i
©
Ê)` to the handler for that entryü °dONLNd    
ù
Â
©
Í)|. °dONLNd
Øl
ª¯(
∏l!If you specify an entry with the cÄ°dONLNd-
Ø˘
ª
S)çkCoreEventClass]‡°dONLNd<
Ø
S
ª
´)Z event class and the °dONLNdQ
ºl
ȴ(
≈ltypeWildCard{Ä°dONLNd]
º¥
»∂)H
 ˚Ä°dONLNd^
º∂
»Ò)event ID, the „Ä°dONLNdl
ºÒ
»
Ü);Apple Event Manager dispatches 
‡°dONLNdã
º
á
»
œ)ñApple events of °dONLNdõ
…l
’y(
“lthe]`°dONLNdû
…z
’|)
 ›`°dONLNdü
…|
’÷)kCoreEventClass◊¿°dONLNdÆ
…÷
’
◊)Z< event class with any event ID to the handler for that entryb °dONLNdÍ
…
◊
’
‹(
“
◊. °dONLNdÌ
€l
Á¯(
‰l!If you specify an entry with the cÄ°dONLNd
€˘
Á
A)çtypeWildCard_°dONLNd
€
A
Á
ô)H event class and the …`°dONLNd/
€
ô
Á
·)XtypeWildCardƒ‡°dONLNd;
€
·
Á
„)H
 °dONLNd<
Ël
Ùß(
Òlevent ID, the h°dONLNdJ
Ëß
Ù
I);#Apple Event Manager dispatches all ◊ °dONLNdm
Ë
I
Ù
È)¢$Apple events of any event class and °dONLNdë
ıl

"(
˛l*any event ID to the handler for that entryó`°dONLNdª
ı
!

#)µ
.°dONLNdΩlÇ(lIf an •`°dONLNd√Çü)Apple ¢‡°dONLNd…†∫)event p °dONLNdœª
’)Adispatch table contains one entry for an event class and a specifiõ¿°dONLNd    
’
ˆ(
’c event °dONLNd    l 
ß(lKID, and also contains another entry that is identical except that it specifi†°dONLNd    e
® 
‹(
®es a wildcará°dONLNd    q
‹ 
‰)4d °dONLNd    s!l-
L(*l6value for either the event class or the event ID, the H °dONLNd    ©!
L-
©)‡Apple Event Manage`°dONLNd    ª!
™-
∂)^r dí¿°dONLNd    æ!
∂-
’)ispatch>@°dONLNd    ≈!
÷-
fl) esD‡°dONLNd    «!
fl-
Ò)     the °dONLNd    Ã.l:~(7lmoréÄ°dONLNd    œ.~:°)e specifiF@°dONLNd    ÿ.¢:¿)$c entryy‡°dONLNd    fl.ø:
). For example, if an ¿°dONLNd    Ù.
:
˜)W3Apple event dispatch table includes one entry that °dONLNd
';lGà(DlspecifiÓ °dONLNd
.;àG·)es the event class as Ø°dONLNd
D;‚G
*)ZkAECoreSuite™Ä°dONLNd
P;
*G
Ñ)H and the event ID as °dONLNd
e;
ÖG
ª)[    kAEDelete†°dONLNd
n;
ªG
”)6, and °dONLNd
tHlTé(Qlanotherñ‡°dONLNd
{HéTê)"
 ‡°dONLNd
|HëT€)entry that specifi:@°dONLNd
éH€T
4)Jes the event class as ˚ °dONLNd
§H
4T
|)YkAECoreSuiteˆ†°dONLNd
∞H
|T
÷)H and the event ID as °dONLNd
≈Ula¥(^ltypeWildCard{Ä°dONLNd
—U¥a…)H, the zÄ°dONLNd
◊U…a
y)&Apple Event Manager will dispatch the ¿°dONLNd
˝U
ya
÷)∞Apple event handler °dONLNdbln
(kl%associated with the entry that specifi√¿°dONLNd7b
n
])°es the event ID as Õ¿°dONLNdJb
]n
ì)P    kAEDelete `°dONLNdSb
ìn
ò)6. ˇ;∞@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-11
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

^Hk4^Hk°dONLNd_äg©(eäIMPORT
ç°dONLNd_©gπ)ANT

ˇ·ˇ‚7^
°dONLNdiäu˙(räIf your application sends ∫°dONLNd.i˙u
|)pApple events to itself using a ,
Courier°dONLNdMuäÅ
(~ätypeProcessSerialNumberw`°dONLNddu
Å
+)ä addrÛ‡°dONLNdiu
+Å
n)ess descriptor r¿°dONLNdyu
oÅ
Å)Decorã °dONLNd}u
ÅÅ
∞)d with the °dONLNdàÅäç“(äälowLongOfPSN{Ä°dONLNdîÅ“ç◊)H f‡°dONLNdñÅÿç
)ield set to V‡°dONLNd¢Å
ç
_)-kCurrentProcessQ@°dONLNd±Å
_ç
t)Z, the P@°dONLNd∑Å
tç
Æ)Apple Event °dONLNd√çäôfi(ñäManager jumps dirL °dONLNd‘çflô
&)Uectly to the appr`°dONLNdÂç
'ô
H)Hopriate û†°dONLNdÌç
Hô
À)!Apple event handler without °dONLNd
    ôä•≤(¢ä    going thr&@°dONLNd
ô≥•
$))ough the normal event-pr懰dONLNd
*ô
$•
t)qocessing sequence,‡°dONLNd
;ô
u•
¢)Q. For this r"@°dONLNd
Gô
¢•
¿)-eason, °dONLNd
N•ä±
*(Æä%your application will not appear to r%†°dONLNd
s•
+±
K)°un mor冰dONLNd
y•
K±
±) e slowly when it sends °dONLNd
ê±äΩÍ(∫äApple events to itself.≠@°dONLNd
ß±ÍΩ
)` For mor≥°dONLNd
ر
Ω
a)&e information, see @°dONLNd
±
bΩ
~)R“AddrðdONLNd
«±
~Ω
©)
essing an ÀÄ°dONLNd
—±
©Ω
Δ)+Apple °dONLNd
◊Ωä…√(ΔäEvent for DirF°dONLNd
‰Ωƒ…
5):ect Dispatching” on page †°dONLNd
˝Ω
6…
H)r5-13iÄ°dONLNd
Ω
H…
J)
.,Zapf DingbatsÈÄ°dONLNd¿
O»
V)
s
ç°dONLNdΩ
W…
Y)
 

ÌHÙ4ÓHÙ ÔäÔ

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdfiäÌ
(ÈäHandling the Required ðdONLNdfi
Ì
e)ãApple Eventsˇˇˇˇˇˇ€r)˘
4
°dONLNd*Ùä

(˝äThis section describes the r@°dONLNdFÙ



)wequir5Ä°dONLNdKÙ


%)ed <Ä°dONLNdNÙ
%

y)Apple events—the √@°dONLNd_Ù
y

)TApple events your application °dONLNd}

ä
À(

ämust support t¿°dONLNdã

Ã

Ù)BBo be compatible with System 7 and later versions of system softwar¨‡°dONLNdÕ


Ù
(


Ùe—°dONLNdœ
ä

h(
ä4and the descriptor types for all parameters of the rÖÄ°dONLNd

h

)fiequirú¿°dONLNd



å)ed £¿°dONLNd

å
) Apple events. It also describes °dONLNd+
ä
'
n(
$ä5how to write the handlers for these events, and it prÄ°dONLNd`

o
'
»)Âovides sample code.°dONLNdt
-ä
9ê(
6ä
Tµ¿°dONLNdu
-è
9–)o support the r@Ä°dONLNdÑ
-—
9Ë)BequirW¿°dONLNdâ
-Ë
9ı)ed ^¿°dONLNdå
-ı
9
≥)*Apple events, you must set the necessary fl–Ä°dONLNd∑
-
≥
9
fl)æags in the ≥¿°dONLNd¬
-
‡
9)-'SIZE'±Ä°dONLNd»
-
9)$
 °dONLNd…
:ä
Fç(
Cä
rE°dONLNd 
:é
F¶)esourç@°dONLNdœ
:¶
F
¶)>ce of your application, install entries in your application’s #Ä°dONLNd
:
ß
F(
C
ßApple event dispatch °dONLNd"
Gä
S
Ç(
Pä:table, add code to the event loop of your application to r≤ °dONLNd\
G
Ç
S
˚)¯ecognize high-level events, °dONLNdx
Tä
`ö(
]äandm °dONLNd{
Tõ
`ù)
 Ì °dONLNd|
Tù
`ø)    call the Ä°dONLNdÖ
T¿
`
2)#AEProcessAppleEvent`°dONLNdò
T
2
`
¢)r function, as described in ‰°dONLNd≥
T
¢
`
„)p“Accepting an U¿°dONLNd¡
T
‰
`
)BApple °dONLNd«
aä
m´(
jäEvent,”ü`°dONLNdŒ
a´
m¯)! which begins on ¿°dONLNdfl
a˘
m
)Npage ͆°dONLNd‰
a

m
)4-5>Ä°dONLNdÁ
a

m
6), and ´†°dONLNdÌ
a
6
m
§)“Installing Entries in the æ`°dONLNd
a
§
m)nApple Event Dispatch °dONLNd
nä
zê(
wä
Tµ¿°dONLNd
nè
z¨)ables,”¨`°dONLNd%
n≠
z˙) which begins on ¿°dONLNd6
n˚
z
)Npage ˜†°dONLNd;
n

z
)4-7KÄ°dONLNd>
n
 
z
%). ‡°dONLNd@
n
%
z
+)
Yfi`°dONLNdA
n
*
z
Õ)%ou must also write handlers for each `°dONLNdf
n
Œ
z    )§Apple event; °dONLNds
{ä
á
g(
Ñä3this section describes how to write these handlers.


•H
¨4
¶H
¨ 
ßä
ß

ˇ·ˇ‚7^°dONLNdß
òä
¶æ*    Required Ÿ@°dONLNd∞
òΩ
¶
)3Apple Eventsˇˇˇˇˇˇ‘@(
¢
4
°dONLNdæ
¨ä
∏
(
µäWhen a user opens or prints a fi_ °dONLNdfi
¨

∏
()çle fr™°dONLNd„
¨
(
∏
f)om the Finder4`°dONLNd
¨
f
∏)>%, the Finder sets up the information °dONLNd
πä
≈
J(
¬ä*your application uses to determine which fi“`°dONLNd@
π
J
≈
¶)¿les to open or print. IC`°dONLNdW
π
ß
≈
∫)]n Syc†°dONLNd[
π
∫
≈
Δ)ste¨†°dONLNd^
π
Δ
≈)m 7 and later °dONLNdl
Δä
“∂(
œäversions, it °dONLNdw
Δ∑
“)-Lf your application supports high-level events, the Finder communicates this °dONLNd√
ӊ
fl
%(
‹ä#information to your application thrÅ@°dONLNdÊ
”
%
fl
R)õ
ough the r¿°dONLNd
”
S
fl
j).equir°dONLNdı
”
j
fl
w)ed °dONLNd¯
”
w
fl
±)Apple events¶¿°dONLNd
”
±
fl
∂):. °dONLNd
Âä
Òı(
ÓäThe Finder sends these r6`°dONLNd
ˆ
Ò
)lequirM†°dONLNd$
Â

Ò
)ed T†°dONLNd'
Â

Ò
Ω)%Apple events to your application to rF`°dONLNdL
Â
Ω
Ò
Ï)£equest the °dONLNdW
Úä
˛õ(
˚äcorr`°dONLNd[
Úú
˛Ó)esponding actions:
    °dONLNdnä¢(äApplef
°dONLNds£•)
 
Ê!°dONLNdt•º)eventò¿°dONLNdzÌ
)H    Requestedj °dONLNdÉ

).
 
Í@°dONLNdÑ

7)action
°dONLNdåä%§("äOpen †°dONLNdë•%Ÿ)Applicationò¿°dONLNdùÌ%)H=Perform tasks your application normally performs when a user ò¿°dONLNd⁄$Ì0
Á*7opens your application without opening or printing any ò¿°dONLNd/Ì;
*    documents°dONLNd?äK◊(HäOpen Documentsò¿°dONLNd+?ÌK
4)cOpen the specifi]@°dONLNd;?
5K
u)Hed documents °dONLNdJOä[’(XäPrint Documentsò¿°dONLNdZOÌ[
2)cPrint the specifi‹†°dONLNdkO
2[
p)Eed documents°dONLNdy_äk†(häQuit Ø`°dONLNd~_†k‘)Applicationò¿°dONLNdä_Ìk
Z)MPerform tasks—such as rA‡°dONLNd°_
[k
¶)neleasing memoryÄ°dONLNd∞_
¶k
Æ)K, r’Ä°dONLNd≥_
Æk)equesting the user to ò¿°dONLNd…jÌv
“(sÌ1save documents, and so on—associated with quittin-@°dONLNd˙j
”v
Ú)Êg befor°dONLNd    
j
Úv    )e the ò¿°dONLNd    uÌÅ
á(~Ì"Finder terminates your applicationˇV@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-12    )B    Handling ê)&Apple Events4^*¿
¯
°dONLNd\lh
È(elWIn System 7 and later versions, the Finder uses these events as part of the mechanisms °dONLNdWilu
Û*Wfor launching and terminating applications. When the Finder launches your application, °dONLNdÆvlÇ¥*the application rŸ@°dONLNdøv¥Ç

)Heceives the Open Í°dONLNd–v

Ç
Ê)M0Application, Open Documents, or Print Documents °dONLNd
Élè
û(ålEevent. When the Finder terminates your application, the application rõ¿°dONLNd
EÉ
ûè
–(å
ûeceives the °dONLNd
QêlúÇ(ôlQuit Ø`°dONLNd
VêÇú
›)KApplication event. This method of communicating Finder information to your °dONLNd
°ùl©§(¶lapplication r{‡°dONLNd
Æù§©
«)8Aeplaces the mechanisms used in earlier versions of system softwar:¿°dONLNd
Ôù
»©
œ(¶
»e.°dONLNd
ÚØlª
î(∏lEApplications that do not support high-level events can still use the ,
CourierÜÄ°dONLNd7Ø
îª
‚(∏
îCountAppFilesņ°dONLNdDØ
‚ª
Á)N, °dONLNdFºl»Æ(≈lGetAppFiles{‡°dONLNdQºÆ»Δ)B, and È°dONLNdWºΔ»
)ClrAppFiles‰‡°dONLNdbº
»
)B pr,°dONLNdeº
»
3)ocedur√@°dONLNdkº
3»
^)es (or the „@°dONLNdvº
^»
†)+GetAppParmsfl °dONLNdź
†»
¨)B pr&@°dONLNdѺ
≠»
À)ocedurΩÄ°dONLNdäº
À»
)
e) to get °dONLNdî…l’
0(“l-the Finder information. See the chapter “Intr„†°dONLNd¡…
0’
ƒ)ƒ oduction to File Management” in °dONLNd·÷l‚Ñ(fllInsideÒÄ°dONLNdÁ÷Ñ‚Ü)
 qÄ°dONLNdË÷á‚…)Macintosh: FilesF‡°dONLNd¯÷ ‚
>)C for information on these r. °dONLNd÷
>‚
i)t
outines. T„@°dONLNd÷
h‚
÷)*o make your application °dONLNd5„lÔ
t(Ïl;compatible with System 7 and with earlier and later versionㆰdONLNdp„
tÔ
x(Ï
t
s»†°dONLNdq„
xÔ
ô), you m(`°dONLNdx„
öÔ
ˆ)"ust support both the °dONLNdçl¸fl(˘lold and new mechanisms.°dONLNd•
l
è*Use the +@°dONLNd≠
ê
∫)$Gestalt(†°dONLNd¥
∫

V)*# function to determine whether the k °dONLNd◊

V

Õ)úApple Event Manager is prÄ°dONLNd

Œ

È)xesent. °dONLNd˜
l
r(
lIf2`°dONLNd˘
s
u)
 ≤`°dONLNd˙
u
´)it is and the Õ°dONLNd
´

))6isHighLevelEventAware≈ °dONLNd

)

1)~ flQ‡°dONLNd 

2

µ)     ag is set in your application’s ¬†°dONLNd@

µ

Ÿ)É'SIZE'¿`°dONLNdF

Ÿ

€)$
 °dONLNdG
l
(o(
%l
rE°dONLNdH
p
(à)esourç@°dONLNdM
à
(Â)ce, your application rA`°dONLNdc
Ê
(
|)^"eceives the Finder information thrlÄ°dONLNdÖ

|
(
©)ñ
ough the rÏ°dONLNdè

©
(
¿)-equir@°dONLNdî

¡
(
Œ)ed °dONLNdó
)l
5á(
2lApple˝Ä°dONLNdú
)á
5â)
 }Ä°dONLNdù
)ä
5´)events. °dONLNd¶
;l
G
å(
DlDIf your application accepts high-level events, it must be able to pr•°dONLNdÍ
;
å
G
Æ(
D
åocess thb °dONLNdÚ
;
Ø
G
π)#e fˇ†°dONLNdı
;
π
G
Œ)
our r≥‡°dONLNd˙
;
œ
G
Ê)equirÀ °dONLNdˇ
;
Ê
G
Û)ed °dONLNd
Hl
T¢(
QlApple event ¿°dONLNd
H¢
T´)6s. ⁄ °dONLNd
H´
T±)    
Yö†°dONLNd
H±
T˚)our application rÖ¿°dONLNd"
H˚
T
1)Jeceives the r¿‡°dONLNd/
H
1
T
H)6equirÿ °dONLNd4
H
H
T
U)ed fl °dONLNd7
H
U
T
ô)Apple events frˇ¿°dONLNdF
H
ô
T
Â)Dom the Finder in °dONLNdW
Ul
a≥(
^lthese situations:,Zapf Dingbats°dONLNdi
kl
rq*
n
°dONLNdk
hx
t
©)FIf your application is not open and the user opens your application frëÄ°dONLNd±
h
©
t
È(
q
©om the Finder °dONLNdø
tx
Ä
Â(
}xPwithout opening or printing any documents, the Finder launches your application °dONLNd
Äx
å€*and sends it the Open @†°dONLNd%
Ä€
å
,)cApplication event.°dONLNd8
ïl
úq(
õl
n
°dONLNd:
íx
û
Δ)MIf your application is not open and the user opens one of your application’s °dONLNdá
ûx
™≤*documents fr‡°dONLNdì
û≥
™Ò);om the Finderö@°dONLNd†
û
™
‚)=8, the Finder launches your application and sends it the °dONLNdÿ
™x
∂‚(
≥xOpen Documents event.°dONLNdÓ
øl
Δq(
≈l
n
°dONLNd
ºx
»
Δ)NIf your application is not open and the user prints one of your application’s °dONLNd>
»x
‘≤*documents fr‡°dONLNdJ
»≥
‘Ò);om the Finderö@°dONLNdW
»
‘
‚)=8, the Finder launches your application and sends it the °dONLNdè
‘x
‡‚(
›xPrint Documents event. 0Ä°dONLNd¶
‘„
‡È)k
YÒ°dONLNdß
‘Ë
‡
‰)8our application should print the selected documents and °dONLNdfl
‡x
Ï{(
Èx
rE°dONLNd‡
‡|
Ï÷)emain open until it rä`°dONLNdı
‡÷
Ï
)Zeceives a Quit RÄ°dONLNd
‡

Ï
L)@Application P†°dONLNd
‡
M
Ï
o)7event fr6¿°dONLNd
‡
o
Ï
≠)"om the Finder¡ °dONLNd%
‡
¨
Ï
Æ)=
.°dONLNd'
ıl
¸q(
˚l
n
°dONLNd)
Úx
˛
fi)SIf your application is open and the user opens or prints any of your application’s °dONLNd|
˛x
≤*documents fr‡°dONLNdà
˛≥
Ò);om the Finderö@°dONLNdï
˛

Ï)=7, the Finder sends your application the Open Documents °dONLNdÃ
xÏ(xor Print Documents event.°dONLNdÊl&q(%l
n
°dONLNdËx(
∂)HIf your application is open and the user chooses Restart or Shut Down fr=Ä°dONLNd    0
∑(
ÿ(%
∑om the °dONLNd    7(x4ï(1xFinder^@°dONLNd    =(ñ4
û)<’s Special menu, the Finder sends your application the Quit  °dONLNd    y(
û4
‘(1
ûApplication @°dONLNd    Ö(
’4
Ì)7eventaÄ°dONLNd    ä(
Ì4
Ô)
.ˇ2n@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-13
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh©(eäUpon r’@°dONLNd\©h
)eceiving any of the r|Ä°dONLNd\
h
)Zequirì¿°dONLNd \
h
')ed ö¿°dONLNd#\
'h
)2Apple events, your application should perform the °dONLNdUiäu´(räaction r¶‡°dONLNd]i´u
!)!equested by the event. Her‡Ä°dONLNdwi
!u
…)v'e is a summary of the contents of the r„¿°dONLNdûi
…u
‡)®equir˚°dONLNd£i
‡u)
ed events °dONLNd≠väÇÈ(äand the actions they rö‡°dONLNd√vÈÇ
r)_equest applications to perform:
    °dONLNd„èäö†(óäOpenh±°dONLNdÁè°ö£)
 
ì·°dONLNdËè£ö˛)Application—perform3”°dONLNd˚èˇö

)\
 
≥Û°dONLNd¸è

ö
)tasksû‡°dONLNd

è
ö
)
 
°dONLNd
è
ö
I)
associatedrÌ°dONLNd
è
Iö
K).
 
Û°dONLNd
è
Kö
\)withfl_°dONLNd
è
]ö
_)
 
_°dONLNd
è
`ö
Ç)opening:S°dONLNd
è
Éö
Ö)#
 
∫s°dONLNd
è
Öö
è)an0#°dONLNd
è
êö
í)
 
∞C°dONLNd
è
íö
√)application 
°dONLNd
,ùä©∫(¶äEvent class,
Courier( °dONLNd
8ùÍ©
D)`kCoreEventClass°dONLNd
I≠äπ±(∂äEvent ID( °dONLNd
R≠Íπ
V)`kAEOpenApplication°dONLNd
fΩä…ª(Δä
Parameters( °dONLNd
qΩÍ…
)`None°dONLNd
wÕ䟒(÷äRequested action( °dONLNd
àÕÍŸ
Ô)`7Perform any tasks—such as opening an untitled document ( °dONLNd
øÿ͉*9window—that you would normally perform when a user opens ( °dONLNd
¯„ÍÔ
˚*;your application without opening or printing any documents.
    °dONLNd6
ä
†(
äOpenh±°dONLNd:
°
£)
 
Ë—°dONLNd;
£
Ú)Documents—open„°dONLNdI
Û
ı)P
 
ó°dONLNdJ
ı

)thed°dONLNdM



)
 
àÑ°dONLNdN



!)specifiÌS°dONLNdU

!

+)edc°dONLNdW

,

.)
 
„#°dONLNdX

.

])    documents
°dONLNde
ä
∫(
äEvent classŸ°dONLNdr
˘

S)okCoreEventClass°dONLNdÉ
"ä
.±(
+äEvent IDŸ°dONLNdç
"˘
.
Y)okAEOpenDocuments°dONLNdü
2ä
>ß(
;äRequirE@°dONLNd•
2®
>‚)ed parameter°dONLNd∂
Bû
N¡(
KûKeywor¨`°dONLNdº
B¡
N…)#d:Ÿ°dONLNdø
B˘
N
S)8keyDirectObject°dONLNd—
Rû
^Â(
[ûDescriptor type:Ÿ°dONLNd‚
R˘
^
5)[
typeAEList°dONLNdÔ
bû
nµ(
kûData:Ÿ°dONLNdı
b˘
n
)[
A†°dONLNdˆ
b


n
9) list of alias rˇ‡°dONLNd
b
8
n
J)7ecort@°dONLNd

b
K
n
„)!ds for the documents to be opened°dONLNd-
rä
~’(
{äRequested actionŸ°dONLNd?
r˘
~
t)oOpen the documents specifiÄ°dONLNdY
r
u
~
õ)|    ed in theë°dONLNdb
r
õ
~
ù)&
 °dONLNdc
r
û
~
˛)keyDirectObject Ÿ°dONLNds
}˘
â
&(
ܢ    parameter¨†°dONLNd|
}
&
â
()-
.
    °dONLNdÄ
ûä
©
(
¶ä Print Documents—print the specifiÁ“°dONLNd°
û

©
Y)ìed documents
°dONLNd±
¨ä
∏∫(
µäEvent classŸ°dONLNdæ
¨˘
∏
S)okCoreEventClass°dONLNdœ
ºä
»±(
≈äEvent IDŸ°dONLNdŸ
º˘
»
_)okAEPrintDocuments°dONLNdÏ
Ãä
ÿß(
’äRequirE@°dONLNdÚ
î
ÿ‚)ed parameter°dONLNd
‹û
Ë¡(
ÂûKeywor¨`°dONLNd    
‹¡
Ë…)#d:Ÿ°dONLNd
‹˘
Ë
S)8keyDirectObject°dONLNd
Ïû
¯Â(
ıûDescriptor type:Ÿ°dONLNd/
Ï˘
¯
5)[
typeAEList°dONLNd<
¸ûµ(ûData:Ÿ°dONLNdB
¸˘
)[
A†°dONLNdC
¸


9) list of alias rˇ‡°dONLNdS
¸
8
J)7ecort@°dONLNdW
¸
K
„)"ds for the documents to be printed°dONLNd{ä’(äRequested actionŸ°dONLNdç˘
q)oPrint the documents specifi쇰dONLNd®
r
ö)y
ed in the ê`°dONLNd≤
õ
ı))keyDirectObjectä¿°dONLNd¡
ı
˜)Z
 Ÿ°dONLNd¬˘#
ˆ( ˘5parameter without opening windows for the documents. 
    °dONLNd˙8äCû(@äQuit ï°dONLNdˇ8ûC
|)2Application—perform tasks associated with quitting0Δ°dONLNdˇˇ)fi
 
°dONLNd?FäR∫(OäEvent class◊@°dONLNdKF¯R
R)nkCoreEventClass°dONLNd\Väb±(_äEvent ID◊@°dONLNdeV¯b
d)nkAEQuitApplication°dONLNdyfärª(oä
Parameters◊@°dONLNdÑf¯r
)nNoneˇ§@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-14    )B    Handling ê)&Apple Events4^*¿
¯
°dONLNd
∏ÿl‰r(·l
Y@Ä°dONLNd
πÿr‰„)our application needs to r†‡°dONLNd
”ÿ„‰
¿)q2ecognize only two descriptor types to handle the rÔ@°dONLNdÿ
¿‰
◊)›equirÄ°dONLNd
ÿ
ÿ‰
Â)ed °dONLNdÂlÒ
(Ól*Apple events: descriptor lists and alias ro°dONLNd7Â
Ò
/)±ecor„`°dONLNd;Â
/Ò
Ë)'ds. The Open Documents event and Print °dONLNdbÚl˛
-(˚l,Documents event use descriptor lists to stor冰dONLNdéÚ
-˛
˜)¡-e a list of documents to open. Each document °dONLNdªˇl
í(
l    is specifiìÄ°dONLNd≈ˇí
“)&ed as an alias rZ°dONLNd’ˇ”
Â)AecorŒ`°dONLNdŸˇÂ

K)d in the descriptor list. °dONLNdÙ
l
r(
l
Y@Ä°dONLNdı
r
ï)ou can r√¿°dONLNd˝
ï

)#etrieve the data that specifi‰°dONLNd



Æ)w%es the document to open as an alias r-†°dONLNd?

Ø

¡)£ecor¢°dONLNdC

¡

Î)
d, or you °dONLNdM
l
*Å(
'lcan r†°dONLNdR
Ç
*≈)equest that the †°dONLNdb
≈
*
;)CApple Event Manager coer±‡°dONLNdz

;
*
q)vce the alias r‡°dONLNdà

r
*
Ñ)7ecorê@°dONLNdå

Ñ
*
•)d to a fi†°dONLNdï

•
*
–)!
le system °dONLNdü
+l
7à(
4lspecifiÓ °dONLNd¶
+à
7®)cation (,
Courier£‡°dONLNdÆ
+©
7Õ)!FSSpec°†°dONLNd¥
+Õ
7÷)$) r:Ä°dONLNd∑
+◊
7È)
ecorƇ°dONLNdª
+È
7
)d. The fi °dONLNdƒ
+

7
V)%le system specifi`°dONLNd’
+
V
7
w)Hcation rC@°dONLNd›
+
w
7
â)!ecor∑†°dONLNd·
+
â
7
õ)d prÄ°dONLNdÂ
+
ú
7
‰)ovides a standarrÄ°dONLNdı
+
‰
7
Ï)Hd °dONLNd˜
8l
D’(
Almethod of identifying fiÄ°dONLNd
8÷
DÁ)jles ie‡°dONLNd
8Á
D
@)n System 7 and later˜@°dONLNd(
8
@
D
g)Y     versionsÉ°dONLNd1
8
h
D
j)(
.°dONLNd2
8
k
D
~) See ÷°dONLNd7
8
~
D
€)Inside Macintosh: Filesú‡°dONLNdN
8
‹
D
ı)^ for a °dONLNdU
El
Q
(
Nl(complete description of how to specify fiKÄ°dONLNd~
E
 
Q
O)¥les using fi‘@°dONLNdä
E
O
Q
ó)/le system specifi›Ä°dONLNdõ
E
ó
Q
∏)Hcation r`°dONLNd£
E
π
Q
À)"ecorx¿°dONLNdß
E
À
Q
◊)ds.


o*
v
¯4
p*
v
¯ 
ql
q
¯

ˇ·ˇ‚7^°dONLNd´
bl
p”(
llHandling the Open 5Ä°dONLNdΩ
b”
p
/)gApplication Eventˇˇˇˇˇˇ‘@(
l
Ò
4
°dONLNd–
vl
Çv(
l
W°dONLNd—
vv
Ç
y)
;hen the user opens your application, the Finder uses the PrD°dONLNd
v
z
Ç
È(

zocess Manager to launch °dONLNd$
Él
è
ƒ(
ålMyour application. On startup, your application typically performs any needed °dONLNdq
êl
ú
*%initialization, and then begins to prÅ@°dONLNdñ
ê

ú
Ô)õ6ocess events. If your application supports high-level °dONLNdÃ
ùl
©…(
¶levents, and if the useû¿°dONLNd‚
ù…
©‘)]r o܇°dONLNdÂ
ù’
©
)>pens your application without selecting any documents to open °dONLNd#
™l
∂‚(
≥lor print, your application r”@°dONLNd?
™‚
∂
/)veceives the Open ‰°dONLNdP
™
/
∂
Ä)MApplication event.°dONLNdc
ºl
»r(
≈l
Tµ¿°dONLNdd
ºq
»≈)o handle the Open ì¿°dONLNdv
º≈
»
Â)TAApplication event, your application should do just what the user °dONLNd∑
…l
’
fi(
“lSexpects it to do when it is opened. For example, your application might open a new °dONLNd

÷l
‚»*untitled window in rã °dONLNd
÷»
‚
!)\esponse to an Open Ö@°dONLNd1
÷
!
‚
r)YApplication event.°dONLNdD
Ël
Ùö(
ÒlListing 4-5 @°dONLNdO
Ëõ
Ù
)/ shows a handler that pr8Ä°dONLNdg
Ë

Ù
T)kocesses the Open ‡Ä°dONLNdx
Ë
S
Ù
Á)M!Application event. This handler fi≥@°dONLNdö
Ë
Ë
Ù
ı)ïrst °dONLNdû
ıl
’(
˛lcalls an application-defiÃ@°dONLNd∑
ı’

,)ined function called 7†°dONLNdÀ
ı
-

ô)XMyGotRequiredParam0‡°dONLNd›
ı
ô

ü)l
s0Ä°dONLNdfi
ı
ü

Δ)    , which cs °dONLNdÁ
ı
Δ

⁄)'heckÄ°dONLNdÎ
ı
€

·)s °dONLNdÌlñ(l    whether t`°dONLNdˆó§)+he ¡°dONLNd˘£
)Apple event contains any r°Ä°dONLNd

1)wequir∏¿°dONLNd
1
u)ed parameters. Ï °dONLNd'
u
Δ)DIf so, the handler r÷Ä°dONLNd;
Δ
Ò)Q
eturns an °dONLNdElx(lerr
@°dONLNdHyÇ)or¨°dONLNdJÅ∂), because by°dONLNdV∑ )6 defiÑ °dONLNd[ 
)nition, the Open ßÄ°dONLNdl

—)J*Application event should not contain any rd°dONLNdñ
“
È)æequir{@°dONLNdõ
È
ˆ)ed °dONLNdûl(ô(%l    parameter°dONLNdßö(†).s.Œ°dONLNd©†(–)
 Otherwise?‡°dONLNd≥—(”)1
,ø‡°dONLNd¥”(
ò)( the handler opens a new document windowä°dONLNd‹
ò(
ö)≈
.°dONLNdvlÇ∑(lRequested action◊@°dONLNdv⁄Ç
´)n.Perform any tasks that your application would ◊@°dONLNd?Å⁄ç
*normallyD†°dONLNdGÅ
ç
))
 ƒ†°dONLNdHÅ
ç
€)/perform when the user chooses Quit. Such tasks ◊@°dONLNdwå⁄ò
Ë(ï⁄<typically include asking the user whether to save documents ◊@°dONLNd≥ó⁄£
y*!that have been changed. When appr°dONLNd‘ó
z£
Í)†opriate, the Finder sends ◊@°dONLNdÓ¢⁄Æ
Û(´⁄Bthis event to an application immediately after sending it a Print ◊@°dONLNd
0≠⁄π
∞*/Documents event (unless the application was alrΰdONLNd
_≠
∞π
Ô)÷eady open) or ◊@°dONLNd
m∏⁄ƒ
ó(¡⁄+if the user chooses Restart or Shut Down frƒ@°dONLNd
ò∏
óƒ
’)Ωom the Finder…`°dONLNd
•∏
÷ƒ
fl)?’s ◊@°dONLNd
®√⁄œ
(Ã⁄Special menu.
    °dONLNdˇˇ(plQuit ï°dONLNdˇˇ)2Application—perform tasks associated with quitting0Δ°dONLNdˇˇ)fi (continued)ˇ1–@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-15
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHn4gHn"hH_

ˇ·ˇ‚7^    °dONLNd\äg∂(däListing 4-5°dONLNd\Œg‘)D
A0°dONLNd\‘g
+) handler for the Open 
@°dONLNd#\
+g
o)WApplication event,
Courier
°dONLNd6väÇ
h(ä%FUNCTION MyHandleOApp (theAppleEvent,r °dONLNd[v
hÇ
n)fi
 q¿°dONLNd\v
nÇ
‡)reply: AppleEvent; °dONLNdtÑ“êÿ(ç“
 °dONLNdxÑ
ê
)6
 †°dONLNdyÑ
ê
)
 @°dONLNdzÑ
ê
Œ)handlerRefcon: LongInt): OSErr;°dONLNdöíäûú(õäVAR°dONLNdü†ú¨¢+
m†°dONLNd††¢¨®)
y@°dONLNd°†®¨¥)Er~Ä°dONLNd£†¥¨Ã)r: O}°dONLNd߆èÍ)SErr;°dONLNd≠Æä∫®(∑äBEGIN°dONLNd¥ºú»
§+,myErr := MyGotRequiredParams(theAppleEvent);°dONLNd‚ ú÷
*IF myErr = noErr THENx °dONLNd˜ 
÷
 )~
 °dONLNd˚ÿƉ¥(·Æ
D†°dONLNd¸ÿ¥‰“)oNew;°dONLNd
ÊúÚ
 (ÔúMyHandleOApp := myErr;°dONLNd
Ùä
¢(˝äEND;°dONLNd

ä
Ú*For a description of the `°dONLNd
8
Û

e)iMyGotRequiredParamsx@°dONLNd
K

e

°)r function, see V¿°dONLNd
Z

¢

–)=Listing 4-1j`°dONLNd
e

–

’).
1j`°dONLNd
f

’

Â) on ±@°dONLNd
j

Â

¸)page å °dONLNd
o

˝
)4-35‡°dONLNd
s

). °dONLNd
u
ä
%˛(
"äFor information about the V†°dONLNd
è
ˇ
%
)ureplyT¿°dONLNd
î


%
2) and A‡°dONLNd
ô

3
%
Å)handlerRefcon=°dONLNd
¶

Å
%
‘)N parameters for an :°dONLNd
π

‘
%)SApple event °dONLNd
≈
&ä
2¨(
/ähandler%¿°dONLNd
Ã
&¨
2¡)", see v°dONLNd
“
&¡
2–)“W∏†°dONLNd
‘
&œ
2È)riting @Ä°dONLNd
€
&Í
2
z)Apple Event Handlers” on page ü@°dONLNd
˘
&
z
2
å)ê4-33Û °dONLNd
˝
&
å
2
é)
.s °dONLNd
˛
&
è
2
ë)
 


PH
W4
QH
W 
Rä
R

ˇ·ˇ‚7^°dONLNd
Cä
Q
P(
Mä!Handling the Open Documents Eventˇˇˇˇˇˇ‘@(
M
4
°dONLNd#
Wä
cê(
`ä
Tµ¿°dONLNd$
Wè
c)So handle the Open Documents event, your application should open the documents that °dONLNdw
dä
p
!(
mäthe Open Documents event specifi*@°dONLNdó
d
"
p
R)òes in its dirõÄ°dONLNd§
d
R
p
é)0ect parameterk`°dONLNd±
d
é
p
ì)<. =¿°dONLNd≥
d
ì
p
ô)
Y˛@°dONLNd¥
d
ò
p)our application extracts this °dONLNd“
qä
}
4(
zä%information and then opens the specifiÚ`°dONLNd¯
q
4
}
r)™ed documentsN¿°dONLNd
q
s
}
x)?. N¿°dONLNd
q
x
}
¶)Listing 4-6Ô°dONLNd
q
¶
}). shows a handler for the °dONLNd*
~ä
äÚ(
áäOpen Documents eventfi¿°dONLNd>
~Ú
ä˜)h. 


≠H
µ4
ÆH
µ"
ÆH_

ˇ·ˇ‚7^
    °dONLNdA
£ä
Æ∂(
´äListing 4-6°dONLNdM
£Œ
Æ‘)D
A0°dONLNdN
£‘
Æ
q)% handler for the Open Documents event
°dONLNdu
Ωä
…
h(
Δä%FUNCTION MyHandleODoc (theAppleEvent,r °dONLNdö
Ω
h
…
n)fi
 q¿°dONLNdõ
Ω
n
…
⁄)reply: AppleEvent;°dONLNd∞
ÀÆ
׺(
‘Æ  °dONLNd≥
À¿
◊Δ)
 °dONLNd∏
À

◊
)H
 †°dONLNdπ
À

◊
)
 @°dONLNd∫
À

◊
‘)  handlerRefcon: LongInt): OSErr;°dONLNd€
Ÿä
Âú(
‚äVAR°dONLNd‡
Áú
ÛΔ+myFSS: °dONLNdÍ
Á“
Ûÿ)6
 °dONLNdÔ
Á

Û
D)HFSSpec;°dONLNd¯
ıú
“(
˛ú    docList: °dONLNd
ı“
ÿ)6
 °dONLNd    
ı


\)HAEDescList;°dONLNdú
(úmyErr, ignoreErr: y@°dONLNd+

)l
 °dONLNd0

8)OSErr~ °dONLNd5
8
>)
;°dONLNd8ú¢(ú
i†°dONLNd9¢
)ndex, itemsInList:°dONLNdR

J)xLongInt;°dONLNd\ú+‰((úactualSize: °dONLNdn
+
)l
 °dONLNdp
+
8)Size;°dONLNdw-ú9Δ(6úkeywd: °dONLNdÅ-“9ÿ)6
 °dONLNdÜ-
9
V)H
AEKeyword;°dONLNdí;úG(DúreturnedType: z¿°dONLNd°;Gˆ)T
 °dONLNd®;
G
J)*DescType}°dONLNd∞;
JG
P)0
;°dONLNd≤IäUê(Rä
B†°dONLNd≥IêU®)EGIN°dONLNdπWúc
¯+:{get the direct parameter--a descriptor list--and put it }°dONLNdıeúqˆ*{ into docList}°dONLNdsú
Ê*7myErr := AEGetParamDesc(theAppleEvent, keyDirectObject,°dONLNdGÅ
,ç
™+êtypeAEList, docList);ˇ:@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-16    )B    Handling ê)&Apple Events4^*¿
¯,
Courier
°dONLNd\~h®(e~IF myEr}`°dONLNd\®hΔ)*r = n{Ä°dONLNd\Δh
)
oErr THEN °dONLNdj~vñ(s~BEGI~Ä°dONLNdjñvú)
N°dONLNd xêÑñ(Åê
{†°dONLNd!xñÑ
t)%check for missing required parametersq¿°dONLNdFx
tÑ
z)fi
}°dONLNdJÜêíñ(èê
m†°dONLNdKÜñí
ò)+yErr := MyGotRequiredParams(theAppleEvent);°dONLNdyîê†∫(ùêIF myEr}`°dONLNdÄî∫†ÿ)*r = n{Ä°dONLNdÖîÿ†
)
oErr THEN °dONLNdí¢êÆ®(´êBEGI~Ä°dONLNdñ¢®ÆÆ)
N°dONLNdõ∞¢º®(π¢
{†°dONLNdú∞®º
⁄)3count the number of descriptor records in the list}°dONLNd”æ¢ 
\(«¢myErr := AECountItems (docList,t`°dONLNdÚæ
\ 
b)∫
 t°dONLNdÛæ
b 
∞)itemsInList);°dONLNd
âÿ(’¢IF myErr = no{ °dONLNd
Ãÿ
)NErr Ty@°dONLNd
Ã
ÿ
 )HEN°dONLNd
⁄¥Ê
¬(„¥-{now get each descriptor record from the listo °dONLNd
K⁄
¬Ê
‘(„
¬, }°dONLNd
SË¥Ù¿(Ò¥{ @°dONLNd
UË¿Ù
)coerce the { °dONLNd
`Ë
Ù
‡)B%returned data to an FSSpec record, anm@°dONLNd
ÖË
‡Ù
Ú)fid }°dONLNd
爥
¿(ˇ¥{ @°dONLNd
舿
ˆ)    open the {‡°dONLNd
òˆˆ

V)6associated file}°dONLNd
≠
¥

t(
¥ FOR index := 1 TO itemsInList DO°dONLNd
“
¥
“*BEGIN°dONLNd
›
 Δ
,
Œ+,myErr := AEGetNthPtr(docList, index, typeFSSoÄ°dONLNd    
 
Œ
,
⁄(
)
Œ, °dONLNd
.
D
:
n(
7
Dkeywd, }`°dONLNd
.
n
:
Ú)*returnedType, @myFSS, °dONLNdB
<
D
H
‡(
E
DSizeof(myFSS),actualSize);°dONLNdb
JΔ
V(
SΔIF myEr}`°dONLNdi
J
V
)*r = n{Ä°dONLNdn
J

V
>)oErr THExÄ°dONLNdv
J
>
V
D)0
N°dONLNd}
XΔ
d‰(
aΔBEGIN°dONLNdâ
fÿ
r
Ä+myErr := MyOpenFile(@myFSS);°dONLNd¨
tÿ
Ä
*IF myEr}`°dONLNd≥
t

Ä
&)*r <> n{ °dONLNdπ
t
&
Ä
V)$oErr THEx °dONLNd¡
t
V
Ä
b)0N °dONLNdÀ
ÇÍ
é
™(
ãÍ ; {handle error from MyOpenFile}°dONLNdÒ
êΔ
úÿ(
ôΔEND°dONLNd˙
ûΔ
™fi*ELSE°dONLNd
¨ÿ
∏
û+!; {handle error from AEGetNthPtr}°dONLNd+
∫¥
Δ∫(
ô
E†°dONLNd,
∫∫
ΔÃ)ND;~Ä°dONLNd/
∫Ã
Δ
8) {of For index Do}°dONLNdD
Ȑ
‘¢(
—êEND°dONLNdJ
֐
‚®*ELSE°dONLNdR
‰¢

ò+); {handle error from MyGotRequiredParams}°dONLNd~
Úê
˛“(
˚êignoreErr :{‡°dONLNdâ
Ú“
˛
b)B= AEDisposeDesc(docList)r‡°dONLNd°
Ú
b
˛
h)ê
;°dONLNd§~ê(    ~END°dONLNd©~ñ*ELSE°dONLNd∞ê(
∞+0; {failed to get direct parameter, handle error}°dONLNd‚*~6Ñ(3~
M†°dONLNd„*Ñ6ˆ)yHandleODoc := myErxÄ°dONLNdˆ*ˆ6
)rr;°dONLNd˘8lDÑ(AlEND;°dONLNd˛Pl\Ø*The handler in ÿ†°dONLNdPØ\›)CListing 4-6x‡°dONLNdPfi\Ê)/ fi†°dONLNdPÁ\
)    rst uses the ¿°dONLNd(P
\
o)4AEGetParamDescÄ°dONLNd6P
o\
—)T function to get the dir¢@°dONLNdNP
—\
fl)bect °dONLNdR]liª(flparameter (specifiS°dONLNdd]ºiÁ)P
ed by the ¨Ä°dONLNdn]Ái
A)+keyDirectObject¶‡°dONLNd}]
Ai
e)Z keywor†@°dONLNdÑ]
ei
k)$
dº°dONLNdÖ]
ki
ê)
) out of tZ†°dONLNdè]
ëi
û)&he @°dONLNdí]
ûi
Ÿ)Apple event. °dONLNdüjlv|(slThe;¿°dONLNd¢j}v)
 ª¿°dONLNd£jvß)    handler rc‡°dONLNd¨j®vfl))equests that ©‡°dONLNdπjflv
3)7AEGetParamDesc§†°dONLNd«j
3v
9)T rȆ°dONLNd…j
9v
µ)eturn a descriptor list in the ¬@°dONLNdËj
∂v
‡)}docListø†°dONLNdÔj
‡v
‚)*
 °dONLNdwlɸ(Äl variable. The handler then checkì °dONLNdw¸É
)ês tíÄ°dONLNdw
É
4)
hat it has r$`°dONLNdw
5É
à)/etrieved all of the rù °dONLNd4w
àÉ
ü)Sequir¥`°dONLNd9w
üÉ
Ó)ed parameters by °dONLNdJÑlêú(çlcalling the Á@°dONLNdVÑúê
)0MyGotRequiredParams‡ °dONLNdiÑ
ê
O)r function. (See @°dONLNdyÑ
Pê
~)BListing 4-1(‡°dONLNdÑÑ
~ê
´).
1 on page J†°dONLNdéÑ
´ê
≥)-4-ûÄ°dONLNdêÑ
≥ê
Ω)35ûÄ°dONLNdíÑ
Ωê
÷)
 for a °dONLNdôëlùÈ(öldescription of this function.)ˇ@§@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-17
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähÓ(eäOnce the handler has r{°dONLNd\Óh
k)detrieved the descriptor list fr‡°dONLNd5\
lh
ç)~om the ‡`°dONLNd<\
åh
Â) Apple event, it uses ,
Courier°dONLNdQiäu“(räAECountItems{Ä°dONLNd]i“u
œ)H< to count the number of descriptors in the list. Using the ry °dONLNdôi
œu
Ù)˝eturned °dONLNd°väÇ
π(äEnumber as an index, the handler can get the data of each descriptor rS °dONLNdÊv
πÇ
À(
πecor«Ä°dONLNdÍv
ÀÇ
)d in the list. °dONLNd˘Éäè»(åäThis handler rø†°dONLNd
É»è
)>equests that the c°dONLNd
É
è
R)HAEGetNthPtr^‡°dONLNd
#É
Rè
é)B function coer·Ä°dONLNd
1É
éè)<ce the data in the descriptor °dONLNd
Oêäúç(ôä
rE°dONLNd
Pêéú†)ecorπ`°dONLNd
Tê†ú¡)d to a fi¿°dONLNd
]ê¬ú

)"le system specifi#°dONLNd
nê

ú
+)Hcation rI‡°dONLNd
vê
+ú
=)!ecoræ@°dONLNd
zê
=ú
–)!d. The handler can then use the fi· °dONLNd
úê
–ú
˚)ì
le system °dONLNd
¶ù䩶(¶äspecifiÓ °dONLNd
≠ù¶©«)cation r°dONLNd
µù»©⁄)"ecorâ`°dONLNd
πù⁄©
X)d as a parameter to its own ru†°dONLNd
÷ù
X©
≤)~outine for opening fi\@°dONLNd
Îù
≥©
¡)[les.°dONLNd
Øäª≠(∏äFor mor¿°dONLNd
˜Øƪ

)$e information on the Ø°dONLNdØ

ª
^)\AEGetParamDesc©¿°dONLNdØ
^ª
ì)T function, se>†°dONLNd'Ø
îª
õ)6e à@°dONLNd)Ø
õª
≤)page c °dONLNd.Ø
≥ª
≈)4-69∑°dONLNd2Ø
Ż
«)
.7°dONLNd3Ø
Ȼ
Ó) For mor<¿°dONLNd;Ø
Óª
ı)&e °dONLNd=ºä»fl(≈äinformation on the fl†°dONLNdPºfl»
!)UAEGetNthPtr€Ä°dONLNd[º
!»
6)B and »†°dONLNd`º
7»
)AECountItemsƒ °dONLNdlº
»
∏)H functions, señ°dONLNdzº
π»
¿):e fl†°dONLNd|º
¿»)“Getting Data Out °dONLNdé…ä’
(“äof a Descriptor List” on page *`°dONLNd¨…
’
)Ç4-31~@°dONLNd∞…
’
 )
.°dONLNd≤€äÁË(‰äAfter extracting the fi&†°dONLNd…€ÈÁ
1)_le system specifi/‡°dONLNd⁄€
1Á
R)Hcation rV¿°dONLNd‚€
RÁ
d)!ecorÀ °dONLNdÊ€
dÁ)'d that describes the document to open, °dONLNdËäÙ
(Òäyour application can use this r¿°dONLNd,Ë
Ù
")Üecorw °dONLNd0Ë
"Ù
d)d to open the fiGÄ°dONLNd@Ë
eÙ
∏)Cle. For example, in $‡°dONLNdTË
πÙ
Á)TListing 4-6≈ °dONLNd_Ë
ÁÙ)., the code °dONLNdjıä

ø(˛äpasses the fiχ°dONLNdwıø


)5le system specifiˆ °dONLNdàı



()Hcation r°dONLNdêı
)


;)"ecorë`°dONLNdîı
;


_)
d to its r¿°dONLNdûı
`


∫)%outine for opening fi¯`°dONLNd≥ı
∫


€)Z    les, the °dONLNdº
ä
Δ(
ä
MyOpenFile|@°dONLNdΔ
Δ
Ú)< function. °dONLNd“
ä
 ù(
äThe ª¿°dONLNd÷
ù
 Ÿ)
MyOpenFile∏°dONLNd‡
Ÿ
 
∑)<4 function should be designed so that it can be calle» °dONLNd

∑
 
¬)fid iL@°dONLNd

√
 
œ)n rb†°dONLNd

œ
 )esponse to °dONLNd%
!ä
-£(
*äboth tS@°dONLNd+
!§
-
π);he Open Documents event and to events generated by the user¡Ä°dONLNdf
!
∏
-
¯(
*
∏. For example, °dONLNdu
.ä
:¢(
7äwhenC`°dONLNdy
.£
:•)
 √`°dONLNdz
.•
:
)the user chooses Open fr£@°dONLNdí
.

:)m7om the File menu, the code that handles the mouse-down °dONLNd…
;ä
G (
Däevent uses the u`°dONLNdÿ
;À
G
%)AStandardGetFileo¿°dONLNdÁ
;
%
G
1)Z pr∂‡°dONLNdÍ
;
1
G
O)ocedurN °dONLNd
;
P
G
ƒ)e to let the user choose a fia¿°dONLNd
;
ƒ
G
Ô)tle; it then °dONLNd
Hä
Tù(
Qäcalls˛°dONLNd
Hù
Tü)
 ~°dONLNd
H†
T‹)
MyOpenFilez@°dONLNd)
H‹
T
)<, passing the fi)`°dONLNd9
H

T
d)@le system specifi2†°dONLNdJ
H
d
T
Ö)Hcation rYÄ°dONLNdR
H
Ö
T
ó)!ecorÕ‡°dONLNdV
H
ó
T
£)d r.†°dONLNdY
H
§
T
÷)eturned by °dONLNdd
Uä
a‰(
^äStandardGetFilez`°dONLNds
U‰
a
Å)Z%. By isolating code that performs a r•`°dONLNdò
U
Å
a
œ)ùequested action fr8`°dONLNd™
U
–
a)Oom code that °dONLNd∑
bä
nÏ(
käinteracts with the userÄ°dONLNdŒ
bÏ
n
≈)b2, you can easily adapt your application to handle Ƈ°dONLNd
b
≈
n)ŸApple events °dONLNd
oä
{°(
xäthat r °dONLNd
o¢
{
)equest the same actionÁ‡°dONLNd)
o

{

)c. °dONLNd,
Åä
çõ(
ääNotÜ¿°dONLNd/
Åõ
ç∏)e the u4‡°dONLNd6
Åπ
çƒ)se ªÄ°dONLNd9
Ń
çœ)of ‡°dONLNd<
Å–
ç‡)the b@°dONLNd@
Ň
ç
.)AEDisposeDesc]`°dONLNdM
Å
.
ç)N6 function to dispose of the descriptor list when your °dONLNdÉ
éä
öfl(
óähandler no longer rȆ°dONLNdñ
éfl
öˆ)Uequir‡°dONLNdõ
é˜
ö
?)es the data in it. ˘‡°dONLNdÆ
é
>
ö
D)G
Y∫`°dONLNdØ
é
D
ö
≥)our handler should also r{¿°dONLNd»
é
¥
ö
Ÿ)p    eturn a r‡°dONLNd—
é
⁄
ö    )&esult code.


∏H
ø4
πH
ø 
∫ä
∫

ˇ·ˇ‚7^°dONLNd›
´ä
π
K(
µä"Handling the Print Documents Eventˇˇˇˇˇˇ‘@(
µ
4
°dONLNd

øä
Àê(
Ȋ
Tµ¿°dONLNd
øè
À)Vo handle the Print Documents event, your application should extract information about °dONLNdX
Ãä
ÿ
(
’äthe documents to be printed frÆ°dONLNdv
Ã

ÿ
>)Ü
om the dirº†°dONLNdÄ
Ã
>
ÿ
z).ect parameteråÄ°dONLNdç
Ã
z
ÿ
⁄)<, then print the specifi˜†°dONLNd•
Ã
⁄
ÿ
Á)`ed °dONLNd®
Ÿä
Âø(
‚ädocuments. °dONLNd¥
Îä
˜
N*.If your application can interact with the userá¿°dONLNd‚
Î
N
˜
‡)ƒ!, it should open windows for the °dONLNd
¯ä
Y(
ä/documents, display a Print dialog box for the fig °dONLNd3
¯
Z
Û)–#rst document, and use the settings °dONLNdVä†(äenterÏ°dONLNd[†
)ed by the user for the fil°dONLNdt
)g@rst document to print all the documents. If user interaction is °dONLNd¥ä
E(ä*not allowed, your application may either rk@°dONLNdfi
E
|)ªeturn the err°°dONLNdÎ
|
á)7or â °dONLNdÓ
à)errAENoUserInteractionć°dONLNd    )Ñ
 °dONLNd    ä+
g((ä3or print the documents using default settings. See     ¿°dONLNd    8
h+
©)fi“Interacting W' °dONLNd    F
©+
‹)Aith the User¿°dONLNd    R
‹+
„)3,”É¿°dONLNd    T
„+) which °dONLNd    [,ä8∑(5ä
begins on û°dONLNd    e,∑8Œ)-page x‡°dONLNd    j,œ8·)4-45ÿ°dONLNd    n,·8
s)", for information about using the u °dONLNd    ê,
t8
‡)ìAEInteractWithUsern`°dONLNd    ¢,
‡8)l function to °dONLNd    Ø9äEË(Bäinteract with the userfiÄ°dONLNd    ≈9ÁEÈ)]
.^Ä°dONLNd    Δ9ÍEÏ)
 °dONLNd    »KäW
(Tä Note that your application can r‚`°dONLNd    ËK
W
n)çemain open after prÊ°dONLNd    ˚K
nW)W$ocessing the Print Documents event; °dONLNd
Xäd∫(aä    when appr冰dONLNd
(X∫d
ì)02opriate, the Finder sends your application a Quit ˛‡°dONLNd
ZX
ìd
‰)ŸApplication event °dONLNd
leäq
y(nä5immediately after sending it a Print Documents event.°dONLNd
¢wäÉ
u*3The handler for the Print Documents event shown in ¸`°dONLNd
’w
uÉ
£)ÎListing 4-7ú†°dONLNd
‡w
§É
©)/ i°dONLNd
‚w
™É)s similar to the handler °dONLNd
˚Ñäê
(çäfor the Open Documents even5¿°dONLNdÑ
ê
r)Öt, except that it prints tŸ‡°dONLNd0Ñ
rê
∂)che documents r0‡°dONLNd>Ñ
∑ê
À)Eeferrœ†°dONLNdCÑ
Àê
ˇ)ed to in the °dONLNdPëäùñ(öädirI °dONLNdSëóù”)ect parameter°dONLNd`ë”ù’)<
.ˇ†@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-18    )B    Handling ê)&Apple Events4^*¿
¯

g*n
¯4g*n
¯"h*_

ˇ·ˇ‚7^
°dONLNd\lgò(dlListing 4-7°dONLNd\∞g∂)D
A0°dONLNd\∂g
P)& handler for the Print Documents event,
Courier
°dONLNd5vlÇ
J(l%FUNCTION MyHandlePDoc (theAppleEvent,r °dONLNdZv
JÇ
P)fi
 q¿°dONLNd[v
PÇ
º)reply: AppleEvent;°dONLNdpÑêêñ(çê
 °dONLNdvÑÍê)Z
 †°dONLNdwÑêˆ)
 @°dONLNdxшê
∞)handlerRefcon: LongInt): OSErr;°dONLNdòílû~(õlVAR°dONLNdù†~¨®+myFSS: °dONLNd߆¥¨∫)6
 °dONLNd¨†¸¨
&)HFSSpec;°dONLNdµÆ~∫¥(∑~    docList: °dONLNd¡Æ¥∫∫)6
 °dONLNdΔƸ∫
>)HAEDescList;°dONLNd”º~»Í(≈~myErr, ignoreErr: y@°dONLNd˺ͻ)l
 °dONLNd̺¸»
 )OSErr;°dONLNdı ~÷(”~index, itemsInList:°dONLNd
 ¸÷
,)~LongInt;°dONLNd
ÿ~‰Δ(·~actualSize: °dONLNd
+ÿ͉)l
 °dONLNd
-ÿ¸‰
)Size;°dONLNd
4Ê~Ú®(Ô~keywd: °dONLNd
>Ê¥Ú∫)6
 °dONLNd
CʸÚ
8)H
AEKeyword;°dONLNd
OÙ~
“(˝~returnedType: z¿°dONLNd
^Ù“
ÿ)T
 °dONLNd
eÙ¸

2)*    DescType;°dONLNd
o
l
ä(
lBEGIN°dONLNd
v
~

⁄+:{get the direct parameter--a descriptor list--and put it }°dONLNd
≤
~
*ÿ*{ into docList}°dONLNd
√
,~
8
»*7myErr := AEGetParamDesc(theAppleEvent, keyDirectObject,°dONLNd
:

F
å+êtypeAEList, docList);°dONLNd
H~
T
(
Q~IF myErr = noErr THEN °dONLNd3
V~
bú*BEGIN°dONLNd;
dê
p
z+'{check for missing required parameters}°dONLNde
rê
~
ò*,myErr := MyGotRequiredParams(theAppleEvent);°dONLNdî
Äê
å
*IF myErr = noErr THEN °dONLNd≠
éê
öÆ*BEGIN°dONLNd∂
ú¢
®
⁄+4{count the number of descriptor records in the list}°dONLNdÓ
™¢
∂
∞*-myErr := AECountItems (docList, itemsInList);°dONLNd
∏¢
ƒ*IF myErr = no{ °dONLNd,
∏
ƒ
)NErrz°dONLNd/
∏

ƒ
 ) THEN°dONLNd9
Δ¥
“
‘(
œ¥0{now get each descriptor record from the list, }°dONLNdn
‘¥
‡
Ú*5{ coerce the returned data to an FSSpec record, and }°dONLNd®
‚¥
Ó
\*{ print the associated file}°dONLNd…
¥
¸
t* FOR index := 1 TO itemsInList DO°dONLNdÓ
˛¥
“*BEGIN°dONLNd˘Δ
⁄+.myErr := AEGetNthPtr(docList, index, typeFSS, °dONLNd4
D&
Ú+~keywd, returnedType, @myFSS, °dONLNd^(
D4
ò*Sizeof(myFSS),z¿°dONLNdl(
ò4
û)T
 z`°dONLNdm(
û4
Ê)actualSize);°dONLNd6ΔB
>(?ΔIF myErr = noErr THExÄ°dONLNdì6
>B
D)x
N°dONLNdöDΔPÃ(MΔ
B†°dONLNdõDÃP‰)EGIN°dONLNd¶Rÿ^
Ü+myErr := MyPrintFile(@myFSS);°dONLNd `ÿl
b*IF myErr <> noErr THEN °dONLNdÈnÍz
™+ ; {handle error from MyOpenFile}°dONLNd|Δàÿ(ÖΔEND°dONLNdäΔñfi*ELSE°dONLNd#òÿ§
û+!; {handle error from AEGetNthPtr}°dONLNdI¶¥≤
8(Ø¥END; {of For index Do}°dONLNdb¥ê¿¢(ΩêENDˇ,6@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-19
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿,
Courier°dONLNd\ÆhΔ(eÆELSE°dONLNdj¿v
∂+); {handle error from MyGotRequiredParams}°dONLNd4xÆÑ
Ü(ÅÆ$ignoreErr := AEDisposeDesc(docList);°dONLNdZÜúíÆ(èúEND°dONLNd_îú†¥*ELSE°dONLNdf¢ÆÆ
Œ+0; {failed to get direct parameter, handle error}°dONLNdò∞úº
 (πúMyHandlePDoc := myErr;°dONLNdØæä ¢(«äEND;

ÈH4ÍH ÎäÎ

ˇ·ˇ‚7^°dONLNd¥‹äÍÍ*Handling the Quit ›@°dONLNdΔ‹ÈÍ
E)_Application Eventˇˇˇˇˇˇ‘@(Ê
4
°dONLNdŸä¸ê(˘ä
Tµ¿°dONLNd⁄è¸fi)o handle the Quit (Ä°dONLNdÏfl¸)PCApplication event, your application should take any actions that arm‡°dONLNd
/¸(˘e °dONLNd
1˝ä
    Œ(
änecessary befor∞@°dONLNd
@˝Œ
    
≈)D8e it is terminated (such as saving any open documents). ˛‡°dONLNd
x˝
≈
    
Û)˜Listing 4-8ü °dONLNd
É˝
Ù
    )/ shows °dONLNd
ä

ä

-(
ä%an example of a handler for the Quit A°dONLNd
Ø


-

~)£Application event.°dONLNd
¬
ä
(ª(
%ä    When appr5†°dONLNd
À
º
(
ï)22opriate, the Finder sends your application a Quit ߇°dONLNd
˝

ï
(
Ê)ŸApplication event °dONLNd
)ä
5(
2äTimmediately after a Print Documents event. The Finder also sends your application a °dONLNdc
6ä
B†*Quit Ø`°dONLNdh
6†
B
Æ)=Application event if the user chooses Restart or Shut Down frg¿°dONLNd•
6
Ø
B
Ì(
?
Øom the Finderl‡°dONLNd≤
6
Ó
B
˜)?’s °dONLNdµ
Cä
O (
LäSpecial menu. 


rH
z4
sH
z"
sH_

ˇ·ˇ‚7^
    °dONLNdƒ
hä
s∂*$Listing 4-8°dONLNd–
hŒ
s‘)D
A0°dONLNd—
h‘
s
&) handler for the Quit à°dONLNdÁ
h
%
s
i)QApplication event
°dONLNd˙
Çä
é
h(
ãä%FUNCTION MyHandleQuit (theAppleEvent,r °dONLNd
Ç
h
é
n)fi
 q¿°dONLNd 
Ç
n
é
⁄)reply: AppleEvent;°dONLNd7
ê“
úÿ(
ô“
 °dONLNd;
ê

ú
)6
 †°dONLNd<
ê

ú
)
 @°dONLNd=
ê

ú
Œ)handlerRefcon: LongInt): OSErr;°dONLNd]
ûä
™ú(
ßäVAR°dONLNdb
¨ú
∏¿+myErr:°dONLNdm
¨ˆ
∏
)ZOSErr;°dONLNdu
∫ú
ΔÍ(
√úuserCanceled:°dONLNdá
∫ˆ
Δ
&)ZBoolean;°dONLNdê
Ȋ
‘®(
—äBEGIN°dONLNdó
÷ú
‚
Ü+'{check for missing required parameters}°dONLNd¿
‰ú

§*,myErr := MyGotRequiredParams(theAppleEvent);°dONLNdÓ
Úú
˛Δ*IF myEr}`°dONLNdı
ÚΔ
˛‰)*r = n{Ä°dONLNd˙
Ú‰
˛
)oErr THExÄ°dONLNd
Ú

˛
 )0N °dONLNdú∫(    úBEGIN°dONLNdÆ
å+%userCanceled := MyPrepareToTerminate;°dONLNd6Æ(
&*IF userCanceled THEN°dONLNdN*¿6
n+MyHandleQuit := kUserCanceled°dONLNdn8ÆDΔ(AÆELSE°dONLNdvF¿R
D+MyHandleQuit := noErr;°dONLNdéTú`Æ(]úEND°dONLNdìbún¥*ELSE°dONLNdöpÆ|¥+
M†°dONLNdõp¥|
)yHandleQuit :z¿°dONLNd®p
|
2)N= myErr;°dONLNd±~ää¢(áäEND;ˇ"@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-20    )B    Handling ê)&Apple Events4^*¿
¯
°dONLNd\lhØ(elThe handler in ÿ†°dONLNd\Øh›)CListing 4-8x‡°dONLNd\fih
¿)/5 calls another function supplied by the application, °dONLNdOiluy(rlthe]`°dONLNdRizu|)
 ,
Courier›`°dONLNdSi|uÙ)MyPrepareToTerminate’‡°dONLNdgiÙu
fi)x5 function. This function saves the documents for any °dONLNdúvlÇÇ(lopen톰dONLNd†vÇÇÑ)
 †°dONLNd°vÖÇ»)windows and r˙¿°dONLNdÆv«Ç
£)B2eturns a Boolean value that indicates whether the e°dONLNd‡v
§Ç
Ú)›user canceled the °dONLNdÚÉlèß(ålQuit operatio·‡°dONLNdˇÉßèØ);n.3@°dONLNd

É∞è
Á)    I This is another example of isolating code for interacting with the user °dONLNd
Jêlús(ôlfrò‡°dONLNd
Lêsú˛)om the code that performs the r¿°dONLNd
kêˇú
C)åequested action‡°dONLNd
zê
Dú
^)E. By st≥ °dONLNd
Åê
^ú
a)
rë¿°dONLNd
Çê
bú
Ù)"ucturing your application in this °dONLNd
§ùl©y(¶lwa◊°dONLNd
¶ùy©~)
yJ`°dONLNd
ßù~©Á), you can use the same r¢Ä°dONLNd
øùÁ©
)ioutine to ra¿°dONLNd
 ù
©
Ä).espond to a user action (; °dONLNd
„ù
Å©
fi)lsuch as choosing the °dONLNd
¯™l∂Ä(≥lQuitç¿°dONLNd
¸™Ä∂Ç)
 ¿°dONLNd
˝™É∂π)
command fr!Ä°dONLNd™π∂
E)6 om the File menu) or to the corrV†°dONLNd'™
E∂
v)å
esponding ,Ä°dONLNd1™
v∂
Õ)1Apple event. (For a °dONLNdE∑l√º(¿ldescription of the à °dONLNdX∑º√
.)PMyGotRequiredParamsÅ°dONLNdk∑
.√
c)r function, se‡°dONLNdx∑
d√
k)6e _Ä°dONLNdz∑
k√
z)“W¢ °dONLNd|∑
y√
ì)riting *°dONLNdÉ∑
î√
Œ)Apple Event °dONLNdèƒl–¬(ÕlHandlers” on page ¡‡°dONLNd°ƒ¬–‘)V4-33¿°dONLNd•ƒ’–◊)
.ï¿°dONLNd¶ƒ◊–⁄)
)

fi*Ï
¯4fl*Ï
¯
°dONLNd®fllÁã(ÂlIMPORT
ç°dONLNdÆflãÁõ)ANT

ˇ·ˇ‚7^
°dONLNd≤Ílˆ‚(ÛlWhen your application is rå°dONLNdÃÍ‚ˆ
g)v!eady to quit, it should call the [†°dONLNdÌÍ
hˆ
™)ÜExitToShellWÄ°dONLNd¯Í
™ˆ
¨)B
 °dONLNd˘ˆl
u(ˇlprG °dONLNd˚ˆv
î)
ocedurfi`°dONLNd
ˆî
¢)e fr@‡°dONLNdˆ£

))om the main event loop, not fr:`°dONLNd#ˆ
)

¨)Üom your handler for the Quit °dONLNd@
l
¿(
lApplication event. ù¿°dONLNdS
¿
Δ)T
Y^@°dONLNdT
Δ

£)3our application should quit only after the handler °dONLNdá
l
o(
l
rE°dONLNdà
p
é)eturns Ÿ °dONLNdè
é
¨)noErr◊@°dONLNdî
¨
Ú) as its function rO@°dONLNd¶
Û


)Gesult.,Zapf Dingbats¿°dONLNd≠



)
s


>*
E
¯4
?*
E
¯ 
@l
@
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdØ
/l
>•(
:l    Handling ò~°dONLNd∏
/•
>
¶)9(Apple Events Sent by the Edition Managerˇˇˇˇˇˇ€r(
:

4
°dONLNd‚
El
Q (
NlIf your application pr.¿°dONLNd¯
EÀ
Q
‡)_@ovides publish and subscribe capabilities, it should handle the °dONLNd8
Rl
^
{(
[l=Apple events sent by the Edition Manager in addition to the rfl@°dONLNdu
R
{
^
í(
[
{equirˆÄ°dONLNdz
R
í
^
ü)ed ˝Ä°dONLNd}
R
ü
^
fi)Apple events. W†°dONLNdã
R
fl
^
Â)@
Y °dONLNdå
R
Â
^
ˆ)our °dONLNdê
_l
k
(
hl%application should also handle the Cr
¿°dONLNdµ
_

k
‡)¶0eate Publisher event, which is described in the °dONLNdÂ
ll
xπ(
ul“Handling the Cr© °dONLNdı
lπ
x
)Meate Publisher Event”Q‡°dONLNd

l

x
J)` section on 
@°dONLNd
l
K
x
b)2page ‹ °dONLNd
l
b
x
t)4-220°dONLNd
l
u
x
w)
.°dONLNd!
~l
ä
3(
ál+The Edition Manager sends your application ʇ°dONLNdL
~
3
ä
)«(Apple events to communicate information °dONLNdt
ãl
ó
¬(
îlLabout the publishers and subscribers in your application’s documents. Specifi™`°dONLNd¡
ã
¬
ó
÷(
î
¬cally^¿°dONLNdΔ
ã
÷
ó
Î), the °dONLNdÃ
òl
§Œ(
°lEdition Manager uses ‡°dONLNd·
òœ
§
)c(Apple events to notify your application °dONLNd

Æl
µq(
¥l
n
°dONLNd
´x
∑
D)-when the information in an edition is updated°dONLNd:
¿l
«q(
Δl
n
°dONLNd<
Ωx
…
M)0when your application needs to write the data fr@°dONLNdl
Ω
N
…
 )÷om a publisher to an edition°dONLNdâ
“l
Ÿq(
ÿl
n
°dONLNdã
œx
€
û)Bwhen your application should locate a particular publisher and scrfl`°dONLNdÕ
œ
û
€
∏(
ÿ
ûoll thr~`°dONLNd‘
œ
π
€
‚)    ough the °dONLNd›
€x
Á„(
‰xdocument to that locatio6`°dONLNdı
€‰
ÁÈ)l
nˇ1"@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-21
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

jHp4jHp käk

ˇ·ˇ‚7^°dONLNd\äj
'(fäThe Section Read, Section W®@°dONLNd\
'j
«)ùrite, and Section Scroll Eventsˇˇˇˇˇˇ‘@)Ë
4
°dONLNd<pä|
E(yä+The following descriptions identify the thrφ°dONLNdgp
E|
Q)ªee °Ä°dONLNdjp
Q|))Apple events sent by the Edition Manager—°dONLNdì}äâÙ(ÜäSection Read, Section W,Ä°dONLNd™}Ùâ
K)jrite, and Section Scr`‡°dONLNdø}
Kâ)W.oll—and the actions they tell applications to °dONLNdÌääñ∞(ìäperform.°dONLNdVhätœ(qäSee the chapter Ú¿°dONLNdfhœt⁄)E“EÄ°dONLNdhh€t
¸)Adition Manager” in this book for details on how your application °dONLNd©uäÅØ(~äshould rT °dONLNd±uØÅ
)%espond to these events.
    °dONLNdˆ£äÆ
T(´ä-Section Read—read information into the specifi∞√°dONLNd
$£
TÆ
Ä)
ed sectionì°dONLNd
.£
ÅÆ
É)-
 Ç3°dONLNdˇˇ)
 
°dONLNd
>±äΩ∫(∫äEvent class,
CourierŸ°dONLNd
K±˘Ω
q)oSectionEventMsgClass°dONLNd
a¡äÕ±( äEvent IDŸ°dONLNd
k¡˘Õ
Y)oSectionReadMsgID°dONLNd
}—ä›ß(⁄äRequirE@°dONLNd
É—®›‚)ed parameter°dONLNd
î·ûÌ¡(ÍûKeywor¨`°dONLNd
ö·¡Ì…)#d:Ÿ°dONLNd
ù·˘Ì
S)8keyDirectObject°dONLNd
ØÒû˝Â(˙ûDescriptor type:Ÿ°dONLNd
¿Ò˘˝
A)[typeSectionH°dONLNd
œ

û
µ(

ûData:Ÿ°dONLNd
’

˘

)[
A†°dONLNd
÷





e) handle to the section rF‡°dONLNd
Ó


e

w)decorª@°dONLNd
Ú


w
)"d of the subscriber whose edition Ÿ°dONLNd
˘

|(
˘contains updated information°dONLNd2
ä
(’(
%äRequested actionŸ°dONLNdD
˘
(
ÿ)o1Update the subscriber with the new information fr∂ °dONLNdu

ÿ
(
˘)flom the Ÿ°dONLNd|
'˘
3
(
0˘edition.
    °dONLNdá
Hä
Sµ(
Pä    Section W™!°dONLNdê
Hµ
S
)+rite—write the specifiO°dONLNd¶
H

S
t)[ed section to an edition
°dONLNd¬
Vä
b∫(
_äEvent classŸ°dONLNdœ
V˘
b
q)oSectionEventMsgClass°dONLNdÂ
fä
r±(
oäEvent IDŸ°dONLNdÔ
f˘
r
_)oSectionWriteMsgID°dONLNd
vä
Çß(
äRequirE@°dONLNd
v®
Ç‚)ed parameter°dONLNd
Üû
í¡(
èûKeywor¨`°dONLNd
Ü¡
í…)#d:Ÿ°dONLNd"
ܢ
í
S)8keyDirectObject°dONLNd4
ñû
¢Â(
üûDescriptor type:Ÿ°dONLNdE
ñ˘
¢
A)[typeSectionH°dONLNdT
¶û
≤µ(
ØûData:Ÿ°dONLNdZ
¶˘
≤
)[
A†°dONLNd[
¶


≤
e) handle to the section rF‡°dONLNds
¶
e
≤
w)decorª@°dONLNdw
¶
w
≤
≈)d of the publisher°dONLNdã
∂ä
¬’(
øäRequested actionŸ°dONLNdù
∂˘
¬
)o
W†°dONLNdû
∂

¬
N)
rite the publisher…†°dONLNd∞
∂
O
¬
®)L’s data to its edition.
    °dONLNd 
׊
‚
Ç(
flä8Section Scroll—scroll through the document to the specifiÅ°dONLNd
◊
Ç
‚
Æ)¯
ed section
°dONLNd
Âä
Ò∫(
ÓäEvent classŸ°dONLNd
¢
Ò
q)oSectionEventMsgClass°dONLNd4
ıä
±(
˛äEvent IDŸ°dONLNd>
ı˘

e)oSectionScrollMsgID°dONLNdRäß(äRequirE@°dONLNdX®‚)ed parameter°dONLNdiû!¡(ûKeywor¨`°dONLNdo¡!…)#d:Ÿ°dONLNdr˘!
S)8keyDirectObject°dONLNdÑ%û1Â(.ûDescriptor type:Ÿ°dONLNdï%˘1
A)[typeSectionH°dONLNd§5ûAµ(>ûData:Ÿ°dONLNd™5˘A
)[
A†°dONLNd´5

A
e) handle to the section rF‡°dONLNd√5
eA
w)decorª@°dONLNd«5
wA
fl)d of the publisher to scrT °dONLNd‡5
‡A
ˆ)ioll to°dONLNdËEäQ’(NäRequested actionŸ°dONLNd˙E˘Q
)oScrN°dONLNd˝E
Q
)oll @°dONLNd
E
Q
")thrÌ°dONLNdE
!Q
:)ough J °dONLNd    E
;Q
‚)%the document to the publisher identifi˘†°dONLNd/E
‚Q)ß
ed by the Ÿ°dONLNd9P˘\
(Y˘specifiG °dONLNd@P
\
H)ed section r⁄°dONLNdLP
H\
Z)2ecorN`°dONLNdPP
[\
f)d. ˇ~@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-22    )B    Handling ê)&Apple Events4^*¿
¯

j*p
¯4j*p
¯ klk
¯

ˇ·ˇ‚7^°dONLNd\lj
.(fl#Handling the Create Publisher Eventˇˇˇˇˇˇ‘@(f
Ò
4
°dONLNd%pl|
Ù(yl[If your application supports publish and subscribe capabilities, it should also handle the °dONLNdÄ}lâw*Cr\°dONLNdÇ}wâ“)eate Publisher event.,
Courier2†°dONLNdˇˇ)\
 2@°dONLNdˇˇ)
 ≤@°dONLNdˇˇ)
 °dONLNdÙ
ºl
»ÿ(
≈lWhen your application rʆ°dONLNd
ºÿ
»
)leceives the Cr8¿°dONLNd
º

»
¶)>"eate Publisher event, it should cr~Ä°dONLNd;
º
¶
»
¡)êeate a °dONLNdB
…l
’ò(
“l
publisher ,@°dONLNdL
…ô
’
)-and write the publisherû`°dONLNdc
…


’
Ã)h0’s data to an edition. The data of the publisher¯‡°dONLNdì
…
À
’
Û)
, and the °dONLNdù
÷l
‚
(
fll$location and name of the edition, arG°dONLNd¡
÷
    
‚
!)ùe defiÇ¿°dONLNd«
÷
!
‚
R)ned by the O@°dONLNd“
÷
R
‚
±)1Apple event. If the Cr¿°dONLNdË
÷
≤
‚
Û)`eate Publisher °dONLNd˜
„l
Ô∂(
Ïlevent includes a â °dONLNd
„∂
Ô
)JkeyDirectObjectÉÄ°dONLNd
„

Ô
@)Z
 parameter◊ °dONLNd!
„
?
Ô
Í)/', then your application should publish °dONLNdH
l
¸
    (
˘l#the data contained in the parameter>‡°dONLNdk

    
¸
')ù    . If the Œ†°dONLNdt

'
¸
Å)keyDirectObject…°dONLNdÉ

Å
¸
‰)Z parameter is missing, °dONLNdö
˝l    
5(l-then your application should publish the currÔÄ°dONLNd«
˝
5    
Ù)…,ent selection. If the document doesn’t have °dONLNdÛ
lÖ(la curr/°dONLNd˘
Ü
])2ent selection, your handler for the event should r√ °dONLNd+

]
ù)◊eturn a nonzerA °dONLNd9

û
©)Ao r˚†°dONLNd<

©
ÿ)esult code.°dONLNdHl(ê(%l    If the Crο°dONLNdQê(
)$ eate Publisher event includes a ˛@°dONLNdq
(
ç)ãkeyAEEditionFileLoc˜ °dONLNdÑ
ç(
Ω)r
 parameterJ¿°dONLNdé
Ω(
Ÿ)0, your °dONLNdï)l5
Ô(2lWapplication should use the location and name contained in the parameter as the default °dONLNdÏ6lB
*)location and name of the edition. If the ¿°dONLNd6
B
å)ÆkeyAEEditionFileLoc
†°dONLNd(6
åB
Ô)r parameter is missing, °dONLNd?ClO
Á(LlTyour application should use the default location and name your application normally °dONLNdìPl\

*%uses to specify the edition container‡°dONLNd∏P

\
)û
.°dONLNd∫blnö(klListing 4-9 @°dONLNd≈bõn
)/ shows a handler for the Cr†°dONLNd‡b
n
Î)x2eate Publisher event. This handler checks for the °dONLNdol{Δ(xlkeyDirectObjectz`°dONLNd!oΔ{
)Z parameter and the ’‡°dONLNd4o
{
é)VkeyAEEditionFileLocŒ¿°dONLNdGo
é{
æ)r
 parameter"`°dONLNdQo
æ{
Û)0. If either of °dONLNd`|làº(Ölthese is not specifi¿°dONLNdt|Ωà
π)Q:ed, the handler uses default values. The handler uses the °dONLNdÆâlï±(ílapplication-defi|‡°dONLNdæâ≤ïÏ)Fned function A‡°dONLNdÀâÌï
A);DoNewPublisher<†°dONLNdŸâ
Aï
F)T tˇ°dONLNd€â
Fï
V)o cr)¿°dONLNdflâ
Wï
Ï)$eate the publisher and its edition, °dONLNd    ñl¢t(ülcrµ@°dONLNd    ñt¢µ)eate a section r∏`°dONLNd    ñµ¢«)Aecor,¿°dONLNd    ñ»¢
C)d, and update other data strh@°dONLNd    5ñ
C¢
Z){ucturÓ °dONLNd    :ñ
Z¢
Ó)!es associated with the document. °dONLNd    [£lر(¨lSee the chapter Ú¿°dONLNd    k£±غ)E“EÄ°dONLNd    m£ΩØ
)dition Manager”ñ@°dONLNd    |£
Ø
)I in–°dONLNd    £
Ø
)
 P°dONLNd    Ä£
Ø
?)
this book 䇰dONLNd    ä£
?Ø
ü)+for an example of the π`°dONLNd    †£
üØ
Û)`DoNewPublisher¥ °dONLNd    Æ£
ÛØ
ı)T
 °dONLNd    Ø∞lºë(πlfunctioné@°dONLNd    ∑∞ëºì)%
.
    °dONLNdòñl°
(ûl"Create Publisher—create a publisheÈŸ°dONLNd∫ñ
°
)ô
r
°dONLNdø§l∞ú(≠lEvent classŸ°dONLNdç€∞
/)okAEMiscStdSuit”¿°dONLNd⁄§
/∞
5)T
e°dONLNd›¥l¿ì(ΩlEvent IDŸ°dONLNdÁ¥€¿
A)okAECreatePublishe“†°dONLNd¯¥
A¿
G)f
r°dONLNd˚ƒl–â(ÕlRequirE@°dONLNd

ƒä–ƒ)ed parameterŸ°dONLNd
ƒ€–Û)QNone°dONLNd
‘l‡√(›lOptional parameter°dONLNd
,‰Ä£+Keywor¨`°dONLNd
2‰£´)#d:Ÿ°dONLNd
5‰€
5)8keyDirectObject°dONLNd
GÙÄ
«(˝ÄDescriptor type:Ÿ°dONLNd
XÙ€

M)[typeObjectSpecifier°dONLNd
n
Ä
ó(
ÄData:Ÿ°dONLNd
t
€

#)[An object specifi؇°dONLNd
Ö

$

3)Ier r± °dONLNd
â

3

E)ecor%Ä°dONLNd
ç

F

~)d that specifiÄ°dONLNd
õ



ö)9es the ã °dONLNd
¢

ö

Ô)Apple event object Ÿ°dONLNd
µ
€

Í(
€Aor objects to publish. If this parameter is omitted, publish the Ÿ°dONLNd
ˆ
€
&Ì*curr°dONLNd
˙
Ó
&
')ent selection.°dONLNd

*l
6√(
3lOptional parameter°dONLNd!
:Ä
F£+Keywor¨`°dONLNd'
:£
F´)#d:Ÿ°dONLNd*
:€
F
M)8keyAEEditionFileLoc°dONLNd@
JÄ
V«(
SÄDescriptor type:Ÿ°dONLNdQ
J€
V
)[    typeAlias°dONLNd]
ZÄ
fó(
cÄData:Ÿ°dONLNdc
Z€
f
)[
An alias rD`°dONLNdm
Z

f
)+ecor∏¿°dONLNdq
Z

f
œ),d that contains the location of the edition Ÿ°dONLNdù
e€
q
(
n€container to cr5†°dONLNd¨
e

q
Ú)@4eate. If this parameter is omitted, use the default Ÿ°dONLNd‡
p€
|
&(
y€edition containerJÄ°dONLNdÒ
p
&
|
()K
.°dONLNdÙ
Äl
å∑(
âlRequested action∑Ÿ°dONLNd
Ä€
åÊ)oCrµ°dONLNd
ÄÊ
å
k)eate a publisher for the specifiπÛ°dONLNd(
Ä
k
å
÷)Öed data using the specifi8œ°dONLNdA
Ä
◊
å
˘)led loca-‘¯Ÿ°dONLNdI
å€
ò
](
ï€tion for the edition container)`°dONLNdg
å
]
ò
«)Ç. If the data isn’t specifiÆò°dONLNdÇ
å
«
ò
˘)jed, publishX9Ÿ°dONLNdé
ò€
§˛(
°€the currΩô°dONLNdñ
ò˛
§
Î)#:ent selection. If the location of the edition isn’t specifisö°dONLNd—
ò
Ï
§
˘)Óed,Ÿ°dONLNd’
§€
∞
D(
≠€use the default location.ˇ*˙@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-23
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHn4gHn"hH_

ˇ·ˇ‚7^    °dONLNd\äg∂(däListing 4-9°dONLNd\Œg‘)D
A0°dONLNd\‘g
n)' handler for the Create Publisher event,
Courier
°dONLNd6väÇ
»(ä5FUNCTION MyHandleCreatePublisherEvent (theAppleEvent,°dONLNdyÑ
tê
Ê+Íreply: AppleEvent; °dONLNdöí
tû
¯*handlerRefcon: LongIntw¿°dONLNd∞í
¯û
˛)Ñ
)°dONLNdø†
t¨
Ä(©
t: @°dONLNd¡†
Ĩ
§)OSErr;°dONLNd»Æä∫ú(∑äVAR°dONLNdœºú»Δ+myErr: °dONLNdfiº
,»
P)êOSErr;°dONLNdÊ ú÷Í(”úreturnedType:°dONLNd˚ 
,÷
b)ê    DescType;°dONLNd
ÿú‰
(·úthePublisherDataDesc:°dONLNd
#ÿ
,‰
V)êAEDesc;°dONLNd
,ÊúÚfi(ÔúactualSize:°dONLNd
;ʉÚÍ)H
 °dONLNd
@Ê
,Ú
\)HLongInt;°dONLNd
JÙú
¸(˝úpromptForDialog:°dONLNd
bÙ
,

\)êBoolean;°dONLNd
l
ú
(
úthisDocument: °dONLNd
Ç

,

ò)êMyDocumentInfoPtr;°dONLNd
ñ
ú
“(
ú    preview: °dONLNd
ß

,

\)êHandle; °dONLNd
±
ú
*ˆ(
'úpreviewFormat: °dONLNd
»

,
*
t)êFormatType; °dONLNd
÷
,ú
8
(
5údefaultLocation: °dONLNd
Ô
,
,
8
™)êEditionContainerSpec;°dONLNd
:ä
F®(
CäBEGIN°dONLNd
Hú
T
V+MyGetDocumentPtr(thisDocument);°dONLNd-
Vú
b
Ï*8myErr := AEGetParamDesc(theAppleEvent, keyDirectObject, °dONLNdo
d
,
p
™+êtypeObjectSpecifier, °dONLNdé
r
,
~
∞*thePublisherDataDesc);°dONLNd¶
Äú
åÍ(
âúCASE myErr OF°dONLNd∂
éÆ
ö
 +errAEDescNotFound: °dONLNdÃ
úÆ
®Ã*BEGIN°dONLNd’
™¿
∂+8{use the current selection as the publisher and set up }°dONLNd
∏¿
ƒ*6{ info for later when DoNewPublisher displays preview}°dONLNdK
Δ¿
“
Ï*2preview := MyGetPreviewForSelection(thisDocument);°dONLNdÅ
‘¿
‡
P*previewFormat := 'TEXT';°dONLNdú
‚Æ
ÓΔ(
ÎÆEND;°dONLNd£
Æ
¸ÿ*noErr: °dONLNdÆ
˛¿

Ú+3{use the data in keyDirectObject parameter as the }°dONLNdÂ¿
™*'{ publisher (which is returned in the }°dONLNd¿&
*7{ thePublisherDataDesc variable), and set up info for }°dONLNdK(¿4
Œ*-{ later when DoNewPublisher displays preview}°dONLNd|6¿B*8MySetInfoForPreview(thePublisherDataDesc, thisDocument, °dONLNdªDˆP¸+6
 °dONLNdøD
,P
2)6
 †°dONLNd¿D
2P
») preview, previewFormat);°dONLNd‹RÆ^‰([Æ    OTHERWISE°dONLNdË`ÆlÃ*BEGIN°dONLNdÒn¿z
§+&MyHandleCreatePublisherEvent := myErr;°dONLNd|¿à
í*#Exit(MyHandleCreatePublisherEvent);°dONLNdAäÆñÃ(ìÆEND; °dONLNdHòú§¥(°úEND;°dONLNdN¶ú≤
™*-myErr := AEDisposeDesc(thePublisherDataDesc);ˇf@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-24    )B    Handling ê)&Apple Events4^*¿
¯,
Courier
°dONLNd\~h
‡(e~;myErr := AEGetParamPtr(theAppleEvent, keyAEEditionFileLoc, °dONLNdDj¸v
å+~ typeFSS, returnedType, °dONLNdex¸Ñ
ò* @defaultLocation.theFile,°dONLNdàܸí
™* SizeOf(FSSpec), actualSize);°dONLNdßî~†Ã(ù~CASE myErr OF°dONLNd∑¢êÆ
+errAEDescNotFound: °dONLNdŒ∞¢º
‘+3{use the default location as the edition container}°dONLNd
æ¥ 
Œ+/myErr := MyGetDefaultEditionSpec(thisDocument, °dONLNd
EÃ
zÿ
‡+ΔdefaultLocation);°dONLNd
Y⁄êÊ∫(„ênoErr: °dONLNd
cËêÙÆ*BEGIN°dONLNd
n˸Ù
‘)l${the keyAEEditionFileLoc parameter }°dONLNd
õˆ¸

∞*{ contains a default location}°dONLNd
Ω
¢

ò(
¢)defaultLocation.thePart := kPartsNotUsed;°dONLNd
Í
¢

¬*0defaultLocation.theFileScript := smSystemScript;°dONLNd
 ê
,®(
)êEND;°dONLNd$
.ê
:Δ*    OTHERWISE°dONLNd0
<ê
HÆ*BEGIN°dONLNd9
J¢
V
Ü+&MyHandleCreatePublisherEvent := myErr;°dONLNdc
X¢
d
t*#Exit(MyHandleCreatePublisherEvent);°dONLNdâ
fê
rÆ(
oêEND; °dONLNdê
t~
Äñ(
}~END;°dONLNdñ
Ç~
é
Ü*,myErr := MyGotRequiredParams(theAppleEvent);°dONLNdƒ
ê~
ú
*IF myErr <> noErr THEN°dONLNd‹
û~
™ú*BEGIN°dONLNd‰
¨ê
∏
t+&MyHandleCreatePublisherEvent := myErr;°dONLNd
∫ê
Δ
b*#Exit(MyHandleCreatePublisherEvent);°dONLNd2
»~
‘ñ(
—~END;ˇ˛Öˇ°dONLNd8
÷~
‚
€*;myErr := AEInteractWithUser(kAEDefaultTimeout, gMyNotifyRec˚›°dONLNds
÷
€
‚
Ì(
fl
€Ptr˙Ω°dONLNdv
÷
Ì
‚
˜), °dONLNdÑ
‰
2

ò(
Ì
2@MyIdleFunction);°dONLNdó
Ú~
˛
Ü(
˚~,IF myErr = noErr THEN promptForDialog := TRUoÄ°dONLNd√
Ú
Ü
˛
å(
˚
Ü
E°dONLNdÀÿfi(    ÿ
 †°dONLNdÃfi‰)
 @°dONLNdÕ‰
ò)ELSE promptForDialog := FALSE;°dONLNdÌ~
»(~7myErr := DoNewPublisher(thisDocument, promptForDialog, °dONLNd.
(
û+êpreview, previewFormat, °dONLNdP*
6
t*defaultLocation);°dONLNdc8~D
Ï(A~={add keyErrorNumber and keyErrorString parameters if desired}°dONLNd°FlR~(OlEND~‡°dONLNd§F~RÑ)
;°dONLNd¶^lj®(glNote that the ‡°dONLNd¥^©j
Q)=MyHandleCreatePublisherEvent˘`°dONLNd–^
Pj
Ç)ß handler in ñ@°dONLNd‹^
Éj
±)3Listing 4-96Ä°dONLNdÁ^
≤j
⁄)/
 uses the °dONLNdÒklwÿ(tlAEInteractWithUsery@°dONLNdkÿw
fi)l< function to determine whether user interaction is allowed. °dONLNd?xlÑu(ÅlIf ≤`°dONLNdBxuÑÉ)    so, d‡°dONLNdFxÑÑ‹)the handler sets the ¿°dONLNd[x›Ñ
7)YpromptForDialog °dONLNdjx
7Ñ
j)Z variable to ı‡°dONLNdwx
jÑ
Ç)3TRUEÙ`°dONLNd{x
ÇÑ
⁄), indicating that the °dONLNdëÖlë¿(élDoNewPublisherz¿°dONLNdüÖ¿ë
ª)T; function should display the publisher dialog box. If not, ˇ;@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-25
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh‚(eäthe handler sets the ,
Courier#‡°dONLNd\„h
=)YpromptForDialog@°dONLNd$\
=h
p)Z variable to °dONLNd1\
qh
è)4FALSE °dONLNd6\
èh
∑)
, and the Ÿ†°dONLNd@\
∑h)(DoNewPublisher‘`°dONLNdN\h)T
 °dONLNdOiäu„(räfunction does not prˆÄ°dONLNdci„u
Ú)Y>ompt the user for the location or name of the edition. For mor~`°dONLNd°i
Ûu
˙(r
Ûe °dONLNd£väÇ›(äinformation about Ç°dONLNdµv›Ç
I)SAEInteractWithUserΩ‡°dONLNd«v
HÇ
])k, see  °dONLNdÕv
^Ç
ü)“Interacting W+Ä°dONLNd€v
üÇ
“)Aith the User °dONLNdÁv
“Ç
Ÿ)3,”à °dONLNdÈv
ŸÇ
˘) which °dONLNdÉäè∑(åä
begins on û°dONLNd˙É∑èŒ)-page x‡°dONLNdˇÉœè·)4-45ÿ°dONLNd
É·èÊ). ÿ°dONLNd
ÉÊèË)
 

¥Hª4µHª ∂ä∂

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd
•ä¥œ(∞äGetting Dat¿˙°dONLNd
•œ¥
)E
a Out of a“Δ°dONLNd
•
¥
)<n rb°dONLNd
•
¥
_)Apple Eventˇˇˇˇˇˇ€r)¯
4
°dONLNd
+ªä«ê(ƒä
T†¿°dONLNd
,ªê«ù)he ]`°dONLNd
/ªù«
)Apple Event Manager storF °dONLNd
Gª
«
∫)u'es the parameters and attributes of an Ÿ °dONLNd
nª
∫«)®Apple event in a °dONLNd
»ä‘
(—äformat that is internal to the v‡°dONLNd
û»
‘
i)~Apple Event Managerh`°dONLNd
±»
i‘
n)a. :¿°dONLNd
≥»
n‘
t)
Y˚@°dONLNd
¥»
s‘
í)ou use '@°dONLNd
ª»
ì‘
˜) Apple Event Manager °dONLNd
œ’ä·ƒ(fiäfunctions to rH °dONLNd
›’≈·
);etrieve the data fr=°dONLNd
’
·
1)Nom an ˘Ä°dONLNd
ˆ’
0·
Ä)Apple event and rˆ`°dONLNd’
Ä·)P eturn it to your application in °dONLNd'‚äÓè(Îä
a°dONLNd(‚èÓë)
 °dONLNd)‚íÓ
!) format your application can use.°dONLNdJÙä
¡(˝äMost of the fd¿°dONLNdWÙ¬

)8unctions that rw@°dONLNdfÙ


?)@etrieve data fr¿°dONLNduÙ
@

P)>om y‡°dONLNdxÙ
P

ˆ)$Apple event parameters and attribute˙@°dONLNdúÙ
ˆ

)¶s a∑@°dONLNdüÙ
)
r|@°dONLNd†Ù
)e °dONLNd¢

ä

(

ä"available in two forms: one that rq‡°dONLNdƒ




`)íeturns the desir3 °dONLNd‘


a

≥)Eed data in a specifiûÄ°dONLNdË


≥

œ)Red buf∏‡°dONLNdÓ


œ
)fer and one °dONLNd˙
ä
°(
äthat r °dONLNd
¢
˚)eturns a descriptor réÄ°dONLNd
˚

)Yecor‡°dONLNd



÷)-d containing the same data. For example, the °dONLNdF
ä
'ÿ(
$äAEGetParamPtr{ °dONLNdS
ÿ
'
9)N function uses a specifY‡°dONLNdj

9
'
X)aied buf\†°dONLNdq

X
'
u)fer to r頡dONLNdy

u
'
¸)eturn the data contained in an °dONLNdò
(ä
4(
1äApple event parameter`°dONLNd≠
(
4
)f
, and the ˇ°dONLNd∑
(

4
l)(AEGetParamDesc„†°dONLNd≈
(
l
4
ö)T function r∂‡°dONLNd–
(
ö
4
¯).eturns the descriptor °dONLNdÊ
5ä
Aç(
>ä
rE°dONLNdÁ
5é
A†)ecorπ`°dONLNdÎ
5†
A€)d for a specifi@°dONLNd˙
5‹
A
)<ed parameter∏@°dONLNd
5

A
):. °dONLNd    
Gä
Sê(
Pä
Y@Ä°dONLNd

Gê
S’)ou can also use I°dONLNd
G’
S
z)E#Apple Event Manager functions to ge”¿°dONLNd=
G
z
S
∏)•t data out of d`°dONLNdL
G
π
S
Ê)?escriptor r[‡°dONLNdW
G
Ê
S
¯)-ecor–@°dONLNd[
G
¯
S)ds, °dONLNd_
Tä
`„(
]ädescriptor lists, and ∂ °dONLNdu
T„
`˜)YAE rfi °dONLNdy
T˜
`
    )ecorRÄ°dONLNd}
T


`
)ds. }†°dONLNdÅ
T

`
)
Y> °dONLNdÇ
T

`
)5ou use similar functions to put data into descriptor °dONLNd∑
aä
mç(
jä
rE°dONLNd∏
aé
m†)ecorπ`°dONLNdº
a†
m
)ds, descriptor lists, and H@°dONLNd÷
a
    
m
)iAE rp@°dONLNd⁄
a

m
/)ecor䠡dONLNdfi
a
/
m
;)ds.°dONLNd‚
sä
Á(
|äWhen your handler r퇰dONLNdı
sÁ

)]eceives an û†°dONLNd
s


Ø)/#Apple event, you typically use the l`°dONLNd#
s
∞

˛)öAEGetParamPtr™ °dONLNd0
s
˝
)M, °dONLNd2
Ää
å(
âäAEGetAttributePtrº@°dONLNdC
ÄÔ
åÙ)e, º@°dONLNdE
ÄÙ
å
H)AEGetParamDesc∑°dONLNdS
Ä
H
å
X)T, or ü °dONLNdX
Ä
Y
å
≈)AEGetAttributeDescò`°dONLNdj
Ä
≈
å
)l function to get °dONLNd{
çä
ôì(
ñäthì¿°dONLNd}
çì
ôœ)    e data out of tÜ@°dONLNdå
ç–
ô›)=he B‡°dONLNdè
ç›
ô
)Apple event.°dONLNdú
üä
´§(
®äSome ÙÄ°dONLNd°
ü§
´
ë)4Apple Event Manager functions let your application r›@°dONLNd’
ü
ë
´
˜)Ìequest that the data be °dONLNdÌ
¨ä
∏ç(
µä
rE°dONLNdÓ
¨é
∏
h)4eturned using any descriptor type, even if it is difh °dONLNd"
¨
h
∏
t)⁄ferJ†°dONLNd%
¨
t
∏
ã)ent fr¿‡°dONLNd+
¨
ã
∏)om the original descriptor °dONLNdF
πä
≈
(
¬ä&type. If the original data is of a dif&°dONLNdl
π
 
≈
,)ñferÄ°dONLNdo
π
,
≈
î)ent descriptor type, the ú`°dONLNdà
π
î
≈
¯)hApple Event Manager °dONLNdú
Δä
“–(
œäattempts to coerP °dONLNd¨
Δ—
“
")Gce the data to the rü¿°dONLNd¿
Δ
"
“
î)Qequested descriptor type. °dONLNd€
ÿä
‰÷(
·äFor example, the œ°dONLNdÏ
ÿ÷
‰
$)LAEGetParamPtr  °dONLNd˘
ÿ
$
‰
ª)N$ function lets you specify the desir°dONLNd
ÿ
º
‰)òed descriptor type °dONLNd0
Âä
Ò©(
Óäof the rο°dONLNd8
©
Ò
)esulting data as follows:°dONLNdR
¸äú(äVAR°dONLNdW
ú+theAppleEvent:°dONLNdk


J)lAppleEvent;°dONLNdxú$Í(!úreturnedType:°dONLNdäˆ$¸)Z
 °dONLNdå
$
>)    DescType;°dONLNdó&ú2fi(/úmultResult:°dONLNd®&
2
8)lLongInt;°dONLNd≤4ú@‰(=úactualSize: °dONLNdƒ4
@
&)lSize;°dONLNdÀBúN¿(KúmyErr:°dONLNd”B¿NΔ)$
 °dONLNdÿB
N
,)HOSErr;°dONLNdflZäf
»(cä5myErr := AEGetParamPtr(theAppleEvent, keyMultResult, °dONLNdh
t
+~
 †°dONLNdh
t
)
 @°dONLNdh
t
Œ)typeLongInteger, returnedType, °dONLNdEv
Ç
(

 †°dONLNdFv
Ç
)
 @°dONLNdGv
Ç
‘) @multResult, SizeOf(multResult),°dONLNdoÑ
ê
(ç

 †°dONLNdpÑ
ê
)
 @°dONLNdqÑ
ê
\)actualSize);ˇ%x@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-26    )B    Handling ê)&Apple Events4^*¿
¯
°dONLNd\lh€(elIn this example, the desirêÄ°dONLNd\€h
$)oed type is specifi&†°dONLNd,\
%h
])Jed in the thir‰@°dONLNd:\
]h
≥)8d parameter by the ,
Courier°dONLNdMiluΔ(rltypeLongIntegerz`°dONLNd\iΔu
*)Z descriptor type. This ré`°dONLNdti
*u
q)dequests that the ”`°dONLNdÖi
qu
’)GApple Event Manager °dONLNdôvlÇ~(lcoerÙ`°dONLNdùv~Çâ)ce Æ@°dONLNd†väÇ
2)+the data to a long integer if it is not alr4 °dONLNdÀv
3Ç
á)©eady of this type. T˛ °dONLNdflv
ÜÇ
ó)So pr∫¿°dONLNd„v
òÇ
≈)
event coer¸`°dONLNdÌv
ł
Ì)-    cion and °dONLNdˆÉlèÑ(ålensur$ °dONLNd˚ÉÖè
)#e that the descriptor type of the rƒÄ°dONLNd
É
è
Ê)ê3esult is of the same type as the original, specify °dONLNd
Qêlú¥(ôltypeWildCard{Ä°dONLNd
]ê¥úÊ)H for the thirV°dONLNd
jêÊú
)2d parameter≈`°dONLNd
uê
ú
)5
.°dONLNd
w¢lÆ(´lThe ]`°dONLNd
{¢ÆÁ)Apple Event Manager rQ@°dONLNd
ê¢ÁÆ˛)heturn(`°dONLNd
ï¢ˇÆ
#)
s, in the ¸Ä°dONLNd
ü¢
#Æ
k)$returnedType¯°dONLNd
´¢
kÆ
õ)H
 parameterK†°dONLNd
µ¢
õÆ
£)0, té°dONLNd
∏¢
£Æ
ı)he descriptor type °dONLNd
ÀØlªã(∏lof the rο°dONLNd
”Ø㪺)esulting da‡°dONLNd
fiØΩª«)2ta.À@°dONLNd
·Ø«ª
é)
- This is useful information when you specify ( °dONLNdØ
èª
◊)»typeWildCard#†°dONLNdØ
׻
ı)H as the °dONLNd"ºl»Å(≈ldesirO¿°dONLNd'ºÇ»
¢)Bed descriptor type; you can determine the descriptor type of the rv°dONLNdiº
¢»
Î(≈
¢esulting data by °dONLNdz…l’›(“lexamining this parameterU†°dONLNdí…›’fl)q
.°dONLNdî€lÁ(‰lThe ]`°dONLNdò€Á
)Apple Event Manager can coer¬@°dONLNd¥€
Á
:)àce many dif[°dONLNdø€
;Á
G)4fer=Ä°dONLNd¬€
GÁ
·)$ent types of data. For example, the °dONLNdÊËlÙ
 (Òl'Apple Event Manager can convert alias rü@°dONLNdË
 Ù
2)¥ecor†°dONLNdË
3Ù
Q)ds to fi1°dONLNdË
QÙ
ô)le system specifi:@°dONLNd*Ë
ôÙ
∫)Hcation ra °dONLNd2Ë
∫Ù
Ã)!ecor’Ä°dONLNd6Ë
ÃÙ
€)ds, °dONLNd:ıl


ˆ(˛l[integers to Boolean data types, and characters to numeric data types, in addition to other °dONLNdï
l

Æ*Kdata type conversions. For a complete list of the data types for which the Ï°dONLNd‡

Æ

Ë(

ÆApple Event °dONLNdÏ
l
†(
l
Manager prY °dONLNdˆ
†
“)4ovides coert°dONLNd

“

$)2cion handling, see ”Ä°dONLNd

$

*)R
T    @°dONLNd

*

t)able 4-1 on page 8Ä°dONLNd&

t

|)J4-å`°dONLNd(

|

Ü)43å`°dONLNd*

Ü

à)

.°dONLNd,
!l
-r(
*l
Tµ¿°dONLNd-
!q
-»)o perform data coerà °dONLNd@
!»
-
)Wcions that the ˝¿°dONLNdO
!

-
⁄)=-Apple Event Manager doesn’t perform, you can °dONLNd|
.l
:u(
7lprG °dONLNd~
.v
:—)
ovide your own coer¡@°dONLNdë
.—
:
#)[cion handlers. See ”‡°dONLNd§
.
#
:
2)R“WÄ°dONLNd¶
.
2
:
°)riting and Installing CoerÕ‡°dONLNd¿
.
°
:
Ê)ocion Handlers,”çÄ°dONLNdœ
.
Á
:
È)F
 °dONLNd–
;l
G∂(
Dlwhich begins on p`°dONLNd‡
;∑
GŒ)Kpage K@°dONLNdÂ
;œ
G·)4-41ü °dONLNdÈ
;·
G
D), for information on pr§Ä°dONLNd
;
D
G
©)coviding your own coerù‡°dONLNd
;
©
G
Á)ecion handlers.°dONLNd$
Ml
Y‚(
VlApple event parameters ar]¿°dONLNd=
M‚
Y

)ve keywor ¿°dONLNdE
M

Y
0))d-specifi˛Ä°dONLNdN
M
0
Y
p)%ed descriptor r√ °dONLNd]
M
q
Y
É)Aecor7Ä°dONLNda
M
Ñ
Y
ì)ds. b†°dONLNde
M
ì
Y
ô)
Y# °dONLNdf
M
ô
Y
∏)ou can °dONLNdm
Zl
f{(
cluseç¿°dONLNdp
Z{
f})
 ¿°dONLNdq
Z~
f“)AEGetParamDescÄ°dONLNd
Z“
f
3)T to get the descriptor rò °dONLNdó
Z
3
f
E)aecorÄ°dONLNdõ
Z
F
f
é)d of a parameterE@°dONLNd´
Z
é
f
’)H, or you can use °dONLNdº
gl
s∫(
plAEGetParamPtr{ °dONLNd…
g∫
s‡)N
 to get tha‡°dONLNd”
g·
s
)'e data out of tT`°dONLNd‚
g

s
^)=he descriptor rŒ†°dONLNdÒ
g
^
s
p)@ecorC°dONLNdı
g
q
s
π)d of a parameter{¿°dONLNd
g
π
s
‘)H. If an ° °dONLNd
g
‘
s
Ò)Apple °dONLNd
tl
Ä
-(
}l,event parameter consists of an object specifi– °dONLNd@
t
-
Ä
<)¡er r—`°dONLNdD
t
<
Ä
N)ecorE¿°dONLNdH
t
O
Ä
ê)d, you can use <†°dONLNdW
t
ë
Ä
«)B    AEResolve9@°dONLNd`
t
«
Ä
Ù)6
 and your °dONLNdj
Ål
ç
(
äl"own object accessor functions to r¬`°dONLNdå
Å

ç
g)îesolve the object specifi2`°dONLNd•
Å
h
ç
w)her r3†°dONLNd©
Å
w
ç
â)ecor®°dONLNd≠
Å
â
ç
Ò)d—that is, to locate the °dONLNdΔ
él
ö
(
ól(Apple event object it describes. For mor«@°dONLNdÓ
é

ö
u)Øe information about ‡°dONLNd
é
v
ö
¨)[    AEResolveÄ°dONLNd
é
¨
ö
fi)6 and object °dONLNd
õl
ß—(
§laccessor functions, see '¿°dONLNd/
õ“
ß·)f“Wj`°dONLNd1
õ‡
ß
)riting Object ®¿°dONLNd?
õ

ß
u)9Accessor Functions,”Ç¿°dONLNdS
õ
v
ß
√)] which begins on Û °dONLNdd
õ
√
ß
⁄)Mpage Œ°dONLNdi
õ
€
ß
Ì)6-28!‡°dONLNdm
õ
Ó
ß
Û). °dONLNdo
®l
¥§(
±lAttributes ar√¿°dONLNd|
®§
¥·)8e also keywor°†°dONLNdâ
®·
¥
)=d-specifi`°dONLNdí
®

¥
G)&ed descriptor rD°dONLNd°
®
H
¥
Z)Aecor∏`°dONLNd•
®
Z
¥
‘)ds, and you can use similar °dONLNd¡
µl
¡o(
æl
rE°dONLNd¬
µp
¡Ú)outines to get the descriptor rT°dONLNd·
µÚ
¡
)Çecor»`°dONLNdÂ
µ

¡
Ì)9d of an attribute or to get the data out of an attribute.°dONLNd
«l
”
/(
–l+The following sections show how to use the ,Ä°dONLNdJ
«
0
”
~)ƒAEGetParamPtrj@°dONLNdW
«
}
”
Ç)M, j@°dONLNdY
«
Ç
”
Ë)AEGetAttributePtr¶Ä°dONLNdj
«
Á
”
Ï)e, °dONLNdl
‘l
‡¿(
›lAEGetParamDescz¿°dONLNdz
‘¿
‡–)T, or b‡°dONLNd
‘—
‡
=)AEGetAttributeDesc\ °dONLNdë
‘
=
‡
“)l$ function to get the data out of an °dONLNdµ
·l
Ìá(
ÍlApple˝Ä°dONLNd∫
·á
Ìâ)
 }Ä°dONLNdª
·ä
̧)event.

*
¯4*
¯ l
¯

ˇ·ˇ‚7^°dONLNd¬
˛lÁ(lGetting Data Out of an 6Ä°dONLNdŸ
˛Á
c){Apple Event Parameterˇˇˇˇˇˇ‘@(
Ò
4
°dONLNdlr(l
Y@Ä°dONLNdÒr≥)ou can use the ȇ°dONLNd    ≥

)AAEGetParamPtr°dONLNd    


)N or M °dONLNd    

d)AEGetParamDescG‡°dONLNd    
d
Ï)T! function to get the data out of °dONLNd    @l+y((lan s°dONLNd    Cy+fl)Apple event parameter`°dONLNd    Xfl+
)f
. Use the º†°dONLNd    b
+
U)(AEGetParamPtr∑¿°dONLNd    o
U+
û)N function (or the _`°dONLNd    Å
ü+
·)JAEGetKeyPtr[@°dONLNd    å
·+
„)B
 °dONLNd    ç,l8
#(5l(function, which works the same way) to r⁄¿°dONLNd    µ,
#8
—)∑'eturn the data contained in a parameter`°dONLNd    ‹,
“8
Í)Ø. Use °dONLNd    ‚9lE|(Blthe ›`°dONLNd    Ê9|E–)AEGetParamDescÿ °dONLNd    Ù9–E
†)T/ function when you need to get the descriptor r≈Ä°dONLNd
#9
†E
≤)–ecor9‡°dONLNd
'9
≥E
Œ)d of a °dONLNd
.FlR
*(Ol.parameter or to extract the descriptor list frÎÄ°dONLNd
\F
*R
o)æom a parameter†°dONLNd
jF
pR
r)F
.°dONLNd
lXldß(alFor example, q†°dONLNd
yX®d˛)<suppose you need tц°dONLNd
ãX˛d
Ô)V8o get the data out of a Section Read event. The Edition °dONLNd
√elq
—(nlQManager sends your application a Section Read event to tell your application to r
†°dONLNde
“q
‰(n
“ead °dONLNdrl~“({lupdated information fr°°dONLNd.r“~
R)fom an edition into the specifi8`°dONLNdLr
S~
ç)Åed subscriberx@°dONLNdYr
ç~
≤):    . The dir} °dONLNdbr
≤~
Ò)%ect parameter °dONLNdplãá(àlof the »`°dONLNdwáã
P).Apple event contains a handle to the section r6†°dONLNd•
Qã
c) ecor´°dONLNd©
cã
¥)d of the subscriber»°dONLNdº
¥ã
π)Q. ö`°dONLNdæ
πã
ø)
YZ‡°dONLNdø
øã
)ou can use °dONLNd ålò|(ïlthe ›`°dONLNdŒå|ò )AEGetParamPtrÿÄ°dONLNd€å ò
b)N% function to get the data out of the ¸†°dONLNdå
bò
ö)òApple event.ˇ@ˆ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-27
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähê(eä
Y@Ä°dONLNd
\êh–)ou specify the Ä°dONLNd\–h
j)@#Apple event that contains the desir>¿°dONLNd3\
jh
§)öed parameterw¿°dONLNd?\
§h
€):, the keyworNÄ°dONLNdK\
€h
ˇ)7    d of the °dONLNdTiäuü(rädesirO¿°dONLNdYi†u⁄)ed parameterà¿°dONLNdei⁄u
Æ):2, the descriptor type the function should use to r#°dONLNdói
Øu
˘)’eturn the data, a °dONLNd©väÇò(äbuf5°dONLNd¨vôÇ√)fer to stor∂‡°dONLNd∑v√Ç
W)*$e the data, and the size of this buf≠°dONLNd€v
WÇ
¡)îfer as parameters to the ,
Courier›`°dONLNdÙv
¡Ç)jAEGetParamPtrÿÄ°dONLNd

vÇ)N
 °dONLNd
Éäè«(åäfunction. The  °dONLNd
É«è
)=AEGetParamPtr≈ °dONLNd
É
è
C)N function rò`°dONLNd
(É
Cè
◊).#eturns the descriptor type of the r≠ °dONLNd
KÉ
◊è)îesulting data °dONLNd
Yêäú
`(ôä4and the actual size of the data, and it places the r¸ °dONLNd
çê
`ú
◊)÷equested data in the specifi˜¿°dONLNd
©ê
ÿú
Ù)xed buf °dONLNd
Øê
ıú
)ferd‡°dONLNd
≤êú)
.°dONLNd
¥ßä≥ú(∞äVAR°dONLNd
πµú¡“+    sectionH:°dONLNd
»µ
¡
\)lSectionHandle;°dONLNd
ÿ√úœ(ÃútheAppleEvent:°dONLNd
Ï√
œ
J)lAppleEvent;°dONLNd
˘—ú›(⁄úreturnedType: °dONLNd—
›
>)l    DescType;°dONLNdflúΉ(ËúactualSize: °dONLNd*fl
Î
&)lSize;°dONLNd1Ìú˘¿(ˆúmyErr:°dONLNd9Ì¿˘Δ)$
 °dONLNd>Ì
˘
,)HOSErr;°dONLNdE
ä

‘(
ä7myErr := AEGetParamPtr(theAppleEvent, keyDirectObject, °dONLNdÑ



+~
 †°dONLNdÖ



)
 @°dONLNdÜ



˛)'typeSectionH, returnedType, @sectionH, °dONLNdµ
!

-
(
*

 †°dONLNd∂
!

-
)
 @°dONLNd∑
!

-
»)SizeOf(sectionH), actualSize);°dONLNd÷
9ä
E„(
BäIn this example, the ¿¿°dONLNdÎ
9„
E
=)YkeyDirectObjectª °dONLNd˙
9
=
E
a)Z keywor¥Ä°dONLNd

9
a
E
Ü)$d specifiæ`°dONLNd

9
Ü
E
µ)%es that the xÄ°dONLNd
9
∂
E)0AEGetParamPtrs†°dONLNd#
9
E)N
 °dONLNd$
Fä
R
1(
Oä&function should extract information frÀÄ°dONLNdJ
F
1
R
_)ß
om the dirªÄ°dONLNdT
F
_
R
†).ect parameter; H¿°dONLNdc
F
°
R
Ô)BAEGetParamPtrC‡°dONLNdp
F
Ô
R
ı)N rà‡°dONLNdr
F
ı
R)eturns °dONLNdy
Sä
_⁄(
\äthe data in the buf†°dONLNdå
S€
_
)Q
fer specifi‡°dONLNdó
S

_
1)+
ed by the _`°dONLNd°
S
1
_
a)+sectionH\`°dONLNd©
S
a
_
å)0 variable. °dONLNdµ
eä
qê(
nä
Y@Ä°dONLNd∂
eê
q≥)ou can r√¿°dONLNdæ
e≥
qˆ)#equest that the À¿°dONLNdŒ
eˆ
q
^)CApple Event Manager rø†°dONLNd„
e
^
q)h)eturn the data using the descriptor type °dONLNd
rä
~
(
{ä!of the original data or you can r
 °dONLNd-
r

~
Y)åequest that the      °dONLNd=
r
Y
~
œ)CApple Event Manager coer¨`°dONLNdU
r
œ
~)vce the data into °dONLNdf
ä
ã

(
àäa descriptor type that is dif]`°dONLNdÉ



ã
)wfer?‡°dONLNdÜ


ã
$)ent fr∂ °dONLNdå

$
ã
g)om the original^¿°dONLNdõ

h
ã
s)D. TîÄ°dONLNdû

r
ã
É)
o prQ °dONLNd¢

Ñ
ã
±)
event coerí¿°dONLNd¨

±
ã
Ã)-cion, so@°dONLNd≥

Õ
ã
˙)pecify the °dONLNdæ
åä
òü(
ïädesirO¿°dONLNd√
å†
ò˛)ed descriptor type as )†°dONLNdŸ
åˇ
ò
G)_typeWildCard% °dONLNdÂ
å
G
ò
I)H
.°dONLNdÁ
ûä
™ù(
ßäThe ª¿°dONLNdÎ
ûù
™Â)typeSectionH∑@°dONLNd˜
ûÂ
™
I)H descriptor type specifi\‡°dONLNd
û
J
™
})ees that the r‹°dONLNd
û
}
™
¯)3eturned data should be coerK`°dONLNd7
û
˘
™)|ced to °dONLNd>
´ä
∑Í(
¥äa handle to a section r’‡°dONLNdU
´Í
∑¸)`ecorJ@°dONLNdY
´˝
∑
)d. 8`°dONLNd\
´

∑
)
Y¯‡°dONLNd]
´

∑
â)ou can use the information r¢†°dONLNdy
´
ä
∑
 )}eturned in the v@°dONLNdà
´
À
∑
˚)AsectionHs@°dONLNdê
´
˚
∑
˝)0
 °dONLNdë
∏ä
ƒ
8(
¡ä)variable to identify the subscriber and r«°dONLNd∫
∏
8
ƒ
§)Æead in the information fr¿°dONLNd”
∏
•
ƒ
Á)mom the edition.°dONLNd„
 ä
÷„(
”äIn this example, the ¿¿°dONLNd¯
 „
÷
1)YAEGetParamPtrª‡°dONLNd
 
1
÷
_)N function rè °dONLNd
 
_
÷
{).eturns£@°dONLNd
 
{
÷
})
,#@°dONLNd
 
~
÷
ú) in the :`°dONLNd
 
ú
÷
‰)returnedType5‡°dONLNd+
 
‰
÷
)H     variablep¿°dONLNd4
 

÷)&
,¿°dONLNd5
 
÷)
 °dONLNd6
׊
„ˇ(
‡äthe descriptor type of the r†°dONLNdR
◊

„
∂)v+esulting data. The descriptor type of the rø °dONLNd}
◊
∂
„
Ò)∂esulting data °dONLNdã
‰ä
≈(
Ìämatches the rÅ°dONLNdò
‰≈

c);$equested descriptor type unless the ‘@°dONLNdº
‰
c
)û#Apple Event Manager wasn’t able to °dONLNdfl
Òä
˝ú(
˙äcoerÙ`°dONLNd„
Òú
˝
)ce the data to the specifiÌ °dONLNd˝
Ò

˝
î)j ed descriptor type or you specifiÏ°dONLNd
Ò
ï
˝
»)èed the desir~Ä°dONLNd*
Ò
…
˝)4ed descriptor °dONLNd8
˛ä
´(ätype as Z@°dONLNd@
˛¨
Ù)"typeWildCardU¿°dONLNdL
˛Ù

%)H. If the coerY‡°dONLNdY
˛
%

a)1cion fails, the ⁄°dONLNdi
˛
a

…)<Apple Event Manager rÕ‡°dONLNd~
˛
…

˜)heturns the °dONLNdâä(äerrAECoercionFaily†°dONLNdöˆ)f r憰dONLNdúˆ
%)esult code.°dONLNd®ä)ù(&äThe ª¿°dONLNd¨ù)Î)AEGetParamPtr∂‡°dONLNdπÎ)
)N function rä °dONLNdƒ
)
5).eturnsû@°dONLNd 
5)
7)
,@°dONLNdÀ
8)
:)
 û@°dONLNdÃ
:)
U)in the 5`°dONLNd”
V)
í)
actualSize1†°dONLNd›
í)
Õ)< variable, the …‡°dONLNdÏ
Õ));actual size of °dONLNd˚*ä6
(3ä#the data (that is, the size of coerï°dONLNd*
6
m)ãced data, if any coerŸ‡°dONLNd3*
m6
≈)Xcion was performedA °dONLNdE*
Δ6
À)Y).°dONLNdG*
Ã6) If the value °dONLNdU7äCç(@ä
rE°dONLNdV7éC∂)    eturned ii‡°dONLNd_7∂C÷)(n this v†°dONLNdg7◊C

)!ariable is gr®¿°dONLNdt7

C)39eater than the amount your application allocated for the °dONLNd≠DäPò(Mäbuf5°dONLNd∞DôP›)fer to hold the rÍ`°dONLNd¡D›P
â)D'eturned data, your application can incr͇°dONLNdËD
âP
È)¨ease the size of its buf̆°dONLNd    D
ÈP)`fer to this °dONLNd    Qä]
(Zä amount, and get the data again. √`°dONLNd    ,Q
]
)é
Yɇ°dONLNd    -Q
]
ü)ou can also choose to use the 3@°dONLNd    KQ
†]
Ù)ÇAEGetParamDesc.°dONLNd    YQ
Ù]
ˆ)T
 °dONLNd    Z^äj
¨(gäAfunction when your application doesn’t know the size of the data.°dONLNd    úpä|›*In general, use the È¿°dONLNd    ∞p›|
+)SAEGetParamPtr‰‡°dONLNd    Ωp
+|
≈)N& function to extract data that is of fi4†°dONLNd    ‰p
Δ|)õxed length or °dONLNd    Ú}äâ
 (Üäknown maximum length, and the @°dONLNd
}
!â
u)óAEGetParamDesc˛°dONLNd
}
tâ)S% function to extract data that is of °dONLNd
Cääñ‰(ìävariable length. The ‡°dONLNd
XäÂñ
9)[AEGetParamDesc†°dONLNd
fä
9ñ
g)T function r͇°dONLNd
qä
fñ
»)-eturns the descriptor r;†°dONLNd
àä
…ñ
€)cecor∞°dONLNd
åä
ۖ
˜)d for aá¿°dONLNd
ìä
¯ñ
˝)
nY °dONLNd
îä
˛ñ)
 °dONLNd
ïóä£(†äApple event parameter`°dONLNd
™ó£
)fD. This function is useful, for example, for extracting a descriptor °dONLNd
Ó§ä∞°(≠älist fri°dONLNd
ı§°∞Ê)om a parameterÜ °dONLNd§Ê∞Ë)E
. °dONLNd§È∞Î)
 ˇ∂@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-28    )B    Handling ê)&Apple Events4^*¿
¯
°dONLNd\lhr(el
Y@Ä°dONLNd
\rhü)
ou specifye¿°dONLNd\ûh†),
,¿°dONLNd\†h¢)
 e¿°dONLNd\£hÓ)as parameters to ,
Courier®†°dONLNd\Óh
B)KAEGetParamDesc£`°dONLNd,\
Bh
G)T, £`°dONLNd.\
Gh
W)the ¢`°dONLNd2\
Wh
€)Apple event that contains the °dONLNdPiluÅ(rldesirO¿°dONLNdUiÇuº)ed parameterà¿°dONLNdaiºuÛ):, the keywor_Ä°dONLNdmiÛu
-)7d of the desirq¿°dONLNd{i
-u
g):ed parameter™¿°dONLNdái
gu
“):, the descriptor type the °dONLNd°vlÇ’(lfunction should use to r®°dONLNdπv’Ç
3)ieturn the descriptor rª¿°dONLNdœv
3Ç
E)^ecor0 °dONLNd”v
FÇ
z)d, and a bufÓ°dONLNdflv
zÇ
§)4fer to storo‡°dONLNdÍv
•Ç
¿)+e the r€‡°dONLNdÒv
¿Ç
Â)eturned °dONLNd˘Élèü(åldescriptor rfl@°dONLNd
Éüè±)3ecorS†°dONLNd
    É≤è∫)d.Ô`°dONLNd
É∫èœ) The ´ °dONLNd
É–è
$)AEGetParamDesc•‡°dONLNd
É
$è
R)T function ry °dONLNd
)É
Rè
¥).eturns the descriptor r…‡°dONLNd
@É
¥è
Δ)becor>@°dONLNd
DÉ
«è
Í)d using °dONLNd
Lêlúò(ôl
the specifiKÄ°dONLNd
WêôúÓ)-ed descriptor type. °dONLNd
l¢lÆ≈(´lFor example, the dirò °dONLNd
Ä¢≈Æ
È)Y@ect parameter of the Open Documents event contains a descriptor °dONLNd
¿Ølª¨(∏llist that specifiî`°dONLNd
—بª
!)@es the documents to open. @°dONLNd
ÎØ
"ª
()v
Yÿ°dONLNd
ÏØ
'ª
h)ou can use the v °dONLNd
˚Ø
iª
Ω)BAEGetParamDescp‡°dONLNd    Ø
Ωª
Ú)T function to °dONLNdºl»
(≈l&get the descriptor list out of the dir¿°dONLNd<º
»
B)öect parameter·†°dONLNdIº
A»
C);
.°dONLNdK”lfl~(‹lVAR°dONLNdP·~ÌÆ+docList:°dONLNd^·ÍÌ
,)lAEDescList;°dONLNdkÔ~˚“(¯~theAppleEvent:°dONLNdÔÍ˚
,)lAppleEvent;°dONLNdå˝~
    ¢(
~myErr:°dONLNdî˝¢
    ®)$
 °dONLNdô˝Í
    
)HOSErr;°dONLNd†
l
!
º(
l8myErr := AEGetParamDesc(theAppleEvent, keyDirectObject, °dONLNd·
#¸
/
z+êtypeAEList, docList);°dONLNd˜
;l
G≈(
DlIn this example, the b`°dONLNd
;≈
G
)YApple event specifiõ@°dONLNd
;

G
k)Ued by the variable /†°dONLNd2
;
l
G
∫)RtheAppleEvent*¿°dONLNd?
;
∫
G
º)N
 °dONLNd@
Hl
Tê(
Qlcontainsp@°dONLNdH
Hë
Tì)%
 @°dONLNdI
Hì
T†)theÕ†°dONLNdL
H°
T£)
 M†°dONLNdM
H§
Tπ)desir`°dONLNdR
H∫
TÙ)ed parameterV`°dONLNd^
HÙ
T
):. The í °dONLNdd
H

T
f)keyDirectObjectåÄ°dONLNds
H
f
T
ä)Z keyworÖ‡°dONLNdz
H
ä
T
Ø)$d specifiè¿°dONLNdÉ
H
Ø
T
fi)%es that the °dONLNdè
Ul
a¿(
^lAEGetParamDescz¿°dONLNdù
U¿
a
_)T% function should get the descriptor ro‡°dONLNd¬
U
_
a
q)üecor‰@°dONLNdΔ
U
q
a
¢)d of the dirÔ‡°dONLNd“
U
¢
a
fi)1ect parameterø¿°dONLNdfl
U
fi
a
„)<. °dONLNd·
bl
n|(
klThe;¿°dONLNd‰
b}
n)
 ª¿°dONLNdÂ
b
nª)
typeAEList∏°dONLNdÔ
bª
n
)< descriptor type specifi]†°dONLNd
b
 
n
É)ees that the descriptor rw°dONLNd
b
É
n
ï)cecorÎ`°dONLNd#
b
ï
n
œ)d should be r,Ä°dONLNd0
b
–
n
ı);eturned °dONLNd8
ol
{
(
xl+as a descriptor list. In this example, the Ë °dONLNdc
o

{
n)ÆAEGetParamDesc‚‡°dONLNdq
o
n
{
ú)T function r∂ °dONLNd|
o
ú
{
Ò).eturns a descriptor °dONLNdê
|l
àó(
Öllist in the Á@°dONLNdú
|ó
à¡)+docList‰†°dONLNd£
|¡
àÈ)*
 variable.°dONLNdÆ
él
ö
<(
ól3The descriptor list contains a list of descriptor rè °dONLNd·
é
<
ö
N)–ecorÄ°dONLNdÂ
é
O
ö
d)ds. Tí°dONLNdÍ
é
c
ö
æ)o get the descriptor r_@°dONLNd
é
ø
ö
—)\ecor”†°dONLNd
é
—
ö
Ò)ds and °dONLNd
õl
ß
 (
§l-their data out of a descriptor list, use the t`°dONLNd8
õ
!
ß
i)µAECountItemso‡°dONLNdD
õ
i
ß
§)H function to fi¬¿°dONLNdS
õ
§
ß
Û);nd the number of °dONLNdd
®l
¥ü(
±ldescriptor rfl@°dONLNdp
®ü
¥±)3ecorS†°dONLNdt
®≤
¥‰)ds in the lis—@°dONLNdÅ
®‰
¥Ó)2t a솰dONLNdÑ
®Ô
¥
2)nd then make r°@°dONLNdí
®
2
¥
å)Cepetitive calls to the @°dONLNd©
®
ç
¥
œ)[AEGetNthPtr °dONLNd¥
®
œ
¥
—)B
 °dONLNdµ
µl
¡
;(
æl1function to get the data out of each descriptor r†°dONLNdÊ
µ
<
¡
N)–ecorÑ°dONLNdÍ
µ
N
¡
j)d. See Ú¿°dONLNdÒ
µ
j
¡
–)“Getting Data Out of a °dONLNd
¬l
Œ⁄(
ÀlDescriptor List” on page a°dONLNd!
¬€
ŒÌ)o4-31¥‡°dONLNd%
¬Ì
Œ
) for mor`°dONLNd-
¬

Œ
O)$e information.°dONLNd<
‘l
‡®(
›lNote that the ‡°dONLNdJ
‘©
‡˝)=AEGetParamDesc˛†°dONLNdX
‘¸
‡
à)S! function copies the descriptor r `°dONLNdy
‘
â
‡
õ)çecorî¿°dONLNd}
‘
õ
‡
™)d frI`°dONLNdÅ
‘
´
‡
Ã)om the °dONLNdà
·l
Ìô(
Íl    parameterS†°dONLNdë
·ô
Ì“)-. When you’rÿ°dONLNdù
·“
Ì
C)9e done with a descriptor rÄ@°dONLNd∑
·
D
Ì
V)recorÙ†°dONLNdª
·
V
Ì
∂)d that you obtained fri¿°dONLNd—
·
∑
Ì
«)aom °dONLNd‘
Ól
˙¿(
˜lAEGetParamDescz¿°dONLNd‚
Ó¿
˙
g)T(, you must dispose of it by calling the Ä°dONLNd

Ó
h
˙
∂)®AEDisposeDesc†°dONLNd
Ó
∂
˙
‡)N
 function.°dONLNd"lÇ(    lIf an •`°dONLNd(Ç
a)2Apple event parameter consists of an object specifiÛ°dONLNd[
a
p)fler rÙ@°dONLNd_
p
Ç)ecorh†°dONLNdc
É
ƒ)d, you can use °dONLNdrl¢(l    AEResolve|†°dONLNd{¢≥)6 to r˘Ä°dONLNdÄ≥
)esolve the object specifÅ °dONLNdò

*)eier rj¿°dONLNdù
*
<)ecorfl °dONLNd°
<
î)d (that is, locate the #`°dONLNd∏
ï
Ú)YApple event object it °dONLNdŒl&‚(#ldescribes), as explained in ¬`°dONLNdÍ‚&
)v    “Finding ëÄ°dONLNdÛ
&
ì)*Apple Event Objects” on page C†°dONLNd
î&
¶)à3-46óÄ°dONLNd
¶&
®)
.

D*K
¯4E*K
¯ FlF
¯

ˇ·ˇ‚7^°dONLNd7lEÁ(AlGetting Data Out of an 6Ä°dONLNd-7ÁE
){    Attributeˇˇˇˇˇˇ‘@(A
Ò
4
°dONLNd8KlWr(Tl
Y@Ä°dONLNd9KrW≥)ou can use the ȇ°dONLNdHK≥W
)AAEGetAttributePtr„Ä°dONLNdYK
W
')f or K†°dONLNd]K
(W
î)AEGetAttributeDescD‡°dONLNdoK
îW
È)l function to get the °dONLNdÑXldÙ(al!data out of the attributes of an 7¿°dONLNd•XÙd
,)àApple event.Ä°dONLNd±X
-d
/)9
 ˇ9¯@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-29
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähê(eä
Y@Ä°dONLNd
\êhΩ)
ou specifye¿°dONLNd\ºhæ),
,¿°dONLNd\æh¿)
 e¿°dONLNd\¡h
)as parameters to ,
Courier®†°dONLNd\
h
r)KAEGetAttributePtr‰‡°dONLNd/\
qh
y)e, t'@°dONLNd2\
zh
á)    he „‡°dONLNd5\
Üh
)Apple event that contains the °dONLNdSiäuü(rädesirO¿°dONLNdXi†u

)ed attribute, the keyworÜ`°dONLNdpi

u
D)jd of the desirò†°dONLNd~i
Du
):/ed attribute, the descriptor type the function °dONLNd≠väÇÀ(äshould use to r¿°dONLNdºvÃÇ
%)Beturn the data, a bufa`°dONLNd—v
%Ç
O)Yfer to stor„@°dONLNd‹v
OÇ
„)*$e the data, and the size of this bufŸ`°dONLNd
v
„Ç
Î)îfeˆ‡°dONLNd
v
ÎÇ
Ó)
r, °dONLNd
v
ÔÇ
Ò)
.¨ °dONLNd
v
ÒÇ) The °dONLNd
    Éäè(åäAEGetAttributePtry†°dONLNd
Éè
)f function rL‡°dONLNd
%É
è
≤).#eturns the descriptor type of the ra†°dONLNd
HÉ
≤è)îeturned data and the °dONLNd
]êäú‰(ôäactual size of the dat°dONLNd
sêÂúÒ)[a añ°dONLNd
vêÒúˆ)
ng`°dONLNd
wê˜ú
)d p@°dONLNd
zê
ú
2)laces the r‡°dONLNd
Öê
2ú
©),equested data in the specifiÄ°dONLNd
°ê
™ú
Δ)xed buf‡°dONLNd
ßê
Δú
“)fero†°dONLNd
™ê
—ú
”)
.°dONLNd
¨¢äÆ
W(´ä0For example, this code gets the data out of the Ô@°dONLNd
‹¢
WÆ
√)ÕkeyEventSourceAttrËÄ°dONLNd
Ó¢
√Æ)l attribute of an °dONLNd
ˇØäªΩ(∏ä
Apple evenà`°dONLNd    ØΩª¬)3t.°dONLNdΔä“ú(œäVAR°dONLNd‘ú‡+theAppleEvent:°dONLNd%‘
‡
J)lAppleEvent;°dONLNd2‚úÓ(ÎúreturnedType: °dONLNdF‚
Ó
>)l    DescType;°dONLNdQú¸fi(˘úsourceOfAE:°dONLNdb
¸
8)lInteger;°dONLNdl˛ú

fi(
úactualSize:°dONLNd}˛



&)lSize;°dONLNdÑ
ú
¿(
úmyErr:°dONLNdå
¿
Δ)$
 °dONLNdë



,)HOSErr;°dONLNdò
$ä
0
˛(
-ä>myErr := AEGetAttributePtr(theAppleEvent, keyEventSourceAttr, °dONLNd⁄
2¿
>Δ+6
 °dONLNd·
2
,
>
Ï)l typeShortInteger, returnedType, °dONLNd
@
,
L
Ú*!@sourceOfAE, SizeOf(sourceOfAE), °dONLNd6
N
,
Z
n*actualSize){‡°dONLNdA
N
n
Z
z)B; °dONLNdD
fä
rù(
oäThe ª¿°dONLNdH
fù
r
    )keyEventSourceAttrµ°dONLNdZ
f
    
r
-)l keyworÆ`°dONLNda
f
-
r
R)$d specifi∏@°dONLNdj
f
R
r
ù)%es the attribute fr/†°dONLNd}
f
û
r)Lom which to get the data. °dONLNdó
sä
ù(
|äThe ª¿°dONLNdõ
sù
˝)typeShortIntegerµ¿°dONLNd´
s˝

a)` descriptor type specifi[`°dONLNd√
s
b

Ÿ)ees that the data should be rô°dONLNdfl
s
Ÿ
)weturned as a °dONLNdÏ
Ää
å◊(
âäshort integer; the '`°dONLNdˇ
Äÿ
å
 )NreturnedType"‡°dONLNd
Ä
 
å)H6 variable contains the actual descriptor type that is °dONLNdA
çä
ôç(
ñä
rE°dONLNdB
çé
ôµ)    eturned. ”‡°dONLNdK
çµ
ôª)'
Yî`°dONLNdL
çª
ô
.)ou also must specify a buf¿°dONLNdf
ç
.
ô
r)sfer to hold the r5 °dONLNdw
ç
s
ô)E%eturned data and specify the size of °dONLNdú
öä
¶´(
£äthis bufÓ °dONLNd§
ö´
¶∑)!fer@‡°dONLNdß
ö∑
¶
). If the data is not alr
¿°dONLNdø
ö

¶
i)[eady a short integer‡°dONLNd”
ö
i
¶
~)W, the 
‡°dONLNdŸ
ö
~
¶
€)Apple Event Manage« °dONLNdÎ
ö
€
¶
Â)]r c™°dONLNdÓ
ö
Ê
¶
Ù)oerÆ °dONLNdÒ
ö
Ù
¶
˝)ceË°dONLNdÛ
ö
˝
¶
)    
s%°dONLNdÙ
ö
¶) iç`°dONLNdˆ
ö
¶)t °dONLNd¯
ßä
≥»(
∞äas necessary b@°dONLNd
ß…
≥⁄)?eform@°dONLNd

ß⁄
≥Â)e r{‡°dONLNd
ßÂ
≥
,)eturning it. The Ç`°dONLNd
ß
,
≥
í)GAEGetAttributePtr|°dONLNd/
ß
í
≥
¿)f function rO@°dONLNd:
ß
¿
≥
‹).eturnsc`°dONLNd@
ß
‹
≥
¸)    , in the °dONLNdI
¥ä
¿Δ(
Ωä
actualSize|@°dONLNdS
¥Δ
¿Ò)< variable, ∑ °dONLNd^
¥Ò
¿
M)+the actual size of the L`°dONLNdu
¥
N
¿
Q)]
r`°dONLNdv
¥
R
¿
w)eturned M‡°dONLNd~
¥
w
¿
Ö)%dat¨°dONLNdÅ
¥
Ö
¿
ë)a a,°dONLNdÑ
¥
í
¿
∂)    fter coerr‡°dONLNdç
¥
∂
¿)$cion has taken place. °dONLNd£
¡ä
Õê(
 ä
Y@Ä°dONLNd§
¡ê
Õ
,)#ou can check this value to make sur†°dONLNd«
¡
-
Õ
å)ùe you got all the data.°dONLNdfl
ӊ
flø(
‹äAs with the 4¿°dONLNdÎ
”¿
fl
)6AEGetParamPtr/‡°dONLNd¯
”

fl
c)N function, you can r–Ä°dONLNd
”
c
fl
ñ)Uequest that ŸÄ°dONLNd
”
ñ
fl
¸)3AEGetAttributePtr” °dONLNd)
”
¸
fl
˛)f
 °dONLNd*
‡ä
Ïç(
Èä
rE°dONLNd+
‡é
Ï
Õ)Keturn the data using the descriptor type of the original data, or you can r˙†°dONLNdv
‡
Õ
Ï(
È
Õequest that the °dONLNdÜ
Ìä
˘
(
ˆäApple Event Manager coer#@°dONLNdû
Ì


˘
Ω)w.ce the data into a descriptor type that is difÁ†°dONLNdÃ
Ì
Ω
˘
…)ºfer  °dONLNdœ
Ì
…
˘
‡)ent fr@`°dONLNd’
Ì
·
˘)om the °dONLNd‹
˙ä±(ä
original. °dONLNdÁä„*In this example, the ¿¿°dONLNd¸„
I)YAEGetAttributePtr∫`°dONLNd
I
w)f function r熰dONLNd
w
©).eturns the rD °dONLNd$
™
˝)3equested data as a °dONLNd7ä%‡("äshort integer in the · °dONLNdL‡%
)V
sourceOfAE›`°dONLNdV
%)<5 variable, and you can get information about the sourÀ‡°dONLNdã%)Îce °dONLNdé&ä2•(/äof the »`°dONLNdï&•2
L)%Apple event by examining this value. ]†°dONLNd∫&
M2
S)®
Y °dONLNdª&
S2
ô)ou can test the r
 °dONLNdÃ&
ô2)Feturned value against the °dONLNdÊ3ä?∫(<ä
values defiéÄ°dONLNdÒ3∫?
)0ned by the data type ¥¿°dONLNd3
?
_)]AEEventSourc∞@°dONLNd3
_?
e)H
e؇°dONLNd3
e?
g)
.°dONLNdJäV
‘(Sä7TYPE AEEventSource = (kAEUnknownSource, kAEDirectCall, °dONLNdTX
d
+~
 †°dONLNdUX
d
‘)!kAESameProcess, kAELocalProcess, °dONLNd~f
r
(o

 †°dONLNdf
r
z)kAERemoteProcess);ˇ‹@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-30    )B    Handling ê)&Apple Events4^*¿
¯
°dONLNd\lhº(elThe constants defiµ °dONLNd\ºh
)Pned by the data type ,
Courier€`°dONLNd'\
h
g)]AEEventSource÷Ä°dONLNd4\
gh
Ï)N have the following meanings:°dONLNd
œÒl˝
(˙l&The next example shows how to use the ‡°dONLNd
ıÒ
˝
Ö)≥AEGetAttributePtrÄ°dONLNdÒ
Ö˝
Ò)f function to get data out °dONLNd ˛l

á(
lof the &¿°dONLNd'˛à


)keyMissedKeywordAttr@°dONLNd;˛



-)x attribute. ;`°dONLNdG˛
-


÷)-&After your handler extracts all known °dONLNdm
l
ß(
lparameters frʇ°dONLNdz
ß
≈);om an £`°dONLNdÄ
≈

}))Apple event, it should check whether the “°dONLNd©

}

ı)∏keyMissedKeywordAttr Ä°dONLNdΩ

ı

˜)x
 °dONLNdæ
l
$
è(
!lHattribute exists. If it does, then your handler did not get all of the rÄ°dONLNd

ê
$
ß(
!
êequir.¿°dONLNd

ß
$
Ë)ed parameters.°dONLNd
*l
6†(
3lNote that if b¿°dONLNd'
*°
6
)5AEGetAttributePtr\`°dONLNd8
*

6
)f r°`°dONLNd:
*

6
;)eturns the 퇰dONLNdE
*
<
6
¢)/errAEDescNotFoundåÄ°dONLNdV
*
¢
6
®)f r—Ä°dONLNdX
*
®
6
Ô)esult code, then °dONLNdi
7l
C|(
@lthe ›`°dONLNdm
7|
CÙ)keyMissedKeywordAttr’‡°dONLNdÅ
7Ù
C
‚)x8 attribute does not exist—that is, your application has °dONLNdπ
Dl
Pƒ(
Mlextracted all of the r{¿°dONLNdœ
Dƒ
P€)Xequirì°dONLNd‘
D€
P
()ed parameters. If ¯¿°dONLNdÊ
D
(
P
é)MAEGetAttributePtrÚ`°dONLNd˜
D
é
P
î)f r7`°dONLNd˘
D
ï
P
≥)eturns ÀÄ°dONLNd
D
≥
P
—)noErr@°dONLNd
D
—
P
Ï), then °dONLNd
Ql
]|(
Zlthe ›`°dONLNd
Q|
]Ù)keyMissedKeywordAttr’‡°dONLNd$
QÙ
]
)x< attribute does exist—that is, your handler did not get all °dONLNd`
^l
jw(
glof …`°dONLNdc
^w
jã)the rο°dONLNdh
^ã
j¢)equir°dONLNdm
^£
j‰)ed parameters.°dONLNd|
ul
Å
Ï(
~l@myErr := AEGetAttributePtr(theAppleEvent, keyMissedKeywordAttr, °dONLNdΔ
É

è
Ê+¢$typeWildCard, returnedType, NIL, 0, °dONLNdÙ
ë

ù
V*actualSize);°dONLNd

©l
µ∞(
≤lThe data in the 1°dONLNd
©±
µ
))EkeyMissedKeywordAttr)Ä°dONLNd%
©
)
µ
≠)x attribute contains the keywork°dONLNdC
©
≠
µ
—)Ñ    d of the °dONLNdL
∂l
¬r(
øl
fiå¿°dONLNdN
∂r
¬})rst˛¿°dONLNdQ
∂}
¬)
 ~¿°dONLNdR
∂Ä
ƒ)
rC¿°dONLNdS
∂Ñ
¬õ)equir[°dONLNdX
∂õ
¬’)ed parameterî°dONLNdd
∂’
¬Û):, if anyï°dONLNdl
∂Ú
¬
h), that your handler didn’t rÄ°dONLNdà
∂
i
¬
Í)wetrieve. If you want this data °dONLNdß
√l
œo(
Ãl
rE°dONLNd®
√p
œœ)eturned, specify a buf˙‡°dONLNdæ
√œ
œˆ)_
fer to holÚ °dONLNd»
√˜
œ
)(d it a8†°dONLNdŒ
√

œ
N)nd specify the «Ä°dONLNd›
√
N
œ
\)@buf|Ä°dONLNd‡
√
]
œ
k)fer †°dONLNd‰
√
l
œ
x)siz2°dONLNdÁ
√
x
œ
)e.{†°dONLNdÈ
√

œ
fi) Otherwise, as in this °dONLNd
–l
‹∏(
Ÿlexample, specify æ¿°dONLNd
–∏
‹ )LNIL_@°dONLNd
– 
‹˜) as the bufƆ°dONLNd
–˜
‹
z)- fer and 0 as the size of the buf°dONLNd?
–
{
‹
á)Ñferc¿°dONLNdB
–
Ü
‹
à)
.°dONLNdD
‚l
Ó
(
Îl"This example shows how to use the ͆°dONLNdf
‚

Ó
q)üAEGetAttributePtr‰@°dONLNdw
‚
q
Ó
€)f function to get the addrü`°dONLNdê
‚
‹
Ó
˜)kess of °dONLNdó
Ôl
˚µ(
¯lthe sender of an I¿°dONLNd®
Ôµ
˚ı)IApple event fr-`°dONLNd∂
Ôı
˚
)@om the T@°dONLNdΩ
Ô

˚
j)!keyAddressAttrO°dONLNdÀ
Ô
j
˚
∞)T attribute of the 뇰dONLNd›
Ô
∞
˚
Ë)FApple event:°dONLNdÍl~(lVAR°dONLNdÔ~ ÿ+theAppleEvent: z`°dONLNdˇÿ 
)ZAppleEvent;°dONLNd"~.“(+~returnedType: °dONLNd"ÿ.
)Z    DescType;°dONLNd*0~<Ã(9~addressOfAE: °dONLNd<0ÿ<
)Z    TargetID;°dONLNdG>~JΔ(G~actualSize: °dONLNdX>ÿJˆ)ZSize;°dONLNd_L~X®(U~myErr: °dONLNdkLÿXˆ)ZOSErr~ °dONLNdpLˆX¸)
;°dONLNdshlt
»(ql:myErr := AEGetAttributePtr(theAppleEvent, keyAddressAttr, °dONLNd∑v
Ç
∂+¢typeTargetID, returnedType, °dONLNd›Ñ
ê
‡*#@addressOfAE, SizeOf(addressOfAE), °dONLNd
í
û
V*actualSize);
    °dONLNdRulÄï(}l    Constant °dONLNd\u‡Ä
)tMeaning
°dONLNdeÉlèÃ(ålkAEUnknownSource°dONLNdvɇèÙ)tSour
`°dONLNdzÉıè
)ce of ¶@°dONLNdÄÉ
è
n)Apple event unknown°dONLNdïìlü∫(úlkAEDirectCall°dONLNd£ì‡üÁ)t
A∫†°dONLNd§ìÁüˆ) dir¿°dONLNd®ì˜ü
É) ect call that bypassed the PPC Tÿ°dONLNd»ì
Çü
ü)ãoolbox°dONLNd–£lØ¿(¨lkAESameProcess°dONLNdfl£‡ØÊ)t
Tµ¿°dONLNd‡£ÂØÌ)arz¿°dONLNd‚£ÓØ
t)     get application is also the souri°dONLNd
£
tØ
±)Üce application°dONLNd
≥løΔ(ºlkAELocalProcess°dONLNd
"≥‡øÙ)tSour
`°dONLNd
&≥ıø
m)ce application is another prıÄ°dONLNd
B≥
lø
ˆ)wocess on the same computer as °dONLNd
`æ‡ ¸(«‡the tar‰¿°dONLNd
gæ¸ 
=)get application°dONLNd
xŒl⁄Ã(◊lkAERemoteProcess°dONLNd
⌇⁄Ù)tSour
`°dONLNd
çŒı⁄
P)ce application is a prfi†°dONLNd
£Œ
O⁄
Å)Zocess on a r쇰dONLNd
،
Ç⁄
Î)3emote computer on the °dONLNd
≈Ÿ‡Â
(‚‡networkˇ<|@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-31
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähù(eäThe ,
Courierª¿°dONLNd\ùhÒ)keyAddressAttr∂Ä°dONLNd\Òh
)T keywor؇°dONLNd\
h
:)$d specifiπ¿°dONLNd"\
:h
«)%#es the attribute to get the data frø†°dONLNdE\
«h
Ì)çom. The °dONLNdMiäu“(rätypeTargetID{Ä°dONLNdYi“u
3)H descriptor type specif8¿°dONLNdpi
4u
Æ)bies that the data should be r^¿°dONLNdçi
Æu
Ú)zeturned as a tarfl†°dONLNdùi
Úu)Dget ID °dONLNd§väÇç(ä
rE°dONLNd•védž)ecorπ`°dONLNd©v†Çª)d; the 2Ä°dONLNd∞vºÇ
)returnedType.°dONLNdºv
Ç
Ë)H7 variable contains the actual descriptor type that is r–†°dONLNdÛv
ËÇ)‰    eturned. °dONLNd¸Éäèê(åä
Y@Ä°dONLNd˝Éêè˝)ou can examine the addr"@°dONLNd
É˝è
)mess r™‡°dONLNd
É
è
P)eturned in the ~Ä°dONLNd
(É
Qè
ì)AaddressOfAEz`°dONLNd
3É
ìè)B variable to determine the °dONLNd
Nêäú≈(ôäsender of the ¯`°dONLNd
\ê≈ú˝);Apple event.°dONLNd
i¢äÆ©(´äThe tar√ °dONLNd
p¢©Æ )get ID r?°dONLNd
x¢ÀÆ›)"ecor≥`°dONLNd
|¢›ÆÈ)d r °dONLNd
¢ÍÆ
*)eturned in the Á¿°dONLNd
é¢
*Æ
l)@addressOfAE㠡dONLNd
ô¢
lÆ
Í)B variable contains the senderŸÄ°dONLNd
∂¢
ÎÆ    )’s port °dONLNd
æØäª
(∏ä"name, port location, and session rΩ`°dONLNd
‡Ø
ª
.)îeferiÄ°dONLNd
‰Ø
/ª
h)ence numberÒ`°dONLNd
ÔØ
gª
r)8. T' °dONLNd
ÚØ
rª
§)o get the pr\@°dONLNd
˛Ø
§ª)2ocess serial number for a °dONLNdºä»ì(≈äprG °dONLNdºî»
h)
0ocess on the local machine, pass the port name r`°dONLNdJº
h»
µ)‘eturned in the tar˘`°dONLNd\º
¥»
’)Lget ID ru@°dONLNddº
÷»
Ë)"ecorȆ°dONLNdhº
Ë»)    d to the °dONLNdq…ä’
V(“ä"GetProcessSerialNumberFromPortNames@°dONLNdì…
V’
Ç)à function. ”‡°dONLNdû…
Ç’
à),
Yî`°dONLNdü…
à’
Ó)ou can then pass the pr¢°dONLNd∂…
Ó’)focess °dONLNdº÷ä‚Â(fläserial number to the œ†°dONLNd—÷‚
c)[GetProcessInformation«¿°dONLNdÊ÷
c‚
û)~ function to fi†°dONLNdı÷
ü‚
Δ)<    nd the cr`°dONLNd˛÷
Δ‚)'eator signatur¢‡°dONLNd÷‚
)=e °dONLNd„äÔ≈(Ïäfor a given pr;‡°dONLNd„ΔÔfl)<ocess.Â@°dONLNd"„flÔ
)     (For mor>‡°dONLNd+„
    Ô)*<e information about these functions, see the chapter “Event °dONLNdg七(˘äManager” in À¿°dONLNdsƒ¸
    ):Inside Macintosh≠¿°dONLNdÉ

¸
)F: M°dONLNdÜ
¸
C)
acintosh T@°dONLNdê
B¸
[))oolbox◊@°dONLNdñ
[¸
Ü) Essentials„@°dONLNd°
ܸ
à)+
.c@°dONLNd¢
â¸
å)
)°dONLNd§
ä
≠(
äFor mor¿°dONLNd´
Æ

)$e information about tarX¿°dONLNd¬



9)fget addrp`°dONLNd 

9

d)%esses, see 
‡°dONLNd’

e

®),“Specifying a T–†°dONLNd‰

ß

Ø)BardONLNdÊ

∞

¿)    get R`°dONLNdÍ

¿

◊)Addr °dONLNdÓ

ÿ

˙)ess” on °dONLNdˆ
ä
°(
äpage Z‡°dONLNd˚
¢
¥)5-10Æ¿°dONLNdˇ
¥
∂)
.


9H
@4
:H
@ 
;ä
;

ˇ·ˇ‚7^°dONLNd

,ä
:
K(
6ä%Getting Data Out of a Descriptor Listˇˇˇˇˇˇ‘@(
6
4
°dONLNd(
@ä
Lê(
Iä
Y@Ä°dONLNd)
@ê
L—)ou can use the ȇ°dONLNd8
@—
L
)AAECountItemsÂ`°dONLNdD
@

L)H7 function to count the number of items in a descriptor °dONLNd{
Mä
YÊ(
Välist, and you can use `°dONLNdë
MÁ
Y
/)]AEGetNthDesc‡°dONLNdù
M
/
Y
=)H or |°dONLNd°
M
=
Y
)AEGetNthPtrw‡°dONLNd¨
M

Y
◊)B to get a descriptor r* °dONLNd¬
M
ÿ
Y
Í)YecorûÄ°dONLNdΔ
M
Í
Y)    d or its °dONLNdœ
Zä
f
(
cädata out of a descriptor list.°dONLNdÓ
lä
x
D*'The Open Documents event contains a dirS‡°dONLNd
l
D
x
≥)∫ect parameter that specifi•`°dONLNd/
l
≥
x
È)oes the list of °dONLNd>
yä
Ö
—(
ÇäLdocuments to open. The list of documents is contained in a descriptor list. Ä°dONLNdä
y
“
Ö
Î(
Ç
“After °dONLNdê
Üä
í
(
èä!extracting the descriptor list fr`°dONLNd±
Ü

í
^)Üom the parameter˝‡°dONLNd¡
Ü
]
í)M(, you can determine the number of items °dONLNdÈ
ìä
ü
I(
úä.in the list and then extract each descriptor r«Ä°dONLNd
ì
I
ü
[)øecor;‡°dONLNd
ì
\
ü
k)d frÄ°dONLNd
ì
k
ü
ÿ)om the descriptor list. Se °dONLNd9
ì
Ÿ
ü
‡)ne T¿°dONLNd;
ì
‡
ü
¯)Figur'Ä°dONLNd@
ì
¯
ü)e 3-9 °dONLNdF
†ä
¨Ø(
©äon page !¿°dONLNdN
†∞
¨∏)&3-u†°dONLNdP
†∏
¨¬)19u†°dONLNdR
†¬
¨«)
 fIÄ°dONLNdT
†»
¨
é)+or a depiction of the Open Documents event.°dONLNdÄ
≤ä
æ
!(
ªä For example, when your handler r€Ä°dONLNd†
≤
!
æ)ó1eceives an Open Documents event, you can use the °dONLNd—
øä
Àfi(
»äAEGetParamDescz¿°dONLNdfl
øfi
À
)T function to rÖ‡°dONLNdÌ
ø

À
N)9eturn the dirÄ°dONLNd˙
ø
O
À
„)8$ect parameter as a descriptor list. 
Ä°dONLNd
ø
„
À
È)î
YÀ°dONLNd
ø
Ë
À)ou can °dONLNd&
Ãä
ÿ±(
’ä    then use <Ä°dONLNd/
̲
ÿ˙)(AECountItems8°dONLNd;
Ã˙
ÿ
)H to r¥‡°dONLNd@
Ã

ÿ
ô) eturn the number of descriptor rÇ`°dONLNd`
Ã
ö
ÿ
¨)èecorˆ¿°dONLNdd
Ã
¨
ÿ
‰)ds in the list.°dONLNdt
„ä
Ôú(
ÏäVAR°dONLNdy
Òú
˝+theAppleEvent:°dONLNdç
Ò

˝
J)lAppleEvent;°dONLNdö
ˇúÃ(údocList:°dONLNd®
ˇ

J)lAEDescList;°dONLNdµú‰(úitemsInList:°dONLNd«

8)lLongInt;°dONLNd—ú'¿($úmyErr:°dONLNd›
'
,)lOSErr;°dONLNd‰3ä?
‘(<ä7myErr := AEGetParamDesc(theAppleEvent, keyDirectObject,°dONLNd$A
M
ò+êtypeAEList, docList);°dONLNd:Oä[
í(Xä,myErr := AECountItems(docList, itemsInList);°dONLNdggäsù*The ª¿°dONLNdkgùsÒ)AEGetParamDesc∂Ä°dONLNdygÒs
)T function râ¿°dONLNdÑg
s
1).eturèÄ°dONLNdàg
1s
=)ns,‡°dONLNdãg
>s
\) in the 5°dONLNdìg
\s
Ü)docList2`°dONLNdög
Üs
¨)*     variablem@°dONLNd£g
¨s
Æ)&
,Ì@°dONLNd§g
Æs
∞)
 m@°dONLNd•g
±s
€)
a copy of -†°dONLNdØg
‹s
Ï)+the °dONLNd≥täÄ–(}ädescriptor list fr@°dONLNd≈t—ġ)G
om the dirÛ@°dONLNdœt˛Ä
Δ)-+ect parameter of the Open Documents event. ÿ`°dONLNd˙t
ΔÄ
Ã)»
Yò‡°dONLNd˚t
ÃÄ)ou specify this °dONLNd    Åäçµ(äälist to the Â`°dONLNd    ŵç˝)+AECountItems‡‡°dONLNd    #Å˝ç
')H
 function.ˇ#í@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-32    )B    Handling ê)&Apple Events4^*¿
¯
°dONLNd\lhr(el
Y@Ä°dONLNd
\rh
†)Eou specify the descriptor list whose items you want to count in the fiF°dONLNdG\
†h
È(e
†rst parameter to ,
Courier°dONLNdXilu¥(rlAECountItems{Ä°dONLNddi¥uÃ)H. The X‡°dONLNdjiÃu
4)Apple Event Manager rL¿°dONLNdi
4u
P)heturns`‡°dONLNdÖi
Pu
R)
,‡‡°dONLNdÜi
Ru
T)
 `‡°dONLNdái
Uu
ø)in the second parameter% °dONLNdûi
øu
ƒ)j, % °dONLNd†i
ƒu
‘)the °dONLNd§vlÇÿ(lnumber of items in the li'°dONLNdΩvŸÇ‚)mst.&`°dONLNd¿v„Ç
t)
! When extracting the descriptor rÚ °dONLNd·v
tÇ
Ü)ëecorfÄ°dONLNdÂv
áÇ
õ)ds frX °dONLNdÍv
õÇ
Ú)om a list, you often °dONLNdˇÉlè
1(ål,use the number of items as a loop index. Her‰Ä°dONLNd
+É
1è
t)≈e’s an example:°dONLNd
;öl¶
,(£l FOR index := 1 TO itemsInList DO°dONLNd
]®~¥ú+BEGIN°dONLNd
d∂~¬
¬*6{for each descriptor record in the list, get its data}°dONLNd
úƒ~–ñ*END;°dONLNd
°‹lËÓ(ÂlThe format of the descriptor r °dONLNd
ø‹ÔË

)ÉecoràÄ°dONLNd
√‹

Ë
ß)*ds in a descriptor list is private to the q°dONLNd
Ì‹
ßË
·)¶Apple Event °dONLNd
˘Èlıì(ÚlManagerT†°dONLNdÈìıò)'. '°dONLNdÈòıû)
YÁÄ°dONLNdÈùıÂ)ou must use the ©¿°dONLNdÈÊı
()IAEGetNthPtr•†°dONLNdÈ
(ı
6)B or ¿°dONLNd"È
7ı
)AEGetNthDesc    @°dONLNd.È
ı
‘)H function to extract °dONLNdCˆl
ü(ˇldescriptor rfl@°dONLNdOˆü
±)3ecorS†°dONLNdSˆ≤
Δ)ds frE@°dONLNdXˆΔ

)om a descriptor list.˘ °dONLNdmˆ


)W
 y °dONLNdnˆ
 

")
 °dONLNdp
l
r(
l
Y@Ä°dONLNdq
r

S)6ou specify the descriptor list that contains the desir<¿°dONLNdß

S

ì)·ed descriptor r
`°dONLNd∂

î

¶)Aecoru¿°dONLNd∫

¶

Ó)ds and an index °dONLNd 
l
!«(
las parameters to the  @°dONLNdfl
»
!

)\AEGetNthPtr °dONLNdÍ



!
i)B function. The index rÚ‡°dONLNd

h
!
v)^eprɆ°dONLNd

w
!
∏)esents a specifi¿°dONLNd

π
!
Ô)Bc descriptor °dONLNd 
"l
.o(
+l
rE°dONLNd!
"p
.Ç)ecorπ`°dONLNd%
"Ç
.Ë)d in the descriptor list. ÷†°dONLNd?
"Ë
.˚)fThe `°dONLNdC
"¸
.
>)AEGetNthPtr@°dONLNdN
"
>
.
@)B
 é@°dONLNdO
"
@
.
g)    function Ä°dONLNdX
"
h
.
k)(
r·Ä°dONLNdY
"
k
.
®)eturns the dat1 °dONLNdg
"
©
.
¬)>a for t/Ä°dONLNdn
"
√
.
–)he °dONLNdq
/l
;ü(
8ldescriptor rfl@°dONLNd}
/ü
;±)3ecorS†°dONLNdÅ
/≤
;æ)d r¥`°dONLNdÑ
/æ
;Ã)eprE °dONLNdá
/Õ
;
+)esented by the specifi¿°dONLNdù
/
+
;
V)^
ed index. °dONLNd®
Al
Mr(
Jl
Y@Ä°dONLNd©
Ar
M
Ö)@ou also specify the descriptor type the function should use to r∂†°dONLNdÈ
A
Ö
M
fi(
J
Öeturn the data, a buf˛@°dONLNd˛
A
fi
M
Ï)Yfer °dONLNd
Nl
Zà(
Wlto storq¿°dONLNd    
Nà
Z
)$e the data, and the size of this bufg‡°dONLNd-
N

Z
()îfer∫†°dONLNd0
N
'
Z
a). If the specifi∏Ä°dONLNd@
N
b
Z
¢);ed descriptor r} °dONLNdO
N
£
Z
µ)AecorÒÄ°dONLNdS
N
µ
Z
Î)d exists, the °dONLNda
[l
gÆ(
dlAEGetNthPtr{‡°dONLNdl
[Æ
g‹)B function rO °dONLNdw
[‹
g
,).eturns the keywor∫°dONLNdà
[
,
g
})Pd of the parameter– °dONLNdö
[
}
g
Û)Q, the descriptor type of the °dONLNd∑
hl
to(
ql
rE°dONLNd∏
hp
t
Ñ)Beturned data, and the actual size of the data, and it places the r[¿°dONLNd˙
h
Ñ
t
fl(
q
Ñequested data in the °dONLNd
ul
Åà(
~lspecifiÓ °dONLNd
uà
ŧ)ed bufİdONLNd
u•
ű)fer[@°dONLNd
u∞
Å≤)
.°dONLNd!
ál
ì}(
êlHer`°dONLNd$
á}
ì˙)e’s an example that uses the ˜‡°dONLNdA
á˙
ì
<)}AEGetNthPtrÛ¿°dONLNdL
á
<
ì
º)B function to extract an item frF`°dONLNdk
á
Ω
ì
fi)Åom the °dONLNdr
îl
†”(
ùldescriptor list in the dirJ†°dONLNdå
î‘
†
ì)h(ect parameter of the Open Documents even°dONLNd¥
î
î
†
ô)¿t:°dONLNd∑
´l
∑
™(
¥l5myErr := AEGetNthPtr(docList, index, typeFSS, keywd, °dONLNdÙ
πÍ
≈
»+~%returnedType, @myFSS, Sizeof(myFSS), °dONLNd!
«Í
”
2*actualSize);°dONLNd.
fll
Î(
ËlThe ª¿°dONLNd2
fl
Ω)docListπ °dONLNd9
fl©
ÎÓ)* variable specifi‚ °dONLNdJ
flÓ
Î
P)Ees the descriptor list frI`°dONLNdc
fl
Q
Î
)c
om the dir9`°dONLNdm
fl

Î
Ÿ).ect parameter of the °dONLNdÇ
Ïl
¯Ñ(
ılOpen˘°dONLNdÜ
ÏÑ
¯Ü)
 y°dONLNdá
Ïá
¯Ï)Documents event. The Ä°dONLNdú
ÏÌ
¯
)findex†°dONLNd°
Ï

¯
P) variable specifiA†°dONLNd≤
Ï
P
¯
÷)E es the index of the descriptor rs`°dONLNd“
Ï
÷
¯
Ë)ÜecorÁ¿°dONLNd÷
Ï
Ë
¯
)d °dONLNdÿ
˘lö(lto extract. d °dONLNd‰
˘ö†).
Y$†°dONLNdÂ
˘†·)ou can use the Œ°dONLNdÙ
˘·
)AtypeFSSÀ`°dONLNd˚
˘

Í)*6 descriptor type, as in this example, to specify that °dONLNd1l¢(lthe data be rQ¿°dONLNd>£·)7eturned as a fiÿ°dONLNdM·
))>le system specifi·@°dONLNd^
)
J)Hcation r °dONLNdf
K
])"ecor|Ä°dONLNdj
]
{)d. The u†°dONLNdq
{
fl)Apple Event Manager °dONLNdÖlΩ(lautomatically coer@°dONLNdóæ
~)R.ces the original data type of the descriptor rY†°dONLNd≈
~
ê)¿ecorŒ°dONLNd…
ê
ü)d frdž°dONLNdÕ
†
‘)om an alias °dONLNdŸ l,o()l
rE°dONLNd⁄ p,Ç)ecorπ`°dONLNdfi Ç,à)
d’ °dONLNdfl à,ä)
 U °dONLNd‡ ã,£)to a fi¿°dONLNdÁ §,Ï)le system specifi#°dONLNd¯ Ï,
)Hcation rI‡°dONLNd 
,
)!ecoræ@°dONLNd 
,
=)d. The ¿°dONLNd 
>,
Ä)AEGetNthPtr†°dONLNd 
Ä,
Æ)B function r‰‡°dONLNd! 
≠,
ƒ)-eturnº°dONLNd& 
≈,
Œ)s tª`°dONLNd) 
œ,
‹)
he °dONLNd,-l9ç(6lkeywor˘`°dONLNd2-ç9û)!d of^Ä°dONLNd6-ü9°)
 fiÄ°dONLNd7-°9⁄)the paramete⁄@°dONLNdC-€9
j):"r and the descriptor type of the r:†°dONLNde-
k9
©)êesulting data iÄ°dONLNdt-
™9
¬)?n the ±@°dONLNdz-
¬9
‡)keywdØ`°dONLNd-
‡9
‚)
 °dONLNdÄ:lF(Cland Ì °dONLNdÑ:F«)returnedTypeˆ°dONLNdê:«Fœ)H v‡°dONLNdí:–FÈ)    ariablY‡°dONLNdò:ÈF˙)es, r%Ä°dONLNdù:˚F
,)espectively^Ä°dONLNd®:
+F
-)0
.fiÄ°dONLNd©:
-F
/)
 °dONLNd´LlXr(Ul
Y@Ä°dONLNd¨LrX)ou = °dONLNdØLÄXî)also X°dONLNd¥LîXÃ)specify a bufQ`°dONLNd¡LÃX
")8fer to hold the desirÄ°dONLNd÷L
#X
”)W*ed data and the size (in bytes) of the buf´Ä°dONLNd    L
”X
€)∞fe…°dONLNd    L
€X
fi)
r˛@°dONLNd    L
fiX
‡)
.~@°dONLNd    L
·X
Ô) In °dONLNd    Yleπ(blthis example, the ‡°dONLNd    Y∫eÿ)NmyFSS°dONLNd    Yÿe
) variable specifi8°dONLNd    0Y
e
G)E
es the buf—°dONLNd    :Y
Ge
S)*fer#¿°dONLNd    =Y
Se
ñ). The function r≤¿°dONLNd    MY
ñe
ı)Ceturns the actual size °dONLNd    dflrπ(olof the data in the ú°dONLNd    wfπrı)M
actualSizeò@°dONLNd    Åfır
e)< variable. If this size is larÄ`°dONLNd    üf
er
⁄)pger than the size of the bufŸ°dONLNd    ªf
⁄r
Ë)ufer °dONLNd    øslâ(|lyou pr“‡°dONLNd    ≈sâ
√)Iovided, you know that you didn’t get all of the data for the descriptor r◊°dONLNd
s
√
’(|
√ecorK`°dONLNd
s
÷
fi)d.°dONLNd
Ölëü(élListing 4-10 @°dONLNd
!Ö†ë⁄)4 shows a morΔ†°dONLNd
-Ö⁄ë
†):-e complete example of extracting the items frÏ@°dONLNd
ZÖ
†ë
Á)Δom a descriptor °dONLNd
jílû
(õl!list in the Open Documents event.ˇ4Æ@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-33
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHn4gHn"hH_

ˇ·ˇ‚7^    °dONLNd\ägª(däListing 4-10°dONLNd\Œg
a)D'Extracting items from a descriptor list,
Courier
°dONLNd6väÇú(äVAR°dONLNd;Ñúê¿+index:°dONLNdGÑ
ê
8)lLongInt;°dONLNdQíúûÍ(õúitemsInList: °dONLNddí
û
8)lLongInt;°dONLNdn†ú¨Ã(©údocList:°dONLNd|†
¨
J)lAEDescList;°dONLNdâÆú∫Δ(∑úkeywd: °dONLNdñÆ
∫
D)l
AEKeyword;°dONLNd¢ºú»(≈úreturnedType: °dONLNd∂º
»
>)l    DescType;°dONLNd¡ ú÷¿(”úmyFSS:°dONLNdÕ 
÷
2)lFSSpec;°dONLNd÷ÿú‰‰(·úactualSize: °dONLNdËÿ
‰
&)lSize;°dONLNdÔÊúÚ¿(ÔúmyErr:°dONLNd˜Ê¿ÚΔ)$
 °dONLNd¸Ê
Ú
,)HOSErr;°dONLNd

ä

J(
ä FOR index := 1 TO itemsInList DO°dONLNd
&
ú
∫+BEGIN°dONLNd
.
Æ
*
Ï+5myErr := AEGetNthPtr(docList, index, typeFSS, keywd, °dONLNd
m
,
,
8
+~%returnedType, @myFSS, Sizeof(myFSS), °dONLNd
ú
:
,
F
t*actualSize);°dONLNd
´
HÆ
T
í(
QÆ&IF myErr <> noErr THEN DoError(myErr);°dONLNd
‘
VÆ
b
V*myErr := MyOpenFile(@myFSS);°dONLNd
Û
dÆ
p
í*&IF myErr <> noErr THEN DoError(myErr);°dONLNd
rú
~¥(
{úEND;°dONLNd 
Ää
å
P(
âä!myErr := AEDisposeDesc(docList); s†°dONLNdA
Ä
P
å
V)Δ
 


≤H
π4
≥H
π 
¥ä
¥

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdC
£ä
≤ó(
Æä
WS°dONLNdD
£ó
≤∏)riting À°dONLNdK
£∑
≤
;) Apple Event Handlersˇˇˇˇˇˇ€r(
Æ
4
°dONLNda
πä
≈≤(
¬ä    For each $ °dONLNdj
π≤
≈
ô)(2Apple event your application supports, you must pr
`°dONLNdú
π
ô
≈)Áovide a function called °dONLNd¥
Δä
“î(
œäanQ`°dONLNd∂
Δï
“ó)
 s°dONLNd∑
Δó
“Ú)Apple event handler„Ä°dONLNd 
ΔÒ
“
    )Z. The @°dONLNd–
Δ


“
|)AEProcessAppleEvent °dONLNd„
Δ
|
“
Ò)r function calls one of your @°dONLNdˇ
Δ
Ò
“)uApple °dONLNd
ӊ
fl˚(
‹äevent handlers when it pr"†°dONLNd
”¸
fl
,)rocesses an ≈†°dONLNd)
”
+
fl
f)/Apple event. ‚¿°dONLNd6
”
f
fl
l);
Y£@°dONLNd7
”
l
fl
})our 4 °dONLNd;
”
~
fl)Apple event handlers should °dONLNdW
‡ä
ÏÂ(
Èäperform any action rU¿°dONLNdk
‡Â
Ï
-)[equested by the ¿°dONLNd{
‡
-
Ï
œ)H$Apple event, add parameters to the rÆ@°dONLNdü
‡
œ
Ï
‰)¢eply  °dONLNd§
‡
Â
Ï)Apple °dONLNd™
Ìä
˘¬(
ˆäevent if appr“¿°dONLNd∑
̬
˘˝)8opriate, and rcÄ°dONLNd≈
Ì˛
˘
#)<    eturn a rˇ†°dONLNdŒ
Ì
#
˘
R)%esult code.°dONLNd⁄
ˇäù(äThe ]`°dONLNdfi
ˇù
j)-Apple Event Manager uses dispatch tables to r‘ °dONLNd
ˇ
j
Ä)Õoute ~`°dONLNd
ˇ
Ä
Ì)Apple events to the appr‰†°dONLNd(
ˇ
Ì)mopriate °dONLNd0äÂ(äApple event handlerÄ°dONLNdC‰È)Z. ¬‡°dONLNdEÈÔ)
YÉ`°dONLNdFÔ
D)ou must supply an ç`°dONLNdX
D)U+Apple event handler for each entry in your °dONLNdÉä%≈("äapplication’s \¿°dONLNdë≈%
˚);FApple event dispatch table. Each handler must be a function that uses °dONLNd◊&ä2ö(/äthisπ °dONLNd€&ö2ú)
 9 °dONLNd‹&ù2º)syntax:°dONLNd‰=äIΔ(Fä
FUNCTION M|@°dONLNdÓ=ΔI“)<yE{Ä°dONLNd=“I
º)'ventHandler (theAppleEvent: AppleEvent;l‡°dONLNd=
ºI
¬)Í
 °dONLNd!K
W
 (T

 †°dONLNd"K
 W
&)
r@°dONLNd#K
&W
å)eply: AppleEvent;x‡°dONLNd4K
åW
í)f
 °dONLNd>Y
e
 (b

 †°dONLNd?Y
 e
&)
h@°dONLNd@Y
&e
‡)andlerRefcon: LongInt): OSErr; °dONLNd`qä}ï(zäThr °dONLNdbqñ}Õ)e parameter ÿ°dONLNdnqÕ}
)7theAppleEvent«‡°dONLNd{q
}
)N
 G‡°dONLNd|q
}
8)is the Ï@°dONLNdÉq
7}
û)Apple event to handle. 1¿°dONLNdöq
ü}
•)h
YÚ@°dONLNdõq
§}
)our handler uses 1°dONLNd¨q
Ò})MApple °dONLNd≤~ää
∂(áäCEvent Manager functions to extract any parameters and attributes frz`°dONLNdı~
∂ä
◊(á
∂om the B‡°dONLNd¸~
◊ä)!Apple event °dONLNdãäó
&(îä"and then performs the necessary prú`°dONLNd*ã
&ó
P)ú
ocessing. †°dONLNd4ã
Qó
¸)+(If any of the parameters include object °dONLNd\ò䧶(°äspecifiÓ °dONLNdcò¶§µ)er rÔ`°dONLNdgòµ§«)ecorc¿°dONLNdkò»§
F)ds, your handler should call Ó °dONLNdàò
F§
|)~    AEResolveÍ¿°dONLNdëò
|§
ç)6 to rg†°dONLNdñò
é§)esolve them—that is, to locate °dONLNdµ•ä±ö(Æäthe °dONLNdπ•ö±
V)*Apple event objects they describe. For mor°dONLNd„•
W±)Ω*e information, see the chapter “Resolving °dONLNd≤äæ®(ªäand Cr… °dONLNd≤®æ

)eating Object Specifi≈`°dONLNd(≤
æ
&)Zer Recor$°dONLNd0≤
'æ
o)%ds” in this book.ˇ!˙@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-34    )B    Handling ê)&Apple Events4^*¿
¯
°dONLNd\lhr(el
T†¿°dONLNd
\rh)he ,
Courierª¿°dONLNd\hù)replyπ‡°dONLNd    \ùh
) parameter is the default r˝¿°dONLNd$\
h
.)reply prà °dONLNd+\
/h
n) ovided by the £ °dONLNd9\
nh
œ)?Apple Event ManagerdONLNdL\
œh
‘)a. °dONLNdNiluo(rl
(”‡°dONLNdOiou∑)“Replying to an ∏‡°dONLNd_i∑uˆ)HApple Event,”’¿°dONLNdliˆu
C)? which begins on F °dONLNd}i
Du
[)Npage !°dONLNdÇi
\u
n)4-36t‡°dONLNdÜi
nu
s), t‡°dONLNdài
su
y)
dꆰdONLNdâi
yu
”)escribes how to add °dONLNdùvlÇ·(lparameters to the default r`°dONLNd∏v‚Çı)veply:‡°dONLNdºvÙÇ
).) The  Ä°dONLNd√v
Ç
])handlerRefcon≈†°dONLNd–v
]Ç
≠)N parameter is the r`°dONLNd„v
ÆÇ
æ)Qefer Ä°dONLNdÁv
æÇ
‘)ence °dONLNdÏÉlè§(ålconstant stor °dONLNd˘É•èÕ)9
ed in the ¢@°dONLNd
ÉÕè
)()Apple event dispatch table entry for the  `°dONLNd
,É
è
∫)≤Apple event. ÁÄ°dONLNd
9É
∫è
¿);
Y®°dONLNd
:É
¿è
ˆ)our handler °dONLNd
Fêlú≠(ôlcan check the rÓ†°dONLNd
Uê≠úΩ)Aeferö¿°dONLNd
Yêæú
2)ence constant, if necessary´°dONLNd
tê
1ú
®)s, for information about the Ë°dONLNd
êê
®ú
‡)wApple event.°dONLNd
ù¢lÆr(´l
Y@Ä°dONLNd
û¢rÆ∑)ou can use the rƇ°dONLNd
Æ¢∑Æ«)Eefer[°dONLNd
󛯒
·)?ence constant for anything you wish. For example, if you want t3Ä°dONLNd
Ò¢
‚Æ
È(´
‚o °dONLNd
ÛØlªfl(∏luse the same handler for s!‡°dONLNd؇ª˝)teveral X°dONLNdØ˝ª
3)Apple event¢¿°dONLNdØ
3ª
9)6s,_¿°dONLNd!Ø
:ª
Î)+ you can install entries for each event in °dONLNdLºl»æ(≈lyour application’s € °dONLNd_ºæ»
ÿ)R@Apple event dispatch table that specify the same handler but difö@°dONLNdüº
Ÿ»
Â(≈
Ÿfer|¿°dONLNd¢º
»
ı)ent °dONLNd¶…l’o(“l
rE°dONLNdß…p’Ä)eferÒ °dONLNd´…Ä’ƒ)ence constants. ü†°dONLNdª…≈’À)E
Y` °dONLNdº…À’
O)our handler can then use the r”°dONLNd⁄…
O’
_)Ñefer °dONLNdfi…
`’
Ì)!ence constant to distinguish the °dONLNdˇ÷l‚x(flldif™`°dONLNd÷x‚Ñ)fer凰dONLNd÷Ñ‚î)ent ㇰdONLNd    ÷)Apple events it handles.°dONLNd"ËlÙr(Òl
Tµ¿°dONLNd#ËqÙÇ)o prr`°dONLNd'ËÉÙ´)    ovide an Œ‡°dONLNd0Ë´Ù
;)( Apple event handler in C, be sur߇°dONLNdPË
;Ù
t)êe to include t͆°dONLNd^Ë
tÙ
Í)9he Pascal declaration befor&¿°dONLNdyË
ÎÙ
Ú)we °dONLNd{ıl

“(˛lthe handler declarationb¿°dONLNdíı”


C)g. This is the syntax for an ¥Ä°dONLNdÆı
C


∑)pApple event handler in C: °dONLNd…
l
r(
l
p†°dONLNd 
r

)ascal OSErr MyEventHandlev@°dONLNd„



‡)ñ$r (const AppleEvent *theAppleEvent, °dONLNd


&
+
 †°dONLNd


&
)
 @°dONLNd


&
∞)const AppleEvent *reply, °dONLNd6
(

4
(
1

 †°dONLNd7
(

4
)
 @°dONLNd8
(

4
í)long handlerRefcon);°dONLNdM
@l
L
(
Il(After extracting all known parameters frÚÄ°dONLNdu
@

L
?)≤om the ª°dONLNd|
@
?
L
€)!"Apple event, every handler should °dONLNdû
Ml
Y”(
Vldetermine whether the |`°dONLNd¥
M”
Y
k)g"Apple event contains any further r˙Ä°dONLNd÷
M
k
Y
Ç)òequir¿°dONLNd€
M
É
Y
«)ed parameters. Ä°dONLNdÍ
M
«
Y
Õ)D
Yÿ°dONLNdÎ
M
Ã
Y
›)our °dONLNdÔ
Zl
f
(
cl"handler can determine whether it r뇰dONLNd
Z

f
N)öetrieved all the r¡@°dONLNd#
Z
N
f
e)HequirÿÄ°dONLNd(
Z
e
f
÷)ed parameters by checkinÁ°dONLNd@
Z
÷
f
fi)qg °dONLNdB
gl
sñ(
pl    whether t`°dONLNdK
gó
s§)+he `°dONLNdN
g§
s
)keyMissedKeywordAttr‡°dONLNdb
g

s
Ò)x6 attribute exists. If the attribute exists, then your °dONLNdò
tl
Ä∑(
}lhandler has not rø¿°dONLNd©
t∑
ġ)Ketrieved all the rÔ °dONLNdª
tˇ
Ä
)Hequir`°dONLNd¿
t

Ä
À)&ed parameters and should immediately r\†°dONLNdÊ
t
À
Ä
Ú)¥    eturn an °dONLNdÔ
Ål
çx(
älerr
@°dONLNdÚ
Åy
çÇ)or¨°dONLNdÙ
ÅÅ
ç
0),. If the attribute does not exist, then the _ °dONLNd 
Å
0
ç
Ÿ)Ø$Apple event does not contain any morm@°dONLNdD
Å
Ÿ
ç
‡)©e °dONLNdF
él
öo(
ól
rE°dONLNdG
ép
öá)equir\@°dONLNdL
éá
ö
¬)Fed parameters, although it may contain additional optional parameters.°dONLNdì
†l
¨(
©lThe ]`°dONLNdó
†
¨
r)2Apple Event Manager determines which parameters arj°dONLNd…
†
r
¨
∑)Ûe optional accor @°dONLNdŸ
†
∏
¨
Í)Fding to the °dONLNdÂ
≠l
πç(
∂lkeywor˘`°dONLNdÎ
≠ç
π–)!ds listed in the ¿°dONLNd¸
≠—
π
U)DkeyOptionalKeywordAttrÄ°dONLNd
≠
U
π
©)Ñ attribute. The sourK`°dONLNd&
≠
©
π
Ú)Tce application is °dONLNd8
∫l
Δo(
√l
rE°dONLNd9
∫p
Δ
)"esponsible for adding these keyworç`°dONLNd[
∫

Δ
5)ù
ds to the ˚`°dONLNde
∫
5
Δ
π)(keyOptionalKeywordAttrÛ °dONLNd{
∫
π
Δ
Ê)Ñ attribute, °dONLNdá
«l
”õ(
–lbut is not rD¿°dONLNdì
«ú
”≥)0equir\°dONLNdò
«≥
”
å)5ed to do so, even if that parameter is listed in the ›@°dONLNdÕ
«
å
”
Ë)ŸApple Event Registry: °dONLNd„
‘l
‡¨(
›lStandard Suites6‡°dONLNdÚ
‘≠
‡
)A as an optional parameterÍÄ°dONLNd
‘

‡
N)o. If the sour¯‡°dONLNd
‘
N
‡
⁄)2 ce application does not add the °dONLNd8
·l
Ì∫(
Ílnecessary keyworJ°dONLNdH
·ª
Ìfl)O    d to the {°dONLNdQ
·fl
Ì
c)$keyOptionalKeywordAttrr¿°dONLNdg
·
c
Ì
≠)Ñ attribute, the tarR°dONLNdz
·
≠
Ì
Ò)Jget application °dONLNdä
Ól
˙s(
˜ltrá`°dONLNdå
Ós
˙÷)eats the parameter as r@¿°dONLNd£
Ó◊
˙Ó)dequirX°dONLNd®
ÓÓ
˙
)ed for that q °dONLNd¥
Ó

˙
)0Apple event. If the tarS°dONLNdÀ
Ó

˙
Ì)aget application supports °dONLNd‰
˚l©(lthe parameter±°dONLNdÒ
˚©
    )=, it should handle the Z`°dONLNd    
˚
    
q)`Apple event as the souræ °dONLNd    
˚
q
)hce application expects. If the °dONLNd    >lx(ltará`°dONLNd    Ax
¬)Jget application does not support the parameter and checks whether it has rP†°dONLNd    ã
√
Ù(
√eceived all °dONLNd    ól!Ä(lthe r¢`°dONLNd    úÄ!ó)equirπ†°dONLNd    °ó!È)ed parameters, it fi§Ä°dONLNd    µÍ!
")Snds that ther« °dONLNd    ¬
"!
√)8&e’s another parameter that the client °dONLNd    Ë"l.≈(+lapplication consider=¿°dONLNd    ¸"Δ.◊)Zed rh °dONLNd
"◊.Ó)equir`°dONLNd
"Ó.
6)ed, and should r¶°dONLNd
"
6.
d)Heturn the rÄ°dONLNd
 "
e.
î)/esult code # °dONLNd
+"
î.
Ù)/errAEParamMissed °dONLNd
;"
Ù.
ˆ)`
 °dONLNd
</l;
(8l'without attempting to handle the event.dONLNd
c/
;
)∞
 °dONLNd
eAlMö(JlListing 4-1솰dONLNd
pAöMü).
1솰dONLNd
qAüM
9)$ shows a function that checks for a Ä°dONLNd
ïA
:M
≤)õkeyMissedKeywordAttr°dONLNd
©A
≤M
fl)x attribute. ( °dONLNd
µA
flM
Ê)-
Ab¿°dONLNd
∂A
ÊM
Ë)
 °dONLNd
∑NlZ
7(Wl2handler calls this function after getting all the œÄ°dONLNd
ÈN
7Z
:)À
rîÄ°dONLNd
ÍN
;Z
R)equir´¿°dONLNd
ÔN
RZ
_)ed  °dONLNd
ÚN
`Z
fl)parameters it knows about fr”`°dONLNdN
flZ
Ô)om °dONLNd[lgy(dlan s°dONLNd[yg±)Apple event.ˇ4Ä@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-35
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHn4gHn"hH_

ˇ·ˇ‚7^    °dONLNd\ägª(däListing 4-11°dONLNd\Œg‘)D
A0°dONLNd\‘g
=) function that checks for a ,
Courier    ∞°dONLNd*\
=g
°)ikeyMissedKeywordAttr°dONLNd>\
©g
Ã)l
 attribute
°dONLNdJväÇ
(ä@FUNCTION MyGotRequiredParams (theAppleEvent: AppleEvent): OSErr;°dONLNdãÑäêú*VAR°dONLNdêíúû¿+myErr:°dONLNdúí
û
,)lOSErr;°dONLNd§†ú¨Í(©úreturnedType:°dONLNd∑†
¨
>)l    DescType;°dONLNd¬Æú∫fi(∑úactualSize:°dONLNd”Æ
∫
&)lSize;°dONLNdŸºä»®(≈äBEGIN°dONLNd‡ ú÷
ò+*myErr := AEGetAttributePtr(theAppleEvent, °dONLNd
ÿ
>‰
D+¢
 †°dONLNd
ÿ
D‰
»)keyMissedKeywordAttr, °dONLNd
3ʈÚ
(Ôˆ  °dONLNd
9Ê
>Ú
D)H
 †°dONLNd
:Ê
DÚ
Ï)typeWildCard, returnedType, °dONLNd
aÙ
>

D(˝
>
 †°dONLNd
bÙ
D

º)NIL, 0, actualSize);°dONLNd
x
ú

b(
ú!IF myErr = errAEDescNotFound THEN°dONLNd
§

b

h)Δ
 °dONLNd
®
Æ

å(
Æ%{you got all the required parameters}°dONLNd
–
Æ
*
V*MyGotRequiredParams := noErr°dONLNd
Ó
,ú
8
>(
5úELSE IF myErr = noErr THEN °dONLNd
,
b
8
h)Δ
 °dONLNd
:Æ
F
t(
CÆ!{you missed a required parameter}°dONLNd<
HÆ
T
û*(MyGotRequiredParams := errAEParamMissed;°dONLNde
Vä
b¢(
_äEND;°dONLNdj
nä
zø*The code in @†°dONLNdv
n¿
zÓ)6Listing 4-1T@°dONLNdÅ
nÓ
zÛ).
1T@°dONLNdÇ
nÛ
z
)
 uses the ¸`°dONLNdå
n

z
Å)(AEGetAttributePtrˆ°dONLNdù
n
Å
z
÷)f function to get the °dONLNd≤
{ä
á
(
ÑäkeyMissedKeywordAttrxÄ°dONLNdΔ
{

á
®)x) attribute. This attribute contains the f˜°dONLNdÔ
{
®
á
º)¶irst rñ`°dONLNdı
{
Ω
á
‘)equir≠†°dONLNd˙
{
‘
á)ed parameterʆ°dONLNd
{
á):, °dONLNd
àä
î£(
ëäif anyÅ°dONLNd
à¢
î
), that your handler didn’t r¯Ä°dONLNd*
à

î
D)vetrieve. If K`°dONLNd6
à
E
î
´)-AEGetAttributePtrE°dONLNdG
à
´
î
±)f rä°dONLNdI
à
±
î
fl)eturns the °dONLNdT
ïä
°(
ûäerrAEDescNotFoundy†°dONLNde
ï
°ˆ)f r憰dONLNdg
ïˆ
°
7)esult code, the A@°dONLNdw
ï
8
°
æ)BApple event doesn’t contain a °dONLNdï
¢ä
Æ
(
´äkeyMissedKeywordAttrxÄ°dONLNd©
¢

Æ
I)x attribute. If the $`°dONLNdº
¢
I
Æ)G,Apple event doesn’t contain this attribute, °dONLNdË
Øä
ª
È(
∏äRthen your handler has extracted all of the parameters that the client application °dONLNd:
ºä
»Ø*consider‡°dONLNdB
º∞
»¡)&ed r1@°dONLNdF
º¡
»ÿ)equirHÄ°dONLNdK
ºÿ
»Á)ed. °dONLNdP
Ί
⁄£(
◊äIf the ¿°dONLNdW
Τ
⁄

)AEGetAttributePtr    `°dONLNdh
Œ


⁄
8)f function r‹†°dONLNds
Œ
7
⁄
U)-eturns p¿°dONLNdz
Œ
V
⁄
t)noErrn‡°dONLNd
Œ
t
⁄
ñ)     as the rŒ@°dONLNdà
Œ
ñ
⁄
Ó)"esult code, then the °dONLNdù
ۊ
Á
◊(
‰äNattribute does exist, meaning that your handler has not extracted all of the ro@°dONLNdÎ
€
◊
Á
Ó(
‰
◊equirÜÄ°dONLNd
€
Ó
Á
˚)ed °dONLNdÛ
Ëä
Ù
X(
Òä/parameters. In this case, your handler should rcÄ°dONLNd"
Ë
X
Ù
å)Œeturn an errç@°dONLNd.
Ë
å
Ù
Δ)4or and not pr≤‡°dONLNd;
Ë
Δ
Ù
):
ocess the °dONLNdE
ıä
•(
˛äApple˝Ä°dONLNdJ
ı•
ß)
 }Ä°dONLNdK
ı®
¬)event.°dONLNdRä£(äThe fi»Ä°dONLNdX£¥)rst rÄ°dONLNd]µÂ)
emaining rd¿°dONLNdg¸)0equir|°dONLNdl¸
_)ed parameter is specifi‡°dONLNdÉ
`
º)ded by the data of the °dONLNdôä 
(äkeyMissedKeywordAttrxÄ°dONLNd≠
 
ë)x# attribute. If you want this data r¯ °dONLNd–
ë 
)èeturned, specify a bufÆ°dONLNdÊ
Ò 
)`fer to °dONLNdÌ!ä-
(*ä"hold the data. Otherwise, specify º¿°dONLNd!
-
0)îNIL]@°dONLNd!
0-
]) as the buf¨†°dONLNd!
]-
‡)- fer and 0 as the size of the buf°dONLNd=!
·-
Ì)Ñfera¿°dONLNd@!
Ï-)    . If you °dONLNdI.ä:¬(7äspecify a bufy`°dONLNdV.¬:
£)85fer to hold the data, you can check the value of the É`°dONLNdã.
£:
fl)·
actualSize†°dONLNdï.
fl:)< parameter °dONLNd†;äGÍ(Däto see if the data is larR†°dONLNdπ;ÍG
0)`ger than the bufïÄ°dONLNd…;
0G
|)Ffer you allocated.°dONLNd‹MäY≠(VäFor mor¿°dONLNd„MÆY
8)$e information about specifying @°dONLNdM
8Y
Ë)ä'Apple event parameters as optional or r‘¿°dONLNd)M
ÁY
˛)ØequirÏ°dONLNd.M
˛Y)ed, °dONLNd2Zäfö(cäsee –@°dONLNd6Zöf
J)'“Specifying Optional Parameters for an ¿°dONLNd]Z
Kf
fi)±Apple Event” beginning on page ¿°dONLNd|Z
flf
Ï)î5-7c†°dONLNdZ
Ïf
Ò). ˇ'†@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-36    )B    Handling ê)&Apple Events4^*¿
¯

k*r
¯4l*r
¯ mlm
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\lk«(glReplying to an ˝í°dONLNd\Δk
)ZApple Eventˇˇˇˇˇˇ€r(g

4
°dONLNdrl~r({l
Y@Ä°dONLNdrr~¨)our handler r◊‡°dONLNd*r¨~
):outine for a particular È¿°dONLNdBr
~
U)cApple event is r‡°dONLNdRr
V~
€)Gesponsible for performing the °dONLNdplãç(àlaction r¶‡°dONLNdxçã’)!equested by the T‡°dONLNdà’ã
i)H!Apple event, and can optionally r\Ä°dONLNd©
iã
Ø)îeturn data in a rÄ°dONLNd∫
∞ã
≈)Geply u`°dONLNdø
ŋ
‚)Apple °dONLNd≈ålòú(ïlevent. The ™†°dONLNd–åúò
L)0&Apple Event Manager passes a default r`°dONLNdˆå
Mò
b)±eply q@°dONLNd˚å
bò
fl)Apple event to your handlerò°dONLNd
å
flò
˜)}. The °dONLNd
ôl•ë(¢l    default r0 °dONLNd
%ôí•ß)&eply ï°dONLNd
*ôß•
Δ)?Apple event has no parameters when it is passed to your handler‘°dONLNd
iô
Δ•
À(¢
Δ. ¶`°dONLNd
kô
À•
—)
Yf‡°dONLNd
lô
—•
‚)our °dONLNd
p¶l≤

(Øl#handler can add parameters to the rÑÄ°dONLNd
ì¶

≤
)ûeply È`°dONLNd
ò¶
≤
Δ)(Apple event. If the client application r^ °dONLNd
¿¶
«≤
Ò)®    equested °dONLNd
…≥løw(ºla r≈°dONLNd
Ã≥wøä)eplyÏÄ°dONLNd
–≥âøû), the ÎÄ°dONLNd
÷≥ûø
)Apple Event Manager rfl`°dONLNd
Î≥
ø
8)heturns the rdONLNd
˜≥
9ø
N)3eply ˙¿°dONLNd
¸≥
Nø
ø)Apple event to the client. °dONLNd≈l—É(ŒlThe rÄ¿°dONLNd≈É—ò)eply †°dONLNd"≈ò—˙)Apple event is identifi,`°dONLNd9≈˚—
&)c
ed by the ,
CourierÖ‡°dONLNdC≈
&—
Ä)+kCoreEventClassÄ@°dONLNdR≈
Ä—
Ê)Z event class and by the °dONLNdj“lfi¢(€l    kAEAnswer|†°dONLNds“¢fiÃ)6
 event ID.e†°dONLNd}“Õfi
Q)+! If the client application specif–`°dONLNdû“
Qfi
q)Ñied the {Ä°dONLNd¶“
rfi
Æ)!
kAENoReplyw¿°dONLNd∞“
Æfi
≥)< f °dONLNd≤“
¥fi
fl)lag in the °dONLNdΩfllÎä(Ëlreply~ °dONLNd¬fläÎÿ) parameter of the µ‡°dONLNd‘flÿθ)NAESend≥†°dONLNd⁄fl¸Î
8)$ function, the @‡°dONLNdÈfl
9Î
◊)="Apple Event Manager passes a null °dONLNdÏl¯ü(ıldescriptor rfl@°dONLNdÏü¯±)3ecorS†°dONLNdÏ≤¯¯)d (a descriptor r"Ä°dONLNd,Ï˘¯
)Gecorñ‡°dONLNd0Ï
¯
5)
d of type ô@°dONLNd:Ï
5¯
_)*typeNulñ†°dONLNdAÏ
_¯
e)*
lñ@°dONLNdBÏ
e¯
fl) whose data handle has the °dONLNd]˘l
Ü(
lvalue _`°dONLNdc˘á
ô)NIL^@°dONLNdf˘ô
ú)
)≤ °dONLNdg˘ú

A)' to your handler instead of a default r„Ä°dONLNdé˘
A

V)•eply H`°dONLNdì˘
W

í)Apple event. eÄ°dONLNd†˘
í

ò);
Y&°dONLNd°˘
ò

Ô)our handler should °dONLNd¥
l
˝(
l"check the descriptor type of the rã@°dONLNd÷
˝

)ëeply  °dONLNd€



a)Apple event beforöÄ°dONLNdÏ

b

Œ)Pe attempting to add any °dONLNd
l
Í(
lattributes or parameters to it–@°dONLNd"
Í
Ô)~. q‡°dONLNd$
Ô

)An aäÄ°dONLNd(



)ttempØ°dONLNd-



')t t≥¿°dONLNd0

'

O)        o add an S¿°dONLNd9

P

Ì))#Apple event attribute or parameter °dONLNd\
 l
,Δ(
)lto a null descriptor r¿`°dONLNdr
 Δ
,ÿ)Zecor4¿°dONLNdv
 Ÿ
,Á)d g_†°dONLNdy
 Á
,
)enerate¬‡°dONLNdÄ
 

,
) 
sˇ‡°dONLNdÅ
 

,
') an errRÄ°dONLNdà
 
(
,
1)or˝@°dONLNdä
 
0
,
5). °dONLNdç
2l
>ÿ(
;lIf the client application r™°dONLNd®
2ÿ
>
)lequests a r^‡°dONLNd≥
2

>
)/eplyÜ`°dONLNd∑
2

>
.), the Ö`°dONLNdΩ
2
.
>
ú)Apple Event Manager pr{`°dONLNd”
2
ú
>
Ø)nepar °dONLNd◊
2
∞
>
Δ)es a r◊¿°dONLNd›
2
Δ
>
€)eply °dONLNd‚
?l
K
>(
Hl1Apple event for the client by passing a default ré`°dONLNd
?
>
K
S)“eply Û@°dONLNd
?
S
K
–)Apple event to your handler°dONLNd3
?
—
K
‹)~. T:¿°dONLNd6
?
‹
K
È)he °dONLNd9
Ll
Xë(
Ul    default r0 °dONLNdB
Lí
Xß)&eply ï°dONLNdG
Lß
X
Δ)?Apple event has no parameters when it is passed to your handler‘°dONLNdÜ
L
Δ
X
À(
U
Δ. ¶`°dONLNdà
L
À
X
—)
Yf‡°dONLNdâ
L
—
X
‚)our °dONLNdç
Yl
e
(
bl'handler can add any parameters to the re°dONLNd¥
Y

e
2)±eply …‡°dONLNdπ
Y
2
e
”)&Apple event. If your application is a °dONLNdfl
fl
r≥(
olspelling checker+‡°dONLNdÔ
f≥
r
)G, for example, you can rÙ†°dONLNd
f

r
ö)geturn a list of misspelled worØ°dONLNd%
f
õ
r
Ë)Åds in a parameter °dONLNd6
f
Ë
r
Ì)M. °dONLNd9
xl
ÑÀ(
ÅlWhen your handler fi⁄†°dONLNdM
xÀ
ÑÛ)_    nishes prÄ°dONLNdV
xÛ
Ñ
()(ocessing an ’¿°dONLNdb
x
(
Ñ
o)5Apple event, it rê@°dONLNds
x
p
Ñ
ö)H
eturns a ri`°dONLNd}
x
ö
Ñ
‘)*esult code to °dONLNdã
Öl
ëÿ(
élAEProcessAppleEveny@°dONLNdù
Öÿ
ëfi)l
tx‡°dONLNdû
Öfi
ë
)    , which r@°dONLNdß
Ö

ë
:)'eturns this r"Ä°dONLNd¥
Ö
:
ë
≠)5esult code as its function r °dONLNd–
Ö
≠
ë
Á)sesult. If your °dONLNdfl
íl
ûî(
õl    handler r( °dONLNdË
íï
ûŸ))eturns a nonzer„ °dONLNd˜
íŸ
û‰)Do rù†°dONLNd˙
íÂ
û
ª)/esult code, and if you have not added your own °dONLNd)
ül
´¿(
®lkeyErrorNumberz¿°dONLNd7
ü¿
´)T
 parameterŒ`°dONLNdA
üÔ
´
)/, the Õ`°dONLNdG
ü

´
Ä)Apple Event Manager also r‹ °dONLNda
ü
Ä
´
µ)|eturns this rÓ`°dONLNdn
ü
µ
´
‰)5esult code °dONLNdy
¨l
∏t(
µlto7‡°dONLNd{
¨u
∏w)    
 ∑‡°dONLNd|
¨w
∏
)'the client application by putting the r˙Ä°dONLNd£
¨

∏
e)§esult code into a o¿°dONLNdµ
¨
f
∏
∫)KkeyErrorNumberjÄ°dONLNd√
¨
∫
∏
Ï)T parameter °dONLNdŒ
πl
ŏ(
¬l    for the rfi`°dONLNd◊
πè
≈§)#eply C@°dONLNd‹
π•
≈
fl)IApple event. The client can check for the existence of this parameter to °dONLNd%
Δl
“
>(
œl-determine whether the handler performed the rî°dONLNdR
Δ
>
“
Ö)“equested action.°dONLNdc
ÿl
‰Í(
·lThe client application specifiˇ °dONLNdÅ
ÿÍ
‰
N)~es whether it wants a rfl@°dONLNdò
ÿ
N
‰
c)deply D °dONLNdù
ÿ
d
‰
˜)!Apple event or not by specifying °dONLNdæ
Âl
Òr(
Ól
flå¿°dONLNd¿
Âr
Òä)ags (rÒ¿°dONLNdΔ
Âä
Òò)eprÇÄ°dONLNd…
Âô
Ò
)esented by constants) in the T‡°dONLNdÊ
Â

Ò
F)}sendModeQ‡°dONLNdÓ
Â
F
Ò
î)0 parameter of the ↰dONLNd    
Â
î
Ò
∏)NAESendá`°dONLNd    
Â
∏
Ò
‚)$
 function.°dONLNd    
˜lº(lIf the client specifi@°dONLNd    &
˜Ωÿ)Qes the @°dONLNd    -
˜Ÿ
!)kAEWaitReply˚¿°dONLNd    9
˜
 
()G flàÄ°dONLNd    <
˜
)
Q)
ag in the .¿°dONLNd    F
˜
R
Ç))sendMode+¿°dONLNd    N
˜
Ç
≤)0
 parameter`°dONLNd    X
˜
±
Δ)/, the ‹¿°dONLNd    ^
˜
Δ
Í)AESend⁄Ä°dONLNd    d
˜
Í
Ï)$
 °dONLNd    elø(lfunction does not rÙ`°dONLNd    xø
B)Seturn until the timeout specifiä°dONLNd    ó
C
n)Ñ
ed by the „Ä°dONLNd    °
n
¬)+timeoutInTicksfi@°dONLNd    Ø
¬
Ù)T parameter °dONLNd    ∫lÇ(lexpir!¿°dONLNd    øÉË)es or the server applica‡°dONLNd    ◊ÈÙ)ftioØ °dONLNd    ⁄Ù
)n r≈Ä°dONLNd    ›

*)
eturns a rû†°dONLNd    Á
*
=)*eplyΔ °dONLNd    Î
<
ƒ). When the server application rÁÄ°dONLNd


ƒ
Í)à    eturns a °dONLNd
l*o('l
rE°dONLNd
p*É)eplylÄ°dONLNd
Ç*ó), the …‡°dONLNd
ó*µ)reply»°dONLNd
#µ*Ú) parameter to ꇰdONLNd
1Û*
)>AESend醰dONLNd
7
*
U)$ contains the r°@°dONLNd
F
U*
j)>eply  °dONLNd
K
k*
Ù)Apple event that your handler °dONLNd
i+l7o(4l
rE°dONLNd
j+p7∞)eturned to the ¿°dONLNd
y+±7
#)AAEProcessAppleEvent†°dONLNd
å+
#7
J)r     functionù‡°dONLNd
ï+
J7
u)'    . When thû°dONLNd
û+
u7
¬)+e client applicatiokÄ°dONLNd
±+
√7
¯)Nn no longer °dONLNd
Ω8lDã(Alneeds tˇ¿°dONLNd
ƒ8ãDΩ)he original æ °dONLNd
–8ΩD
)2Apple event and the r`°dONLNd
Â8
D
H)a    eply evenÊÄ°dONLNd
Ó8
HD
¬)*t, it must dispose of them, bo‡°dONLNd8
√D
fl){ut the °dONLNdElQ
(Nl Apple Event Manager disposes of t†°dONLNd2E
Q
*)ò    both the Ä°dONLNd;E
+Q
ã)'Apple event and the r^¿°dONLNdPE
ãQ
€)`eply event for the °dONLNdcRl^
([l"server application when the serverLÄ°dONLNdÖR
^
8)ö’s handler rx‡°dONLNdëR
8^
a)2
eturns to D‡°dONLNdõR
b^
‘)*AEProcessAppleEvent=¿°dONLNdÆR
‘^
÷)r
.Ω¿°dONLNdØR
÷^
ÿ)
 =¿°dONLNd∞R
Ÿ^
€)
 ˇ=¥@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-37
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\äh⁄(eäIf the client specifi@°dONLNd\€h¯)Qed the ,
Courierfl°dONLNd\¯h
F)kAEQueueReply⁄ °dONLNd)\
Fh
N)N flf‡°dONLNd,\
Oh
ç)    ag, the client r∂¿°dONLNd<\
çh
√)>eceives the rÒ‡°dONLNdI\
√h)6eply event at a °dONLNdYiäu
(rälater time during its normal pr2Ä°dONLNdxi
u
})áocessing of other events.=‡°dONLNdëi
}u
)l
 °dONLNdì{äáê(Ñä
Y@Ä°dONLNdî{êá
P),our handler should always set its function r±Ä°dONLNd¿{
Pá
r)¿    esult to °‡°dONLNd…{
sá
ë)#noErr†°dONLNdŒ{
ëá
‹) if it successfully °dONLNd„àäîø(ëähandles the ¨Ä°dONLNdÔàøî
)5Apple event. If an err¸@°dONLNd
à
î
´)^ or occurs, your handler should r¶¿°dONLNd
%à
¨î
‚)èeturn either °dONLNd
2ïä°
(ûäerrAEEventNotHandledxÄ°dONLNd
Fï
°
b)x or some other nonzer °dONLNd
[ï
c°
n)ao r◊†°dONLNd
^ï
n°
≈)esult code. If the errl@°dONLNd
tï
Δ°
—)Xor °dONLNd
x¢äÆ
°(´ä>occurs because your application cannot understand the event, rË¿°dONLNd
∂¢
°Æ
ª(´
°eturn °dONLNd
ºØäª
(∏äerrAEEventNotHandledxÄ°dONLNd
–Ø
ª
L)x. This allows the i@°dONLNd
‚Ø
Lª)J*Apple Event Manager to look for a handler °dONLNdºä»
9(≈ä(in the system special handler or system  °dONLNd4º
:»    )∞/Apple event dispatch tables that might be able °dONLNdc…ä’ï(“äto ∑‡°dONLNdf…ï’
    )handle the event. If the errd°dONLNdÇ…

’
˘)u7or occurs because the event is impossible to handle as °dONLNdπ÷䂶(fläspecifiÓ °dONLNd¿÷¶‚π)ed, ròÄ°dONLNd≈÷∫‚Ë)eturn the r°dONLNd–÷È‚
)/esult code r⁄†°dONLNd‹÷
‚
Î)2.eturned by whatever function caused the failur∫‡°dONLNd
÷
΂)–e, or °dONLNd„äÔ”(Ïäwhatever other r!`°dONLNd „‘Ô
!)Jesult code is appr솰dONLNd2„
!Ô
B)Mopriate.°dONLNd;ıä

¿(˛äFor exampleq†°dONLNdFı¡

Ú)7, suppose yE@°dONLNdQıÛ


=)2our application r0`°dONLNdbı
=


•)Jeceives a Get Data evenÄ¿°dONLNdyı
•


Æ)ht r °dONLNd|ı
Ø


»)
equesx†°dONLNdÅı
»


fl)ting tΔ@°dONLNdáı
fl

)he name of °dONLNdí
ä
¨(
äthe curr`°dONLNdö
≠
‹)#ent printerYÄ°dONLNd•
€

π).1, and your application cannot handle such an even@°dONLNd÷

∫
)flt. In this situation, °dONLNdÏ
ä
è(
ä
y °dONLNdÌ
ê
¬)ou should rfl‡°dONLNd¯
¬
‹)2eturn 7°dONLNd˛
›

U)errAEEventNotHandled/Ä°dONLNd

U
)x* in case another handler available to the °dONLNd<
ä
(
(
%äApple Event Manager can handl`°dONLNdY


(
π)ê%e the Get Data event. This strategy al °dONLNd~

π
()üllows users to take °dONLNdí
)ä
5
#(
2ä#advantage of system capabilities fr^`°dONLNdµ
)
#
5
¸)ô0om within your application via system handlers. °dONLNdÊ
;ä
Gí(
Dä
H—`°dONLNdÁ
;í
G≤)owever†°dONLNdÌ
;≥
G
±)!;, if your application cannot handle a Get Data event that rN†°dONLNd(
;
±
G
Í)˛equests the fi(†°dONLNd6
;
Î
G
˘):fth °dONLNd:
Hä
T
ˇ(
QäPparagraph in a document because the document contains only four paragraphs, you °dONLNdä
Uä
aØ*should rT °dONLNdí
UØ
a
)%eturn some other nonzerÁ¿°dONLNd©
U

a
/)lo err^Ä°dONLNdÆ
U
0
a
9)or    @°dONLNd∞
U
9
a
f)    , because f¨`°dONLNdª
U
f
a)-#urther attempts to handle the eventÌ°dONLNdfi
U
a)ú ar2°dONLNd·
U
a)e °dONLNd„
bä
n±(
kä    pointless¿°dONLNdÏ
b≤
n¥)(
.°dONLNdÓ
tä
Ä™(
}äIf your “`°dONLNdˆ
t™
Ä
.) Apple event handler calls the €†°dONLNd
t
.
Ä
d)Ñ    AEResolveÿ@°dONLNd
t
d
Ä
°)6 function and S†°dONLNd+
t
¢
Ä
ÿ)>    AEResolveP@°dONLNd4
t
ÿ
Ä
˝)6
 calls an °dONLNd>
Åä
ç
œ(
ääLobject accessor function in the system object accessor dispatch table, your ™Ä°dONLNdä
Å
œ
ç(
ä
œApple event °dONLNdñ
éä
öŸ(
óähandler may not rÄ°dONLNdß
é⁄
ö
î)P+ecognize the descriptor type of the token r9°dONLNd“
é
î
ö
¸)∫eturned by the functionw‡°dONLNdÈ
é
¸
ö)h. In °dONLNdÓ
õä
ß±(
§ä
this case,0°dONLNd¯
õ≤
ß
)( your handler should r堡dONLNd
õ

ß
C)ceturn the r_ °dONLNd
õ
D
ß
s)/esult code b¿°dONLNd$
õ
s
ß
˜)/errAEUnknownObjectTypeZÄ°dONLNd:
õ
˜
ß
¸)Ñ. °dONLNd<
®ä
¥Á(
±äWhen your handler r퇰dONLNdO
®Á
¥
)]eturns this r• °dONLNd\
®

¥
])5esult code, the '¿°dONLNdl
®
^
¥)B'Apple Event Manager attempts to locate °dONLNdì
µä
¡≤(
æä    a system 
¿°dONLNdú
µ≥
¡
:))Apple event handler that can r`°dONLNd∫
µ
:
¡
µ)áecognize the token. For mor`°dONLNd’
µ
µ
¡){e information, see °dONLNdË
Š
Œ
(
Àä"“Installing Entries in the Object I@°dONLNd

¬

Œ
p)çAccessor Dispatch T;@°dONLNd
¬
p
Œ
ç)Yables,”1‡°dONLNd$
¬
é
Œ
€) which begins on ¢@°dONLNd5
¬
€
Œ
Ú)Mpage } °dONLNd:
¬
Û
Œ)6-21—°dONLNd>
¬
Œ)
.°dONLNd@
‘ä
‡ê(
݊
T†¿°dONLNdA
‘ê
‡ù)he ]`°dONLNdD
‘ù
‡
â)1Apple Event Manager automatically adds any nonzer°dONLNdu
‘
ä
‡
ï)Ìo r–Ä°dONLNdx
‘
ï
‡)esult code that your handler °dONLNdï
·ä
Ìç(
Íä
rE°dONLNdñ
·é
Ìø)eturns to a ë°dONLNd¢
·ø
Ì
)1keyErrorNumberã¿°dONLNd∞
·

Ì
e)T parameter in the rx‡°dONLNd√
·
e
Ì
z)Reply ›¿°dONLNd»
·
z
Ì
Ù)Apple event. In addition to °dONLNd‰
Óä
˙ç(
˜ä
rE°dONLNdÂ
Óé
˙¬)eturning a r*°dONLNdÒ
Ó¬
˙
Y)4#esult code, your handler can also r∞†°dONLNd    
Ó
Y
˙
ç)óeturn an err⁄`°dONLNd     
Ó
ç
˙
–)4or string in the °dONLNd    1
˚äfi(äkeyErrorStringz¿°dONLNd    ?
˚fi
0)T parameter of the rwÄ°dONLNd    R
˚
0
E)Reply ‹`°dONLNd    W
˚
E
Ä)Apple event. ˘Ä°dONLNd    d
˚
Ä
Ü);
Y∫°dONLNd    e
˚
Ü
Á)our handler should prb†°dONLNd    z
˚
Ë)bovide °dONLNd    ÄäÓ(ämeaningful text in the â`°dONLNd    óÓ
B)dkeyErrorStringÑ °dONLNd    •
B
r)T
 parameter◊¿°dONLNd    Ø
q)/&, so that the client can display this °dONLNd    ’ä!ˆ(ästring to the user if desir\Ä°dONLNd    ˆ!
)led.¡‡°dONLNd    Û
!
)
 °dONLNd    ı'ä3Ω(0äListing 4-12 @°dONLNd

'æ3ƒ)4 s›@°dONLNd
'ƒ3
#)hows how to add the ¢¿°dONLNd
'
$3
x)`keyErrorStringùÄ°dONLNd
%'
x3
 )T parameter to the rà¿°dONLNd
8'
 3
fl)Reply ̆°dONLNd
='
fl3
¸)Apple °dONLNd
C4ä@∏(=äevent. See  @°dONLNd
N4π@
/)/“Adding Parameters to an h@°dONLNd
g4
/@
ì)vApple Event” on page &‡°dONLNd
|4
î@
°)e5-5z¿°dONLNd
4
°@
) for a description of the °dONLNd
ôAäMÿ(JäAEPutParamPtr{ °dONLNd
¶AÿM
)N
 function.ˇv@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-38    )B    Handling ê)&Apple Events4^*¿
¯

g*n
¯4g*n
¯"h*_

ˇ·ˇ‚7^
°dONLNd\lgù(dlListing 4-12°dONLNd\∞g›)DAdding the ,
CourierP°dONLNd\fig
$).keyErrorStringö0°dONLNd&\
)g
Ü)K parameter to the reply –°dONLNd>\
Üg
µ)]Apple event
°dONLNdKvlÇ
Ú(lAFUNCTION MyHandler (theAppleEvent: AppleEvent; reply: AppleEvent;°dONLNdìÑÿêfi+l
 †°dONLNdîÑfiê‰)
 @°dONLNdïщê
§) handlerRefcon: LongInt): OSErr; °dONLNd∂ílû~(õlVAR°dONLNdª†~¨¢+myErr:°dONLNd≈†Δ¨Í)HOSErr;°dONLNdÕÆ~∫®(∑~errStr:°dONLNdÿÆΔ∫)HStr255;°dONLNd‡ºl»ä(≈lBEGIN°dONLNdÁ ~÷
2+{handle your Apple event here}°dONLNd
Ê~Ú
‡*;{if an error occurs when handling an Apple event, set the }°dONLNd
EÙ~

ò*/{ function result and error string accordingly}°dONLNd
v
~

*IF myErr <> noErr THEN°dONLNd
é
~
ú*BEGIN°dONLNd
ñ
ê
*
+MyHandler := myErr;x‡°dONLNd
™


*
‘)r# {result code to be returned--the }°dONLNd
◊
,

8
‘+!{ Apple Event Manager adds this }°dONLNd
:

F
⁄*"{ result code to the reply Apple }°dONLNd.
H

T
¬*{ event as the keyErrorNumber t¿°dONLNdL
H
¬
T
»)¥
}°dONLNdW
V

b
V(
_
{ parameter}°dONLNdf
dê
p
V(
mê!IF (reply.dataHandle <> NIL) THEN°dONLNdä
rê
~
∂*1{add error string parameter to the default reply}°dONLNdæ
Äê
åÆ*BEGIN°dONLNd«
é¢
ö
¬+0{strings should normally be stored in resources}°dONLNd˚
ú¢
®
\*errStr := 'Why error occurred';°dONLNd
™¢
∂
∂*.myErr := AEPutParamPtr(reply, keyErrorString, °dONLNdX
∏
2
ƒ
Œ+êtypeIntlText, @errStr[1], °dONLNd~
Δ
2
“
í*length(errStr));°dONLNdë
‘ê
‡®(
›êEND;°dONLNdó
‚~
Óä(
Î~EN@°dONLNdô
‚ä
Óê)
D°dONLNdú
~
¸ñ(
˘~ELSE°dONLNd£
˛ê

+MyHandler := noErr;°dONLNd∑lÑ(lEND;°dONLNdº$l0‹*If your handler needs to rN °dONLNd÷$›0
√)q7eturn data to the client, it can add parameters to the °dONLNd1l=o(:l
rE°dONLNd1p=É)eplyà@°dONLNd1É=Ö)
 ©‡°dONLNd1Ö=¿)Apple event. Ù†°dONLNd 1¿=Û);Listing 4-13dONLNd,1Ù=
ª)4, shows how a handler for the Multiply event °dONLNdX>lJz(Gl(an•@°dONLNd[>zJ|)
 %@°dONLNd\>}J≠)
imaginary Õ‡°dONLNdf>¨J
Õ)/@Apple event that asks the server to multiply two numbers) might °dONLNd¶KlWo(Tl
rE°dONLNdßKpWá)eturn °dONLNd¨KàWä)
 ú °dONLNd≠KäWû)the ræÄ°dONLNd≤KûW
L)+esults of the multiplication to the client.ˇ7@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-39
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

gHn4gHn"hH_

ˇ·ˇ‚7^    °dONLNd\ägª(däListing 4-13°dONLNd\Œg
K)DAdding parameters to the reply á°dONLNd,\
Kg
z)}Apple event,
Courier
°dONLNd9väÇ
(äFUNCTION MyMultHandlerw¿°dONLNdOv
Ç
)Ñ
 w`°dONLNdPv
Ç
º)(theAppleEvent: AppleEvent; °dONLNduÑ
ê
å+reply: AppleEvent; °dONLNdëí
û
⁄* handlerRefcon: LongInt): OSErr; °dONLNd≤†ä¨ú(©äVAR°dONLNd∑Æú∫¿+myErr:°dONLNd√Æ
∫
,)lOSErr;°dONLNdÀºú»¸(≈únumber1,number2:°dONLNd·º
»
8)lLongInt;°dONLNdÎ ú÷‰(”úreplyResult:°dONLNd˝ 
÷
8)lLongInt;°dONLNd
ÿú‰fi(·úactualSize:°dONLNd
ÿ
‰
&)lSize;°dONLNd
ÊúÚÍ(ÔúreturnedType:°dONLNd
2Ê
Ú
>)l    DescType;°dONLNd
<Ùä
®(˝äBEGIN°dONLNd
C
ú

Ú+9{get the numbers to multiply from the parameters of the }°dONLNd
~
ú

Ï*8{ Apple event; put the numbers in the number1 and numberk°dONLNd
∂

Ï

˛(

Ï2 }°dONLNd
ª
ú
*
Ï(
'ú8{ variables and then perform the requested multiplicatiok°dONLNd
Û

Ï
*
¯(
'
Ïn}°dONLNd
˜
,ú
8
∞(
5ú.myErr := MyDoMultiply(theAppleEvent, number1, °dONLNd/
:
,
F
™+ênumber2, replyResult)x °dONLNdD
:
™
F
∞)~
;°dONLNdG
Hú
T¢(
Qú
I†°dONLNdH
H¢
TΔ)F myEr}`°dONLNdN
HΔ
T‰)$r = n{Ä°dONLNdS
H‰
T
)oErr THExÄ°dONLNd[
H

T
 )0N °dONLNd`
VÆ
b
t(
_Æ!IF (reply.dataHandle <> NIL) THEN°dONLNdÖ
d¿
p+9{return result of the multiplication in the reply Apple }°dONLNd¬
r¿
~Í*{ event}`°dONLNd…
rÍ
~)*
}°dONLNdŒ
Ä¿
åÍ(
â¿myErr :}`°dONLNd’
ÄÍ
å
t)*= AEPutParamPtr(reply, t¿°dONLNdÏ
Ä
t
å
‘)äkeyDirectObject,n¿°dONLNd¸
Ä
‘
å
⁄)`
 °dONLNd    
é
P
ö
V(
ó
P
t†°dONLNd

é
V
ö)ypeLongInteger, @replyResult,t¿°dONLNd'
é
ö
)Æ
 °dONLNd4
ú
P
®
V(
•
P
S†°dONLNd5
ú
V
®
Œ)izeOf(replyResult));°dONLNdK
™ú
∂
&(
≥úMyMultHandler := myErr;°dONLNdd
∏ú
ƒ
û*+{if an error occurs, set the error string }°dONLNdë
Δú
“
>*{ accordingly, as shown in u‡°dONLNd¨
Δ
>
“
Ü)¢Listing 4-12q`°dONLNd∏
Δ
Ü
“
å)H
}°dONLNd∫
‘ä
‡¢(
݊END;

H4H ä

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNdø
˜äŸ*%Disposing of –∂°dONLNdÃ
˜ÿ
Ñ)NApple Event Data Structuresˇˇˇˇˇˇ€r(
4
°dONLNdÈä
&(ä#Whenever a client application uses Z °dONLNd
&
…)ú#Apple Event Manager functions to cr¡`°dONLNd/
…)£eate a descriptor °dONLNdAä&ç(#ä
rE°dONLNdBé&†)ecorπ`°dONLNdF†&¯)d, descriptor list, or I@°dONLNd]˘&
5)YApple event rŸ°dONLNdj
5&
G)<ecorM`°dONLNdn
H&
c)d, the h °dONLNdu
c&
Ô)Apple Event Manager allocates °dONLNdì'ä3˚(0ämemory for these data strE°dONLNd¨'¸3
)ructur ‡°dONLNd±'
3
)es—Ä°dONLNd≥'
3
®)    " in the client’s application heap.fl@°dONLNd’'
®3
Í)å Likewise, wheÙ °dONLNd„'
Í3
˘)Bn a °dONLNdÁ4ä@‡(=äserver application e\@°dONLNd˚4·@˙)WxtractlÄ°dONLNd
4˙@˛)
s©Ä°dONLNd4˛@
;) a descriptor r¿°dONLNd4
<@
N)>ecor} °dONLNd4
N@
V)d ‡°dONLNd4
W@
^)    fr1¿°dONLNd4
^@
|)om an Ó@°dONLNd4
{@
≥)Apple event π°dONLNd+4
¥@
‹)9    by using ˛`°dONLNd44
‹@
˘)(Apple °dONLNd:AäM
(JäEvent Manager functions, the ˚†°dONLNdWA
M
z)ÑApple Event Manager cr_¿°dONLNdmA
{M
˛)meates a copy of the descriptor °dONLNdåNäZç(Wä
rE°dONLNdçNéZ†)ecorπ`°dONLNdëN†Z¶)
d’ °dONLNdíN¶Z®)
,U °dONLNdìN©Z´)
 ’ °dONLNdîN´Z
Y)(including the data to which its handle r∂@°dONLNdºN
YZ
s)Æefers, Õ°dONLNd√N
sZ
©)in the server}@°dONLNd–N
´Z)8’s application heap.°dONLNdÂ`äl”(iäWhenever you fi1°dONLNdÙ`‘l
?)Jnish using a descriptor re`°dONLNd`
?l
Q)kecorŸ¿°dONLNd`
Ql
Ï)%d or descriptor list that you have cr `°dONLNd6`
Ìl)ú    eated or °dONLNd?mäyº(väextracted frÿ °dONLNdKmºy⁄)2om an dONLNdQm⁄y
 )Apple event, yo‰°dONLNd`m
 y
O)F
u should dñ°dONLNdjm
Py
Ω)0ispose of the descriptor rø†°dONLNdÑm
Ωy
œ)mecor4°dONLNdàm
–y
Û)d—and °dONLNdézäÜõ(Éäther"`°dONLNdízúÜ
y)1eby deallocate the memory it uses—by calling the ‰`°dONLNd√z
yÜ
«)›AEDisposeDescflÄ°dONLNd–z
«Ü
Ó)N     functionm¿°dONLNdŸz
ÔÜ)(    . If the °dONLNd‚áäìΩ(êädescriptor rfl@°dONLNdÓáΩìœ)3ecorS†°dONLNdÚá–ì
)d you pass to Ø °dONLNdá
ì
[)=AEDisposeDesc™@°dONLNdá
[ì
ê)N (such as an 3‡°dONLNdá
ëì
…)6Apple event ˛†°dONLNd&á
…ì
Ã)8
r√†°dONLNd'á
Õì
fl)ecor8°dONLNd+á
‡ì
Ë)d ”¿°dONLNd-á
Ëì
)or an °dONLNd3îä†ó(ùäAEc°dONLNd5îò†ö)
 „°dONLNd6îö†ù)
r®°dONLNd7îû†∞)ecor`°dONLNd;
Q)%d) includes other nested descriptor rl`°dONLNd`î
Q†
c)†ecor‡¿°dONLNddî
c†
°)ds, one call to ¬‡°dONLNdtî
¢†
)?AEDisposeDescæ°dONLNdÅî
†)N will °dONLNdá°ä≠›(™ädispose of them all
‡°dONLNdö°fi≠„)T. ˇ"∫@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-40    )B    Handling ê)&Apple Events4^*¿
¯
°dONLNd\lh
2(el-When a client application adds a descriptor rï`°dONLNd-\
2h
D)Δecor    ¿°dONLNd1\
Eh
f)d to an –`°dONLNd9\
eh
ˆ) Apple event (for example, when °dONLNdXilu}(rlit cr`°dONLNd]i}u–)eates a descriptor r—‡°dONLNdqi–u‚)SecorF@°dONLNdui„u
)d by calling ,
Courierdž°dONLNdÇi
u
a)6AECreateDesc~ °dONLNdéi
au
Ú)H# and then puts a copy of it into a °dONLNd±vlÇ¥(lparameter of an Õ`°dONLNd¡v¥Ç
)HApple event by calling 8¿°dONLNdÿv
Ç
o)gAEPutParamDesc3Ä°dONLNdÊv
oÇ
†)T), it is still rU°dONLNdˆv
†Ç
‡)1esponsible for °dONLNd
Élè
(ål&disposing of the original descriptor rF`°dONLNd
+É
è
 )¢ecor∫¿°dONLNd
/É
 è
+)d. x °dONLNd
2É
+è
≤) After a client application has fi@°dONLNd
SÉ
≥è
 )ànisheî°dONLNd
XÉ
 è
Ì)d using °dONLNd
`êlúq(ôl
b†°dONLNd
aêrúì)oth the ‡°dONLNd
iêìúË)!Apple event specifiH¿°dONLNd
|êËú
)U
ed in the E@°dONLNd
Üê
ú
5))AESendC°dONLNd
åê
5ú
Ü)$ function and the r‡¿°dONLNd
üê
Üú
õ)Qeply E†°dONLNd
§ê
úú
fl)Apple event, it °dONLNd
¥ùl©
(¶l$should dispose of their descriptor rØÄ°dONLNd
ÿù
©
)õecor#‡°dONLNd
‹ù
©
 )
d?†°dONLNd
›ù
 ©
T)s by calling ù@°dONLNd
Íù
T©
Z)4
Aú‡°dONLNd
Îù
Z©
ú)EDisposeDesò¿°dONLNd
ˆù
ú©
¢)B
cò`°dONLNd
˜ù
¢©
§)
.`°dONLNd
¯ù
•©
’) The client °dONLNd™l∂
*(≥l+application should dispose of them even if «@°dONLNd/™
*∂
N)æAESend≈°dONLNd5™
N∂
T)$ r
°dONLNd7™
U∂
ô)eturns a nonzer≈°dONLNdF™
ô∂
§)Do rÄ°dONLNdI™
•∂
÷)esult code. °dONLNdVºl»(≈lThe ]`°dONLNdZº»
U)1Apple event that a server application’s handler r=@°dONLNdãº
U»
‡)÷"eceives is a copy of the original °dONLNd≠…l’è(“levent crÇÄ°dONLNdµ…è’
ø)#Feated by the client application. When a server application’s handler rh†°dONLNd˚…
ø’
Ë(“
ø
eturns to °dONLNd÷l‚fi(fllAEProcessAppleEventx‡°dONLNd÷fi‚Û)r, the w‡°dONLNd÷Û‚
∂)*Apple Event Manager disposes of the server„°dONLNdH÷
∑‚
–)ƒ’s copO °dONLNdN÷
—‚
˜)
y (in the °dONLNdX„lÔá(Ïlserverô °dONLNd^„àÔ·)’s application heap) ≈@°dONLNds„·Ô
)Yof both the ûÄ°dONLNd„
Ô
s)2Apple event and the r¯¿°dONLNdî„
sÔ
◊)`eply event. The server °dONLNd´l¸≠(˘lapplication is r!@°dONLNdªƸ
m)B,esponsible for disposing of any descriptor r”†°dONLNdÁ
m¸
)øecorH°dONLNdÎ
ĸ
ï)ds crV°dONLNd
ï¸
 )eated while °dONLNd¸˝l
    ∑(
lextracting data fr¿°dONLNd˝∏
    Ÿ)Lom the ‚@°dONLNd˝ÿ
    
)     Apple eve@°dONLNd˝

    
).
n͆°dONLNd˝

    
)
t-°dONLNd ˝

    
t) or adding data to the rÕ‡°dONLNd8˝
t
    
§)eeply event.°dONLNdD
l
…(
lIn general, outputs frfl °dONLNdZ
…
Ÿ)]om J@°dONLNd]
⁄

r) Apple Event Manager functions ar    `°dONLNd}

s

Õ)ôe your application’s °dONLNdí
l
(o(
%l
rE°dONLNdì
p
(®)esponsibility∞Ä°dONLNd†
ß
(≥)7. Oå`°dONLNd£
¥
(fl)    nce you fi∞ °dONLNd≠
fl
(
_)+nish using them, you should QÄ°dONLNd…

`
(
q)Åuse fl@°dONLNdÕ

q
(
ø)AEDisposeDesc⁄`°dONLNd⁄

ø
(
“)N to dÆ°dONLNdfl

”
(
Ò)ispose °dONLNdÊ
)l
5ä(
2lof any KÄ°dONLNdÌ
)ä
5‰)Apple event data strR`°dONLNd

)‰
5˚)Zucturÿ@°dONLNd
)˚
5
)es crî °dONLNd
)

5
9)
eated or r≤†°dONLNd
)
9
5
±)*eturned by these functions:°dONLNd»
ìl
ü
(
úl)If you attempt to dispose of descriptor rD‡°dONLNdÒ
ì

ü
.)∞ecorπ@°dONLNdı
ì
.
ü
>)ds rW°dONLNd˘
ì
?
ü
€)%eturned by successful calls to these °dONLNd
†l
¨ÿ(
©lfunctions without using Í`°dONLNd6
†ÿ
¨
&)lAEDisposeDescÂÄ°dONLNdC
†
&
¨
fi)N), your application may not be compatible °dONLNdl
≠l
πÄ(
∂lwith” °dONLNdp
≠Ä
πÇ)
 S °dONLNdq
≠É
πô)futurº†°dONLNdv
≠ô
π„)e versions of the ⁄`°dONLNdà
≠„
π
D)JApple Event ManagerÀ‡°dONLNdõ
≠
D
π
r)a    . HoweverXÄ°dONLNd§
≠
r
π
„)., if any of these functions °dONLNd¿
∫l
Δo(
√l
rE°dONLNd¡
∫p
ΔÇ)eturJ¿°dONLNd≈
∫Ç
Δè)n aú °dONLNd»
∫è
Δ∞) nonzer√°dONLNdœ
∫∞
Δª)!o r}Ä°dONLNd“
∫º
Δ˚)esult code, thefiÄ°dONLNd·
∫˚
Δ
)?y r≤†°dONLNd‰
∫

Δ
p)eturn a null descriptor r@°dONLNd˝
∫
q
Δ
É)jecor܆°dONLNd

∫
É
Δ
˜)d, which does not need to °dONLNd
«l
Ӡ(
–lbe disposed,`°dONLNd&
«°
”¨)5 ofu¿°dONLNd)
Ǭ
”±). °dONLNd,
Ÿl
Âö(
‚l
Outputs frΔ‡°dONLNd6
Ÿö
‘).om functions€†°dONLNdB
Ÿ‘
Â˚):
, such as û`°dONLNdL
Ÿ¸
Â
>)(AEGetKeyPtr‹‡°dONLNdW
Ÿ
=
Â
?)A
,\‡°dONLNdX
Ÿ
@
Â
~) that use a bufu¿°dONLNdg
Ÿ
~
Â
˜)>fer rather than a descriptor °dONLNdÑ
Êl
Úo(
Ôl
rE°dONLNdÖ
Êp
ÚÇ)ecorπ`°dONLNdâ
ÊÇ
Úô)d to rR°dONLNdè
Êö
Ú¬)    eturn dat@°dONLNdò
Ê√
Ú–))a d£°dONLNdõ
Ê–
ÚÏ)o not rf¿°dONLNd¢
ÊÌ
Ú
)equir~°dONLNdß
Ê

Ú
8)e the use of ¸ °dONLNd¥
Ê
8
Ú
Ü)4AEDisposeDesc˜@°dONLNd¡
Ê
Ü
Ú
Ø)N. It is ther_‡°dONLNdÕ
Ê
∞
Ú
¡)*efor∑‡°dONLNd—
Ê
¡
Ú
“)e pr»†°dONLNd’
Ê
“
Ú
˜)    eferable °dONLNdfi
Ûl
ˇ
T(
¸l7to use these functions for any data that is not identifi ‡°dONLNd
Û
T
ˇ
ô)Ëed by a handle. °dONLNd'l
å(l@Some of the functions described in the chapter “Resolving and CrC¿°dONLNdg
ç
Ê(
çeating Object Specifi@°dONLNd|
Á
Ú)Zer °dONLNdlÖ(lRecor¢`°dONLNdÑÖÈ)ds” in this book also cr?‡°dONLNdúÍ
1)eeate descriptor rÙ¿°dONLNd≠
1
C)Gecori °dONLNd±
D
è)ds. If you set the ¶`°dONLNdƒ
è
›)KdisposeInputs°Ä°dONLNd—
›
fl)N
 °dONLNd“l+ß((lparameter to »‡°dONLNdflß+≈);FALSE«°dONLNd‰≈+
◊)? for any of the following functions, you should dispose of any °dONLNd    #,l8á(5lApple˝Ä°dONLNd    (,á8â)
 }Ä°dONLNd    ),ä8Δ)event data str܇°dONLNd    7,Δ8›)<uctur¿°dONLNd    <,fi8
)es that they crã@°dONLNd    K,
8
?)=    eate or ré°dONLNd    T,
?8
Y)$eturn:°dONLNd    ¥flrr(ol
Y@Ä°dONLNd    µfrrŸ)our application is also r·°dONLNd    ŒfŸr
∏)g4esponsible for disposing of some of the tokens it crT`°dONLNd
f
πr
Ì)‡eates in the °dONLNd
slu(|lprG °dONLNd
svû)

ocess of r˛‡°dONLNd
sû
)(esolving an object specifi‚ °dONLNd
5s

)ner r„`°dONLNd
9s

-)ecorW¿°dONLNd
=s
.
Î)+d. For information about token disposal, se3Ä°dONLNd
hs
Ï
Û)æe °dONLNd
jÄlåÉ(âl“Defi†°dONLNd
oÄÑå†)ning T„†°dONLNd
uÄüåÂ)okens” on page ‚°dONLNd
ÑÄÊå¯)G6-395‡°dONLNd
àĢå˚)
.µ‡°dONLNd
âÄ˚å˝)
 °dONLNd0
;l
G¥(
DlAECoerceDesc°dONLNd=
;Ï
G
F)ÄAEDuplicateDesc°dONLNdN
Kl
WÆ(
TlAECoercePtr°dONLNdZ
KÏ
W
X)ÄAEGetAttributeDesc°dONLNdn
[l
gÿ(
dlAECreateAppleEvent°dONLNdÅ
[Ï
g
4)ÄAEGetKeyDesc°dONLNdè
kl
w¥(
tlAECreateDesc°dONLNdú
kÏ
w
4)ÄAEGetNthDesc°dONLNd™
{l
á¥(
ÑlAECreateList°dONLNd∑
{Ï
á
@)ÄAEGetParamDesc°dONLNd    Z>lJ‰(GlCreateCompDescriptor°dONLNd    o>

J
v)ûCreateObjSpecifier°dONLNd    ÉNlZˆ(WlCreateLogicalDescriptorˇ˙?°dONLNd    õN

Z
à)ûCreateRangeDescriptor ˇCT@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-41
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

kHr4lHr mäm

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\äkó(gä
WS°dONLNd
\ók
~)'riting and Installing Coercion Handlersˇˇˇˇˇˇ€r(g
4
°dONLNd*rä~
4({ä&When your application extracts data frØÄ°dONLNdPr
4~
y)™om a parameterÆ°dONLNd^r
y~
ú)E
, it can r˛°dONLNdhr
ú~
fl)#equest that the °dONLNdxr
‡~
˝)DApple °dONLNd~äã‘(àäEvent Manager rv`°dONLNdç‘ã
¶)J2eturn the data using a descriptor type that is difÛ`°dONLNdø
¶ã
≤)“fer’‡°dONLNd¬
≤ã
…)ent frL °dONLNd»
 ã)om the original °dONLNdÿåäò
u(ïä5descriptor type. For example, when extracting data frÜ@°dONLNd
å
uò
£)Î
om the dirv@°dONLNd
å
£ò
˝).ect parameter of the °dONLNd
,ôä•
 (¢äOpen Documents event, you can rÒ °dONLNd
Kô
 •
})ñequest that the alias r™@°dONLNd
bô
~•
ê)^ecor†°dONLNd
fô
ë•
Æ)ds be r熰dONLNd
mô
Æ•
Â)eturned as fi쇰dONLNd
zô
•)7
le system °dONLNd
Ѷä≤¶(ØäspecifiÓ °dONLNd
㶶≤«)cation r°dONLNd
춻≤⁄)"ecorâ`°dONLNd
ó¶⁄≤¸)ds. The øÄ°dONLNd
ü¶¸≤
√)"*Apple Event Manager can automatically coer2@°dONLNd
…¶
IJ
˜)»ce many difÀ°dONLNd
Ԧ
˜≤)3fer≠Ä°dONLNd
◊¶≤)ent °dONLNd
€≥äøÃ(ºätypes of data fr†°dONLNd
Î≥Õø
)Com one to another°dONLNd
¸≥
ø
")P. °dONLNd
˛≥
"ø
()
T;¿°dONLNd
ˇ≥
'ø
q)able 4-1 on page k°dONLNd≥
qø
y)J4-懰dONLNd≥
yø
É)43懰dONLNd≥
Éø)
  shows descriptor types and the °dONLNd4¿äÃ√(…äkinds of coer_`°dONLNdA¿√ø)9cion that the T°dONLNdO¿¸Ã
ñ)9Apple Event Manager can perform퇰dONLNdn¿
ñÃ
ò)ö
.°dONLNdp“äfiê(€ä
Y@Ä°dONLNdq“êfiÕ)ou can also pr‡¿°dONLNd“Õfi
)=ovide your own r´Ä°dONLNdè“
fi
C)M
outines, rÔ‡°dONLNdô“
Cfi
W))eferr醰dONLNdû“
Xfi
|)    ed to as 
ˇ°dONLNdß“
|fi
œ)$coercion handlers,5‡°dONLNdπ“
–fi
)T to coerb °dONLNd¡“
fi) ce data °dONLNd…fläÎ
(Ëä!into any other descriptor type. Tч°dONLNdÍfl
Î
})éo install your own coer‡°dONLNd
fl
~Î
‡)fcion handlers, use the ,
Courier°dONLNdÏä¯
(ıäAEInstallCoercionHandlerw°dONLNd0Ï
¯
F)ê function. ◊†°dONLNd;Ï
F¯
L),
Yò °dONLNd<Ï
L¯
˛))ou specify as parameters to this function,Zapf Dingbats°dONLNdf
ä
    è(
ä
n
°dONLNdhˇñ

0)$the descriptor type of the data coeré °dONLNdåˇ
0

Ç)öced by the handler°dONLNdü
ä
è(
ä
n
°dONLNd°
ñ

)the descriptor type of the r†°dONLNdΩ



E)vesulting data°dONLNdÀ
&ä
-è(
,ä
n
°dONLNdÕ
#ñ
/ª)the addrŸ‡°dONLNd’
#ª
/˘)%ess of the coer∏†°dONLNd‰
#˘
/
ò)>%cion handler for this descriptor type°dONLNd

8ä
?è(
>ä
n
°dONLNd
5ñ
A°)a r≈°dONLNd
5°
A±)eferq °dONLNd
5≤
AÌ)ence constant°dONLNd!
Jä
Qè(
Pä
n
°dONLNd#
Gñ
S
m)0a Boolean value that indicates whether your coerÎÄ°dONLNdS
G
m
S)◊$cion handler expects the data to be °dONLNdw
Sñ
_≤(
\ñspecifiÓ °dONLNd~
S≤
_
)ed as a descriptor rÔ¿°dONLNdí
S

_
)Tecord °dONLNdñ
S

_
Ø)$d or as a pointer to the actual data°dONLNdª
hä
oè(
nä
n
°dONLNdΩ
eñ
q
m)0a Boolean value that indicates whether your coerÎÄ°dONLNdÌ
e
m
q
˛)◊ cion handler should be added to °dONLNd
qñ
}˚(
zñyour application’s coer≠‡°dONLNd$
q˚
}
)ecion Õ`°dONLNd)
q

}
;)
dispatch tW°dONLNd3
q
<
}
°),able or the system coer3†°dONLNdJ
q
°
}
∂)ecion S °dONLNdO
q
∂
}
fi)    dispatch ö`°dONLNdX
q
fi
}
Û)(table°dONLNd^
Çä
éù(
ãäThe 
ª¿°dONLNdb
Çù
é
()system coercion dispatch table”‡°dONLNdÄ
Ç
(
é
ˆ)ã1 is a table in the system heap that contains coerM`°dONLNd±
Ç
˜
é)œcion °dONLNd∂
èä
õ
K(
òä-handlers available to all applications and pr
Ä°dONLNd„
è
L
õ
r)¬    ocesses rê °dONLNdÏ
è
r
õ
ˆ)&unning on the same computerÜ°dONLNd
è
ˆ
õ)Ñ. The °dONLNd
úä
®ú(
•äcoerÙ`°dONLNd
úú
®
J)(cion handlers in your application’s coerõ†°dONLNd9
ú
K
®
©)Øcion dispatch table ar√`°dONLNdO
ú
©
®)^e available only to your °dONLNdh
©ä
µ’(
≤äapplication. Whe—‡°dONLNdx
©’
µ‚)Kn a#@°dONLNd{
©„
µ
/)ttempting to coerˇ@°dONLNdå
©
.
µ
M)Kce data@°dONLNdì
©
N
µ
c) , the @°dONLNdô
©
c
µ
 )Apple Event Manager fiÄ°dONLNdÆ
©
 
µ)girst looks for a °dONLNdø
∂ä
¬ú(
øäcoerÙ`°dONLNd√
∂ú
¬
F)'cion handler in your application’s coer^†°dONLNdÍ
∂
G
¬
◊)´#cion dispatch table. If it cannot fiv °dONLNd
∂
◊
¬)ênd a handler °dONLNd
Ê
œ
d(
Ãä4for the descriptor type, it looks in the system coerè¿°dONLNdO
√
d
œ
Ú)⁄!cion dispatch table for a handlerT@°dONLNdp
√
Ú
œ)é. If it °dONLNdx
–ä
‹≤(
Ÿä    doesn’t fi†°dONLNdÇ
–≥
‹ˇ))nd a handler therÚ@°dONLNdì
–ˇ
‹
ú)L&e, it attempts to use the default coer°dONLNdπ
–
ù
‹    )ûcion handling described °dONLNd—
݊
Èó(
Êäby ¿°dONLNd‘
›ò
Èû)
TLÄ°dONLNd’
›ù
ÈÁ)able 4-1 on page {¿°dONLNdÊ
›Á
ÈÔ)J4-œ†°dONLNdË
›Ô
È˘)43œ†°dONLNdÍ
›˘
È
-)
. If it can’t fiÑ¿°dONLNd˙
›
.
È
^)5
nd an apprÄ°dONLNd
›
_
È
µ)1opriate default coerJ†°dONLNd
›
µ
È
Ï)Vcion handler‡°dONLNd$
›
Ï
È
˘)7, it °dONLNd)
Íä
ˆç(
Ûä
rE°dONLNd*
Íé
ˆº)eturns the 6Ä°dONLNd5
ÍΩ
ˆ
)/errAECoercionFai0Ä°dONLNdE
Í

ˆ
#)`
l0 °dONLNdF
Í
#
ˆ
)) ru °dONLNdH
Í
)
ˆ
Z)esult code. °dONLNdU
¸ä•(äAny h˘ °dONLNdZ
¸•ƒ)andler 
‡°dONLNda
¸≈
) that you add $@°dONLNdn
¸

O);to the system coeró°dONLNdÄ
¸
O
ù)Ocion dispatch tabl∞ °dONLNdí
¸
ù
®)Ne s6¿°dONLNdï
¸
©
…)hould rÕ‡°dONLNdú
¸
…
˝) eside in the °dONLNd©    ä·(äsystem heap. If ther[°dONLNdΩ    ·
)W    e was alrf°dONLNdΔ    

ñ)' eady an entry in the system coerˇ†°dONLNdÊ    
ñ
˙)écion dispatch table for °dONLNd˛ä"ó(äthe]`°dONLNd    
ò"ö)
 ›`°dONLNd    ö"
)same descriptor type, it is rц°dONLNd    
"
M)xeplaced. Ther °dONLNd    ,
N"
_)<eforg °dONLNd    0
_"
É)
e, if therè`°dONLNd    :
É"
¯)$e is an entry in the system °dONLNd    V#ä/ú(,äcoerÙ`°dONLNd    Z#ú/
Ì)Ncion dispatch table for the same descriptor type, you should chain it to your °dONLNd    ®0ä<®(9äsystemi °dONLNd    Æ0©<´)
 È °dONLNd    Ø0´<Ω)coer]Ä°dONLNd    ≥0æ<
4)cion handler as explained i
`°dONLNd    Œ0
5<
=)wn R¿°dONLNd    –0
=<
M)“Cr.¿°dONLNd    ”0
M<
”)eating and Managing the CoerᇰdONLNd    Ô0
”<)Ücion Handler °dONLNd    ¸=äI∫(Fä
Dispatch TûÄ°dONLNd
=πI÷)/ables,”ï °dONLNd
=◊I
$) which begins on Ä°dONLNd
=
%I
<)Npage ‡`°dONLNd
#=
<I
N)4-964@°dONLNd
'=
OI
Q)
.

WHe4XHe°dONLNd
)Wva~(_v
s
°dONLNd
*Xä`ì(^ä
Wú°dONLNd
+Xì`æ)    ARNING

ˇ·ˇ‚7^
°dONLNd
2cäo°(läBeforÛ¿°dONLNd
7c°o
;)$e an application calls a system coer! °dONLNd
[c
<o
s)õcion handlerÊ`°dONLNd
gc
ro
π)6, system softwar¥@°dONLNd
wc
∫o
¡)He °dONLNd
yoä{…(xähas set up the _†°dONLNd
ào…{‹)?A5 rk‡°dONLNd
åo‹{
w)&egister for the calling application. FQ‡°dONLNd
≤o
x{
ö)ú    or this r∏ °dONLNd
ªo
ö{
¡)"
eason, if °dONLNd
≈{äáß(Ñäyou pr“‡°dONLNd
À{ßá˝)ovide a system coerô‡°dONLNd
fi{˛á
5)Wcion handler_ °dONLNd
Í{
5á
ê)7, it should never use ≈‡°dONLNd{
êá
Ω)[
A5 global °dONLNd
áäì
ø(êäGvariables or anything that depends on a particular context; otherwise, °dONLNdQìäü
<**the application that calls the system coer#@°dONLNd{ì
=ü
§)≥cion handler may crashz@°dONLNdëì
§ü
¶)g
.˙@°dONLNdìñ
´û
≤)
sˇ!@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-42    )B    Handling ê)&Apple Events4^*¿
¯
°dONLNd\lhr(el
Y@Ä°dONLNd
\rhõ)    ou can pr≈‡°dONLNd
\õh–))ovide a coer#¿°dONLNd\—h
Q)6cion handler that expects to r'°dONLNd4\
Qh
€)Ä!eceive the data in a descriptor rW@°dONLNdU\
€h
Ì)äecorÀ†°dONLNdY\
Ìh
ı)d °dONLNd[ilué(rlor a bufù °dONLNdciéu†)"fer rÚ@°dONLNdhi†u¥)eferrë°dONLNdmiµu
)ed to by a pointer∑†°dONLNdi
u
)M. When you install your coer¨`°dONLNdõi
u
∂)}cion handlerq†°dONLNdßi
∂u
)7, you specify °dONLNdµvlÇÓ(lhow your handler wishes to r–†°dONLNd—vÓÇ
/)Çeceive the datag‡°dONLNd‡v
0Ç
D)B. Wh9@°dONLNd‰v
EÇ
Ù)'enever possible, you should write your °dONLNd
Élè~(ålcoerÙ`°dONLNd
É~è
j)8cion handler so that it can accept a pointer to the data˛°dONLNd
GÉ
jè
∂)Ï, because it’s mor
¿°dONLNd
YÉ
∑è
Δ)Me efD@°dONLNd
]É
Δè
Ã)
fiQ°dONLNd
_É
Ãè
Ú)
cient for °dONLNd
iêlú|(ôlthe °dONLNd
mê|úı)Apple Event Manager to pr¨‡°dONLNd
Üêıú
:)yovide your coer     °dONLNd
ïê
;ú
Á)F(cion handler with a pointer to the data.°dONLNd
æ¢lÆs(´l
A∫†°dONLNd
ø¢sÆà) coerØ°dONLNd
ƒ¢àÆ
Ï)Rcion handler that accepts a pointer to data must be a function with the following °dONLNdØlªã(∏lsyntax:,
Courier°dONLNdΔl“
º*8FUNCTION MyCoercePtr (typeCode: DescType; dataPtr: Ptr; °dONLNd^‘͇+~
 †°dONLNd_‘‡
º)"dataSize: Size; toType: DescType; °dONLNdâ‚ÍÓ(ÎÍ
 †°dONLNdä‚Ó
z)handlerRefcon: LongInt;°dONLNd©͸(˘Í
 †°dONLNd™¸
ò)VAR result: AEDesc): OSErr; °dONLNd«
l
(
lThe ª¿°dONLNdÀ

Ø)typeCode∏¿°dONLNd”
Ø

≠)0< parameter is the descriptor type of the original data. The F`°dONLNd

Æ

ÿ)ˇdataPtrC¿°dONLNd

ÿ

⁄)*
 °dONLNd
l
!
(
l*parameter is a pointer to the data to coerÜ°dONLNdA


!
=)≥ce; the @°dONLNdI

>
!
n)dataSize@°dONLNdQ

n
!
Ê)0 parameter is the length, in °dONLNdn
"l
.œ(
+lbytes, of the data. The  `°dONLNdÜ
"–
.Ù)dtoType °dONLNdå
"Ù
.
V)$ parameter is the desirņ°dONLNd£
"
V
.
»)bed descriptor type of the r
@°dONLNdæ
"
…
.
Ô)s    esulting °dONLNd«
/l
;ó(
8l
data. The ‡°dONLNd—
/ò
;Ê),handlerRefcon°dONLNdfi
/Ê
;
-)N parameter is a rê`°dONLNdÔ
/
-
;
=)Gefer<Ä°dONLNdÛ
/
>
;
v)ence constanô@°dONLNdˇ
/
v
;
)8t sò†°dONLNd
/
Ä
;
å)
torÄ°dONLNd
/
ç
;
»)ed in the coerÜ`°dONLNd
/
»
;
ı);cion table °dONLNd
<l
H
](
El7entry for the handler and passed to the handler by the 8`°dONLNdU
<
]
H
Ô)ÒApple Event Manager whenever °dONLNdr
Il
U›(
Rlthe handler is called. The »°dONLNdç
I›
U

)qresult≈¿°dONLNdì
I


U
F)$ parameter is th‡°dONLNd£
I
G
U
T)Fe du@°dONLNd¶
I
T
U
Å)escriptor r∏¿°dONLNd±
I
Å
U
ì)-ecor- °dONLNdµ
I
î
U
†)d r燰dONLNd∏
I
†
U
Í)eturned by your °dONLNd»
Vl
b~(
_lcoerÙ`°dONLNdÃ
V~
bµ)cion handlerπ†°dONLNdÿ
Vµ
b∑)7
.°dONLNd⁄
hl
tr(
ql
Y@Ä°dONLNd€
hr
tñ)our coer§ °dONLNd„
hñ
t
)$cion handler should coer*@°dONLNd˚
h

t
g)nce the data to the desirц°dONLNd
h
g
t
—)ced descriptor type and r”†°dONLNd+
h
—
t
Î)jeturn °dONLNd1
ul
Åu(
~lthì¿°dONLNd3
uu
ÅÇ)    e d˘ °dONLNd6
uÇ
Ň)ata in the descriptor r±‡°dONLNdM
u·
ÅÛ)_ecor&@°dONLNdQ
uÙ
Å
)d specifi0 °dONLNdZ
u

Å
D)%
ed by the ↰dONLNdd
u
D
Å
h)+resultá`°dONLNdj
u
h
Å
ò)$
 parameter€°dONLNdt
u
ó
Å
·)/. If your handler °dONLNdÜ
Çl
éÒ(
ãlsuccessfully performs the coer@°dONLNd§
ÇÚ
é
)Ü
cion, it sáÄ°dONLNdÆ
Ç

é
6)$hould r†°dONLNdµ
Ç
7
é
a)!
eturn the ” °dONLNdø
Ç
a
é
)*noErr—@°dONLNdƒ
Ç

é
Ö) r@°dONLNdΔ
Ç
Ü
é
≠)    esult cod–@°dONLNdœ
Ç
≠
é
Á)'e; otherwise, °dONLNd›
èl
õt(
òlit *¿°dONLNd‡
èu
õö)    should r˛‡°dONLNdË
èô
õ∏)$eturn aV°dONLNdÔ
èπ
õ⁄)  nonzer|‡°dONLNdˆ
è⁄
õÂ)!o r7`°dONLNd˘
èÊ
õ
)    esult codÒ`°dONLNd
è

õ
)'e.°dONLNd
°l
≠s(
™l
A∫†°dONLNd
°s
≠à) coerØ°dONLNd
°à
≠
3)(cion handler that accepts a descriptor r†°dONLNd3
°
4
≠
F)¨ecorá°dONLNd7
°
F
≠
 )d must be a function with the °dONLNdU
Æl
∫∏(
∑lfollowing syntax:°dONLNdg
≈l
—
Œ*;FUNCTION MyCoerceDesc (theAEDesc: AEDesc; toType: DescType;°dONLNd™
”Í
fl+~
 †°dONLNd´
”
flˆ)
 @°dONLNd¨
”ˆ
fl
Ä)handlerRefcon: LongInt;°dONLNdÀ
·Í
Ì(
ÍÍ
 †°dONLNdÃ
·
̈)
 @°dONLNdÕ
·ˆ
Ì
ò)VAR result: AEDesc): OSErr;°dONLNdÈ
˘lØ(lThe parameter ÿ°dONLNd˜
˘ØÂ)C    theAEDesc…`°dONLNd
˘Â
5)6 is the descriptor r´`°dONLNd
˘
5
G)Pecor¿°dONLNd
˘
H
‹)#d that contains the data to be coer∫‡°dONLNd;
˘
‹
)îced. °dONLNd@l(lThe ª¿°dONLNdD£)toTypeπÄ°dONLNdJ£
T)$* parameter is the descriptor type of the rpÄ°dONLNdt
U
¶)≤esulting data. The ¿°dONLNdá
ß
ı)RhandlerRefcon‡°dONLNdî
ı
˜)N
 °dONLNdïl±(lparameter is a r{`°dONLNd•±¡)Eefer'Ä°dONLNd©¬˙)ence constanÑ@°dONLNdµ˙
)8t sɆ°dONLNd∏

)
torÄ°dONLNdª

L)ed in the coerq`°dONLNd…
L
Í);%cion table entry for the handler and °dONLNdÓ l,Î()lpassed to the handler by the o†°dONLNd Î,
Ó)8Apple Event Manager whenever the handler is called. The °dONLNdC-l9ê(6lresult}¿°dONLNdI-ê9‡)$ parameter is the r÷Ä°dONLNd\-‡9
9)Pesulting descriptor r7 °dONLNdq-
:9
L)Zecor´Ä°dONLNdu-
L9
T)d.°dONLNdx?lKr(Hl
Y@Ä°dONLNdy?rKñ)our coer§ °dONLNdÅ?ñK
)$cion handler should coer*@°dONLNdô?
K
Ö)nce the data in the descriptor r°dONLNd∏?
ÖK
ó)Åecorä`°dONLNdº?
óK
—)d to the desirã °dONLNd ?
—K
fi):ed °dONLNdÕLlX…(Uldescriptor type and ri†°dONLNd‚L…XÏ)]eturn th‘Ä°dONLNdÍLÏX˘)#e d9‡°dONLNdÌL˙X
X)ata in the descriptor rÚ†°dONLNd    L
XX
j)^ecorg°dONLNd    L
kX
ê)d specifip‡°dONLNd    L
êX
ª)%
ed by the  `°dONLNd    L
ªX
fl)+result» °dONLNd    !L
flX
·)$
 °dONLNd    "Yleô(bl    parameterS†°dONLNd    +Yôeû)-. &°dONLNd    -Yûe§)
YÊÄ°dONLNd    .Y£e˛)our handler should rç°dONLNd    BYˇe
;)\eturn an appr˛¿°dONLNd    OY
;e
`)<    opriate r¢`°dONLNd    XY
ae
ê)&esult code.

s*Å
¯4t*Å
¯
    °dONLNd    drl}(zlNote

ˇ·ˇ‚7^
°dONLNd    ilãr*
Tµ¿°dONLNd    jqãë)o ensurO`°dONLNd    qíãÕ)!e that no coer™`°dONLNd    Õã
¶);2cion is performed and that the descriptor type of °dONLNd    ±ãlóÄ(îlthe r¢`°dONLNd    ∂ãÄó
Å)>esult is of the same descriptor type as the original, specify °dONLNd    Ùól£¥(†ltypeWildCard{Ä°dONLNd
ó¥£Ï)H for the desird†°dONLNd
óÏ£
)8ed type.,Zapf DingbatsÁ@°dONLNd
ö
¢
)(
uˇ0|@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡ä    Handling ê)&Apple Events

, (‡4-43
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähê(eä
Tµ¿°dONLNd
\èh±)able 4-1√@°dONLNd    \±h
_)"* lists the descriptor types for which the ؆°dONLNd3\
_h
Õ)ÆApple Event Manager pr•†°dONLNdI\
Õh
Ï)novides °dONLNdPiäuú(räcoerÙ`°dONLNdTiúuÆ)cion쇰dONLNdXiØu¥). 

òH†4ôH† úäú

ˇ·ˇ‚7^
    °dONLNd[éäô±(ñä    Table 4-1°dONLNdeé»ô
S)>"Coercion handling provided by the 
¿°dONLNdáé
Sô
©)ãApple Event Managerëp°dONLNdˇˇ)V
 
°dONLNd¶¶ä±‹(ÆäOriginal descriptor °dONLNd∫∞äªú*
typeÌ0°dONLNdæ∞úª÷) of data to be °dONLNdÕ∫ä≈¨(¬äcoerced°dONLNd’∫˛≈
b)tDesired descriptor type°dONLNdÌ∫
x≈
©)zDescription,
Courier
°dONLNd˙»ä‘∫(—ätypeChar°dONLNd
»˛‘
@)ttypeInteger°dONLNd
”˛fl
X*typeLongInteger°dONLNd
fi˛Í
4*    typeSMInt°dONLNd
&È˛ı
@*typeSMFloat°dONLNd
1Ù˛

^*typeShortInteger°dONLNd
Aˇ˛

4*    typeFloat°dONLNd
J

˛

L*typeLongFloat°dONLNd
W
˛
!
R*typeShortFloat°dONLNd
e
 ˛
,
F*typeExtended°dONLNd
q
+˛
7
.*typeComp°dONLNd
y
6˛
B
L*typeMagnitude°dONLNd
á»
x‘
Á(—
xAny string that is a valid °dONLNd
¢”
xfl
{*
rE°dONLNd
£”
|fl
ä)epr’¿°dONLNd
¶”
äfl)esentation of a number can be °dONLNd
ƒfi
xÍ
ä(Á
xcoerÙ`°dONLNd
»fi
äÍ
Ó)ced into an equivalent °dONLNd
flÈ
xı
∫(Ú
xnumeric value.°dONLNd
Hä
TÃ(
QätypeInteger°dONLNd
Sä
_Í*typeLongInteger °dONLNd"
^ä
j¿*    typeSMInt°dONLNd+
iä
uÃ*typeSMFloat°dONLNd6
tä
ÄÍ*typeShortInteger°dONLNdF
ä
ã¿*    typeFloat°dONLNdO
ää
ñê*
t†°dONLNdP
äê
ñÿ)ypeLongFloat°dONLNd\
ïä
°fi(
ûätypeShortFloat°dONLNdj
†ä
¨“*typeExtended°dONLNdv
´ä
∑∫*typeComp°dONLNd~
∂ä
¬ÿ*typeMagnitude°dONLNdå
H˛
T
.(
Q˛typeChar°dONLNdï
H
x
T)z Any numeric descriptor type can °dONLNdµ
S
x
_
ó*be coer≈†°dONLNdº
S
ó
_)ced into the equivalent text °dONLNdŸ
^
x
j
î(
g
xstring.°dONLNd˙
Ȋ
‘Ã(
—ätypeInteger°dONLNd
ӊ
flÍ*typeLongInteger °dONLNd
fiä
Í¿*    typeSMInt°dONLNd
Èä
ıÃ*typeSMFloatˇ˙_°dONLNd)
ÙäÍ*typeShortInteger °dONLNd:
ˇä¿*    typeFloat°dONLNdC
äÿ*typeLongFloat°dONLNdPä!fi*typeShortFloat°dONLNd^ ä,“*typeExtended°dONLNdj+ä7∫*typeComp°dONLNdr6äBÿ*typeMagnitude°dONLNdÄ
»˛
‘
@(
—˛typeInteger°dONLNdã
”˛
fl
X*typeLongInteger°dONLNdö
fi˛
Í
4*    typeSMInt°dONLNd£
È˛
ı
@*typeSMFloat°dONLNdÆ
Ù˛
^*typeShortInteger°dONLNdæ
ˇ˛
4*    typeFloat°dONLNd«
˛
L*typeLongFloat°dONLNd‘˛!
R*typeShortFloat°dONLNd‚ ˛,
F*typeExtended°dONLNdÓ+˛7
.*typeComp°dONLNdˆ6˛B
L*typeMagnitude°dONLNd
»
x
‘(
—
x Any numeric descriptor type can °dONLNd$
”
x
fl
ó*be coer≈†°dONLNd+
”
ó
fl)ced into any other numeric °dONLNdF
fi
x
Í
Ω(
Á
xdescriptor type.°dONLNdpHäT∫(QätypeChar°dONLNdyH˛T
.)ttypeType°dONLNdÅS˛_
R*typeEnumerated°dONLNdè^˛j
@*typeKeyword°dONLNdõi˛u
F*typeProperty°dONLNd®H
xT
†(Q
xAny fourΩ@°dONLNd∞H
†T    )(-character string can be °dONLNd…S
x_
ä(\
xcoerÙ`°dONLNdÕS
ä_)ced to one of these descriptor °dONLNdÏ^
xj
í(g
xtypes.°dONLNd{äáfi(ÑätypeEnumerated°dONLNdÜäíÃ*typeKeyword°dONLNdëäù“*typeProperty°dONLNd%úä®∫*typeType°dONLNd.{˛á
.(Ñ˛typeChar°dONLNd7{
xá)z"Any of these descriptor types can °dONLNdYÜ
xí
ó*be coer≈†°dONLNd`Ü
óí)ced to the equivalent text °dONLNd{ë
xù
î(ö
xstring.á∞°dONLNdá∞
ıπ+}    continuedˇû@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-44    )B    Handling ê)&Apple Events4^*¿
¯°dONLNd›jlr(plNOTE\0°dONLNd‚iár
5)Some of the descriptor types listed in this table aró=°dONLNdi
5r
¡)Æ'e synonyms; for example, the constants ,
Courier°dONLNd=sl{ó(yl    typeSMIntΔ°dONLNdFró{®)+ and O}°dONLNdKs©{ı)typeShortInteger=›°dONLNd[rˆ{
;)M have the same fourxÉ°dONLNdnr
;{
t)E-character code, Cd°dONLNds
u{
y):
'J°dONLNdÄs
z{
ç)shorM‚°dONLNdÑs
ç{
ë)
'»°dONLNdÖr
í{
î)
.
°dONLNdñl¢¥(ültypeIntlText°dONLNdñ‡¢
)ttypeChar°dONLNdñ
Z¢
q)zThe rÄ¿°dONLNdñ
q¢
÷)esult contains text onlyC °dONLNd3ñ
÷¢
€)e, °dONLNd5°
Z≠
Œ(™
Zwithout the script code or °dONLNdP¨
Z∏
£*language code fr¿°dONLNd`¨
§∏
Í)Jom the original °dONLNdp∑
Z√
ç(¿
Zdescriptor rfl@°dONLNd|∑
ç√
ü)3ecorS†°dONLNdÄ∑
†√
®)d.°dONLNdÑ…l’ú(“ltypeTrue°dONLNdç…‡’
")ttypeBoolean°dONLNdô…
Z’
q)zThe rÄ¿°dONLNdû…
q’
„)esult is the Boolean value °dONLNdπ‘
Z‡
r(›
ZTRUE~Ä°dONLNdΩ‘
r‡
t)
.°dONLNd¿ÊlÚ¢(Ôl    typeFalse°dONLNd ʇÚ
")ttypeBoolean°dONLNd÷Ê
ZÚ
q)zThe rÄ¿°dONLNd€Ê
qÚ
„)esult is the Boolean value °dONLNdˆÒ
Z˝
x(˙
ZFALSE~ °dONLNd˚Ò
x˝
z)
.°dONLNd˛
l
¿(
ltypeEnumerated°dONLNd

‡

")ttypeBoolean°dONLNd


Z

ø)zThe enumerated value u@°dONLNd
.

¿

‰)f'true's°dONLNd
4

‰

Ê)$
 °dONLNd
5

Z

”(

Zbecomes the Boolean value XÄ°dONLNd
O

‘

Ï)zTRUEW°dONLNd
S

Ï

Ò). °dONLNd
U

Z
%
ø(
"
ZThe enumerated value u@°dONLNd
j

¿
%
‰)f'fals's°dONLNd
p

‰
%
Ê)$
 °dONLNd
q
$
Z
0
”(
-
Zbecomes the Boolean value XÄ°dONLNd
ã
$
‘
0
Ú)zFALSEV†°dONLNd
ê
$
Ú
0
Ù)
.°dONLNd
ì
6l
BÆ(
?ltypeBoolean°dONLNd
ü
6‡
B
4)ttypeEnumerated°dONLNd
Æ
6
Z
B
Æ)zThe Boolean value •@°dONLNd
¿
6
Æ
B
Ã)TFALSE£`°dONLNd
≈
6
Ã
B
Œ)
 °dONLNd
Δ
A
Z
M
Â(
J
Zbecomes the enumerated value °dONLNd
„
L
Z
X
~*'fals'}¿°dONLNd
È
L
~
X
◊)$. The Boolean value £°dONLNd
˝
L
◊
X
Ô)YTRUE°Ä°dONLNd

L
Ô
X
Ò)
 °dONLNd
W
Z
c
Â(
`
Zbecomes the enumerated value °dONLNd
b
Z
n
~*'true'}¿°dONLNd%
b
~
n
Ä)$
.°dONLNd(
tl
ÄÃ(
}ltypeShortInteger°dONLNd9
l
ã¢*    typeSMInt°dONLNdC
t‡
Ä
"(
}‡typeBoolean°dONLNdO
t
Z
Ä
a)z
A∫†°dONLNdP
t
a
Ä
)  value of 1 becomes the Boolean °dONLNdp

Z
ã
t(
à
Zvalue _`°dONLNdv

u
ã
ç)TRUE]‡°dONLNdz

ç
ã
í). ˇÄ°dONLNd|

ë
ã
ò)
A: °dONLNd}

ô
ã
Ò) value of 0 becomes °dONLNdë
ä
Z
ñ
´(
ì
Zthe Boolean value Δ‡°dONLNd£
ä
´
ñ
…)QFALSE≈°dONLNd®
ä
…
ñ
À)
.°dONLNd´
úl
®Æ(
•ltypeBoolean°dONLNd∑
ú‡
®
@)ttypeShortIntegerz°dONLNd«
ú
@
®
F)`
 °dONLNd»
߇
≥
(
∞‡    typeSMInt°dONLNd“
ú
Z
®
a(
•
Z
A∫†°dONLNd”
ú
a
®
â)
 value of c`°dONLNd›
ú
ä
®
®))FALSEaÄ°dONLNd‚
ú
®
®
›) becomes 0. ¿°dONLNdÓ
ú
›
®
‰)5
AO`°dONLNdÔ
ú
‰
®
Ê)
 °dONLNd
ß
Z
≥
Ä(
∞
Z    value of ®¿°dONLNd˘
ß
Ä
≥
ò)&TRUEß@°dONLNd˝
ß
ò
≥
 ) becomes 1.°dONLNd

πl
Ţ(
¬l    typeAlias°dONLNd
π‡
≈

)ttypeFSS°dONLNd
π
Z
≈
Ñ)z
An alias rÎ`°dONLNd&
π
Ñ
≈
ñ)*ecor_¿°dONLNd*
π
ó
≈
ª)    d is coer@°dONLNd3
π
º
≈
È)%ced into a °dONLNd>
ƒ
Z
–
`(
Õ
Z
fiå¿°dONLNd@
ƒ
`
–
®)le system specifiñ°dONLNdQ
ƒ
®
–
…)Hcation rº‡°dONLNdY
ƒ
…
–
€)!ecor1@°dONLNd]
ƒ
‹
–
‰)d.°dONLNda
÷l
‚¿(
flltypeAppleEvent°dONLNdp
÷‡
‚
F)ttypeAppParameters°dONLNdÇ
÷
Z
‚
j)zAn :@°dONLNdÖ
÷
j
‚
ø)Apple event is coer¿°dONLNdò
÷
ø
‚
Ï)Uced into a °dONLNd£
·
Z
Ì
Ï(
Í
Z#list of application parameters for °dONLNdΔ
Ï
Z
¯
j*the ›`°dONLNd 
Ï
j
¯
‹)LaunchParamBlockRec÷@°dONLNd›
Ï
‹
¯
fi)r
 °dONLNdfi
˜
Z
§(
Zparameter block.°dONLNd    lπ(lany descriptor type°dONLNd    ‡
)t
typeAEList°dONLNd    
Z
a)z
A∫†°dONLNd    
a
ó) descriptor rô‡°dONLNd    
ó
©)6ecor@°dONLNd!    
™
Œ)    d is coer√¿°dONLNd*    
Œ
Û)$    ced into °dONLNd3
Z 
ˆ(
Z&a descriptor list containing a single °dONLNdY
Z+
p*item.°dONLNd`1l=®(:l
typeAEList°dONLNdk1‡=
)ttype of list item°dONLNd}1
Z=
a)z
A∫†°dONLNd~1
a=
€) descriptor list containing a °dONLNdú<
ZH
™(E
Zsingle descriptor ró °dONLNdØ<
™H
º)PecorÄ°dONLNd≥<
ΩH
·)    d is coer¡°dONLNdº<
·H
Ú)$ced °dONLNd¿G
ZS
®(P
Zinto a descriptor rP‡°dONLNd”G
©S
ª)Oecor≈@°dONLNd◊G
ªS
√)d.a°dONLNdŸG
ƒS
Δ)    
 

g*n
¯4g*n
¯ jlj
¯

ˇ·ˇ‚7^
    °dONLNdˇˇ(dl    Table 4-1°dONLNdˇˇ)>"Coercion handling provided by the 
¿°dONLNdˇˇ)ãApple Event Managerëp°dONLNdˇˇ)V (continued)
°dONLNdˇˇ(|lOriginal descriptor °dONLNdˇˇ*
typeÌ0°dONLNdˇˇ) of data to be °dONLNdˇˇ(êlcoerced°dONLNdˇˇ)tDesired descriptor type°dONLNdˇˇ)zDescriptionˇ=»@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡äInteracting WÅ0)5ith the User

, (‡4-45
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

^Hx4^Hx

àHê4âHê äHä

ˇ·ˇ‚7^ˇˇ©ˇÆ°dONLNduHà™(ÉHInteracting WS-°dONLNdu™à˝)bith the UserˇˇˇˇˇˇU˛(É
4
°dONLNdô䕈(¢äWhen your application rʆ°dONLNd2ôˆ•
%)leceives an Ú`°dONLNd=ô
%•)/2Apple event, it may need to interact with the usera¿°dONLNdoô•)€. °dONLNdq¶ä≤
É(Øä8For example, it may need to display a dialog box asking û`°dONLNd©¶
É≤
®)˘    the user | °dONLNd≤¶
©≤
Ë)&for additional °dONLNd¡≥äø‚(ºäinformation or config`°dONLNd’≥„ø
)YrmatioŒ@°dONLNd€≥
ø
)n.†°dONLNd›≥
    ø
)    
 r°dONLNdfi≥
ø
)
Y2Ä°dONLNdfl≥
ø
Y)ou must use the ,
CourierÙ¿°dONLNdÔ≥
Yø
≈)HAEInteractWithUserÓ°dONLNd

≥
≈ø)l function to make °dONLNd
¿äÃò(…äsurâ °dONLNd
¿òÃ
) e your application is in the forR‡°dONLNd
6¿
Ã
+)Öegrp†°dONLNd
9¿
+Ã
[)
ound befor:°dONLNd
C¿
\Ã
Û)1%e it actually interacts with the usercÄ°dONLNd
h¿
ÛÃ
¯)ó. °dONLNd
k“äfi
π(€äGBoth the client application and the server application specify their prx†°dONLNd
≤“
πfi
…(€
πefer$¿°dONLNd
∂“
 fi    )ences for user °dONLNd
≈fläκ(Ëäinteraction.ö@°dONLNd
—flºÎ—)2 The V°dONLNd
÷fl“Î
>)AEInteractWithUserO@°dONLNd
Ëfl
>Î
È)l( function checks the user interaction pr‰@°dONLNdfl
ÈÎ
˘)´eferê`°dONLNdfl
˙Î)ences °dONLNdÏä¯
Â(ıäSset by each application. If both the client and the server allow user interaction, °dONLNdm˘ä
ˆ*AEInteractWithUsery@°dONLNd˘ˆ

Q)l usually posts a notifÓ`°dONLNdï˘
Q

u)[    ication r˝†°dONLNdû˘
u

—)$equest, and the NotiféÄ°dONLNd≥˘
“

Ú)]ication °dONLNdª
ä

)(
ä$Manager brings the server to the forn‡°dONLNdfl

)

7)üegr冰dONLNd‚

7

ë)ound after the user rΆ°dONLNd˜

ë

Î)Zesponds to the notifi'†°dONLNd

Ï
    )[cation °dONLNd
ä
ç(
ä
rE°dONLNd
é
Ø)equest. °dONLNd
%ä
1ù(
.äThe ª¿°dONLNd!
%ù
1
    )AEInteractWithUserµ°dONLNd3
%
    
1
‚)l3 function can also bring the server application dir°dONLNdf
%
„
1)⁄ectly to the °dONLNds
2ä
>ñ(
;äfor`°dONLNdv
2ó
>•)egr, °dONLNdy
2•
>
Î)Mound, but only if the client application is the active application on the sam°dONLNdΔ
2
Ï
>
Û(
;
Ïe °dONLNd»
?ä
Kº(
Hä
computer a¡†°dONLNd“
?º
K
)2nd has set two fl!¿°dONLNd„
?

K
1)Iags in the °dONLNdÓ
?
2
K
b)-sendMode°dONLNdˆ
?
b
K
∞)0 parameter of the 9¿°dONLNd
?
∞
K
‘)NAESend7Ä°dONLNd
?
‘
K)$ function: °dONLNd
Lä
Xó(
Uäthe]`°dONLNd
Lò
Xö)
 ›`°dONLNd
Lö
X‚)kAEWaitReplyÿ‡°dONLNd)
L‚
XÍ)H fle†°dONLNd,
LÎ
X
ß)    .ag, which indicates that it is waiting for a r∞ °dONLNdZ
L
ß
X
∫)ºeply◊†°dONLNd^
L
π
X
·)
, and the °dONLNdh
Yä
e(
bäkAECanSwitchLayery†°dONLNdy
Y
eı)f f°dONLNd{
Yˆ
e
˜)=lag, which indicates that it wants the server application to °dONLNd∏
fä
r°(
oäcome`°dONLNdº
f¢
r§)
 É`°dONLNdΩ
f§
r∞)dirLÄ°dONLNd¿
f±
r)ectly to the for„‡°dONLNd–
f
r˛)?egr
†°dONLNd”
fˇ
r
è) ound rather than posting a notifiQ`°dONLNdÙ
f
è
r
∞)êcation rx@°dONLNd¸
f
∞
r
œ)!equest.°dONLNd
xä
Ñê(
Åä
Tµ¿°dONLNd
xè
Ѫ)o specify iX°dONLNd
xº
ќ)-ts prİdONLNd
x–
ч)efer †°dONLNd
x‡
Ñ
)Bences for how the server application should interact with the userî°dONLNd[
x

Ñ(
Å

,°dONLNd\
x
Ñ)
 °dONLNd]
Öä
ë

(
éäthe client application sets v^‡°dONLNdz
Ö

ë
&)xarious flÄ@°dONLNdÉ
Ö
&
ë
R)$ags in the cÄ°dONLNdé
Ö
S
ë
É)-sendMode`Ä°dONLNdñ
Ö
É
ë
¿)0 parameter to )`°dONLNd§
Ö
¡
ë
Â)>AESend' °dONLNd™
Ö
Â
ë
˝)$. The °dONLNd∞
íä
û
#(
õä!Apple Event Manager sets the corr؆°dONLNd—
í
#
û
Z)ôesponding fl†°dONLNd›
í
Z
û
Ü)7ags in the ”‡°dONLNdË
í
á
û
ˇ)-keyInteractLevelAttrÃ`°dONLNd¸
í
ˇ
û
)x
 °dONLNd˝
üä
´Œ(
®äattribute of the B‡°dONLNd
üŒ
´
)DApple event.°dONLNd
±ä
Ω
(
∫ä"The server application sets its prÉ@°dONLNd=
±

Ω
))èefer/`°dONLNdA
±
*
Ω
k)ences with the Ò¿°dONLNdP
±
k
Ω
ı)AAESetInteractionAllowedÈ °dONLNdg
±
ı
Ω
˜)ä
 °dONLNdh
æä
 (
«äYfunction. This function lets your application specify whether it allows interaction with °dONLNd¡
Àä
◊«*the user as a r_¿°dONLNd–
À«
◊Ì)=
esult of r&†°dONLNd⁄
ÀÓ
◊
")'eceiving an t†°dONLNdÊ
À
"
◊
b)4Apple event frX@°dONLNdÙ
À
b
◊
î)@om itself; fr®@°dONLNd

À
î
◊
È)2om itself and other °dONLNd
ÿä
‰ì(
·äprG °dONLNd
ÿî
‰Ê)
ocesses on the locaÈÄ°dONLNd*
ÿÊ
‰
)Rl computer;ìÄ°dONLNd5
ÿ

‰
.)3 or frÄ°dONLNd;
ÿ
/
‰
{)om itself, local prI@°dONLNdN
ÿ
{
‰
Ω)Locesses, and pr≠Ä°dONLNd]
ÿ
Ω
‰
Ê)B
ocesses frv`°dONLNdg
ÿ
Á
‰
˜)*om °dONLNdj
Âä
Ò
!(
Óä another computer on the network.°dONLNdã
˜äê*
Y@Ä°dONLNdå
˜ê¸)our application calls the ¬°dONLNd¶
˜¸
h)lAEInteractWithUserª@°dONLNd∏
˜
h
©)l function befor© °dONLNd«
˜
©    )Ae interacting with the °dONLNdfiäù(äuser√°dONLNd‚ú™). If ı`°dONLNdÁ™
)AEInteractWithUserÓ†°dONLNd˘

)l r3†°dONLNd˚

K)eturns the % °dONLNd
L
j)/noErr#@°dONLNd
j
p) rh@°dONLNd
p)%esult code, then your application is °dONLNd2äú(äcurrØ°dONLNd6ú◊)ently in the fr3‡°dONLNdEÿÛ)<ont anÄ°dONLNdKÙˇ)d f˛ °dONLNdNˇ
)
r√ °dONLNdO

x)ee to interact with the userl¿°dONLNdk
x
Ü)u. If ü °dONLNdp
Ü
Ú)AEInteractWithUserò`°dONLNdÇ
Ú
Ù)l
 °dONLNdÉä*ç('ä
rE°dONLNdÑé*º)eturns the 6Ä°dONLNdèΩ*
A)/errAENoUserInteraction.@°dONLNd•
A*
G)Ñ rs@°dONLNdß
G*)-esult code, the conditions didn’t allow user °dONLNd‘+ä7
´(4äBinteraction and your application should not interact with the user3Ä°dONLNd    +
´7
≠(4
´
.°dONLNd    =äI°(FäThe rÄ¿°dONLNd    =°I
˝)Test of this section explains how to set user interactions for the client and server °dONLNd    qJäV
(Sä!applications and the practical ef†°dONLNd    íJ
V
#)çfec§`°dONLNd    ïJ
#V
,)t t© °dONLNd    òJ
,V
f)    hese settings \°dONLNd    ¶J
gV
~);have @°dONLNd    ´J
V
π)when a serveI¿°dONLNd    ∑J
πV
≈):r nç¿°dONLNd    ∫J
≈V
)eeds to interact °dONLNd    ÀWäcª(`äwith a user °dONLNd    ÷WªcΩ)1
.ˇ"∂@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-46    )BInteracting WÅ0)5ith the User4^*¿
¯

k*r
¯4l*r
¯ mlm
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\lk◊(glSetting the Client ãj°dONLNd\◊k
)kApplication’/R°dONLNd\
k
’)Fs User Interaction Preferencesˇˇˇˇˇˇ€r)”
4
°dONLNd?rl~
?({l3The client application sets its user interaction pr‡Ä°dONLNdrr
?~
O)”efer冰dONLNdvr
P~
û)ences by setting fl@°dONLNdâr
ü~
À)Oags in the ,
Courier°dONLNdîlãú(àlsendMode}°dONLNdúúãÍ)0 parameter to the £@°dONLNdÆÍã
)NAESend°°dONLNd¥
ã
M)$ function. The †°dONLNd√
Nã
Ò)@"Apple Event Manager automatically °dONLNdÂålò∞(ïladds the specifi@°dONLNdıå±òƒ)Eed fl≤ °dONLNd˙åƒò)ags to the ìÄ°dONLNd
åÒò
i)-keyInteractLevelAttrå°dONLNd
å
iò
Ø)x attribute of the Œ‡°dONLNd
+å
Øò
Í)FApple event. °dONLNd
8ôl•é(¢lThese flœ °dONLNd
@ôé•®)"ags ar‡@°dONLNd
Fô®•≥)e rÓ‡°dONLNd
Iô≥•¡)epr†°dONLNd
Lô¬•
])#esented by the following constants:°dONLNdÁ
®l
¥«(
±lFor example, supposlÄ°dONLNd˙
®»
¥‘)\e a∂ °dONLNd˝
®‘
¥
Δ)9 client application sends a Set Data event to a database °dONLNd6
µl
¡˝(
æl application to change a customer`°dONLNdV
µˇ
¡
)ì’s addrï °dONLNd]
µ

¡
ø)%ess. The database application is confi!°dONLNdÉ
µ
¿
¡
œ)£gur|@°dONLNdÜ
µ
œ
¡
Á)ed to °dONLNdå
¬l
Œo(
Àl
rE°dONLNdç
¬p
Œ∫)equest user confiº °dONLNdû
º
Œ
L)J rmation of changes to a customerX@°dONLNdæ
¬
N
Œ
[)î’s r°Ä°dONLNd¬
¬
[
Œ
m)ecor‡°dONLNdΔ
¬
n
Œ
Í) d. In this case the client sets °dONLNdÊ
œl
€|(
ÿlthe ›`°dONLNdÍ
œ|
€–)kAECanInteractÿ °dONLNd¯
œ–
€ÿ)T fld‡°dONLNd˚
œŸ
€˝)    ag beforS†°dONLNd
œ˝
€
‡)$4e sending the event. Thus, the database application °dONLNd7
‹l
Ë
b(
Âl;attempts to interact with the user if interaction is alloweZ`°dONLNdr
‹
c
Ë
t)˜d. If(Ä°dONLNdw
‹
u
Ë
Ï) interaction is not allowed, °dONLNdî
Èl
ıÊ(
Últhe database makes the corr.@°dONLNdØ
ÈÁ
ı
£){)ection anyway without consulting the userA¿°dONLNdÿ
È
£
ı
—)º    . HoweverŒ`°dONLNd·
È
–
ı
Ó)-    , if the °dONLNdÍ
ˆl
p(
ˇl<client application sends a Delete event to delete a customer≠@°dONLNd&
ˆ
q
~(
ˇ
q’s rˆÄ°dONLNd*
ˆ
~
ê)ecorj‡°dONLNd.
ˆ
ë
Æ)d entirë`°dONLNd5
ˆ
Æ
Ù)ely and sets the °dONLNdFl“(lkAEAlwaysInteracty†°dONLNdW“◊)f f°dONLNdYÿ
£)0lag, the database application deletes the specifŸ†°dONLNdâ
£
∑)Àied rÏ`°dONLNdé
∑
…)ecor`¿°dONLNdí
 
“)d ¸Ä°dONLNdî
“
Ë)only :‡°dONLNdô
È
Ò)if °dONLNdúlÌ(lit can interact with the user fiï°dONLNdºÌ
)Å    rst and rπ °dONLNd≈

I)%eceives confiï¿°dONLNd“
J
‚)8$rmation of the decision to delete a °dONLNdˆl)o(&l
rE°dONLNd˜p)Ç)ecorπ`°dONLNd˚Ç)
∫)Jd. If interaction with the user is not allowed, the database application r…Ä°dONLNd    E
∫)
Â(&
∫
eturns an °dONLNd    O*l6x(3lerr
@°dONLNd    R*y6Ç)or¨°dONLNd    T*Å6ƒ). By setting the àÄ°dONLNd    e*≈6
+)DkAEAlwaysInteractÇ °dONLNd    v*
+6
3)f fl‡°dONLNd    y*
46
ª)     ag, the client application ensurt¿°dONLNd    ô*
ª6
Í)áes that the °dONLNd    •7lCÄ(@lentir
¿°dONLNd    ™7ÅCå)e r`°dONLNd    ≠7åCû)ecorç¿°dONLNd    ±7ûC
®)>d won’t be lost if the user sends the Delete event by mistake.°dONLNd    IlU
T(Rl8If the client application doesn’t specify any of the thr¸@°dONLNd
(I
TU
≠)Ëee user interaction fl∂‡°dONLNd
>I
ÆU
“)Z    ags, the °dONLNd
GVlbâ(_lApple }Ä°dONLNd
MVäb
)Event Manager sets either the @°dONLNd
kV
b
p)ÜkAENeverInteract@°dONLNd
{V
pb
é)` or the ”¿°dONLNd
ÉV
éb
‚)kAECanInteractŒÄ°dONLNd
ëV
‚b
Í)T fl[@°dONLNd
îV
Îb
¯)    ag °dONLNd
ócloá(llin the  °dONLNd
ûcào
)keyInteractLevelAttr†°dONLNd
≤c
o
F)x attribute of the RÄ°dONLNd
ƒc
Fo
—)FApple event, depending on the °dONLNd
‚pl|ë(yl    location ?¿°dONLNd
Îpí|
ê)&>of the server application. If the server application is on a rÿ°dONLNd)p
ê|
ÿ)˛emote computerp °dONLNd7p
ÿ|
›)H, 
    °dONLNd
p≤lΩ~(∫lFlag°dONLNd
u≤ÊΩ
)zDescription
°dONLNd
Ç¿lÃÃ(…lkAENeverInteract°dONLNd
ì¿ÊÃ
´)z-The server application should never interact °dONLNd
¿ÀÊ◊˙*with” °dONLNd
ƒÀ˙◊¸)
 S °dONLNd
≈À˝◊

)the0Ä°dONLNd
»À
◊
)
 ∞Ä°dONLNd
…À
◊
 )user∞‡°dONLNd
ÕÀ
 ◊
")
 0‡°dONLNd
ŒÀ
#◊
+)inꠡdONLNd
–À
+◊
-)
 j†°dONLNd
—À
.◊
1)
r/†°dONLNd
“À
2◊
f)esponse to tÄ °dONLNd
fiÀ
f◊
s)4he <¿°dONLNd
·À
s◊
z)
A°dONLNd
‚À
{◊
∑)pple event. If °dONLNd
Ò÷Ê‚ˆ(flÊthisπ °dONLNd
ı÷ˆ‚¯)
 9 °dONLNd
ˆ÷˘‚ˇ)
flE‡°dONLNd
¯÷ˇ‚
    )ag’°dONLNd
˙÷
    ‚
)

 U°dONLNd
˚÷
‚
)isz`°dONLNd
˝÷
‚
)
 ˙`°dONLNd
˛÷
‚
#)set,√`°dONLNd÷
$‚
&)
 C`°dONLNd÷
'‚
ì)AEInteractWithUser<†°dONLNd÷
ì‚
ô)l rņ°dONLNd÷
ô‚
«)eturns the °dONLNd"·ÊÌ
j(ÍÊerrAENoUserInteractionw¿°dONLNd8·
jÌ
p)Ñ rº¿°dONLNd:·
pÌ
∫)esult code. This f¸@°dONLNdL·
∫Ì
„)Jlag is the °dONLNdWÏʯ
0(ıÊdefault when an °Ä°dONLNdgÏ
0¯
ù)JApple event is sent to a r(‡°dONLNdÅÏ
û¯
Ô)nemote application.°dONLNdï¸l
¿(
lkAECanInteract°dONLNd§¸Ê

Ã)z6The server application can interact with the user in r*†°dONLNd⁄¸
Õ

Ú)Áesponse °dONLNd‚
Ê
Ù(
Êto t˙@°dONLNdÊ
Ù


)he ∂‡°dONLNdÈ




)
A~ °dONLNdÍ

    

€)/pple event—by convention, if the user needs to °dONLNd
Ê

u(
Ê supply information to the server.‡°dONLNd9

u

õ)è. If this fl' °dONLNdE

ú

Â)'ag is set and the °dONLNdW
Ê
)
W(
&Êserver allows interaction, P@°dONLNdr

X
)
ƒ)rAEInteractWithUserIÄ°dONLNdÑ

ƒ
)
‚)l either °dONLNdå
(Ê
4
è(
1Ê(brings the server application to the forì¿°dONLNd¥
(
è
4
ù)©egr±Ä°dONLNd∑
(
ù
4
‰)ound or posts a °dONLNd«
3Ê
?˝(
<Ênotifi˛`°dONLNdÕ
3˝
?
)cation r%@°dONLNd’
3

?
\)"equest. This fl|`°dONLNd‰
3
\
?
Õ)=ag is the default when an Ø¿°dONLNd˛
3
Õ
?
Í)qApple °dONLNd
>Ê
J
}(
GÊ%event is sent to a local application.≤@°dONLNd)
>
}
J
)ó
 °dONLNd,
Nl
Z“(
WlkAEAlwaysInteract°dONLNd>
NÊ
Z
Ã)z6The server application can interact with the user in r*†°dONLNdt
N
Õ
Z
Ú)Áesponse °dONLNd|
YÊ
eÙ(
bÊto t˙@°dONLNdÄ
YÙ
e

)he ∂‡°dONLNdÉ
Y


e
)
A~ °dONLNdÑ
Y
    
e
‚).pple event—by convention, whenever the server °dONLNd≤
dÊ
p
ò(
mÊ(application normally asks a user to confi)Ä°dONLNd€
d
ô
p
‚)≥rm a decision or °dONLNdÏ
oÊ
{
T(
xÊinteract in any other way °dONLNd
o
T
{
˜)n', even if no additional information is °dONLNd,
zÊ
Ü
(
ÉÊ    needed fr~†°dONLNd5
z

Ü
D)*om the userËÄ°dONLNd@
z
C
Ü
i)3. If this fl‡¿°dONLNdL
z
j
Ü
)' ag is set and the server allows °dONLNdl
ÖÊ
ë
(
éÊinteraction, @°dONLNdy
Ö

ë
á)5AEInteractWithUserÄ°dONLNdã
Ö
á
ë
Ú)l either brings the server °dONLNd•
êÊ
ú
B(
ôÊapplication to the for⁄Ä°dONLNdª
ê
B
ú
P)\egr¯@°dONLNdæ
ê
P
ú
Æ)ound or posts a notifi|Ä°dONLNd‘
ê
Ø
ú
–)_cation r£`°dONLNd‹
ê
–
ú
Ò)!equest. ˇB*@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡äInteracting WÅ0)5ith the User

, (‡4-47
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿°dONLNd\ähö(eäthe °dONLNd\öh∑)Apple |Ä°dONLNd
\∏h
!)Event Manager sets the ,
Courier@°dONLNd!\
"h
Ç)jkAENeverInteract@°dONLNd1\
Çh
ä)` flò°dONLNd4\
äh
Ò)ag as the default. If the °dONLNdNiäuß(räserver [¿°dONLNdUi®u
E)$application is on the local computeró°dONLNdyi
Eu
Z)ù, the ñ°dONLNdi
Zu
·)Apple Event Manager sets the °dONLNdúväÇfi(äkAECanInteractz¿°dONLNd™vfiÇ„)T f °dONLNd¨v‰Ç
)lag as the 1°dONLNd∑v
Ç
1),default.°dONLNd¿àäîç(ëä
IfiÄ°dONLNd¡àçîÂ)n addition to the thrØ`°dONLNd÷àÊî
?)Yee user interaction flj°dONLNdÏà
@î
˛)Z-ags, the client application can set another fló°dONLNd
à
˛î)æag °dONLNd
ïä°•(ûäin the  °dONLNd
$ﶰ÷)sendMode °dONLNd
,ï÷°
)0 parameter to ›°dONLNd
:ï
°
7)=AESend⁄¿°dONLNd
@ï
7°
H)$ to rW†°dONLNd
Eï
I°
å)equest that the _†°dONLNd
Uï
å°
)CApple Event Manager °dONLNd
i¢äÆ
N(´ä,immediately bring the server application dir]‡°dONLNd
ï¢
NÆ
ç)ƒectly to the forı@°dONLNd
•¢
çÆ
õ)?egr°dONLNd
®¢
úÆ)ound instead of posting a °dONLNd
¬Ø䪰(∏änotifi˛`°dONLNd
»Ø°ª¬)cation r%@°dONLNd
–Ø√ª‚)"equest:°dONLNdç
;ä
G∞(
DäNote tha‰ °dONLNdï
;∞
G„)&t although tB °dONLNd°
;‰
GÒ)4he ] °dONLNd§
;Ò
G
W)kAECanSwitchLayerV¿°dONLNdµ
;
W
G
_)f fl„Ä°dONLNd∏
;
_
G
ö)ag must be se•°dONLNd≈
;
õ
G
§)<t fª@°dONLNd»
;
§
G
¿)    or the ¢`°dONLNdœ
;
¿
G
˙)Apple Event °dONLNd€
Hä
T
H(
Qä+Manager to bring the server application dirF °dONLNd
H
I
T
à)øectly to the for›Ä°dONLNd
H
à
T
ñ)?egr˚@°dONLNd
H
ñ
T
 )ound, settin™ °dONLNd%
H
À
T)5g it does not °dONLNd3
Uä
aè(
^ä
g °dONLNd4
Uê
a›)uarantee that the °dONLNdF
U›
a
ù)M)Apple Event Manager will bypass the notifi≤†°dONLNdp
U
ù
a
æ)¿cation rŸÄ°dONLNdx
U
æ
a
˚)!equest if user °dONLNdá
bä
nˆ(
käinteraction is permitted. Δ °dONLNd°
bˆ
n
#)l    Another fl1°dONLNd´
b
$
n
C).ag, the Ä°dONLNd≥
b
D
n
å) kAEWaitReply°dONLNdø
b
å
n
î)H fl•¿°dONLNd¬
b
î
n)ag, must also be set in the °dONLNdfi
oä
{∫(
xäsendMode}°dONLNdÊ
o∫
{Ê)0     parameteõ`°dONLNdÔ
oÊ
{È),
r–†°dONLNd
oÈ
{
É)$, and the client application must pr°dONLNd
o
Ñ
{
Á)õovide an idle function.°dONLNd,
Åä
çù(
ääThe ª¿°dONLNd0
Åù
çÂ)kAEWaitReply∑@°dONLNd<
ÅÂ
çÌ)H flD°dONLNd?
ÅÓ
ç
/)    ag is one of thr´ °dONLNdO
Å
/
ç
A)Aee flÀ °dONLNdT
Å
A
ç
m)ags in the Æ`°dONLNd_
Å
n
ç
û)-sendMode´`°dONLNdg
Å
û
ç)0 parameter that a client °dONLNdÄ
éä
ö
Ÿ(
óäMapplication can set to specify whether and how the client should wait for a rò`°dONLNdÕ
é
Ÿ
ö
Ï(
ó
Ÿeplyø‡°dONLNd—
é
Î
ö
). °dONLNd”
õä
ßú(
§ä(ForÀ °dONLNd◊
õú
ßû)
 K °dONLNdÿ
õü
ߧ)
aK °dONLNdŸ
õ§
߶)
 À °dONLNd⁄
õ¶
ß
)description of these flʆ°dONLNdÒ
õ

ß
))_    ags, see °dONLNd˙
õ
*
ß
c)%“Sending an µ`°dONLNd
õ
b
ß)8$Apple Event and Handling the Reply” °dONLNd*
®ä
¥Ø(
±äon page !¿°dONLNd2
®∞
¥¬)&3-30u†°dONLNd6
®¬
¥
å)3.) If the client application is not waiting for a r®¿°dONLNdi
®
å
¥
ü) eply–@°dONLNdm
®
û
¥
ˆ), the user may have °dONLNdÅ
µä
¡˚(
æäcontinued with other wor˜Ä°dONLNdô
µ˚
¡
)qk. (@°dONLNdú
µ

¡
)An¿‡°dONLNdû
µ

¡
i) application switch ¯ °dONLNd≤
µ
i
¡
†)Vat this point g`°dONLNd¿
µ
°
¡
∏)8mighÑ@°dONLNdƒ
µ
∏
¡
√)t bŒ@°dONLNd«
µ
√
¡
ˇ)e unexpected °dONLNd‘
Š
Κ(
Àäandm °dONLNd◊
¬õ
Ν)
 Ì °dONLNdÿ
¬ù
Œº)would D‡°dONLNdfi
¬Ω
Œ“) thus ¿°dONLNd„
¬”
Œ
e)#violate the principle of user contr∂ °dONLNd
¬
e
Œ
¥)íol as described in Â`°dONLNd
¬
¥
Œ)OMacintosh Human °dONLNd)
ϊ
€›(
ÿäInterface Guidelines.°dONLNd?
·ä
Ì
*#If the client application sets the H`°dONLNdb
·

Ì
^)åkAEWaitReplyC‡°dONLNdn
·
^
Ì
f)H fl–†°dONLNdq
·
f
Ì
Ω)ag, it should also pr˚†°dONLNdÜ
·
Ω
Ì
¯)Wovide an idle °dONLNdî
Óä
˙Î(
˜äfunction when it calls ˙`°dONLNd´
ÓÎ
˙
)aAESend¯ °dONLNd±
Ó

˙)$< so that it can handle events such as update events that it °dONLNdÌ
˚äç(ä
rE°dONLNdÓ
˚é
)eceives while waiting for the rIÄ°dONLNd
˚

&)Öeplyq°dONLNd
˚
%
r). Idle functions ar≠Ä°dONLNd$
˚
r
±)Me described in ãÄ°dONLNd3
˚
≤
¡)@“WŒ °dONLNd5
˚
¿
˚)riting an Idle °dONLNdDä∏(ä
Function,”IÄ°dONLNdNπ
)/ which begins on π‡°dONLNd_

)Mpage î¿°dONLNdd

0)5-21蠡dONLNdh
0
2)
.°dONLNdjä&
(#ä When a server application calls ˝°dONLNdä
&
Ç)åAEInteractWithUser8‡°dONLNdú
Ç&
ƒ)l, the function fi1@°dONLNd≠
≈&
Î)C    rst check-‡°dONLNd∂
Ï&
Ú)'s °dONLNd∏'ä3¥(0ä    whether t`°dONLNd¡'µ3¬)+he `°dONLNdƒ'¬3
")kAENeverInteract`°dONLNd‘'
"3
*)` fl¶ °dONLNd◊'
*3
R)
ag in the L`°dONLNd·'
S3
À))keyInteractLevelAttrD‡°dONLNdı'
À3)x attribute of the °dONLNd    4ä@Ù(=äApple event is set. (The j`°dONLNd     4Ù@
Ω)j-Apple Event Manager sets this attribute accoṙ°dONLNd    M4
Ω@
ı)…ding to the fltÄ°dONLNd    [4
ˆ@)9ags °dONLNd    _AäM¶(JäspecifiÓ °dONLNd    fA¶MŒ)
ed in the ͆°dONLNd    pAœMˇ))sendModeÁ†°dONLNd    xAˇM
<)0 parameter of ¬°dONLNd    ÜA
=M
a)>AESendø¿°dONLNd    åA
aM
Ç)$
.) If the £`°dONLNd    ñA
ÉM
„)"kAENeverInteractù`°dONLNd    ¶A
„M
Î)` fl* °dONLNd    ©A
ÏM)    ag is set, °dONLNd    ¥NäZˆ(WäAEInteractWithUsery@°dONLNd    ΔNˆZ
6)l immediately r‡°dONLNd    ‘N
7Z
e)Aeturns the `°dONLNd    flN
fZ
Í)/errAENoUserInteraction     °dONLNd    ıN
ÍZ
)Ñ rN °dONLNd    ˜N
Z)esult °dONLNd    ˝[ägÙ(däcode. If the client specifiÁ`°dONLNd
[Ùg

)jed L¿°dONLNd
[
g
V)kAECanInteractGÄ°dONLNd
)[
Vg
d)T or ؆°dONLNd
-[
dg
 )kAEAlwaysInteract©@°dONLNd
>[
 g
œ)f, °dONLNd
@hätˆ(qäAEInteractWithUsery@°dONLNd
Rhˆt
D)l checks the server7`°dONLNd
dh
Et
X)O’s prÇ¿°dONLNd
ih
Xt
h)efer.‡°dONLNd
mh
it
⁄)ences for user interaction.ó`°dONLNd
àh
⁄t
‹)q
 
    °dONLNd
ÿ»ä”ú(–äFlag°dONLNd
›»
”
5)zDescription
°dONLNd
Í÷ä‚(fläkAECanSwitchLayer°dONLNd
¸÷
‚)zCIf both the client and server allow interaction, and if the client °dONLNd?·
Ì
“*1application is the active application on the locam¿°dONLNdp·
”Ì)œl computer °dONLNd{Ï
¯
    (ı

a°dONLNd|Ï
    ¯
`)nd is waiting for a r^ °dONLNdëÏ
`¯
“)Weply (that is, it has set the °dONLNdؘ


L(

kAEWaitReply{Ä°dONLNdª˜
L

Q)H f‡°dONLNdΩ˜
R

g)lag), Î@°dONLNd√˜
g

”)AEInteractWithUser‰Ä°dONLNd’˜
”
)l brings the °dONLNd·



.(


server dir$‡°dONLNdÎ

/

n)+ectly to the forº@°dONLNd˚

n

|)?egr⁄°dONLNd˛

|

À)ound. Otherwise, °dONLNd



p(

AEInteractWithUsery@°dONLNd!

p

Ø)l uses the Notif4‡°dONLNd0

∞
)@ication Manager to °dONLNdC


$
(
!

rE°dONLNdD


$
˘)9equest that the user bring the server application to the °dONLNd}
#

/
(
,
for`°dONLNdÄ
#

/
)egr, °dONLNdÉ
#

/
8)ound.‡°dONLNdà
#
9
/
;)
 dONLNdâ
#
;
/
=)
 ˇ∞@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-48    )BInteracting WÅ0)5ith the User4^*¿
¯

k*r
¯4l*r
¯ mlm
¯

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\lk›(glSetting the Server ˝J°dONLNd\‹k
!)pApplication’°2°dONLNd\
"k
⁄)Fs User Interaction Preferencesˇˇˇˇˇˇ€r)Œ
4
°dONLNd?rl~
({l'The server sets its user interaction prÁ°dONLNdfr
~
)¢eferì °dONLNdjr
~
r)ences by using the ,
Courier°dONLNd}lãˆ(àlAESetInteractionAllowedw`°dONLNdîˆã
)ä     function†°dONLNdù
ã
.)(. Th˜¿°dONLNd°
.ã
V)
is functio⁄°dONLNd´
Wã
y))n specif± °dONLNd≥
yã
»)"ies the conditions °dONLNdΔålòâ(ïlunder ∞Ä°dONLNdÃåâòë)
wÄ°dONLNdÕåíò
à)    :hich your application is willing to interact with the userL‡°dONLNd
å
áò
â)ı
.°dONLNd
    £lØ
\(¨l(myErr := AESetInteractionAllowed(level);°dONLNd
2ªl«*The ª¿°dONLNd
6ª«ù)levelπ‡°dONLNd
;ªù«˙) parameter is of type V‡°dONLNd
Qª˚«
a)^AEInteractAllowedPÄ°dONLNd
bª
a«
f)f. °dONLNd
e“lfiÑ(€lTYPE°dONLNd
k“êfi
å)$*AEInteractAllowed = (kAEInteractWithSelf, °dONLNd
ü‡
Ï
í+~kAEInteractWithLocal, °dONLNd
øÓ
˙
Ü*kAEInteractWithAll);°dONLNd
‘
l
r(
l
Y@Ä°dONLNd
’
r

s)=ou can specify one of these values for the interaction level:°dONLNd∫
»l
‘
Ä(
—lCIf the server application does not set the user interaction level, ¿°dONLNd˝
»
Å
‘
Ì(
—
ÅAEInteractWithUser°dONLNd
»
Ì
‘
Ô)l
 °dONLNd
’l
·Å(
filuses J¿°dONLNd
’Ç
·˙)kAEInteractWithLocalC@°dONLNd)
’˙
·
3)x as the value.°dONLNd8
Ál
Û˙(
l#If the application sends itself an ÿ°dONLNd[
Á˙
Û
V)éApple event (that is, Ú °dONLNdq
Á
V
Û
^)\if Æ`°dONLNdt
Á
_
Û
Ó)    #the application is both the client °dONLNdó
Ùl
(
˝l$and the server) without setting the Ω‡°dONLNdª
Ù

g)õkAENeverInteract∑‡°dONLNdÀ
Ù
g
o)` flD†°dONLNdŒ
Ù
p
)    ag, ”¿°dONLNd“
Ù

Î)AEInteractWithUserÕ°dONLNd‰
Ù
Î
Ì)l
 °dONLNdÂ
l
z(
lAalways allows user interaction. If the client application is a pr—‡°dONLNd&

z
√(

zocess on the locam†°dONLNd7

ƒ
ˆ)Jl computer °dONLNdBlõ(l
and specifi[@°dONLNdMúß)0es ·‡°dONLNdPß˚)kAECanInteract‹†°dONLNd^˚
    )T or D¿°dONLNdb


p)kAEAlwaysInteract>`°dONLNds
p
r)f
,æ`°dONLNdt
r
á) and ´Ä°dONLNdy
à
ê)if g¿°dONLNd|
ë
∏)        the serve.@°dONLNdÖ
π
„)(r has set t:†°dONLNdê
„
)*he °dONLNdìl'∏($linteraction level tf‡°dONLNd¶π'¿)Mo \`°dONLNd®¡'«)
k\°dONLNd©«'
9)AEInteractWithLocalT‡°dONLNdº
9'
G)r or Ω°dONLNd¿
G'
≠)kAEInteractWithAl∂†°dONLNd—
≠'
≥)f
l∂@°dONLNd“
≥'
µ)
,6@°dONLNd”
∂'
Œ) then °dONLNdŸ(l4ÿ(1lAEInteractWithUsery@°dONLNdÎ(ÿ4
ì)l/ allows user interaction. If the client is a prà¿°dONLNd(
ì4
≈)ªocess on a r>°dONLNd&(
Δ4
„)3emote °dONLNd,5lA‹(>lcomputer on the networkÄ°dONLNdC5›A
)q and specifil¿°dONLNdO5
A
)2es Û`°dONLNdR5
A
n)kAECanInteractÓ °dONLNd`5
nA
|)T or V@°dONLNdd5
}A
„)kAEAlwaysInteractO‡°dONLNdu5
„A
Â)f
,œ‡°dONLNdv5
ÂA
Á)
 °dONLNdwBlNÿ(KlAEInteractWithUsery@°dONLNdâBÿN
®)l2 allows user interaction only if the server specif߆°dONLNdªB
®N
∏)–ied °dONLNdøOl[|(Xlthe ›`°dONLNd√O|[Ë)kAEInteractWithAll÷†°dONLNd’OË[)l flc`°dONLNdÿOÒ[
∏)    2ag for the interaction level. In all other cases, °dONLNd
\lhÿ(elAEInteractWithUsery@°dONLNd\ÿh
e)l! does not allow user interaction.“@°dONLNd=\
eh
g)ç
 R@°dONLNd>\
hh
j)
 
    °dONLNd
l
*~(
'lFlag°dONLNd
¯
*
))åDescription
°dONLNd%
-l
9fi(
6lkAEInteractWithSelf°dONLNd9
-¯
9˛)å
Y@Ä°dONLNd:
-˛
9
)
o∂°dONLNd;
-

9
a)ur server application B`°dONLNdQ
-
b
9
‘)_can interact with the user ü‡°dONLNdl
-
‘
9
fl)rin °dONLNdo
8¯
D˚(
A¯
rE°dONLNdp
8¸
D
:)esponse to an F °dONLNd~
8
:
D
m)>
Apple evenNÄ°dONLNdà
8
m
D
x)3t oÜ`°dONLNdã
8
x
D
à)nly O@°dONLNdè
8
â
D
¿)when your a°dONLNdö
8
¡
D
Û)8pplication i0@°dONLNd¶
8
Û
D
˘)2s °dONLNd®
C¯
O
<(
L¯also the client añ†°dONLNdπ
C
<
O
h)D
pplicationMÄ°dONLNd√
C
i
O
€)-—that is, only when your °dONLNd‹
N¯
Z
i(
W¯application is sending theˆ@°dONLNdˆ
N
i
Z
k)q
 ‡°dONLNd˜
N
l
Z
«)Apple event to itself.°dONLNd
^l
j‰(
glkAEInteractWithLocal°dONLNd$
^¯
j˛)å
Y@Ä°dONLNd%
^˛
j
fl)5our server application can interact with the user in °dONLNdZ
i¯
u˚(
r¯
rE°dONLNd[
i¸
u
:)esponse to an F °dONLNdi
i
:
u
)>+Apple event only if the client application °dONLNdî
t¯
Ä
Ô(
}¯9is on the same computer as your application. This is the °dONLNdÕ
¯
ã
ˆ*=default if the server application does not call the function °dONLNd

ä¯
ñ
Ç*AESetInteractionAllowedw`°dONLNd!
ä
Ç
ñ
Ñ)ä
.°dONLNd$
öl
¶ÿ(
£lkAEInteractWithAll°dONLNd7
ö¯
¶˛)å
Y@Ä°dONLNd8
ö˛
¶
)our sl¿°dONLNd=
ö

¶
a)erver application B`°dONLNdO
ö
b
¶
‘)Ncan interact with the user ü‡°dONLNdj
ö
‘
¶
fl)rin °dONLNdm
•¯
±˚(
Ư
rE°dONLNdn
•¸
±
:)esponse to an F °dONLNd|
•
:
±
m)>
Apple evenNÄ°dONLNdÜ
•
m
±
ô)3t sent by aB°dONLNdë
•
ö
±
ß)-ny "Ä°dONLNdî
•
®
±
«)client a¿‡°dONLNdú
•
«
±
ˆ)pplication °dONLNdß
∞¯
º
C(
π¯on any computer+†°dONLNd∂
∞
C
º
E)K
.ˇ9¶@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4H\,Palatino
&e.
3+ä"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@äResponding to ,):Apple Events4⁄ä˙(‡äInteracting WÅ0)5ith the User

, (‡4-49
ˇˇˇˇˇˇˇˇ4
l4
älòÄ.
lB
äoMM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
lB
äo
lB
äo$””””””””””””””””””””””””””””””òÄ

l6
ä@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
l6
ä@
l6
ä@˜˜˜˜˜˜˜˜˜˜˜˜˜¸
ˇˇ˛¸˛ˇˇ¸ˇˇˇ˛˙ˇ˛˙ˇ˜˜˜˜˜˜˜˜˜˜˜˜
4
è4Ö?òÄ

è6Ö@MM
!ġˇˇˇˇˇˇˇˇˇˇÃÃˇˇˇˇôôˇˇˇˇffˇˇˇˇ33ˇˇˇˇˇˇÃÃˇˇˇˇÃÃÃÃˇˇÃÃôôˇˇÃÃffˇˇÃÃ33ˇˇÃÃˇˇôôˇˇˇˇôôÃÃˇˇôôôôˇˇôôffˇˇôô33ˇˇôôˇˇffˇˇˇˇffÃÃˇˇffôôˇˇffffˇˇff33ˇˇffˇˇ33ˇˇˇˇ33ÃÃˇˇ33ôôˇˇ33ffˇˇ3333ˇˇ33ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇˇˇÃÃˇˇÃÃÃÃˇˇôôÃÃˇˇffÃÃˇˇ33ÃÃˇˇÃÃÃÃˇˇÃÃÃÃÃÃÃÃÃÃôôÃÃÃÃffÃÃÃÃ33ÃÃÃÃÃÃôôˇˇÃÃôôÃÃÃÃôôôôÃÃôôffÃÃôô33ÃÃôôÃÃffˇˇÃÃffÃÃÃÃffôôÃÃffffÃÃff33ÃÃffÃÃ33ˇˇÃÃ33ÃÃÃÃ33ôôÃÃ33ffÃÃ3333ÃÃ33ÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇˇˇôôˇˇÃÃôôˇˇôôôôˇˇffôôˇˇ33ôôˇˇôôÃÃˇˇôôÃÃÃÃôôÃÃôôôôÃÃffôôÃÃ33ôôÃÃôôôôˇˇôôôôÃÃôôôôôôôôôôffôôôô33ôôôôôôffˇˇôôffÃÃôôffôôôôffffôôff33ôôffôô33ˇˇôô33ÃÃôô33ôôôô33ffôô3333ôô33ôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇˇˇffˇˇÃÃffˇˇôôffˇˇffffˇˇ33ffˇˇffÃÃˇˇffÃÃÃÃffÃÃôôffÃÃffffÃÃ33ffÃÃffôôˇˇffôôÃÃffôôôôffôôffffôô33ffôôffffˇˇffffÃÃffffôôffffffffff33ffffff33ˇˇff33ÃÃff33ôôff33ffff3333ff33ffˇˇffÃÃffôôffffff33ff33ˇˇˇˇ33ˇˇÃÃ33ˇˇôô33ˇˇff33ˇˇ3333ˇˇ33ÃÃˇˇ33ÃÃÃÃ33ÃÃôô33ÃÃff33ÃÃ3333ÃÃ33ôôˇˇ33ôôÃÃ33ôôôô33ôôff33ôô3333ôô33ffˇˇ33ffÃÃ33ffôô33ffff33ff3333ff3333ˇˇ3333ÃÃ3333ôô3333ff333333333333ˇˇ33ÃÃ33ôô33ff333333ˇˇˇˇˇˇÃÃˇˇôôˇˇffˇˇ33ˇˇÃÃˇˇÃÃÃÃÃÃôôÃÃffÃÃ33ÃÃôôˇˇôôÃÃôôôôôôffôô33ôôffˇˇffÃÃffôôffffff33ff33ˇˇ33ÃÃ33ôô33ff333333ˇˇÃÃôôff33ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓ››ªª™™ààwwUUDD""ÓÓÓÓÓÓ››››››ªªªªªª™™™™™™ààààààwwwwwwUUUUUUDDDDDD""""""
è6Ö@
è6Ö@$˛˙ˇ˚ˇˇ˚ˇˇ˚ˇˇ    ˛˛ˇˇˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˛˙ˇ˜˛¸ˇ
ˇ˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜    ˇ˛ˇ˛ˇˇ˛ˇˇˇˇ˛ˇˇ
˚ˇˇ˜˜˜˜˝¸ˇ
˛ˇ˛ˇˇ˝˛ˇ˛
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˜˜˛
ˇˇ¸¸
ˇˇ˛¸
ˇ˛ˇ¸
ˇˇ˛˛
ˇˇ¸˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˙ˇˇ
˛ˇ˛ˇˇ
˛ˇ˛ˇˇ˝˛ˇ˛˜˛˙ˇ˜˝˛ˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˜˜˜˛˙ˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ
˛ˇˇˇ˜˙ˇˇ¸
ˇˇ˛˛
ˇˇ¸¸
ˇˇ˛˝˝ˇˇ
˛ˇˇˇˇ
˛ˇˇˇˇ    ˛ˇˇˇ˛˜˛¸ˇˇ˚ˇ˛˙ˇˇ˛˝ˇ˛˜˝¸ˇ
˛ˇ˛ˇˇ˜    ˛ˇˇ˛
˛ˇˇˇˇ
˛ˇˇˇˇ    ˝ˇˇˇ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜4^H¿

kHr4lHr mäm

ˇ·ˇ‚7^ˇˇ‹.ˇ◊°dONLNd\äk
3(gäRequesting User Interactionˇˇˇˇˇˇ€r(g
4
°dONLNdrä~
™({äDIf your server application needs to interact with the user for any r6°dONLNdar
´~({
´eason, it must call the ,
Courier°dONLNdyäãˆ(àäAEInteractWithUsery@°dONLNdãˆã
T)l function to make suru@°dONLNd†
Tã
ï)^e it is in the for4Ä°dONLNd≤
ñã
§)BegrR@°dONLNdµ
§ã
‘)
ound befor†°dONLNdø
’ã
)1e it actually °dONLNdÕåäòÏ(ïäinteracts with the userÄ°dONLNd‰åÏò
)b. When ‡°dONLNdÎå
ò
z)"AEInteractWithUser
 °dONLNd˝å
zò)l# allows user interaction (based on °dONLNd
 ôä•Í(¢äthe client’s and server@°dONLNd
7ôÏ•ˇ)b’s prQ†°dONLNd
<ôˇ•
)efer˝¿°dONLNd
@ô
•
/)ences), cÄ°dONLNd
Hô
0•
ú)!AEInteractWithUser\¿°dONLNd
Zô
ú•
Î)l brings the server °dONLNd
m¶ä≤Ê(Øäapplication to the for⁄Ä°dONLNd
ɶÊ≤Ù)\egr¯@°dONLNd
ܶÙ≤
>)ound—either dir- °dONLNd
ï¶
?≤
¢)Kectly or after the user r˛@°dONLNd
ƶ
¢≤
Û)cesponds to a notifi\‡°dONLNd
¡¶
Ù≤)Rcation °dONLNd
»≥äøç(ºä
rE°dONLNd
…≥éø‚)equest—and then rX¿°dONLNd
⁄≥‚ø
)T    eturns a l‡°dONLNd
„≥
ø
&)&noErrk°dONLNd
Ë≥
&ø
,) r∞°dONLNd
Í≥
,ø
f)esult code. If f°dONLNd
˘≥
gø
”);AEInteractWithUser_@°dONLNd≥
”ø)l brings the °dONLNd¿äÖ(…äserver to the for`°dONLNd(¿–Ãfi)Fegrù °dONLNd+¿fiÃ
)ound dirP°dONLNd3¿
Ã
)'ectly(°dONLNd8¿
Ã
C), the cliena`°dONLNdC¿
CÃ
L)*t rË¿°dONLNdF¿
LÃ
Z)    etu˚‡°dONLNdI¿
ZÃ
h)rns¸‡°dONLNdL¿
hÃ
í) to the for†Ä°dONLNdW¿
ìÃ
°)+egræ@°dONLNdZ¿
°Ã)ound immediately after °dONLNdqÕ䟜(÷äthe server has fiT@°dONLNdÇÕ–Ÿ
\)F nished interacting with the user) °dONLNd¢Õ
\Ÿ
j)å. If [Ä°dONLNdßÕ
jŸ
÷)AEInteractWithUserT¿°dONLNdπÕ
÷Ÿ)l brings the °dONLNd≈⁄äÊ–(„äserver to the for`°dONLNd÷⁄–Êfi)Fegrù °dONLNdŸ⁄fiÊ
8)ound after the user r¸ °dONLNdÓ⁄
8Ê
â)Zesponds to a notifiZ¿°dONLNd
⁄
äÊ
´)Rcation rņ°dONLNd    ⁄
´Ê
˙)!equest, the server °dONLNdÁäÛç(ä
rE°dONLNdÁéÛÿ)emains in the for~‡°dONLNd.ÁÿÛÊ)Jegrú†°dONLNd1ÁÊÛ
£)+ound after completing the user interaction.°dONLNd]˘ä
ï(
äThr °dONLNd_˘ñ
ù)e ª¿°dONLNda˘ù
£)
Aª`°dONLNdb˘£

    )EInteractWithUserµ°dONLNds˘
    

O)f function specifi1`°dONLNdÑ˘
P
)G,es how long your handler is willing to wait °dONLNd∞
ä
§(
äfor a r
°dONLNd∑
•
“)
esponse fr °dONLNd¡
—

),om the userZ°dONLNdÃ



®)4'. For example, if the timeout value is Ò`°dONLNdÛ

®

”)£900 ticks (¨`°dONLNd˛

‘
),
15 secondsB‡°dONLNd

)0
)ñ¿°dONLNd    

    )
 °dONLNd

ä
≠(
äand the Ï °dONLNd
≠

I)#!Apple Event Manager posts a notifiÕ`°dONLNd4

J

k)ùcation rÙ@°dONLNd<

k

∑)!equest, the Notifi`°dONLNdN

∏

ˇ)Mcation Manager °dONLNd]
 ä
,¨(
)äbegins tÄ°dONLNde
 ≠
,

)#o display a blinking i3‡°dONLNd{
 


,
R)]con in the upperú °dONLNdã
 
R
,
¥)H-right corner of the scrχ°dONLNd£
 
¥
,
Ω)beeÄ °dONLNd•
 
æ
,
‚)
    n, then rE@°dONLNdÆ
 
„
,)%emoves °dONLNdµ
-ä
9±(
6ä    the notifi[¿°dONLNdø
-≤
9”)(cation rdž°dONLNd«
-”
9
)!equest (and thä@°dONLNd’
-

9
C)?e blinking i>°dONLNd·
-
D
9
¥)2con) if the user does not rI °dONLNd¸
-
¥
9
ˆ)pespond within °dONLNd

:ä
Fî(
Cä15°dONLNd
:î
Fñ)

 °dONLNd
:ó
F∫)secondsÄ°dONLNd
:∫
F
Ü)#/. (The discussion that follows describes some r톰dONLNdC
:
Ü
F)Ã"estrictions on the icons that can °dONLNde
Gä
S
(
Pä be displayed in this situation.)°dONLNdÜ
Yä
eí*
NŒ‡°dONLNdá
Yí
e
B))ote that the timeout value passed to the a`°dONLNd∞
Y
C
e
Ø)±AEInteractWithUserZ†°dONLNd¬
Y
Ø
e
)l function is separate °dONLNdÿ
fä
rë(
oäfrò‡°dONLNd⁄
fë
r
.)#om the timeout value passed to the @°dONLNd˝
f
/
r
S)ûAESend°dONLNd
f
S
r
π)$ function, which specifiÈ¿°dONLNd
f
π
r
)fes how long the °dONLNd+
sä

I(
|ä/client application is willing to wait for the rk†°dONLNdZ
s
I

n)ø    eply or r‹°dONLNdc
s
n

å)%eturn r¯ °dONLNdj
s
å

Ø)    eceipt fr¡`°dONLNds
s
∞

Ô)$om the server °dONLNdÅ
Ää
åª(
âäapplication6‡°dONLNdå
ĺ
åƒ)2. Iï`°dONLNdè
ă
å…)f i@°dONLNdë
Ä 
å
6)AEInteractWithUserbÄ°dONLNd£
Ä
6
å
d)l does not r»†°dONLNdÆ
Ä
d
å
ç).
eceive a rÈ`°dONLNd∏
Ä
ç
å
∫))
esponse frÿÄ°dONLNd¬
Ä
∫
å)-om the user within °dONLNd’
çä
ô∂(
ñä
the specifiKÄ°dONLNd‡
ç∑
ô”)-ed tim؆°dONLNdÊ
ç”
ô⁄)e,˘@°dONLNdË
ç⁄
ô‹)
 y@°dONLNdÈ
ç›
ô
I)AEInteractWithUserrÄ°dONLNd˚
ç
I
ô
O)l r∑Ä°dONLNd˝
ç
O
ô
m)eturns K†°dONLNd
ç
n
ô
∂)errAETimeoutG °dONLNd
ç
∂
ô
ª)H. °dONLNd
üä
´ê(
®ä
Y@Ä°dONLNd
üê
´)Uou may want to give the user a method of setting the interaction level. For example, °dONLNdi
¨ä
∏
.(
µä$some users may not want to be interrÑ¿°dONLNdç
¨
.
∏
É)§upted while backgrS†°dONLNdü
¨
Ñ
∏
ß)Vound prÄ°dONLNd¶
¨
®
∏
Ë)$ocessing of an 3 °dONLNdµ
¨
Ë
∏)@Apple °dONLNdª
πä
≈
7(
¬ä'event occurs, or they may not want to rdž°dONLNd‚
π
7
≈)≠0espond to dialog boxes when your application is °dONLNd
Δä
“¥(
œä    handling ë`°dONLNd
Δ¥
“
)*Apple events sent frL`°dONLNd/
Δ

“
m)Yom another computer±°dONLNdB
Δ
l
“
n)_
.ˇ$å@ˇˇˇˇˇ@

ˇ·ˇ‚7^
4*\
¯,Palatino
&e.
3+l"CHAPTER ”)>
4,    Helvetica    ˇˇ—ÚˇÆ(@lResponding to ,):Apple Events4⁄*˙
¯

(‡*4-50    )BInteracting WÅ0)5ith the User4^*¿
¯
°dONLNd\lhü(elListing 4-14 @°dONLNd\†h
)4 illustrates the use of the ,
Courier-`°dONLNd(\
h
z)nAEInteractWithUser&†°dONLNd:\
zh
¶)l function. á@°dONLNdE\
¶h
¨),
YG¿°dONLNdF\
¨h
fi)ou call this °dONLNdSilu™(rlfunction befoṙ°dONLNdai™u
Ê)>Ie your application displays a dialog box or otherwise interacts with the °dONLNd™vlǶ(luser when pr
‡°dONLNd∂vßÇ‹);ocessing an  °dONLNd¬v€Ç
)4Apple event. @°dONLNdœv
Ç
)<
YÕ¿°dONLNd–v
Ç
“)+ou specify a timeout value, a pointer to a °dONLNd˚ÉlèÖ(ålNotifi{‡°dONLNd

ÉÜè—)cation Manager r¥¿°dONLNd
É—è„)Kecor) °dONLNd
ɉè
()d, and the addr‡°dONLNd
$É
(è
÷)D)ess of an idle function as parameters to °dONLNd
Mêlúÿ(ôlAEInteractWithUserª‡°dONLNd
_ê◊úŸ)k
.

ø*«
¯4¿*«
¯"¿*_

ˇ·ˇ‚7^
    °dONLNd
aµl¿ù(ΩlListing 4-14°dONLNd
nµ∞¿ÿ)D
Using the @°dONLNd
xµŸ¿
3))AEInteractWithUser/`°dONLNd
äµ
:¿
\)a     function
°dONLNd
ïœl€
(ÿlmyErr := AEInteractWithUsev@°dONLNd
؜
€
)úr(uÄ°dONLNd
±œ
€
h)kAEDefaultTimep@°dONLNd
øœ
h€
n)T
oo‡°dONLNd
¿œ
n€
z)uto °dONLNd
¬œ
z€
Œ), gMyNotifyReci‡°dONLNd
–œ
Œ€
‡)TPtrh¿°dONLNd
”œ
‡€
Ï), °dONLNd
fl›
È
(Ê

 †°dONLNd
‡›
È
)
@@°dONLNd
·›
È
z)MyIdleFunction);°dONLNd
ÚÎl˜(ÙlIF myErr <> noErr THEN°dONLNd
˘~

»+7{the attempt to interact failed; do any error handling}°dONLNdC
~
“*DoError(myErr)°dONLNdR
l
!Ñ(
lELSE°dONLNdX
#~
/
∂+4{interact with the user by displaying a dialog box }°dONLNdé
1~
=
»*7{ or by interacting in any other way that is necessary}°dONLNd«
?~
K*DisplayMyDialogBox;x‡°dONLNd⁄
?
Kˆ)r
 °dONLNd‹
Wl
cr(
`l
Y@Ä°dONLNd›
Wr
c
0).ou can set a timeout value, in ticks, in the fiÛ@°dONLNd
W
0
c
y)ærst parameter to . °dONLNd
W
z
c
Ê)JAEInteractWithUserj°dONLNd/
W
Â
c
Í)k. °dONLNd1
dl
pè(
mlUse the +@°dONLNd9
dê
pˆ)$kAEDefaultTimeout$‡°dONLNdJ
dˆ
p
e)f constant if you want the †‡°dONLNdd
d
e
p
Ì)oApple Event Manager to use a °dONLNdÅ
ql
}
(
zl)default value for the timeout value. The (°dONLNd™
q

}
Í)≤,Apple Event Manager uses a timeout value of °dONLNd÷
~l
ä
7(
ál/about one minute if you specify this constant. ⁄ °dONLNd
~
7
ä
=)À
Yö†°dONLNd
~
=
ä
¢)ou can also specify the ïÄ°dONLNd
~
£
ä
fl)f
kNoTimeOutë¿°dONLNd(
~
fl
ä
·)<
 °dONLNd)
ãl
ó
[(
îl8constant if your application is willing to wait an indefiq°dONLNdb
ã
\
ó
–)nite amount of time for a r≠‡°dONLNd}
ã
–
ó
ı)tesponse °dONLNdÖ
òl
§s(
°lfrò‡°dONLNdá
òs
§ß)om the user¿°dONLNdí
òß
§
)4. Usually you should prP°dONLNd©
ò

§
Ò)h4ovide a timeout value, so that your application can °dONLNd›
•l
±†(
Ælcomplete prA°dONLNdË
•°
±‰)5ocessing of the {†°dONLNd¯
•‰
±
3)CApple event in a r≈ °dONLNd

•
3
±
©)Oeasonable amount of time. °dONLNd%
∑l
ê(
¿lIf you specify Ä°dONLNd4
∑´
√Ω)?NIL£°dONLNd7
∑º
√
) instead of a NotifiÜ¿°dONLNdK
∑

√
Y)Rcation Manager rø†°dONLNd[
∑
Y
√
k)Kecor4°dONLNd_
∑
l
√
Ï)d in the second parameter of °dONLNd|
ƒl
–ÿ(
ÕlAEInteractWithUserª‡°dONLNdé
ƒ◊
–Ï)k, the ∫‡°dONLNdî
ƒÏ
–
˜);Apple Event Manager looks for an application icon with the °dONLNdœ
—l
ݖ(
⁄l    ID specifi⇰dONLNdŸ
—ñ
›
!)* ed by the application’s bundle ( @°dONLNd˘
—
"
›
()å
'‡°dONLNd˙
—
(
›
@)BNDL`°dONLNd˛
—
@
›
F)
'°dONLNdˇ
—
F
›
O)) r∂‡°dONLNd
—
O
›
g)    esourˇ °dONLNd
—
g
›
◊)ce and the application’s fiÀ`°dONLNd"
—
ÿ
›
‚)qle °dONLNd%
fil
Ío(
Ál
rE°dONLNd&
fip
ÍÄ)eferÒ °dONLNd*
ހ
Íô)ence (ô‡°dONLNd0
fiö
͆)
'ôÄ°dONLNd1
ޠ
Í∏)FREFò°dONLNd5
fi∏
Íæ)
'ó†°dONLNd6
fiæ
Í«)) r0Ä°dONLNd9
fi»
͇)
esourx¿°dONLNd>
fi‡
Í

)ce. The ê°dONLNdF
fi


Í
k)!Apple Event Manager fiÀ†°dONLNd\
fi
k
Í
¢)jrst looks for  °dONLNdj
fi
£
Í
∞)8an jÄ°dONLNdm
fi
∞
Í
∂)
'j °dONLNdn
fi
∂
Í
Œ)SICNh†°dONLNdr
fi
Œ
Í
‘)
'h@°dONLNds
fi
‘
Í
÷)
 °dONLNdt
Îl
˜o(
Ùl
rE°dONLNdu
Îp
˜à)esourç@°dONLNdz
Îà
˜◊)ce with the specifi¿°dONLNdç
Î◊
˜
#)Oed ID; if it can’t fi•‡°dONLNd¢
Î
$
˜
?)Mnd an d`°dONLNd®
Î
@
˜
F)
'd°dONLNd©
Î
F
˜
^)SICNbÄ°dONLNd≠
Î
^
˜
d)
'b °dONLNdÆ
Î
d
˜
j) rß °dONLNd∞
Î
j
˜
Ç)esourÔ`°dONLNdµ
Î
Ç
˜
“)ce, it looks for the °dONLNd 
¯lr(
l
'†°dONLNdÀ
¯rä)ICN#~ °dONLNdœ
¯äê)
'}¿°dONLNd–
¯êñ) r¬¿°dONLNd“
¯ñÆ)esour°dONLNd◊
¯Ø≈)ce anñ@°dONLNd‹
¯≈Í)d compr≤‡°dONLNd„
¯Í
+)%esses the icon t<`°dONLNdÛ
¯
,
7)Bo fV@°dONLNdˆ
¯
7
Ö)it in the menu barK °dONLNd
¯
Ö
ù)N. The (Ä°dONLNd
¯
ù
◊)Apple Event °dONLNdl
‘(lOManager won’t look for any members of an icon family other than the icon specifi†°dONLNdj
’
Ì(
’ed in °dONLNdpl|(lthe ›`°dONLNdt|Ç)
'›°dONLNduÇö)ICN#€Ä°dONLNdyö†)
'€ °dONLNdz†¶) r  °dONLNd|ßø)esourh`°dONLNdÅø )ce.°dONLNdÖ$l0Ù(-l If the application doesn’t have ˙¿°dONLNd•$Ù0˙)à
'˙`°dONLNd¶$˙0
)SICN¯‡°dONLNd™$
0
)
'¯Ä°dONLNd´$
0
&) or `†°dONLNdØ$
'0
-)
'`@°dONLNd∞$
-0
E)ICN#^¿°dONLNd¥$
E0
K)
'^`°dONLNdµ$
K0
Q) r£`°dONLNd∑$
Q0
i)esourΆ°dONLNdº$
i0
·)ces, or if it doesn’t have a fiÚÄ°dONLNd€$
·0